Re: Proposal for integration of the graphical installer

[Frans Pop]

On Saturday 13 May 2006 23:23, Frans Pop wrote:
> Yesterday Joey and I discussed the integration of the graphical
> installer into the regular build system, and the result is below for
> wider discussion and comments.

Yesterday Joey and I managed to do the integration for i386.
This means that we already have an official daily gtk-miniiso available 
from the "other images" link on the d-i project page:
http://people.debian.org/~joeyh/d-i/images/daily/gtk-miniiso/mini.iso

The latest hd-media image also includes g-i.

CD images that include the graphical installer should be available after 
the next CD build, but may still need changes to get them working.


As soon as we've things tested for i386, I'll also do amd64 which should 
take only very little time as a lot of the configuration is shared with 
i386. As the daily builds for amd64 are down currently due to the archive 
integration, images will probably not be available for a while yet.

I will also take a look at powerpc, integrate things as far as possible 
based on Sven's work and ask Colin to check the changes and fix where 
needed.

Note that the implementation is a bit different from the setup in my 
branch. The setup in trunk is more hierarchical and makes better use of 
the existing configs for regular images, especially for the pkg-list 
files.

Cheers,
FJP


pgpfq5Yd4uZig.pgp
Description: PGP signature

Bug#367149: kbd-chooser: [powerpc] does not detect ADB keyboards

[Eddy Petrişor]

On 5/15/06, Frans Pop <[EMAIL PROTECTED]> wrote:

On Sunday 14 May 2006 07:22, Frans Pop wrote:
> It's currently unsure if the keyboard will work correctly with AT
> keymaps as well as USB-MAC. I'll test that over the next days.

The current daily images now show the AT keymap list. I've tested this on
Frank Lichtenheld's Powerbook G4 laptop, and all keys are mapped OK for
the German keyboard.

The only change from the USB-MAC keymaps is that the apple key no longer
works as the modifier key. Instead these can be accessed using Fn-Alt,
which can probably be explained as that is probably equivalent to the
right-Alt key on "regular" AT keyboards on i386.

AFAICT the options are:
- should the AT keymaps be made to support the apple key as modifier key
or
- should we go back to using the USB-MAC keymaps for powerpc
or
- should powerpc users learn to use Fn-Alt instead of the apple key

Going back to USB-MAC keymaps is possibly not the prefered option because
as I understand it the input layer of the 2.6 kernel translates
everything to "AT", so in principle all architectures should now use AT
keymaps.


I personally use the Option key (or Apple as some might call it) as an
AltGr key. The Fn+Alt is used for right click emulation while
Fn+Option is for middle click. I need all of the keys as they are in
order to be able to use diacritics and be able to use applications in
a fast and confortable manner. So please keep this in mind when you
decide what to do.


P.S. Eddy: a test by you too would be very welcome, especially if you can
do a full installation and check the full range of characters on the
installed system.


Ok, there is a partition on which I can do test installations; btw,
two linux installations on a new world powerpc machine imposes a
problem: all kernels should be placed on the same partition due to a
limitation in yaboot. How does d-i deal with this when Debian is
installed on a system on which there is already installed another
linux system?

--
Regards,
EddyP
=
"Imagination is more important than knowledge" A.Einstein

Bug#367149: kbd-chooser: [powerpc] does not detect ADB keyboards

[Frans Pop]

On Sunday 14 May 2006 07:22, Frans Pop wrote:
> It's currently unsure if the keyboard will work correctly with AT
> keymaps as well as USB-MAC. I'll test that over the next days.

The current daily images now show the AT keymap list. I've tested this on 
Frank Lichtenheld's Powerbook G4 laptop, and all keys are mapped OK for 
the German keyboard.

The only change from the USB-MAC keymaps is that the apple key no longer 
works as the modifier key. Instead these can be accessed using Fn-Alt, 
which can probably be explained as that is probably equivalent to the 
right-Alt key on "regular" AT keyboards on i386.

AFAICT the options are:
- should the AT keymaps be made to support the apple key as modifier key
or
- should we go back to using the USB-MAC keymaps for powerpc
or
- should powerpc users learn to use Fn-Alt instead of the apple key

Going back to USB-MAC keymaps is possibly not the prefered option because 
as I understand it the input layer of the 2.6 kernel translates 
everything to "AT", so in principle all architectures should now use AT 
keymaps.

Advice and comments very welcome.

Cheers,
FJP

P.S. Eddy: a test by you too would be very welcome, especially if you can 
do a full installation and check the full range of characters on the 
installed system.


pgpd7osNC8RfO.pgp
Description: PGP signature

Re: Integrating klibc's ipconfig into netcfg

[Joey Hess]

Andrew Pollock wrote:
> Does that mean the that cases there are largely irrelevant? I mean pump
> doesn't appear to support setting that vendor-class-identifier option...

Yes, we've only used the dhcp 2 client for quite a while, dhcp
preseeding came long after we used anything else, and will need to be
retrofitted for any other dhcp client we use.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#290871: marked as done (installation-reports: pivot_root fails due to /dev naming in grub config)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT

Debian-installer-version: RC2 (20041121)
Date: 2005-01-14
Method: netinst CD

Machine: hp proLiant DL380
Root Device: HP CISS (hardware RAID 5)
   /dev/cciss/c0d0p1 (94M) bootable /boot
   /dev/cciss/c0d0p2 (199G) /
   /dev/cciss/c0d0p3 swap

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [E]

Comments/Problems:

The device naming used in the grub config does not match the names available at
boot time.  Specifically /dev/cciss/c0d0p* devices were not available until
after booting, the /dev/cciss/host0/... naming is used instead.

Boot argument "linux26".  There are no problems booting the CD and
setting up the base system, and no error messages at grub installation.
Reboot fails when it attempts to switch from /boot to root

  /dev/cciss/host0/target0: p1 p2 p3
  pivot_root: No such file or directory
  /sbin/init: 4??: cannot open dev/console: No such file
  Kernel panic: Attempted to kill init!

I rebooted the install CD, got as far as the partition menu, dropped into
a console on F2.
  mount /dev/cciss/host0/target0/part0 /target
  nano /target/grub/menu.list

Located the lines that read
   kernel /vmlinuz-2.6.8-1-386 root=/dev/cciss/c0d0p2
and replaced with
   kernel /vmlinuz-2.6.8-1-386 root=/dev/cciss/host0/target0/part2

unmounted, rebooted.  This works around the problem.



--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#245268: marked as done (failed to find bios drive for /dev/cciss/c0d0p4)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040421/sarge-i386-netinst.iso
uname -a: Linux debian 2.4.25 #1 SMP Sat Nov 1 04:54:10 CET 2003 i686 GNU/Linux 
(self-compiled kernel from another installation)
Date: Thu Apr 22 11:36:13 CEST 2004
Method: netinst cdrom

Machine: HP Proliant ML350 G3 (same as in #241237)
Processor: P4 Xeon 2.8 GHz
Memory: 2.5 GB
Root Device: /dev/cciss/c0d0p4
Root Size/partition table:  
Disk /dev/cciss/c0d0: 145.6 GB, 145667358720 bytes
255 heads, 32 sectors/track, 34866 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

Device Boot  Start End  Blocks   Id  System
/dev/cciss/c0d0p1   1   8   32624   83  Linux   
 # not used (working woody system)
/dev/cciss/c0d0p2   91205 4883760   82  Linux swap  
 # not used (working woody system)
/dev/cciss/c0d0p31206539817107440f  W95 Ext'd (LBA) 
 
/dev/cciss/c0d0p4   *5399   34866   120229440   83  Linux   
 # /
/dev/cciss/c0d0p512062402 4883744   83  Linux   
 # not used (working woody system)
/dev/cciss/c0d0p624032881 1954304   83  Linux   
 # not used (working woody system)
/dev/cciss/c0d0p728825275 9767504   83  Linux   
 # not used (working woody system)
/dev/cciss/c0d0p852765398  501824   82  Linux swap  
 # swap

Output of lspci and lspci -n:
debian:~# lspci -n
pcilib: Cannot open /sys/bus/pci/devices
:00:00.0 Class 0600: 1166:0014 (rev 32)
:00:00.1 Class 0600: 1166:0014
:00:00.2 Class 0600: 1166:0014
:00:02.0 Class 0100: 9005:00c0 (rev 01)
:00:02.1 Class 0100: 9005:00c0 (rev 01)
:00:03.0 Class 0300: 1002:4752 (rev 27)
:00:04.0 Class 0200: 14e4:16a6 (rev 02)
:00:05.0 Class 0880: 0e11:a0f0
:00:0f.0 Class 0601: 1166:0201 (rev 93)
:00:0f.1 Class 0101: 1166:0212 (rev 93)
:00:0f.2 Class 0c03: 1166:0220 (rev 05)
:00:0f.3 Class 0600: 1166:0225
:00:11.0 Class 0600: 1166:0101 (rev 05)
:00:11.2 Class 0600: 1166:0101 (rev 05)
:02:02.0 Class 0104: 0e11:0046 (rev 01)
:05:02.0 Class 0604: 8086:b154
:06:04.0 Class 0200: 8086:1229 (rev 08)
:06:05.0 Class 0200: 8086:1229 (rev 08)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [O]

Comments/Problems:
Grub installation failed. 
>From messages:
Selecting previously deselected package grub.
(Reading database ... 9141 files and directories currently installed.)
Unpacking grub (from .../grub_0.93+cvs20031021-8_i386.deb) ...
Setting up grub (0.93+cvs20031021-8) ...
Probing devices to guess BIOS drives. This may take a long time.
/dev/cciss/c0d0p4 does not have any corresponding BIOS drive.

>From syslog:
Jul 25 19:38:55 (none) user.notice grub-installer: info: Installing grub on 
'(hd0)'
Jul 25 19:38:55 (none) user.notice grub-installer: info: grub-install support 
--no-floppy
Jul 25 19:38:55 (none) user.notice grub-installer: info: Running chroot /target 
/sbin/grub-install --no-floppy "(hd0)"
Jul 25 19:38:55 (none) user.notice grub-installer: error: Running 'grub-install 
--no-floppy "(hd0)"' failed.
Jul 25 19:38:57 (none) user.warn main-menu[279]: WARNING **: Configuring 
'grub-installer' failed with error code 1
Jul 25 19:38:57 (none) user.warn main-menu[279]: WARNING **: Menu item 
'grub-installer' failed.

I also tried a lilo install, but this failed, I guess because lilo was not 
installed.

Reboot using the kernel from an already installed woody system worked fine, and 
base-config gave no problems. The woody install causes the weird partition 
layout I used, which probably caused the grub failure.

I chose LANG_INST="en_US" and LANGUAGE_INST="en", which made the timezone 
chooser default to US timezones, which was not what I wanted. Lang

Bug#248820: marked as done (various grub-installer comments (install report))

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

I am writing this from memory at work, so not all the fields are filled.

Debian-installer-version: Beta 4 downloaded von Debian
uname -a: 
Date: May 12th, 2004
Method: Installed by booting from CD

Machine: ISSAM Smartbook (German laptop)
Processor:Pentium 4, 2.5 Mhz
Memory: 512 Mb
Root Device: 
Root Size/partition table:
hda1 - Xandros
hda2 - Debian Testing (this is where I installed Debian
hda3 - Linspire 4.5 Laptop Edition
hda5 - swap
hda6 - free
hda7 - home
Output of lspci:

Base System Installation Checklist:

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

Comments/Problems:

Installing boot loader:
You get a question if you want to install grub in mbr (yes,no). There is no
indication what will happen if you answer no. There should at least be a
note saying that if you answer no, you'll have a chance to install it
somewhere else on the next screen.

On the next screen you say that you can use grub notation hd0 or standard
/dev notation to install grub somewhere else. I wrote "/dev/hda2" (without
quotes of course). Installer tried to install grub but returned an error. I
then returned to previous screen to install grub in mbr and it worked. Here
I have a few comments:
1. Installing boot loader in some other partition has grub notation "hd0,x"
for partitions where x is partition number starting from 0, not "hd0" as
you say in the text. Am I correct?
2. Also, you only say "standard /dev notation". You should give a complete
example. I tried with "/dev/hda2" but it didn't work.
3. If you can't install grub on other partitions like lilo but you can
install it on other disks giving only the disk notation (hd1 or /dev/hdb),
it isn't clearly stated on these screens.

But I would really prefer having these two screens (mbr and other) merged
into one screen, where you can choose where to install grub. And you give a
complete example of every possible option (mbr, other disk, other
partition? ). That would be so much simpler.

Internet connection:
The installer is made for boxes connected to a network. There is no option
or help for typical home users having DSL-connection. At the end it asks
for a debian repository to start to download packages. Here is where the
installation stops, because there is no DSL support in the installer and so
no connection to the internet. It would be great if you have a option for
DSL. Just ask for a user name and password and instructions how to start
and stop the connection (I pay pro minute so I want to be able to start and
stop it at will and also to see when the connection is up).

Keyboard:
Kudos for you for separating language and keyboard layout. I live in
Germany with a German keyboard but prefer my computer to talk to me in
English. But when choosing the keyboard layout, it would be great if you
could have an extra input field for testing it after choosing to see if you
made the right choice.

That's it for now.
Regards

Tony Akkanen




--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#244975: marked as done (grub-installer fails with simple partition layout)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---

Package: installation-reports

Debian-installer-version: 2004-04-19 
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta3/sarge-i386-businesscard.iso


uname -a: i wish i could
Date: 2004-04-19
Method: netinstall from "debian.tu-bs.de" i think...

Machine: AMD K6-2, K6BV3+/66 Rev B1

Processor: AMD K6-2 450 MHz
Memory: 512MB
Root Device: IDE (primary master) ST310211A
Root Size/partition table:

 ---Starting---  EndingStart Number of
 # Flags Head Sect Cyl   ID  Head Sect Cyl SectorSectors
-- -        --- ---
 1  0x80110 0x83   15   63 1023  63 5468337
 2  0x00   15   63 1023 0x83   15   63 1023 5468400  976752
 3  0x00   15   63 1023 0x83   15   63 1023 644515213095936
 4  0x00000 0x00000   0   0

hda1/
hda2swap
hda3/home

Output of lspci:

00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo 
MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] 
(rev 12)
00:07.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management 
(rev 20)

00:12.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 23)
00:14.0 Ethernet controller: Digital Equipment Corporation DECchip 
21142/43 (rev 41)


