[ale] Kernel panic: No init found?????

[Jim Seymour]

Joseph A Knapka wrote:
> Try "init=/bin/bash". If it works, that will get you
> a command line on an "empty" machine (no daemons,
> no networking, no nothing). You can then browse around
> the filesystem and see what's up. Normally init
> would be /sbin/init; make sure that file exists, and is
> executable.
> 
> If "init=/bin/bash" results in the same error, then
> it probably means your hard drive's partition table
> is fried. If you have a copy of the partition table
> around (it's always a good idea!), you can boot into
> something like TomsRootBoot and fdisk the HD back
> into shape. You will probably need to run lilo
> after doing so. Let us know if you get this far.
> 
> Cheers,
> 
> -- Joe

Well still a no go.  The init=/bin/bash stopped at the same point. 
Based on what you've said it looks like a reinstall.  I do not have a
copy of the partition table :-(

Thanks,
Jim Seymour

---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.