On Sun, Feb 27, 2005 at 08:55:41AM -0500, Harry Cochran wrote: > Done. And it boots 2.6.8-2-32-smp!
good. Now you know what to write up :^) > >If that boots, then: > >o unmount /boot > > No ... umount /boot or umount -f /boot comes back with: > "device is busy" Sounds like sda1 did not get mounted as /boot Does "mount" list /boot? > Is there a problem leaving the redundant /boot on sda3? Only that it might cause confusion later. > SinoHub5:/# fdisk -l /dev/sda ... Good ... > SinoHub5:/# mount > /dev/sda3 on / type ext2 (rw,errors=remount-ro) > proc on /proc type proc (rw) > /dev/sda1 on /boot type ext2 (rw) > /dev/sdb1 on /var type ext3 (rw) Good > SinoHub5:/# cat /etc/palo.conf Good > SinoHub5:/# ls -l /boot > total 0 Not Good. vmlinux/initrd symlinks and *-2.6.8.1-2-* files should be here. > >The "ls" command assumes the f0 partition is mounted on /boot. > > Well I was feeling pretty good until I saw ls -l /boot come back with total > 0. I assume that's bad news. Right. > You didn't say to change init-partitioned to > update-partitioned, so maybe I screwed up there. Should I have just gotten > rid of that line? No - you've already run "palo --init-partition" once and that's sufficient. The vmlinux/initrd didn't get copied to sda1 when it was mounted as /mnt. umount sda1 by hand and "mount /dev/sda1 /mnt" so you can clone the original contents of /boot (sda3) to /mnt (sda1). > Thanks again Grant. This is very close now. I just need one more push to > complete. I hope you have time to reply today. For some definition of today :^) welcome, grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
