I've been looking at the bootscripts and want to do some fairly major
reorganization. I'm putting this out as a basis of discussion.
1. Remove /etc/sysconfig/rc
Presently this does
rc_base=/etc/rc.d
rc_functions=${rc_base}/init.d/functions
network_devices=/etc/sysconfig/network-devices
The i
This is requesting feedback on many of the exact things we discussed in a
recent thread, although some of the conclusions were different.
I can't pull up the exact thread at the moment since I'm on the road, but DJ
should be able to point the way.
Thanks,
JH
On Jul 7, 2011, at 12:31 PM, Bruc
Jeremy Huntwork wrote:
> This is requesting feedback on many of the exact things we discussed
> in a recent thread, although some of the conclusions were different.
I believe you are referring to the thread starting at
http://linuxfromscratch.org/pipermail/lfs-dev/2011-May/064677.html
There are
On Thu, Jul 7, 2011 at 9:31 AM, Bruce Dubbs wrote:
> I've been looking at the bootscripts and want to do some fairly major
> reorganization. I'm putting this out as a basis of discussion.
>
> 1. Remove /etc/sysconfig/rc
>
> Presently this does
>
> rc_base=/etc/rc.d
> rc_functions=${rc_base}/init
Nathan Coulson wrote:
>> 2. Â Remove /etc/sysconfig/network-devices
>>
>> Move the scripts ifdown, iftest, and ifup to /sbin. Â Integrate
>> ipv4-static* into the if* commands.
>
> I did not like how ifup/down was getting complicated, but would this
> not lock us into ipv4/static support only?
>
On Thu, Jul 7, 2011 at 12:53 PM, Bruce Dubbs wrote:
> Nathan Coulson wrote:
>
>>> 2. Â Remove /etc/sysconfig/network-devices
>>>
>>> Move the scripts ifdown, iftest, and ifup to /sbin. Â Integrate
>>> ipv4-static* into the if* commands.
>>
>> I did not like how ifup/down was getting complicated, b
Nathan Coulson wrote:
>> Alternatively we could use something like:
>>
>> #TYPE:IP:PREFIX:MASK:GATEWAY:BOOT
>> eth0=static:192.168.1.1:24:192.168.1.255:192.168.1.1:onboot
>
> that, is beautiful.
I'm not sure about that. :)
> [ipv6 uses : for deliminators if I recall]
Yes, of course. I forgot
On Jul 7, 2011, at 4:28 PM, Nathan Coulson wrote:
> speaking of, I never dug into ipv6 yet, wonder what it's going to require.
Just FYI on IPv6:
For static assignments `ip` usage is identical to IPv4, just with a different
address format:
ip addr add dev eth0 1:1:1:1:2:2:2:2/64
Zachary Kotlarek wrote:
> I haven't ever found a use for a DHCPv6 client,
Dynamic DNS: having the DHCP server update the DNS server with A, ,
PTR, and (well, uh... more PTR) records for each client that registers
with it (and which sends a hostname in the request, of course, but AFAIK
this is
Bruce Dubbs wrote:
> Nathan Coulson wrote:
>
>>> Alternatively we could use something like:
>>>
>>> #TYPE:IP:PREFIX:MASK:GATEWAY:BOOT
>>> eth0=static:192.168.1.1:24:192.168.1.255:192.168.1.1:onboot
>> that, is beautiful.
>
> I'm not sure about that. :)
Adding extra fields for each new service
On Jul 7, 2011, at 10:05 PM, Bryan Kadzban wrote:
> Zachary Kotlarek wrote:
>> I haven't ever found a use for a DHCPv6 client,
>
> Dynamic DNS: having the DHCP server update the DNS server
I can see that. I moved to mdns for such things well before I added IPv6 to my
network, so I've never ca
On Thu, Jul 7, 2011 at 3:26 PM, Bruce Dubbs wrote:
> Nathan Coulson wrote:
>
>>> Alternatively we could use something like:
>>>
>>> #TYPE:IP:PREFIX:MASK:GATEWAY:BOOT
>>> eth0=static:192.168.1.1:24:192.168.1.255:192.168.1.1:onboot
>>
>> that, is beautiful.
>
> I'm not sure about that. :)
>
>> [ipv
12 matches
Mail list logo
