|
osdir.com mailing list archive |
|
Subject: Re: Re: 2.6 kernel - msg#00090List: linux.mondo.develTom Mortell wrote:- Here are some of my observations using mindi-0.95-1 mondo-1.75-1 under bleeding-edge Linux 2.6.1. Please try the snapshots. OK, now testing with mindi-0.95_cvs_20040204-1.i386.rpm and mondo-1.75_cvs_20040204-fdr10.i386.rpm for Fedora Core 1. Ouch 3) I went to the trouble to compile a custom kernel for a machine with skimpy memory and made ramdisk a module: rd.ko. Mondoarchive complained because there was no ramdisk device. "modprobe rd" before running mondoarchive took the pain out of that one. I _think_ this has been fixed but I'm not sure. Try the snapshot. Also try adding 'rd' to the list of modules at the start of mindi - FLOPPY_MODS probably. In /usr/local/bin/mindi, I added "rd" to FLOPPY_MODS="ide-floppy floppy rd". No improvement on running mondoarchive. I see that the check for a ramdisk is done in mondo/common/libmondo-tools.c: if (run_program_and_log_output ("cat /proc/devices | grep ramdisk", FALSE)) { if (!ask_me_yes_or_no("Your kernel has no ramdisk support. That's mind-numbingly stupid but I'll allow it if you're planning to use a failsafe kernel. Are you?")) Fedora compiles ramdisk into the kernel. I made ramdisk a module for my little old computer, so until the ramdisk is used, there is no "ramdisk" in /proc/devices. By following the instructions in "docs/AdvBashScript/ramdisk.sh", the module rd is loaded and, since I didn't specify the file system type, vfat. (vfat is in /etc/filesystems, which is examined before /proc/filesystems, which contains ramfs.) I will continue to do 'fgrep -q "ramdisk" /proc/devices || modprobe rd' in my script that runs mondoarchive. I my opinion, anyone who compiles his own kernel, is likely to know what modules have to be loaded and therefore no change has to be made to mondoarchive. -- Tom Mortell ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn Thread at a glance:
Previous Message by Date: click to view message previewRe: Re: 2.6 kernelHugo Rabson wrote: Tom Mortell wrote:- Ouch 1) The standard 2.6 kernel was too big to fit on a floppy. Mondoarchive's "-k FAILSAFE" option got around that thorn. The solution is to put the kernel on one floppy and the ramdisk on another. No-one has so far come forward to implement this functionality. Paying customers haven't asked for it either. That means it is fairly far down the list of things to do. Fedora Core 1 development vmlinuz-2.6.1-1.47 has a size of 1468543 bytes (1.4 M). It will fit on an ext2 formated floppy, fd0u1722, 1.6M. 'df -h' reports it to be 91% full. I guess it won't be long before the standard, compressed kernel won't fit. Some new PCs are shipped without floppy drives. For my old PC, the FAILSAFE kernel is adequate for restore processing. As far as I am concerned, you can push the "2 floppy boot" farther down the list. -- Tom Mortell ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn Next Message by Date: click to view message previewRe: Re: 2.6 kernelHugo Rabson wrote: Tom Mortell wrote:- Here are some of my observations using mindi-0.95-1 mondo-1.75-1 under bleeding-edge Linux 2.6.1. Please try the snapshots. Now testing with mindi-0.95_cvs_20040204-1.i386.rpm and mondo-1.75_cvs_20040204-fdr10.i386.rpm for Fedora Core 1. Ouch 9) It needed "modprobe vfat" to do a "-Vi" ---FATALERROR--- Either call mondoarchive with '-o', or recompile your kernel to include VFAT support. That's a bug in your distro. It should autoload vfat.o (vfat.ko, if 2.6) if the vfat filesystem is required by a userland program. (Jesse, Joshua, correct me if I'm wrong, please?) On rebooting to clean out modules, and then running: mondoarchive -Vn 192.168.0.1:/tftpboot -d /backup with the nfs partition mounted, I get the error message: " Checking sanity of your Linux distribution Done. Your kernel appears not to support vfat filesystems. I am therefore using LILO instead of SYSLINUX as the CD/floppy's boot loader. " I see that in mondo/common/libmondo-devices.c, at is_this_a_valid_disk_format (char *format) the line cat /proc/filesystems ... checks for the existence of the filesystem, eg, vfat. When I do: # fgrep "vfat" /proc/filesystems # echo $? 1 and then # modprobe vfat then do # fgrep "vfat" /proc/filesystems vfat # echo $? 0 So "vfat" is found in /proc/filesystems only after the module is loaded. vfat is also in /etc/filesystems, which is provided by setup-2.5.27-1.1. This is probably very distribution dependent. If I can think of a better way of checking on the ability to handle a filesystem, I will make a patch. If and until then, doing fgrep -q "vfat" /proc/filesystems || modprobe vfat in my backup script takes care of that problem for this linux 2.6 user. -- Tom Mortell ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn Previous Message by Thread: click to view message previewRe: Re: 2.6 kernelHugo Rabson wrote: Tom Mortell wrote:- Ouch 1) The standard 2.6 kernel was too big to fit on a floppy. Mondoarchive's "-k FAILSAFE" option got around that thorn. The solution is to put the kernel on one floppy and the ramdisk on another. No-one has so far come forward to implement this functionality. Paying customers haven't asked for it either. That means it is fairly far down the list of things to do. Fedora Core 1 development vmlinuz-2.6.1-1.47 has a size of 1468543 bytes (1.4 M). It will fit on an ext2 formated floppy, fd0u1722, 1.6M. 'df -h' reports it to be 91% full. I guess it won't be long before the standard, compressed kernel won't fit. Some new PCs are shipped without floppy drives. For my old PC, the FAILSAFE kernel is adequate for restore processing. As far as I am concerned, you can push the "2 floppy boot" farther down the list. -- Tom Mortell ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn Next Message by Thread: click to view message previewRe: Re: 2.6 kernelHugo Rabson wrote: Tom Mortell wrote:- Here are some of my observations using mindi-0.95-1 mondo-1.75-1 under bleeding-edge Linux 2.6.1. Please try the snapshots. Now testing with mindi-0.95_cvs_20040204-1.i386.rpm and mondo-1.75_cvs_20040204-fdr10.i386.rpm for Fedora Core 1. Ouch 9) It needed "modprobe vfat" to do a "-Vi" ---FATALERROR--- Either call mondoarchive with '-o', or recompile your kernel to include VFAT support. That's a bug in your distro. It should autoload vfat.o (vfat.ko, if 2.6) if the vfat filesystem is required by a userland program. (Jesse, Joshua, correct me if I'm wrong, please?) On rebooting to clean out modules, and then running: mondoarchive -Vn 192.168.0.1:/tftpboot -d /backup with the nfs partition mounted, I get the error message: " Checking sanity of your Linux distribution Done. Your kernel appears not to support vfat filesystems. I am therefore using LILO instead of SYSLINUX as the CD/floppy's boot loader. " I see that in mondo/common/libmondo-devices.c, at is_this_a_valid_disk_format (char *format) the line cat /proc/filesystems ... checks for the existence of the filesystem, eg, vfat. When I do: # fgrep "vfat" /proc/filesystems # echo $? 1 and then # modprobe vfat then do # fgrep "vfat" /proc/filesystems vfat # echo $? 0 So "vfat" is found in /proc/filesystems only after the module is loaded. vfat is also in /etc/filesystems, which is provided by setup-2.5.27-1.1. This is probably very distribution dependent. If I can think of a better way of checking on the ability to handle a filesystem, I will make a patch. If and until then, doing fgrep -q "vfat" /proc/filesystems || modprobe vfat in my backup script takes care of that problem for this linux 2.6 user. -- Tom Mortell ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn Loading Comments...
|
|
