On Thursday 24 April 2008, darren kirby wrote:
> > Well, I had to put a lot more parameters for it to work -- I am not
> > using grub but my parameters aside from the ro are
> > init=/linuxrc ramdisk=8192 real_root=/dev/sda2 udev
> > and some more specific to me. I am using something close to the
quoth the John covici:
> on Thursday 04/24/2008 Alan McKinnon([EMAIL PROTECTED]) wrote
>
> > On Thursday 24 April 2008, [EMAIL PROTECTED] wrote:
> > > So assuming I've made some mistake in grub.conf I try to boot from
> > > grub command line.
> > >
> > > root = (hd0,0) (which is /dev/sda1
on Thursday 04/24/2008 Alan McKinnon([EMAIL PROTECTED]) wrote
> On Thursday 24 April 2008, [EMAIL PROTECTED] wrote:
>
> > So assuming I've made some mistake in grub.conf I try to boot from
> > grub command line.
> >
> > root = (hd0,0) (which is /dev/sda1 in linux terms)
> >
> > kerne
On Thursday 24 April 2008, [EMAIL PROTECTED] wrote:
> So assuming I've made some mistake in grub.conf I try to boot from
> grub command line.
>
> root = (hd0,0) (which is /dev/sda1 in linux terms)
>
> kernel /kernel-2.6.25-r1
Nope. Kernel needs a root= parameter. It can't know what is your
Just when I began to think I knew a thing or two about grub I'm
finding I am failing to get a working grub.conf going on a new
install.
True, the install is inside a vmware machine on windows vista but that
has not presented a problem in previous versions of windows and it
does not appear to be h
5 matches
Mail list logo