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

Bug#365669: marked as done (debootstrap doesn't create /dev/hd* entries)

Your message dated Wed, 21 Sep 2016 01:19:36 +0200
with message-id <87k2e6xipj.fsf@deep-thought.43-1.org>
and subject line Re: Bug#365669: debootstrap and devices
has caused the Debian Bug report #365669,
regarding debootstrap doesn't create /dev/hd* entries
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
immediately.)


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

Subject says it all: no /dev/hd* entries are created by debootstrap.

Configuration
-------------

VmWare on Windows, with an hda and a hdc drive.
Booting from hdc, which carries what I'll call the "base system", a netboot image that I ripped off from my rootserver provider and adapted to boot from hdc. 
Incidentally, the base system is a Debian, with a 2.6.26 kernel.
I'm bootstrapping things onto the hda drive. hda partitions were mounted on the following mountpoints (which hence had to be created before running debootstrap): 
  /inst      /dev/hda5
  /inst/boot /dev/hda1
  /inst/usr  /dev/hda6
  /inst/var  /dev/hda7

Behaviour
---------
debootstrap runs through without any problems, and populates /inst/dev in three steps: 
1) Create the /dev directory (very early, even before downloading packages).
2) Create a lot of standard devices (core, full, kmem, loop*, mem, null, port, ptmx, ram*, random, tty, urandom, zero; after download). 3) Create the MAKEDEV script and devices that seem at least partly 386-specific (agpgart, audio*, console, dsp*, initctl, midi*, mixer*, mpu*, pts, rmidi*, sequencer, shm, smpte*, sndstat, tty0; almost near the end of the process).
It does not create /dev/hd* (or /dev/sd*) nodes, though I'm pretty sure they *should* be created (all the instructions on the WWW say "debootstrap, then chroot", and don't mention having to manually create the /dev/hd* nodes; I'm actually following their leads, so I'm not sure where exactly I'm doing things differently.) 

What next?
----------

* Did I make any dumb mistakes,
* should I turn to a mailing list for advice (I didn't find a clueful one yet, pointers very much appreciated!), or 
* is this a bug in debootstrap?
I'm willing to provide any logs or other information, or run additional tests as requests. FWIW, a full transcript of the installation steps I took can be found at http://durchholz.org/jo/debian-install/Main/DebianRootServer . The steps relevant for my current problems can be found starting at http://durchholz.org/jo/debian-install/Main/AllocatePartitions#ConcretePartitionLayout 

Regards,
Jo

--- End Message ---
--- Begin Message --- 
With udev and debootstrap only creating a minimal /dev (#571136), I
don't think this bug is relevant any longer and should be closed.

Ansgar

--- End Message ---
Reply to: