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

Bug#252672: Package: installation-reports

Package: installation-reports

Debian-installer-version:  Debian GNU/Linux testing "Sarge" - Official
NetInst Snapshot i386 Binary-1 (20040315)uname -a: -
Date: April 24, 2004
Method: Boot and install directly from CD
Machine: Homebuilt w Matsonic MS7016S mb
Processor: Celeron 366
Memory: 256Mb
Root Device: IDE Seagate 80Gb
Root Size/partition table:  

Output of lspci:

Base System Installation Checklist:

Initial boot worked:    [ ]
Configure network HW:   [O]
Config network:         [E]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [E]
Create file systems:    [ ]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [E]
Reboot:                 [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it


"Configure the Network"
- The text reads "In rare circumstances, you may have no router, in that
case you can leave this blank."
- I left the box blank and I received the error message "Malformed IP

"Partition disks" errors
I had previously partitioned my disk using cfdisk without any problems or
errors. According to the fdisk man page, cfdisk is the preferred
partitioning tool under linux followed by fdisk followed by parted. I also
inferred that preferred also meant safest.' Consequently, I was not actually
trying to re-partition my disk but was rather informing the installer (or so
I thought) of my current layout and how I planned to use it. Everthing
seemed to be going well until the time came to actually confirm/partition my
disk when I received the message that my disk "has a rather strange layout"
and so the disk cannot be resized(!) without errors. Since this is not the
first time I have had an installer tell me this with the various
configurations I have had -- I received a previous error from Mandrake's
Disk Druid that said essentially the same thing -- I did not worry too much
about it. 

After the paritioning problems I went to the command line ran mkreiserfs on
my target partition and mounted it under /TARGET and then returned to the
menu. When I selected "Install Base System" I received another error
"/usr/sbin/mkinitrd: cannot determine root device." I figured that I could
always use a different kernel image + initrd copied over from somewhere

"Partition disks, Method for using this partition"
- It would be a nice feature if the text displayed the name of the partition
in question -- e.g. /dev/hda6

"Install a bootloader"
I have been using Grub without any problems and it was already installed and
therefore I had initially chosen NOT to install a bootloader. At some time
during the install after the partition error mentioned above, I changed my
mind, however. I selected the "Install Grub" menu item but was then taken
back into the "Partition disks" dialogue! Since when does GRUB depend on a
harddisk layout created by parted? This seems to me a bad dependency.
Never-the-less, I figured that I could do the same using the shell but I was
mistaken: I could not find grub or the grub-installer anywhere in the root
filesystem accessible to me.    

Comment on the use of Devfs
According to what I have read, devfs is deprecated in favor of udev+sysfs. I
was a fan of devfs until I read the udev developer's account so I would have
been all for the move to incorporate devfs in the installer up until a few
months ago. However, it seems to me that if devfs is used in the installer
then the devices should at least be mapped to standard names so I don't have
to do /dev/discs/disc0/ etc. to get to /dev/hda6. 


Tollef Fog Heen <mailto:tfheen@debian.org>

Last modified: Sun Dec  8 00:01:34 CET 2002


Reply to: