The patch to have GRUB load a device-tree is interesting. This is
certainly worthy of discussion.
Three issues come up when looking though:
First, your patch modifies /etc/grub.d/10_linux, but misses
/etc/grub.d/10_linux_xen. /etc/grub.d/10_linux_xen needs a fairly
similar treatment.
Second, r
For a Raspberry PI, I've got the initial workings of a script to
accomplish this goal.
First, install u-boot-rpi, raspi-firmware, and grub-efi-arm64.
Next, create a filesystem on a device the Raspberry PI will boot from.
For anything pre-RP4, this will have to VFAT and show up in a MBR. A
system
There may be several distinct bugs involved with #824954. For one, I
suspect `grub-install`'s behavior needs to change if EFI variables aren't
supported. I use this as a flag which could distinguish installation on
top of a full EFI implementation (perhaps Tianocore-derived), versus
U-Boot's rath
Package: flash-kernel
Version: 3.103
Severity: wishlist
Subject should say it all.
I would like to learn what actions `flash-kernel` would be taking.
Having simulate and verbose options is a common software feature.
--
(\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/)
sted for use as an ifupdown hook script by Elliott Mitchell
# .
#
### BEGIN INIT INFO
# Provides: udhcpd
# Required-Start:$remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start busybox udhcpd at boot
On Fri, Mar 06, 2015 at 09:02:39AM +0300, Michael Tokarev wrote:
> 06.03.2015 02:57, Elliott Mitchell wrote:
> > The documentation seems to suggest udhcpd can only handle binding to one
> > interface and using one IP address range per udhcpd process. Due to
> > this, it would
Upon a bit more thinking about the situation, I must suggest the
overlapping feature of adding a hook script to allow udhcpd to be
started/stopped by `ifupdown` instead of only by init script. This ends
up dovetailing into support for multiple interfaces.
--
(\___(\___(\__ --=> 8-)
Package: udhcpd
Version: 1:1.20.0-7
Severity: wishlist
The documentation seems to suggest udhcpd can only handle binding to one
interface and using one IP address range per udhcpd process. Due to
this, it would be handy if Debian's init scripts had support for
starting/stopping multiple udhcpd pr
8 matches
Mail list logo