Base System Installation Checklist:

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

Comments/Problems:

the installation of the GRUB bootloader with (hd0,0) failed with error 
message, but let me reboot the system anyway... on another occasion i 
tried to install LILO, after GRUB failed, but i did not get any 
feedback, if the operation was successful...


i tried several different settings for the GRUB settings... (hd0) which 
was the default, but didn't work either.


my first guess was "cable select" on the HD was not working as supposed, 
but BIOS recognized the drive right, nevermind where i put it... also 
exchanged cables and finaly jumperd the drive as master...


/boot/grub/device.map

(fd0)   /dev/fd0
(hd0)   /dev/hda

/boot/grub/menu.lst

title   Debian GNU/Linux, kernel 2.4.25-1-386
root(hd0,0)
kernel  /boot/vmlinuz-2.4.25-1-386 root=/dev/hda1 ro
initrd  /boot/initrd.img-2.4.25-1-386
savedefault
boot

title   Debian GNU/Linux, kernel 2.4.25-1-386 (recovery mode)
root(hd0,0)
kernel  /boot/vmlinuz-2.4.25-1-386 root=/dev/hda1 ro single
initrd  /boot/initrd.img-2.4.25-1-386
savedefault
boot


any suggestions at what may have gone wrong are more than wellcome...
thanks...


|

  Dipl. - Des.  Falko Oldenburg
  Entwicklung & Support

  Programmfabrik GmbH
  Frankfurter Allee 73D
  D - 10724 Berlin

  Tel.:  +49 (0)30 - 42081604
  Fax:   +49 (0)30 - 42081606
  Email: [EMAIL PROTECTED]

  www.programmfabrik.de
  www.easydb.de

--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#293717: marked as done (grub-install hangs)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 21:03:27 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Solve in current images
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: debian-installer
Version: RC2 (from downloaded Sarge net install on 23.Nov.2004)

grub-install hangs during install.  this is a normal install with / 
= /dev/hda2grub should install to MBR on /dev/hda   filesystem is XFS
in the installer the indicator freezes at the 50% point.   in the syslog it 
shows the last command executed as .../sbin/grub-install  with a few options
i had to install lilo to get debian to install


--- End Message ---
--- Begin Message ---
Hello,

This is a know bug in grub and to workaround it at moment, current d-i
images select LILO in case of /boot to be in XFS fs.

Since we already have some reported bug about int in grub, i'm closing
this one.

Thanks,

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#301960: marked as done (grub installation fails with HP Smart Array 6i (cciss) using rc3 2.6 installer)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: rc3 for i386 from cdimage.debian.org
uname -a: Linux testi 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 unknown
Date: Tue 29 Mar 2005 12:30
Method: Booted from rc3/i386 CD, and ran "linux26" installer.

Machine: HP Proliant DL380 G4 server
Processor: Intel Xeon 3,2 GHz 1MB
Memory: 2 GB ECC 
Root Device: HP Smart Array 6i / cciss partition 2 (/dev/cciss/c0d0p2)
Root Size/partition table: 

Disk /dev/cciss/c0d0: 35139 cylinders, 255 heads, 32 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start End   #cyls#blocks   Id  System
/dev/cciss/c0d0p1   *  0+ 31  32-257008+  83  Linux
/dev/cciss/c0d0p2 32 517 4863903795   83  Linux
/dev/cciss/c0d0p3518 760 2431951897+  83  Linux
/dev/cciss/c0d0p4761 882 122 9799655  Extended
/dev/cciss/c0d0p5761+882 122-979933+  82  Linux swap

Output of lspci and lspci -n:

:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 0c)
:00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 
(rev 0c)
:00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 
(rev 0c)
:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 
(rev 02)
:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 
(rev 02)
:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 
(rev 02)
:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 
(rev 02)
:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI 
Controller (rev 02)
:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 
02):00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 
100 Storage Controller (rev 02)
:01:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
:01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights 
Out Controller (rev 01)
:01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights 
Out  Processor (rev 01)
:02:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09)
:02:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09)
:03:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
Gigabit Ethernet (rev 10)
:03:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
Gigabit Ethernet (rev 10)
:04:03.0 RAID bus controller: Compaq Computer Corporation Smart Array 64xx 
(rev 01)
:05:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09)
:05:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09)

:00:00.0 0600: 8086:3590 (rev 0c)
:00:02.0 0604: 8086:3595 (rev 0c)
:00:06.0 0604: 8086:3599 (rev 0c)
:00:1d.0 0c03: 8086:24d2 (rev 02)
:00:1d.1 0c03: 8086:24d4 (rev 02)
:00:1d.2 0c03: 8086:24d7 (rev 02)
:00:1d.3 0c03: 8086:24de (rev 02)
:00:1d.7 0c03: 8086:24dd (rev 02)
:00:1e.0 0604: 8086:244e (rev c2)
:00:1f.0 0601: 8086:24d0 (rev 02)
:00:1f.1 0101: 8086:24db (rev 02)
:01:03.0 0300: 1002:4752 (rev 27)
:01:04.0 0880: 0e11:b203 (rev 01)
:01:04.2 0880: 0e11:b204 (rev 01)
:02:00.0 0604: 8086:0329 (rev 09)
:02:00.2 0604: 8086:032a (rev 09)
:03:01.0 0200: 14e4:1648 (rev 10)
:03:01.1 0200: 14e4:1648 (rev 10)
:04:03.0 0104: 0e11:0046 (rev 01)
:05:00.0 0604: 8086:0329 (rev 09)
:05:00.2 0604: 8086:032a (rev 09)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [O]

Comments/Problems:

Grub installation fails. The error from third console (alt+f3) is:
"file /boot/grub/stage1 not read correctly"

When installing with 2.4 kernel (the default) grub installs OK and works OK.


--- End Message ---
--- Begin Message ---
Hello,

Loo

Bug#238911: marked as done (grub-installer does not activate MBR, where grub got installed)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 2004/03/14, download ftp.debian.org
uname -a: Linux linus 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686
GNU/Linux
Date: 2004/03/19, 16:40
Method: CDROM netinst 100MB (beta 3 of Debian-installer)
Machine: NoName PC
Processor: AMD Duron 900 MHz
Memory: 512 MB
Root Device: /dev/hda12
Root Size/partition table: 3GB
% fdisk -l /dev/hda
Disk /dev/hda: 40.0 GB, 4003776 bytes
255 heads, 63 sectors/track, 4867 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/hda1   1 128 1028128+   6  FAT16
/dev/hda2   * 129190014233590f  W95 Ext'd (LBA)
/dev/hda5 129 192  514048+  82  Linux swap
/dev/hda6 193 256  514048+  83  Linux
/dev/hda7 257 517 2096451   83  Linux
/dev/hda8 518 648 1052226   83  Linux
/dev/hda9 649 909 2096451b  W95 FAT32
/dev/hda109101170 2096451b  W95 FAT32
/dev/hda11   11711535 2931831   83  Linux
/dev/hda12   15361900 2931831   83  Linux

% mount
/dev/hda12 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
/dev/hda1 on /dosc type vfat (rw)
/dev/hda9 on /dosd type vfat (rw)
/dev/hda10 on /dose type vfat (rw)
/dev/hda11 on /pam type ext2 (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)

Output of lspci:

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [E]

Comments/Problems:

Reboot used still active old MBR in hda1, not hda2 as seleted in
GRUB configuration dialog: hda0,1. After enabling hda2 as active,
Debian base config came up fine.

Wish: Chain loading old MBR in hda1 would have been nice.

German translation is almost perfect. Good job!



--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#259899: marked as done (uses hd2,0 instead of hd0,0)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---








Package: installation-reports

 

Debian-installer-version: 07082004

uname -a: Linux Grundle 2.6.6-1-386 #1 Wed May 12 13:19:06 EST 2004
i686 GNU/Linux

Date: 7-08-2004 22:00:00

