Processed: Re: Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Processing control commands: retitle -1 debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url Bug #759290 [debian-installer] debian-installer: 'Automated install' does not delay the locale and keyboard questions Changed Bug title to 'debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url' from 'debian-installer: 'Automated install' does not delay the locale and keyboard questions' tag -1 - unreproducible Bug #759290 [debian-installer] debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url Removed tag(s) unreproducible. severity -1 wishlist Bug #759290 [debian-installer] debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url Severity set to 'wishlist' from 'minor' -- 759290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b759290.140903377130395.transcr...@bugs.debian.org
Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Control: retitle -1 debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url Control: tag -1 - unreproducible Control: severity -1 wishlist Hi Samuel, thanks for your quick reply! On Tue, Aug 26, 2014 at 01:52:17AM +0200, Samuel Thibault wrote: Andreas B. Mundt, le Mon 25 Aug 2014 23:19:03 +0200, a écrit : when experimenting with unattended installations using PXE-boot and preseeding d-i, I did not find the 'Automated install' (auto mode) working as described in [1]: The auto kernel parameter is an alias for auto-install/enable and setting it to true delays the locale and keyboard questions until after there has been a chance to preseed them ... When I choose 'Automated install' from the 'Advanced options' menu, the first questions show up nevertheless (before setting up the network) and I have to answer them or preseed them on the kernel boot line. Could it be that the delaying functionality got lost? No, it is still there, but only if you provide some preseeding URL on the boot line or CD image etc. Otherwise it will prompt for the URL, and I guess that while at it, there's no point in not configuring the keyboard before that. At any rate, booting jessie b1 with the Automated install boot entry and passing url=http://dept-info.labri.fr/~thibault/preseed-jessie.txt on the kernel command line does install a Debian system without any prompt. You are right, it works indeed when providing a url, just tested it here. Before, I was using the method B.2.5. Using a DHCP server to specify preconfiguration files described in [1]. Is there a reason not to delay the questions with that method? Perhaps it could be mentioned in [1], but feel free to close this bug if you think it's inappropriate. Best regards, Andi [1] https://www.debian.org/releases/stable/i386/apbs02.html.en#preseed-dhcp -- 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/20140826061601.GA3568@flashgordon
Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Andreas B. Mundt, le Tue 26 Aug 2014 08:16:01 +0200, a écrit : Before, I was using the method B.2.5. Using a DHCP server to specify preconfiguration files described in [1]. Is there a reason not to delay the questions with that method? Probably not, and then it's a bug indeed. Samuel -- 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/20140826092108.gh5...@type.youpi.perso.aquilenet.fr
Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Control: tags -1 + pending Hello, Andreas B. Mundt, le Tue 26 Aug 2014 08:16:01 +0200, a écrit : Before, I was using the method B.2.5. Using a DHCP server to specify preconfiguration files described in [1]. Is there a reason not to delay the questions with that method? This apparently takes back March 2010: locale kbd selection was disabled only on explicit URL on boot parameters. I've made it always done whenever auto is enabled, as I don't see why we shouldn't do it. Fixing fully-automated-from-dhcp seems more important to me than the inconvenience of a qwerty layout for typing the URL if really none is available. Samuel -- 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/20140826100413.gk5...@type.youpi.perso.aquilenet.fr
Processed: Re: Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Processing control commands: tags -1 + pending Bug #759290 [debian-installer] debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url Added tag(s) pending. -- 759290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b759290.140904745926543.transcr...@bugs.debian.org
Bug#759327: (no subject)
Package: installation-reports Boot method: network (PXE with preseeding) Image version: http://d-i.debian.org/daily-images/i386/daily/netboot/netboot.tar.gz Date: Tue, 26 Aug 2014 12:12:17 +0200 Machine: selfmade PC Processor: AMD Athlon II X2 250 Memory: 2 GiB Partitions: automatic partitioning scheme Output of lspci -knn (or lspci -nn): (irrelevant) 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:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I have been using automatic preseed installations with Wheezy for quite some time without problems. So I tried it today with Testing by using the daily network installer (see above) and setting d-i mirror/suite string testing d-i mirror/udeb/suite string testing in my preseed.cfg file. Everything seemed to work out fine until I got this message: Extracting .//var/cache/apt/archives/acl_2.2.52-1_i386.deb requires the bzcat command, which is not available After that the installation was not able to proceed. -- 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/53fc5fc8.5010...@jamesie.de
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
Hi, yesterday I joined the videostream of the installer BoF at DebConf[1]. I also became a bit involved via IRC. Joey Hess raised the question about the criteria to add a Blend or not. I answered all in the list of the bug report #758116 which IMHO fits the criterion of actively maintained and some valuable content for users. I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Kind regards Andreas. [1] https://summit.debconf.org/debconf14/meeting/44/debian-installer-and-cd-bof/ -- http://fam-tille.de -- 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/20140826112723.ga26...@an3as.eu
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
On 08/26/2014 01:27 PM, Andreas Tille wrote: I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I second the inclusion of Debian GIS tasks, as I would love for the Debian GIS tasks to be installable via d-i. Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- 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/53fc72ad.3020...@xs4all.nl
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
Le Tue, Aug 26, 2014 at 01:27:23PM +0200, Andreas Tille a écrit : Hi, yesterday I joined the videostream of the installer BoF at DebConf[1]. I also became a bit involved via IRC. Joey Hess raised the question about the criteria to add a Blend or not. I answered all in the list of the bug report #758116 which IMHO fits the criterion of actively maintained and some valuable content for users. I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Hi Andreas, Joey and everybody, I am sure that it would be great for Debian Med to have the Blends as first-class citizens in the Debian Installer. While it is not difficult to install the metapackages by hand, I expect that having it as an option in the installer will help convincing people to give it a try. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- 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/20140826120926.ga5...@falafel.plessy.net
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Package: debian-installer Version: 20140802 Severity: important On 13/08/14 02:55, Cyril Brulebois wrote: (Looking at syslog when I can, it seems anna is the tool running into a full partition, which isn't surprising.) [...] I'm very concerned to see that Jessie Alpha 1 images were already totally broken for kfreebsd-i386 (ditto for kfreebsd-amd64 in graphical mode), and that it doesn't seem to have been detected/worked on/fixed. And yet... linux-i386 has almost same problem (but different cause?). The patch that fixed this on kfreebsd will not help here. Using: http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/mini.iso wheezy install guide suggests a minimum of 80MB RAM to run d-i. But even with 128MB RAM, not choosing any additional components, I saw this issue during anna: Aug 26 12:28:18 anna[1577]: DEBUG: retrieving open-iscsi-udeb 2.0.873+git0.3b4b4500-3 Aug 26 12:28:22 anna[1577]: corrupted status flag!!: 0 Aug 26 12:28:22 anna[1577]: (process:4260): tar: write error: No space left on device main-menu crashes and fails to respawn after that. 'free' oddly reports there is still 61MB free memory. 'df -h' doesn't work for the root filesystem, it can't find mount point. The installer was not running in low-memory mode. With 96MB it does, but still hits the same issue on a different udeb. With 80MB it doesn't even complete init. Regards, -- Steven Chamberlain ste...@pyro.eu.org Aug 26 12:05:44 syslogd started: BusyBox v1.22.1 Aug 26 12:05:44 kernel: [1.046259] platform eisa.0: EISA: Detected 0 cards Aug 26 12:05:44 kernel: [1.046404] TCP: cubic registered Aug 26 12:05:44 kernel: [1.046418] NET: Registered protocol family 10 Aug 26 12:05:44 kernel: [1.046775] mip6: Mobile IPv6 Aug 26 12:05:44 kernel: [1.046777] NET: Registered protocol family 17 Aug 26 12:05:44 kernel: [1.046788] mpls_gso: MPLS GSO support Aug 26 12:05:44 kernel: [1.046820] Using IPI Shortcut mode Aug 26 12:05:44 kernel: [1.046947] registered taskstats version 1 Aug 26 12:05:44 kernel: [1.047384] rtc_cmos 00:00: setting system clock to 2014-08-26 12:05:44 UTC (1409054744) Aug 26 12:05:44 kernel: [1.047443] PM: Hibernation image not present or could not be loaded. Aug 26 12:05:44 kernel: [1.048566] Freeing unused kernel memory: 568K (c1591000 - c161f000) Aug 26 12:05:44 kernel: [1.048947] Write protecting the kernel text: 3992k Aug 26 12:05:44 kernel: [1.049071] Write protecting the kernel read-only data: 1316k Aug 26 12:05:44 kernel: [1.081028] systemd-udevd[38]: starting version 208 Aug 26 12:05:44 kernel: [1.081904] random: systemd-udevd urandom read with 0 bits of entropy available Aug 26 12:05:44 kernel: [1.110599] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 Aug 26 12:05:44 kernel: [1.228421] virtio-pci :00:03.0: irq 40 for MSI/MSI-X Aug 26 12:05:44 kernel: [1.228459] virtio-pci :00:03.0: irq 41 for MSI/MSI-X Aug 26 12:05:44 kernel: [1.228493] virtio-pci :00:03.0: irq 42 for MSI/MSI-X Aug 26 12:05:45 kernel: [1.596179] tsc: Refined TSC clocksource calibration: 2399.999 MHz Aug 26 12:05:45 kernel: [2.193870] vga16fb: initializing Aug 26 12:05:45 kernel: [2.193878] vga16fb: mapped to 0xc00a Aug 26 12:05:45 kernel: [2.193886] checking generic (fc00 eb000) vs hw (a 1) Aug 26 12:05:45 kernel: [2.194556] fb1: VGA16 VGA frame buffer device Aug 26 12:05:45 init: starting pid 135, tty '': '/sbin/reopen-console /sbin/debian-installer' Aug 26 12:05:45 init: starting pid 138, tty '/dev/tty4': '/usr/bin/tail -f /var/log/syslog' Aug 26 12:05:46 debconf: Setting debconf/language to en Aug 26 12:05:46 main-menu[157]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Aug 26 12:05:46 main-menu[157]: INFO: Menu item 'localechooser' selected Aug 26 12:05:48 debconf: Setting debconf/language to en Aug 26 12:09:25 main-menu[157]: INFO: Menu item 'localechooser' succeeded but requested to be left unconfigured. Aug 26 12:09:25 main-menu[157]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Aug 26 12:09:26 main-menu[157]: INFO: Menu item 'localechooser' selected Aug 26 12:09:26 debconf: Setting debconf/language to en Aug 26 12:09:27 localechooser: info: Language = 'en' Aug 26 12:09:27 localechooser: info: line=en;0;US;en_US.UTF-8;;console-setup Aug 26 12:09:27 localechooser: info: Set debian-installer/language = 'en' Aug 26 12:09:27 localechooser: info: Default country = 'US' Aug 26 12:09:27 localechooser: info: Default locale = 'en_US.UTF-8' Aug 26 12:09:27 localechooser: info: Set debian-installer/consoledisplay = 'console-setup' Aug 26 12:09:27 debconf: Setting debconf/language to en Aug 26 12:09:28 kernel: [ 225.497590] random: nonblocking pool is initialized Aug 26 12:09:28 localechooser: info: Set debian-installer/country = 'GB' Aug 26 12:09:29 localechooser: info: Set debian-installer/locale = 'en_GB.UTF-8' Aug 26
Re: Priority of partman-iscsi
On 26/08/14 06:40, Christian PERRIER wrote: While adding i18n to partman-iscsi, I noticed that it is a sta,ndard component of D-I. My understanding of iSCSI devices is that this is quite a corner case for installation. Therefore, shouldn't the package be priority: optional. [...] I agree, there is a need to slim d-i's memory requirements and this seems a good candidate to become optional. Please see bug #759336 I just filed which specifically mentioned iSCSI udebs. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Steven Chamberlain, le Tue 26 Aug 2014 13:48:53 +0100, a écrit : Using: http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/mini.iso wheezy install guide suggests a minimum of 80MB RAM to run d-i. But even with 128MB RAM, not choosing any additional components, I saw this issue during anna: These figures haven't been updated for Jessie yet indeed. Samuel -- 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/20140826130059.ga3...@type.bordeaux.inria.fr
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
Greetings, Fellow Debianites, On Tue, Aug 26, 2014 at 01:27:23PM +0200, Andreas Tille wrote: Hi, yesterday I joined the videostream of the installer BoF at DebConf[1]. I also became a bit involved via IRC. Joey Hess raised the question about the criteria to add a Blend or not. I answered all in the list of the bug report #758116 which IMHO fits the criterion of actively maintained and some valuable content for users. I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Yes, I have to say that I would find it awesome if we could list at install time the blends that are available. In my opinion, this feature would undoubtedly help the user and give the feeling that things are cleverly organised in Debian and that everything is made to simplify the system installation, which is of great importance if we think that Debian still has the reputation of being difficult to deal with at install time. Thanks, Andreas to bring this forward for us not at the DebConf or not immediately involved with the installer-related topics. Cheers, Filippo -- Filippo Rusconi, PhD - public crypto key 7694CF42@ pgp.mit.edu Researcher at CNRS and Debian Developer lopi...@debian.org Author of ``massXpert'' at http://www.massxpert.org -- 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/20140826125406.GD2011@licorne
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
On 26/08/14 14:00, Samuel Thibault wrote: Steven Chamberlain, le Tue 26 Aug 2014 13:48:53 +0100, a écrit : Using: http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/mini.iso wheezy install guide suggests a minimum of 80MB RAM to run d-i. But even with 128MB RAM, not choosing any additional components, I saw this issue during anna: These figures haven't been updated for Jessie yet indeed. Those probably should not be updated until nearer the freeze; the Linux kernel for jessie hasn't entered sid yet and that may change memory requirements and udeb sizes a bit. I should be able to help with that, I'll already be testing lots of low-memory installs, in order to find a good size for the kfreebsd d-i ramdisks. It's odd that there still seemed to be ~50% free memory when this problem happened, though. Is there some maximum size that the linux-i386 root ramdisk can grow to? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- 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/53fc875b.90...@pyro.eu.org
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Steven Chamberlain, le Tue 26 Aug 2014 14:10:51 +0100, a écrit : I should be able to help with that, I'll already be testing lots of low-memory installs, in order to find a good size for the kfreebsd d-i ramdisks. Well, the testing has to be done for each architecture, since that change quite a bit depending on the arch. Samuel -- 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/20140826131530.gc3...@type.bordeaux.inria.fr
Re: d-i's purpose
During Steve's talk it was mentioned that cloud/VPS installs often don't use d-i, and that means lots of questions do not get asked and configuration generated as a result. Some people would like to still have that. This seems like another reason for userland bits of d-i to be able to run standalone, either on first-boot of a part-installed system, or in a debootstrapped container (for OpenVZ/LXC/jail-like VPSes). On 21/08/14 14:00, Steven Chamberlain wrote: And I've had other d-i issues recently where I thought d-i is so inherentely hard to debug, rebuild, test; I really wish the whole thing could run inside of a chroot/jail/container, or at least the individual components run standalone under gdb/ktrace like a normal application, and have easy access to fully-featured (not Busybox) utils, make quick changes to test, read and save a copy of logs, etc.. IMHO being able to more easily run some or all of d-i standalone, would be a blessing when trying to debug and develop it. Instead of needing to rebuild udebs, and iso images, need a whole Qemu VM to boot them, and then have some difficulty interrogating what's going on inside it with the limited available tools inside. with d-i growing larger and now using a GUI by default, hasn't the full Debian Live system become a more practical base to install from now? It was also mentioned that Debian Live image generation is being integrated a bit more with regular CD image building (at least, on the same machine for now). So we're getting closer to this. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Steven Chamberlain, le Tue 26 Aug 2014 14:10:51 +0100, a écrit : It's odd that there still seemed to be ~50% free memory when this problem happened, though. Is there some maximum size that the linux-i386 root ramdisk can grow to? There seems to be something odd somewhere indeed. Just trying to update the lowmem value for amd64 brings me from 109MiB to 164MiB, that's a big jump! I guess the kernel somehow now has a heuristic to limit the rootfs size. When using 163MiB, I hit a bug when lvm tries to start, and indeed / is said to be full while free shows 44MiB free. Samuel -- 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/20140826134625.ge3...@type.bordeaux.inria.fr
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Hi, On 26/08/14 14:15, Samuel Thibault wrote: Steven Chamberlain, le Tue 26 Aug 2014 14:10:51 +0100, a écrit : I should be able to help with that, I'll already be testing lots of low-memory installs, in order to find a good size for the kfreebsd d-i ramdisks. Well, the testing has to be done for each architecture, since that change quite a bit depending on the arch. If we say in the install manual that a particular arch needs 80MiB RAM to run d-i, do you think we should have a Jenkins job that runs installs in a Qemu VM having exactly that amount? So we know if/when that stops being the case? And a question for Holger: looking at jenkins.d.n - is it only GUI installs that are tested currently? Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- 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/53fc902e.3070...@pyro.eu.org
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Samuel Thibault, le Tue 26 Aug 2014 15:46:25 +0200, a écrit : Steven Chamberlain, le Tue 26 Aug 2014 14:10:51 +0100, a écrit : It's odd that there still seemed to be ~50% free memory when this problem happened, though. Is there some maximum size that the linux-i386 root ramdisk can grow to? There seems to be something odd somewhere indeed. Just trying to update the lowmem value for amd64 brings me from 109MiB to 164MiB, that's a big jump! I guess the kernel somehow now has a heuristic to limit the rootfs size. When using 163MiB, I hit a bug when lvm tries to start, and indeed / is said to be full while free shows 44MiB free. In /proc/mounts, one can read for the rootfs on / a size= value, which seems to be half the memory size. That's probably the culprit, perhaps it can be worked around somehow for d-i at least. Samuel -- 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/20140826134932.gf3...@type.bordeaux.inria.fr
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Steven Chamberlain, le Tue 26 Aug 2014 14:48:30 +0100, a écrit : On 26/08/14 14:15, Samuel Thibault wrote: Steven Chamberlain, le Tue 26 Aug 2014 14:10:51 +0100, a écrit : I should be able to help with that, I'll already be testing lots of low-memory installs, in order to find a good size for the kfreebsd d-i ramdisks. Well, the testing has to be done for each architecture, since that change quite a bit depending on the arch. If we say in the install manual that a particular arch needs 80MiB RAM to run d-i, do you think we should have a Jenkins job that runs installs in a Qemu VM having exactly that amount? So we know if/when that stops being the case? That could be useful indeed. I don't know how jenkins works exactly, but it needs to really go through the dialog boxes (selection portuguese as language, etc.) Samuel -- 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/20140826135058.gg3...@type.bordeaux.inria.fr
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
Samuel Thibault, le Tue 26 Aug 2014 15:49:32 +0200, a écrit :
In /proc/mounts, one can read for the rootfs on / a size= value, which
seems to be half the memory size. That's probably the culprit, perhaps
it can be worked around somehow for d-i at least.
Indeed:
static unsigned long shmem_default_max_blocks(void)
{
return totalram_pages / 2;
}
which probably makes sense for an installed system, but not for an
installer. We can however do this early at boot:
mount / -o remount,size=$(( $(grep ^MemTotal: /proc/meminfo | { read x y z;
echo $y; }) * 1024 )
notably before unpacking .udebs, S15lowmem would probably be a fine
place for this? (it notably already does the computation trick)
Samuel
--
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/20140826140510.gh3...@type.bordeaux.inria.fr
Bug#759336: linux-i386 lowmem install: anna fails with ENOSPC
On 26/08/14 15:05, Samuel Thibault wrote:
[...] We can however do this early at boot:
mount / -o remount,size=$(( $(grep ^MemTotal: /proc/meminfo | { read x y z;
echo $y; }) * 1024 )
notably before unpacking .udebs, S15lowmem would probably be a fine
place for this? (it notably already does the computation trick)
Yes I think it could go there, but remembering that this is needed
whether the installer decides to go into low-memory mode or not.
Apparently you can just say size=100%
It could be any value sufficiently larger than 50%, but I think I'd
prefer 100% so that - in case of a bug that fills the tmpfs - memory
exhaustion happens rather than ENOSPC, because the latter might not
leave space for an explanation to be written to syslog.
mount(8), Mount options for tmpfs:
size=nbytes
Override default maximum size of the filesystem. The size is
given in bytes, and rounded up to entire pages. The default is
half of the memory. The size parameter also accepts a suffix %
to limit this tmpfs instance to that percentage of your physical
RAM: the default, when neither size nor nr_blocks is specified,
is size=50%
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
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/53fc988c.8060...@pyro.eu.org
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
Hello! (sorry for top posting) DebianParl is a blend that could also be in taskel, no? https://wiki.debian.org/DebianParl Best regards. //Erik -Original Message- From: Charles Plessy [mailto:ple...@debian.org] Sent: 26 August 2014 14:09 To: 758...@bugs.debian.org; debian-ble...@lists.debian.org Subject: Re: Please be verbose whether you would like to get your Blend promoted by tasksel Le Tue, Aug 26, 2014 at 01:27:23PM +0200, Andreas Tille a écrit : Hi, yesterday I joined the videostream of the installer BoF at DebConf[1]. I also became a bit involved via IRC. Joey Hess raised the question about the criteria to add a Blend or not. I answered all in the list of the bug report #758116 which IMHO fits the criterion of actively maintained and some valuable content for users. I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Hi Andreas, Joey and everybody, I am sure that it would be great for Debian Med to have the Blends as first-class citizens in the Debian Installer. While it is not difficult to install the metapackages by hand, I expect that having it as an option in the installer will help convincing people to give it a try. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-blends-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140826120926.ga5...@falafel.plessy.net -- 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/4b654b63c9a4614ea1f088b2490e8f3a20cb3...@ucexlwp007.ep.parl.union.eu
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
On 26.08.2014 13:27, Andreas Tille wrote: [...} I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Hi, I would really like to see that the tasks of the Debian Games Blend are installable via d-i. A package with tasksel descriptions, »games-tasks«, is already available. Please let me know if there is anything else that can be done from my side. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
[ replying only to bug + list - hope all are subscribed ] Quoting JOSEFSSON Erik (2014-08-26 16:27:43) Hello! (sorry for top posting) Feeling sorry is no use. Consider at least strip fullquote next time. DebianParl is a blend that could also be in taskel, no? https://wiki.debian.org/DebianParl DebianParl is a blend, yes, but currently not defined by metapackage(s) so cannot technically be included in tasksel. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Alpha install ISOs
On Mon, 2014-08-25 at 21:26 -0700, Bill MacAllister wrote: [...] E: Couldn't find any package by regex 'usb-storage-modules-3.10-3-alpha-generic-di' Seems like I need to create those packages for Alpha. How do I do that? Those should all come from the kernel packaging. I expect alpha already has a kernel and you just need to update the KERNEL_VERSION = 3.10-3 somewhere in the d-i tree to whatever the current kernel version is. Or perhaps even just to update your di tree to the latest git which ought to be pointing at the current kernel version already. Ian. -- 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/1409066555.28009.3.ca...@hellion.org.uk
Re: Priority of partman-iscsi
Christian PERRIER bubu...@debian.org (2014-08-26): While adding i18n to partman-iscsi, I noticed that it is a sta,ndard component of D-I. My understanding of iSCSI devices is that this is quite a corner case for installation. Therefore, shouldn't the package be priority: optional. The consequence would be that iSCSI partitioning wouldn't be showing up in partman menus in default installs.but only when users of expert mode choose to load to udeb. I'm no expert but that looks good to me. Mraw, KiBi. signature.asc Description: Digital signature
Bug#759327: installation fails with acl/bzcat dependency error
Control: retitle -1 installation fails with acl/bzcat dependency error Christof Boeckler pos...@jamesie.de (2014-08-26): Package: installation-reports Boot method: network (PXE with preseeding) Image version: http://d-i.debian.org/daily-images/i386/daily/netboot/netboot.tar.gz Date: Tue, 26 Aug 2014 12:12:17 +0200 Machine: selfmade PC Processor: AMD Athlon II X2 250 Memory: 2 GiB Partitions: automatic partitioning scheme Output of lspci -knn (or lspci -nn): (irrelevant) 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:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I have been using automatic preseed installations with Wheezy for quite some time without problems. So I tried it today with Testing by using the daily network installer (see above) and setting d-i mirror/suite string testing d-i mirror/udeb/suite string testing in my preseed.cfg file. Everything seemed to work out fine until I got this message: Extracting .//var/cache/apt/archives/acl_2.2.52-1_i386.deb requires the bzcat command, which is not available Hi, and thanks for your report. I've checked with ftpmasters that no priority change happened in this area lately. It seems it's rather due to the fact acl is still using bz2 (for legacy reasons apparently; it wasn't switched to xz). Ansgar should be dealing with this soon (filing a bug etc.). Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#759327: installation fails with acl/bzcat dependency error
Processing control commands: retitle -1 installation fails with acl/bzcat dependency error Bug #759327 [installation-reports] (no subject) Changed Bug title to 'installation fails with acl/bzcat dependency error' from '(no subject)' -- 759327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b759327.140906961821613.transcr...@bugs.debian.org
Bug#752410: libdebian-installer: ppc64el support
Ben Hutchings b...@decadent.org.uk (2014-08-25): On Mon, 2014-08-25 at 14:11 -0300, Breno Leitao wrote: HI Ben, Do you still have any feedback about the new patch? I have no objections, but I am not a maintainer for this package so it is not for me to apply. I suppose I could blindly apply it, but I'd rather have someone else review it to make sure. Aurelien maybe? Mraw, KiBi. signature.asc Description: Digital signature
Re: Priority of partman-iscsi
Cyril Brulebois k...@debian.org (2014-08-26):
Christian PERRIER bubu...@debian.org (2014-08-26):
While adding i18n to partman-iscsi, I noticed that it is a sta,ndard
component of D-I. My understanding of iSCSI devices is that this is
quite a corner case for installation. Therefore, shouldn't the package
be priority: optional. The consequence would be that iSCSI
partitioning wouldn't be showing up in partman menus in default
installs.but only when users of expert mode choose to load to udeb.
I'm no expert but that looks good to me.
OK, I'm going to take that back.
Julien pointed out on IRC that iSCSI is much more common than I initially
thought, as opposed to multipath or nbd (which indeed are optional), and
Colin that hiding iSCSI wouldn't be a huge service to our users.
Therefore it looks to me that standard is the proper value.
If we want to avoid showing untranslated material in a default install, it
might be sufficient to make sure the partman-iscsi/text/configure_iscsi
string is translated in all languages first; and translators can keep up
with the other strings of this package whenever they have time?
I understand extra strings are no fun. But the freeze is still a few weeks
away, and l10n-{only,mostly} uploads/migrations are very much possible;
remember the bulk of l10n changes I reviewed/approved during the wheezy
freeze. ;)
Mraw,
KiBi.
signature.asc
Description: Digital signature
Bug#752410: marked as done (libdebian-installer: ppc64el support)
Your message dated Tue, 26 Aug 2014 19:57:45 +0200
with message-id 20140826175745.gi15...@hall.aurel32.net
and subject line Re: Bug#752410: libdebian-installer: ppc64el support
has caused the Debian Bug report #752410,
regarding libdebian-installer: ppc64el support
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.)
--
752410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libdebian-installer
Version: 0.91
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
here is a patch from Ubuntu for ppc64el support in libdebian-installer.
F.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)
Kernel: Linux 3.14-1-powerpc64le (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libdebian-installer-0.91/src/system/Makefile.am libdebian-installer-0.91/src/system/Makefile.am
--- libdebian-installer-0.91/src/system/Makefile.am 2013-12-28 08:51:24.0 +
+++ libdebian-installer-0.91/src/system/Makefile.am 2014-05-20 10:28:31.0 +
@@ -21,6 +21,7 @@
subarch-mips-linux.c \
subarch-mipsel-linux.c \
subarch-powerpc-linux.c \
+ subarch-ppc64el-linux.c \
subarch-sh4-linux.c \
subarch-sparc-linux.c \
subarch-x86-linux.c \
diff -Nru libdebian-installer-0.91/src/system/subarch-ppc64el-linux.c libdebian-installer-0.91/src/system/subarch-ppc64el-linux.c
--- libdebian-installer-0.91/src/system/subarch-ppc64el-linux.c 1970-01-01 00:00:00.0 +
+++ libdebian-installer-0.91/src/system/subarch-ppc64el-linux.c 2014-05-20 10:28:31.0 +
@@ -0,0 +1,92 @@
+#include ctype.h
+#include stdlib.h
+#include stdio.h
+#include string.h
+#include strings.h
+
+#include debian-installer/system/subarch.h
+
+struct map {
+ char *entry;
+ char *ret;
+};
+
+static struct map map_generation[] = {
+ { OldWorld, powermac_oldworld },
+ { NewWorld, powermac_newworld },
+ { NuBus, powermac_nubus },
+ { NULL, NULL }
+};
+
+static struct map map_machine[] = {
+ { PReP, prep },
+ { CHRP Pegasos, chrp_pegasos },
+ { EFIKA, chrp_pegasos },
+ { CHRP IBM, chrp_rs6k },
+ { CHRP, chrp },
+ { Amiga, amiga },
+ { 64-bit iSeries Logical Partition, iseries },
+ { NULL, NULL }
+};
+
+static struct map map_platform[] = {
+ { PS3, ps3 },
+ { Cell, cell },
+ { PA Semi, pasemi },
+ { Maple, chrp_ibm },
+ { pSeries, chrp_ibm },
+ { P4080 DS, fsl },
+ { QEMU e500, fsl },
+ { NULL, NULL }
+};
+
+static char *check_map(struct map map[], const char *entry)
+{
+ for (; map-entry; map++)
+ if (!strncasecmp(map-entry, entry, strlen(map-entry)))
+ return map-ret;
+
+ return NULL;
+}
+
+const char *di_system_subarch_analyze(void)
+{
+ FILE *cpuinfo;
+ char line[1024];
+ char cpuinfo_platform[256], cpuinfo_machine[256], cpuinfo_generation[256];
+ char *ret, *pos;
+
+ cpuinfo = fopen(/proc/cpuinfo, r);
+ if (cpuinfo == NULL)
+ return unknown;
+
+ while (fgets(line, sizeof(line), cpuinfo) != NULL) {
+ pos = strchr(line, ':');
+ if (pos == NULL)
+ continue;
+ while (*++pos (*pos == '\t' || *pos == ' '));
+
+ if (strstr(line, platform) == line)
+ strncpy(cpuinfo_platform, pos, sizeof(cpuinfo_platform));
+
+ if (strstr(line, machine) == line)
+ strncpy(cpuinfo_machine, pos, sizeof(cpuinfo_machine));
+
+ if (strstr(line, pmac-generation) == line)
+ strncpy(cpuinfo_generation, pos, sizeof(cpuinfo_generation));
+ }
+
+ fclose(cpuinfo);
+
+ ret = check_map(map_platform, cpuinfo_platform);
+ if (ret)
+ return ret;
+ ret = check_map(map_machine, cpuinfo_machine);
+ if (ret)
+ return ret;
+ ret = check_map(map_generation, cpuinfo_generation);
+ if (ret)
+ return ret;
+
+ return unknown;
+}
---End Message---
---BeginMessage---
Version: 0.95
On Tue, Aug 26, 2014 at 07:02:28PM +0200, Cyril Brulebois wrote:
Ben Hutchings b...@decadent.org.uk (2014-08-25):
On Mon, 2014-08-25 at 14:11 -0300, Breno Leitao wrote:
HI Ben,
Do you still have any feedback about the new patch?
I have no objections, but I am not a maintainer for this package so
it is not for me to apply.
I suppose I could blindly apply it, but I'd rather have someone else
review it to make sure. Aurelien maybe?
Oh I fixed that in version 0.95, but I just realized I forgot to add a
closes entry in the changelog. Closing the bug with this mail
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net
New team member
Hi, FWIW I've just added Baptiste (in Cc) to the d-i group. Welcome! Quoting the request mail: | Hi, | | I'm involved in -l10n-french team and I'm updating the french translation of d-i manual. | I'd like to migrate it from xml to poxml. | | Thank's | | Baptiste I trust you're in touch with Christian and will check with him before making any changes to i18n/l10n infrastructure? Mraw, KiBi. signature.asc Description: Digital signature
Re: Debian installer and CD BoF: my views for jessie
Steven Chamberlain ste...@pyro.eu.org (2014-08-25): On 25/08/14 04:55, Cyril Brulebois wrote: * Architecture support: my own, limited testing made me discover how badly broken d-i on GNU/kFreeBSD was, and I shared my concerns some days ago with BSD people and the release team. I haven't seen anyone commit to fixing d-i there and making sure it's kept in a good shape. [ To be determined, needs release team input at least. ] But I provided patches already for all the important issues you mentioned: #757985, #757987, #757988 Thanks, appreciated. and at least replied about the other, to say that it's not a blocker for jessie release: #757986 It was already there in wheezy. Not being able to fix annoying prompts/red screens on a default installation, over a whole release cycle, makes me sad. In case you still need me to say it explicitly, I am committed to testing for and fixing kfreebsd d-i issues between now and release. I'll be trying to automate some of this too (initially my own thing, hopefully leading to jenkins.d.n integration someday). Well, yes, that's the kind of thing I'm looking for. We need people committed to keeping their port alive and useful. Having people upload some packages and disappear for a while is OK when some others stay and do the needed work/testing/fixing… (Unless you tell me otherwise I'll drop the cc in further mails since you seem to be subscribed to -boot@? Wasn't exactly sure until now.) I admit I was not doing full test installs since the d-i alpha (though I was doing daily builds of it as part of the kfreebsd 10.1 kernel packaging work). I still thought it was early days to worry about d-i, and didn't know the Beta 1 was coming. I watched Steve's talk and I do understand the need for this to happen now. As I mentioned in another mail, communication for Beta 1 wasn't exactly perfect, if not entirely missing. But that doesn't mean that d-i shouldn't work most of the time; or, if unexpected stuff happens (and that happens regularly!), it should be detected ASAP, documented, and possibly with plans/ideas to get things fixed up, if fixes can't be merged right away. I might be misremembering of course but I think d-i on linux archs has been working more or less during the whole release cycle. (The parted transition being an excellent example of the contrary, even if it was detected straight away, and fixed in a tiny number of days.) Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
reopen 759189 Daniel Baumann daniel.baum...@progress-technologies.net (2014-08-26): close 759189 thanks I see you've fixed the bug in your package: http://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?id=a212be5de579ed41643e4eaf1a03775839608ff5 so this bug can be closed here, #751731 is enough to track it on your end. Not until it's uploaded, and I'm not going to upload debian-installer just for that. signature.asc Description: Digital signature
Bug#759148: marked as done (d-i manual: loop-AES no longer supported - update docs)
Your message dated Tue, 26 Aug 2014 21:01:33 +0200 with message-id 20140826210133.769ea98f9b1f9a7f34c36...@mailbox.org and subject line Re: Bug#759148: d-i manual: loop-AES no longer supported - update docs has caused the Debian Bug report #759148, regarding d-i manual: loop-AES no longer supported - update docs 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.) -- 759148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-guide Tags: patch Hi, In netinst CD Jessie Beta1 there seems to be no support for crypt method loop-AES. I suspect this is intended. The d-i manual therefore needs an update. Patch attached. Cheers Holger -- Holger Wansing hwans...@mailbox.org Index: boot-new/mount-encrypted.xml === --- boot-new/mount-encrypted.xml (Revision 69255) +++ boot-new/mount-encrypted.xml (Arbeitskopie) @@ -8,13 +8,14 @@ If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each -of these volumes during the boot. The actual procedure differs -slightly between dm-crypt and loop-AES. +of these volumes during the boot. /para +!-- sect2 id=mount-dm-crypt titledm-crypt/title +-- para @@ -68,6 +69,7 @@ After entering all passphrases the boot should continue as usual. /para +!-- loop-AES is not supported by the installer at the moment /sect2 sect2 id=mount-loop-aes @@ -98,6 +100,7 @@ /para /sect2 +-- sect2 id=crypto-troubleshooting titleTroubleshooting/title @@ -122,7 +125,10 @@ The easiest case is for encrypted volumes holding data like filename/home/filename or filename/srv/filename. You can -simply mount them manually after the boot. For loop-AES this is +simply mount them manually after the boot. + +!-- +For loop-AES this is a one-step operation: informalexamplescreen @@ -136,8 +142,9 @@ the passphrase for this volume. /parapara +-- -For dm-crypt this is a bit trickier. First you need to register the +For dm-crypt this is a bit tricky. First you need to register the volumes with applicationdevice mapper/application by running: informalexamplescreen Index: using-d-i/modules/partman-crypto.xml === --- using-d-i/modules/partman-crypto.xml (Revision 69255) +++ using-d-i/modules/partman-crypto.xml (Arbeitskopie) @@ -104,7 +104,7 @@ /varlistentry varlistentry -termIV algorithm: userinputcbc-essiv:sha256/userinput/term +termIV algorithm: userinputxts-plain64/userinput/term listitempara @@ -119,7 +119,7 @@ /parapara From the provided alternatives, the default -userinputcbc-essiv:sha256/userinput is currently the least +userinputxts-plain64/userinput is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms. @@ -202,8 +202,10 @@ /varlistentry /variablelist +/para -/parapara +!-- loop-AES is not supported by the installer at the moment +para If you select menuchoice guimenuEncryption method:/guimenu guimenuitemLoopback (loop-AES)/guimenuitem /menuchoice, the menu @@ -264,7 +266,10 @@ Please see the section on erasing data above. -/para/listitem +/para +-- + +/listitem /varlistentry /variablelist @@ -321,16 +326,12 @@ After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in -the same way as ordinary partitions. The following example shows two -different volumes. The first one is encrypted via dm-crypt, the second -one via loop-AES. +the same way as ordinary partitions. The following example shows a +volume encrypted via dm-crypt. informalexamplescreen Encrypted volume (replaceablesda2_crypt/replaceable) - 115.1 GB Linux device-mapper #1 115.1 GB F ext3 - -Loopback (replaceableloop0/replaceable) - 515.2 MB AES256 keyfile - #1 515.2 MB F ext3 /screen/informalexample Now is the time to assign mount points to the volumes and optionally @@ -340,7 +341,7 @@ Pay attention to the identifiers in parentheses (replaceablesda2_crypt/replaceable -and replaceableloop0/replaceable in this case) and the mount +in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process
Re: isolinux: isohybrid dropped, breaking debian-installer builds
close 759189 thanks I see you've fixed the bug in your package: http://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?id=a212be5de579ed41643e4eaf1a03775839608ff5 so this bug can be closed here, #751731 is enough to track it on your end. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/53fcd7de.4060...@progress-technologies.net
Bug#759029: installation-report: loongson-2f: Jessie Beta 2 netboot mostly OK
On 23/08/14 23:00, Steven Chamberlain wrote: I only picked 'standard' and 'SSH server' tasks so was surprised to see these installed: libcairo2 libgl1-mesa-dri libgl1-mesa-glx libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libpangocairo-1.0-0 pinentry-gtk2 This is now a well-known issue, came up during GnuPG BoF. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- 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/53fcdd7d.5030...@pyro.eu.org
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
Hi Andreas, Yes. It is a great idea to be able to choose your blend at installation time. Most of my machines are used for different purposes, and not to have to remember the name of a meta-package to install after the initial installation would be fantastic. It is much easier to tell someone new to install Debian and select Debian GIS from the list, than to refer them to a wiki with post-installation instructions. Cheers, Ross -- 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/53fce48f.2010...@the-gammons.net
Re: Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
Daniel Baumann daniel.baum...@progress-technologies.net (2014-08-26): On 08/26/2014 09:07 PM, Cyril Brulebois wrote: Not until it's uploaded, and I'm not going to upload debian-installer just for that. since this is not a bug in isolinux, can you explain why should it be kept open? Sure: breaking reverse dependencies is a bug; a quite nasty one when that happens in an uncoordinated and deliberately disruptive manner. signature.asc Description: Digital signature
Re: Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
On 08/26/2014 09:07 PM, Cyril Brulebois wrote: Not until it's uploaded, and I'm not going to upload debian-installer just for that. since this is not a bug in isolinux, can you explain why should it be kept open? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/53fced03.1070...@progress-technologies.net
Bug#485586: debian-installer: Default to graphical install
Hi, Holger Wansing hwans...@mailbox.org wrote: Defaulting to a graphical (gtk) frontend on i386 and amd64 would mean that it becomes the regular frontend, unless it is desired to credit the newt frontend with some special status. From a global point of view, the graphical frontend is still something special, an exceptional case, since it's only available on 2 archs out of 8 in Jessie. So I would leave the text installer on 'regular' status IMO. Well, amd64+i386 is probably close to almost all installations… Hmm, we should change regular installer - text installer then and don't use regular installer anymore, as proposed by Brian? Might lead to several changes and several outdated translations... I globally changed regular installer into text-based installer in the manual now. Holger -- Holger Wansing hwans...@mailbox.org -- 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/20140826223911.9d33aed7ee386990966ed...@mailbox.org
Re: Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
On 08/26/2014 10:29 PM, Cyril Brulebois wrote: Sure: breaking reverse dependencies is a bug; a quite nasty one when that happens in an uncoordinated and deliberately disruptive manner. i do disgree with that interpretation which can be seen in the previous mail, but insisting on that would not get us anywhere. now, can you give me a *technical* reason why the bugreport needs to be kept open? is there a need to keep syslinux out of testing or why does it need to be kept open? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/53fcefa1.2080...@progress-technologies.net
Re: Alpha install ISOs
--On August 26, 2014 at 4:22:35 PM +0100 Ian Campbell i...@hellion.org.uk wrote: On Mon, 2014-08-25 at 21:26 -0700, Bill MacAllister wrote: [...] E: Couldn't find any package by regex 'usb-storage-modules-3.10-3-alpha-generic-di' Seems like I need to create those packages for Alpha. How do I do that? Those should all come from the kernel packaging. I expect alpha already has a kernel and you just need to update the KERNEL_VERSION = 3.10-3 somewhere in the d-i tree to whatever the current kernel version is. I think you are referring to the values in the config/alpha.cfg file. I set the following values there: KERNELVERSION = 3.10-3-alpha-generic KERNELMAJOR = 3.10 That is not the newest version, but it is the one that currently works on alphas. The most current is 3.14-2. I tried specifying that and got to essentially the same point. Or perhaps even just to update your di tree to the latest git which ought to be pointing at the current kernel version already. This is a fresh di checkout. It is current as far as I can tell. Of course, alpha has had installer built for it for quite a while. Ian. Thanks for the suggestions, Bill -- Bill MacAllister -- 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/0542892596D63B5CC04A09E0@deeth.local
Bug#759388: Os-prober doesn't notice initrd files other than debian's one
package: os-prober
version: 1.64
Os-prober doesn't notice initrd files other than debian's one.
In a partiion I've Slackware. I created a initd.gz for slaclware
(generic kernel needs a initrd for ext4 module, if not I receive
a kernel panic) and tried to make grub set it from debian.
Please, consider
1) in Slackware partition there is a initrd.gz
===
root@debian:~# ls /mnt/slackware/boot/
config elilo-ia32.efiinside.bmp System.map
vmlinuz
config-generic-3.10.17 elilo-x86_64.efi onlyblue.bmp System.map-
generic-3.10.17 vmlinuz-generic-3.10.17
config-huge-3.10.17 initrd.gz README.initrd System.map-
huge-3.10.17 vmlinuz-huge-3.10.17
efi
===
2) os-prober doesn't notice it:
===
root@debian:~# os-prober
/dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sdc4:Slackware Linux (Slackware 14.1):Slackware:linux
===
and after, to control:
===
root@debian:~# linux-boot-prober /dev/sdc4
/dev/sdc4:/dev/sdc4::/boot/vmlinuz-generic-3.10.17::root=/dev/sdc4
/dev/sdc4:/dev/sdc4::/boot/vmlinuz-huge-3.10.17::root=/dev/sdc4
===
3) update-grub2 obviuosly doent's set that initrd:
===
root@debian:~# update-grub2
Creazione di grub.cfg...
Trovata immagine linux: /boot/vmlinuz-3.14-2-amd64
Trovata immagine initrd: /boot/initrd.img-3.14-2-amd64
Trovato Windows Boot Manager su /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Trovato Slackware Linux (Slackware 14.1) su /dev/sdc4
Adding boot menu entry for EFI firmware configuration
done
===
4) the relevant part of /boor/grub/grub.cfg:
===
menuentry 'Slackware Linux (Slackware 14.1)' --class gnu-linux --class gnu --
class os $menuentry_id_option 'osprober-gnulinux-simple-e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf' {
insmod part_gpt
insmod ext2
set root='hd2,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-
efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4 e76be8b8-55fb-47bd-a5b7-2a30a50f4dbf
else
search --no-floppy --fs-uuid --set=root e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
fi
linux /boot/vmlinuz-generic-3.10.17 root=/dev/sdc4
}
submenu 'Opzioni avanzate per Slackware Linux (Slackware 14.1)'
$menuentry_id_option 'osprober-gnulinux-advanced-e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf' {
menuentry 'Slackware Linux (Slackware 14.1) (su /dev/sdc4)' --class
gnu-linux --class gnu --class os $menuentry_id_option 'osprober-
gnulinux-/boot/vmlinuz-generic-3.10.17--e76be8b8-55fb-47bd-a5b7-2a30a50f4dbf'
{
insmod part_gpt
insmod ext2
set root='hd2,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4
--hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4 e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
else
search --no-floppy --fs-uuid --set=root e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
fi
linux /boot/vmlinuz-generic-3.10.17 root=/dev/sdc4
}
menuentry 'Slackware Linux (Slackware 14.1) (su /dev/sdc4)' --class
gnu-linux --class gnu --class os $menuentry_id_option 'osprober-
gnulinux-/boot/vmlinuz-huge-3.10.17--e76be8b8-55fb-47bd-a5b7-2a30a50f4dbf' {
insmod part_gpt
insmod ext2
set root='hd2,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4
--hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4 e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
else
search --no-floppy --fs-uuid --set=root e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
fi
linux /boot/vmlinuz-huge-3.10.17 root=/dev/sdc4
}
}
===
i dont' understand why it's impossible to choose
between huge and generic kernel, and above all why
it lacks all occorrences of initrd
--
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/2000818.erFXFB4bb6@debian
Processed: your mail
Processing commands for cont...@bugs.debian.org:
unarchive 537656
Bug #537656 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[di-netboot-assistant] Please update tftp server root directory
Unarchived Bug 537656
reopen 537656
Bug #537656 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[di-netboot-assistant] Please update tftp server root directory
Bug reopened
Ignoring request to alter fixed versions of bug #537656 to the same values
previously set
End of message, stopping processing here.
Please contact me if you need assistance.
--
537656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.140909249617537.transcr...@bugs.debian.org
acl needs bzcat command
Hi all, just tried to install using PXE environment latest (jessie). netboot.tar.gz from there: http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/ version dated 02-08-2014 tried both amd64 and i386 versions. first hit ldlinux.c32 issue (bug #750586) after workaround, installation fails during Install base system acl-xxx.deb needs bzcat command which is not available i checked installer environment, and i see that zcat exists, but no bzcat. someone else encountered that bug ? Gasha -- 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/53fd0b74.5050...@pie-dabas.net
Re: acl needs bzcat command
Hi, and thanks for your mail. Gasha ga...@pie-dabas.net (2014-08-27): just tried to install using PXE environment latest (jessie). netboot.tar.gz from there: http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/ version dated 02-08-2014 tried both amd64 and i386 versions. first hit ldlinux.c32 issue (bug #750586) after workaround, installation fails during Install base system acl-xxx.deb needs bzcat command which is not available i checked installer environment, and i see that zcat exists, but no bzcat. someone else encountered that bug ? Yep, this is #759327. Mraw, KiBi. signature.asc Description: Digital signature
Re: Alpha install ISOs
On Tue, 2014-08-26 at 14:44 -0700, Bill MacAllister wrote: --On August 26, 2014 at 4:22:35 PM +0100 Ian Campbell i...@hellion.org.uk wrote: On Mon, 2014-08-25 at 21:26 -0700, Bill MacAllister wrote: [...] E: Couldn't find any package by regex 'usb-storage-modules-3.10-3-alpha-generic-di' Seems like I need to create those packages for Alpha. How do I do that? Those should all come from the kernel packaging. I expect alpha already has a kernel and you just need to update the KERNEL_VERSION = 3.10-3 somewhere in the d-i tree to whatever the current kernel version is. I think you are referring to the values in the config/alpha.cfg file. I set the following values there: KERNELVERSION = 3.10-3-alpha-generic KERNELMAJOR = 3.10 That is not the newest version, but it is the one that currently works on alphas. Which archive/repo are you building against? Does it contain this version of the kernel? I don't see 3.10-3-alpha-generic in the debian-ports.org repo, which seems to have 3.14-2 and 3.15-trunk. Ian. -- 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/1409095153.28009.60.ca...@hellion.org.uk
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
On Tue, Aug 26, 2014 at 1:27 PM, Andreas Tille andr...@an3as.eu wrote: Hi, yesterday I joined the videostream of the installer BoF at DebConf[1]. I also became a bit involved via IRC. Joey Hess raised the question about the criteria to add a Blend or not. I answered all in the list of the bug report #758116 which IMHO fits the criterion of actively maintained and some valuable content for users. I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Since I have revived the Debian Junior blend I also, as previous posters, think it is a superb idea to be able to easily install this and other blends. Since I missed the d-i and cd BoF, what is needed to make this happen? Is there anything I can do to help? -- Per -- 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/cabyrxstjzca2sd0rp0qzrfppyz+vo6p9gbhukpgg+qkxv27...@mail.gmail.com
Bug#754093: debian-installer: ppc64el: ping / vmlinuz
Package: src:debian-installer
Tags: patch
Hi,
Would you have any news/comments about the patch attached in this bug?
We would like to switch the kernel on ppc64el to vmlinuz starting with
3.16 (introduction of zImage support for 64el).
I am attaching an interdiff for that, on top of the previous patch,
and a full debdiff for your convenience.
I could successfully build d-i on ppc64el w/ those changes (plus adding
a build-dep on grub-ieee1275-bin, apparently missed, for grub-mknetdir),
on the debdiff.
$ tar tf debian-installer-images_20140802ppc64el1_ppc64el.tar.gz |
fgrep vmlinu
./installer-ppc64el/20140802ppc64el1/images/cdrom/vmlinuz
./installer-ppc64el/20140802ppc64el1/images/netboot/debian-installer/ppc64el/vmlinuz
The respective bug on the linux source package has been filled on
Debian #759389 (and Ubuntu LP #1358920).
Thanks!
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -u b/build/config/ppc64el.cfg b/build/config/ppc64el.cfg
--- b/build/config/ppc64el.cfg
+++ b/build/config/ppc64el.cfg
@@ -3,10 +3,10 @@
MKLIBS = mklibs-copy
KERNELMAJOR = 2.6
-BASEVERSION = 3.14-1
+BASEVERSION = 3.16-1
KERNELVERSION = $(BASEVERSION)-powerpc64le
KERNEL_FLAVOUR = di
-KERNELNAME = vmlinux
+KERNELNAME = vmlinuz
KERNELIMAGEVERSION = $(KERNELVERSION)
GRUB_CFG_CDROM = boot/ppc64el/grub-cdrom.cfg
@@ -26,11 +26,11 @@
$(TEMP_CD_TREE)/ppc/chrp \
$(TEMP_CD_TREE)/install
- cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/install/vmlinux
+ cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/install/vmlinuz
cp $(TEMP_INITRD) $(TEMP_CD_TREE)/install/initrd.gz
bootvars-subst \
- KERNEL /install/vmlinux \
+ KERNEL /install/vmlinuz \
INITRD /install/initrd.gz \
$(GRUB_CFG_CDROM) $(TEMP_CD_TREE)/boot/grub/grub.cfg
@@ -47,7 +47,7 @@
$(TEMP_CD_INFO_DIR)/ppc/chrp
bootvars-subst \
- KERNEL /install/vmlinux \
+ KERNEL /install/vmlinuz \
INITRD /install/initrd.gz \
$(GRUB_CFG_CDROM) $(TEMP_CD_INFO_DIR)/boot/grub/grub.cfg
grub-mkimage -O powerpc-ieee1275 -p '(ieee1275/cdrom)/boot/grub' \
@@ -65,7 +65,7 @@
cp $(TEMP_KERNEL) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)
bootvars-subst \
- KERNEL $(NETBOOT_PATH)/vmlinux \
+ KERNEL $(NETBOOT_PATH)/vmlinuz \
INITRD $(NETBOOT_PATH)/initrd.gz \
$(GRUB_CFG_NETBOOT) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/grub.cfg
if [ -n $(SPLASH_PNG) ]; then \
diff -Nru debian-installer-20140802/build/boot/ppc64el/grub-cdrom.cfg
debian-installer-20140802ppc64el1/build/boot/ppc64el/grub-cdrom.cfg
--- debian-installer-20140802/build/boot/ppc64el/grub-cdrom.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/boot/ppc64el/grub-cdrom.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,11 @@
+set timeout=-1
+
+menuentry Install {
+ linux ${KERNEL} -- quiet
+ initrd ${INITRD}
+}
+
+menuentry Rescue mode {
+ linux ${KERNEL} rescue/enable=true -- quiet
+ initrd ${INITRD}
+}
diff -Nru debian-installer-20140802/build/config/ppc64el/cdrom.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el/cdrom.cfg
--- debian-installer-20140802/build/config/ppc64el/cdrom.cfg1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el/cdrom.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,8 @@
+MEDIA_TYPE = CD-ROM
+
+TARGET = $(INITRD) $(KERNEL) $(DEBIAN_CD_INFO)
+EXTRANAME = $(MEDIUM)/
+
+MANIFEST-KERNEL = kernel for use with mkisofs to build a CD
+MANIFEST-INITRD = initrd for use with mkisofs to build a CD
+MANIFEST-DEBIAN_CD_INFO = mkisofs config files for CD
diff -Nru debian-installer-20140802/build/config/ppc64el/netboot.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el/netboot.cfg
--- debian-installer-20140802/build/config/ppc64el/netboot.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el/netboot.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,9 @@
+MEDIA_TYPE = netboot image
+
+NETBOOT_DIR_TARGETS = $(TEMP_INITRD) $(TEMP_KERNEL)
+TARGET = $(NETBOOT_DIR) $(NETBOOT_TAR) $(MINIISO)
+EXTRANAME = $(MEDIUM)/
+
+MANIFEST-NETBOOT_DIR = boot directory for tftp server
+MANIFEST-NETBOOT_TAR = tarball of boot directory
+MANIFEST-MINIISO = tiny CD image that boots the netboot installer
diff -Nru debian-installer-20140802/build/config/ppc64el.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el.cfg
--- debian-installer-20140802/build/config/ppc64el.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el.cfg 2014-08-26
22:57:13.0 +
@@ -0,0 +1,76 @@
+MEDIUM_SUPPORTED = netboot cdrom
+
+MKLIBS = mklibs-copy
+
+KERNELMAJOR = 2.6
+BASEVERSION = 3.16-1
+KERNELVERSION = $(BASEVERSION)-powerpc64le
Bug#754093: debian-installer: ppc64el: ping / vmlinuz
Hi,
and thanks for both the bug report and the patch.
Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com (2014-08-26):
Would you have any news/comments about the patch attached in this bug?
I'll rather let Aurelien comment on ppc64el patches. (Also, some bits
could probably be shared between powerpc and ppc64el?)
We would like to switch the kernel on ppc64el to vmlinuz starting with
3.16 (introduction of zImage support for 64el).
3.16 is soon going to be the default anyway, as soon as it's uploaded to
unstable and built on all architectures.
I am attaching an interdiff for that, on top of the previous patch,
and a full debdiff for your convenience.
I could successfully build d-i on ppc64el w/ those changes (plus adding
a build-dep on grub-ieee1275-bin, apparently missed, for grub-mknetdir),
on the debdiff.
$ tar tf debian-installer-images_20140802ppc64el1_ppc64el.tar.gz |
fgrep vmlinu
./installer-ppc64el/20140802ppc64el1/images/cdrom/vmlinuz
./installer-ppc64el/20140802ppc64el1/images/netboot/debian-installer/ppc64el/vmlinuz
The respective bug on the linux source package has been filled on
Debian #759389 (and Ubuntu LP #1358920).
Thanks!
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -u b/build/config/ppc64el.cfg b/build/config/ppc64el.cfg
--- b/build/config/ppc64el.cfg
+++ b/build/config/ppc64el.cfg
@@ -3,10 +3,10 @@
MKLIBS = mklibs-copy
KERNELMAJOR = 2.6
-BASEVERSION = 3.14-1
+BASEVERSION = 3.16-1
KERNELVERSION = $(BASEVERSION)-powerpc64le
KERNEL_FLAVOUR = di
-KERNELNAME = vmlinux
+KERNELNAME = vmlinuz
KERNELIMAGEVERSION = $(KERNELVERSION)
GRUB_CFG_CDROM = boot/ppc64el/grub-cdrom.cfg
@@ -26,11 +26,11 @@
$(TEMP_CD_TREE)/ppc/chrp \
$(TEMP_CD_TREE)/install
- cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/install/vmlinux
+ cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/install/vmlinuz
cp $(TEMP_INITRD) $(TEMP_CD_TREE)/install/initrd.gz
bootvars-subst \
- KERNEL /install/vmlinux \
+ KERNEL /install/vmlinuz \
INITRD /install/initrd.gz \
$(GRUB_CFG_CDROM) $(TEMP_CD_TREE)/boot/grub/grub.cfg
@@ -47,7 +47,7 @@
$(TEMP_CD_INFO_DIR)/ppc/chrp
bootvars-subst \
- KERNEL /install/vmlinux \
+ KERNEL /install/vmlinuz \
INITRD /install/initrd.gz \
$(GRUB_CFG_CDROM) $(TEMP_CD_INFO_DIR)/boot/grub/grub.cfg
grub-mkimage -O powerpc-ieee1275 -p '(ieee1275/cdrom)/boot/grub' \
@@ -65,7 +65,7 @@
cp $(TEMP_KERNEL) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)
bootvars-subst \
- KERNEL $(NETBOOT_PATH)/vmlinux \
+ KERNEL $(NETBOOT_PATH)/vmlinuz \
INITRD $(NETBOOT_PATH)/initrd.gz \
$(GRUB_CFG_NETBOOT) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/grub.cfg
if [ -n $(SPLASH_PNG) ]; then \
diff -Nru debian-installer-20140802/build/boot/ppc64el/grub-cdrom.cfg
debian-installer-20140802ppc64el1/build/boot/ppc64el/grub-cdrom.cfg
--- debian-installer-20140802/build/boot/ppc64el/grub-cdrom.cfg
1970-01-01 00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/boot/ppc64el/grub-cdrom.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,11 @@
+set timeout=-1
+
+menuentry Install {
+ linux ${KERNEL} -- quiet
+ initrd ${INITRD}
+}
+
+menuentry Rescue mode {
+ linux ${KERNEL} rescue/enable=true -- quiet
+ initrd ${INITRD}
+}
diff -Nru debian-installer-20140802/build/config/ppc64el/cdrom.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el/cdrom.cfg
--- debian-installer-20140802/build/config/ppc64el/cdrom.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el/cdrom.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,8 @@
+MEDIA_TYPE = CD-ROM
+
+TARGET = $(INITRD) $(KERNEL) $(DEBIAN_CD_INFO)
+EXTRANAME = $(MEDIUM)/
+
+MANIFEST-KERNEL = kernel for use with mkisofs to build a CD
+MANIFEST-INITRD = initrd for use with mkisofs to build a CD
+MANIFEST-DEBIAN_CD_INFO = mkisofs config files for CD
diff -Nru debian-installer-20140802/build/config/ppc64el/netboot.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el/netboot.cfg
--- debian-installer-20140802/build/config/ppc64el/netboot.cfg
1970-01-01 00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el/netboot.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,9 @@
+MEDIA_TYPE = netboot image
+
+NETBOOT_DIR_TARGETS = $(TEMP_INITRD) $(TEMP_KERNEL)
+TARGET = $(NETBOOT_DIR) $(NETBOOT_TAR) $(MINIISO)
+EXTRANAME = $(MEDIUM)/
+
+MANIFEST-NETBOOT_DIR = boot directory for tftp server
+MANIFEST-NETBOOT_TAR = tarball of boot directory
+MANIFEST-MINIISO = tiny CD image that boots the netboot installer
diff -Nru debian-installer-20140802/build/config/ppc64el.cfg
Bug#754093: debian-installer: ppc64el: ping / vmlinuz
Hi, On Wed, Aug 27, 2014 at 01:32:32AM +0200, Cyril Brulebois wrote: Hi, and thanks for both the bug report and the patch. Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com (2014-08-26): Would you have any news/comments about the patch attached in this bug? I'll rather let Aurelien comment on ppc64el patches. (Also, some bits could probably be shared between powerpc and ppc64el?) I have this patch in mind for ppc64el d-i (as well as the other one on partman-partioning-auto), I will look in details at it soon, but I would like to test build it using the Debian archive first. We would like to switch the kernel on ppc64el to vmlinuz starting with 3.16 (introduction of zImage support for 64el). 3.16 is soon going to be the default anyway, as soon as it's uploaded to unstable and built on all architectures. I'll look at this one soon. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- 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/20140826234737.gn15...@hall.aurel32.net
Bug#754093: debian-installer: ppc64el: ping / vmlinuz
On 08/26/2014 08:32 PM, Cyril Brulebois wrote: and thanks for both the bug report and the patch. Sure; my pleasure. Mauricio Faria de Oliveiramauri...@linux.vnet.ibm.com (2014-08-26): Would you have any news/comments about the patch attached in this bug? I'll rather let Aurelien comment on ppc64el patches. (Also, some bits could probably be shared between powerpc and ppc64el?) I'm not familiar w/ the approach/decision the original author(s) took about it, nor am familiar w/ the broader scope of d-i, so I'd like to defer the sharing question if possible. :) (I have only guesses about the lack of sharing because pcp64el is not actually/can't be a flavor of powerpc). I can try to find more info if needed. We would like to switch the kernel on ppc64el to vmlinuz starting with 3.16 (introduction of zImage support for 64el). 3.16 is soon going to be the default anyway, as soon as it's uploaded to unstable and built on all architectures. Yup. I just mentioned that to justify the base version bump to 3.16 on the patch, without that version being on sid yet. :) Thanks again, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- 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/53fd1ccc.6040...@linux.vnet.ibm.com
Re: Debian Installer Jessie Beta 1 release
Are you saying XFCE is the problem? Is there going to be an updated installer you want me to test again, or what do you suggest to get ORCA working?? Thanks for looking into this. On Sun, 24 Aug 2014 14:52:38 +0200 Samuel Thibault sthiba...@debian.org wrote: Cyril Brulebois, le Fri 22 Aug 2014 01:43:07 +0200, a écrit : Given what I mentioned above, I think what's in debian-installer should just work as it previously did? I have tested it again with the gnome desktop and it works fine indeed. Samuel -- To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140824125238.gc3...@type.youpi.perso.aquilenet.fr -- 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/web-583063...@admin.nni.com
Re: Debian Installer Jessie Beta 1 release
cstrobel, le Tue 26 Aug 2014 20:31:55 -0400, a écrit : Are you saying XFCE is the problem? Yes. Is there going to be an updated installer you want me to test again, or what do you suggest to get ORCA working?? You can use a gnome image, such as http://cdimage.debian.org/cdimage/jessie_di_beta_1/amd64/iso-cd/debian-jessie-DI-b1-amd64-gnome-CD-1.iso Samuel -- 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/20140827003929.gy4...@type.youpi.perso.aquilenet.fr
Re: Alpha install ISOs
--On August 27, 2014 at 12:19:13 AM +0100 Ian Campbell i...@hellion.org.uk wrote: On Tue, 2014-08-26 at 14:44 -0700, Bill MacAllister wrote: --On August 26, 2014 at 4:22:35 PM +0100 Ian Campbell i...@hellion.org.uk wrote: On Mon, 2014-08-25 at 21:26 -0700, Bill MacAllister wrote: [...] E: Couldn't find any package by regex 'usb-storage-modules-3.10-3-alpha-generic-di' Seems like I need to create those packages for Alpha. How do I do that? Those should all come from the kernel packaging. I expect alpha already has a kernel and you just need to update the KERNEL_VERSION = 3.10-3 somewhere in the d-i tree to whatever the current kernel version is. I think you are referring to the values in the config/alpha.cfg file. I set the following values there: KERNELVERSION = 3.10-3-alpha-generic KERNELMAJOR = 3.10 That is not the newest version, but it is the one that currently works on alphas. Which archive/repo are you building against? Does it contain this version of the kernel? http://ftp.debian-ports.org/debian I don't see 3.10-3-alpha-generic in the debian-ports.org repo, which seems to have 3.14-2 and 3.15-trunk. I should have been more explicit in describing what I have tried. I initially tried specifying the 3.10-3 kernel and then tried again with the 3.14-2 kernel. Both failed and the failures were different only in the version number of the kernel. Here is the kernel specification I am using now: KERNELVERSION = 3.14-2-alpha-generic KERNELMAJOR = 3.14 And here are the errors from the latest run: Building dependency tree... Done E: Unable to locate package fat-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'fat-modules-3.14-2-alpha-generic-di' E: Unable to locate package fb-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'fb-modules-3.14-2-alpha-generic-di' E: Unable to locate package kernel-image-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'kernel-image-3.14-2-alpha-generic-di' E: Unable to locate package nic-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'nic-modules-3.14-2-alpha-generic-di' E: Unable to locate package nic-shared-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'nic-shared-modules-3.14-2-alpha-generic-di' E: Unable to locate package nic-wireless-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'nic-wireless-modules-3.14-2-alpha-generic-di' E: Unable to locate package srm-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'srm-modules-3.14-2-alpha-generic-di' E: Unable to locate package srm-reader E: Unable to locate package usb-storage-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'usb-storage-modules-3.14-2-alpha-generic-di' Makefile:634: recipe for target 'stamps/get_udebs-netboot-stamp' failed Bill -- Bill MacAllister -- 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/A302122022B06F504A291020@deeth.local
Re: Alpha install ISOs
On Tue, 2014-08-26 at 19:13 -0700, Bill MacAllister wrote: --On August 27, 2014 at 12:19:13 AM +0100 Ian Campbell i...@hellion.org.uk wrote: On Tue, 2014-08-26 at 14:44 -0700, Bill MacAllister wrote: --On August 26, 2014 at 4:22:35 PM +0100 Ian Campbell i...@hellion.org.uk wrote: On Mon, 2014-08-25 at 21:26 -0700, Bill MacAllister wrote: [...] E: Couldn't find any package by regex 'usb-storage-modules-3.10-3-alpha-generic-di' Seems like I need to create those packages for Alpha. How do I do that? Those should all come from the kernel packaging. I expect alpha already has a kernel and you just need to update the KERNEL_VERSION = 3.10-3 somewhere in the d-i tree to whatever the current kernel version is. I think you are referring to the values in the config/alpha.cfg file. I set the following values there: KERNELVERSION = 3.10-3-alpha-generic KERNELMAJOR = 3.10 That is not the newest version, but it is the one that currently works on alphas. Which archive/repo are you building against? Does it contain this version of the kernel? http://ftp.debian-ports.org/debian I don't see 3.10-3-alpha-generic in the debian-ports.org repo, which seems to have 3.14-2 and 3.15-trunk. I should have been more explicit in describing what I have tried. I initially tried specifying the 3.10-3 kernel and then tried again with the 3.14-2 kernel. Both failed and the failures were different only in the version number of the kernel. Here is the kernel specification I am using now: KERNELVERSION = 3.14-2-alpha-generic KERNELMAJOR = 3.14 And here are the errors from the latest run: Building dependency tree... Done E: Unable to locate package fat-modules-3.14-2-alpha-generic-di E: Couldn't find any package by regex 'fat-modules-3.14-2-alpha-generic-di' Judging from ftp://ftp.debian-ports.org/debian/pool-alpha/main/l/linux/ (assuming you are building against debian-ports) the kernel isn't building any udebs for alpha. I've no idea why that should be, but you probably need to fix that first. Ian. -- 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/1409106316.28009.87.ca...@hellion.org.uk
Re: Alpha install ISOs
--On August 27, 2014 at 3:25:16 AM +0100 Ian Campbell i...@hellion.org.uk wrote: Judging from ftp://ftp.debian-ports.org/debian/pool-alpha/main/l/linux/ (assuming you are building against debian-ports) the kernel isn't building any udebs for alpha. I've no idea why that should be, but you probably need to fix that first. Yup. Thanks for your help. I most likely will be back when I fix that. Bill -- 'We have meet the enemy, and he is us' Walt Kelly -- 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/E7A8F4BD4F44CC9FB44B2C79@deeth.local
