You might be interested in this meeting at DebConf. It should be
streamed (see http://blog.debconf.org/blog/debconf13/hl_dc13_video.dc)
so others can participate by IRC, though I'm not sure how well that
works for meetings.
Secure Boot for Debian Linux
today, 14:30 CST (12:30 UTC), talk room 2
Linux kernel ABI bump in testing: from 3.9-1 to 3.10-2
Full summary: http://d-i.debian.org/kernel-summary.html#testing
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hi,
It seems you have a couple of separate ideas maybe:
* a pre-configured system, a project more like a 'Debian Pure Blend'
* a generic 'tasksel' task of networking utils
The FreedomBox is an example of a more specialised project. Debian Edu
also preconfigures its servers for NAT. And there
Hi,
On 03/08/13 14:58, Christian PERRIER wrote:
Quoting Steven Chamberlain (ste...@pyro.eu.org):
Yes, for grub2 2.0 we just need to drop pxecmd. Sort of related to
So, you mean drop it from there?
installer/build/config/hurd.cfg:GRUB_MODULES_PXE=pxe pxecmd
I've done this with my first
Colin Watson and Stefano Rivera talked about how Ubuntu had implemented
Secure Boot and what they believed were the requirements.
Apparently, the Secure Boot spec requires each stage of the boot code to
validate signatures only until ExitBootServices() is called. (At this
point the firmware
On Tue, 2013-08-13 at 22:54 +0200, Ben Hutchings wrote:
Colin Watson and Stefano Rivera talked about how Ubuntu had implemented
Secure Boot and what they believed were the requirements.
[...]
Sorry, I'm having name confusion here. Who do I really mean?
Ben.
--
Ben Hutchings
Experience is
Hi,
many thanks for the summary.
Ben Hutchings b...@decadent.org.uk (2013-08-13):
Colin Watson and Stefano Rivera talked about how Ubuntu had implemented
Secure Boot and what they believed were the requirements.
Apparently, the Secure Boot spec requires each stage of the boot code to
Cyril Brulebois wrote:
(Sorry, I'm new to all this) do you mean (1) the regular linux image
packages are getting a signature added, and we're using those like we do
today, or (2) that we'll have additional linux image packages with the
signatures to be used instead of the usual linux image
On Tue, 2013-08-13 at 23:38 +0200, Cyril Brulebois wrote:
[...]
4. The kernel team may also need to upload kernel images for signing and
add linux-image-signed packages with the Debian-signed kernel images.
This is because some quirks in the kernel should be run before calling
Debian installer build overview
---
Failed or old builds:
* OLD BUILD:armhf Aug 11 09:48 buildd@hasse build_mx5_netboot
http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot.log
* OLD BUILD:armhf Aug 11 09:51 buildd@hasse
good day sir.
i just installed debian wheezy kde from a live cd
image. but any time i try to apt-get update or aptitude update i get
this message=
Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64
LIVE/INSTALL Binary 20130505-13:41] wheezy Release.gpg
Ign cdrom://[Debian
11 matches
Mail list logo