Method: Network install from the download disk (link: http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/sarge-i386-netinst.iso.
I did a net install. No proxies. I booted from a cdrom drive (hda), from
ftp-mirror.internap.org.

 

 

Machine: Whitebox supermicro DBU
 MB onboard scsi disabled (flaky),
offboard 29160, onboard ide for cdrom only, 2 offboard Silicon image ide raid
cards.

Processor: 2x pIII slot 1 550mhz

Memory: 886

Root Device: scsi /dev/sda (scsi0:A:0): 160.000MB/s transfers
(80.000MHz DT, offset 127, 16bit)

Vendor: FUJITSU  
Model: MAJ3091MP Rev: 0114

      Type:  
Direct-Access 
ANSI SCSI revision: 04

scsi0:A:0:0: Tagged Queuing
enabled.  Depth 8

 

Root Size/partition table: Disk /dev/sda: 9137 MB, 9137912832 bytes

255 heads, 63 sectors/track, 1110 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

   Device Boot 
Start
End  Blocks   Id  System

/dev/sda1  
*  
1 
30  240943+  83  Linux ß \boot

/dev/sda2 
31 212
1461915   83  Linux ß swap

/dev/sda3
213    1110
7213185   83  Linux ß \

 

Output of lspci:

:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX -
82443BX/ZX/DX Host bridge (rev 03)

:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX -
82443BX/ZX/DX AGP bridge (rev 03)

:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB
PIIX4 ISA (rev 02)

:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB
PIIX4 IDE (rev 01)

:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB
PIIX4 USB (rev 01)

:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4
ACPI (rev 02)

:00:0e.0 SCSI storage controller: Adaptec
AHA-2940U2/U2W / 7890/7891

:00:0f.0 Ethernet controller: 3Com Corporation
3CR990-TX-95 [Typhoon 56-bit] (rev 02)

:00:10.0 SCSI storage controller: Adaptec
AIC-7892A U160/m (rev 02)

:00:12.0 RAID bus controller: Silicon Image, Inc.
(formerly CMD Technology Inc) PCI0680 Ultra ATA-133 Host Controller (rev 02)

:00:14.0 IDE interface: Silicon Image, Inc.
(formerly CMD Technology Inc) PCI0680 Ultra ATA-133 Host Controller (rev 01)

:01:00.0 VGA compatible controller: nVidia
Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 11)

Base System Installation Checklist:

 

Initial boot worked:    [o ]

Configure network HW:   [o ]

Config network: [o ]

Detect
CD: 
[o ]

Load installer modules: [o ]

Detect hard drives: [o ]

Partition hard drives:  [o ]

Create file systems:    [o ]

Mount partitions:   [o ]

Install base system:    [o ]

Install boot loader:    [e ]

Reboot:
[o ]

[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

 

Comments/Problems:

 

The install went relatively smoothly, except grub seems to want to boot
from hd2,0 instead of hd0,0 don’t know why I didn’t put 2,0 in
anywhere but it seems to want to boot from there. The other issue is that I want
to install my root on a sw raid5 md device, 3 scsi drives, but the installer
didn’t allow me to choose raid5 only 0,1. The last problem I have is that
I have my disks w/ persistent superblocks from another dist I had installed
(suse9.0) and for some reason this kernel is not auto-mounting them. I’m
playing w/ mdadm to get them all mounted up right now. Scary though because I have
data on one of the drive sets (170gb of data J). Other than
that it was pretty smooth and worked out well. Keep up the great work! 

 

 

 






--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#255978: marked as done (grub fails: does not have any corresponding BIOS drive)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: Beta 4 110mb image from 
http://www.debian.org/devel/debian-installer/
uname -a: 
Date: 2004-06-24 1:48 pm
Method: Boot off CD, network install from mirror.optusnet.com.au, not proxied
boot "linux26" kernel initially, then switched back to default after
display problems

Machine: Compaq Proliant DL380 G3
Processor: Dual 2.8gb Xeon
Memory: 4.5gb
Root Device: 2x72g SCSI, hardware RAID 1 (HP CISS card)
Root Size/partition table:
Disk /dev/cciss/c0d0: 72.8 GB, 72833679360 bytes
255 heads, 32 sectors/track, 17433 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/cciss/c0d0p1   *   11675 6833984   83  Linux
/dev/cciss/c0d0p21676   1743364292640f  W95 Ext'd (LBA)
/dev/cciss/c0d0p51676   1731063790784   83  Linux
/dev/cciss/c0d0p6   17311   17433  501824   82  Linux swap

Output of lspci:
:00:00.0 Host bridge: ServerWorks CMIC-LE (rev 13)
:00:00.1 Host bridge: ServerWorks CMIC-LE
:00:00.2 Host bridge: ServerWorks: Unknown device 
:00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
:00:04.0 System peripheral: Compaq Computer Corporation: Unknown device 
b203 (rev 01)
:00:04.2 System peripheral: Compaq Computer Corporation: Unknown device 
b204 (rev 01)
:00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
:00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05)
:00:0f.3 Host bridge: ServerWorks CSB5 LPC bridge
:00:10.0 Host bridge: ServerWorks CIOB-X2 (rev 05)
:00:10.2 Host bridge: ServerWorks CIOB-X2 (rev 05)
:00:11.0 Host bridge: ServerWorks CIOB-X2 (rev 05)
:00:11.2 Host bridge: ServerWorks CIOB-X2 (rev 05)
:01:03.0 RAID bus controller: Compaq Computer Corporation Smart Array 
5i/532 (rev 01)
:02:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X 
Gigabit Ethernet (rev 02)
:02:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X 
Gigabit Ethernet (rev 02)
:06:1e.0 PCI Hot-plug controller: Compaq Computer Corporation PCI Hotplug 
Controller (rev 14)

Base System Installation Checklist:

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

Comments/Problems:

* Didn't detect ethernet card (should be tg3)
* Can't switch from VT2-5 back to VT1 (get screenful of red vertical lines)
After these first two problems I rebooted to use standard boot image,
instead of linux26.

This time both tg3 interfaces were detected, and switching between VTs
worked fine.

DHCP was fine

I chose to do a automatic partition (separate partitions for home dirs),
and then made all partitions reiserfs instead of ext3.

GRUB installer died with:
Executing 'grub-install (hd0)' failed.
This is a fatal error.

VT3 shows:
Probing devices to guess BIOS drives. This may take a long time.
/dev/cciss/c0d0p1 does not have any corresponding BIOS drive.

/dev/cciss/c0d0p1 is the name of my root partition.

I manually chose to install LILO on /dev/cciss/c0d0 and it worked fine.

On boot there were a pile of errors just after the Partition check:

VFS: Can't find ext3 filesystem on dev cciss0(104,1).
mount: wrong fs type, bad option, bad superblock on /dev2/root2,
or too many mounted file systems

However the boot was fine.


Defaulting to showing US timezones on base system config annoyed me, as I'm
in Australia. But it didn't cause a problem.

Base config went well. Including aptitude was a nice touch.

After running for a bit, I realised that the base install kernel doesn't
include SMP!  I don't remember seeing an option to use it.



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you c

Bug#248637: marked as done (Can not boot when /boot is not in the first 1024 cylinders and the BIOS is old. grub-installer detects no errors. Notice that LILO can boot this machine so if grub-install

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 21:01:36 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Still reproducable?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT
Summary: Grub Error 18 on first reboot

Debian-installer-version: Beta 4
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-
i386-netinst.iso


uname -a:
Linux debian 2.4.25-1-386 #2 Wed Apr 14 19:38:08 EST 2004 i686 GNU/Linux


Date: 5th May 2004
Method: Booted off CD, standalone machine

Machine:
Processor: Pentium III, 450 Mhz
Memory: 512Mb
Root Device: IDE, 10Gb Fujitsu MPF3102AT  (LBA)

Root Size/partition table:
>From the second successful install (NOTE: /boot partition)
# /etc/fstab: static file system information.
#
#
proc/proc   procdefaults0   0
/dev/hda3   noneswapsw  0   0
/dev/hda1   /boot   ext3defaults0   2
/dev/hda2   /   ext3defaults,errors=remount-ro 0 1
/dev/hdd/media/cdromiso9660 ro,user,noauto  0   0
/dev/fd0/media/floppy   autorw,user,noauto  0   0
/dev/hdd/cdrom  iso9660 ro,user,noauto  0   0

Output of lspci and lspci -n:
lspci:
:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host
bridge (rev 02)
:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP
bridge (rev 02)
:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
:00:0d.0 Multimedia audio controller: ESS Technology ES1969 Solo-1
Audiodrive
:00:11.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC
AGP (rev 7a)

lspci -n:
:00:00.0 Class 0600: 8086:7190 (rev 02)
:00:01.0 Class 0604: 8086:7191 (rev 02)
:00:07.0 Class 0601: 8086:7110 (rev 02)
:00:07.1 Class 0101: 8086:7111 (rev 01)
:00:07.2 Class 0c03: 8086:7112 (rev 01)
:00:07.3 Class 0680: 8086:7113 (rev 02)
:00:0d.0 Class 0401: 125d:1969
:00:11.0 Class 0200: 8086:1229 (rev 08)
:01:00.0 Class 0300: 1002:475a (rev 7a)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[ O]
Configure network HW:   [O ]
Config network: [ O]
Detect CD:  [ O]
Load installer modules: [O ]
Detect hard drives: [ O]
Partition hard drives:  [ O]
Create file systems:[ O]
Mount partitions:   [ O]
Install base system:[O ]
Install boot loader:[ O]
Reboot: [ E]

Comments/Problems:

Did the most basic install.

On the partition screen selected “Erase entire disk” then “All files on
one partition”

On the first reboot after installing GRUB, the machine hung with a “GRUB
Error 18” message which indicates that “Selected cylinder exceeds maximum
supported by BIOS“, presumably because I am using a disk >8Gb with an old
BIOS

I do not have this problem using LILO.
A workaround is to create a /boot partition at the beginning of the disk
(see above partition table)

I believe that the “Erase entire disk” option in partition management
should either create a default /boot partition or at least warn you that
you may need to create one if you are using a large disk with an old BIOS.


Other than that the installer was easy to use.

Cheers,
Gary Hullock
--
"...Still, it's the heaviest of all these volumes, and thus, in
hardback at least, could undoubtedly be used to stun a burglar;
which has always been my definition of real art."
The Kindly Ones - Neil Gaiman

--- End Message ---
--- Begin Message ---
Hello,

I wish  to know if you can still reducable the bug and provide as much
information as possible to us be able to close it.

Thanks, 

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#260852: marked as done (grub fails: does not have any corresponding BIOS drive)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: 

uname -a: 
Date: <07/22/2004>
Method: 

Machine: 
Processor: xeon
Memory: 1G
Root Device: 

Root Size/partition table: <
0.3 G on /
6G on /usr
6G on /var
0.3G on /tmp
14G on /home
8G on /someuser
0.5G swap>

Output of lspci:
:00:00.0 Host bridge: ServerWorks CNB20-HE Host Bridge (rev 32)
:00:00.1 Host bridge: ServerWorks CNB20-HE Host Bridge
:00:00.2 Host bridge: ServerWorks CNB20-HE Host Bridge
:00:02.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 
01)
:00:02.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 
01)
:00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
:00:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X 
Gigabit Ethernet (rev 02)
:00:05.0 System peripheral: Compaq Computer Corporation Advanced System 
Management Controller
:00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
:00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05)
:00:0f.3 Host bridge: ServerWorks CSB5 LPC bridge
:00:11.0 Host bridge: ServerWorks CIOB-X2 (rev 05)
:00:11.2 Host bridge: ServerWorks CIOB-X2 (rev 05)
:02:02.0 RAID bus controller: Compaq Computer Corporation Smart Array 64xx 
(rev 01)

Base System Installation Checklist:

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

Comments/Problems:


Claire Boussard.

--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#261535: marked as done (Running 'grub-install --no-floppy "(hd0)"' failed)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: 20040316
uname -a: Linux (none) 2.4.25-1-386 #1 The Feb 24 08:11:13 est 2004 i686
unknown
Date: 19032004
Method: netinstall CDROM

Machine: DL380G3
Processor: 2.8 Ghz
Memory: 2,5 Go RAM
Root Device: IDE CDROM
Root Size/partition table: 
tmpfs  /
/dev/cdroms/cdrom0 /cdrom
/dev/cciss/disc0/part1 /target

Output of lspci:

compaq smartarray 5i
serverworks
broadcom NetXtrem


Base System Installation Checklist:

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

Comments/Problems:

the base system crash when it tries to install kernel :
kernel-image-2.4.25-1-386
press virtual consol 3

The module list has been changed and modules.dep need to be rebuild.
it says : I have to reboot in order for the modules file to be created
correctly. 

