Bug#869844: base-installer: debian 9.1.0 live iso - base-installer tar process copying live system failed, no space left on device
On Thu, Jul 27, 2017 at 8:12 AM, Steve McIntyrewrote: > On Thu, Jul 27, 2017 at 06:55:46AM +0700, Dhanar Adi Dewandaru wrote: > >Package: base-installer > >Severity: important > > > >Dear Maintainer, > > > >I hope i file this bug against the correct package. > > > >When installing debian using live iso, base-installer failed while > copying live system with error message tar no space left on the device. > This cause the installation to fail. > >This seems to be similar to #748579. But i think it is not since i am > using the original iso without netbootin. > > > >I am using debian-live-9.1.0-amd64-mate+nonfree.iso (the SHA1SUM has > been checked OK). > >When booting the iso, i choose Debian Installer option on the boot menu > (i did not go the live desktop). > >This issue did not exist on the previous version of the live iso > (debian-live-9.0.1-amd64-mate+nonfree.iso). > > > >I tested this a couple of times on VirtualBox and I was able to reproduce > the issue every time (sorry, i do not have any spare PC to test it on real > hardware). > >Please see the following screenshot for more details. > > > >https://pasteboard.co/GCNcTdW.png > >https://pasteboard.co/GCNd67b.png > > > >Hopefully, this bug can be fixed soon because it makes it impossible to > install debian from live iso. > > There may not be a bug here. What setup did you use for the partitions > and filesystems on your machine? > > -- > Steve McIntyre, Cambridge, UK. > st...@einval.com > We don't need no education. > We don't need no thought control. > I choose "Guided - use entire disk" and "All files in one partition" See the overview here: https://pasteboard.co/GCO8z87.png Yes, i think it may be a bug in the base-installer or something else causing base-installer to fail.
Bug#869844: base-installer: debian 9.1.0 live iso - base-installer tar process copying live system failed, no space left on device
On Thu, Jul 27, 2017 at 06:55:46AM +0700, Dhanar Adi Dewandaru wrote: >Package: base-installer >Severity: important > >Dear Maintainer, > >I hope i file this bug against the correct package. > >When installing debian using live iso, base-installer failed while copying >live system with error message tar no space left on the device. This cause the >installation to fail. >This seems to be similar to #748579. But i think it is not since i am using >the original iso without netbootin. > >I am using debian-live-9.1.0-amd64-mate+nonfree.iso (the SHA1SUM has been >checked OK). >When booting the iso, i choose Debian Installer option on the boot menu (i did >not go the live desktop). >This issue did not exist on the previous version of the live iso >(debian-live-9.0.1-amd64-mate+nonfree.iso). > >I tested this a couple of times on VirtualBox and I was able to reproduce the >issue every time (sorry, i do not have any spare PC to test it on real >hardware). >Please see the following screenshot for more details. > >https://pasteboard.co/GCNcTdW.png >https://pasteboard.co/GCNd67b.png > >Hopefully, this bug can be fixed soon because it makes it impossible to >install debian from live iso. There may not be a bug here. What setup did you use for the partitions and filesystems on your machine? -- Steve McIntyre, Cambridge, UK.st...@einval.com We don't need no education. We don't need no thought control.
Bug#869844: base-installer: debian 9.1.0 live iso - base-installer tar process copying live system failed, no space left on device
Package: base-installer Severity: important Dear Maintainer, I hope i file this bug against the correct package. When installing debian using live iso, base-installer failed while copying live system with error message tar no space left on the device. This cause the installation to fail. This seems to be similar to #748579. But i think it is not since i am using the original iso without netbootin. I am using debian-live-9.1.0-amd64-mate+nonfree.iso (the SHA1SUM has been checked OK). When booting the iso, i choose Debian Installer option on the boot menu (i did not go the live desktop). This issue did not exist on the previous version of the live iso (debian-live-9.0.1-amd64-mate+nonfree.iso). I tested this a couple of times on VirtualBox and I was able to reproduce the issue every time (sorry, i do not have any spare PC to test it on real hardware). Please see the following screenshot for more details. https://pasteboard.co/GCNcTdW.png https://pasteboard.co/GCNd67b.png Hopefully, this bug can be fixed soon because it makes it impossible to install debian from live iso. Thank you. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#823020: marked as done (installation-reports: problems with u-boot and ext4)
Your message dated Wed, 26 Jul 2017 15:44:54 -0400 with message-id <87h8xz6kzt@aikidev.net> and subject line Re: Bug#823020: Bug#823500: cannot boot from ext4 has caused the Debian Bug report #823020, regarding installation-reports: problems with u-boot and ext4 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 ow...@bugs.debian.org immediately.) -- 823020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: important X-Debbugs-Cc: ma...@denx.de I've done several installs now on both a Wandboard Solo and an Novena board, and u-boot has problems reading the the dtbs subdirectory needed to load the device-trees, and fails to boot after an otherwise successful install. The problem seems to *mostly* be with subdirectories, and since the device-tree files in stored in /boot/dtbs/${version}/${device}.dtb. Installs done with jessie and the same u-boot version work fine. Also, recreating the ext4 filesystem with mkfs.ext4 works fine, even with, as far as I can tell, identical filesytem flags. I suspect other boards using u-boot and ext4 filesystem will also have similar problems. live well, vagrant -- Package-specific info: Boot method: network Image version: https://d-i.debian.org/daily-images/armhf/20160426-00:33/netboot/ Date: 20160426 Machine: Wandboard Solo Partitions: sfdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 3.7 GiB, 3980394496 bytes, 7774208 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 Disklabel type: dos Disk identifier: 0xcd2ecfc6 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 * 2048 976895 974848 476M 83 Linux /dev/mmcblk0p2 976896 4882431 3905536 1.9G 83 Linux /dev/mmcblk0p3 4882432 5859327 976896 477M 82 Linux swap / Solaris /dev/mmcblk0p4 5859328 6883327 1024000 500M 83 Linux Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[ ] Comments/Problems: Network boot and SD card boot worked fine, but initial boot failed due to issues with u-boot being unable to consistantly read the ext4 filesystem. -- 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="9 (stretch) - installer build 20160426-00:13" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux wbs20160426-18 4.5.0-1-armmp #1 SMP Debian 4.5.1-1 (2016-04-14) armv7l GNU/Linux usb-list: usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 4.5.0-1-armmp ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub lsmod: Module Size Used by lsmod: dm_mod 98863 0 lsmod: md_mod118279 0 lsmod: jfs 174600 0 lsmod: btrfs1091195 0 lsmod: xor 4782 1 btrfs lsmod: zlib_deflate 20354 1 btrfs lsmod: raid6_pq 87885 1 btrfs lsmod: vfat 10249 0 lsmod: fat56693 1 vfat lsmod: ext4 559642 2 lsmod: crc16 1274 1 ext4 lsmod: mbcache 9488 1 ext4 lsmod: jbd2 95959 1 ext4 lsmod: crc32c_generic 1862 5 lsmod: usb_storage45523 0 lsmod: scsi_mod 188696 1 usb_storage lsmod: ci_hdrc_imx 6936 0 lsmod: ci_hdrc34941 1 ci_hdrc_imx lsmod: ehci_hcd 64352 1 ci_hdrc lsmod: extcon 10462 1 ci_hdrc lsmod: udc_core9769
Bug#868869: debian-installer should not recommend to change password periodically (and more)
On Wed 26 Jul 2017 at 17:00:12 +0100, Miguel Figueiredo wrote: > On 24-07-2017 11:38, Hideki Yamane wrote: > >Hi, > > > >On Sun, 23 Jul 2017 10:49:53 +0200 > >Philipp Kernwrote: > >>It seems to me that today at least the guidance of mixed > >>character classes still makes some sense as a default, to avoid the most > >>obvious blunder of just using a simple dictionary word and be > >>compromised over SSH because password authentication is turned on. > > > > Okay, I agree with it. > > > >>And change it to make brute force attacks harder. > > > > But it also makes administrator to remember it harder as its trade-off... > > (and they maybe choose easy password as a result). It's a not good idea > > to suggests to change root password periodically, IMO. It's not a best > > practice. > > > > 1) Add password check feature whether password has an enough strength > > like RHEL's anaconda or SUSE's installer. > > 2) Drop suggestion root password change periodically from message. > > > > is better. > > We have libpam-passwqc on the archive, which it's a "Password > quality-control PAM module". > I think it addresses the point of checking the password strength. It possibly does, but isn't it more suitable as a solution to #854653 or #364526 rather than this bug (changing a password at periodic intervals, no matter how strong it is)? -- Brian.
Bug#868869: debian-installer should not recommend to change password periodically (and more)
On 24-07-2017 11:38, Hideki Yamane wrote: Hi, On Sun, 23 Jul 2017 10:49:53 +0200 Philipp Kernwrote: It seems to me that today at least the guidance of mixed character classes still makes some sense as a default, to avoid the most obvious blunder of just using a simple dictionary word and be compromised over SSH because password authentication is turned on. Okay, I agree with it. And change it to make brute force attacks harder. But it also makes administrator to remember it harder as its trade-off... (and they maybe choose easy password as a result). It's a not good idea to suggests to change root password periodically, IMO. It's not a best practice. 1) Add password check feature whether password has an enough strength like RHEL's anaconda or SUSE's installer. 2) Drop suggestion root password change periodically from message. is better. We have libpam-passwqc on the archive, which it's a "Password quality-control PAM module". I think it addresses the point of checking the password strength.
Bug#869513: console-setup changes remain only till next reboot
forcemerge 857132 861454 863630 869513 thanks On Tue, Jul 25, 2017 at 10:47:18PM +0200, Harry Haller wrote: > > Yes, setupcon works - (but only until the next boot too). It seems this bug is another reappearance of a known problem. Unfortunately, some smart people have tried to find the cause and have failed. The bug shows itself only when the system uses systemd. For now you have two options: 1. you can include the command 'setupcon' in some script, for example in .(bash_)profile so that it is executed when you login or 2. you can remove systemd from your system, http://without-systemd.org. Anton Zinoviev
Processed: Re: Bug#869513: console-setup changes remain only till next reboot
Processing commands for cont...@bugs.debian.org: > forcemerge 857132 861454 863630 869513 Bug #857132 [console-setup] console-setup (again) stopped to apply font at startup Bug #861454 [console-setup] console-setup: Have to use setupcon at every boot Bug #863630 [console-setup] console-setup.service doesn't affect tty consoles Bug #869513 [console-setup] console-setup changes remain only till next reboot Severity set to 'important' from 'normal' Marked as found in versions console-setup/1.160 and console-setup/1.163. Added tag(s) d-i. Bug #863630 [console-setup] console-setup.service doesn't affect tty consoles Marked as found in versions console-setup/1.164. Marked as found in versions console-setup/1.164. Marked as found in versions console-setup/1.164. Bug #861454 [console-setup] console-setup: Have to use setupcon at every boot Merged 857132 861454 863630 869513 > thanks Stopping processing here. Please contact me if you need assistance. -- 857132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857132 861454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861454 863630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863630 869513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868869: debian-installer should not recommend to change password periodically (and more)
On Tue, Jul 25, 2017 at 11:14:42PM +0100, Brian Potkin wrote: > It is a nice debating point but I am inclined to go along with this > assessment when it comes to the installer. Nobody takes any notice > of the advice anyway and there are far more important things to > attend to. I'm not sure that's true. Bad advice in an installer is not a good idea. I've always been unhappy about having it there, and as that previous bugreport shows, so were you. In addition, if we're going to change this recommendation, then now (at the beginning of a new release cycle) is the best time for doing so. I'd be inclined to agree it should be removed, but I'd be happy to follow the consensus here. -- Could you people please use IRC like normal people?!? -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008 Hacklab
Bug#868869: debian-installer should not recommend to change password periodically (and more)
On Tue, Jul 25, 2017 at 11:22:19PM +0200, Philipp Kern wrote: > On 07/24/2017 12:38 PM, Hideki Yamane wrote: > > But it also makes administrator to remember it harder as its trade-off... > > (and they maybe choose easy password as a result). It's a not good idea > > to suggests to change root password periodically, IMO. It's not a best > > practice. > > I'd say it's one of two things: If it's easy, make sure to change it > periodically. If it's hard enough to withstand brute-force, you don't > need to. The problem with regular-change policies is that it *encourages* easy passwords, since if you want to remember something generated by "pwgen -s 15" or some such, it will take you quite a while to do so, and by that time it may be time to renew it again. -- Could you people please use IRC like normal people?!? -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008 Hacklab