Bug#757182: debian-installer: Please provide a warning about BTRFS
On 6 August 2014 03:46, Russell Coker wrote: > Package: debian-installer > Severity: normal > > http://www.spinics.net/lists/linux-btrfs/msg36461.html > > BTRFS has some issues that can cause system lockups, filesystem deadlocks that > prevent writing to disk, and other problems. After some discussion on the > BTRFS mailing list (see the above URL for the archive) the consensus seems to > be that we should have a warning. BTRFS isn't at the stage where someone with > little knowledge of it can just use it. To have it work reliably the sysadmin > needs to know more about it than for other filesystems. > I disagree and the assessment here is unjust. By default we offer ext4, [ with lvm2 [ with cryptsetup LUKS ] ]. mdadm raid needs additional setup. For none of the above, we show any warnings. In the manual partitioning, again ext4 is the default. To get to BTRFS, one needs to change from ext4 to it, which imho there is a sufficient amount of hoops to jump through. I wouldn't want to loose ability to install on to btrfs, since developers have need to have working installers with btrfs. >From UX perspective, users don't read warnings =) When people ask me if they should use btrfs, or if btrfs is ready my reply is usually "if you have to ask, you shouldn't use it. Instead study and benchmark it to know for sure what you are getting into with your workload." ext4 is Debian's and Ubuntu's default filesystem for upcoming releases. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/canbhlujvfc4glrrx_aqf5iyggzntm-vol1ky7-2fdxqebch...@mail.gmail.com
Bug#757220: d-i manual: update kernelversions for Jessie
Package: installation-guide Tags: patch Hi, there are entities for kernel versions in the d-i manual, which need to be updated. Patch attached, while I' unsure about the kfreebsd version: kfreebsd-image package version in jessie is 10 currently, but the jessie-alpha1 installer still installs kfreebsd-9. What will be in Jessie when releasing? Holger -- Holger Wansing Index: build/arch-options/linux === --- build/arch-options/linux (Revision 69224) +++ build/arch-options/linux (Arbeitskopie) @@ -4,5 +4,5 @@ archspec="$archspec;linux-any" arch_kernel="Linux" arch_parttype="Linux" -kernelversion="3.2.0" +kernelversion="3.16.0" kernelpackage="linux-image" Index: build/arch-options/hurd === --- build/arch-options/hurd (Revision 69224) +++ build/arch-options/hurd (Arbeitskopie) @@ -4,5 +4,5 @@ archspec="$archspec;hurd-any" arch_kernel="Hurd" arch_parttype="Linux" -kernelversion="1.3.99" +kernelversion="1.4" kernelpackage="gnumach" Index: build/arch-options/kfreebsd === --- build/arch-options/kfreebsd (Revision 69224) +++ build/arch-options/kfreebsd (Arbeitskopie) @@ -4,5 +4,5 @@ archspec="$archspec;kfreebsd-any" arch_kernel="kFreeBSD" arch_parttype="FreeBSD" -kernelversion="8" +kernelversion="9" kernelpackage="kfreebsd-image"
Bug#757220: d-i manual: update kernelversions for Jessie
Holger Wansing (2014-08-06): > Package: installation-guide > Tags: patch > > > Hi, > > there are entities for kernel versions in the d-i manual, which need to > be updated. > > Patch attached, while I' unsure about the kfreebsd version: > kfreebsd-image package version in jessie is 10 currently, but the > jessie-alpha1 installer still installs kfreebsd-9. > What will be in Jessie when releasing? There was some discussion lately on debian-bsd@ (Cc'd) about kernel-related things, including which version would be released upstream just before/after the freeze. The 3-component Linux version was an artifact (and we're at 3.2.60 now), I'd rather mention "3.16" which is going to be the basis, and basically what matters. We're likely ending up with a 3.16.x version, with a high, unknown, moving x. :) Mraw, KiBi. > Holger > > > > -- > Holger Wansing > Index: build/arch-options/linux > === > --- build/arch-options/linux (Revision 69224) > +++ build/arch-options/linux (Arbeitskopie) > @@ -4,5 +4,5 @@ > archspec="$archspec;linux-any" > arch_kernel="Linux" > arch_parttype="Linux" > -kernelversion="3.2.0" > +kernelversion="3.16.0" > kernelpackage="linux-image" > Index: build/arch-options/hurd > === > --- build/arch-options/hurd (Revision 69224) > +++ build/arch-options/hurd (Arbeitskopie) > @@ -4,5 +4,5 @@ > archspec="$archspec;hurd-any" > arch_kernel="Hurd" > arch_parttype="Linux" > -kernelversion="1.3.99" > +kernelversion="1.4" > kernelpackage="gnumach" > Index: build/arch-options/kfreebsd > === > --- build/arch-options/kfreebsd (Revision 69224) > +++ build/arch-options/kfreebsd (Arbeitskopie) > @@ -4,5 +4,5 @@ > archspec="$archspec;kfreebsd-any" > arch_kernel="kFreeBSD" > arch_parttype="FreeBSD" > -kernelversion="8" > +kernelversion="9" > kernelpackage="kfreebsd-image" signature.asc Description: Digital signature
Re: Bug#739011: debian-installer: broken monospace font in g-i
Cyril Brulebois (2014-04-05): > Cyril Brulebois (2014-02-16): > > I've tried rebuilding the udeb, adding that extra directory (taken on > > the host), and fonts are indeed back to normal, and the extra vertical > > scroll bar goes away. > > Ping? Ping again. Mraw, KiBi. signature.asc Description: Digital signature
Bug#757244: installation-reports: No separated /boot filesystem
Package: installation-reports Severity: normal Dear Maintainer, This week I installed two similar wheezy system. I have two RAID1 arrays. A small 300 MB md0 for /boot and a 80 GB md1 for LVM with usual filesystems (root, usr, var and so on). I both cases I marked /dev/md0 as ext4 /boot. However the installer forgot it after mkfs. It was not mounted during install as well as it was missing from fstab. The kernel and grub files silently went to root filesystem. I had to copy content of /boot to the manually mounted /dev/md0 and to fix fstab. Gabor -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux 7.1.0 "Wheezy" - Official i386 NETINST Binary-1 20130615-21:53 Date: Machine: General server with Tomcat I7210 motherboard Partitions: # df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on rootfsrootfs 494912 145064349848 30% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs51436260 51176 1% /run /dev/mapper/vgt5-root xfs 494912 145064349848 30% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 102860 0102860 0% /run/shm /dev/mapper/vgt5-home xfs1939456 32956 1906500 2% /home /dev/mapper/vgt5-tmp xfs1939456 32952 1906504 2% /tmp /dev/mapper/vgt5-usr xfs3893248 510124 3383124 14% /usr /dev/mapper/vgt5-usrlocal xfs1939456 40044 1899412 3% /usr/local /dev/mapper/vgt5-var xfs3893248 232252 3660996 6% /var /dev/md0 ext4282279 27586240117 11% /boot # fdisk /dev/sda [...] Disk /dev/sda: 82.3 GB, 82348277760 bytes 255 heads, 63 sectors/track, 10011 cylinders, total 160836480 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00078ee1 Device Boot Start End Blocks Id System /dev/sda1 *2048 585727 291840 fd Linux raid autodetect /dev/sda2 585728 16083558380124928 fd Linux raid autodetect # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sda2[0] sdb2[1] 80059264 blocks super 1.2 [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 291520 blocks super 1.2 [2/2] [UU] unused devices: # 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] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7 (wheezy) - installer build 20130613" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux time5 3.2.0-4-486 #1 Debian 3.2.46-1 i686 GNU/Linux lsmod: Module Size Used by lsmod: fuse 51989 0 lsmod: ufs57656 0 lsmod: qnx4 12992 0 lsmod: ntfs 161748 0 lsmod: reiserfs 167423 0 lsmod: raid0 12776 0 lsmod: efivars17787 0 lsmod: dm_mod 57438 21 lsmod: raid1 26262 2 lsmod: md_mod 81567 3 raid0,raid1 lsmod: xfs 506920 6 lsmod: jfs 131002 0 lsmod: ext4 298331 0 lsmod: crc16 12327 1 ext4 lsmod: jbd2 51626 1 ext4 lsmod: ext3 133894 0 lsmod: jbd42496 1 ext3 lsmod: btrfs 471646 0 lsmod: crc32c 12576 1 lsmod: libcrc32c 12394 1 btrfs lsmod: zlib_deflate 21318 1 btrfs lsmod: vfat 17117 0 lsmod: fat40358 1 vfat lsmod: ext2 49804 0 lsmod: mbcache12938 3 ext2,ext3,ext4 lsmod: e1000 76491 0 lsmod: nls_utf8 12416 0 lsmod: isofs 30544 0 lsmod: usb_storage35245 0 lsmod: sg 21589 0 lsmod: sd_mod 35425 6 lsmod: usbhid 31704 0 lsmod: crc_t10dif 12332 1 sd_mod lsmod: sr_mod 17468 0 lsmod: cdrom 34813 1 sr_mod lsmod: hid60152
Bug#745262: console-setup: Caps lock doesn't take effect on øæå (Danish characters)
On Sun, Apr 20, 2014 at 10:35:23PM +0200, Samuel Thibault wrote: > > Andreas, le Sun 20 Apr 2014 03:30:13 +0200, a écrit : > > > On the Linux console the caps lock key doesn't take effect on the > > Danish characters æøå. With caps lock on they are simply rendered > > æøå (lower case), and not ÆØÅ as one would expect. > > Oops, indeed, it seems the version in Jessie does not properly defines > the ctrll layer for upper cases like it used to in Wheezy. See ckbcomp > dk: > > keycode 39 = +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute > dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute > dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute > dead_doubleacute > > It uses only +U+00e6 +U+00c6, while it should use +U+00c6 +U+00e6 for > ctrll layers. I am unable to reproduce this. What locale do you use? I've tested with LC_ALL=C, LC_ALL=da_DK.utf8 and LC_ALL=da_DK. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140806173902.ga10...@debian.lan
Bug#732696: Re: Bug#732696: os-prober: Fails to detect new package-management Haiku builds
Hello, On 15/07/2014 13:09, Jeroen Oortwijn wrote: > Hello, > > As the writer of the original probe [1], I will try to answer some questions. As the original writer of the original probe (:D), let me comment on this as well... >> TBH if this were mine I'd be inclined to remove most of this logic. The >> prober doesn't do anything with the files other than to look to see if >> they're there. Simply checking the boot loader for 'haiku' would be a >> lot simpler and more robust. > > Yes, but that could give false-positives: When the user has > 'makebootable'd' a partition, but then removed all the files to use it > for something else. The stage 1 bootloader would then still be > present, but not the stage 2 bootloader and the kernel. The partition > would then still be detected as containing an OS. > That's why the probe checks if the stage 1 bootloader, stage 2 > bootloader and kernel are all present. +1 Although OTOH in theory GRUB2 is able to load haiku_loader directly so it might work without makebootable, but nobody knows and uses it, and I never finished multiboot support so it always asks where its boot partition is. > Because David's patch doesn't work anymore, I have created a new > patch. See attached file. > This patch can also be found at my bazaar branch [3]. The resulting > packages can be found in my PPA [4]. I added some sed to add the version info, I noticed at least the windows probe did this, and I saw no reason not to do it. First version was quite naive, but it should now be robust enough to handle future official releases I think, degrading partially with missing hrev and other parts. Some tests here: http://pastebin.com/KsseypUb Currently my menu ends up like: Haiku R1 alpha4 (hrev47000) which is much nicer than just the OS name. Patch against your branch attached, hopefully with correct format, I'm not used to bzr. > I removed the detection of the non package management builds of Haiku, > because I don't think there will be a lot of non-PM versions installed > when the next Haiku release is out. Haiku releases currently are in > alpha phase, so a lot can still be changed. Though from now on all > releases will be package management based. Well the last official release is still alpha4 though, which is non-PM. And I still have a pre-PM partition on at least one machine to compare until I fix several regressions. But I copied the existing probe as a different name and it just works for me. François. # Bazaar merge directive format 2 (Bazaar 0.90) # revision_id: re...@free.fr-20140806181508-8ewigskp1r29yybv # target_branch: http://bazaar.launchpad.net/~idefix/ubuntu/trusty/os-\ # prober/HaikuPM/ # testament_sha1: e5e1cf1cc481796312c43938b873f8ebed3731dd # timestamp: 2014-08-06 20:33:38 +0200 # base_revision_id: oortw...@gmail.com-20140713175637-ciywgnvjqwou9vq9 # # Begin patch === modified file 'os-probes/mounted/x86/83haiku' --- os-probes/mounted/x86/83haiku 2014-07-13 17:56:37 + +++ os-probes/mounted/x86/83haiku 2014-08-06 18:15:08 + @@ -23,11 +23,13 @@ if system="$(item_in_dir "system" "$mpoint")" && packages="$(item_in_dir "packages" "$mpoint/$system")" && item_in_dir -q "haiku_loader-.*\.hpkg" "$mpoint/$system/$packages" && - item_in_dir -q "haiku-.*\.hpkg" "$mpoint/$system/$packages" + rev="$(item_in_dir "haiku-.*\.hpkg" "$mpoint/$system/$packages")" then debug "Stage 2 bootloader and kernel found" label="$(count_next_label Haiku)" - result "$partition:Haiku:$label:chain" + rev="$(echo "$rev" | sed 's/haiku-//;s/^\(r[0-9]\+\)./\U\1\E /;s/ \([a-z]\+[0-9]\+\)[_-]/ \1 /;s/ [a-z]*_\?\(hrev[0-9]\+\)\+-/ (\1) /;s/[^ ]\+.hpkg//;s/ $//')" + long="Haiku $rev" + result "$partition:$long:$label:chain" exit 0 else debug "Stage 2 bootloader and kernel not found: exiting" # Begin bundle IyBCYXphYXIgcmV2aXNpb24gYnVuZGxlIHY0CiMKQlpoOTFBWSZTWfqPiDkABK/flAAwVPv//9di Ug+1AIAIAGAHfeF923EpR6Ta7zqV0SkrrVQkpNAp4TU2U2k9JoyB6mTJkYnpNGgAAMlGiehH oPUJMhiDIDRkYgwQGmgcwBGCYgGATBNGQ0MAmCMTCSaop6nqNHpqYTQ9QNNGm1AD1AAAGgIpE0TE ZGiPSNFHqeT1R+kjQeoPUNNHk1D1AIpIAmRoMk2glNtTIjaj0mIAAZHqECiiUgpsuPBrqYIXh8k3 xEYB1K1q2mJ1QRedIDXWTwLWjVwrkTbajH44vn1Hp4sjTa48jwle+L2sMRBA+X7IY1NrBrgqlIb8 2jDNP4bDy9HWBr/Q1e/4OeTI8/6a3PDCx1dGJ6VNL5DHq3VlQ3nBsm9PbDZx7s+Gt6G97mjd7OvR 19tHwDkmmSNmik2kA7Akcw8MSQmF6ReiIXCmm2ZKDinglC3AudVwQNDnl7SUjFgeYegRyE4CQhqH gtP7nJejk+6uCwrEGmHi0NoJZpt3oC3WhK7dNPMSJiLxVTNxmExk5vX7sxiSghaBtk7RsVXW225g DCoUGPZXslPcDNTIV/omGoT2HI6xPSyegBohgAkPvkAdjaXTSkBAaFr+eu0kW0LWH0vpoMGkDKOw gbpED3vtrGXsHZkeDliOsSzQJgJfOc7W5x5UE1sCaLLpznflTBlaHvHRrrFggAvQv2nk6XTr0iQD p1F1dIWnKgAwGnV46NRY0DY4hMTQJ9Y3l8/w35uWxqbDAT1DiNhtdNMxcJ7h2OmriyYBCjMy5twB 068uHChtuEsNXVODAS+4vLsSq2QW2EcxzWkSzGgu3WXJB2CYjdbhUTQc98ybxNxr00jGyWegNrrL hKTRhSHATFqOV99WzmCuLbSyrN3z1FezZlIoUohMTaJfDAw3qJbVUJn62fTbKOga4CCy+wi1xSci B2DK2azCXiJZkEbmcS24tuZxuvCQyi6UjjQz7rLQyr5GtTK2qsxcNpIpuJzTombIInEtJ4NIBsdF wPwsBt1RzrIFNJME6yAIjGhTFYgHKXhG/dBcKJi0GUUzBjlzZhNTBhVm1BfBBNp5u5sQ3bT4iUtR Zcqa3VMJXAMzgajEo7LLpR2vgw8tvE
Bug#757220: d-i manual: update kernelversions for Jessie
Hi, Cyril Brulebois wrote: > > there are entities for kernel versions in the d-i manual, which need to > > be updated. > > > > Patch attached, while I' unsure about the kfreebsd version: > > kfreebsd-image package version in jessie is 10 currently, but the > > jessie-alpha1 installer still installs kfreebsd-9. > > What will be in Jessie when releasing? > > There was some discussion lately on debian-bsd@ (Cc'd) about > kernel-related things, including which version would be released > upstream just before/after the freeze. > > The 3-component Linux version was an artifact (and we're at 3.2.60 now), > I'd rather mention "3.16" which is going to be the basis, and basically > what matters. We're likely ending up with a 3.16.x version, with a high, > unknown, moving x. :) So I have changed now to Linux 3.16 hurd1.4 kfreebsd9 for the time being. Leaving this bugreport open as a reminder for the real kfreebsd version. Holger -- Holger Wansing -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140806225323.bea11ae4ad12de9e51b9b...@mailbox.org
Bug#757099: d-i manual: update relevant archs for jessie
Holger Wansing (2014-08-05): > Package: installation-guide > Tags: patch > > Hi, > > arch list for d-i manual needs an update (dropped architectures): Speaking of which, I didn't chase yet which revisions triggered this, but the manual is currently failing to build due to missing or broken entities. (Nested comments aren't allowed, so I fixed that locally but then ran into other issues.) Could you please take a look? Mraw, KiBi. signature.asc Description: Digital signature
Bug#757099: d-i manual: update relevant archs for jessie
Cyril Brulebois (2014-08-06): > Speaking of which, I didn't chase yet which revisions triggered this, > but the manual is currently failing to build due to missing or broken > entities. > > (Nested comments aren't allowed, so I fixed that locally but then ran > into other issues.) Thanks for your commit, things look better now (successful build with dpkg-buildpackage at least). The remainder seems to be that jenkins jobs try to build 'eu' which doesn't seem like a supported language. The other Holger is in Cc for that part; svn blame suggests 'eu' has been disabled for a very long time already. Mraw, KiBi. signature.asc Description: Digital signature
Bug#757316: whole disk one big partition is a bad default
Package: debian-installer Please do not make the default for beginners making the whole disk one big partition anymore. Just leave a little free space just in case... You never know when they might need to tune their unmounted file system etc... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvh8olhe@jidanni.org
Bug#757316: whole disk one big partition is a bad default
07.08.2014 10:35, 積丹尼 Dan Jacobson wrote: > Package: debian-installer > > Please do not make the default for beginners making the whole disk one > big partition anymore. > > Just leave a little free space just in case... How much is "a little" ? > You never know when they might need to tune their unmounted file system > etc... So once we do this, people will start filing bugreports saying that debian does not use all their HDD space even if told to do so. I don't think it is right. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53e31f89.1090...@msgid.tls.msk.ru