I tryed to finish the installation, but there is no grub or lilo, so the
server doesn t boot.

--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#255003: marked as done (Package: installation-reports)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: Beta4 (06/18/04)
uname -a:
Date: 06/18/04 10:54
Method: Boot CD-Rom (110 Mo)

Machine: Medion (Laptop)
Processor: 2.6Ghz Celeron
Memory: 512 Mo
Root Device: IDE
Root Size/partition table: 5000 Mo
Output of lspci: (lots of things but not important for
the problem)

Base System Installation Checklist:

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

Comments/Problems: Hard Disk Boot Sector Invalid

It's very good for all ! Very good job !






Créez gratuitement votre Yahoo! Mail avec 100 Mo de stockage !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/

Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! 
Messenger sur http://fr.messenger.yahoo.com

--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#285890: marked as done ('IR: Dell Precision 370')

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 
Debian GNU/Linux testing "Sarge" - Official Snapshot i386 Binary-1 (20041213)
uname -a: Linux cl2 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux
Date: Thu Dec 16 10:12:00 CET 2004
Method: netinst iso, standard install, mirror: gd.tuwien.ac.at

Machine: Dell Precision 370
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz
Memory: 1GB
Root Device: /dev/md0
cl2:~# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda2[0] sdb1[1]
  3903680 blocks [2/2] [UU]

Root Size/partition table:  
cl2:~# fdisk -ul

Disk /dev/sda: 160.0 GB, 1600 bytes
255 heads, 63 sectors/track, 19452 cylinders, total 31250 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *  63  112454   561966  FAT16
/dev/sda2  112455 7920044 3903795   fd  Linux raid autodetect

Disk /dev/sdb: 160.0 GB, 1600 bytes
255 heads, 63 sectors/track, 19452 cylinders, total 31250 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1  63 7807589 3903763+  fd  Linux raid autodetect

cl2:~# df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/md0  3.7G  449M  3.1G  13% /


Output of lspci and lspci -n:

:00:00.0 Host bridge: Intel Corp. 925X Memory Controller Hub (rev 04)
:00:01.0 PCI bridge: Intel Corp. 925X PCI Express Root Port (rev 04)
:00:1c.0 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 1 (rev 03)
:00:1c.1 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 2 (rev 03)
:00:1d.0 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #1 (rev 03)
:00:1d.1 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #2 (rev 03)
:00:1d.2 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #3 (rev 03)
:00:1d.3 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03)
:00:1d.7 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller (rev 03)
:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev d3)
:00:1e.2 Multimedia audio controller: Intel Corp. 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) AC'97 Audio Controller (rev 03)
:00:1f.0 ISA bridge: Intel Corp. 82801FB/FR (ICH6/ICH6R) LPC Interface 
Bridge (rev 03)
:00:1f.1 IDE interface: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE 
Controller (rev 03)
:00:1f.2 IDE interface: Intel Corp. 82801FR/FRW (ICH6R/ICH6RW) SATA 
Controller (rev 03)
:00:1f.3 SMBus: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 03)
:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 00fd 
(rev a2)
:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 
Gigabit Ethernet PCI Express (rev 01)
:00:00.0 0600: 8086:2584 (rev 04)
:00:01.0 0604: 8086:2585 (rev 04)
:00:1c.0 0604: 8086:2660 (rev 03)
:00:1c.1 0604: 8086:2662 (rev 03)
:00:1d.0 0c03: 8086:2658 (rev 03)
:00:1d.1 0c03: 8086:2659 (rev 03)
:00:1d.2 0c03: 8086:265a (rev 03)
:00:1d.3 0c03: 8086:265b (rev 03)
:00:1d.7 0c03: 8086:265c (rev 03)
:00:1e.0 0604: 8086:244e (rev d3)
:00:1e.2 0401: 8086:266e (rev 03)
:00:1f.0 0601: 8086:2640 (rev 03)
:00:1f.1 0101: 8086:266f (rev 03)
:00:1f.2 0101: 8086:2652 (rev 03)
:00:1f.3 0c05: 8086:266a (rev 03)
:01:00.0 0300: 10de:00fd (rev a2)
:02:00.0 0200: 14e4:1677 (rev 01)

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [E]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [E]

Comments/Problems:

CD Detection: d-i failed to detect the cdrom. Workaround: Switch the
BIOS from RAID/AHCI to RAID/ATA. After this it was detected
automatically.

Reboot: This machine has a 57MB system

Bug#267432: marked as done (Should not select "Other operating systems" as default)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---

Package: debian-installer
Version: Release Candidate 1

When you have other non-Unix OSes on the disk and the debian-installer 
install them in /boot/grub/menu.lst, the entry "other operating 
systems", which acts as a title to them, is selected as default; but 
this does not work. The OS should be selected instead.


--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#259297: marked as done (installation-report: Adaptec 2120S w/RAID5... installer fails to install grub)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 21:01:36 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Still reproducable?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version: 2004-07-13  Image from:
http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/i386/current/sarge-i38
6-netinst.iso
uname -a: Linux geocentric 2.6.7-1-386 #1 Thu Jun 24 12:42:08 EDT 2004 i686
unknown
Date: 2004-07-13, 12:00pm CST
Method: I used the current sarge-i386-netinst.iso from the above location.
I used the "standard" install method using the Linux 2.6 Kernel.  This was a
machine that was behind a firewall on my company LAN with non-proxied access
to the internet.

Machine: IBM IntelliStation Z Pro 6221-1PU

Processor: Dual Intel Xeon 2.4 Ghz

Memory: 1.5 GB

Root Device: Root device was a Hardware RAID Array (Level 5), Adaptec 2120S
w/ 3x Seagate 73.4GB U320SCSI 68PIN 10K SEA-ST373307LW

Root Size/partition table: ...
File System: ext3
Mount point: /
Bootable flag: on
Size 146.7 GB

Output of lspci:
Couldn't find the location of the command via a boot menu in the
installer... :(

Base System Installation Checklist:

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

Comments/Problems:

I was pleased to see my Broadcom NetXtreme 10/100/1000 integrated Ethernet
card was detected properly by the installer now.  Looks like the tg3 driver
issues were sorted out now?

The only problem I had was GRUB not installing properly to my RAID array.
As mentioned above, I have a Adaptec 2120S RAID Controller hooked up to 3x
Seagate 73.4 GB U320SCSI 68PIN 10K SEA-ST373307LW drives.  The drives are
configured into a single RAID5 Volume and detected by the installer as such.
However, grub fails to load with a "Fatal Error"
t

--- End Message ---
--- Begin Message ---
Hello,

I wish  to know if you can still reducable the bug and provide as much
information as possible to us be able to close it.

Thanks, 

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#258216: marked as done (cannot handle traditional device names)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Debian-installer-version:   05 July 2004
uname -a:   
Date:   07 July 2004
Method: -Boot from floppy
-Install base from local proxy
(apt-proxy)
Machine:Generic
Processor:  486DX4/100
Memory: 64MB
Root Device:IDE, /dev/hda
Root Size/partition table:  1GB
Output of lspci:No PCI on this machine

Base System Installation Checklist:

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

Comments/Problems:

One of the last installation screens is to determine where you would
like to install grub.  Choices are MBR or elsewhere.  If you don't
choose MBR then elsewhere is suggested as grub notation (hd0) or
/dev/hda.

This is a problem.  Users unfamiliar with grub won't necessarily know
that the first partion on the first hard drive is hd(0,1).  It could be
hd(0,0) for instance, or even hd(1,1), both of which seem logical and
might be guessed...there appears to be no other help.

As for the suggestion of using /dev/hda... this won't work because none
of the old style drive paths are supported at this stage, so, no
/dev/hda, /dev/sda, /dev/hda1 etc etc.  Drives are specified using 'new'
drive paths of /dev/ide/bus...blah/blah/blah which leaves the
instructions incorrect and the newby wondering whats going on.

Regards,
Craig




--
This email is confidential and intended solely for the use of the individual to 
whom it is addressed.  
Any views or opinions presented are solely those of the author and do not 
necessarily represent those of NAUTRONIX LTD.

If you are not the intended recipient, you have received this email in error 
and use, dissemination, forwarding, printing, or copying of 
this email is strictly prohibited.  If you have received this email in error 
please contact the sender.   

Although our computer systems use active virus protection software, and we take 
various measures to reduce the risk of viruses 
being transmitted in e-mail messages and attachments sent from this company, we 
cannot guarantee that such e-mail messages 
and attachments are free from viruses on receipt.  It is a condition of our 
using e-mail to correspond with you, that any and all liability 
on our part arising directly or indirectly out of any virus is excluded.  
Please ensure that you run virus checking software on all e-mail 
messages and attachments before reading them.


--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#258010: marked as done (install failure to cciss)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT

Debian-installer-version: sid-amd64-netinst.iso from bach.hpc2n.umu.se at 
20040706
uname -a: Linux m192-h 2.6.7-3-k8-smp #1 SMP Wed Jun 30 23:41:26 UTC 2004 
x86_64 GNU/Linux
Date: 20040706
Method: Bootded netinst from cdrom

Machine: HP DL585
Processor: 2 x Opteron 248
Memory: 8 GB
Root Device: cciss (Compaq Computer Corporation Smart Array 5i/532)
Root Size/partition table:
 104 0  143367120 cciss/c0d0
 104 1 146864 cciss/c0d0p1 [/]
 104 2  1 cciss/c0d0p2
 104 54883744 cciss/c0d0p5 [/usr]
 104 62929424 cciss/c0d0p6 [/var]
 104 7 391664 cciss/c0d0p7 [/tmp]
 104 8  134517584 cciss/c0d0p8 [lvm2 pv, created after installation]
 104 9 497744 cciss/c0d0p9


Output of lspci and lspci -n:
:00:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07)
:00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05)
:00:04.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03)
:00:04.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05)
:00:07.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:00:07.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01)
:00:08.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:00:08.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01)
:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
:01:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b)
:01:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b)
:01:02.0 System peripheral: Compaq Computer Corporation: Unknown device 
b203 (rev 01)
:01:02.2 System peripheral: Compaq Computer Corporation: Unknown device 
b204 (rev 01)
:01:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
:02:04.0 RAID bus controller: Compaq Computer Corporation Smart Array 
5i/532 (rev 01)
:02:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
Gigabit Ethernet (rev 10)
:02:06.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
Gigabit Ethernet (rev 10)
:04:09.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:04:09.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01)
:04:0a.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:04:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01)
:04:0b.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:04:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01)
:04:0c.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:04:0c.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01)
:05:0d.0 Network controller: MYRICOM Inc. Myrinet 2000 Scalable Cluster 
Interconnect (rev 04)
:06:0e.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet 
Controller (Copper) (rev 01)
:06:0e.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet 
Controller (Copper) (rev 01)

