Thanks Andy and Ken.
I suspect that some combination of modules and perhaps a missing initrd.img
file is my issue.
On Sat, Oct 30, 2010 at 5:41 PM, Ken Moffat wrote:
> On Sat, Oct 30, 2010 at 04:41:12PM -0600, John Mitchell wrote:
> >
> > I don't think this is a 'grub
, 30 Oct 2010 16:41:12 -0600
> John Mitchell wrote:
>
> > Thanks Andy.
> >
> > I'm a bit out of phase with the email server.
> >
> > Yes -- the kernel does boot and prints a bunch of stuff (successful
> stuff)
> > to screen.
> >
> > T
Andy,
The error is emitted from:
./init/do_mounts.c
I ran the following command and found this one match above:
find . -name *.c -exec grep "Cannot open root device" {} \; -print
Regards,
John
On Sat, Oct 30, 2010 at 4:41 PM, John Mitchell wrote:
> Thanks Andy.
>
> I&#
asn't mentioned in the
book-6.7?
Thanks,
John
On Sat, Oct 30, 2010 at 4:03 PM, Andrew Benton wrote:
> On Sat, 30 Oct 2010 15:10:04 -0600
> John Mitchell wrote:
>
> > Hi,
> >
> > I have an older and existing grub (0.98) installation on my host that
> >
Thanks for your reply Andy.
Yes -- the kernel is found and it seems to run along just fine until
the following error:
VFS: Cannot open root device "sdb8" or unknown-block(0,0)
There are a few more messages after that but I don't really have
access to them because I have know way to save them.
T
Hi,
I have an older and existing grub (0.98) installation on my host that
works.
I was hoping to use my existing grub installation and point to my new LFS
system.
I believe that the new kernel is found -- there seems to be trouble with
finding the LFS '/' partition.
Any ideas or suggestions?
R
I think the given syntax will work but here is a simple working example that
includes ''case'' in the way you were looking for. this does the "ls"
command back to back followed by the switch statement followed by another
"ls" command:
time { ls && ls && case $(uname -m) in x86_64) echo "HELLO" ;
Hi,
I don't quite understand how re-writing the 'specs' file under the '/tools'
directory actually works -- by the way it does work!.
The specs file that is written with the fancy 'sed' script shows up as:
/tools/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/specs
I don't get how writing the spec file
Hi Edgar,
I'm curious about your "Fedora 13" basis. I have been using RH and Fedora
for many years but never really dug into linux like this. I have finally
become frustrated enough with the maintenance/upgrade issues that I decided
to take more control.
Can you perhaps describe (to whatever de
Hi,
I'm wandering if it makes any sense to configure /etc/ld.so.conf to include
lib64 directories
- /usr/local/lib64
- /opt/lib64
I guess this can always be added later?
Thanks,
John
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/fa
Casey,
Hmm... it appears that you didn't run one of the commands given in the
book.
QUOTING FROM THE BOOK: Section 6.9
When running *make install*, a script called test-installation.pl performs a
small sanity test on our newly installed Glibc. However, because our
toolchain still points to the /
FYI: The compiler segfault below created one of my test errors that I
reported earlier. -- This is one I guess I can legitimately ignore?
Not sure about the remaining errors:
make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/sources/glibc-build/nptl/tst-rwlock6.ou
Hi,
This is my first crack at LFS. I'm wandering if the error associated with
the link below was ever resolved?
*Previous and related errors:*
http://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg14143.html
*My setup:*
- Book 6.7
- 64 bit -- athlon x2
- host kernel = 2.6.31
13 matches
Mail list logo
