 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 09 Nov 2008 19:00:24 +0100, Darren New <dne### [at] san rrcom> wrote:
> My stumbling block here is that if I use chroot, I no longer have /dev
> for GRUB to write things to.
You must bind /dev in the new environment before chrooting.
Gentoo users know how to chroot properly, as it is a required step when
installing Gentoo:
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fredrik Eriksson wrote:
> You must bind /dev in the new environment before chrooting.
>
> Gentoo users know how to chroot properly, as it is a required step when
> installing Gentoo:
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6
Thanks. I figured it was merely a stumbling block rather than a wall. ;-)
I'll put that into my instructions file under "in case of complete user
screw-up..."
I'm learning way more about system administration than I ever wanted to
know, you know? :-)
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 09 Nov 2008 10:00:24 -0800, Darren New wrote:
> Jim Henderson wrote:
>> Yeah, I would concur with that - have had that experience myself.
>
> My stumbling block here is that if I use chroot, I no longer have /dev
> for GRUB to write things to. If it comes to that much of a disaster,
> I'll reinstall stuff and rescue things on a per-file/per-directory
> basis. :-)
I also mount /dev/ in the chrooted environment.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
