Your message dated Fri, 22 Nov 2024 14:01:28 +0100 with message-id <[email protected]> and subject line Re: #254727 Creates swap even when there is already one has caused the Debian Bug report #254727, regarding Creates swap even when there is already one to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 254727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254727 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: installation-reports INSTALL REPORT Debian-installer-version: 6 Jun 2004 (Beta4 image) uname -a: Linux mulder 2.4.25-1-386 #2 Wed Apr 14 19:38:08 EST 2004 i586 GNU/Linux Date: 6 Jun 2004 Method: Hard disk boot (I downloaded the cd image and booted with the vmlinuz image, as described in the Installation-HOWTO) Machine: HP Vectra Processor: Pentium 166 MHz Memory: 112 MB Root Device: IDE /dev/hdb2 Root Size/partition table: Where can I find the partition table? Output of lspci and lspci -n: ---lspci: 0000:00:00.0 Host bridge: Intel Corp. 430HX - 82439HX TXC [Triton II] (rev 03) 0000:00:06.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 0000:00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 23) 0000:00:0d.0 VGA compatible controller: S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] (rev 14) 0000:00:0f.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01) 0000:00:0f.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] 0000:00:0f.2 USB Controller: Intel Corp. 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) ---lspci -n: 0000:00:00.0 Class 0600: 8086:1250 (rev 03) 0000:00:06.0 Class 0200: 10b7:9050 0000:00:0c.0 Class 0100: 1000:0001 (rev 23) 0000:00:0d.0 Class 0300: 5333:8901 (rev 14) 0000:00:0f.0 Class 0601: 8086:7000 (rev 01) 0000:00:0f.1 Class 0101: 8086:7010 0000:00:0f.2 Class 0c03: 8086:7020 (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked: [E] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems: [O] Mount partitions: [O] Install base system: [O] Install boot loader: [E] Reboot: [O] Comments/Problems: The initial boot didn't work. The installation manual said that I had to type this in lilo.conf: image=/boot/newinstall/vmlinuz label=newinstall initrd=/boot/newinstall/initrd.gz append="devfs=mount,dall" It said that a 'root=' line would be ignored. But when I booted, it said that it couldn't open the root file system. I found that I had to append 'root=/dev/ram' before booting the image; this worked well. ----------- I was also not really happy with the automatic partioning. I already had some partions, but I wanted to let the installer partition the drive automatically, so delete the partitions and let the installer partition the free space. However, I couldn't delete the partition with the downloaded cd-image (of course). I deleted the other partitions, but the installer didn't use the space after the cd-image (where formerly my swap partition resided). Instead, it created a swap partition in the free space _before_ the partition with the cd-image. I still wanted to use the space after it, so I created a swap partition in that space and let the installer try it again. But it made a second swap partition! That's why I'm not really happy with it... ----------- The bootloader installed well, but it didn't include Windows NT on my first disk (not that I use it very often... :) ). I had to do this manually. Maybe this is because I had LILO before I started with the installation, which resided before the WinNT bootloader, so that the installer couldn't recognize it. ----------- I hope this is useful. Frank Mulder
--- End Message ---
--- Begin Message ---> I've noticed the same behavior. Also (as you noticed as well), if there > already is a swap partition on the drive to begin with, automatic > partitioning will still create a new swap partition instead of using the > existing one. Shortly this has infact been trimmed even more, to not touch existing swap partitions by default, to not break a hibernated parallel installation. So, not a bug, but a feature for multi-OS installations / machines. Closing this report. -- Holger Wansing <[email protected]> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
