howto join
-- Lucifer
i mixed up with steps
hi , i am new to debian installer , read some document and article about debian installer but i can't under stand the steps to use debian installer for a CDD. can any one guide me please.
Re: The future of the D-I team
On Thu, Feb 26, 2009 at 09:49:58PM +0100, Christian Perrier wrote: Now that the lenny release is over, I think it's time for all of us to gather and discuss what the D-I team currently is and what should be done for the lenny-squeeze release cycle (not technically speaking but first more on organisational issues). If we organize something called a team meeting to talk about this, who would attend? If it's at a feasible time for me, sure. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Daily build failures
On Thu, Feb 19, 2009 at 06:58:35AM +0100, Christian Perrier wrote: My daily builds are failing since the release: [...] reducing libnewt.so.0.52 /usr/lib//libnewt.so.0.52 73216L ./tmp/netboot/treeBFD: BFD (GNU Binutils for Debian) 2.19.1 internal error, aborting at ../../bfd/elf.c line 4650 in assign_file_positions_for_non_load_sections BFD: Please report this bug. Looks like this should be reported to the binutils maintainer. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 517114 to auto-install
# Automatically generated email from bts, devscripts version 2.10.35lenny3 reassign 517114 auto-install -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 517114 to auto-install
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 reassign 517114 auto-install Bug#517114: please enable the prompt to enter preseeding url Bug reassigned from package `debian-installer' to `auto-install'. 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 debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517364: installation-reports: System not bootable after install
Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: Debian Lenny 5.0 (both AMD64 or i386) Date: 2008-02-25 Machine: Intel D945GCLF2 (Atom330) Partitions: sda : sda1 78GB type 0xFD (linux raid autodetect) sda2 1GB type 0x83 (swap) sdb : sdb1 78GB type 0xFD (linux raid autodetect) sdb2 1GB type 0x83 (swap) Comments/Problems: When the root filesystem is installed on a RAID1 MD device (without a /boot partition), by default the installer does not mark the components devices (let's says sda1 and sdb1) as bootable in the partition table. Grub is then successfully installed in the MBR of sda but some really really stupid BIOS (tested on at least 2 different Intel motherboards) refuse to consider the disk as bootable unles at least 1 partition is marked to be bootable. In fact, no matter which partition is set bootable, the bios just don't try to run the MBR loader if there is no partition marked to be bootable. For the moment, one solution is to boot the installation CD in rescue mode just after install, run cfdisk in a shell and set the Boot flag on the first partition of the first drive (let's say sda1). This solves the problem. reinstalling grub in the MBR is not mandatory. It would be VERY useful to add a small warning at Grub installation time Warning : The disk where your are atempting to install grub has no bootable partitions. In this particular situation, some (uncommon) systems will refuse to run the bootloader even if it's correctly installed. To avoid this problem, you need to toogle the boot flag of one partition on the concerned drive. Would you like to run the partition editor now ? (default choice=No) -- About hardware report and install report. Sorry but I didn't wrote this bug report on the buggy machine, so the hardware summary was false. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517369: installation-report: Wrong 30_otheros configuration file for grub2
Package: installation-reports Version: 2.38 Severity: normal -- Package-specific info: Boot method: DVD Image version: Debian GNU/Linux 5.0.0 Lenny - Official i386 DVD Binary-1 20090214-16:54 Date: 23 feb 2009 Machine: Assembled PC Partitions: df -Tl will do; the raw partition table is preferred FilesystemTypeblocchi di 1K Usati Disponib. Uso% Montato su /dev/hdb3 ext318508460 2894292 14673964 17% / tmpfstmpfs 193244 0193244 0% /lib/init/rw udev tmpfs 10240 160 10080 2% /dev tmpfstmpfs 193244 0193244 0% /dev/shm Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: The partition number used for the command set root=(hd0, x) in 30_otheros file complies with the old grub configuration (starting from 0) but the grub2 configuration requires starting from 1, so I had to change all the entries in that file with x+1. Cheers, Andrea -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux lenny 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] [1106:0305] (rev 03) lspci -knn: 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] [1106:8305] lspci -knn: 00:07.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 40) lspci -knn: Kernel driver in use: parport_pc lspci -knn: Kernel modules: parport_pc lspci -knn: 00:07.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) lspci -knn: Kernel driver in use: VIA_IDE lspci -knn: Kernel modules: via82cxxx lspci -knn: 00:07.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 16) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:07.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 16) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:07.4 Bridge [0680]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] [1106:3057] (rev 40) lspci -knn: 00:07.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT82C686 AC97 Audio Controller [1106:3058] (rev 50) lspci -knn: 00:08.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) lspci -knn: Kernel driver in use: 8139too lspci -knn: Kernel modules: 8139too, 8139cp lspci -knn: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:4742] (rev 5c) lsmod: Module Size Used by lsmod: nls_cp437 5504 0 lsmod: ufs63748 0 lsmod: qnx47684 0 lsmod: ntfs 180416 0 lsmod: dm_mod 45384 0 lsmod: md_mod 65940 0 lsmod: xfs 446836 0 lsmod: reiserfs 187008 0 lsmod: jfs 148060 0 lsmod: ext3 103688 1 lsmod: jbd35092 1 ext3 lsmod: vfat8832 0 lsmod: fat39964 1 vfat lsmod: ext2 52744 0 lsmod: mbcache 6656 2 ext3,ext2 lsmod: 8139too20096 0 lsmod: 8139cp 17024 0 lsmod: mii 4864 2 8139too,8139cp lsmod: nls_utf81664 6 lsmod: isofs 27684 0 lsmod: nls_base6528 7 nls_cp437,ntfs,jfs,vfat,fat,nls_utf8,isofs lsmod: zlib_inflate 13952 1 isofs lsmod: ide_generic 2432 0 [permanent] lsmod: sd_mod 21904 0 lsmod: thermal_sys10656 0 lsmod: usb_storage75328 0 lsmod: scsi_mod 129420 2
Please unblock glib2.0 and gtk+2.0
Hi, glib2.0 and gtk+2.0 should be ready to migrate to squeeze today. Since they contain udebs, they need manual handling. Could you please unblock them? After that, the road is open for GTK+ 2.14 in unstable and GTK+ 2.12.12 in lenny, as discussed before. Cheers, -- .''`. Debian 5.0 Lenny has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `-me that if you don't install Lenny, he'd melt your brain. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#514055: debian still not working on PS3
* Geoff Levand geoffrey.lev...@am.sony.com [2009-02-26 09:43]: I just tried the latest testing CD (2000.02.12), and it still fails with the same problem I reported for Lenny DI RC2. The installer fails on mounting the CD-ROM. The PS3 ps3_gelic network and PS3 ps3rom and ps3disk storage drivers are missing from the installer's initrd. I entered a bug report that went unanswered here: The short answer is that there isn't really an active powerpc porter working on the installer. That's why your bug report is unanswered. I'm copying Wouter Verhelst who indicated some interest in helping with the powerpc port. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517439: installation-report: successful install
Package: installation-reports Version: 2.38 Severity: wishlist -- Package-specific info: Boot method: usb key Image version: net install amd64 business-card lenny (was testing) Date: 2009 01 31 Machine: Toshiba Tecra R10K Partitions: Disk /dev/sda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x5130cb2e Device Boot Start End Blocks Id System /dev/sda1 * 1 23330 187398193+ 83 Linux /dev/sda2 23331 24321 7960207+ 5 Extended /dev/sda5 23331 24321 7960176 82 Linux swap / Solaris Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: All ok. Very impressive hardware autodetection, compared to my first debian install 10 years ago. Wifi did not work out of the box. This is unavoidable, since the chip needs a closed-source external firmware and a newer 2.6.28 kernel with the iwlagn driver. I had to manually select the intel driver in xorg.conf, VESA was the default. It is a safe choice for the moment, since the intel driver (hand-compiled 2.6.28.3 kernel, xf86-video-intel server module 2.3.2) crashed several times the whole computer using 3D softwares like oolite or wine-grimfandango. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20090126-22:56 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux pegase 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: Kernel driver in use: e1000e lspci -knn: Kernel modules: e1000e lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
Bug#517471: ability to configure the random key encryption of tmp partitions during installaion
package: debian-installer severity: wishlist It is possible to encrypt loop-aes and dm-crypt tmp (like /tmp or /var/tmp) partitions with a random key at boot time, but the Debian installer will not configure this. The installer will only configure swap partitions like that. Creating a random key at each boot is more secure than using the same one, since then data will be securely deleted when the key is deleted, which normally happens at shutdown. (For exceptions, read about cold boot attacks.) Random keys also spare the user the trouble of having to type a password at each boot and worrying about the security of the key and the password. A possible workaround is to configure the would-be tmp partitions as swap partitions during the installation process, and manually configure them to be tmp partitions after the first boot of the new Debian system. An fstab entry for a loop-aes encrypted swap partition, with a new random key at each boot, looks like this. /dev/sda6 noneswap sw,loop=/dev/loop0,encryption=serpent256 0 0 An fstab entry for a loop-aes encrypted tmp partition, with a new random key at each boot, looks like this. /dev/sda7 /tmpext2 defaults,loop=/dev/loop1,encryption=serpent256,phash=random/1777 0 0 More detailed documentation about loop-aes can be found in the losetup manual page. Similar functionality is available for dm-crypt. A crypttab entry for a dm-crypt encrypted swap partition, with a new random key at each boot, looks like this. sda7_crypt /dev/sda6 /dev/random cipher=serpent-cbc-essiv:sha256,size=256,swap Here is the fstab entry. /dev/mapper/sda6_crypt none swapsw0 0 A crypttab entry for a dm-crypt encrypted tmp partition, with a new random key at each boot, looks like this. sda7_crypt /dev/sda7 /dev/random cipher=serpent-cbc-essiv:sha256,size=256,tmp=ext2 Here is the fstab entry. /dev/mapper/sda7_crypt /tmp ext2defaults0 0 More detailed information about dm-crypt can be found in the manual pages cryptsetup and crypttab. Personally, I prefer to use loop-aes for this application for the following reasons: * It has a multi-key mode in which it uses 64 keys plus an additional 65th key, which makes it more secure. * It seems to be faster during boot time. Dm-crypt seems to take a long time creating the ext2 partitions. * dm-crypt might be more supported by Linux, but it is just a tmp partition, so if a kernel upgrade breaks loop-aes, there will be no data loss. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517491: Squeeze: installation-reports
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 28.02.2009 Machine: Mboard - Asus M2V Processor: AMD Athlon 64 X2 Memory: 2 gb Partitions: df -Tl will do; the raw partition table is preferred Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: hard drives not detected! [hda, hdb sda (SATA)]. In Lenny - OK! Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- С уважением, Владимир Онищенко E-Mail: vlanon(at)mail(dot)ru -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