:00:03.0 Class 0604: 1022:7460 (rev 07)
:00:04.0 Class 0601: 1022:7468 (rev 05)
:00:04.1 Class 0101: 1022:7469 (rev 03)
:00:04.3 Class 0680: 1022:746b (rev 05)
:00:07.0 Class 0604: 1022:7450 (rev 12)
:00:07.1 Class 0800: 1022:7451 (rev 01)
:00:08.0 Class 0604: 1022:7450 (rev 12)
:00:08.1 Class 0800: 1022:7451 (rev 01)
:00:18.0 Class 0600: 1022:1100
:00:18.1 Class 0600: 1022:1101
:00:18.2 Class 0600: 1022:1102
:00:18.3 Class 0600: 1022:1103
:00:19.0 Class 0600: 1022:1100
:00:19.1 Class 0600: 1022:1101
:00:19.2 Class 0600: 1022:1102
:00:19.3 Class 0600: 1022:1103
:01:00.0 Class 0c03: 1022:7464 (

Bug#253864: marked as done (debian-installer grub install crash)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: debian-installer
Version: test1

  When trying to install grub, receive a fatal error.

Here is the log :

Setting up grub (0.94+cvx20040511-1)...
Probing devices to guess BIOS ...
The file /boot/grub/stage1 not read correctly




signature.asc
Description: Ceci est une partie de message	numériquement signée.
--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#315923: marked as done (Kernel panic after Sarge installation on Dell with SATA drive)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: install
Version: debian-31r0a-i386-binary-1.iso
Severity: critical

I attempted to install Sarge (2.6.8-2-686) today on a Dell
Dimension 8400 desktop.  Upon reboot after installation,
there was a kernel panic with the following error messages:

pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!

Just before this, the messages indicate that the kernel has found
the hard disk (Serial ATA Maxtor 6Y160M0):

scsi0: ata_piix
Using anticipatory io scheduler

  [drive info]

ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15

and so on (I am typing this by hand, since the machine then
crashed and there are no logs).

By replacing "hda" with "sda" in the following line in
/boot/grub/menu.lst, I was able to prevent the panic:

kernel/vmlinuz-2.6.8-2-686 root=/dev/hda6 ro

The boot then failed when it tried to fsck the swap and
remaining ext3 partitions until I made similar replacements
of "hda" with "sda" in /etc/fstab.  This allowed the boot
process to finish, but then the kernel would not recognize
the cdrom drive.

This may be related to bugs #299478 and #285981.

Other people have described this problem here:

   http://www.debianplanet.org/node.php?id=1094

The same problem appears here:

   http://wiki.debian.net/?DebianInstallerBrokenThings

without attribution or a bug reference.


Everett Lipman

--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Bug#234887: marked as done (crash installing grub)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 
uname -a: Linux ns 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686
GNU/Linux
Date: 2004-02-10 10:00
Method: network install ftp.es.debian.org, no proxie

Machine: HP ProLiant DL360 G3
Processor: Xeon
Memory: 1GB
Root Device: SCSI HP Smart Array 5i
Root Size/partition table:
Output of lspci:

Base System Installation Checklist:

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

Comments/Problems:
First of all, excuse my english. I'm spanish.
It seems that the new HP ProLiant DL360 G3 has changed the Compact Smart
Array 5i disk controller for the new HP Smart Array 5i, and the second
is lightly incompatible with te first one. In fact, the installation
process detects the Compact controller but it can't make it work. So,
therefore may be in some way incompatible.



--- End Message ---
--- Begin Message ---
Hello,

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in
http://www.debian.org/devel/debian-installer/

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Processed: tagging 360578

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.19
> tags 360578 + patch
Bug#360578: busybox: passwd uses null salt (weak encryption) [CVE-2006-1058]
Tags were: security
Tags added: patch

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#367149: kbd-chooser: [powerpc] does not detect ADB keyboards

[Eddy Petrişor]

On 5/14/06, Frans Pop <[EMAIL PROTECTED]> wrote:

Package: kbd-chooser
Version: 1.26

It appears that kbd-chooser does not actually detect ADB keyboards as used
for example on Powerbook G4 laptops.
Until Beta 2 keyboard selection only worked because of the default mac-usb
keyboard added in usb-kbd.c, but that's absolutely not optimal.

After a short look at Frank Lichtenhelds laptop, it seems that the
keyboard can be detected from the /proc/bus/input/devices file (see
attachment).

It's currently unsure if the keyboard will work correctly with AT keymaps
as well as USB-MAC. I'll test that over the next days.


I can test this when is ready. (An explamation for way to
infirm/confirm that the keyboard was detected correctly would be nice
to have before doing this, 'though).

PowerBook 5,2 here.

--
Regards,
EddyP
=
"Imagination is more important than knowledge" A.Einstein

Bug#311186: marked as done (install: Installation leaves badly configured GRUB)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 18:52:25 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Should be fixed in current installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: install
Severity: important
Tags: experimental


Installing using 
/pub/cdimage-testing/daily/i386/20050527/debian-testing-i386-netinst.iso
and entering partition /dev/hda1 on /boot, /dev/hda6 on /, installs kernel
2.6.8 correctly in /boot. However, GRUB is now configured incorrectly:
  boot (hd0,0)
  kernel /boot/vmlinuz-2.6.8
  initrd /boot/something

This fails to boot since /boot is on (hd0,0). Therefore, '/boot' should be
removed from both 'kernel' and 'initrd' line from GRUB configuration.
Changing this resumes booting (instead of 'cannot find file').

Maybe related:
After finishing installation, /etc/fstab contains
  # UNCONFIGURED FSTAB FOR BASE SYSTEM
and /boot contains
  lrwxrwxrwx  1 root root 1 2004-11-14 01:09 boot -> .

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

--- End Message ---
--- Begin Message ---
Hello,

This problems looks to be already fixed in current installer
images. If you can still reproduce this problem, please reopen this
bug.

Thanks,

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."
--- End Message ---

Re: Integrating klibc's ipconfig into netcfg

[Andrew Pollock]

On Sun, May 14, 2006 at 11:00:59PM +0200, Geert Stappers wrote:
> On Mon, May 15, 2006 at 03:33:08AM +1000, Andrew Pollock wrote:
> > Hello,
> > 
> > I've been meaning to do this for probably a year, but I've finally gotten
> > around to actually looking into what is involved in using ipconfig in netcfg
> > as a replacement to dhcp-client, so we can get rid of DHCPv2 altogether.
> > 
> > The first observation I've made is that it doesn't appear to pass the
> > hostname in the request.
> 
> In dhcp.c is this code snippet:
> 
> | case DHCLIENT:
> |   /* First, set up dhclient.conf */
> |
> |   if ((dc = file_open(DHCLIENT_CONF, "w")))
> |   {
> | fprintf(dc, "send dhcp-class-identifier \"d-i\";\n" );
> | if (dhostname)
> | {
> |   fprintf(dc, "send host-name \"%s\";\n", dhostname);
> | }
> | fclose(dc);
> |   }
> 
> So only when dhostname is set, it sends the hostname in the request.
 
Yup, I figured it wasn't something that happened all the time.
 
> >  I'm attempting to clarify this with the author at the moment,
> > but if someone with more C-fu than myself wants to take a look,
> > I'd appreciate it.
> 
> I hope the above text did help.
> 
> 
> > If indeed this is the case, is this a show stopper? I recall some bugs filed
> > in the past from people trying to install on a cable connection where the
> > cable provider required the hostname in order to issue a lease, so I'm
> > assuming it is.
> 
> Beside sending the hostname for cable providers,
> there is also the need to send dhcp-class-identifier "d-i",
> to allow DHCP preseeding.

I think that getting it to set random options is going to be a big ask, it's
too lightweight for that. Might be back to the drawing board...

Does that mean the that cases there are largely irrelevant? I mean pump
doesn't appear to support setting that vendor-class-identifier option...

regards

Andrew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

installing debian without debian-installer

[chantra]

Hi,

I've installed debian etch without debian-installer or any CD
image.

The fact that debian-installer ("base-config") is now execute during
the first installation part before the reboot, and that there is not
anymore "base-config" or similar in the repository force me to do a
manual installation old school.

Well, the aim was to install debian without using any cd or booting
device, but simply by using the linux image my computer was already
running on.

That was a good experience and made an article explaining how-to
achieve this.
http://www.debuntu.org/2006/05/14/51-how-to-installing-debian-etch-from-a-running-debian-based-system

I know it is not much of what this mailing list is for, but I thought
it might interest some of you.

cheerio,
chantra

Bug#285898: Still reproducable?

[Otavio Salvador]

Hello,

We are trying to figure out which bugs were solved in GRUB in sid and
testing since the release of sarge and since your bug report is very
old would be good if you could test if it still reproducable in
current beta2 or snapshot d-i images?

Images: http://www.debian.org/devel/debian-installer/

TIA,

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#365747: marked as done (base-installer: Add /dev/mapper in all cases needed)

[Debian Bug Tracking System]

Your message dated Sun, 14 May 2006 14:02:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365747: fixed in base-installer 1.57
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: base-installer
Severity: wishlist

Now /dev/mapper structure is created only if lvm2 is detected. However,
device-mapper is also used by dm-crypt and EVMS. This patch creates
/target/dev/mapper in case device-mapper module is loaded. This
directory is needed (atleast) to get grub installed.

The approach in the patch has the slight inconvinience of creating the
directory in some cases even if not really needed. For example in case
user has created encrypted partitions that are not / or /boot related.
In My (lazy) opinion, wasting few nodes on target is accepteble, since
adding more fine grained tests would instead bloat the base-installer
script and make it more fragile.

(Riku: please file such requests as wishlist bugs next time)
Index: postinst
===
--- postinst(revision 36896)
+++ postinst(working copy)
@@ -323,18 +323,20 @@
if [ -e /proc/mdstat ] && grep -q ^md /proc/mdstat ; then
apt-install mdadm
fi
-   # LVM: create VG and LV devices
-   if pvdisplay | grep -iq "physical volume ---" && grep -q " 
device-mapper$" /proc/misc; then
-   apt-install lvm2
-   mount -t proc proc /target/proc
+   # device-mapper
+   if grep -q " device-mapper$" /proc/misc; then
mkdir -p /target/dev/mapper
if [ ! -e /target/dev/mapper/control ] ; then
major=$(grep "[0-9] misc$" /proc/devices | sed 's/[ 
]\+misc//')
minor=$(grep "[0-9] device-mapper$" /proc/misc | sed 
's/[ ]\+device-mapper//')
mknod /target/dev/mapper/control c $major $minor
fi
-   chroot /target vgscan --mknodes || true
-   umount /target/proc
+   if pvdisplay | grep -iq "physical volume ---"; then
+   apt-install lvm2
+   mount -t proc proc /target/proc
+   chroot /target vgscan --mknodes || true
+   umount /target/proc
+   fi
fi
# UML: create ubd devices
if grep -q "model.*UML" /proc/cpuinfo; then
--- End Message ---
--- Begin Message ---
Source: base-installer
Source-Version: 1.57

We believe that the bug you reported is fixed in the latest version of
base-installer, which is due to be installed in the Debian FTP archive:

base-installer_1.57.dsc
  to pool/main/b/base-installer/base-installer_1.57.dsc
base-installer_1.57.tar.gz
  to pool/main/b/base-installer/base-installer_1.57.tar.gz
base-installer_1.57_i386.udeb
  to pool/main/b/base-installer/base-installer_1.57_i386.udeb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frans Pop <[EMAIL PROTECTED]> (supplier of updated base-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 14 May 2006 22:54:26 +0200
Source: base-installer
Binary: base-installer
Architecture: source i386
Version: 1.57
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Frans Pop <[EMAIL PROTECTED]>
Description: 
 base-installer - Install the base system (udeb)
Closes: 365747
Changes: 
 base-installer (1.57) unstable; urgency=low
 .
   [ Frans Pop ]
   * Create devmapper device nodes in /target if these are used in the 
installer;
 needed for partman crypto (closes: #365747). Patch by Riku Voipio.
   * If root is encrypted, also create crypto device nodes. Patch by David
 Härdeman.
 .
   [ Martin Michlmayr ]
   * Remove incomplete LART and BAST support.
   * Drop Riscstation since it's no longer supported in 2.6 kernels.
 .
   [ Colin Watson ]
   * Rename install_kernel to install_linux, to allow for future ports to
 other systems.
 .
   [ Christian Perrier ]
   * Split _Choices to __Choices in templates
 .
   [ Updated t

Re: Running debian-installer from the command line?

[Joachim Durchholz]

Geert Stappers schrieb:

On Fri, May 12, 2006 at 02:54:07PM +0200, Joachim Durchholz wrote:
So... what I'm really after is a way to skip all the boot machinery in 
debian-installer. It should still do everything else (hardware 
detection, partitioning, base configuration, package installation, and 
whatever else I forgot to mention).


Have you tried to unpack the d-i image in / of the running system,
and doing a `telinit -Q` ?


No, I didn't know anything about the way that an installation system boots.
But it does sound like a viable approach. It didn't occur to me that 
installers might use the same startup machinery as a normal system 
(silly me...)


Um... telinit alone might not work, and there's some setup work 
involved. Let me spell out the steps:


1. Base system has / on a RAM disk
2. Partition and format the HDD as needed
3. Mount the future root partition on (say) /mnt/root
4. Download the ISO into / (or to /mnt/root if it won't fit into the
   RAM disk)
5. mkdir /mnt/iso, loop-mount the ISO to /mnt/iso
6. cp -a /mnt/iso /mnt/root
7. Shutdown most daemons. Particularly those that service any IP ports.
   (Other services, too?)
8. chroot /mnt/iso /bin/bash --login
9. telinit -Q

Did I leave anything essential out? Caveats? Pitfalls?

It's a bit late for me right now. I'll try this tomorrow, with any 
advice that I might receive integrated.


Regards,
Jo


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[LONG] ppp-udeb: A succesful installation using it, some ideas and some requests for advices

[Eddy Petrişor]

Hello all,

I have some good news regarding ppp-udeb and PPPoE. As the subject
says, I have managed to conduct an installation over PPPoE using the
patched ppp-udeb I have created and a customized image[1].

The good news:
- the pppoe connection was configured and packages were downloaded
from the internet over that connection
- the ppp-udeb has appeared within the additional components list

The bad news:
- there seem to be some problems with pppoe modules not being loaded
automatically (must I add „modprobe pppoe" in the postinst? if so, how
do I keep the output from interfering with debconf?)
- there are some weird side effects (probably due to messages being
spitted out to stderr or stdout in the postinst); what should I do
with the error messages? I would like to have errors logged in the
syslog, but it looks to me that I should direct stdout messages to
/dev/null so it does not interact with debconf
- the postinst starts multiple connections if the step is run
multiple times, so is not policy compliant and it should changed to
detect running connections on the interface which will be used (a
little bit tricky for multiple net card systems)
- if the pppoe connection fails, then that is silent; no message is
given which is bad
- the dialog boxes for username and password are asymetric (entry
fields way close to the left margin) and the title of the dialog is
cut.





There are some problems which are a little bit more complex and I am
asking for advice:
a) the pppoe connection detection should it fail silently on a normal install?
b) when should the ppp-udeb postinst should be ran? after or before
dhcp (fails)?
c) what should be done for systems with multiple network cards?
d) how can the pppoe software be added automatically to the target
system (in case the pppoe configuration succeded during the
installation it would make sense to have it configured in the target
system, too)




The way I am thinking the PPPoE configuration should be done/integrated in d-i:
- if dhcp fails, try the detection of concentrators (implies running
ifconfig ethX up)
- if concentrator detection fails, drop to manual configuration
- if a concentrator is found on a card, request user input regarding
username and password for the PPPoE configuration
- try the configuration with the given data
- in case it fails, drop a fat error message (requesting the info to
be reinserted?)
- in case configuration succedes, then everything is fine

Please comment (my explanation and more questions are below).


The pppoe and dhcp protocols are orthogonal, so if one configuration
succedes on a card, there is no way the other will. So the question
is, when should the PPPoE configuration be attempted? It seems logical
to be attempted after dhcp has failed because it will mean that less
input will be necessary on default installs.
But that, AFAIK, would lead to an unnecessary step in the
configuration and the imposibility to run the PPPoE configuration
directly from the d-i menu. Is this a real problem?

The PPPoE protocol works with the so called concentrators which could
be detected automatically which would mean that for Ethernet cards
which are not supposed to connect to PPPoE servers for configuration
the pppoe questions could be omitted and the installer should be
directed to static configuration. I am not sure if there are cases in
which the concentrator is not detected, but I fear that in the case in
question the whole configuration will fail altogether.
The detection of the concentrators and the actual configuration can't
be made in deifferent postinst scripts, so would it make sense to
return 0 as an exit code from the ppp-udeb postinst if no
concentrators are found?

Once the configuration is made for one card, should it be attempted
for others, too? This is a little bit difficult and I fear there are
not so many practical cases in which it will apply, if none.

In systems with multiple cards, I don't think there is a way to know,
after the configuration has been done, on which Ethernet card the ppp
connection exists, so if the postinst is ran multiple times there are
issues related to determining which pppd process corresponds to which
etherenet card.
I probably the concentrators detection could be ran again, but should
the current ppp connection be dropped, if it exists?


In case the PPPoE connection fails, should the user be given the
chance to configure the card as static? Note that if the concentrator
is found it shouldn't make sense and it might be possible that the
configuration data was given incorrectly.


There is small issue, if the concentrator is searched on a card, then
the card in question must be "ifconfig CARD up" with no IP, should
this be restored if the concentrator is not found? Would it affect the
static configuration?


How can the configuration information be copied to the target system
after the system is installed?



[1] using instructions at http://wiki.debian.org/DebianInstaller/Modify

--
Regards,
Edd

Re: partman-crypto: dm-crypt status update

[David Härdeman]

On Sun, May 14, 2006 at 11:15:00PM +0200, Jesus Climent wrote:

On Sun, May 14, 2006 at 09:59:05PM +0200, David Härdeman wrote:

Hi all,

Here's a short status update on the progress of adding dm-crypt support 
to partman-crypto.


The support is now at a stage where it is possible to perform a full 
crypto-on-root installation and to boot into the newly installed 
system.


GREAT!

I am testing it over here in Mexico and seems to work mostly fine (although I
have not been able to complete a single installation for other reasons).

There seems to be a bug somewhere, because sometimes it finds the lvm crypto
partition and sometimes it fails...


Hmm...lvm-on-crypto and crypto-on-lvm is currently untested. It's on my 
todo list now that the basic (i.e. crypto on a device like /dev/sda2) 
functionality works.


The only known bug so far is that the /target filesystem isn't cleanly 
unmounted when it's on an encrypted partition. Any suggestions on where 
to start looking?


No idea, but I guess you know that one has to delete the dm accessing the
partition before umounting it, right?


Um, not sure what you mean. If /dev/sda2 is setup via dm-crypt as 
/dev/mapper/crypt0 which is in turn mounted as /...then the teardown 
order should be first to unmount / and then to remove the crypt0 
mapping. Since unmounting / wouldn't work very well, I'd expect it to be 
remounted ro, but it doesn't seem to work...ext2fsck complains on the 
first boot...


Re,
David


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

base-installer_1.57_i386.changes ACCEPTED

[Debian Installer]

Accepted:
base-installer_1.57.dsc
  to pool/main/b/base-installer/base-installer_1.57.dsc
base-installer_1.57.tar.gz
  to pool/main/b/base-installer/base-installer_1.57.tar.gz
base-installer_1.57_i386.udeb
  to pool/main/b/base-installer/base-installer_1.57_i386.udeb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 365747 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: partman-crypto: dm-crypt status update

[Jesus Climent]

On Sun, May 14, 2006 at 09:59:05PM +0200, David Härdeman wrote:
> Hi all,
> 
> Here's a short status update on the progress of adding dm-crypt support 
> to partman-crypto.
> 
> The support is now at a stage where it is possible to perform a full 
> crypto-on-root installation and to boot into the newly installed 
> system.

GREAT!

I am testing it over here in Mexico and seems to work mostly fine (although I
have not been able to complete a single installation for other reasons).

There seems to be a bug somewhere, because sometimes it finds the lvm crypto
partition and sometimes it fails...

> The only known bug so far is that the /target filesystem isn't cleanly 
> unmounted when it's on an encrypted partition. Any suggestions on where 
> to start looking?

No idea, but I guess you know that one has to delete the dm accessing the
partition before umounting it, right?

Cheers,

-- 
Jesus Climent  info:www.pumuki.org dj:triplestereo.com
Unix SysAdm|Linux User #66350|Debian Developer|2.6.16|Helsinki Finland
GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429  7E18 66FC 1D7F 8694 6D69

If you think that there is a solution, you'll die here.
--Gibarian (Solaris)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Integrating klibc's ipconfig into netcfg

[Geert Stappers]

On Mon, May 15, 2006 at 03:33:08AM +1000, Andrew Pollock wrote:
> Hello,
> 
> I've been meaning to do this for probably a year, but I've finally gotten
> around to actually looking into what is involved in using ipconfig in netcfg
> as a replacement to dhcp-client, so we can get rid of DHCPv2 altogether.
> 
> The first observation I've made is that it doesn't appear to pass the
> hostname in the request.

In dhcp.c is this code snippet:

| case DHCLIENT:
|   /* First, set up dhclient.conf */
|
|   if ((dc = file_open(DHCLIENT_CONF, "w")))
|   {
| fprintf(dc, "send dhcp-class-identifier \"d-i\";\n" );
| if (dhostname)
| {
|   fprintf(dc, "send host-name \"%s\";\n", dhostname);
| }
| fclose(dc);
|   }

So only when dhostname is set, it sends the hostname in the request.


>  I'm attempting to clarify this with the author at the moment,
> but if someone with more C-fu than myself wants to take a look,
> I'd appreciate it.

I hope the above text did help.


> If indeed this is the case, is this a show stopper? I recall some bugs filed
> in the past from people trying to install on a cable connection where the
> cable provider required the hostname in order to issue a lease, so I'm
> assuming it is.

Beside sending the hostname for cable providers,
there is also the need to send dhcp-class-identifier "d-i",
to allow DHCP preseeding.


> regards
> 
> Andrew

Cheers
Geert Stappers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of base-installer_1.57_i386.changes

[Archive Administrator]

base-installer_1.57_i386.changes uploaded successfully to localhost
along with the files:
  base-installer_1.57.dsc
  base-installer_1.57.tar.gz
  base-installer_1.57_i386.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

partman-crypto: dm-crypt status update

[David Härdeman]

Hi all,

Here's a short status update on the progress of adding dm-crypt support 
to partman-crypto.


The support is now at a stage where it is possible to perform a full 
crypto-on-root installation and to boot into the newly installed 
system.


This depends on:

o partman-crypto built from SVN
o base-installer built from SVN + patch from #365747
o cryptsetup built from SVN + a pending patch which adds 
 update-initramfs to postinst

o libpopt0 udeb built with patch from #358671

all of these will be in the standard repository as soon as the 
maintainer uploads a new version of the relevant package.


The only known bug so far is that the /target filesystem isn't cleanly 
unmounted when it's on an encrypted partition. Any suggestions on where 
to start looking?


Next I'll be working on getting lvm-on-crypto working.

Regards,
David


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#367264: mapping clause now useless; please remove

[EspeonEefi]

Package: netcfg
Severity: normal

A bit of history for reference can be found in bug #340935 .

If the interface set up should be brought up upon detection by a 
hotplugging mechanism, netcfg inserts the following clause into the 
generated /etc/network/interfaces file:

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping eth0
script grep
map eth0

(This is written by netcfg_write_common() in netcfg-common.c.)

Now, I believe this is cruft code left over from the old hotplugging 
system. I believe that the way it used to work was that you would have 
something like...

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth0
map eth2

Then, when the first network was hotplugged, hotplug would go

ifup eth0=hotplug

ifup would look through /etc/network/interfaces looking for the 
definition of the logical interface hotplug. It would find the mapping 
clause and would proceed to call the script named by the script 
definition with the physical interface as the argument and it would send 
the lines marked by map to its standard input. That is, it would see 
hotplug was a mapping logical interface, it would call

grep eth0

and write to grep's standard input

eth0
eth2

At this point, grep would return the line

eth0

which ifup would use then as the logical interface to bring up the 
physical eth0 as. (That is, ifup would transform ifup eth0=hotplug into 
ifup eth0=eth0.)

Note that the same thing would be done for eth2.

Note however, that upon hotplugging the second network card, physical 
interface eth1, ifup eth1=hotplug would get nothing back from grep. ifup 
would take this as a sign that eth1 should not be brought up under the 
current conditions.

(This is why the comment says that the mapping clause is there to 
contain a list of hotpluggable interfaces.)

Unfortunately, all of this was lost in the fix to shift to allow-hotplug 
to mark hotpluggable interfaces (see the bug referenced above). Now 
we're left with netcfg putting a totally useless mapping clause with an 
utterly confusing associated comment into the default installed 
/etc/network/interfaces...

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for integration of the graphical installer

[Eddy Petrişor]

On 5/14/06, Christian Perrier <[EMAIL PROTECTED]> wrote:

> > I'm not really completely fond of these names, mostly because I find
> > them hard to type on non US keyboards.
> >
> > I would vote for "gui" and "gui-expert"...or "expert-gui"
>
> Is the hyphen the problem? I've left that out currently.

At least the hyphen can be a problem. It's actually pretty hard to
find it on a laptop with a French keyboard mapped as a US keyboard.

"gui" is perfect with that matter as this only involves keys that are
in the same place on all keyboard layouts (except Dvorak, but noone
cares about it for newbies..:-)))


