please supply some documentation for bootnetx64.efi. Also choosing different preseed for each netboot.
I need to do a EFI network (boot and) install, and I'm wondering if this file (bootnetx64.efi) can help me. But there is no documentation on it (except the suggestion in the install manual https://www.debian.org/releases/stable/amd64/ch04s05.en.html#dhcpd "specify a boot loader appropriate for UEFI machines, for example...") My problem is this: I can UEFI netboot using grubx64.efi. However, it loads a standard grub.cfg which runs an interactive installer. I need to preseed the install, and I need to load a different preseed file for each server booted. For non-uefi this is achieved using pxelinux's behaviour of tftp-ing a configuration based on MAC addresses etc. and fallback to a standard location. I'm wondering if grubx64.efi or bootnetx64.efi support similar behaviour? Or else how to get specific information into the installer (such as IP address and hostname), if not via specific pre-seed files per machine? (We can overwrite the grub.cfg each time with the needs of a specific server, but this is not ideal, as it will cause a failure if more than one machine is being net-installed at the same time.) In general though I'm also looking for pointers to documentation. If someone could point to anything that explains what bootnetx64.efi is and what it does, I'd be happy to contribute that back to the wiki or install manual. -- Thanks, Alex King P.S. I didn't find much relevant in the install manual except as mentioned above. I didn't find bootnetx64.efi not mentioned in any of the following locations: * https://wiki.debian.org/DebianInstaller/FAQ * /usr/share/doc/debian-installer-12-netboot-amd64, or any man pages in the package * https://wiki.debian.org/DebianInstaller * https://wiki.debian.org/SecureBoot * https://wiki.debian.org/UEFI * https://duckduckgo.com/?q=bootnetx64.efi+debian+network+boot+uefi=ftsa=web https://wiki.debian.org/PXEBootInstall mentions using grubx64.efi for the standard installer, but doesn't mention how to select a grub.cfg per machine.
Bug#1041231: bluetooth on debian bookworm@macbook pro 2012
]: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc] Kernel driver in use: nvidia Kernel modules: nvidia 01:00.1 Audio device [0403]: NVIDIA Corporation GK107 HDMI Audio Controller [10de:0e1b] (rev a1) Subsystem: Apple Inc. GK107 HDMI Audio Controller [106b:00fc] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 02:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM57765 Gigabit Ethernet PCIe [14e4:16b4] (rev 10) Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM57765 Gigabit Ethernet PCIe [14e4:16b4] Kernel driver in use: tg3 Kernel modules: tg3 02:00.1 SD Host controller [0805]: Broadcom Inc. and subsidiaries BCM57765/57785 SDXC/MMC Card Reader [14e4:16bc] (rev 10) Subsystem: Broadcom Inc. and subsidiaries BCM57765/57785 SDXC/MMC Card Reader [14e4:] Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4331 802.11a/b/g/n [14e4:4331] (rev 02) Subsystem: Broadcom Inc. and subsidiaries BCM4331 802.11a/b/g/n [14e4:4331] Kernel driver in use: bcma-pci-bridge Kernel modules: bcma 04:00.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5901] (rev 08) Subsystem: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5900] Kernel driver in use: firewire_ohci Kernel modules: firewire_ohci 05:00.0 PCI bridge [0604]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Kernel driver in use: pcieport 06:00.0 PCI bridge [0604]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Kernel driver in use: pcieport 06:03.0 PCI bridge [0604]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Kernel driver in use: pcieport 06:04.0 PCI bridge [0604]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Kernel driver in use: pcieport 06:05.0 PCI bridge [0604]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Kernel driver in use: pcieport 06:06.0 PCI bridge [0604]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Kernel driver in use: pcieport 07:00.0 System peripheral [0880]: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] [8086:1513] Subsystem: Device [:] Kernel driver in use: thunderbolt Kernel modules: thunderbolt Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect media: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: This report is not for network issue. But I did have network issue initially - wifi was not detected. I had to install firmware-b43-installer package (i had to connect my laptop using ethernet cable - which luckily it has). Anyway, back to the issue i want to report - I couldnt get bluetooth to pair correctly with my mouse & keyboard. I had to install bluez-firmware. After that, it works fine. -- Best regards, Alex Wibowo
Re: [PATCH v3 1/6] man2/: use IEC or ISO multiples to clarify long numeric digit strings
and other such expanded words. Rob P.S. Maybe this is a generational thing? Are the kids saying "kibibyte" in high school these days? I don't think so. Teachers usually don't know these prefixes either, I guess. Do you expect to change global language usage patterns or just make the man pages less relevant to their intended audience? Honestly, I expect the former. Not single-handedly, but rather I feel supported by a lot of (very common) software out there. I understand it's not everywhere, but also it's not as if it didn't exist prior to me. As for the Linux man-pages, at least a few already use these (prior to me, I believe, since I don't remember changing that): $ grep -rl -e KiB -e MiB -e GiB man*/ man2/ioctl_getfsmap.2 man2/process_vm_readv.2 man2/add_key.2 man2/execve.2 man2/getrlimit.2 man2/ioctl_fideduperange.2 man2/kexec_load.2 man2/alloc_hugepages.2 man3/btree.3 man4/fd.4 man4/loop.4 man5/proc.5 man7/pipe.7 man7/keyrings.7 man7/units.7 $ grep -rn kibi man5/tmpfs.5:60:suffix for Ki, Mi, Gi (binary kilo (kibi), binary mega (mebi), and binary giga man2/msgctl.2:216:int msgpool; /* Size in kibibytes of buffer pool man7/units.7:58:Ki kibi2^10 = 1024 man7/units.7:104:the MB are megabytes and the KiB are kibibytes. They'll have to remove the second space from my cold dead fingers. That's exactly how the change will happen, yes. This was published 9 years ago: https://www.cultofpedagogy.com/two-spaces-after-period/ It's funny, I'm still in my twenties. :p All those style guides are plain wrong. I've read their rationales, and they make no sense at all. Using one space is discarding information, and that is bad. Blame Tim Berners-Lee. The cultural shift started when HTML rendered all runs of whitespace as a single space back in 1991. People write what they read. Actually, it comes from much earlier than that. Have a look at <https://web.archive.org/web/20171107164742/http://www.heracliteanriver.com/?p=324> The real reason seems to be that single spaces lowered the quality of required editors, and thus prices. It's all about the money. I guess the "problems" are the consistency thing referred in the second sentence... Well, it's not inconsistency, it's just that different things are different. I don't like oranges and tomatoes because they're inconsistent; one fruit is red and the other is orange... Nonsense. I got an english minor in college, and one of the things it drilled into me is if it's correct and nobody does it, it's not correct. I do agree with that. The thing here is that I disagree about it not being used. If you look at many commonly-used programs, you'll see it all over the place: top(1), free(1), fdisk(1), ... English! It's a mess. We jettisoned the second person singular because british nobility started copying the queen (who spoke for the nation, thus always in the "we are not amused" plural) and it moved downhill until eventually addressing someone else as thou was fighting words because it meant you considered the person you were addressing your social inferior (yes the Amish got physically attacked for this, it's part of the reason they moved). This is also one of those subtleties in shakespeare, the way he uses "thou" as an insult, because the transition was ongoing in his time: Ahhh, thou is 2nd singular! That explains many things :). I learnt something new today. https://drmarkwomack.com/engl-3306/handouts/shakespeares-language/thou-and-you-in-shakespeare/ But do I expect kibibytes to take off? Not really, no. Could be wrong, but... I hope you're wrong in this one. ;) Rob Cheers, Alex -- <http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5 OpenPGP_signature Description: OpenPGP digital signature
Re: [PATCH v3 1/6] man2/: use IEC or ISO multiples to clarify long numeric digit strings
you can say Kelvin ;) In colloquial texts, or more appropriately in colloquial talking, degrees (without specifying), tons (same), or "megs", are fine, but for a manual, where we want precision (especially since we do mix decimal and binary multipliers often), I would strongly avoid misusing terms. They have no incentives to sell 1 TiB drives, because they are visually almost the same, but there's around 9.95% more bytes, so it's more expensive to produce. It's not worth it for them. "No, a _bud_ lite..." I would say making the docs easy to understand for users is more important than adhering to some specs users might not be familiar with. Well, using MiB prompts readers to use their search engine to learn what that is (that's how I learnt it the first time; and that's what one does when reading a book and finding a new word). "They'll google it" is the modern version of "they'll read the documentation". They will not, you're just delegating blame. I can't imagine someone reading MiB in a manual page and not searching what that means (unless the reader doesn't care about that specific value). Rob P.S. Maybe this is a generational thing? Are the kids saying "kibibyte" in high school these days? I don't think so. Teachers usually don't know these prefixes either, I guess. I know that "hacker means computer breakin specialist" is something a small number of boomers will resist to the death despite a google news search only pulling up one meaning in general usage. And the "two spaces after period" thing old hands cling to will only end when they die despite the chicago manual of style, the AP stylebook, the MLA handbook, and the APA publication manual all agreeing its' been one space after a period for decades now. They'll have to remove the second space from my cold dead fingers. All those style guides are plain wrong. I've read their rationales, and they make no sense at all. Using one space is discarding information, and that is bad. Let's list their reasons (AFAICS): - "It [2 spaces] doesn't look good." Subjective, and I disagree. - "We don't use monospace anymore, so it's not necessary to recognize the end of a sentence." It may be less necessary, but that doesn't make it bad. BTW, does that implicitly recognize that monospace should _always_ use 2 spaces? Thanks. Still with proportional font you can confuse sentence endings with initials in some cases (depending on the context), so 2 spaces is still necessary. - "2 spaces only increase reading speed for those used to them, and only marginally (according to studies)." Having a very small benefit is better than not having it. The fact that one-spacers are slower readers should raise questions. - "introducing two spaces after a sentence-ending period—and only after those periods—causes problems. Absolute consistency is easy to monitor when double spaces are never allowed, but less easy when some spaces after periods are double and others single" I guess the "problems" are the consistency thing referred in the second sentence... Well, it's not inconsistency, it's just that different things are different. I don't like oranges and tomatoes because they're inconsistent; one fruit is red and the other is orange... Nonsense. - "Old English used 3-em space after period, but old Spanish or French didn't, in fact they often used 0 spaces after punctuation". So what? Were they more readable thanks to that? No. I've had to read old Spanish, and it's pretty painful. In fact, 3-em after period old English is quite readable. - "2-spacers are just imitating previous writers; they don't know what they're doing". Imitating wise old customs without knowing the rationale is not bad per se. Deviating from them without a rationale is even worse. ... Cheers, Alex But maybe "kibibyte" is more than a shibboleth to somebody somewhere... -- <http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5 OpenPGP_signature Description: OpenPGP digital signature
Re: [PATCH v3 1/6] man2/: use IEC or ISO multiples to clarify long numeric digit strings
On 2/20/23 15:29, Stefan Puiu wrote: Hi Alex, Hi Stefan, 4 KiB is not that much better than 4096, since 4096 is easy to read. For higher numbers such as 33554432, it becomes more important to use 32 KiB. For consistency, using 4 KiB seems reasonable. How about using KiB / MiB over a certain number of digits? It seems excessive to use them everywhere. We might do that. So far, I prefer having the patches change everything, and then we can later discuss about discarding part of them. Also, for the record, I had no idea what KiB / MiB means and how it's different from KB/MB until this discussion. I googled it before writing this reply, and found this among the first hits: https://ux.stackexchange.com/a/13850. That answer was written more than a decade ago. These days, binary prefixes are more common. In fact, I'd say most GNU/Linux commands respect them (an important exception being GNU coreutils (for example ls(1)). But many programs use prefixes accurately, such as fdisk(8). In the Linux man-pages we have units(7), which documents these. Maybe that page should be more known. BTW, that answer is inaccurate (at least today): drive manufacturers have the distinction pretty clear, and use it precisely (with lawsuits won thanks to this); they use metric prefixes, because they mean it. They can sell you 1 TB instead of 1 TiB, and most people won't even know, but those who know, will know that 1 TB is 1'000'000'000'000 B, which is what you get. They have no incentives to sell 1 TiB drives, because they are visually almost the same, but there's around 9.95% more bytes, so it's more expensive to produce. It's not worth it for them. I would say making the docs easy to understand for users is more important than adhering to some specs users might not be familiar with. Well, using MiB prompts readers to use their search engine to learn what that is (that's how I learnt it the first time; and that's what one does when reading a book and finding a new word). I think that shouldn't be considered an impediment, but an opportunity to learn something new. Once you know the difference, you appreciate the preciseness. I hate when I see some software that uses the metric prefixes for meaning binary multipliers. I also hate software that operates on bytes, when you almost always want binary multipliers but only have metric multipliers (hey partman, I mean you!). I reported a bug to the Debian installer recently because it's very painful to partition a drive from it. Cheers, Alex -- <http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5 OpenPGP_signature Description: OpenPGP digital signature
Re: hello, issue with grub and os-prober
sorry i mistypoed PROBER for PROPER fixed On Sat, Feb 19, 2022, 16:58 Alex fxmbsw7 Ratchev wrote: > ive helped a fella install and update debian > but then os-prober wont run, for his windows partition > we added GRUB_DISABLE_OS_PROBER=false to /etc/default/grub without effect > > see termux ssh screenshots of both >
Re: Bug#1004452: bullseye-pu: package gnupg2/2.2.27-2+deb11u1
but yes its a 5 tree debian, oldstable stable testing unstable experimental On Sat, Feb 19, 2022, 18:10 Adam D. Barratt wrote: > Control: tags -1 + confirmed d-i > > On Thu, 2022-01-27 at 17:02 -0500, Daniel Kahn Gillmor wrote: > > Please consider an update to GnuPG in debian bullseye, from version > > 2.2.27-2 to 2.2.27-2+deb11u1. > > > > The version mentioned above is correct, but the proposed changelog is > not: > > +gnupg2 (2.2.27-2+deb11+1) bullseye; urgency=medium > > (it should be "deb11u1", not "deb11+1"). > it is unstable / experimental > > > The fixes, by Christoph Biedel and Raphaël Hertzog, are narrowly > > targeted and fix real, significant issues that a subset of users > > have. > > They have been in debian unstable and testing for a while now without > > issue: > > > > -- > > [ Raphaël Hertzog ] > > * Avoid network interaction in generator. Closes: #993578 > > > > [ Christoph Biedl ] > > * Backport "Scd: Fix CCID driver for SCM SPR332/SPR532". Closes: > > #982546 > > -- > > > > The debdiff from the version in bullseye (2.2.27-2) is attached. > > Thanks. > > That looks fine to me, but will need a d-i ack as the package builds a > udeb; tagging and CCing accordingly. > these doesnt tell me anythjng, im no debian dev > > Regards, > > Adam > >
Bug#999567: severity
Dear maintainer, My corporate IT nags me with this CVE, and other distros have already fixed it (Fedora, SUSE, Ubuntu). Yet it seems nothing happens here. I had to build and install the current version from salsa, but I don't believe this is how things are supposed to be. Do you confirm that this bug is important to you or do you think it's so minor that it can be ignored? My colleagues are also bothered by the IT, but we can file an exception for this instead of building our own versions, and a rationale from you might be helpful to all of us. Have a nice day, Alex Thiessen
Re: What's missing for arm64 Xen boot with FDT via Grub in Debian Bullseye?
Julien Grall writes: > On 28/05/2021 13:49, Alex Bennée wrote: >> Hi, > > Hi Alex, > >> I'm currently trying to pull together the threads for booting Xen on >> Debian. I'm currently doing this within QEMU's TCG emulation and the >> "virt" machine model: >>-machine type=virt,virtualization=on,gic-version=3 \ >>-cpu max,pauth-impdef=on >> with the firmware on my Ubuntu machine: >>-drive >> if=pflash,file=/usr/share/AAVMF/AAVMF_CODE.fd,format=raw,readonly=on >> -drive if=pflash,file=$HOME/images/AAVMF_VARS.fd,format=raw >> (qemu-efi-aarch64 Version: 0~20180205.c0d9813c-2ubuntu0.3) >> When booting this way I get the Grub menu and Xen is loaded by Grub >> but >> falls over later: >>(XEN) MODULE[0]: f5869000 - f59b60c8 Xen >>(XEN) MODULE[1]: 00013857d000 - 00013858 Device Tree >>(XEN) MODULE[2]: f73a1000 - f8da0780 Kernel >>(XEN) MODULE[3]: f59b7000 - f739f99b Ramdisk >>(XEN) >>(XEN) CMDLINE[f73a1000]:chosen placeholder >> root=UUID=435201aa-c5cf-4e7a-8107-5eef28844188 ro console=hvc0 >>(XEN) >>(XEN) Command line: placeholder dom0_mem=2G loglvl=all guest_loglvl=all >> no-real-mode edd=off >>(XEN) parameter "placeholder" unknown! >>(XEN) parameter "no-real-mode" unknown! >>(XEN) parameter "edd" unknown! >>(XEN) Domain heap initialised >>(XEN) Booting using Device Tree >>(XEN) Platform: Generic System >>(XEN) >>(XEN) >>(XEN) Panic on CPU 0: >>(XEN) Unable to find a compatible timer in the device tree >>(XEN) >> It seems like there are bits of the DT missing. I can however >> successfully boot Xen with the Linux guest using the guest-loader device >> and bypassing the firmware/boot code step. This gives: >>(XEN) MODULE[0]: 4020 - 4034d0c8 Xen >>(XEN) MODULE[1]: 4800 - 4810 Device Tree >>(XEN) MODULE[2]: 4600 - 46eb2200 Kernel >>(XEN) >>(XEN) CMDLINE[4600]:chosen root=/dev/sda2 console=hvc0 >> earlyprintk=xen >>(XEN) >>(XEN) Command line: dom0_mem=4G dom0_max_vcpus=4 >>(XEN) Domain heap initialised >>(XEN) Booting using Device Tree >>(XEN) Platform: Generic System >>(XEN) Taking dtuart configuration from /chosen/stdout-path >>(XEN) Looking for dtuart at "/pl011@900", options "" >> Xen 4.15.1-pre >>(XEN) Xen version 4.15.1-pre (alex.bennee@) (aarch64-linux-gnu-gcc >> (Debian 8.3.0-2) 8.3.0) debug=y Tue May 18 09:34:55 UTC 2021 >>(XEN) Latest ChangeSet: >>(XEN) build-id: a50d8f03a1a15662ac7c4e5f73f2f544a6739df2 >>(XEN) Processor: 411fd070: "ARM Limited", variant: 0x1, part 0xd07, rev >> 0x0 >>(XEN) 64-bit Execution: >>(XEN) Processor Features: 01000222 >>(XEN) Exception Levels: EL3:No EL2:64+32 EL1:64+32 EL0:64+32 >>(XEN) Extensions: FloatingPoint AdvancedSIMD GICv3-SysReg >>(XEN) Debug Features: 10305106 >>(XEN) Auxiliary Features: >>(XEN) Memory Model Features: 1124 >>(XEN) ISA Features: 00011120 >>(XEN) 32-bit Execution: >>(XEN) Processor Features: 0131:10011001 >>(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle >>(XEN) Extensions: GenericTimer >>(XEN) Debug Features: 03010066 >>(XEN) Auxiliary Features: >>(XEN) Memory Model Features: 10101105 4000 0126 02102211 >>(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121 >>(XEN) Using SMC Calling Convention v1.0 >>(XEN) Using PSCI v0.2 >>(XEN) SMP: Allowing 8 CPUs >>(XEN) enabled workaround for: ARM erratum 832075 >>(XEN) enabled workaround for: ARM erratum 834220 >>(XEN) enabled workaround for: ARM erratum 1319367 >>(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 62500 KHz >>(XEN) GICv3 initialization: >>(XEN) gic_dist_addr=0x000800 >>(XEN) gic_maintenance_irq=25 >>(XEN) gic_rdist_stride=0 >>(XEN) gic_rdist_regions=1 >>(XEN) redistributor regions: >>(XEN) - region 0: 0x00080a - 0x0
What's missing for arm64 Xen boot with FDT via Grub in Debian Bullseye?
-loader,addr=0x4600,kernel=$HOME/lsrc/linux.git/builds/arm64/arch/arm64/boot/Image,bootargs="root=/dev/sda2 console=hvc0 earlyprintk=xen" \ -smp 8 So some questions: - is Xen on arm64 tested on Debian Bullseye? If so what platform? - how do I tell Grub to do a straight FDT boot with the DT from the firmware? - are there any missing pieces I should be aware of? I appreciate that ACPI is the preferred enterprise way of booting but at the moment I think FDT is probably preferred because: - lack of real HW with decent ACPI (my MachiatoBin only boots with DT) - I want to try additional hypervisors who don't have ACPI aware implementations That said if I can get an ACPI version of Xen booting via Grub that would be an improvement. -- Alex Bennée
Bug#833706: this is not solved
On Fri, 22 Feb 2019 07:36:37 +0100 spambox wrote: > i stumbled on the same bug in a PXE based installation on vmware > > the console displays a segfault and "error 4 in libc-2.23.so" >From your screenshot it looks like Ubuntu you are installing - we hit this >exact issue with Ubuntu 16.04 (Xenial), when using the original netboot image. >It seems there is some sort of conflict between that and the latest libc6-udeb >package the installer retrieves (from xenial-updates). Using the latest netboot image from xenial-updates resolved things for us, so I'd suggest ensuring whatever you're using to boot the installer is up to date. Alex
Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer
> It seems libzstd 1.3.5+dfsg-2 hasn't yet reached the archive. Maybe > it was not uploaded, or maybe it was rejected for some reason? > > > https://salsa.debian.org/med-team/libzstd/commit/9b865b77d2bfc41c5865f255cf3e4aae18bbe934 > > Thanks you for working on this! > Nicholas Hi Nicholas, it is in the new queue: https://ftp-master.debian.org/new/libzstd_1.3.5+dfsg-2.html We just need to wait or ?
Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer
Hi,
On 10/11/2018 10:42 PM, Cyril Brulebois wrote:
> Hi,
>
> And thanks for checking with us (explicit Cc's welcome, by the way).
Ok, will do in the future.
>
> From a quick look at debian/control:
>> Package: libzstd1-udeb
>> Architecture: any
>> Multi-Arch: same
>
> This field isn't needed for d-i.
>
>> Section: debian-installer
>> Depends: ${misc:Depends},
>> ${shlibs:Depends}
>> Package-Type: udeb
>> Description: fast lossless compression algorithm
>> Zstd, short for Zstandard, is a fast lossless compression algorithm,
>> targeting
>> real-time compression scenarios at zlib-level compression ratio.
>> .
>> This package contains the shared library.
>> .
>> This is a minimal package for debian-installer.
>
> FWIW: A single-line description is sufficient in a d-i context.
>
>
> From a quick look at debian/rules, a real issue:
>> override_dh_makeshlibs:
>> dh_makeshlibs -plibzstd1 -V'libzstd1 (>=1.3.5)'
>> --add-udeb=libzstd-udeb
>
> You're passing libzstd-udeb to --add-udeb, while the actual package is
> called libzstd1-udeb, so the generated shlibs file (see DEBIAN/shlibs in
> your build tree) will point to a package that doesn't exist, generating
> dependencies that can be satisfied for udebs using symbols from libzstd.
>
> [I'm used to seeing a space after '>=' but apparently having no space
> seems supported as well:
> (sid-amd64-devel)kibi@armor:~/hack/libzstd$ grep '>='
> /var/lib/dpkg/info/*shlibs | grep -v '>= '
> /var/lib/dpkg/info/libgcrypt20:amd64.shlibs:libgcrypt 20 libgcrypt20
> (>=1.8.0-0)
> /var/lib/dpkg/info/libgcrypt20:amd64.shlibs:udeb: libgcrypt 20
> libgcrypt20-udeb (>=1.8.0-0)
> /var/lib/dpkg/info/libprocps6:amd64.shlibs:libprocps 6 libprocps6
> (>=2:3.3.13-1)
> /var/lib/dpkg/info/libprocps7:amd64.shlibs:libprocps 7 libprocps7
> (>=2:3.3.15-1)
> /var/lib/dpkg/info/libtasn1-6:amd64.shlibs:libtasn1 6 libtasn1-6 (>=4.7-0)
> ]
>
> Other than that, the resulting udeb after a binary build looks OK to me.
>
>
> Cheers,
>
Fixed all the mentioned above issues in the repository.
Thank you for the detailed answer!
Alex
signature.asc
Description: OpenPGP digital signature
Re: Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer
On 10/09/2018 07:39 PM, Nicholas D Steeves wrote: > Control: retitle -1 please build libzstd udeb so that btrfs-progs can use > zstd in Debian Installer > Control: reassign -1 src:libzstd/ 1.3.5+dfsg-1 Done, dropped zstd-udeb. > > Please read what Cyril (Debian Installer Team) wrote at these bugs in > case these questions have already been answered: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898410 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886968 Thank you, that was useful. I've updated the libzstd repository[0]. @Kibi, could you please review that? basically I just call dh_makeshlibs with -V'libzstd1 (>=1.3.5)' as there are new symbols introduced in this version. Thank you, Alex [0] https://salsa.debian.org/med-team/libzstd/ signature.asc Description: OpenPGP digital signature
Re: [Debian-med-packaging] Bug#908834: please build zstd udeb so that btrfs-progs can use zstd in Debian Installer
On 10/09/2018 04:32 PM, Dimitri John Ledkov wrote: > is o > On Tue, 9 Oct 2018 at 12:23, Alex Mestiashvili > wrote: >> >> On 09/14/2018 08:04 PM, Nicholas D Steeves wrote: >>> Package: zstd >>> Version: 1.3.5+dfsg-1 >>> Severity: wishlist >>> >>> Dear Debian Med Packaging Team, >>> >>> Would you please build a zstd udeb so that btrfs-progs can use zstd in >>> Debian Installer and Rescue System? It uses zstd for transparent >>> filesystem compression. >>> >>> eg: `chattr +c`, or `btrfs filesystem defrag -c`, or via a mount >>> option `compress=zstd`. I believe the first and last of these use the >>> kernel's libzstd, and that the udeb is primarily required for >>> `btrfs-repair` to handle zstd extents in the Rescue System. Also, please >>> continue to CC Dmitri Ledkov, Debian's btrfs-progs maintainer. >>> >>> Cheers, >>> Nicholas >>> >>> ___ >>> Debian-med-packaging mailing list >>> debian-med-packag...@alioth-lists.debian.net >>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging >>> >> >> >> As far as I see it's enough to add udeb stanzas in d/control in order to >> build the udebs[0]. >> Is there anything else to consider before uploading lisbzstd with udebs? >> > > No, that's not at all enough. It ends up creating two empty packages, > without any files in them. Oh, I see. I thought there is some debhelper magic involved and didn't check the generated packages.. > > One needs to actually install a library into the library udeb and > tools into tools-udeb. > Note for fbtrfs only library-udeb is needed. Does that also apply for btrfs-repair? Initial bug report is about zstd udeb as I see. > > Maybe > https://patches.ubuntu.com/libz/libzstd/libzstd_1.3.5+dfsg-1ubuntu1.patch > is of help That's clear now. Thank you. > > Also do get it reviewed, as last time unwritten rules w.r.t. udebs got > enforced and above patch was rejected on ground of not strict enough > alternative shlibs deps generated. Thank you for clarifying, but I didn't understand the reason of reject :). > > Please figure out what's missing before uploading to avoid a reject again. I've pushed quite the same changes as yours to zstd repository now. @debian-boot folks, please review and please either fix it or explain what is required. Are there any udeb related docs available? Thank you, Alex
Re: [Debian-med-packaging] Bug#908834: please build zstd udeb so that btrfs-progs can use zstd in Debian Installer
On 09/14/2018 08:04 PM, Nicholas D Steeves wrote: > Package: zstd > Version: 1.3.5+dfsg-1 > Severity: wishlist > > Dear Debian Med Packaging Team, > > Would you please build a zstd udeb so that btrfs-progs can use zstd in > Debian Installer and Rescue System? It uses zstd for transparent > filesystem compression. > > eg: `chattr +c`, or `btrfs filesystem defrag -c`, or via a mount > option `compress=zstd`. I believe the first and last of these use the > kernel's libzstd, and that the udeb is primarily required for > `btrfs-repair` to handle zstd extents in the Rescue System. Also, please > continue to CC Dmitri Ledkov, Debian's btrfs-progs maintainer. > > Cheers, > Nicholas > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > As far as I see it's enough to add udeb stanzas in d/control in order to build the udebs[0]. Is there anything else to consider before uploading lisbzstd with udebs? Thank you, Alex [0] https://salsa.debian.org/med-team/libzstd/commit/3cb048aab364b5fca41d0c2feb7cdf943786cee4 signature.asc Description: OpenPGP digital signature
[PATCH] scripts/gusty: move /proc symlink logic to stage_one
This affects all post gutsy Ubuntu releases and now more closely
mirrors the behaviour in debian-common. The recent changes to
container detection broke QEMU's debootstrap for Ubuntu guests as
setup_proc_symlink would attempt to delete the real containerised
/proc in a stage 2 context causing the bootstrap to fail.
I've added in_target /bin/true to more closely align, it's simply a
check to ensure stage two can execute commands. There is probably
scope for more re-factoring as the remaining differences are mostly
dealing with code names, mirror locations and some minor and possibly
out of date init differences.
Signed-off-by: Alex Bennée
---
scripts/gutsy | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/scripts/gutsy b/scripts/gutsy
index c3e44fc..b460e90 100644
--- a/scripts/gutsy
+++ b/scripts/gutsy
@@ -91,9 +91,15 @@ first_stage_install () {
fi
setup_devices
+
+if doing_variant fakechroot || [ "$CONTAINER" = "docker" ]; then
+ setup_proc_symlink
+ fi
}
second_stage_install () {
+ in_target /bin/true
+
setup_dynamic_devices
x_feign_install () {
@@ -122,9 +128,7 @@ Status: install ok installed" >>
"$TARGET/var/lib/dpkg/status"
baseprog="$(($baseprog + ${1:-1}))"
}
- if doing_variant fakechroot || [ "$CONTAINER" = "docker" ]; then
- setup_proc_symlink
- else
+ if ! doing_variant fakechroot; then
setup_proc
in_target /sbin/ldconfig
fi
--
2.17.1
Bug#903657: debootstrap checks for existence of wget on --second-stage, breaking --foreign bootstraps
Package: debootstrap Version: 1.0.95ubuntu0.1 Severity: important Dear Maintainer, QEMU's build system has support for debootstrap using binfmt_misc and QEMU's linux-user emulation. Since commit 9a6ebf628 this is broken as it checks for the presence of wget which isn't available in the second-stage environment. If the user is doing a --second-stage it shouldn't matter that wget is missing as all the packages have already been downloaded on the host system. For reference the wrapper script is: https://git.qemu.org/?p=qemu.git;a=blob;f=tests/docker/dockerfiles/debian-bootstrap.pre;h=56e1aa7a21418437b5b0fbaf473a8686338d9014;hb=cee35138b59c6d6b0808c5fa644e3f063832860f And you should be able to debootstrap on QEMU's master with a line like: make docker-binfmt-image-debian-ubuntu-xenial-arm64 DEB_ARCH=arm64 \ DEB_TYPE=xenial DEB_URL=http://ports.ubuntu.com EXECUTABLE=./aarch64-linux-user/qemu-aarch64~ There is also a bug in QEMU's own script which means it always falls back to the SCM version of debootstrap, but that is mine to fix ;-) -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, armhf Kernel: Linux 4.15.0-24-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.19.4-1ubuntu2.1 Versions of packages debootstrap recommends: ii gnupg 2.2.4-1ubuntu1.1 ii ubuntu-keyring 2018.02.28 Versions of packages debootstrap suggests: pn ubuntu-archive-keyring -- no debconf information
Re: Beginner question - stable installer build fails - why?
On 28/01/18 12:51, Cyril Brulebois wrote: Alex King <a...@king.net.nz> (2018-01-28): I wanted to build a net installer that would load stable (actually jessie but I'll start with stable) but using a recent kernel. Firstly I went to https://wiki.debian.org/DebianInstaller#Development and https://wiki.debian.org/DebianInstaller/CheckOut I checked out the dev version using Anonymous checkout instructions and was reading... "If you just want to build bootable images, see d-i/installer/build/README" So I was reading that README and realised that I probably wanted to build from stable not the development version, so I followed the instructions in there starting with "apt-get source debian-installer", the rest you can see in my original message. Now that I see Cyril's message it makes sense to use dpkg-buildpackage. I don't build debian packages every day so I am not really familiar with all the normal tools/workflow of a debian developer. Now I am reading https://wiki.debian.org/DebianInstaller/Build, which my browser tells me I read before (maybe a while ago.) I see that has the advice to use dpkg-buildpackage. Probably a note about dpkg-buildpackage and/or debian/rules could go in build/README? dpkg-buildpackage and debian/rules are the standard interface to building Debian packages, so there's very little point in mentioning that specifically. Also, build/README contains this: | Recipe: | - Install the build-dependencies on the host system |(run dpkg-checkbuilddeps in the parent installer/ directory). | - Create your own sources.list.udeb.local, otherwise the build host's |sources.list is taken as a template for sources.list.udeb. | - Run "make" to get a list of available targets. | - Build an image using one of the build_ targets (build_netboot, |all_build, etc). You may want to set the USE_UDEBS_FROM variable, |documented below. | - Look in dest/ for the completed images. and the documentation of USE_UDEBS_FROM points to debian/rules already. Cheers, Yes, I was following those instructions. How about this? Thanks, Alex diff --git a/build/README b/build/README index 90b73bcc0..76b31f706 100644 --- a/build/README +++ b/build/README @@ -17,7 +17,8 @@ Recipe: - Run "make" to get a list of available targets. - Build an image using one of the build_ targets (build_netboot, all_build, etc). You may want to set the USE_UDEBS_FROM variable, - documented below. + documented below. (Setting USE_UDEBS_FROM is requried for building a + released version, e.g. stable or oldstable) - Look in dest/ for the completed images. Note that this does not create full debian ISO images; that is left to the
Re: Beginner question - stable installer build fails - why?
Indeed that worked very well and resulted in a successful build, thank you. My next steps: * Follow https://lists.debian.org/debian-boot/2017/12/msg00375.html to build with a backports kernel. * Try to do the same with Jessie, which is what my customer actually wants. * Make whatever changes necessary so the backport kernel is installed in the installed system as well as the installer. If that works maybe set up a regular build and put that up on http for people to use. I.e. stable/oldstable netboot with backport kernels. I think there would be interest in that for people trying to get older versions on latest hardware, which is my use case. Thanks again, Alex On 28/01/18 06:02, Cyril Brulebois wrote: Hi, Alex King <a...@king.net.nz> (2018-01-27): I'm trying to build an installer following build/README, but must have something basic wrong. So far I have: * apt-get source debian-installer * Install the build-dependencies on the host system * (did not install a sources list as I'm happy with the system one) * make build_netboot If you're going to build using make under build/ directly, you need to pass a few variables to get appropriate settings. You're lacking at least USE_UDEBS_FROM, which defaults to unstable: build/config/common:USE_UDEBS_FROM ?= unstable This should work (provided you start from a clean tree): make -C build build_netboot USE_UDEBS_FROM=stretch Alternatively, use dpkg-buildpackage, so that debian/rules sets the appropriate variables for you. $ cat sources.list.udeb # This file is automatically generated, edit sources.list.udeb.local instead. deb [trusted=yes] copy:/home/developer/debian-installer-20170615+deb9u2/build/ localudebs/ deb http://deb.debian.org/debian unstable main/debian-installer deb http://ftp.debian.org/debian unstable main/debian-installer → unstable instead of stretch, as expected. $ apt-cache search virtio-modules-4.9.0-4-amd64-di (nothing) That's expected given your sources.list: no main/debian-installer component there, so apt doesn't know about those udebs. Try rmadison (from devscripts) instead. By the way, there's a bump from 4.9.0-4 to 4.9.0-5 coming up through stretch-proposed-updates. I've pushed an updated to the stretch branch accordingly: https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?id=71c369f53351dab573d153cda41ee26351a85564 Cheers,
Re: Beginner question - stable installer build fails - why?
Hi, thanks for your help, see below regarding documentation. On 28/01/18 00:52, Geert Stappers wrote: On Sat, Jan 27, 2018 at 11:38:54AM +1300, Alex King wrote: I'm trying to build an installer following build/README, but must have something basic wrong. So far I have: * apt-get source debian-installer * Install the build-dependencies on the host system * (did not install a sources list as I'm happy with the system one) * make build_netboot I would have start with make And upon success make build_netboot This fails with lots of missing udebs: ... E: Couldn't find any package by regex 'virtio-modules-4.9.0-4-amd64-di' Makefile:633: recipe for target 'stamps/get_udebs-netboot-stamp' failed make[2]: *** [stamps/get_udebs-netboot-stamp] Error 100 Makefile:288: recipe for target '_build' failed make[1]: *** [_build] Error 2 Makefile:282: recipe for target 'build_netboot' failed make: *** [build_netboot] Error 2 $ cat /etc/apt/sources.list deb http://deb.debian.org/debian stretch main deb-src http://deb.debian.org/debian stretch main deb http://ftp.debian.org/debian stretch-backports main deb-src http://ftp.debian.org/debian stretch-backports main $ cat sources.list.udeb # This file is automatically generated, edit sources.list.udeb.local instead. deb [trusted=yes] copy:/home/developer/debian-installer-20170615+deb9u2/build/ localudebs/ deb http://deb.debian.org/debian unstable main/debian-installer deb http://ftp.debian.org/debian unstable main/debian-installer $ apt-cache search virtio-modules-4.9.0-4-amd64-di (nothing) $ grep virtio-modules-4.9.0-4-amd64-di /var/lib/apt/lists/* /var/lib/apt/lists/deb.debian.org_debian_dists_stretch_main_source_Sources: multipath-modules-4.9.0-4-amd64-di, usb-modules-4.9.0-4-amd64-di, usb-storage-modules-4.9.0-4-amd64-di, pcmcia-storage-modules-4.9.0-4-amd64-di, fb-modules-4.9.0-4-amd64-di, input-modules-4.9.0-4-amd64-di, event-modules-4.9.0-4-amd64-di, mouse-modules-4.9.0-4-amd64-di, nic-pcmcia-modules-4.9.0-4-amd64-di, pcmcia-modules-4.9.0-4-amd64-di, nic-usb-modules-4.9.0-4-amd64-di, sata-modules-4.9.0-4-amd64-di, acpi-modules-4.9.0-4-amd64-di, i2c-modules-4.9.0-4-amd64-di, crc-modules-4.9.0-4-amd64-di, crypto-modules-4.9.0-4-amd64-di, crypto-dm-modules-4.9.0-4-amd64-di, efi-modules-4.9.0-4-amd64-di, ata-modules-4.9.0-4-amd64-di, mmc-core-modules-4.9.0-4-amd64-di, mmc-modules-4.9.0-4-amd64-di, nbd-modules-4.9.0-4-amd64-di, squashfs-modules-4.9.0-4-amd64-di, speakup-modules-4.9.0-4-amd64-di, virtio-modules-4.9.0-4-amd64-di, uinput-modules-4.9.0-4-amd64-di, sound-modules-4.9.0-4-amd64-di, hyperv-modules-4.9.0-4-amd64-di, udf-modules-4.9.0-4-amd64-di, fuse-modules-4.9.0-4-amd64-di, /var/lib/apt/lists/deb.debian.org_debian_dists_stretch_main_source_Sources: virtio-modules-4.9.0-4-amd64-di udeb debian-installer extra arch=amd64 profile=!stage1 So maybe those are available in sources but not as binary packages? What am I doing wrong? } What should I do? Tell which documentation is being used. So that it can become clear what should be changed. ( the documentation or the steps sofar done ) I wanted to build a net installer that would load stable (actually jessie but I'll start with stable) but using a recent kernel. Firstly I went to https://wiki.debian.org/DebianInstaller#Development and https://wiki.debian.org/DebianInstaller/CheckOut I checked out the dev version using Anonymous checkout instructions and was reading... "If you just want to build bootable images, see d-i/installer/build/README" So I was reading that README and realised that I probably wanted to build from stable not the development version, so I followed the instructions in there starting with "apt-get source debian-installer", the rest you can see in my original message. Now that I see Cyril's message it makes sense to use dpkg-buildpackage. I don't build debian packages every day so I am not really familiar with all the normal tools/workflow of a debian developer. Now I am reading https://wiki.debian.org/DebianInstaller/Build, which my browser tells me I read before (maybe a while ago.) I see that has the advice to use dpkg-buildpackage. Probably a note about dpkg-buildpackage and/or debian/rules could go in build/README? Cheers, Alex Groeten Geert Stappers
Beginner question - stable installer build fails - why?
I'm trying to build an installer following build/README, but must have something basic wrong. So far I have: * apt-get source debian-installer * Install the build-dependencies on the host system * (did not install a sources list as I'm happy with the system one) * make build_netboot This fails with lots of missing udebs: ... E: Couldn't find any package by regex 'virtio-modules-4.9.0-4-amd64-di' Makefile:633: recipe for target 'stamps/get_udebs-netboot-stamp' failed make[2]: *** [stamps/get_udebs-netboot-stamp] Error 100 Makefile:288: recipe for target '_build' failed make[1]: *** [_build] Error 2 Makefile:282: recipe for target 'build_netboot' failed make: *** [build_netboot] Error 2 $ cat /etc/apt/sources.list deb http://deb.debian.org/debian stretch main deb-src http://deb.debian.org/debian stretch main deb http://ftp.debian.org/debian stretch-backports main deb-src http://ftp.debian.org/debian stretch-backports main $ cat sources.list.udeb # This file is automatically generated, edit sources.list.udeb.local instead. deb [trusted=yes] copy:/home/developer/debian-installer-20170615+deb9u2/build/ localudebs/ deb http://deb.debian.org/debian unstable main/debian-installer deb http://ftp.debian.org/debian unstable main/debian-installer $ apt-cache search virtio-modules-4.9.0-4-amd64-di (nothing) $ grep virtio-modules-4.9.0-4-amd64-di /var/lib/apt/lists/* /var/lib/apt/lists/deb.debian.org_debian_dists_stretch_main_source_Sources: multipath-modules-4.9.0-4-amd64-di, usb-modules-4.9.0-4-amd64-di, usb-storage-modules-4.9.0-4-amd64-di, pcmcia-storage-modules-4.9.0-4-amd64-di, fb-modules-4.9.0-4-amd64-di, input-modules-4.9.0-4-amd64-di, event-modules-4.9.0-4-amd64-di, mouse-modules-4.9.0-4-amd64-di, nic-pcmcia-modules-4.9.0-4-amd64-di, pcmcia-modules-4.9.0-4-amd64-di, nic-usb-modules-4.9.0-4-amd64-di, sata-modules-4.9.0-4-amd64-di, acpi-modules-4.9.0-4-amd64-di, i2c-modules-4.9.0-4-amd64-di, crc-modules-4.9.0-4-amd64-di, crypto-modules-4.9.0-4-amd64-di, crypto-dm-modules-4.9.0-4-amd64-di, efi-modules-4.9.0-4-amd64-di, ata-modules-4.9.0-4-amd64-di, mmc-core-modules-4.9.0-4-amd64-di, mmc-modules-4.9.0-4-amd64-di, nbd-modules-4.9.0-4-amd64-di, squashfs-modules-4.9.0-4-amd64-di, speakup-modules-4.9.0-4-amd64-di, virtio-modules-4.9.0-4-amd64-di, uinput-modules-4.9.0-4-amd64-di, sound-modules-4.9.0-4-amd64-di, hyperv-modules-4.9.0-4-amd64-di, udf-modules-4.9.0-4-amd64-di, fuse-modules-4.9.0-4-amd64-di, /var/lib/apt/lists/deb.debian.org_debian_dists_stretch_main_source_Sources: virtio-modules-4.9.0-4-amd64-di udeb debian-installer extra arch=amd64 profile=!stage1 So maybe those are available in sources but not as binary packages? What am I doing wrong? Thanks, Alex
Re: How to install a stable system with a backport kernel
On 25/01/18 18:50, Cyril Brulebois wrote: Hi Alex, Alex King <a...@king.net.nz> (2018-01-25): I need to install a stable system, but with a kernel from backports (or testing). I am using netboot. The system needs drivers from a more modern kernel than what's in stable to access its disks. Currently the only way I can see to install this system is to use another (non debian installer) method, such as fai or installing a testing system on a small partition and using that to debootstrap the system I want. For various reasons both are not ideal. Here are some ways I can think of to solve this problem: 1. Use an installer compiled with a backport kernel. This does not exist to my knowledge, but if anyone can point me to a netboot.tar.gz that does this I would be happy. On this list, a few weeks ago: https://lists.debian.org/debian-boot/2017/12/msg00365.html Cheers, Apologies i had not seen that despite google and some browsing in the archives. That would be ideal. Let me know if there is anything I can do to help with the effort there. This is a problem I've come across before and likely will again. I'd prefer to contribute to a more durable and public solution rather than just finding a quick workaround. I will likely follow up on jhcha54008's work at https://lists.debian.org/debian-boot/2017/12/msg00375.html and I'll post back here if I come up with anything useful. Thanks, Alex
How to install a stable system with a backport kernel
I need to install a stable system, but with a kernel from backports (or testing). I am using netboot. The system needs drivers from a more modern kernel than what's in stable to access its disks. Currently the only way I can see to install this system is to use another (non debian installer) method, such as fai or installing a testing system on a small partition and using that to debootstrap the system I want. For various reasons both are not ideal. Here are some ways I can think of to solve this problem: 1. Use an installer compiled with a backport kernel. This does not exist to my knowledge, but if anyone can point me to a netboot.tar.gz that does this I would be happy. 2. Use the testing installer, but pass --release stretch or --release stretch-backports to the installer. This does not work, the installer complains it can't find kernel modules. Even if booted with an appropriate monolithic kernel (I tried), this doesn't work. 3. Run the testing installer, but swap the release to stretch at the start of the install the base system stage. Any hints on how to do that? I see the following in choose-mirror.postinst: # If a -support udeb is available for the selected release, install it # This will mostly be used to preserve backwards compatibility with stable if db_get mirror/codename && [ "$RET" ]; then anna-install $RET-support || true fi But it seems using the net installer, there is no way to run with a --release that is not the same version as the installer. Perhaps we need a --installer-release and --target-release? All ideas welcome. Thanks, Alex
Bug#846256: failure on boot
> 2. If they finish in time, this is ok. Suppose however that >systemd-tmpfiles-setup starts before the scripts of console-setup >finish their work. (Is this possible?) Yes. We have seen this happen. Although it being a race condition, it's hard to reproduce, and we've only seen it happen on at least 8 core servers. > It wourld be preferable if there were a directive to tell systemd not to > run systemd-tmpfiles-setup during the execution of console-setup. Putting systemd-tmpfiles-setup in the "After" stanza of the console-setup unit file would fix the bug. At least since we've done this on our internal fork, we haven't seen the bug. Regards, Alex Badics
Bug#846256: failure on boot
Hi, We also encountered the bug, and to me, it seems to be caused by the systemd-tmpfiles-setup.service, shown as "Create Volatile Files and Directories". This is because /tmp is listed as "D" in /usr/lib/tmpfiles.d/tmp.conf, which means its contents gets removed when /bin/systemd-tmpfiles --remove is called, and the service files does exactly that. You might see it in your journal that the bug only happens if console-setup is started before systemd-tmpfiles-setup. I think not having "DefaultDependencies=no" in setup-console's unit file or explicitly having systemd-tmpfiles-setup in After would solve the problem. Also, isn't Bug#818065 a duplicate of this? Regards, Alex Badics
Bug#861065: please add gnustep
Package: tasksel
Version: 3.39
Severity: wishlist
Please add tasks/gnustep-desktop
Task: gnustep-desktop
Section: user
Parent: desktop
Relevance: 8
Test-default-desktop: 3 gnustep
Key:
task-gnustep-desktop
And debian/control:
Package: task-gnustep-desktop
Architecture: all
Description: GNUstep
This task package is used to install the Debian desktop, featuring
the GNUstep desktop environment, and with other packages that Debian
users
expect to have available on the desktop.
Depends: ${misc:Depends},
task-desktop,
gnustep-games,
gnustep-examples,
gnustep,
gnustep-devel,
wdm
Thank you
A bugreport for live-tasks is following...
Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut
Slightly off-topic here, but *please* don't use Virtualbox for testing with EFI. The virtualbox EFI support is half-assed and broken and will cause problems later. What alternative do you advise me? You've missed out the "down arrow three times" here - with that it works, I've just tested myself You're completely right. It works right now :). Could we imagine to have an alternative way? If you implement tab to jump the cursor on the install parameter (so the same as e and three times down arrow) we could reduced significantly the complexity of the steps for a beginner. I remember you all the steps are done without any screen feedback so like a blind person. Best regards. -- Alex ARNAUD Visual-Impairment Project Manager Hypra - "Humanizing technology"
Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut
Le 15/01/2017 à 16:46, Samuel Thibault a écrit : Hello Alex, Hello Samuel « If you wish or need to add any boot parameters for either the installer or the kernel, press Tab (BIOS boot), or 'e' then down arrow three times then 'end' (UEFI boot). This will bring the boot command for the selected menu entry and allow you to edit it to suit your needs. The help screens (see below) list some common possible options. Press 'Enter' (BIOS boot) or 'F10' (UEFI boot) to boot the installer with your options; pressing Esc will return you to the boot menu and undo any changes you made. » Is this enough for your needs? I'm not able to confirm that the instructions you have provided work for me. My test environment is a Virtualbox (5.1) machine with EFI enabled. I have executed the following steps : 1) Pressing "e" 2) Pressing the "end" key 3) Typing "theme=dark" 4) Pressing F10 The installation begins after that steps without the dark theme as I would like to have. Best regards. -- Alex ARNAUD Visual-Impairment Project Manager Hypra - "Humanizing technology"
Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut
Dear all :), The issue still appears in the Debian Installer Stretch Alpha 8 (on EFI). I don't know how to fix this issue myself so I think at this time we have two options : - Change the Debian installation guide to help visual-impaired to activate the ncurse or graphical high-contrast theme. I'm not able to write it myself because the contrast of the first screen makes it completely unreadable for me. - Resolve the issue to provide the same easy steps as describe here : https://www.debian.org/releases/jessie/amd64/ch05s02.html.en#idp71552032 This issue also affects blind people who have non-USB braille displays (because the device is not auto-detected). I'm available on IRC (nickname alexarnaud) or by mail to discuss what is for you the best way for making the Debian Installer accessible for everybody. Best regards. -- Alex ARNAUD Visual-Impairment Project Manager Hypra - "Humanizing technology" Le 17/04/2016 à 00:15, Steve McIntyre a écrit : On Sat, Apr 16, 2016 at 11:41:48PM +0200, Samuel Thibault wrote: Control: reassign -1 debian-installer Hello, Alex ARNAUD, on Wed 13 Apr 2016 17:51:45 +0200, wrote: I've tried to reproduce the instructions in the Debian installation guide in "Accessibility" section at "5.2.7 High-Contrast Theme" : https://www.debian.org/releases/jessie/amd64/ch05s02.html.en#idp71552032 * What was the outcome of this action? I'm not able to enable the high-contract theme. ? This works for me. Did you take care that the keyboard is using a qwerty layout at boot menu? He didn't mention it in the bug report, but Alex was talking about his problem on irc beforehand. He's booting in UEFI mode (and hence using Grub rather than isolinux). While it's possible to set extra variables on the Grub command line, it's much more involved and likely to be very difficult for a sight-impaired user. * What outcome did you expect instead? The best way should be to have only a unique key shortcut (maybe "h" for high-contrast theme) to launch the ncurse installer. Well, it's not really the ncurses installer which matters, but selecting the dark theme. Now, a shortcut is something being considered, see thread on https://lists.debian.org/debian-boot/2016/01/msg00346.html I believe we agreed how we want it to look like, and now it's a "matter" of implementing it. Ah, I missed that thread. It would be much easier for people using Grub if we added an extra menu level, definitely.
Bug#830869: [PATCH] debootstrap: excise all devices.tar.gz code
Since bug #571136 was fixed the --second-stage doesn't even use the
devices tarball so we can remove all its related cruft. The README has
been updated to show when real root access is required and give an
example of a foreign debootstrap which works with fakeroot.
Signed-off-by: Alex Bennée <alex.ben...@linaro.org>
---
.gitignore | 1 -
Makefile| 25 -
README | 18 ++
debootstrap | 3 ---
functions | 8 +---
5 files changed, 15 insertions(+), 40 deletions(-)
diff --git a/.gitignore b/.gitignore
index 8b3512f..8b13789 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1 @@
-devices.tar.gz
diff --git a/Makefile b/Makefile
index 1020cbc..55f229d 100644
--- a/Makefile
+++ b/Makefile
@@ -2,17 +2,9 @@
VERSION := $(shell sed 's/.*(\(.*\)).*/\1/; q' debian/changelog)
DATE := $(shell sed -n '/^ -- /{s/.*> \(.*\)/\1/p;q;}' debian/changelog)
-MAKEDEV ?= /sbin/MAKEDEV
-
-ifeq ($(shell uname),Linux)
-all: devices.tar.gz
-else
all:
-endif
clean:
- rm -f devices.tar.gz
- rm -rf dev
DSDIR=$(DESTDIR)/usr/share/debootstrap
install:
@@ -25,20 +17,3 @@ install:
sed 's/@VERSION@/$(VERSION)/g' debootstrap
>$(DESTDIR)/usr/sbin/debootstrap
chown root:root $(DESTDIR)/usr/sbin/debootstrap
chmod 0755 $(DESTDIR)/usr/sbin/debootstrap
-
-ifeq ($(shell uname),Linux)
- install -o root -g root -m 0644 devices.tar.gz $(DSDIR)/
-endif
-
-devices.tar.gz:
- rm -rf dev
- mkdir -p dev
- chown 0:0 dev
- chmod 755 dev
- (cd dev && $(MAKEDEV) std ptmx fd consoleonly)
- tar --mtime="$(DATE)" -cf - dev | gzip -9n >devices.tar.gz
- @if [ "$$(tar tvf devices.tar.gz | wc -l)" -lt 2 ]; then \
- echo " ** devices.tar.gz is empty!" >&2; \
- exit 1; \
- fi
- rm -rf dev
diff --git a/README b/README
index 5c08e15..af30a75 100644
--- a/README
+++ b/README
@@ -18,11 +18,21 @@ First, get the source.
* Or by visiting <http://packages.debian.org/source/sid/debootstrap>
and downloading the tar.gz file
-Then as root, in the debootstrap source directory:
+Then in the debootstrap source directory:
-make devices.tar.gz
-export DEBOOTSTRAP_DIR=`pwd`
-debootstrap sid sid
+export DEBOOTSTRAP_DIR=`pwd`
+sudo ./debootstrap stable my-stable-dir
+
+If you are running a multi-stage boot strap (for example for a QEMU
+rootfs) you don't even need root:
+
+export DEBOOTSTRAP_DIR=`pwd`
+fakeroot ./debootstrap --foreign --arch=armhf testing my-testing-dir
http://httpredir.debian.org/debian
+
+Of course you will need to execute the second stage as root to finish the
bootstrap:
+
+ (on foreign hardware)
+ /debootstrap/debootstrap --second-stage
Future
diff --git a/debootstrap b/debootstrap
index 2a959bb..4cea268 100755
--- a/debootstrap
+++ b/debootstrap
@@ -18,8 +18,6 @@ if [ -z "$DEBOOTSTRAP_DIR" ]; then
fi
fi
-DEVICES_TARGZ=$DEBOOTSTRAP_DIR/devices.tar.gz
-
. $DEBOOTSTRAP_DIR/functions
exec 4>&1
@@ -635,7 +633,6 @@ if am_doing_phase first_stage; then
if ! am_doing_phase second_stage; then
cp "$0"
"$TARGET/debootstrap/debootstrap"
cp $DEBOOTSTRAP_DIR/functions"$TARGET/debootstrap/functions"
- cp $DEBOOTSTRAP_DIR/devices.tar.gz
"$TARGET/debootstrap/devices.tar.gz"
cp $SCRIPT
"$TARGET/debootstrap/suite-script"
echo "$ARCH">"$TARGET/debootstrap/arch"
echo "$SUITE" >"$TARGET/debootstrap/suite"
diff --git a/functions b/functions
index 031721f..67701ee 100644
--- a/functions
+++ b/functions
@@ -1065,13 +1065,7 @@ setup_devices () {
hurd*)
;;
*)
- if true; then
- setup_devices_simple
- elif [ -e "$DEVICES_TARGZ" ]; then
- zcat "$DEVICES_TARGZ" | (cd "$TARGET"; tar -xf -)
- else
- error 1 NODEVTGZ "no %s. cannot create devices"
"$DEVICES_TARGZ"
- fi
+ setup_devices_simple
;;
esac
}
--
2.9.3
Bug#834635: Attempt to choose a network mirror does not work for stretch installer cd
Package: installation-reports Boot method: CD Image version: debian-testing-amd64-xfce-CD-1.iso Date: 17.Aug 2016 - 16:00 Machine: Notebook: Acer Aspire ES1-711 Processor: Intel 64Bit Memory: Partitions: Output of lspci -knn (or lspci -nn): 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:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [ ] Install boot loader:[O] Overall install:[E] Comments/Problems: I tested on the graphical installer and on the old installer. Both network adapters were recognized, and seem to be ok ( I tried ethernet and wifi). The problem appears on the step "Configure package manager" were I am asked "Do you want to use a network mirror". When choosing "yes", I am sent back to the menu were I can pick an installation-step ... without any error-message. When picking the next step( choose packages to install), I am asked again to pick a mirror ... so only option to procceed is to say: "Dont use a mirror" ... I would at least like to see some error-message which tells me why the installer fails to use a network-mirror. When using the debian-jessie installer CD (v4.5) the step "using network mirror" works fine .. however I got stuck later :X
Bug#830869: debootstrap: script fails first stage due to missing devices.tar.gz despite no longer being used
Hi,
Sorry I misfiled this bug against debhelper, this has now been fixed.
In short there seems to be a bunch of cruft associated with the
devices.tar.gz file which used to be used by the second stage to set up
devices in the bootstrapped chroot. This manifests itself if you run the
script from a SCM checkout without first doing a root based build (which
only works on Debian anyway).
In my case I fixed this by simply making cp || true although I guess
there is a bigger argument for properly excising the code as it is now
longer used AFAICT, see the main script:
if true; then
setup_devices_simple
elif [ -e "$DEVICES_TARGZ" ]; then
zcat "$DEVICES_TARGZ" | (cd "$TARGET"; tar -xf -)
else
error 1 NODEVTGZ "no %s. cannot create devices"
"$DEVICES_TARGZ"
fi
Sorry for the additional bug noise.
--
Alex Bennée
Bug#830869: [debhelper-devel] Bug#830869: debhelper: script fails first stage due to missing devices.tar.gz despite no longer being used
Niels Thykier <ni...@thykier.net> writes: > Alex Bennée: >> >> Niels Thykier <ni...@thykier.net> writes: >> >>> Alex Bennée: >>>> Package: debhelper >>>> Severity: normal >>>> >>> >>> Hi Alex, >>> >>> I am a bit confused by this bug. Did you perhaps intend to submit it >>> against debootstrap instead of debhelper? >> >> Apologies, completion fail. I was fighting M-x debian-bug which took >> several attempts to send the email. >> >> Yes it should be against debootstrap. Can I reassign it in BTS? >> >>> >>>[...] > > Yes you can. :) > > Please see [1] for the how to do it. You may also want to retitle[2] > the bug while you are at it (as it says debhelper). :) Finally, you > should remove the "moreinfo" tag I added. OK Thanks, I think I have it figured out now. Sorry for the noise on your list ;-) -- Alex Bennée
Bug#827822: Poor error message in debootstrap invocation
Package: debootstrap Severity: normal thanks If debootstrap is invoked like so: `sudo debootstrap jessie jessie --include=openssh-server` it errors out with `/usr/sbin/debootstrap: 314: set: Illegal option --`. The correct invocation is to move teh `--include` before `jessi`, but it'd be nice if a readable error message was emitted. (I'm using an older tutorial for invoking debootstrap which suggested the original invocation, I'm not sure if debootstrap's syntax has changed since then, or that post never worked) -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: D1B3 ADC0 E023 8CA6
Re: debian-installer issues with no wireless network connection after a text based Jessie installation
Dear Nick On 05/20/2016 06:52 AM, Nick Gawronski wrote: Hi, I am using the net installer of Jessie version 8.0.0 that includes the firmware Could you give us the full name of the Jessie ISO? as I am totally blind and found that the latest installer once it was installed I had no software speech after installing the system. It depends on how you install your system. If you install you system in braille or in "normal" way it's the normal effect. I was installing Debian Jessie on my laptop with just a text based system mainly for a rescue system for when X windows is down and for times when I don't wish to use X windows. I found that during the installation I was able to connect to the internet and successfully install the system but once the system was rebooted I had no internet access over any network method. As I know, It seems there is no link with accessibility in this case. What would it take for the debian installation to copy the network settings from the installer to the target system as it makes no sence why networking would be setup and working during a text based installation but not in the target system? What file should I edit to add my wireless network as well as my wired network using DHCP so they both will work when my text based system boots? Nick Gawronski The tips I use is to install a new driver for your Debian system. For doing something like that you need to follow some steps : 1) Find the model of your card and the related firmware package in Debian, if it's a Intel Wireless card it's the package firmware-iwlwifi <https://packages.debian.org/fr/jessie/firmware-iwlwifi> 2) Add the backports repo in your environment as explained in this page : http://backports.debian.org/Instructions/ 3) Install the new package with a command like that : "apt-get install -t jessie-backports FIRMWARE_NAME" -- Alex ARNAUD
Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut
On 04/16/2016 11:41 PM, Samuel Thibault wrote: Control: reassign -1 debian-installer Hello, Alex ARNAUD, on Wed 13 Apr 2016 17:51:45 +0200, wrote: I've tried to reproduce the instructions in the Debian installation guide in "Accessibility" section at "5.2.7 High-Contrast Theme" : https://www.debian.org/releases/jessie/amd64/ch05s02.html.en#idp71552032 * What was the outcome of this action? I'm not able to enable the high-contract theme. ? This works for me. Did you take care that the keyboard is using a qwerty layout at boot menu? Sorry for the lack of precisions. Like Steve McIntyre says, I speak about UEFI. * What outcome did you expect instead? The best way should be to have only a unique key shortcut (maybe "h" for high-contrast theme) to launch the ncurse installer. Well, it's not really the ncurses installer which matters, but selecting the dark theme. Now, a shortcut is something being considered, see thread on https://lists.debian.org/debian-boot/2016/01/msg00346.html I believe we agreed how we want it to look like, and now it's a "matter" of implementing it. Because of the severity of the issue I think a bug report is essential. This issue is the main barrier that renders visual impaired unable to install a Debian on recent computer. Personally the only way I found is to use my braille display to install Debian but I think I'm an exception, not all people can read braille and has braille display at his disposition. Best regards. -- Alex ARNAUD
Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut
3054 6023 Rescheduling interrupts /proc/interrupts: CAL:543692586635 Function call interrupts /proc/interrupts: TLB:622798 3501 3279 TLB shootdowns /proc/interrupts: TRM: 0 0 0 0 Thermal event interrupts /proc/interrupts: THR: 0 0 0 0 Threshold APIC interrupts /proc/interrupts: MCE: 0 0 0 0 Machine check exceptions /proc/interrupts: MCP: 22 22 22 22 Machine check polls /proc/interrupts: HYP: 0 0 0 0 Hypervisor callback interrupts /proc/interrupts: ERR: 0 /proc/interrupts: MIS: 0 /proc/meminfo: MemTotal:8082360 kB /proc/meminfo: MemFree: 4526212 kB /proc/meminfo: MemAvailable:7614784 kB /proc/meminfo: Buffers: 196484 kB /proc/meminfo: Cached: 2961948 kB /proc/meminfo: SwapCached:0 kB /proc/meminfo: Active: 933532 kB /proc/meminfo: Inactive:2255504 kB /proc/meminfo: Active(anon): 127000 kB /proc/meminfo: Inactive(anon):25400 kB /proc/meminfo: Active(file): 806532 kB /proc/meminfo: Inactive(file): 2230104 kB /proc/meminfo: Unevictable: 0 kB /proc/meminfo: Mlocked: 0 kB /proc/meminfo: SwapTotal: 1952764 kB /proc/meminfo: SwapFree:1952764 kB /proc/meminfo: Dirty: 1768 kB /proc/meminfo: Writeback: 0 kB /proc/meminfo: AnonPages: 30236 kB /proc/meminfo: Mapped: 6708 kB /proc/meminfo: Shmem:122040 kB /proc/meminfo: Slab: 327540 kB /proc/meminfo: SReclaimable: 305352 kB /proc/meminfo: SUnreclaim:22188 kB /proc/meminfo: KernelStack:1648 kB /proc/meminfo: PageTables: 812 kB /proc/meminfo: NFS_Unstable: 0 kB /proc/meminfo: Bounce:0 kB /proc/meminfo: WritebackTmp: 0 kB /proc/meminfo: CommitLimit: 5993944 kB /proc/meminfo: Committed_AS: 170352 kB /proc/meminfo: VmallocTotal: 34359738367 kB /proc/meminfo: VmallocUsed: 95788 kB /proc/meminfo: VmallocChunk: 34359642191 kB /proc/meminfo: HardwareCorrupted: 0 kB /proc/meminfo: AnonHugePages: 0 kB /proc/meminfo: HugePages_Total: 0 /proc/meminfo: HugePages_Free:0 /proc/meminfo: HugePages_Rsvd:0 /proc/meminfo: HugePages_Surp:0 /proc/meminfo: Hugepagesize: 2048 kB /proc/meminfo: DirectMap4k: 75064 kB /proc/meminfo: DirectMap2M: 2957312 kB /proc/meminfo: DirectMap1G: 5242880 kB /proc/bus/input/devices: I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 /proc/bus/input/devices: N: Name="AT Translated Set 2 keyboard" /proc/bus/input/devices: P: Phys=isa0060/serio0/input0 /proc/bus/input/devices: S: Sysfs=/devices/platform/i8042/serio0/input/input0 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=sysrq kbd /proc/bus/input/devices: B: PROP=0 /proc/bus/input/devices: B: EV=120013 /proc/bus/input/devices: B: KEY=40200 3803078f800d001 fedfffef fffe /proc/bus/input/devices: B: MSC=10 /proc/bus/input/devices: B: LED=7 /proc/bus/input/devices: /proc/bus/input/devices: I: Bus=0003 Vendor=03eb Product=8a31 Version=0111 /proc/bus/input/devices: N: Name="Atmel Atmel maXTouch Digitizer" /proc/bus/input/devices: P: Phys=usb-:00:14.0-7/input0 /proc/bus/input/devices: S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:03EB:8A31.0001/input/input5 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=mouse0 /proc/bus/input/devices: B: PROP=2 /proc/bus/input/devices: B: EV=b /proc/bus/input/devices: B: KEY=400 0 0 0 0 0 /proc/bus/input/devices: B: ABS=2608003 /proc/bus/input/devices: /proc/bus/input/devices: I: Bus= Vendor= Product= Version= /proc/bus/input/devices: N: Name="BRLTTY 5.2dev Linux Screen Driver Keyboard" /proc/bus/input/devices: P: Phys=pid-109/brltty/12 /proc/bus/input/devices: S: Sysfs=/devices/virtual/input/input6 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=sysrq kbd /proc/bus/input/devices: B: PROP=0 /proc/bus/input/devices: B: EV=13 /proc/bus/input/devices: B: KEY=40207 ffc03078f800d2a9 f2beffdfffef fffe /proc/bus/input/devices: -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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) installation-report depends on no packages. Versions of packages installation-report recommends: ii pciutils 1:3.2.1-3 ii reportbug 6.6.3 installation-report suggests no packages. -- no debconf information -- Alex ARNAUD
Re: dark theme boot menu?
On 01/19/2016 11:24 PM, Samuel Thibault wrote: Hello, Hello Sam ! During discussions, it was raised that selecting the dark theme is not really convenient: on the syslinux images one has to press tab and append theme=dark, and on the grub images, one has to edit the grub entry... Enter theme=dark is also hard for newbie because the user must knows qwerty keyboard layout. This of course raises the question: where will this end, will we end up with dozens of boot entries, making the boot menu unusable? :) I think It is not difficult for a user to press enter and after that press keyboard shortcut. This BTW raises the question of documenting shortcuts. For now, the newt frontend prints " moves; selects; activates buttons" there is not much more room, and the gtk frontend doesn't print any, I guess it assumes that the gtk shortcuts are well-known. We could perhaps add an F1 shortcut, which would print all the shortcuts? Of course, there is always the "bootstrapping issue" of somebody not being able to read the shortcut panel because it's too small or not proper colors, etc. but there is no miracle solution here anyway. We can provide a unique shortcut, maybe F11 (for a11y) that display in full screen a new panel in dark theme and big font that provide check boxes for accessibility feature. The navigation could be arrows key up/down and space to activate it. The way for saving could be tab to button at the bottom or F11. For quit without saving we can use Escape key. It is very important to make the shortcuts easy for people with mobility issues and for visual impaired big font and theme dark to make it able to read the options -- Alex ARNAUD
Bug#774331: Work around for `fakechroot fakeroot debootstrap` failure
Hi everyone, I have found a workaround for the problem after searching a solution for several hours. The solution is based on <https://www.notinventedhere.org/articles/linux/debootstrapping-debian-jessie-without-systemd.html>. We need to do a 2-stage hack and exclude systemd to work around the bug: $ fakechroot fakeroot debootstrap --variant=minbase --include sysvinit-core --foreign jessie debian-chroot http://ftp.us.debian.org/debian $ fakechroot fakeroot sed -i -e 's/systemd systemd-sysv //g' debian-chroot/debootstrap/required $ FAKECHROOT_CMD_SUBST=/bin/mount=/bin/true fakechroot fakeroot chroot debian-chroot debootstrap/debootstrap --second-stage Enjoy your debian-chroot by running: $ fakechroot fakeroot chroot debian-chroot Cheers, Alex
Bug#781290: still happens in d-i 20150606
Control: found -1 20150606 This week I reinstalled my laptop with Debian GNU/Linux 8.1.0 Jessie - Official amd64 CD Binary-1 20150606-14:19 and I was surprised that the encrypted LVM volume I created manually from partman has a Linux (83) type instead of Linux LVM (8e). Cheers, Alex signature.asc Description: Digital signature
Bug#788842: merge with bug 767682
Control: severity -1 important Control: merge -1 767682 It seems to me that both #788842 and #789427 are the same bug than #767682 that I stumbled upon on Mon Jul 6th, so let's merge them altogether. Cheers, Alex signature.asc Description: Digital signature
Bug#767682: still happens in d-i 20150606
Control: found -1 20150606 Stumbled upon this bug last Monday while installing Jessie from Debian GNU/Linux 8.1.0 Jessie - Official amd64 CD Binary-1 20150606-14:19 on top of a previous Ubuntu installation that had an existing /boot partition on sda3 formatted with ext4. I formatted the partition from the TUI and then I found that a confirmation was required before proceeding by mkfs.ext4. After that the installation was performed successfully. Cheers, Alex signature.asc Description: Digital signature
Louer son appartement en Israel dans un projet neuf| Rubinstein on the Park à Raanana | Alex Losky
Cette newsletter vous a été envoyée au format graphique HTML. Si vous lisez cette version, alors votre logiciel de messagerie préfère les e-mails au format texte. Vous pouvez lire la version originale en ligne: http://ymlp288.net/z2iA1X Pour une meilleure resolution, visualisez le message en ligne ( http://ymlp288.net/z2iA1X ). Location en Israel | Projet neuf locatif à Raanana : Rubinstein on the Park Contactez Esther : Tel: +972 58-782-58-52 E-mail: esth...@losky.co.il - Rubinstein On the Park propose une révolution dans la location d'appartement en Israel Louer auprès d'un propriétaire fiable et sérieu, fini les incertitudes des fins de contrats, un loyer controlé qui baisse suivant la durée de la période, une gestion professionnelle, un standing neuf et moderne. Le promoteur Rubinstein Ltd se spécialise dans la construction exclusive de projet locatif et reste proprietaire et gestionaire des lieux, ce qui garantit aux locataires une durée de location à sa guise, une variation des loyers en accord bilatéraux, une qualité de service inégalée en Israel. Rubinstein fête ses 83 ans d'activité et fait parti des société des plus anciennes et implantée du secteur et fière de compter quelques millers de locataires à travers ses propres résidences. L'ambition qui l'accompagne depuis sa création est la TRANQUILITÉ et SÉRÉNITÉ du locataire. Un des points forts du projet est son emplacement grâce auquel vous bénéficiez d'un environnement verdoyant, calme et sécurisant d'une part et d'une proximité centres d'activité et d'emplois, des commerces, écoles, centres de loisirs, transports publics et des principaux axes routiers du pays. Vous habiterez à quelques minutes de Tel-Aviv, Herztliya et Netanya. Raanana est un pôle de parcs hi-tech, fleuron de l'économie israelienne, des centaines d'offres d'emploi sont a pourvoir dans différents secteurs. Le groupe Alex Losky: Le Groupe Immobilier Alex Losky commercialise depuis plus de vingt ans, en Israël et dans le monde entier, les plus grands projets de prestige, propriétés commerciales et résidentielles, situés dans les régions métropolitaines de Jérusalem, Tel Aviv, Herzlia, Raanana, Ashdod et Eilat. Plus qu'un investissement, un achat immobilier constitue très souvent un projet de vie. L'écoute et l'échange se situent au cœur de notre démarche, nous donnant ainsi les moyens de répondre au mieux à vos besoins et vos envies. Nous ne considérons pas le succès de notre métier au nombre de transactions réalisées. Notre objectif est de vous satisfaire en vous proposant le bien correspondant à votre projet de vie. Notre parfaite connaissance du marché et l'expertise de nos conseillers régionaux nous permettent de vous proposer des solutions adaptées à chaque cas. Le cabinet d'avocats Journo Berdugo: Michaël Journo a ouvert son cabinet en 2006 à Tel-Aviv. Michaël Journo et Jérôme Berdugo ont fondé le cabinet Journo and Berdugo en janvier 2012, qui est composé à ce jour de 8 avocats. Michaël Journo et Jérôme Berdugo grâce à leur complémentarité représentent de nombreux entrepreneurs (sociétés/particuliers) et investisseurs en Israël et en France, dans tous les aspects de leurs activités. Ils assistent également leurs clients dans le domaine de l'investissement immobilier et de la construction, et accompagnent leurs opérations d'acquisition et de vente, de financement bancaire, de gestion. Dans le cadre de leur expertise en droit de l'immobilier, ils négocient au jour le jour les contrats d'acquisition, de vente et traitent tous les aspects nécessaires à la bonne réalisation du projet d'investissement. Ils ont également élargi récemment leurs domaines de compétences au contentieux civil et commercial. _ Unsubscribe / Désinscription: http://ymlp288.net/ugeyywjwgsgqwbyyhgbsjsygguwmqe
Bug#768464: preseed install of Debian Jessie failing
Package: installation-reports Boot method: ISO image attached to a VirtualBox VM Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd/debian-testing-i386-DVD-1.iso Image sha1 hash: 028a7c958a8f15bd6fe6f6cb43a28cf6a9950f45 Date: 5 November 2014. 11:15 GMT Machine: HP EliteBook 8460p running VirtualBox 4.3.17 r96342 Processor: Intel Core i5-2540M CPU @ 2.60GHz Memory: 384MB Partitions: n/a (virtual machine with a blank 42GB virtual hard disk, installation cancelled prior to partition creation) Output of lspci -knn (or lspci -nn): 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] Subsystem: Red Hat, Inc Device [1af4:0001] Kernel driver in use: virtio-pci 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] 00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01) Subsystem: Intel Corporation Device [8086:] 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) 00:18.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f2) 00:19.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f2) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02) Subsystem: Intel Corporation Device [8086:7270] 00:1f.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) Kernel driver in use: ata_piix 00:1f.2 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02) Kernel driver in use: ahci 00:1f.4 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] Kernel driver in use: ohci-pci Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [E] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I am trying to perform an automated preseed install of Jessie as a guest operating system using VirtualBox running on a Windows 7 Enterprise host. The problem is that when the installer tries to download the preseed file, the network has not been configured. The failure to download the preseed file causes the installer to fall back to an interactive installation. Opening a console shell and running ip address only shows the loopback interface. Looking in /lib/modules, the network device modules are missing (virtio_net.ko). I have tried all the other virtual network interfaces supported by VirtualBox without success. This installation method used to work for me. The last known working ISO is: http://cdimage.debian.org/cdimage/jessie_di_alpha_1/i386/iso-cd/debian-jessie-DI-a1-i386-netinst.iso Dropping back to using a Wheezy ISO (v7.7) works correctly, however using Wheezy is not an option because the GStreamer code I am using requires more recent versions of glib and gobject than those that ship with Wheezy. This transmission contains information that may be confidential and contain personal views which are not necessarily those of YouView TV Ltd. YouView TV Ltd (Co No:7308805) is a limited liability company registered in England and Wales with its registered address at YouView TV Ltd, 3rd Floor, 10 Lower Thames Street, London, EC3R 6YT. For details see our web site at http://www.youview.com
Bug#761423: busybox: using find in pipe with dd produce semi-random output
Package: busybox
Version: 1:1.22.0-8
Severity: normal
Dear Maintainer,
probably the problem is in the mainstream but it affect also Debian.
* What led up to the situation?
I was trying to find a shell way to check if a directory is empty
* What exactly did you do (or not do) that was effective (or
ineffective)?
I created a chroot with only busybox and the libs needed (as shown by ldd) to
be sure it is using only busybox commands.
sudo chroot chrootdir /bin/busybox sh
created a shell function:
isempty() { [ $(find $1 -name ?* | dd bs=$((${#1}+3)) count=1
2/dev/null) = $1 ] ; }
mkdir /test /test/.x
while [ 1 ] ; do if ! isempty /test ; then echo error ; break ; else echo not
empty ; fi ; done
run it few times
run 1 to 3 exit immediatly with error
run 4 show a non emtpy then error
run 5 show 9 non empty then error
(nobody removed or added files in /test)
also running manually the command below show different results from time to time
find /test -name ?* | dd count=1 2/dev/null
* What was the outcome of this action?
output truncated randomically, seem by line ending, when is wrong show only the
first line.
* What outcome did you expect instead?
always the same predictable full output of find.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.14-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages busybox depends on:
ii libc6 2.19-10
busybox recommends no packages.
busybox suggests no packages.
-- no debconf information
--
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/20140913190011.19197.22294.reportbug@hellspawn
Bug#761423: busybox: using find in pipe with dd produce semi-random output
Sorry I see I've missed a `touch /test/.x` in the bugreport. The test case is really simple: % busybox sh BusyBox v1.22.1 (Debian 1:1.22.0-8) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ $ mkdir /tmp/emptytest ~ $ touch /tmp/emptytest/.x ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ /tmp/emptytest/.x ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ /tmp/emptytest/.x ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ ~ $ find /tmp/emptytest/ -name *? | dd count=1 2/dev/null /tmp/emptytest/ /tmp/emptytest/.x The output should be always: /tmp/emptytest/ /tmp/emptytest/.x Assuming dd block size default to 512. Notice that omitting count or in pipe with cat it work properly. I guess something wrong on how dd close the pipe or find handle broken pipes. -- 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/20140913205758.GA1212@hellspawn
debootstrap without dpkg or binutils
Debootstrap does not work on an Arch Linux LiveCD instance because `ar' is
not available. The following patch fixes this.
From ced56c5b06bc52009c0d6fc6cc8b6132e898f3c5 Mon Sep 17 00:00:00 2001
From: Alex Austin circuitsoft.a...@gmail.com
Date: Thu, 10 Apr 2014 14:19:56 -0500
Subject: [PATCH] Add bsdtar support
This allows debootstrap to work on non-debian-based live boot instances that
don't have binutils installed.
Example: Arch Linux LiveCD
---
functions | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/functions b/functions
index 4e3955a..553f28f 100644
--- a/functions
+++ b/functions
@@ -785,7 +785,7 @@ get_debs () {
extraction
-EXTRACTORS_SUPPORTED=dpkg-deb ar
+EXTRACTORS_SUPPORTED=dpkg-deb ar bsdtar
# Native dpkg-deb based extractors
extract_dpkg_deb_field () {
@@ -829,6 +829,33 @@ extract_ar_deb_data () {
fi
}
+extract_bsdtar_deb_field () {
+ local pkg=$1
+ local field=$2
+
+ bsdtar -O -xf $pkg control.tar.gz | zcat |
+ bsdtar -O -xf - control ./control 2/dev/null |
+ grep -i ^$field: | sed -e 's/[^:]*: *//' | head -n 1
+}
+
+extract_bsdtar_deb_data () {
+ local pkg=$1
+ local tarball=$(bsdtar tf $pkg | grep ^data.tar.[bgx]z)
+
+ case $tarball in
+ data.tar.gz) cat_cmd=zcat ;;
+ data.tar.bz2) cat_cmd=bzcat ;;
+ data.tar.xz) cat_cmd=xzcat ;;
+ *) error 1 UNKNOWNDATACOMP Unknown compression type for %s
in %s $tarball $pkg ;;
+ esac
+
+ if type $cat_cmd /dev/null 21; then
+ bsdtar -O -xf $pkg $tarball | $cat_cmd | bsdtar -xf -
+ else
+ error 1 UNPACKCMDUNVL Extracting %s requires the %s
command, which is not available $pkg $cat_cmd
+ fi
+}
+
valid_extractor () {
local extractor=$1
--
1.9.1
[PATCH] Add bsdtar support
This allows debootstrap to work on non-debian-based live boot instances that
don't have binutils installed.
Example: Arch Linux LiveCD
---
functions | 37 +++--
1 file changed, 35 insertions(+), 2 deletions(-)
diff --git a/functions b/functions
index 4e3955a..bbb1d41 100644
--- a/functions
+++ b/functions
@@ -785,7 +785,7 @@ get_debs () {
extraction
-EXTRACTORS_SUPPORTED=dpkg-deb ar
+EXTRACTORS_SUPPORTED=dpkg-deb ar bsdtar
# Native dpkg-deb based extractors
extract_dpkg_deb_field () {
@@ -829,6 +829,33 @@ extract_ar_deb_data () {
fi
}
+extract_bsdtar_deb_field () {
+ local pkg=$1
+ local field=$2
+
+ bsdtar -O -xf $pkg control.tar.gz | zcat |
+ bsdtar -O -xf - control ./control 2/dev/null |
+ grep -i ^$field: | sed -e 's/[^:]*: *//' | head -n 1
+}
+
+extract_bsdtar_deb_data () {
+ local pkg=$1
+ local tarball=$(bsdtar tf $pkg | grep ^data.tar.[bgx]z)
+
+ case $tarball in
+ data.tar.gz) cat_cmd=zcat ;;
+ data.tar.bz2) cat_cmd=bzcat ;;
+ data.tar.xz) cat_cmd=xzcat ;;
+ *) error 1 UNKNOWNDATACOMP Unknown compression type for %s in
%s $tarball $pkg ;;
+ esac
+
+ if type $cat_cmd /dev/null 21; then
+ bsdtar -O -xf $pkg $tarball | $cat_cmd | bsdtar -xf -
+ else
+ error 1 UNPACKCMDUNVL Extracting %s requires the %s command,
which is not available $pkg $cat_cmd
+ fi
+}
+
valid_extractor () {
local extractor=$1
@@ -848,8 +875,10 @@ choose_extractor () {
extractor=$EXTRACTOR_OVERRIDE
elif type dpkg-deb /dev/null 21; then
extractor=dpkg-deb
- else
+ elif type ar /dev/null 21; then
extractor=ar
+ else
+ extractor=bsdtar
fi
info CHOSENEXTRACTOR Chosen extractor for .deb packages: %s
$extractor
@@ -862,6 +891,10 @@ choose_extractor () {
extract_deb_field () { extract_ar_deb_field $@; }
extract_deb_data () { extract_ar_deb_data $@; }
;;
+ bsdtar)
+ extract_deb_field () { extract_bsdtar_deb_field $@; }
+ extract_deb_data () { extract_bsdtar_deb_data $@; }
+ ;;
esac
}
--
1.9.2
--
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/1397167064-9524-1-git-send-email-circuitsoft.a...@gmail.com
Error during boot debian-7.2.0-amd64-CD-1.iso
At start time show this error message in italian: Questo programma non supporta ancora windows 6.2.9200 SPO I suppose in English corresponds to: This program does not yet support Windows 6.2.9200 SPO The pc is old notebook asus x61series (f50sl) ram 4 gb, hd 250 gb with installed on Windows 8.1 Why ? Solution ? Thanks all Alex -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/78970e3971dd72f6bac514311debb844.squir...@webmail.laseroffice.it
Re: late_command not late enough?
Hello Phil, However, baseinstaller will copy the installer's /e/n/i file into the install environment, so I preemptively copy the newly downloaded interfaces file over the installer's /e/n/i file. Thus overwriting the installer's /e/n/i file before it overwrites mine. Yes, this is ass-backwards. Why don't you just do that bit then (i.e. overwrite the installer's /e/n/i and let the installer do the rest), or is the busybox curl in d-i not capable of TFTP, or some such? As far as I can tell, there is no curl available from within the installer's environment. wget is installed, but it doesn't support tftp. The tftp command is available, but it only supports interactive mode. This is why I've been jumping through these hoops in late_command. You _might_ want to check out preseed_fetch as well, depending on how you're getting hold of your preseed file (preseed_fetch gets other files From the same place, which means you can write scripts that are agnostic about where the preseed came from -- at least that's the theory. I've never tried it with TFTP) You are my hero. I was not familiar with preseed_fetch. Now that I've spent some time playing with this, this is /exactly/ what I need. Thank you! Now I'm simply doing the following: d-i preseed/early_command string \ preseed_fetch tftp://10.0.0.254/89_later_than_late_command /usr/lib/finish-install.d/89_later_than_late_command ; \ chmod 755 /usr/lib/finish-install.d/89_later_than_late_command ; This is so much cleaner. Your suspicions were right about whether preseed_fetch would behave correctly when fetching files from the root directory over tftp. I did not find this to be the case (even when adding the /./ hint to the the preseed.cfg url directive). I ended up having to specify tftp://10.0.0.254/. Also, I would like to say (again) that the documentation for late_command is misleading. It is stated in many places (including the example wheezy preseed.cfg file) that late_command is run *just* before the install finishes but while /target is still mounted (implying that is runs right before unmounting). This leaves out important information (partman, netcfg, baseinstall, et al) and forces preseeders to dig into d-i internals just to figure out why their late_command scripts aren't working as expected. I'm curious if there's a technical reason why late_command is run so early in finish-install.d. Otherwise, I recommend moving it to run later in the finish-install.d list. Thanks again Phil. Your suggestions were a big help. ---Alex -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/calnpvjq0xcnqb4gkcifvwcfqfpu55ftfbaavy9epgymbvyg...@mail.gmail.com
Re: late_command not late enough? (also: partman-nfs)
Hello Brian, Anything of use at https://lists.debian.org/debian-user/2013/05/msg01167.html ? Thanks for the link. Basically: yes and no. The core issue is that late_command is run early (07) in the long line of finish.d scripts. partman (20s I believe), netcfg (50's I think), and baseinstaller all run afterwards, forcing me (and others) to resort to unseemly workarounds. I did solve my problems though, via two hacky methods (that I am /not/ proud of). For networking, I do the following: apt-install curl ; \ in-target mkdir -p /etc/network ; \ in-target curl -o /etc/network/interfaces tftp://10.0.0.254/install_interfaces ; \ in-target chmod 644 /etc/network/interfaces ; \ cp /target/etc/network/interfaces /etc/network/interfaces ; \ Here I download (from the tftp server I am netbooting from) a copy of the interfaces file I'd like to use. Since curl is not available in the installer environment, I download the file in the target environment. I don't need to worry about 55netcfg-copy-config since it exits early in its script (since I am not using NM). However, baseinstaller will copy the installer's /e/n/i file into the install environment, so I preemptively copy the newly downloaded interfaces file over the installer's /e/n/i file. Thus overwriting the installer's /e/n/i file before it overwrites mine. Yes, this is ass-backwards. The NFS mount, I'm afraid, is even worse: rm /usr/lib/finish-install.d/55netcfg-copy-config ; \ echo #! /bin/sh /usr/lib/finish-install.d/55netcfg-copy-config ; \ echo set -e /usr/lib/finish-install.d/55netcfg-copy-config ; \ echo echo '10.0.0.254:/home /home nfs _netdev 0 0' /target/etc/fstab /usr/lib/finish-install.d/55netcfg-copy-config ; \ chmod 755 /usr/lib/finish-install.d/55netcfg-copy-config ; Since I know that I don't need 55netcfg-copy-config (and it runs after partman), I choose to overwrite it. I cannot make my own sanely-named script to go into the finish.d folder (without creating a udeb) because the list of files in that folder is created before late_command is run. Thus I must reuse an existing script's name. 55netcfg-copy-config is that script. My generated script simply appends the target's fstab. So... doing things this way has caused a small part of my soul to die. I don't have a good idea of how to solve the networking situation more elegantly (any suggestions?), but I do know that writing a partman-nfs was discussed long ago. If it's still needed, I'm inspired to have a go at writing it -- even if it is only used for preseeding. Unfortunately, I won't have time for this for at least a few weeks (hence the pressure to resort to these hacks -- for the meantime). I am mostly interesting in creating partman-nfs if it has a chance to be used by others and accepted into Debian. If it is the wise wisdom of the Debian boot team that a partman-nfs is not wanted, then I may just go for a custom, internal udeb that just plops a script into finish.d. I'm new to the installer environment, so any pointers or tips for developing and debugging a udeb will also be very helpful. ---Alex -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/kpa9g0$osu$1...@ger.gmane.org
late_command not late enough?
Hello, I am attempting (and failing) to achieve these final two tasks for my preseeded deployment of Wheezy to our computation cluster. 1) Add an NFS mount to fstab. partman seems to be unaware that NFS exists. 2) Setup network bonding. netcfg does not support bonding (and does not intend to). My current approach is to use late_command to fix both of these problems. For fstab, I tried to simply append /etc/fstab; however, partman runs all if its scripts *after* late_command is executed and overwrites my change. I tried to completely replace my /etc/network/interfaces file; however, netcfg runs all of its scripts *after* late_command and clobbers my changes. This is detailed in bug #709017. I briefly attempted to create my own script (/usr/lib/finish-install.d/89true_late_command) to run after almost everything else, but -- as of yet -- I am unable to get debian-installer to execute it. Any help and/or insight is most welcome. ---Alex -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/kopvqg$4k9$1...@ger.gmane.org
Bug#647267: debian-installer: grub-install tries to install on the wrong drive
Just to confirm that this bug still exists: I've just done an ordinary (non-expert) installation toa Thinkpad T420 with the wheezy netinst iso written to a USB drive with unetbootin, and grub was told to install to /dev/sda (the USB drive) rather than /dev/sdb (the installation target), which failed. I had selected guided partitioning with encrypted LVM. Doing the update-grub; grub-install /dev/sdb dance on the emergency console left me with a working system. Perhaps that could be added to the error screen the installer presents in case of a grub-install failure? Interestingly, I had to do the installation a second time with firmware files on a *second* USB device, and on that occasion the correct drive was picked for grub. -- Alex -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51347827.8050...@blackkettle.org
Bug#690149: installation-reports
Package: installation-reports Método de arranque: USB-FLASH-DISK Versão da imagem: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Data: 10/10/2012 Máquina: Acer Aspire ONE 722 – amd c50 dual core , 11,6 Processador: AMD C50 Memória: 2GB Partições: ext4 ( sda1) ,swap ,ext3 (sda2) Saída de lspci -knn (ou lspci -nn): N/A Checklist da Instalação do Sistema Base [O] = OK, [E] = Erro (por favor descreva abaixo), [ ] = não foi tentado Arranque inicial:[E] Detectar placa de rede:[O ] Configurar rede:[ O] Detectar CD:[ ] Carregar módulos do instalador:[O ] Detectar discos rígidos:[ O] Particionar discos rígidos:[O ] Instalar o sistema base:[ O] Configuração do relógio/fuso horário:[O ] Configuração do utilizador/password:[ O] Instalar tarefas:[ ] Instalar gestor de arranque:[ ] Total da instalação:[ ] Comentários/Problemas: Fiquei muito feliz pois o debian wheezy detectou minha wifi e funcinou perfeitamente durante a instalação. Mas depois de instalado o debian e quando passa do grub a tela fica toda distorcida sem qualquer tela preta ou meios para iniciar. não chega a aparecer a tela de login e senha em modo texto. Detalhe é que optei por não instalar ambiente gráfico pois sempre instalo o xorg + jwm depois. mas o erro aconteceu antes que eu pudesse instalar o xorg+jwm. translation to EN I was very happy because the debian wheezy detected my wifi and funcinou perfectly during installation. But once installed debian and grub passes when the screen gets all distorted without any black screen or means to start. not enough to show the login screen and password in text mode. Detail is that I chose not to install a graphical environment for whenever I install xorg + jwm later. but the error happened before I could install xorg + jwm. Atenciosamente, Alexandre Araújo Desenvolvimento - SMA MV | Recife - PE - Brasil - www.mv.com.br +55 (81) 3972.7000 | ramal 81605 Skype:alexandre.araujo.mv
Bug#685228: Support for Haiku x86_64 in os-prober
Package: os-prober Version: 1.54 Severity: wishlist The attached patch modifies os-prober's Haiku detection to also detect an x86_64 installation of Haiku - the kernel is named kernel_x86_64 rather than kernel_x86, so the patch changes it to check for both of these. Thanks, Alex os-prober-1.54-haiku-x86_64.patch Description: Binary data
Re: I want x feature
On Sun, 2012-07-22 at 04:44 +0900, Samuel Thibault wrote: Alejandro Alcántar, le Sat 21 Jul 2012 13:37:39 -0600, a écrit : hi, i love debian , but went recommend to my friends , the have problems to re-size a partition and install with windows together, then thast why end to recomend ubuntu or 'linuxmint'. i wish add this option to debian installer http://sliceoflinux.files.wordpress.com/2009/10/instalar-ubuntu-9-10-06_animado.gif its a resizing hard drive. i thing would be a big step, to make easy install debian for a novice. its a resizing hard drive. i thing would be a big step, to make easy install debian for a novice. See installation manual, e.g. http://www.debian.org/releases/stable/i386/install.txt.en and look for resize in the Manual Partitioning section. Samuel tanks, but its more easy to my friends to install DEBIAN with this tool http://sliceoflinux.files.wordpress.com/2009/10/instalar-ubuntu-9-10-06_animado.gif this is a difference to install Ubuntu OR Debian for him. *more easy and *more faster to do -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1344285812.5175.208.camel@taller
Link-tausch (Handy)
Hallo, Ich möchte gerne Links mit Ihnen austauschen. Ich besitze 2 Seiten: 1. bfreeware.com, ca. 4 Jahre alt, PR 4 (Handy) 2. handytarifevergleich.com, eine neue Seite bfreeware.com = Ihre website A Ihre website A (oder Ihrer Website B) = handytarifevergleich.com Schicken sie mir Ihren Link-text und URL, dann werde ich Ihren Link auf meiner Homepage (bfreeware.com -blogroll oder artikel, Ihre Wahl) veröffentlichen. Ich möchte dann aber auch, dass Sie meinen Link auf Ihrer Homepage (oder artikel-Fügen Sie einen kurzen Satz) veröffentlichen. Wir nicht Austausch von Links auf Partnerpage. Wenn Sie interessiert sind, bitte setzten Sie sich für weitere Erörterungen mit mir in Verbindung. Mit freundlichen Grüßen Joyce -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d9044af3f6e94f54b758c199c1666...@alexandresblog.com
Bug#601011: the patch solves the problem
Hello , run in the same problem - LXC + debootstrap both on squeeze and sid didn't work as expected . Thanks to Alexandre , the patch solves the problem . Alex -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebd36bf.8010...@biotec.tu-dresden.de
Immobilier Israel: Nous serons dans votre ville du 27 au 30 Novembre 2011
Cette newsletter vous a été envoyée au format graphique HTML. Si vous lisez cette version, alors votre logiciel de messagerie préfère les e-mails au format texte. Vous pouvez lire la version originale en ligne: http://ymlp281.net/zHzVz8 Si le message ne s'affiche pas correctement, consultez-le en ligne ( http://www.losky.co.il/campagnes/tournee_en_france/version_en_ligne.php?campID=cn ) Le groupe immobilier Alex Losky vous annonce sa tournée parisienne et vous présente ses plus beaux programmes neufs à Seront présents Avocats et Banques afin de répondre à toutes vos questions Dimanche 27 Novembre 2011 Icube Paris(10h à 20h) Stand Losky-Espace Congrès Cap 15 Quai de Grenelle - 75015 Paris Lyon(17h à 22h) Hôtel Hilton 70, Quai Charles de Gaulles - 69006 Lyon Lundi 28 Novembre 2011 Paris 8ème(17h à 22h) Hôtel Napoléon 40, avenue Friedland Boulogne(17h à 22h) Espace Communautaire 43, Rue des abondances Mardi 29 Novembre 2011 Créteil(17h à 22h) Centre Communautaire Rue du 8 mai 1945 Levallois Perret (17h à 22h) Hôtel Ever Green 8, Place Georges Pompidou Mercredi 30 Novembre 2011 St Brice (17h à 22h) 14, allée des Rouges-Gorges Le Raincy (17h à 22h) 19, allée Chatrian Inscrivez vous dès à présent par formulaire ( http://www.losky.co.il/campagnes/tournee_en_france/landing.php?campID=cn ) ou au : + 33 1 83 649 659 / + 972 2 966 04 69 cont...@concept-nadlan.com - www.concept-nadlan.com _ Désinscription / Changer d'adresse e-mail: http://ymlp281.net/u.php?id=geyywjwgsgqwbyyhgejqw Powered par YourMailingListProvider
Immobilier Neuf en Israel : Pré-ventes groupées.
This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text emails. You can read the original version online: http://ymlp150.com/zQ1t5B Cliquez ici pour voir cet e-mail dans votre navigateur ( http://losky.co.il/campagnes/recherche_de_biens/index.html ) Pour tous nos abonnés désireux de trouver un bien immobilier neuf dans des conditions préférentielles, Concept Nadlan en collaboration avec Alex Losky ont référencés des programmes à travers tous le pays, transmettez votre demande par formulaire afin de recevoir nos offres. L‘immobilier en Israël... vous n’avez pas encore trouvé votre appartement ? Jérusalem 3 pièces à partir de 1.300.000 NIS Tel Aviv 2 pièces à partir de 1.300.000 NIS Nétanya 4 pièces à partir de 1.400.000 NIS Ashdod 4 pièces à partir de 1.250.000 NIS Donnez nous vos critères et laissez nous faire le reste ! N'hésitez pas à nous contacter au +(972) 2 966 04 69 / +(33) 1 83 649 659 ou par le formulaire Groupe Alex Losky Ltd - 19 King David Jérusalem Email : cont...@concept-nadlan.com En conformité avec la loi de la CNIL, nous envoyons nos messages exclusivement à nos inscrits, dans le cas où vous n'en faites pas parti et ne souhaitez plus recevoir nos nouvelles, le lien ci-dessous vous permettra de vous retirez de notre liste. _ Unsubscribe / Change Profile: http://ymlp150.com/u.php?id=gmhhuwsgsguumjhguue Powered by YourMailingListProvider
Bug#639440: [debian-installer] Automatic partiotining: small /tmp
Package: debian-installer Severity: normal --- Please enter the report below this line. --- When using the automatic partitioning into separate partitions, the installer created a 386M /tmp partition. This is not enough, for example, when watching a full-length YouTube movie: http://www.youtube.com/watch?v=4Z9WVZddH9w , filling the partition and stopping playback (probably confusing a less experienced user). I understand you can reload the YouTube movie and skip to the current position, resuming playback and fixing the problem temporarily (I needed to do this 4x to finish the movie) but in the case of a long vimeo.com movie, for example, it can't be done (as I've suffered in the past). I'm not sure I should report the bug here or in the appropriate browser or Flash plugin package, but as the installer left me with a 295G /home partition (which is mostly empty while /tmp is occasionally 100% full), I honestly think there's room for improvement in the partitioner (at least recommending novice users not to use multiple partitions, for example). My sincere thanks for the great work! --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-5-amd64 Debian Release: 6.0.2 500 stable www.debian-multimedia.org 500 stable security.debian.org 500 stable debian.las.ic.unicamp.br --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#629615: Freeze at PCMCIA Detection
Package: installation-reports Boot method: USB Stick Image version: http://cdimage.debian.org/debian-cd/6.0.1a/amd64/iso-cd/debian-6.0.1a-amd64-CD-1.iso Date: Wed Jun 8 13:55:53 CST 2011 Machine: H3C Neocean IX-1540 Storage Server Processor: Intel(R) Core(TM)2 Duo CPU E6400 @ 2.13GHz Memory: 4GiB DDR2 Partitions: Not partitioned yet Output of lspci -knn (or lspci -nn): :00:00.0 Class 0600: 8086:2778 (rev c0) :00:01.0 Class 0604: 8086:2779 (rev c0) :00:03.0 Class 0604: 8086:277a (rev c0) :00:1d.0 Class 0c03: 8086:27c8 (rev 01) :00:1d.1 Class 0c03: 8086:27c9 (rev 01) :00:1d.2 Class 0c03: 8086:27ca (rev 01) :00:1d.3 Class 0c03: 8086:27cb (rev 01) :00:1d.7 Class 0c03: 8086:27cc (rev 01) :00:1e.0 Class 0604: 8086:244e (rev e1) :00:1f.0 Class 0601: 8086:27b8 (rev 01) :00:1f.1 Class 0101: 8086:27df (rev 01) :00:1f.2 Class 0101: 8086:27c0 (rev 01) :00:1f.3 Class 0c05: 8086:27da (rev 01) :01:00.0 Class 0200: 8086:1209 (rev 10) :02:00.0 Class 0604: 10b5:8508 (rev ac) :03:01.0 Class 0604: 10b5:8508 (rev ac) :03:02.0 Class 0604: 10b5:8508 (rev ac) :03:03.0 Class 0604: 10b5:8508 (rev ac) :03:04.0 Class 0604: 10b5:8508 (rev ac) :04:00.0 Class 0604: 1166:0103 (rev c3) :05:00.0 Class 0200: 14e4:164c (rev 12) :06:00.0 Class 0604: 1166:0103 (rev c3) :07:00.0 Class 0200: 14e4:164c (rev 12) :08:00.0 Class 0604: 1166:0103 (rev c3) :09:00.0 Class 0200: 14e4:164c (rev 12) :0a:00.0 Class 0604: 1166:0103 (rev c3) :0b:00.0 Class 0200: 14e4:164c (rev 12) :0c:00.0 Class 0104: 193d:1500 (rev 09) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The system was a H3C Neocean IX-1540 Storage Server, a 4U appliance. It was shipped with SuSE Linux, however is a old kernel. By the way, it is a headless server, even without slot to insert video adapter. I used a USB stick to boot the computer, with output to serial console, and I used another computer to connect to the console port. It freezes at this point: This installation step depends on one or more other steps that have not yet been performed. Choose an installation step: 1. Detect network hardware [*] Prompt: '?' for help, default=1 Detecting network hardware ..95% Detect network hardware --- Some PCMCIA hardware needs special resource configuration options in order to work, and can cause the computer to freeze otherwise. For example, some Dell laptops need exclude port 0x800-0x8ff to be specified here. These options will be added to /etc/pcmcia/config.opts. See the installation manual or the PCMCIA HOWTO for more information. For most hardware, you do not need to specify anything here. PCMCIA resource range options: Prompt: '?' for help ..100% I added hw-detect/start_pcmcia=false to the boot args, however it is of no use -- the system insists to detect PCMCIA device, which do not present in the server.
Bug#622839: Debian installer fails at step install base system with claim that no suitable kernels can be found
Package: debian-installer Version: Squeeze When installing from the small cd amd64 wheezy (the netinst is build on squeeze and the volume identifies as squeeze but I was installing wheezy) in expert non-graphical mode, the installation fails during install base system saying it's unable to find any suitable kernels, and asking if I want to continue. Monitoring the install in a terminal, I see that /target/etc/apt/sources.list, previously containing a placeholder invalid line, has been blanked just before this error message. There is an empty file in /tmp called something like valid kernel versions. I was using LVM on top LUKS if that matters at all, though it probably doesn't. I was able to work around the issue by switching to a virtual terminal, editing the sources file to include a Debian repository and manually installing busybox then the kernel. # Workaround # When you see hte error Ctrl + F2 then enter to activate the console echo deb http://http.us.debian.org/debian stable main contrib non-free /target/etc/apt/sources.list apt-get update apt-get install linux-image-2.6-amd64 # Ctrl + F1 and tell the box to continue installing without kernel. One possible cause of this is that the expert mode install does not configure system mirrors before installing base system. After I worked around the error, the next step was to choose supplementary mirrors to the netinst. I can try to reenact the process later if more detail is needed and record exactly all steps taken. It seems to be reproducible in that it happened twice, though the first time I had manually set up partitions because I wanted xts on my LUKS. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4da7c866.1070...@ugcs.caltech.edu
Bug#582044: hw-detect: same issue with squeeze xen domU running XenServer
Hi,
I've seen this same problem in a squeeze domU running on XenServer. The
Detecting disks and all other hardware screen takes about 15 minutes to
complete. Then the [!] Detect disks screen appears and prompts the user to
select a driver.
I initially chose xen-blkfront but this had no effect apart from to return me
to the same screen. However, when I selected continue with no disk drive the
installation completed successfully and squeeze was installed to /dev/xvda (the
paravirtualized block device).
It seems like hw-detect does not recognise /dev/xvd* as a valid block device to
which Debian can be installed, but the rest of debian-installer has no problem
with it!
I was using the following images:
dists/squeeze/main/installer-i386/current/images/netboot/xen/{vmlinuz,initrd.gz}
from http://ftp.uk.debian.org/debian/
TIA for any suggestions!
Regards,
Alex
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c31e0cf.4030...@eu.citrix.com
Bug#552067: Install process forgets the CD if left alone for long time
Package: debian-installer Version: 20090123lenny4 Hello. I've been with Debian for many,many years. Now I am trying to install 5.03 on a number of computers using cd image http://cdimage.debian.org/debian-cd/5.0.3/i386/iso-cd/debian-503-i386-netinst.iso If install goes quickly, then it appears to be OK. However, if there is large file system is being created (e.g. took 1/2 hour to create encrypted one), or I just leave install unattended for some time, then install process forgets that CD is in the drive. Error message can be cannot figure out how to install base system or please insert the disk labeled - asking for the very same disk that is IN THE CDdrive at the moment. One more detail is that CDdrive is external, connected via USB. When I got those messages, I switched consoles and made sure that /cdrom/ is still readable and mounted properly. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#331523: Link goes to non-related site
A user in #debian reported that: http://www.debian.org/releases/stable/amd64/ch01s02.html.en contains a link to Kernel Traffic which actually goes to a website having nothing to do with kernels. The installation guides for other architectures have the same 'broken' link. I wasn't sure if I should append this bug or create a new one, but the title of this one seemed mostly appropriate. If you'd like a separate bug filed, please let me know. Thank you. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493825: Installation Problem with Debian on Toshiba Laptop
Package: installation-reports Boot method: floppy Image version: http://http.us.debian.org/debian/dists/etch/main/installer-i386/current//images/floppy/boot.img Date: downloaded: 30 July 2008, around 5:00 PM / date on file: 19 July 2008, 8:49 PM Machine: Toshiba Portege M200, currently running Windows XP tablet Processor: 1500 mHz Intel Centrino Memory: 1.5 GB Partitions: n/a Output of lspci -nn and lspci -vnn: n/a Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Initial boot of the network install program off of a floppy disc began, but then hung after claiming that it was unable to locate the floppy disc and went into kernel panic. The floppy drive is an external USB unit, made by Iomega with a model number of BXXUO130, or possibly BXXU0130. I believe that this is a driver error, perhaps caused at the time that BIOS hands over control to Debian, but I do not know this for certain. I was able to take a picture of the screen after the panic. To save space, I'm not including it here, but I have included a transcription below. Much of it may be irrelevant to the issue at hand, but I am including it in case you have use for it: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8024 KDB port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice EISA: Probing bus 0 at eisa.0 Cannot allocate resource for EISA slot 1 EISA: Detected 0 cards. TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 8 NET: Registered protocol family 20 Using IPI Shortcut mode ACPI: (supports S0 S3 S4 S5) Freeing unused kernel memory: 256k freed Time: tsc clocksource has been installed Floppy drive(s): fd0 is 1.44M input: AT Translated Set 2 keyboard as /class/input/input0 floppy0: no floppy controllers found Cannot load floppy module Giving up! /init: 44: sleep: not found Kernel panic - not syncing: Attempted to kill init! _ If this is a driver error, do you have an install package with the proper driver preloaded, or the proper driver and a procedure for how to incorporate it into the install package? Floppy was the method chosen for install because the Portege M200 will only boot off of a limited few external CD drives (it has no internal drives), which we own none of. (We do own an external CD drive which it can read, but not boot from.) We intend to install to an external hard drive (a 40GB unit, formerly the computer's internal drive), although we are unsure if it can boot off of that, and may be forced to make a partition of the main hard drive (80GB). Thank you. -Alex Costenoble -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491098: [Patch] packages/debian-installer-utils/fetch-url-methods/http fix for wget404 for latest busybox wget
Package: di-utils
Version: 1.60
Tags: patch
The wget404 code in
packages/debian-installer-utils/fetch-url-methods/http no longer
matches the error messages from busybox wget.
The attached patch fixes this for the busybox wget in the daily builds of d-i.
The attached patch also considers ftp and matches a different error
generated by ftp.
patch made againt debian-installer svn trunk revision 54394
Regards
Alex Owen
Index: packages/debian-installer-utils/fetch-url-methods/http
===
--- packages/debian-installer-utils/fetch-url-methods/http (revision 54394)
+++ packages/debian-installer-utils/fetch-url-methods/http (working copy)
@@ -3,16 +3,29 @@
url=$1
file=$2
+ if [ $proto = http ] ; then
wget404() {
# see README.wget404 in the debian-installer-utils udeb source for more info about this
local RETVAL=$( {
echo 1
wget $@ 21 3 echo %OK%
echo %EOF%
- } | ( sed -ne '1{h;d};/server returned error 404/{p;s/.*/4/;h;d};/^%OK%$/{s/.*/0/;h;d};$!p;$x;$w /dev/fd/4' 2 ) 41
+ } | ( sed -ne '1{h;d};/server returned error: HTTP\/1\.[01] 404 /{p;s/.*/4/;h;d};/^%OK%$/{s/.*/0/;h;d};$!p;$x;$w /dev/fd/4' 2 ) 41
) 31
return $RETVAL
}
+ elif [ $proto = ftp ] ; then
+ wget404() {
+ # see README.wget404 in the debian-installer-utils udeb source for more info about this
+ local RETVAL=$( {
+ echo 1
+ wget $@ 21 3 echo %OK%
+ echo %EOF%
+ } | ( sed -ne '1{h;d};/bad response to RETR: 550 /{p;s/.*/4/;h;d};/^%OK%$/{s/.*/0/;h;d};$!p;$x;$w /dev/fd/4' 2 ) 41
+ ) 31
+ return $RETVAL
+ }
+ fi
# use the proxy for wgets (should speed things up)
if db_get mirror/$proto/proxy; then
Index: packages/debian-installer-utils/README.wget404
===
--- packages/debian-installer-utils/README.wget404 (revision 54394)
+++ packages/debian-installer-utils/README.wget404 (working copy)
@@ -11,6 +11,20 @@
output does change, the sed will fail safe by returning 1 (i.e. general
error) if no specific error is found.
+From etch to lenny busybox wget error output did change.
+For lenny busybox wget 404 output is for example:
+server returned error: HTTP/1.1 404 Not Found
+This comprises the static string server returned error:
+followed by the server response which should follow rfc2616 section 6.1.
+Thus the output may say HTTP/1.0 instead of HTTP/1.1 and the string Not Found
+may also change. Thus the regular expression:
+ /server returned error: HTTP\/1\.[01] 404 /
+should catch all possible output for lenny.
+
+For the ftp method the error sring is different. The following regexp should work:
+ /bad response to RETR: 550 /
+
+
Here is a copy of the function being documented (since it's bound to
get out of sync with the one in the fetch-url-methods/http file, so you
might as well see the one that's being documented as well ;-)
@@ -20,8 +34,8 @@
local RETVAL=$( {
echo 1
wget $@ 21 3 echo %OK%
-echo %EOF%
-} | ( sed -ne '1{h;d};/server returned error 404/{p;s/.*/4/;h;d};/^%OK%$/{s/.*/0/;h;d};$!p;$x;$w /dev/fd/4' 2 ) 41
+echo %EOF%
+ } | ( sed -ne '1{h;d};/server returned error: HTTP\/1\.[01] 404 /{p;s/.*/4/;h;d};/^%OK%$/{s/.*/0/;h;d};$!p;$x;$w /dev/fd/4' 2 ) 41
) 31
return $RETVAL
}
@@ -35,7 +49,7 @@
1{h;d} -- take the first line (provided by the echo 1) and put it in sed's hold space
this will provide a default return value of 1 unless something else happens
- /server returned error 404/{p;s/.*/4/;h;d}
+ /server returned error: HTTP\/1\.[01] 404 /{p;s/.*/4/;h;d}
If we see a 404 error, print it, then turn it into a 4 and stuff it in the
sed hold space, and finally, delete the 4
This is where our return value of 4 comes from
@@ -86,3 +100,4 @@
STDOUT anyway -- Doh!
Phil Hands -- 2008-02-29
+Alex Owen -- 2008-07-16
i386 pxelinux.cfg no-longer serial friendly!
Hello, I see that d-i is now using the vesamenu for i386 netboot and has dropped the serial pxelinux configuration. If I were to produce a clean patch to re-enable production of a serial config might it be included for lenny? I take it the vesamenu config does not work over a serial port? Thanks for any advice Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: i386 pxelinux.cfg no-longer serial friendly!
If the prompt.cfg could be split in to using an include so that the menu and timeout and prompt lines were seperate from the display and f1,f2,f3 lines then I think I have a cunning plan... I will e-mail/bug report again if I get a working system. Thanks for your thoughts. Alex Owen 2008/7/12 Joey Hess [EMAIL PROTECTED]: Alex Owen wrote: I see that d-i is now using the vesamenu for i386 netboot and has dropped the serial pxelinux configuration. If I were to produce a clean patch to re-enable production of a serial config might it be included for lenny? I take it the vesamenu config does not work over a serial port? I dropped it in the process of splitting up the config files since supporting it was looking to add a lot of extra complexity. Also since I'd never considered the use case for it to be compelling -- with or without the file you still have to manually modify the syslinux configuration to enable serial console. If it can be added back without seriously complicating things, that'd be fine. I do think that vesamenu is right out for serial console, but have not actually checked that. -- see shy jo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFIeOaId8HHehbQuO8RAqbjAJ9UT38PZxTy817epJ4CE1/1OtTTGwCfXLEE +cumsP0I2O9tLhhZH6vOtMc= =+hj6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Update request for 4.0r2 Errata.
Hello, Perhaps someone knowledgeable on this list can comment: were the d-i netboot and floppy images rebuilt for 4.0r2 ? Up-to-date debian mirrors have netboot and floppy images identical to 4.0r1 (from what I can make out). The 4.0r2 press release [1] says: The installer has been updated to use and support the updated kernels included in this release. This change causes old netboot and floppy images to stop working; updated versions are available from the regular locations. To my mind (and atleast one other on #debian-boot) this implies that I should expect 4.0r2 netboot and floppy images to have date stamps and file contents different from 4.0r1 images. My observation is that this is not the case. I (and one other on #debian-boot) have completed netboot installs of 4.0r2 using the netboot images identical to 4.0r1. To save confusion I would like to propose the following sentence be added to the Errata [2] under the existing heading Errata for release 4.0r2: Despite the release announcement indicating that there are updated netboot and floppy images it should be noted that the netboot and floppy images for 4.0r2 are identical to those for 4.0r1. Perhaps someone knowledgeable can comment on the veracity of the above sentance and if appropriate forward the proposal to the errata editor. Many thanks Alex Owen [1] http://www.debian.org/News/2007/20071227 [2] http://www.debian.org/releases/etch/debian-installer/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445450: debian-installer: Unstable/sid kernel modules do not match kernel version in netboot
Package: debian-installer Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The kernel modules listed in the sid Packages.gz for debian-installer (dists/sid/main/debian-installer/binary-i386/Packages.gz , currently showing 2.6.22-2-486-di) do not match the version of the kernel that's used by the sid netboot image. (dists/sid/main/installer-i386/20070308 \ /images/netboot/debian-installer/i386/linux , currently showing \ 2.6.18-4-486). This makes it virtually impossible to install directly to unstable from a netboot. Installing to stable and then upgrading works, but is not feasible if an internal mirror is used that only has certain versions available (testing and sid, for example). - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHBq/aBPYwh6bSSDcRArnuAJ0Wv6TdvW8lzpcBNDwu9kE7M0LWdQCeP5Yc A823eedWUXdgzyYm3QCJtWQ= =KI9r -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
If user enters a password for GRUB it is stored in cleartext
Observed with today's debian-testing-amd64-businesscard.iso. (Testing with a sid installer) The debian installer allows the user to enter a password for GRUB to access advanced features. If the user does so, the password is included in cleartext in /boot/grub/menu.lst GRUB has the capability to use an md5 hash of a password instead of storing the password. These are generated with the grub command md5crypt. For example, to generate a md5 hash of the password foobar (no quotes): echo -e md5crypt\nfoobar | sudo grub --batch | grep Encrypted | sed -e 's/Encrypted: //g' There may be a cleaner way to do this but the above will work. Then, in /boot/grub/menu.lst, where you would write: password foobar instead write (the output from the above command) password --md5 $1$SZmo8$vxbhcjqNC4kHpqZi5n3r81 It is important not to store the password in cleartext for several reasons. Some users (such as myself) may use a password either similar to or identical to the root or user password on the machine for the bootloader. I boot to an encrypted root, but of course /boot is on an unencrypted volume so the password could be snooped. I understand the rationale that on a normal system, if you have read access to menu.conf then you have write access (eg, by rooting the system) and could just clear the password anyway, but given that GRUB provides such a simple way to use a hash instead I think Debian should implement this. As always, thanks for the wonderful, free operating system. Many of us appreciate your effort (including our entire cluster:-), and my two personal machines) Alex Roper UGCS Sysadmin California Institute of Technology signature.asc Description: This is a digitally signed message part.
Bug#422088: [Patch] wish preseed_fetch could distinguish between non-existance of a requested file and other failures to fetch file.
This mail is mostly a note to myself in a safe place! On 08/05/2007, Alex Owen [EMAIL PROTECTED] wrote: On 06/05/07, Joey Hess [EMAIL PROTECTED] wrote: Alex Owen wrote: + elifgrep server returned error 404 $log /dev/null ; then It's generally not a good idea to rely on command error messages like this. I agree, I was thinking that getting wget to give a sensible exit status rather than parsing the error message. Perhaps that warrents a wishlist bug on wget? I have posted to GNU-wget mailing list: http://www.mail-archive.com/wget%40sunsite.dk/msg10259.html proposing wget exits with exit status 4 for 404 errors Attached is an untested patch to busybox wget to implement an exit status of 4 for 404 errors. That is all for this update! Alex Owen --- networking/wget.c 2006-04-16 17:27:46.0 +0100 +++ networking/wget.c.rao 2007-09-13 21:36:44.0 +0100 @@ -372,6 +372,11 @@ case 302: case 303: break; +case 404: + bb_default_error_retval = 4; + chomp(buf); +close_delete_and_die(server returned error %d: %s, atoi(s), buf); + /*Never gets here*/ case 206: if (do_continue) break;
Bug#422088: [Patch] wish preseed_fetch could distinguish between non-existance of a requested file and other failures to fetch file.
On 13/09/2007, Alex Owen [EMAIL PROTECTED] wrote: I have posted to GNU-wget mailing list: http://www.mail-archive.com/wget%40sunsite.dk/msg10259.html proposing wget exits with exit status 4 for 404 errors Reply already... in summary: planning to implement exit codes in the wget version 1.13 time frame. Not willing to do adhoc cases in mean time. upstream wishlist bug here: https://savannah.gnu.org/bugs/index.php?20333 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422088: [Patch] wish preseed_fetch could distinguish between non-existance of a requested file and other failures to fetch file.
On 06/05/07, Joey Hess [EMAIL PROTECTED] wrote: Alex Owen wrote: # TODO add progress bar - if wget -q $url -O $file; then + if wget -q $url -O $file 2$log ; then + rm -f $log return 0 + elifgrep server returned error 404 $log /dev/null ; then It's generally not a good idea to rely on command error messages like this. I agree, I was thinking that getting wget to give a sensible exit status rather than parsing the error message. Perhaps that warrents a wishlist bug on wget? Perhaps reducing the grep line to: + elifgrep 404 $log /dev/null ; then would be more robust? On 06/05/07, Joey Hess [EMAIL PROTECTED] wrote: An alternative way to do this is to first always load the standard preseed file, and then try to fetch the load preseed file, which if it exists, can override settings in the standard file. I used to think that too... untill I discussed the idea with Philip Hands. Alex Owen: I was thinking that a cleaner approach might be to have all public and all examples under classes then override that by placing stuff in local (or local_classes if you want to keep local for your way of doing things). I have test code which will test for the existance of [presee|subclasses|early_script|late_script] under local and use that and fall back to the equivilent file under classes if that fails. Philip Hands: That sounds like the way I used to do that, but it has the problem that if you have a network outage, it's possible to have it skip an existing local file, and then carry on regardless, rather than having it complain that it failed to get a file it was expecting to exist -- this possibility, while slight makes the whole thing non-deterministic, so I'd rather avoid it (unless you have a scheme where a file that exists but is temporarily unavailable is distinguished from one that doesn't exist at all, in which case I'm all ears :-) Alex Owen: If wget (busybox) gives different error code for not found response from web server as opposed to no response from server then you can distinguish. I then wrote this patch as parsing the error message was easier than hacking the wget code! Thanks for your comments, Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422088: [Patch] wish preseed_fetch could distinguish between non-existance of a requested file and other failures to fetch file.
Package: preseed-common
Severity: wishlist
Version: 1.29
Attached is a patch against d-i SVN trunk so that file_preseed can
distinuish between a failure to fetch a file because it does not exist
and any other failure.
If a file does not exist then exit status is 4 otherwise it is 1.
I chose 4 as shorthand for HTTP 404 error.
This should be backwards compatable with existing code that just
checks for sucsess/fail.
New code (I'm thinking custom preseed systems here) can then pase the
exit code.
A custom preseed setup could have 2 dirs such as:
$base/standard
$base/local
a master preseed script could then try to do
preseed_fetch $base/local/script
and if this exits with status 4 fall back to
preseed_fetch $base/standard/script
If some other failure occurs the master preseed script can act accordingly.
I'm thinking of the Hands-Off preseed system here.
Feel free to change the exit code 4 to someother non-zero value if you will!
I'm afraid this code is as yet untested.
Regards
Alex Owen
Index: preseed/fetch-methods/file
===
--- preseed/fetch-methods/file (revision 46683)
+++ preseed/fetch-methods/file (working copy)
@@ -1,6 +1,8 @@
protocol_fetch() {
FILE=${1#file://*}
- if [ ! -e $FILE ] || ! cp $FILE $2; then
+ if [ ! -e $FILE ] ; then
+ return 4
+ elif ! cp $FILE $2; then
return 1
else
return 0
Index: preseed/fetch-methods/http
===
--- preseed/fetch-methods/http (revision 46683)
+++ preseed/fetch-methods/http (working copy)
@@ -1,6 +1,7 @@
protocol_fetch() {
local url=$1
local file=$2
+ local log=/tmp/preseed_fetch_http
iters=0
# use the proxy for wgets (should speed things up)
@@ -10,10 +11,15 @@
while [ $iters -lt 3 ]; do
# TODO add progress bar
- if wget -q $url -O $file; then
+ if wget -q $url -O $file 2$log ; then
+ rm -f $log
return 0
+ elif grep server returned error 404 $log /dev/null ; then
+ rm -f $log
+ return 4
fi
iters=$(($iters + 1))
done
+ rm -f $log
return 1
}
Index: preseed/fetch-methods/floppy
===
--- preseed/fetch-methods/floppy (revision 46683)
+++ preseed/fetch-methods/floppy (working copy)
@@ -4,7 +4,9 @@
mountfloppy || true
touch /var/run/preseed-usedfloppy
- if [ ! -e $FILE ] || ! cp $FILE $2; then
+ if [ ! -e $FILE ] ; then
+ return 4
+ elif ! cp $FILE $2; then
return 1
else
return 0
Bug#421602: wish d-i could pick dhcp response based on vendor-class-identifier
Package: netcfg Version: 1.36 Severity: wishlist This is a wishlist bug so that this post does not get lost/forgotton: http://lists.debian.org/debian-boot/2007/04/msg00988.html patches may follow as time and motivation allows! The dhcp protocol and many (good) clients allow multiple dhcp servers. The debian-installer dhcp client sends a vendor-class-identifier of d-i. The debian-installer dhcp client SHOULD be configurable to only accept dhcp leases which come from servers that send a reply containing a vendor-class-identifier of d-i. If d-i is using dhclient then an /etc/dhclient.conf with a select-timeout line and a require line should enable this functionality if I have read the man page right. One more debconf key would be needed. If it was set true then ( select-timeout could be made equal to the dhcp timeout and require line could ve set ) . Note: netcfg seems to write out /etc/dhclient.conf just before calling dhclient. /etc/dhclient.conf in the initrd is edited as it is copied to the installed /target system. This editing would need to be updated if the code that writes /etc/dhclient.conf is changed. Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
waking up in the 10.x.x.x network
Michael S. Peek said: If I attempt to set up my own DHCP server then I run into a race condition between my DHCP server and the campus DHCP server. There's no way to tell d-i which server to contact, so it'll listen to the first one that it hears back from. So as near as I can tell, there is just no way to make this work. The DHCP protocol has the Vendor Class Identifier which could ne incoperated into the d-i dhcp-client. The dhcp protocol and many (good) clients allow multiple dhcp servers. The debian-installer dhcp client sends a vendor-class-identifier of d-i. The debian-installer dhcp client SHOULD be configurable to only accept dhcp leases which come from servers that send a reply containing a vendor-class-identifier of d-i. If d-i is using dhclient then an /etc/dhclient.conf with a select-timeout line and a require line should enable this functionality if I have read the man page right. It is a shame that http://d-i.alioth.debian.org/manual/en.i386/apbs02.html B.2.5 seems to say that d-i overloads the dhcp filename option to find the location of the preseed file. In my opinion this is better handled using vendor-encapsulated-options. Check out sun solaris install docs for ideas on this front! Mind you I guess there are many simple dhcp servers out there thus making overloading the filename option more practical. Hmm... I think there was some talk of changing the dhcpclient engine for lenny... there seemed to be lots of suggestions... my vote is for udhcpc. Anyway making the dhcp client in d-i more featureful with regards multiple dhcp servers perhaps could be added as a lenny release goal??? Just some thoughts! Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417407: Improve safety of os-prober by ignoring active swap and using blockdev --setro when available
OK here is the patch!
On 07/04/07, Alex Owen [EMAIL PROTECTED] wrote:
Attached is a patch to os-prober to:
(1) make it ignore active swap
[Changes in: os-prober/os-prober]
(2) if blockdev is available then use it to set partitions read-only
before mounting to work arround a feature of ext3 and possible other
journaled filesystems!
[Changes in: os-prober/os-probes/common/50mounted-tests]
Index: os-prober/os-prober
===
--- os-prober/os-prober (revision 46179)
+++ os-prober/os-prober (working copy)
@@ -34,6 +34,13 @@
done
}
+parse_proc_swaps () {
+ while read line; do
+ set -- $line
+ echo $(mapdevfs $1) swap swap
+ done
+}
+
parse_proc_mdstat () {
while read line; do
for word in $line; do
@@ -67,6 +74,7 @@
# Therefore we use mapdevfs to match partitions with mount points
# and partitions used in RAID
grep ^/dev/ /proc/mounts | parse_proc_mounts /tmp/mounted-map || true
+grep ^/dev/ /proc/swaps | parse_proc_swaps /tmp/swaps-map || true
: /tmp/raided-map
if [ -f /proc/mdstat ] ; then
grep ^md /proc/mdstat | parse_proc_mdstat /tmp/raided-map || true
@@ -84,6 +92,12 @@
continue
fi
+ # Skip partitions used as active swap
+ if grep -q ^$mapped /tmp/swaps-map ; then
+ debug $partition: is active swap
+ continue
+ fi
+
if ! grep -q ^$mapped /tmp/mounted-map ; then
for test in /usr/lib/os-probes/*; do
if [ -f $test ] [ -x $test ]; then
Index: os-prober/os-probes/common/50mounted-tests
===
--- os-prober/os-probes/common/50mounted-tests (revision 46179)
+++ os-prober/os-probes/common/50mounted-tests (working copy)
@@ -20,6 +20,25 @@
fi
done
+
+protect_dev(){ #$1=partition : stdout=dev_rw_flag
+dev_rw_flag=0
+if type blockdev /dev/null 21; then
+ if [ `blockdev --getro $1` = 0 ] ; then
+ blockdev --setro $1
+ dev_rw_flag=1
+ fi
+fi
+echo $dev_rw_flag
+}
+
+unprotect_dev(){ #$1=partition $2=dev_rw_flag
+if [ $2 = 1 ] ; then
+ blockdev --setrw $1
+fi
+}
+
+dev_rw_flag=`protect_dev $partition`
for type in $types $delaytypes; do
if mount -o ro -t $type $partition $tmpmnt 2/dev/null; then
debug mounted as $type filesystem
@@ -29,6 +48,7 @@
if $test $partition $tmpmnt $type; then
debug os found by subtest $test
umount $tmpmnt
+ unprotect_dev $partition $dev_rw_flag
rmdir $tmpmnt || true
exit 0
fi
@@ -38,6 +58,7 @@
break
fi
done
+unprotect_dev $partition $dev_rw_flag
rmdir $tmpmnt || true
Bug#417407: Improve safety of os-prober by ignoring active swap and using blockdev --setro when available
clone 417407 -1 reassign -1 util-linux retitle -1 util-linux: wish there was a blockdev-udeb severity -1 wishlist reassign 417407 os-prober tags 417407 +patch retitle 417407 os-prober: protect partitions with blockdev --setro when available thanks Attached is a patch to os-prober to: (1) make it ignore active swap [Changes in: os-prober/os-prober] (2) if blockdev is available then use it to set partitions read-only before mounting to work arround a feature of ext3 and possible other journaled filesystems! [Changes in: os-prober/os-probes/common/50mounted-tests] I do not claim to have tested the patch. I have tried to write the patch so that (2) does nothing if blockdev is not there... Perhaps this means the deb should recommend util-linux while the udeb could require blockdev-udeb? I have cloned this bug as a wishlist against util-linux requesting a blockdev-udeb. Regards Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417407: debian-installer: possible workarounds for d-i destroyed existing raid device
Cut and paste from BTS web interface so sorry for the formatting! From: Samuel Thibault [EMAIL PROTECTED] Subject: Re: Bug#417407: debian-installer: d-i destroyed existing raid device Date: Tue, 3 Apr 2007 19:26:25 +0200 Hi, martin f krafft, le Tue 03 Apr 2007 10:28:24 +0200, a écrit : And the other question of course is why the kernel decided it had any business doing recovery on an fs that was marked for ro mount. Because it always do so, see linux/fs/ext3/super.c:ext3_load_journal(): even if the mount is read-only, the journal is recovered. If (but only if) the device itself is read-only, then nothing is written back to the disk. Ext3 clearly lacks xfs' norecovery mount option. I can think of two possible workarounds for this. NB: I have not looked at the code but I'm just thinking out loud. [1] at the partitioner stage configure md devices... IIRC this should recognize the preexisting device. Then mark the device to be mounted at /home (or /oldhome for the ultra paranoid) and markit to be left alone (ie not formatted). _Presumably_ os-prober would then ignore the md device and it's components when looking for other OS's. [2] wrap the mount/umount sections of code in os-prober with calls to blockdev to set the block device readonly (and restore old perms on umount). This would side step the deficiencies in the unconditional ext3 journal recovery code. (but this would need a block-dev udeb added to util-linux source) Just some thoughts... Alex Owen
Bug#416310: My Fault!
Hello there, I'm afraid this is my fault. I supplied a patch to make grub-installer try to do the right thing in bug http://bugs.debian.org/224641 However the code added there assumes a FULL serial port definition on the kernel command line. eg: for the example Vagrant gives in this bug report console=ttyS0,38400n8 _should_ work (i tested this when writing the patch) while the shorter console=ttyS0,38400 will not (and was not tested - opps!). Also it is preferable to add the console= argument after the -- argument that way it will be taken as a user supplied argument that should be added to the #kopt= line in the grub.conf Perhaps this should be included in the release notes for Etch? For Lenny the code should parse the console= parameter more properly! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416310: My Fault!
On 27/03/07, Frans Pop [EMAIL PROTECTED] wrote: On Tuesday 27 March 2007 21:26, Alex Owen wrote: Perhaps this should be included in the release notes for Etch? No, at most in the D-I errata I would say. Proposed entry for d-i errata: dti386: Serial Console setup with GRUB/dt dd There are some issues with the way the debian-installer tries to setup GRUB to use a serial console. Full details can be found in the bug report a href=http://bugs.debian.org/416310;#416310/a. Briefly these issues can be resolved by ensuring that:br (1) the ttconsole=/tt kernel argument is passed after the tt--/tt kernel argument;br (2) that the parity and bits options are also passed in the ttconsole=/tt definition. For most people this will mean that instead of booting with ttconsole=ttyS0,9600/tt you should boot with tt-- console=ttyS0,9600n8/tt. /dd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416310: [Patch] fix fault in grub_serial_console
This bug lies in the grub-installer script in the function grub_serial_console.
Attached is the file grub_serial_console.txt is a replacement
grub_serial_console function which parses the kernel command line
console= argument in a more robust and (I hope) readable manner.
A test script test.sh is also attached which can be used to excercise
the grub_serial_console function in the file grub_serial_console.txt.
I know this is very late in the release cycle but I would like to see
this rewrite of
grub_serial_console enter d-i for Etch.
Regards
Alex Owen
[For Lenny: While rewriting grub_serial_console I thought I would tidy
up the function get_serial_console. Attached is the file
get_serial_console.txt which contains a drop-in replacement for the
function get_serial_console. This should _not_ be targeted at Etch]
grub_serial_console() {
#$1=output of get_serial_console
local serconsole=${1##console=}
local device=${serconsole%%,*}
local unit=${device##ttyS}
local options=${serconsole##*,}
#Handle case when no options given
[ $options == $device ] local options=
local speed=$(echo $options | sed -e's%^\([0-9]\+\).*%\1%')
local parity_word_flow=${options##${speed}}
local word_flow=${parity_word_flow#?}
local parity=${parity_word_flow%%${word_flow}}
local flow=${word_flow#?}
local word=${word_flow%%${flow}}
case $parity in
n) local parity=--parity=no ;;
e) local parity=--parity=even ;;
o) local parity=--parity=odd ;;
*) local parity= ;;
esac
[ $word ] local word=--word=$word
[ $speed ] || local speed=9600 #Match Kernel Default
echo serial --unit=$unit --speed=$speed $word $parity --stop=1
echo terminal serial
}
test.sh
Description: Bourne shell script
#For Lenny
get_serial_console() {
for x in $(cat /proc/cmdline); do
case $x in
console=*)
local defconsole=${x#*=} ;;
esac
done
if echo ${defconsole} | grep -q ttyS; then
echo console=$defconsole
fi
}
Bug#415830: Partition sizes not sufficient on guided setup
Package: installation-reports Boot method: CD Image Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: 21 Maart 2007 - 18:00 GMT+1 Machine: VMWare (5.5.3 build-34685) Virtual Machine Processor: N/A Memory: 256 Mb Partitions: [EMAIL PROTECTED]:~$ df -Tl Filesystem Type1K-blocks UsedAvail Use%Mounted /dev/sda1 ext3 239554022943640 100%/ tmpfs tmpfs63512 063512 0%/lib/init/rw udev tmpfs10240 5610184 1%/dev tmpfs tmpfs63512 063512 0%/dev/shm /dev/sda6 ext3 5534416 142236 511048 3%/home Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: Yesterday I wanted a quick try of Etch, so I created a VMWare machine. On the installer I choose to use guided partitioning, a separate home partition and let the installer automatically setup the partition layout on my 8,6Gb HDD. A few steps later in the installation process, I choose to install only the Desktop Environment Base System. There was no error or warning during the installation whatsoever. However, on the first boot when GDM loaded and I provided my user details to start Gnome, an error message that stated that my gnome session had crashed popped up. Switching to console provided me with a quite conclusive reason why this happened, 0% free space on my root partition. Obviously I'd manually enter (and double-check) my partition layout on a production system, but many users aren't comfortable with manually editing partition tables. I don't think the installer should allow this situation to happen, or should at least provide a warning that the partition layout doesn't provide enough space for the current package installation options. With kind regards, Alexander van der Mey Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install.
Bug#413814: installing Debian GNU/Linux 4.0 on a Power Macintosh G3 Server
language than French :) ... and *yes*, now I can boot into MacOS 9.2 ... but now when I boot into Debian GNU/Linux with BootX, there is another, more serious problem: When I boot into Debian GNU/Linux with BootX, I can only use the vmlinux and initrd.gz of debian-installer. So instead of booting into my system, I boot into debian-installer. Attempt to solve this problem: start a shell from debian-installer, and chroot to my Debian GNU/Linux system. From there, find the vmlinux and initrd.gz that will allow me to boot directly into Debian GNU/Linux (they are in /boot) and make them accessible to the MacOS 9.2 system. But... First attempt: mount the MacOS 9.2 (HFS) partition in read/write and copy vmlinux and initrd.gz there. The hfs driver isn't built in the kernel, so I need to load it with modprobe hfs... But alas ! It fails because it's not the same kernel version ! Indeed, I'm running the vmlinux kernel from debian-installer, but I'm trying to mount a module in /lib/modules on the installed system. So it's not the same version of the kernel ! And I can't mount the HFS partition. Second attempt: connect to the local network. From the chroot, transfer the vmlinux and initrd.gz files to a machine which has apache installed. Then reboot into MacOS 9.2, use a web browser to access the second machine, and download vmlinux and initrd.gz. Then in the future I can use these vmlinux and initrd.gz to boot into Debian GNU/Linux. debian-installer is for sure better than the tools you had to use to install Debian 3.0 on powerpc... But it seems there are still a few problems... Especially I don't see why MacOS 9.2 becomes unbootable after the installation of Debian GNU/Linux. Of course, I didn't touch the MacOS 9.2 partitions at all. I had a lot of spare space after the MacOS 9.2 partition, and I created my filesystems there. You can look at the output of mac-fdisk -l up there, I didn't mess with the Apple partitions :) Cheers, Alex
Bug#413854: v880 sparc install problem
Package: installation-reports Boot method: CD, netboot Image version: sarge, etch, and daily netboot and CD images Date: March 5-7, 2007 Machine: Sunfire v880 Processor: 4x ultrasparc Memory: 8 GB Partitions: nothing yet. Output of lspci -nn and lspci -vnn: Can't get the box to boot. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Sarge images give the following error: error 256 stack underflow etch and snapshots just display booting linux... then nothing more. adding the -p flag gives us: Error: Cheetah error trap taken afsr[ ] Error: TPC[ ] TNPC[ ] TSTATE[ ] Error: M_SYND(0), E_SYND(0), Privileged Error: Highest Priority Error() Unmapped error from system Then a bunch of D-cache, I-cache, and E-cache errors. And finally, Kernel Panic – not syncing: Irrecoverable deferred error trap For reference, the gentoo 2006.1 minimal CD (2.6.17 plus gentoo patches) seems to boot ok.
Re: Will we be releasing some day?
* To: debian-boot@lists.debian.org * Subject: Re: Will we be releasing some day? * From: Steve Langasek [EMAIL PROTECTED] * Date: Tue, 20 Feb 2007 00:48:54 -0800 * Cc: debian-release@lists.debian.org * In-reply-to: [EMAIL PROTECTED] * Mail-followup-to: debian-boot@lists.debian.org,debian-release@lists.debian.org * Message-id: [EMAIL PROTECTED] The need for GPL compliance in the face of version skew between the kernel debs and the installer were a major reason why, *pre-sarge*, the kernel packages had support added for rolling back to any previous Debian patchlevel. I've just verified that yes, this code is still present in the current linux-2.6 package: if you install linux-source-2.6.18, you will get a linux-patch/usr/src/kernel-patches/all/2.6.18/apply/debian script that lets you specify, with a -R option, the exact patchlevel you want to recreate, so that reproducing previous versions of the linux-2.6 tree is as trivial as possible. Has anyone tested that this still works post linux-2.6_2.6.18.dfsg.1.orig.tar.gz ie since the DFSG orig.tgz ! Presumably the -R option for post linux-2.6_2.6.18.dfsg.1.orig.tar.gz will only work for revisiones with teh same linux-2.6_2.6.18.dfsg.1.orig.tar.gz ??? Any experts want to comment? Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: live and install in one CD?
At the risk of repeating myself a normal deb that had a gui/text-ui to create a preseed file might be the way to go. This preseed-generator could then be installed in the livecd and could append the generated preseed to the normal d-i initramfs and use kexec to bootinto d-i ... That way we have: [1] one way to install debian: d-i [2] a way to install from live-cd [3] a gui to create preseed files (for free!) Just a thought Alex Owen On 09/01/07, Otavio Salvador [EMAIL PROTECTED] wrote: Marco Amadori [EMAIL PROTECTED] writes: The ubiquity approach could be surely be faster than d-i/g-i but I do not think we want to support a different way of installing debian besides than the official one. Indeed. The d-i/g-i is far better and easier to maintain since it won't differ too much from the original installer ;-) The problematic thing that I see is it'll differ on the initial steps of installation since you'll already have the kernel and kernel modules loaded and it can require some modifications from d-i side to support it well. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. ___ Debian-live-devel mailing list Debian-live-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#275360: [Patch] example patch showing where to hook dhcp network config to get dhcp-static config
On 04/01/07, Alex Owen [EMAIL PROTECTED] wrote: This patch is in a VERY EARLY state. It inserts into /etc/dhclient-script so that the ip/mask/route etc form dhcp can be captured. This then needs to be put into the debconf database. this will allow development of static net config from a dhcp boot. The patch writes debconf-set statements to a file which could later be sourced to set the values in debconf-db Opps... here is the patch Index: packages/netcfg/dhclient-script === --- packages/netcfg/dhclient-script (revision 43848) +++ packages/netcfg/dhclient-script (working copy) @@ -89,6 +89,16 @@ # Get the domain name into a file suitable for netcfg to read. echo -n $new_domain_name /tmp/domain_name + # copy DHCP information into debconf database (wishlist #275360) + #this does not fully work but I think this is the place to hook the dhcp process +echo /bin/debconf-set netcfg/get_ipaddress ''$new_ip_address'' /tmp/net.preseed +echo /bin/debconf-set netcfg/get_netmask ''$new_mask'' /tmp/net.preseed +for router in $new_routers; do +echo /bin/debconf-set netcfg/get_gateway ''$router'' /tmp/net.preseed +break +done +echo /bin/debconf-set netcfg/get_nameservers ''$new_domain_name_servers'' /tmp/net.preseed + ;; EXPIRE|FAIL|RELEASE|STOP)
Bug#405129: installation-reports: No message displayed if there is not enough space for the installation.
Just made an successful install using the snapshot net-install for today. Here is what I found out. I chose the newbie option (1 partition for everything) using LVM. Of course I got an extra /boot (236 Mb partition, 13Mb used) and tempfs (126Mb) Choosing the Standard + Desktop tasks, it takes 2.6Gb on the / (root) filesystem just when the installation finishes. If there is any other info you want me to take just let me know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405129: installation-reports: No message displayed if there is not enough space for the installation.
I forgot to say that I chose NO to the PCMCIA option, so that should take some more space over what I said in the previous message. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405129: installation-reports: No message displayed if there is not enough space for the installation.
On Mon, Jan 01, 2007 at 07:56:58AM +0100, Frans Pop wrote: reassign 405129 tasksel severity 405129 important thanks On Sunday 31 December 2006 17:08, alex wrote: I tried to install Etch using the RC1 installer (expertgui way). I didnt allocate enough space for the installation. Obviously, it couldnt finish the installation, and I was getting generic I cant install messages, giving me the option to try again, but I wasnt told that there just wasnt enough space. I had to get out of the installation and check for myself what was wrong. In general this is a known issue. Required disk space for the different tasks are documented in the manual, but is not checked during the installation as technically this is not that easy to implement. It is also not that easy (if possible at all) to detect out of disk as the reason for failures. The installer will respond much like a normal system: with a bunch of errors that can be checked in the logs. How exactly did you partition your disk? I just chose the easy way ... 1 partition for everything, but I chose to use LVM for the partition (just did it for some testing). What tasks did you select? I installed the Spanish version, but it would be something like the Desktop (first option in the menu) + Standard (last option). On which file system did you run out of space? Only had 1 partition. The Desktop task should only be shown as installable if there is sufficient free disk space, though the check is probably too tight at the moment. Yup, I could select the desktop option and ended up out of space, so that will probably need some tweaking. Joey: I've just checked the required disk space for tasks, and 2GB is probably too low for Desktop. IMO you have to consider that Standard + Desktop + Laptop should be installable together. Well, I deleted some packages I didnt need to make some room after a successful install (chosing Desktop + Standard tasks) and installed VMtools (about 120 Mb). It's using 2.3 Gb after removing the .deb packages from the cache. So its quite possible the install is taking more space than what you have calculated. I will probably create another virtual machine with Debian tomorrow. I will use the snapshot net-install CD instead of the RC1 I used last time and let you know how much space it takes. That means (installed + download): Standard: 197 + 60 Desktop + Laptop: 1272 + 421 (Laptop adds only about 6 MB) Grand total: 1950MB That's all for now. Sorry I didnt answer faster, but I went late to bed yesterday, as i had a new year party. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405129: installation-reports: No message displayed if there is not enough space for the installation.
Package: installation-reports Severity: important I tried to install Etch using the RC1 installer (expertgui way). I didnt allocate enough space for the installation. Obviously, it couldnt finish the installation, and I was getting generic I cant install messages, giving me the option to try again, but I wasnt told that there just wasnt enough space. I had to get out of the installation and check for myself what was wrong. I think the gui should tell me that I was out of free space, instead of just failing and even telling me try to select the option again in the menu. PS: The System Info below is about my current working system, not the installer Im talking about. Not removing it because i dont know if reportbug will cry if I delete it. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.19.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405074: installation-reports: problem
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/etch_di_rc1/amd64/iso-cd/debian-testing-amd64-netinst.iso Image md5sum: 4df5c6a083f0c73c2ff8a825e8e75cfd debian-testing-amd64-netinst.iso Date: 2006-12-29 23:06 Machine: HP nx6325 Laptop, BIOS revision F.02 Processor: AMD Turion 64 X2 Memory: 2 GB RAM Partitions: none, did not get there! Output of lspci -nn and lspci -vnn: cannot access a shell! Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: When booting into install from the CD the screen goes blank and that's it. It does not make any difference whether I choose install acpi=off or just install. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#224641: [Patch] fixup serial support for grub for etch d-i
Tested patch of 22/11/06 by running d-i in expert mode and copying a patched grub-installer into /usr/bin/ of the running initrd. Grub is installed properly with serial terminal and the console= parameter is also added to kopt as it should be. With the current kernel you then hit bug http://bugs.debian.org/378204 which is a kernel bug that will disappear with the 2.6.18 kernel transition. Work arround for 2.6.17 kernels is to remove console=ttyS... from kernel command line in grub on first boot then login and either upgrade kernel to 2.6.18 OR echo blacklist 8250_pnp /etc/modprobe.d/local-8250_pnp-off Regards Alex Owen On 22/11/06, Alex Owen [EMAIL PROTECTED] wrote: Here is a revised version of the patch which also fixes syslinux.cfg_withgtk as suggested by Otavio Salvador in: http://lists.debian.org/debian-boot/2006/11/msg00959.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#224641: [Patch] fixup serial support for grub for etch d-i
Her is an updated (but untested) patch against the d-i/trunk to fix
serial support for grub-installer.
Please note that the ${CONSOLE} has been moved to after the -- so
that it is caught as a user param. This saves special casing in the
install-grub script (which was the fix in my last revision of the
patch).
Regards
Alex Owen
Index: installer/build/boot/x86/syslinux.cfg
===
--- installer/build/boot/x86/syslinux.cfg (revision 42805)
+++ installer/build/boot/x86/syslinux.cfg (working copy)
@@ -16,22 +16,22 @@
LABEL install
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL linux
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL expert
kernel ${KERNEL}
- append priority=low ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append priority=low ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL rescue
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} rescue/enable=true --
+ append ${VIDEO_MODE} initrd=${INITRD} rescue/enable=true -- ${CONSOLE}
LABEL auto
kernel ${KERNEL}
- append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
PROMPT 1
TIMEOUT 0
Index: packages/arch/i386/grub-installer/grub-installer
===
--- packages/arch/i386/grub-installer/grub-installer (revision 42805)
+++ packages/arch/i386/grub-installer/grub-installer (working copy)
@@ -37,11 +37,29 @@
if echo ${defconsole} | grep -q console=ttyS; then
local PORT=$(echo ${defconsole} | sed -e 's%^console=ttyS%%' -e 's%,.*%%')
local SPEED=$(echo ${defconsole} | sed -e 's%^console=ttyS[0-9]\+,%%' -e 's% .*%%')
- local SERIAL=${PORT},${SPEED}
+ local SERIAL=ttyS${PORT},${SPEED}
echo console=$SERIAL
fi
}
+grub_serial_console() {
+ #$1=output of get_serial_console
+ local unit=$(echo $1 | sed -e 's%^console=ttyS%%' -e 's%,.*%%')
+ local speed=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,%%' -e 's%[^(0-9)].*%%')
+ local parity=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,[0-9]\+%%' -e 's%[78].*%%')
+ case $parity in
+ n) local parity=no ;;
+ e) local parity=even ;;
+ o) local parity=odd ;;
+ *) local parity= ;;
+ esac
+ local word=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,[0-9]\+[oen]%%' -e 's%r%%')
+ local flow=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,[0-9]\+[oen][78]%%')
+
+ echo serial --unit=$unit --speed=$speed --word=$word --parity=$parity --stop=1
+ echo terminal serial
+ }
+
serial=$(get_serial_console)
# This is copied from update-grub; we've requested that it be moved
@@ -428,6 +446,12 @@
update_grub # again, to add new options to all the Debian kernel entries
fi
+if [ -n $serial ] ; then
+ # Modify menu.lst so _grub_ uses serial console.
+ grub_serial_console $serial | cat - $ROOT/boot/grub/$menu_file $ROOT/boot/grub/$menu_file.new
+ mv $ROOT/boot/grub/$menu_file.new $ROOT/boot/grub/$menu_file
+fi
+
# Generate menu.lst additions for other OSes
tmpfile=/tmp/menu.lst.extras
OLDIFS=$IFS
Bug#224641: [Patch] fixup serial support for grub for etch d-i
Here is a revised version of the patch which also fixes
syslinux.cfg_withgtk as suggested by Otavio Salvador in:
http://lists.debian.org/debian-boot/2006/11/msg00959.html
Index: installer/build/boot/x86/syslinux.cfg
===
--- installer/build/boot/x86/syslinux.cfg (revision 42805)
+++ installer/build/boot/x86/syslinux.cfg (working copy)
@@ -16,22 +16,22 @@
LABEL install
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL linux
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL expert
kernel ${KERNEL}
- append priority=low ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append priority=low ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL rescue
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} rescue/enable=true --
+ append ${VIDEO_MODE} initrd=${INITRD} rescue/enable=true -- ${CONSOLE}
LABEL auto
kernel ${KERNEL}
- append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
PROMPT 1
TIMEOUT 0
Index: installer/build/boot/x86/syslinux.cfg.withgtk
===
--- installer/build/boot/x86/syslinux.cfg.withgtk (revision 42805)
+++ installer/build/boot/x86/syslinux.cfg.withgtk (working copy)
@@ -16,34 +16,34 @@
LABEL install
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL linux
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL installgui
kernel ${KERNEL}
- append ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} ${CONSOLE} --
+ append ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} -- ${CONSOLE}
LABEL expert
kernel ${KERNEL}
- append priority=low ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append priority=low ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL expertgui
kernel ${KERNEL}
- append priority=low ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} ${CONSOLE} --
+ append priority=low ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} -- ${CONSOLE}
LABEL rescue
kernel ${KERNEL}
- append ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} rescue/enable=true --
+ append ${VIDEO_MODE} initrd=${INITRD} rescue/enable=true -- ${CONSOLE}
LABEL rescuegui
kernel ${KERNEL}
- append ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} ${CONSOLE} rescue/enable=true --
+ append ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} rescue/enable=true -- ${CONSOLE}
LABEL auto
kernel ${KERNEL}
- append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} ${CONSOLE} --
+ append auto=true priority=critical ${VIDEO_MODE} initrd=${INITRD} -- ${CONSOLE}
LABEL autogui
kernel ${KERNEL}
- append auto=true priority=critical ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} ${CONSOLE} --
+ append auto=true priority=critical ${VIDEO_MODE_GTK} initrd=${INITRD_GTK} -- ${CONSOLE}
PROMPT 1
TIMEOUT 0
Index: packages/arch/i386/grub-installer/grub-installer
===
--- packages/arch/i386/grub-installer/grub-installer (revision 42805)
+++ packages/arch/i386/grub-installer/grub-installer (working copy)
@@ -37,11 +37,29 @@
if echo ${defconsole} | grep -q console=ttyS; then
local PORT=$(echo ${defconsole} | sed -e 's%^console=ttyS%%' -e 's%,.*%%')
local SPEED=$(echo ${defconsole} | sed -e 's%^console=ttyS[0-9]\+,%%' -e 's% .*%%')
- local SERIAL=${PORT},${SPEED}
+ local SERIAL=ttyS${PORT},${SPEED}
echo console=$SERIAL
fi
}
+grub_serial_console() {
+ #$1=output of get_serial_console
+ local unit=$(echo $1 | sed -e 's%^console=ttyS%%' -e 's%,.*%%')
+ local speed=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,%%' -e 's%[^(0-9)].*%%')
+ local parity=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,[0-9]\+%%' -e 's%[78].*%%')
+ case $parity in
+ n) local parity=no ;;
+ e) local parity=even ;;
+ o) local parity=odd ;;
+ *) local parity= ;;
+ esac
+ local word=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,[0-9]\+[oen]%%' -e 's%r%%')
+ local flow=$(echo $1 | sed -e 's%^console=ttyS[0-9]\+,[0-9]\+[oen][78]%%')
+
+ echo serial --unit=$unit --speed=$speed --word=$word --parity=$parity --stop=1
+ echo terminal serial
+ }
+
serial=$(get_serial_console)
# This is copied from update-grub; we've requested that it be moved
@@ -428,6 +446,12 @@
update_grub # again, to add new options to all the Debian kernel entries
fi
+if [ -n $serial ] ; then
+ # Modify menu.lst so _grub_ uses serial console.
+ grub_serial_console $serial | cat - $ROOT/boot/grub/$menu_file $ROOT/boot/grub/$menu_file.new
+ mv $ROOT/boot/grub/$menu_file.new $ROOT/boot/grub/$menu_file
+fi
+
# Generate menu.lst additions for other OSes
tmpfile=/tmp/menu.lst.extras
OLDIFS=$IFS
