#3145: Unify the service configuration files for Dhclient (ISC DHCP) and Dhcpcd
-------------------------+--------------------------------------------------
Reporter: willimm | Owner: blfs-b...@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.5
Component: BOOK | Version: SVN
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
Comment(by willimm):
Replying to [comment:4 d...@…]:
> There is a little more to it than that. That is why I was asking
specifically what you had in mind. What do we do with the ONBOOT
parameter? I'm not familiar with NM, can it be started before before the
GUI, or do we need to handle it in CLI and wait until the GUI is brought
up to pass control? Can it be built without the GUI and the GUI
components built after X? What about the proposed link state checks?
/sys/class/net/${DEVICE}/carrier? If NM can handle that for us and can
run from CLI without user interaction, then that would be perfect as we
can just eliminate all of my questions and let NM do its job.
What we could do with the ONBOOT parmater, due to the modularity of the
network scripts, we can use it to control which script starts up at boot
time. That would be the most idea way without radical changes to the LFS
initscript system.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/3145#comment:5>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