If the hyphen is the problem, then why not totaly drop it?

--
Regards,
EddyP
=
"Imagination is more important than knowledge" A.Einstein

Re: Proposal for integration of the graphical installer

[Eddy Petrişor]

On 5/14/06, Frans Pop <[EMAIL PROTECTED]> wrote:

On Sunday 14 May 2006 17:46, Joey Hess wrote:
> Geert Stappers wrote:
> > New knowlegde learnt me not to laugh at "experts" doing an
> > installation with the boot option 'expert'. I think it is time to
> > educate the "experts" and tell them and _everyone_ that 'expert' is
> > 'detail'[1]
>
> Hmm, I think that caling it "detail" is the best description I've seen
> of it so far. (As a native English speaker, I'd prefer "detailed" but
> that might be asking for too much).

"expert" is probably easier on non-english speakers though.


Why? do you feel that „expert" sounds similar in more languages than „detailed".

I personaly agree with Joey that „detailed" is better; if you think of
it, that is what actually is happening, you are given a lot of
details.


--
Regards,
EddyP
=
"Imagination is more important than knowledge" A.Einstein

Re: Debian Installer team monthly meeting minutes (20060429 meeting)

[Steve Langasek]

On Sat, May 13, 2006 at 08:33:17AM +0200, Samuel Thibault wrote:
> Samuel Thibault, le Tue 09 May 2006 21:28:27 +0200, a écrit :
> > Samuel Thibault, le Tue 02 May 2006 21:50:39 +0200, a écrit :
> > > Christian Perrier, le Tue 02 May 2006 19:59:54 +0200, a écrit :
> > > > brltty integration
> > > > --
> > > > Unofficial images have been built by Samuel Thibault but we don't have
> > > > much news.

