On Vi, 14 dec 12, 22:23:21, Bob Proulx wrote:
Some things which need addressing:
- use of tmpfses for non-writable locations like /media: we should
be doing this by default; introducing /run/media on the /run
tmpfs was one thing looked at for wheezy; but it didn't get done
for
On 10.12.2012 00:09, Roger Leigh wrote:
On Sun, Dec 09, 2012 at 02:43:36PM -0700, Bob Proulx wrote:
Ross Boylan wrote:
Bob Proulx wrote:
This nfs startup part is a part that seems to have suffered from the
transition from boot time scripts to event driven scripts. This kind
of thing use to
Roger Leigh wrote:
This is an area which could use quite a bit of work. Unfortunately,
as you point out there isn't a single place to fix things--it
touches a whole host of packages, from the initramfs to the
initscripts, to udev and networking.
It does touch many things. The configuration
Wolfgang Karall lists+debian-u...@karall-edv.at wrote:
On 12/11/2012 11:08 AM, Chris Davies wrote:
Bob Proulx b...@proulx.com wrote:
The dhcpd will ping the address after the lease has expired and before
assigning it again and will notice that it is still in use and will
avoid assigning that
On Sun, Dec 09, 2012 at 02:43:36PM -0700, Bob Proulx wrote:
Ross Boylan wrote:
Bob Proulx wrote:
This nfs startup part is a part that seems to have suffered from the
transition from boot time scripts to event driven scripts. This kind
of thing use to work in the previous init script
Bob Proulx b...@proulx.com wrote:
The dhcpd will ping the address after the lease has expired and before
assigning it again and will notice that it is still in use and will
avoid assigning that address to another client.
ICMP ping? Are you sure?
According to the documents I've read (RFC2131
On 12/11/2012 11:08 AM, Chris Davies wrote:
Bob Proulx b...@proulx.com wrote:
The dhcpd will ping the address after the lease has expired and before
assigning it again and will notice that it is still in use and will
avoid assigning that address to another client.
ICMP ping? Are you sure?
Ross Boylan wrote:
I have a theory that the mounts are supposed to happen when the network
device comes up; the regular network up routines are not triggered to
avoid screwing up the root fs. /etc/network/interfaces has
# The primary network interface
# do not bring up interface twice--PXE
Bob Proulx wrote:
I don't think using dhcp is correct because the network is already up
and assigned. But perhaps it is because that would allow the system
to migrate to a different address after the lease expires. I don't
know. I didn't do any testing of that configuration. (Maybe later.)
The solution is to run
mount -a -t nfs
in /etc/rc.local.
Depending on your aesthetics, this might be considered a work-around.
More details below.
On Sun, 2012-12-09 at 01:19 -0700, Bob Proulx wrote:
Ross Boylan wrote:
I have a theory that the mounts are supposed to happen when the network
Bob Proulx wrote:
Ross Boylan wrote:
I have a theory that the mounts are supposed to happen when the network
device comes up; the regular network up routines are not triggered to
avoid screwing up the root fs. /etc/network/interfaces has
# The primary network interface
# do not
On Sun, 2012-12-09 at 14:11 -0700, Bob Proulx wrote:
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_network_configuration_with_ifupdown_legacy
P.P.S. Unanswered Question: Since the PXE boot used dhcp to obtain an
address that means there is a limited lease time
Ross Boylan wrote:
Bob Proulx wrote:
This nfs startup part is a part that seems to have suffered from the
transition from boot time scripts to event driven scripts. This kind
of thing use to work in the previous init script way. I don't know
the best design to make this work in the
I have a diskless workstation running testing, and although
its /etc/fstab is
/dev/nfs / nfs defaults 0 0
none /tmptmpfs defaults 0 0
none /var/runtmpfs defaults 0 0
none /var/lock tmpfs defaults 0 0
none
On 08.12.2012 23:09, Ross Boylan wrote:
192.168.40.2:/usr/local/mnt/usr/local nfs defaults 0 0
192.168.40.2:/usr/local/var/media /usr/local/var/media nfs defaults 0 0
The root fs is mounted correctly (during the boot sequence, before it
gets to fstab), but the other 2 NFS
On Sat, Dec 08, 2012 at 02:09:47PM -0800, Ross Boylan wrote:
I have a diskless workstation running testing, and although
its /etc/fstab is
/dev/nfs / nfs defaults 0 0
none /tmptmpfs defaults 0 0
none /var/runtmpfs defaults 0 0
none
Ross Boylan wrote:
I have a diskless workstation running testing, and although
its /etc/fstab is
/dev/nfs / nfs defaults 0 0
none /tmptmpfs defaults 0 0
none /var/runtmpfs defaults 0 0
none /var/lock tmpfs defaults 0
17 matches
Mail list logo
