Maybe I should stress again that udhcp does work as intended if
"/etc/init.d/udhcpd" start is called from a interactive shell.
Am 03.03.2015 um 03:58 schrieb Cyril Brulebois:
Hi Michael,
Michael Kockmeyer (2015-03-03):
Package: udhcpd
Version: 1:1.20.0-7
udhcpd does not start up at boot tim
udhcpd comes with a /etc/default/udhcpd file:
| # Comment the following line to enable
| DHCPD_ENABLED="no"
|
| # Options to pass to busybox' udhcpd.
| #
| # -SLog to syslog
| # -frun in foreground
|
| DHCPD_OPTS="-S"
Yes, I know that, that line is commented out.
--
To UNSUBSCRIBE,
Package: installation-reports
Severity: normal
Tags: d-i
Dear Maintainer,
Please find bellow my installation report on a MacBook Pro 11-1.
Boot method: USB with week-build Jessie installer netinst iso (2015-03-02)
Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd
/debian
Hello,
My personal systems follow the following partitioning scheme:
1) /boot (ext2)
2) /tmp (random key-encrypted ext2)
3) SWAP (random key-encrypted)
4) everything else (password encrypted, BTRFS)
I'm contemplating to start maintaining/document installation suing
preseeding and was wondering w
After trying to install the system again to see if I could replicate it the
issue, I made a usb key where the firmware-iwlwifi package contained only the
1000-5.ucode file. Initially the interface
asks about 1000-5.ucode, however when I try to load the non-free firmware it
seems like the driver
On Tue, 2015-03-03 at 19:52 +0100, Jon Jahren wrote:
> After trying to install the system again to see if I could replicate it the
> issue, I made a usb key where the firmware-iwlwifi package contained only the
> 1000-5.ucode file. Initially the interface
> asks about 1000-5.ucode, however when
Voeg n...@io-dagaanbieding.nl toe aan je adressenboek om er zeker van te zijn
dat je e-mails van I&O-dagaanbieding zult ontvangen
Uw Dagaanbieding van dinsdag 24 juni 2014
This mail has been sent to :console-se...@packages.debian.org
Ben Hutchings (2015-03-03):
> Yes, that's right. The problem is that we now detect missing firmware
> by scraping the kernel log, and we still pick up old ones after
> installing firmware and poking the driver.
>
> I think we could solve this by noting the timestamp at the bottom of the
> kernel
8 matches
Mail list logo