Le 04/12/2017 à 02:22, Thomas Goirand a écrit :
> On 12/03/2017 05:30 PM, Raphael Hertzog wrote:
>> In the last years, Petter Rheinholdtsen worked on isenkram[2] with a
>> similar but a bit broader goal. I noticed it has better support
>> of clouds and that it will install some virtualization/cloud
Le 23/08/2017 à 10:12, Cyril Brulebois a écrit :
> Ansgar Burchardt (2017-08-23):
>> Emmanuel Kasper writes:
>>> The default base system installed by debootstrap includes all packages
>>> with Pritority essential and
>>> important, but this was n
ion
commit 5e18585594bf93a1bec5e9f4f2496e016084805c
Author: Emmanuel Kasper
Date: Tue Aug 22 22:12:21 2017 +0200
Document which packages are installed by a default variant
The default base system installed by debootstrap includes all packages with
Pritority essential and
important, bu
Le 03/02/2017 à 23:55, Cyril Brulebois a écrit :
> Ian Campbell (2017-02-03):
>> On Fri, 2017-02-03 at 15:51 +0100, Emmanuel Kasper wrote:
>>> Actually on further research, net.ifnames and most dot-containing
>>> parameters are not here for the kernel, but to configure
Actually on further research, net.ifnames and most dot-containing
parameters are not here for the kernel, but to configure on boot various
systemd components, the list of which can be found in
systemd-232/man/kernel-command-line.xml
or online in
https://www.freedesktop.org/software/systemd/man/ke
Le 03/02/2017 à 12:38, Ian Campbell a écrit :
> On Fri, 2017-02-03 at 12:22 +0100, Emmanuel Kasper wrote:
>>>> A kernel boot param like net.ifnames=0 will be skipped when the
>>>> installer parses the boot option for setting the bootloader.
>> A kernel boot param like net.ifnames=0 will be skipped when the
>> installer parses the boot option for setting the bootloader.
>>
>> Found in di-utils:
>>
>> # Skip module-specific variables
>> varnodot="${var##*.*}"
>> if [ "$varnodot" = "" ]; t
Package: di-utils
Version: 1.117
Severity: minor
Tags: d-i
A kernel boot param like net.ifnames=0 will be skipped when the installer
parses the boot option for setting the bootloader.
Found in di-utils:
# Skip module-specific variables
varnodot="${var##*.*}"
Hi
I am reading in the debian installer guide
A “---” in the boot options has special meaning. Kernel parameters that
appear after the last “---” may be copied into the bootloader
configuration for the installed system (if supported by the installer
for the bootloader). The installer will automat
changes since v1:
* do not fallback on dangerous read only kernel mounts if grub-mount is
missing, just exit with error
>From 34a2c247fa08d4e01aa08b5b75977c66d71df4f8 Mon Sep 17 00:00:00 2001
From: Emmanuel Kasper
Date: Tue, 15 Nov 2016 14:52:23 +0100
Subject: [PATCH v2] use grub-mount as
>> Since version 1.45, os-prober instead uses grub-mount when it's
available
>> -- and if grub is installed to use os-prober, it will pull it in.
>
>> So unless another bootloader is also using os-prober, or someone
>> installs and uses it by hand, this won't happen in unstable/testing.
> It's not
Hello
I have noticed during fresh debian installs the package os-prober is
automatically installed when you select grub as a bootloader, as a
'Recommends' of grub-common.
Unfortunately the way os-prober detects other OSes on local media, might
prove cumbersome or even dangerous if you use do virtua
Package: installation-report
Severity: normal
Package: installation-reports
Boot method: CD
Image version: debian-testing-alpha-netinst downloaded the 19/05/2006
Date: 20/05/2006
Machine: Compaq Alphaserver DS10 with SRM console
Processor:EV6
Memory:512M
Partitions:
As seen by GNU parted
pa
13 matches
Mail list logo