> > > Brltty 3.7.2-3 should enter testing on Thursday.

> > Answering to myself. It is still not in testing because of "mayr"
> > mips buildd which keeps brltty in the "Building" state [1] for that
> > architecture, although the package compiled fine [2]...

> Grmbl. Now that this available, I realize that brltty and gnopernicus
> must go into testing _together_, and gnopernicus waits for gnutls13
> (which has a RC bug) and avahi, which depends on qt4-x11, which depends
> on x11proto-core, i.e. Xorg 7.0...

> So this will unfortunately have to wait quite some time...

The gnutls13 RC bugs have just been fixed in NMU, and we are hoping for an
xorg 7 push to testing some time within the next week, so all is not lost.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for integration of the graphical installer

[Christian Perrier]

> > I'm not really completely fond of these names, mostly because I find
> > them hard to type on non US keyboards.
> > 
> > I would vote for "gui" and "gui-expert"...or "expert-gui"
> 
> Is the hyphen the problem? I've left that out currently.

At least the hyphen can be a problem. It's actually pretty hard to
find it on a laptop with a French keyboard mapped as a US keyboard.

"gui" is perfect with that matter as this only involves keys that are
in the same place on all keyboard layouts (except Dvorak, but noone
cares about it for newbies..:-)))




signature.asc
Description: Digital signature

Re: Proposal for integration of the graphical installer

[Joey Hess]

Christian Perrier wrote:
> Quoting Frans Pop ([EMAIL PROTECTED]):
> 
> > - As there will be separate initrds for CD images, we'll also need
> >   separate boot options. We're thinking of "install-gui" and "expert-gui".
> >   Other suggestions welcome.
> 
> 
> I'm not really completely fond of these names, mostly because I find
> them hard to type on non US keyboards.
> 
> I would vote for "gui" and "gui-expert"...or "expert-gui"

Is the hyphen the problem? I've left that out currently.

-- 
see shy jo


signature.asc
Description: Digital signature

Integrating klibc's ipconfig into netcfg

[Andrew Pollock]

Hello,

I've been meaning to do this for probably a year, but I've finally gotten
around to actually looking into what is involved in using ipconfig in netcfg
as a replacement to dhcp-client, so we can get rid of DHCPv2 altogether.

The first observation I've made is that it doesn't appear to pass the
hostname in the request. I'm attempting to clarify this with the author at
the moment, but if someone with more C-fu than myself wants to take a look,
I'd appreciate it.

If indeed this is the case, is this a show stopper? I recall some bugs filed
in the past from people trying to install on a cable connection where the
cable provider required the hostname in order to issue a lease, so I'm
assuming it is.

regards

Andrew


signature.asc
Description: Digital signature

Bug#367245: software raid cannot be used for anything

[Jonas Meyer]

Package: installation-reports

Boot method: business card
Image version: May 13 2006 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-businesscard.iso
Date: May 14 2006

Machine: qemu
Processor:
Memory:
Partitions: 3 qemu images hda hdb and hdd. each 300M and containing 15M for 
raid0 for /boot 
and the rest for lvm on raid5

Output of lspci and lspci -n: 

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [E]
Create file systems:[E]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]

Comments/Problems:
the partitioner cannot be used to do anything with the md devices. 
everything you try to assign to it like a filesystem or a physical 
volume for lvm tries to use md0p1 or md1p1. this is nonsense as md 
devives are not to be partitioned.

also the etch netboot images for i386 seem to be all broken. I could 
get the sarge netboot to work without problems. the etch ones didn't
work at all. in one case init not found - the other an io error for 
/lib/libc.6.so




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for integration of the graphical installer

[Frans Pop]

On Sunday 14 May 2006 17:46, Joey Hess wrote:
> Geert Stappers wrote:
> > New knowlegde learnt me not to laugh at "experts" doing an
> > installation with the boot option 'expert'. I think it is time to
> > educate the "experts" and tell them and _everyone_ that 'expert' is
> > 'detail'[1]
>
> Hmm, I think that caling it "detail" is the best description I've seen
> of it so far. (As a native English speaker, I'd prefer "detailed" but
> that might be asking for too much).

"expert" is probably easier on non-english speakers though.

I'd still prefer to see medium priority become the default "expert" mode 
and low priority become an option once booted at medium priority.


pgpUv7EKdc9F2.pgp
Description: PGP signature

Re: Proposal for integration of the graphical installer

[Christian Perrier]

Quoting Frans Pop ([EMAIL PROTECTED]):

> - As there will be separate initrds for CD images, we'll also need
>   separate boot options. We're thinking of "install-gui" and "expert-gui".
>   Other suggestions welcome.


I'm not really completely fond of these names, mostly because I find
them hard to type on non US keyboards.

I would vote for "gui" and "gui-expert"...or "expert-gui"

As one of the targets os the graphical installer are less experienced
users, we also need to decide whether it will be the default mode for
isntallation.



signature.asc
Description: Digital signature

Re: installer images for amd64 newer then 2006-APR-08

[Frans Pop]

On Sunday 14 May 2006 16:17, Geert Stappers wrote:
> Right now are the most recent images of debian-installer for amd64
> from the 8th of last month. I found those some what old files by
> following the home page of d-i
> on http://www.nl.debian.org/devel/debian-installer/
> to http://amd64.debian.net/debian-installer/daily/
>
> It seems to me that there is no daily build of d-i for amd64 is done.

This is the result of the archive integration for amd64. amd64 is 
currently "unbuildable" because the official archive is incomplete and 
building new images from the old unofficial archive is pointless as it is 
frozen.
People are working on this.

> Is someone willing to donate or to loan me a amd64,
> so that I can do the daily build of d-i for amd64?

No need. The people that did the build are perfectly capable of doing it 
and will resume the daily builds as soon as circumstances allow it again.


pgpTMPC5HwVdD.pgp
Description: PGP signature

Relocation errors in cdebconf plugins

[Max Vozeler]

Hi all,

