You don't understand. It would probably work fine-- BUT the problem
remains. The system sees /dev/sda1 mounted as / because the bootloader
managed to see it and mount it (which it needed to do, simply to access
/vmlinuz itself), but that's it. WHEN I RUN FDISK /DEV/SDA, IT SAYS THAT
/DEV/SDA DOES NOT EXIST. It's that bad.
That is: Once booted, the system simply DOES NOT RECOGNIZE that /dev/sda
has ANY partition table. Even though I (as noted earlier) compiled in
support for ALL available partition table types, including Sun *AND* PC
(and all the others too!)
This is so frustrating.
On Sun, 18 Apr 2004, Mustafa Hussein wrote:
> > JLB
> > I just installed Debian 3.0 on my Sun Ultra 1. I set it up with a nice
> > neat Sun disklabel ('s' in fdisk). It boots great. It works great.
> >
> > Then I try compiling my own kernel-- 2.4.26, from the stock Linux kernel
> > sources available at ftp.kernel.org. I modify silo.conf appropriately, run
> > 'silo'. Reboot. Get the boot prompt and select my new kernel. It starts to
> > boot... then I get 'ldm_validate_partition_table' puking, and the error
> > "No MS-DOS partition table". It asks for my root password for maintenance,
> > and I give it to it. It drops me straight into bash.
>
> What happens if you just do "init 2" from bash?
>
--
Jessica L. Blank, Systems Administrator, twu.net
