[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#347189: marked as done (base-config Terminating (devices missing))

Your message dated Wed, 17 Feb 2010 17:09:00 -0500
with message-id <20100217220900.GA12701@gnu.kitenet.net>
and subject line closing old base-config related bug
has caused the Debian Bug report #347189,
regarding base-config Terminating (devices missing)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

347189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347189
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 3.3.

When i try to debootstrap a new chroot under 0.3.3, call to
base-config fails with words "Terminated", where on 0.2.45 this

a# debootstrap sarge testchroot http://http.us.debian.org/debian
a# chroot testchroot /bin/bash
a-chrooted# base-config

Making a diff on 0.2.45 and 0.3.3 I remarked, that many devices are
not installed anymore in 0.3.3. If I tar them on my 0.2.45 chroot
and untar then on 0.3.3, base-config works.
At present I can't tell which device exactly is missing.
For the installation of some software-packages (I tried ssh) there
seem also to be missing devices.

Any reason for this device list reduction?
I couldn't find documentation on these updates and I may not understand
fully If there need to be another step of system setup to complete
the debootstrapped systems configuration (installing also devices)..

Thanks for any info/update!

+-------------------------------+  +-------------------------------+
| Miro Dietiker                 |  | MD Systems Miro Dietiker      |
+-------------------------------+  +-------------------------------+

--- End Message ---
--- Begin Message ---
From what I can remember of base-config, the behavior in this bug
might have happened if TTY was set to an unusual device (ie, not
/dev/tty*), since base-config reattached script(1) to the tty.

Anyway, in the current system, debootstrap provides only a minimal
/dev. Most devices are provided at boot time via udev. From the
changelog of debootstrap 0.3.1:

    - devices.tar.gz reduced to minimal set of devices; frontends should
      setup udev or supply their own devices or similar in future

(PS, what kind of a debootstrap version is "3.3." ?!)

If you need more devices in a debootstrapped chroot, IMHO the best
option is to mount --bind /dev chroot/dev before chrooting. 
Or, you can run MAKEDEV in the chroot.

see shy jo

Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: