Processed: Re: Bug#801832: Package: installation-reports
Processing control commands: > tag -1 moreinfo Bug #801832 [installation-reports] Package: installation-reports Added tag(s) moreinfo. -- 801832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#801832: Package: installation-reports, lspci secundary
On Thu, Oct 15, 2015 at 07:04:50AM +0300, moxalt wrote: > On Thu, 15 Oct 2015 03:20:04 +0200, Gersho de Lock > wrote: > > > > Boot method: USB (4Go) made with LiLiUSB Creator on Windows7 Pro > > Image version: > > http://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/debian-live-8.2.0-amd64-lxde-desktop.iso.torrent > > > > Résultat de lspci -knn (ou lspci -nn) : sorry i have no idea what that is > > > > Comments/Problems: > > > > The installer tells me it can't find the needed files on the CD and can't > > continue, it then send me to the step selection menu > > To find the results of lspci, boot the system with a live CD or USB, open a > terminal, and type lspci -knn. That should tell us more about the hardware. Yes, that will help. The benefit will be in creating / preparing another USB stick from another image. Having the output of `lspci` is secundary to the original problem. > > The installer tells me it can't find the needed files on the CD Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#801832: Package: installation-reports
control: tag -1 moreinfo stop Hello Gersho, Welcome! On Thu, Oct 15, 2015 at 03:20:04AM +0200, Gersho de Lock wrote: > Package: installation-reports [1] > Boot method: USB (4Go) made with LiLiUSB Creator on Windows7 Pro > Image version: > http://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/debian-live-8.2.0-amd64-lxde-desktop.iso.torrent So an .iso on an USB-storage device > Date: 14oct2015 > Machine: Lenovo B590 > Processor:Intel Core i3-3110M 2.4Ghz > Memory: 4Gb > Partitions: 128Gb SSD >c:\ 75Gb (Windows) and 44 Free (for Debian) > > > Installation du système de base : > [O] = OK, [E] = Error (développez plus bas s'il vous plait), [ ] = non essayé > > Initial boot: [O] > Detect network card:[ ] > Configure network: [ ] So no signs of networking related stuff > Detect CD: [X] The reported problem ... > Load installer modules: [ ] > Detect hard drives: [ ] > Partition hard drives: [ ] > Install base system:[ ] > Clock/timezone setup: [O] > User/password setup:[ ] > Install tasks: [ ] > Install boot loader:[ ] > Overall install:[ ] > > Comments/Problems: > > The installer tells me it can't find the needed files on the CD and > can't continue, it then send me to the step selection menu As far as I known should it be possible the put an .iso on an USB-stick. But I don't known how much magic is involved. Some timeline stuff * install from diskettes ( a.k.a. "floppies" ) * install from CDROM, be came very very popular * install from extra disk * install from extra disk, where the disk is physically an USB device * some optimize on combine CD images and disk images Due my lack in exprience with booting ISOs from USB-devices, can't I tell how to prepare a proper setup. These factors are involved: * bootROM in computer ( what _can_ it support ) * selected boot device * by bootROM expected content on boot device ( what _must_ be present ) * the way the content is available on the boot device Read that a second time with a mind set of "my boot disk is an USB storage device" and a thrid time with mind set "my boot ISO in on USB CDROM" Then we boot a Linux kernel ( so leaving bootROM program code ) for what should the kernel look? A (emulated) disk or an emulated CDROM? Back to > Boot method: USB (4Go) made with LiLiUSB Creator on Windows7 Pro > Image version: > http://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/debian-live-8.2.0-amd64-lxde-desktop.iso.torrent What is 'LiLiUSB Creator'? what kind of input does it want? What output does it produce? Yes, that are very technical questions. But an answer as "I can't tell, I picked a tool that was available and should do the trick" is fine. Another good answer would be: "Hey, I just following documentation from URL" Just provide more information about 'LiLiUSB Creator' On the URL with debian-cd/current-live/amd64/bt-hybrid/debian-live in it. How did you found that? What did you bring there? And now some compliments. Yes, I assume you can handle compliments :-) It is good that you are curious about "Debian". Very nice to see that what you allready did (downloading, preparing USBstick) Best thing is you took the effort to create this installation report. I do hope that you presist in getting Debian installed on your Lenovo B590. > Résultat de lspci -knn (ou lspci -nn) : sorry i have no idea what that is `lspci` is a program that lists PCI devices, it tells about hardware. Right _now_, _not_ a problem. Groeten Geert Stappers Footnote: [1] Downloaded image is 'debian-live', not a debian-installer image. Wait for user feedback before reassigning. -- Leven en laten leven signature.asc Description: Digital signature
Re: Bug#801832: Package: installation-reports
On Thu, 15 Oct 2015 03:20:04 +0200, Gersho de Lock wrote: > Package: installation-reports > > Boot method: USB (4Go) made with LiLiUSB Creator on Windows7 Pro > Image version: > http://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/debian-live-8.2.0-amd64-lxde-desktop.iso.torrent > Date: 14oct2015 Machine: Lenovo B590 > Processor:Intel Core i3-3110M 2.4Ghz > Memory: 4Gb > Partitions: 128Gb SSD >c:\ 75Gb (Windows) and 44 Free (for Debian) > > Résultat de lspci -knn (ou lspci -nn) : sorry i have no idea what that is > > Installation du système de base : > [O] = OK, [E] = Error (développez plus bas s'il vous plait), [ ] = non essayé > > Initial boot: [O] > Detect network card:[ ] > Configure network: [ ] > Detect CD: [X] > Load installer modules: [ ] > Detect hard drives: [ ] > Partition hard drives: [ ] > Install base system:[ ] > Clock/timezone setup: [O] > User/password setup:[ ] > Install tasks: [ ] > Install boot loader:[ ] > Overall install:[ ] > > Comments/Problems: > > The installer tells me it can't find the needed files on the CD and can't > continue, it then send me to the step selection menu To find the results of lspci, boot the system with a live CD or USB, open a terminal, and type lspci -knn. That should tell us more about the hardware.
Bug#801832: Package: installation-reports
Package: installation-reports Boot method: USB (4Go) made with LiLiUSB Creator on Windows7 Pro Image version: http://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/debian-live-8.2.0-amd64-lxde-desktop.iso.torrent Date: 14oct2015 Machine: Lenovo B590 Processor:Intel Core i3-3110M 2.4Ghz Memory: 4Gb Partitions: 128Gb SSD c:\ 75Gb (Windows) and 44 Free (for Debian) Résultat de lspci -knn (ou lspci -nn) : sorry i have no idea what that is Installation du système de base : [O] = OK, [E] = Error (développez plus bas s'il vous plait), [ ] = non essayé Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [X] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [O] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The installer tells me it can't find the needed files on the CD and can't continue, it then send me to the step selection menu
Bug#801688: marked as done (flash-kernel fails with readlink: invalid option -- 'm')
Your message dated Wed, 14 Oct 2015 19:38:54 +0100 with message-id <1444847934.18486.12.ca...@hellion.org.uk> and subject line Re: Bug#801688: flash-kernel fails with readlink: invalid option -- 'm' has caused the Debian Bug report #801688, regarding flash-kernel fails with readlink: invalid option -- 'm' 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.) -- 801688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flash-kernel Version: 3.35+deb8u1 Severity: important Tags: d-i Dear Maintainer, when installing flash-kernel on a very basic and minimal system (created with multistrap) flash-kernel fails to install. While flash-kernel does seem to work and is installed afterwards this makes automated installation via multistrap impossible. My packages from multistrap looks like this, which as you can see is fairly minimal packages=f2fs-tools connman wpasupplicant iptables dropbear avahi-daemon libv4l-0 lsb-invalid-mta ca-certificates mtd-utils busybox apt usbmount udisks2 rsync I guess adding some dialog dependancy is probably the quickest fix, but I don't think is the best solution. root@system-02880482d32a:~# apt-get install flash-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: flash-kernel 0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded. Need to get 0 B/34.2 kB of archives. After this operation, 76.8 kB of additional disk space will be used. debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package flash-kernel. (Reading database ... 14355 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.35+deb8u1_armhf.deb ... Unpacking flash-kernel (3.35+deb8u1) ... Setting up flash-kernel (3.35+deb8u1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline readlink: invalid option -- 'm' BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) multi-call binary. Usage: readlink [-fnv] FILE Display the value of a symlink -f Canonicalize by following all symlinks -n Don't add newline -v Verbose : Unable to determine The new file dpkg: error processing package flash-kernel (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: flash-kernel E: Sub-process /usr/bin/dpkg returned an error code (1) P.S. 3.46~bpo8+1 also suffers the same problem. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.3.0-rc1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- On Wed, 2015-10-14 at 12:14 +0200, Olliver Schinagl wrote: > > I think the problem is that you're using busybox instead of > coreutils > > (which is essential and therefore doesn't have to be explicitly > > depended on). > Depends on how you install your system I suspect. No it doesn't. If coreutils is essential then must be installed on any non-buggy Debian system. > I used multistrap with > a list of packages (which pulls the bare minimal system in, of which > busybox or core-utils don't appear to be dependancies) and that > leaves me with a fully working debian system. Not if coreutils isn't installed it doesn't. By definition. Either multistrap is buggy or it is not designed to provide you with a Debian system in the first place. I don't know which. > I couldn't find where readlink or readline is being called in > flash-kernel or its scripts >From the logs it appears to be used by debconf. This is not a bug in debconf though, as above any package is entitled to assume coreutils is installed. > , but for some reason readlink -m is being > called which may work with the core-utils, but not with busybox. > > Having flash-kernel be functional with atleast busybox doesn't seem > like > a strange requirement. Flash-kernel is for embedded systems and thus > having a bare minimal embedded system isn't all out ot the ordinary > :) flash-kernel is not for embedded systems, it is for Debian systems.
Bug#801810: Passwords are not hashed with MD5 anymore (Appendix B)
Source: installation-guide Version: 20150423+deb8u1 Tags: patch In the section 4.5[1] of Appendix B there are several references to "MD5 hash" as a method of storing passwords. At the end of the section there is a reference to mkpasswd command generating SHA-512 crypt(3) hash. Hence, the hashes should be refered to as "crypt(3) hashes" rather than MD5. Furthermore, the following sentence Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks. while true, is not actually relevant for crypt(3) hashes based on stronger hashes like SHA-256 or SHA-512. I attach a patch for english version of the guide. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. ... Od tej pory wszystko może się zdarzyć. Akcja toczy się... Index: en/appendix/preseed.xml === --- en/appendix/preseed.xml (revision 70042) +++ en/appendix/preseed.xml (working copy) @@ -999,7 +999,7 @@ The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear -text values or MD5 hashes. +text values or crypt(3) hashes. @@ -1006,9 +1006,9 @@ Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these -passwords. Using MD5 hashes is considered slightly better in terms of -security but it might also give a false sense of security as access to a -MD5 hash allows for brute force attacks. +passwords. Storing hashed passwords is considered secure unless a weak +hashing algorithm like DES or MD5 is used which allow for bruteforce +attacks. Recommended password hashing algorithms are SHA-256 and SHA512. @@ -1022,8 +1022,8 @@ # Root password, either in clear text #d-i passwd/root-password password r00tme #d-i passwd/root-password-again password r00tme -# or encrypted using an MD5 hash. -#d-i passwd/root-password-crypted password [MD5 hash] +# or encrypted using an crypt(3) hash. +#d-i passwd/root-password-crypted password [crypt(3) hash] # To create a normal user account. #d-i passwd/user-fullname string Debian User @@ -1031,8 +1031,8 @@ # Normal user's password, either in clear text #d-i passwd/user-password password insecure #d-i passwd/user-password-again password insecure -# or encrypted using an MD5 hash. -#d-i passwd/user-password-crypted password [MD5 hash] +# or encrypted using an crypt(3) hash. +#d-i passwd/user-password-crypted password [crypt(3) hash] # Create the first user with the specified UID instead of the default. #d-i passwd/user-uid string 1010 @@ -1054,7 +1054,7 @@ The following command (available from the whois package) -can be used to generate an MD5 hash for a password: +can be used to generate an SHA-512 based crypt(3) hash for a password: mkpasswd -m sha-512 signature.asc Description: PGP signature
Bug#750586: syslinux-common: Boot fails. Failed to load ldlinux.c32. File must be in /. Upstream bug
Hi, I want to know if this bug have been fixed or not?I downloaded the netboot.tar.gz yesterday and can not boot by PXE. I got this error of failed to load ldlinux.c32Noticed this bug report already more than a year old, I would guess the solution should been compiled in the distributed netboot.tar.gz.Or I really have to build my own netboot.tar.gz?Thanks,GangOn Wed, 04 Jun 2014 20:59:01 +0200 ewew wrote:> Package: syslinux-common> Version: 3:6.03~pre1+dfsg-4 and others> Severity: grave> Tags: d-i upstream> Justification: renders package unusable> > After many time spend on testing. I have found solution to problem described> in bug reports #749991 and #750244. It is comfirmed that netboot.tar.gz for SID > has been built with wrong kernel modules. After spend time with building my own> netboot.tar.gz i have found the solution to error failed to load ldlinux.c32.> This bug has been reintroduced by the upstrem and causes following error.> This info is available on syslinux mailing lists. I also found this problem> seems to be presend in debian-cd bug #699884, but not tested.> Other info is available on debian-devel mailing lists with subject "Possible > kernel modules missmatch in netboot.tar.gz for debian testing".> > Thank You> > Have nice day> > ewew> >
Bug#801769: os-prober does not list connected LUKS encrypted partitions
Package: os-prober
Version: 1.65
Severity: normal
Tags: patch
Dear Maintainer,
* What led up to the situation?
In a multi-boot system, os-prober does not list those encrypted partitions
with other OSs that are manually connected.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Connecting the partition with: sudo cryptsetup luksOpen /dev/sda1 sda1
Confirmed that the partition was mapped in /dev/mapper: ls /dev/mapper
* What was the outcome of this action?
os-prober returned empty
* What outcome did you expect instead?
Listing the OS information in /dev/mapper/sda1
-- System Information:
LSB Version:
security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: SolydXK
Description:SolydK 8 64-bit
Release:8
Codename: solydxk
Architecture: x86_64
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages os-prober depends on:
ii libc6 2.19-18+deb8u1
os-prober recommends no packages.
os-prober suggests no packages.
-- no debconf information
--- /usr/bin/os-prober 2014-09-28 23:04:17.0 +0200
+++ /home/arjen/live/solydk/root/usr/bin/os-prober 2015-10-14 11:11:56.047870558 +0200
@@ -25,6 +25,15 @@
}
partitions () {
+ # List connected LUKS devices
+ if type cryptsetup >/dev/null 2>&1; then
+ for device in $(ls /dev/mapper); do
+ if [ "$(cryptsetup status /dev/mapper/$device | grep LUKS)" != "" ]; then
+echo "/dev/mapper/$device"
+ fi
+ done
+ fi
+
# Exclude partitions that have whole_disk sysfs attribute set.
if [ -d /sys/block ]; then
# Exclude partitions on physical disks that are part of a
Bug#801688: flash-kernel fails with readlink: invalid option -- 'm'
Hey Ben, On 13-10-15 18:57, Ben Hutchings wrote: On Tue, 2015-10-13 at 15:49 +0200, Olliver Schinagl wrote: Package: flash-kernel Version: 3.35+deb8u1 Severity: important Tags: d-i Dear Maintainer, when installing flash-kernel on a very basic and minimal system (created with multistrap) flash-kernel fails to install. While flash-kernel does seem to work and is installed afterwards this makes automated installation via multistrap impossible. My packages from multistrap looks like this, which as you can see is fairly minimal packages=f2fs-tools connman wpasupplicant iptables dropbear avahi-daemon libv4l-0 lsb-invalid-mta ca-certificates mtd-utils busybox apt usbmount udisks2 rsync I guess adding some dialog dependancy is probably the quickest fix, but I don't think is the best solution. root@system-02880482d32a:~# apt-get install flash-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: flash-kernel 0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded. Need to get 0 B/34.2 kB of archives. After this operation, 76.8 kB of additional disk space will be used. debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package flash-kernel. (Reading database ... 14355 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.35+deb8u1_armhf.deb ... Unpacking flash-kernel (3.35+deb8u1) ... Setting up flash-kernel (3.35+deb8u1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline readlink: invalid option -- 'm' [...] I think the problem is that you're using busybox instead of coreutils (which is essential and therefore doesn't have to be explicitly depended on). Depends on how you install your system I suspect. I used multistrap with a list of packages (which pulls the bare minimal system in, of which busybox or core-utils don't appear to be dependancies) and that leaves me with a fully working debian system. I couldn't find where readlink or readline is being called in flash-kernel or its scripts, but for some reason readlink -m is being called which may work with the core-utils, but not with busybox. Having flash-kernel be functional with atleast busybox doesn't seem like a strange requirement. Flash-kernel is for embedded systems and thus having a bare minimal embedded system isn't all out ot the ordinary :) Olliver Ben.
