Neil Bothwick <n...@digimed.co.uk> writes:

> On Sun, 26 Jun 2011 13:34:56 -0500, Harry Putnam wrote:
>
>> (From chrooted shell)
>> 
>> root@sysresccd /dev % ls -l console null
>> crw-rw---- 1 root root 5, 1 Jun 26 17:33 console
>> crw-rw---- 1 root root 1, 3 Jun 26 17:33 null
>
> When you chroot to the install root, you normally bind mount dev first,
> so I would expect those files to be there. Are they there before you
> chroot or bind mount anything?

No... and I'm now getting it that they should be.

Anyway, I'm downloading the latest stage3 I found (06/14) I'll explode
it in a test directory and see whats there.  I've emerged so much
stuff now on the one I been working on that I hate to bugger it up if
there is much chance of salvaging it.  All those kernel builds left
lots of time for emerging all my pet stuff.

ok, a freshly exploded stage3 from 06/14 shows only null being an
un-bound  /dev/ and its a plain file
 # ls -l
  -rw-r--r-- 1 root root 0 Jun 14 13:08 null

So now I've got them in place BEFORE binding to the install media
/dev.

ls -l /mnt/gentoo/dev

-------        ---------       ---=---       ---------      -------- 
Mark Knecht <markkne...@gmail.com> writes:

[...]


> I'm very curious - did you happen to try appending something like
>
> init=/sbin/init 1
>
> to the boot kernel command and seeing what happens? That might be
> instructive about where it's really getting to or what is stopping it
> from proceeding.

No, haven't done that yet.  In fact with /dev/console and dev/null
created in an un-bound /dev as sharp eyed Neil pointed out, I can now
get farther in the boot process.

However, now I'm running into many other problems and still no boot.
many tty could not be accessed but then on reboot with SystemRescueCD
again, I see they were generated into /dev/ but are not character
files.

There was some kind of problem with fsck and at least 2 other
problems something to do with urandom and another I lost track of.

At this point, I'm going to scrap the guest as by now I don't know if
I'm coming or going with this thing.  Boot process has written junk
into dev/, I've written junk into dev/ so I'm starting clean.

I've downloaded a new stg3, new snapshot of portage so I'm going to
try with all untampered with stuff.

I guess I am to create /dev/null and /dev/console again as per
instructions (that is, in an un-bound /mnt/gentoo/dev/)

(Is it normal to find `null' created as a regular file in dev/ (before
any tampering?)

Install vim, eix, reiserfsprogs, rsyslog, grub and gentoo-sources.
Build the kernel, then see what happens. (using your config again)

If it doesn't boot I'll boot to single mode as you requested and see
what I see.


Reply via email to