I'm seeing a problem trying to use the cdebconf-entropy plugin
after loading it in a daily build [0] (it does not happen when it
is included in the initrd [1]). In short: cdebconf dlopen()s the
plugin without problem (RTLD_LAZY), but dies with a relocation
error as soon as the plugin uses mlock():

 writev(2, [{"debconf", 7}, {": ", 2}, {"relocation error", 16}, {": ", 2}, 
{"/usr/lib/cdebconf/frontend/newt/plugin-entropy-text.so", 54}, {": ", 2}, 
{"symbol mlock, version GLIBC_2.0 not defined in file libc.so.6 with link time 
reference", 86}, {"", 0}, {"", 0}, {"\n", 1}], 10) = 170

The problem is apparently that mlock() gets stripped from the
early version of libc.so.6 included in the initrd because nothing
in the initrd references the symbol. The libc later installed
from libc6-udeb does include mlock(), but cdebconf gets started
before it is available and so still has the reduced libc loaded.
It seems that the linker continues to try resolve new symbols in
dlopen()ed plugins using the early reduced libc.

  $ nm -B working/libc.so.6 | grep mlock
  0006db40 T mlock
  0006dbc0 T mlockall
  
  $ nm -B non-working/libc.so.6 | grep mlock
  $

If this is indeed the case, I think it means that cdebconf
plugins must either a) use only symbols that are also referenced
in cdebconf itself or something else included in the initrd or b)
be included in the initrd during library reduction. If somebody
can confirm this conclusion, I'll try to add some mention of
this proble to the cdebconf plugin documentation.

I'm a bit at loss how to solve this for cdebconf-entropy. It
would either need to included in the initrd of all builds that
one may want to use partman-crypto in (udeb: 5148 bytes,
installed: 40k), or there would need to be some kind of mechanism
to tell mklibs (it does the reduction, correct?) that certain
symbols should be retained even if they are not used by anything
in the initrd tree.  Any suggestions what I should do?

Regardless of the above case, I think it's quite bad 
if a plugin can take down cdebconf by having unresolved symbols.
The problem is, I think, that when using RTLD_LAZY, there is no 
way to gracefully signal that a problem resolving symbols has
occured after dlopen() has returned. I have tried this yet, but
in theory using RTLD_NOW should prevent this exact problem. It
should make dlopen() return NULL if any unresoved ymbols exist.
I will try to do a build of cdebconf with RTLD_NOW to verify that
it indeed prevents the problem and doesn't break anything and
let you guys know how it worked out.

cheers,
Max

-- 
[0] http://people.debian.org/~joeyh/d-i/images/2006-05-14/netboot/mini.iso
[1] http://nusquama.org/~max/d-i/crypto/2006-05-14/netboot/mini.iso


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for integration of the graphical installer

[Joey Hess]

Geert Stappers wrote:
> New knowlegde learnt me not to laugh at "experts" doing an installation
> with the boot option 'expert'. I think it is time to educate the
> "experts" and tell them and _everyone_ that 'expert' is 'detail'[1]

Hmm, I think that caling it "detail" is the best description I've seen
of it so far. (As a native English speaker, I'd prefer "detailed" but
that might be asking for too much).

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#367228: FTBFS: missing build-depends on debhelper

[Martin Michlmayr]

Package: srm-reader
Version: 0.09
Severity: serious

> Automatic build of srm-reader_0.09 on juist by sbuild/alpha 0.44
...
> dpkg-source: unpacking srm-reader_0.09.tar.gz
> dpkg-buildpackage: source package is srm-reader
> dpkg-buildpackage: source version is 0.09
> dpkg-buildpackage: host architecture alpha
> dpkg-buildpackage: source version without epoch 0.09
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> make: dh_testdir: Command not found
> make: *** [clean] Error 127

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#366336: d-i adding extra kernel command line parameters -- BOOT_I

[John Smith]

Please close this bug, since it's a feature, not a bug:
the text " -- BOOT_IMAGE=full/path/to/the/kernel-image"
is added to the kernel command line. The fact that it's
truncated at 256 characters, is probably due to the
used bootloader.

Sincerely,

Jan.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

installer images for amd64 newer then 2006-APR-08

[Geert Stappers]

Hello,

Right now are the most recent images of debian-installer for amd64
from the 8th of last month. I found those some what old files by
following the home page of d-i
on http://www.nl.debian.org/devel/debian-installer/ 
to http://amd64.debian.net/debian-installer/daily/

It seems to me that there is no daily build of d-i for amd64 is done.

Is someone willing to donate or to loan me a amd64,
so that I can do the daily build of d-i for amd64?


Cheers
Geert Stappers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Etch/Sid is installable on amd64, the next level

[Geert Stappers]

On Sun, May 14, 2006 at 09:19:23AM +, Wasfi JAOUAD wrote:
> Well, it's ok with the i386 version of the installer, but the AMD64 one still 
> says : 
> 
>!! install the base system
>Cannot install the base system
> The installer connot figure out how to install the base system. No 
> installable CD-ROM 
> was found and no valid miroor was configured.
> (with a scary red background ;-)
> 
> Or you mean the fix will automatically be appiled to AMD64 d-i ?
> Actually Joey's fix dealt with not finding packages inside ISOs, here the ISO 
> itself
> was not found.. hopefully it fixes both..
>
> Full logs of a try with latest binaries from amd64.debian.net are attached.
> [ Attachment: amd64-08-Apr-2006.7z ]


Okay, let's go to the next level of the game. This level is multi-user.

There is a (unwritten??) rule that says that
 the time of the other players is very valueable.

Several technical tools support that rule about costly user time.
One kind of tools are E-mail programms that allow threaded E-mail,
another kind is a bug tracking system. Both kinds make it possible to
the players of the game to read in a single thread or bugreport what is
going.
The tools need human intervention to avoid clutter and/or redundant text.
Do this by replying under the text and removing text that has surely be
seen. ( Keep some text as context for your reply. )


The same message in other words:

- The report of something being broken is been seen.
- There is a sort of desire to help.
- Invest time in making good readable reports _and_ follow-ups.


Cheers
Geert Stappers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#367194: FTBFS: missing build-depends on debhelper

[Martin Michlmayr]

Package: aboot-installer
Version: 0.0.20
Severity: serious

You're missing a build-dependency on debhelper:

> Automatic build of aboot-installer_0.0.20 on juist by sbuild/alpha 0.44
...
> dpkg-buildpackage: source package is aboot-installer
> dpkg-buildpackage: source version is 0.0.20
> dpkg-buildpackage: host architecture alpha
> dpkg-buildpackage: source version without epoch 0.0.20
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> make: dh_testdir: Command not found
> make: *** [clean] Error 127

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for integration of the graphical installer

[Sven Luther]

On Sat, May 13, 2006 at 11:23:52PM +0200, Frans Pop wrote:
> Yesterday Joey and I discussed the integration of the graphical installer 
> into the regular build system, and the result is below for wider 
> discussion and comments.
> 
> The below should be valid for both i386, but may need adjustment for 
> powerpc. Comments from Colin on that are very welcome.

Just a note concerning powerpc.

Most recent powerpc hardware come with slot-loading optical drives. This means
that keeping the businesscard and netinst images small to fit in the
businesscard and netinst medias, apart from being probably a doomed effort, is
not all that useful in itself, as business card CDs are useless with
slot-loading drives.

It is usefull to keep those images relatively small, but given their current
size, growing from 250 to 300 MB or whatever it is, will probably pass
un-noticed.

So, i would vote for always including the g-i images onto the business card,
netinst and cd isos, with the same caveat as on i386 concerning the
installable tasks of CD 1. DVD medias should be un-problematic though.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for integration of the graphical installer

[Geert Stappers]

On Sat, May 13, 2006 at 11:23:52PM +0200, Frans Pop wrote:
> Yesterday Joey and I discussed the integration of the graphical installer 
> into the regular build system, and the result is below for wider 
> discussion and comments.
 
> - As there will be separate initrds for CD images, we'll also need
>   separate boot options. We're thinking of "install-gui" and "expert-gui".
>   Other suggestions welcome.

New knowlegde learnt me not to laugh at "experts" doing an installation
with the boot option 'expert'. I think it is time to educate the
"experts" and tell them and _everyone_ that 'expert' is 'detail'[1]

So my request is to replace 'expert-gui' with 'detail-gui'
And reopen the discussion on 'expert' alternatives.

> Including the g-i images on the netinst will mean that it will grow bigger 
> than its current "maximum" size of 110 MB. The 110 MB limit is set mostly 
> to allow installations from a 128 MB USB-stick (hd-media image + netinst 
> iso together must be smaller than the capacity of the USB stick).
> As we feel it is important to have the graphical installer available on 
> all CD types, we propose to relax the current size limit. This will mean 
> that the default image for USB installations will become 256 MB instead 
> of 128 MB.

I see g-i as an option to d-i  ( not a replace of it )

Keep the current d-i images as they exist
and add extra images for g-i.

That way we can keep d-i on 128Mb USB-stick and allow g-i to demand 256 Mb.

> We'd prefer not let the netinst grow unnecessarily, but relaxing the size 
> limit means that we could also for example include both initramfs-tools 
> and yaird (current netinst images only have one, not both).

For the netinst ISO goes the same:
 add g-i images to the existing d-i images.

I have to admit that I fear to touch the build system of debian-installer.

> We will probably also have to make space on the full CDs to prevent 
> packages needed for the basic tasks overflowing to the 2nd CD.
> The best solution seems to be to move the installation guide to the 2nd 
> CD, possibly keeping only the English version on the first CD. This will 
> probably be needed anyway because of the added space taken by the new 
> translations we'll have for Etch.
> This will of course mean some changes in debian-cd and the README included 
> on the CD.

The full CD will most likely match the netinst-gui.iso.
Will they both allow an 'install' or is it only 'install-gui'?


> Cheers,
> FJP
> 
> P.S. I've also updated the status page for G-I; please check:
>  http://wiki.debian.org/DebianInstaller/GUIToDo

Updated with a request for the daily-build script.


Cheers
Geert Stappers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#367093: Re : Bug#367093 closed by Geert Stappers <[EMAIL PROTECTED]> (Bug#367093: Etch/Sid is installable on amd64)

[Wasfi JAOUAD]

Well, it's ok with the i386 version of the installer, but the AMD64 one still 
says : 

   !! install the base system
   Cannot install the base system
The installer connot figure out how to install the base system. No installable 
CD-ROM 
was found and no valid miroor was configured.
(with a scary red background ;-)

Or you mean the fix will automatically be appiled to AMD64 d-i ?
Actually Joey's fix dealt with not finding packages inside ISOs, here the ISO 
itself
was not found.. hopefully it fixes both..

Full logs of a try with latest binaries from amd64.debian.net are attached.

W.J.
- Message d'origine 
De : Debian Bug Tracking System <[EMAIL PROTECTED]>
À : Wasfi JAOUAD <[EMAIL PROTECTED]>
Envoyé le : Dimanche, 14 Mai 2006, 8h48mn 04s
Objet : Bug#367093 closed by Geert Stappers <[EMAIL PROTECTED]> (Bug#367093: 
Etch/Sid is installable on amd64)

This is an automatic notification regarding your Bug report
#367093: Etch/Sid not installable on amd64,
which was filed against the installation-reports package.

It has been closed by Geert Stappers <[EMAIL PROTECTED]>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact Geert Stappers <[EMAIL PROTECTED]> by replying
to this email.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




-Le message joint suit.-

Date: Sun, 14 May 2006 08:32:22 +0200
From: Geert Stappers <[EMAIL PROTECTED]>
Subject: Bug#367093: Etch/Sid is installable on amd64


On Sun, May 14, 2006 at 06:22:37AM +, Wasfi JAOUAD wrote:
> Joey Hess wrote :
> >> It's this one :
> >> http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz
> >> right ?
> >
> > You'll need to wait until this evening's build to get the fix I
> > uploaded..
>
> Waited. Downloaded.
>
> You're the man Joey. Thanks.
> Debian_user++;
>
> Resolved.
>
> W. J.
>

That is good to hear^Wread.

Have fun with  your Debian GNU/Linux computer system!


Cheers
Geert Stappers





amd64-08-Apr-2006.7z
Description: Binary data

Re: Proposal for integration of the graphical installer

[Davide Viti]

On Sat, May 13, 2006 at 11:23:52PM +0200, Frans Pop wrote:
> - Using the font tarballs is OK for the short run, but now that we
>   are integrating g-i we really need to switch to using udebs.
>   This should be finished before the Etch RC1 release.

I'll try to come up with more detail asap.
Basically we cannot use dejavu as default fonts but we need to 
stick to freefont; both dejavu and freefont exist as an udeb,
we might just need to strip away some glyphs to reduce the size.

AFAICT the only package that needs an official udeb is ttf-thai-tlwg,
but I know Christian is ready to help with this.

Regards,
Davide


signature.asc
Description: Digital signature

Re: [G-I] Udeb dependency resolution issue resolved!

[Davide Viti]

Hey Frans,

On Sat, May 13, 2006 at 05:04:24AM +0200, Frans Pop wrote:
> Today I've been able to upload cdebconf with updated dependencies and 
> built the graphical installer *without any localudebs* :-)
> This means we've finally arrived at the point where we can integrate the 
> graphical installer into trunk.

excellent news, really!
as Attilio pointed out, next milestone should be switching to the latest libs,
and things are already moving in the right direction:

- directfb backend has been integrated in the main CVS repository and the first
  official release containing it, 2.9.0,  is out (is an unstable release, see 
[1])

- as far as fonts are concerned, current g-i covers all the languages supported 
by
  the installer, including the latest Thai and Dzongkha. Consistency is not at 
its
  best; I've put alot of effort trying to switch g-i as to use Dejavu fonts as 
default
  rather than freefont but that's another area where we've taken the current 
libs to
  their limits. I've managed to get this working out of the box using an 
unofficial
  iso based on the latest libs, but using the official libs, debconf just dies 
(see [2])

Ciao,
Davide

[1] http://www.gtk.org/
[2] http://lists.debian.org/debian-boot/2006/05/msg00256.html



signature.asc
Description: Digital signature