Stephen Wille Padnos wrote: > > Note that Ubuntu creates a boot directory in its root partition and does > not mount a separate boot partition by default. It is best to check > whether /boot is a separate partition before looking for kernels there, > since you're guaranteed to not see any BDI kernels in the Ubuntu root > partition. you can check with the command mount. This will print a > list of complicated entries, but the thing you're looking for is "/boot" > in the "mount point" column. > OK, then that boot partition (/dev/sda1) must be his BDI boot partition. Not too clear on what may have been done to the boot block when he installed Ubuntu over the BDI. Probably the only way to boot BDI there would be to copy over the boot file, kernel and menu entries from /dev/sda1 to the Ubuntu /boot directory. I'm pretty sure I could do this and make it work, I used to be pretty good with grub and lilo back when I had real problems with grub under BDI and had to hack things. Haven't needed that level of mucking around since Ubuntu. > > > This isn't quite true. Linux doesn't care a bit about spaces in > filenames, and there are several ways to make sure they're not treated > as whitespace. Yeah, it really is just the command line parsing that needs to know where the file name ends.
Jon ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
