network

[email protected] Fri, 05 Dec 2014 04:59:57 -0800

If you use the [tab][tab] to get there, you'll be expecting to see the trailing slash.

Newer users look for / or .d to remember directories, not files.

Just sayin'.

Sent from my Android phone.

------ Original message------

From: Bryan J Smith

Date: Thu, 12/4/2014 11:13 AM

To: This is the lpi-examdev mailing list.;

Subject:Re: [lpi-examdev] LPI 201 - 205.3 and /etc/network

Why would be remove the trailing slash (/) for consistency?
Why not default to directories always having a trailing slash (/)?

-- bjs

On Thu, Dec 4, 2014 at 3:35 AM, Alessandro Selli <[email protected]> wrote:

On 04/12/2014 10:20, Harald Maaßen wrote:

I think Eric wants to change:

/etc/network, /etc/sysconfig/network-scripts/

into:

/etc/network/, /etc/sysconfig/network-scripts/

He only wants one more slash.... ;-)

All right, however I think that a candidate that correctly identifies /etc/network to be Debian-related and /etc/sysconfig/network-scripts/ to be RedHat-related does know the former is a directory. On the other hand, since /etc/sysconfig/network-scripts/ does have a trailing slash, it sounds congruous that either both or none of them has it. I'd vote to remove it from network-scripts/, though ;-)
Am 04.12.2014 um 10:15 schrieb Alessandro Selli:
On 04/12/2014 10:04, Alexandru Juncu wrote:
On 4 December 2014 at 10:28, Alessandro Selli <[email protected]> wrote:
Il 04/12/2014 08:42, Éric Deschamps ha scritto:
Le 03/12/2014 19:09, Alessandro Selli a écrit :
Il 03/12/2014 18:31, Éric Deschamps ha scritto:
Ok, but in this case I would just add the trailing slash to be a bit
clearer.

Would'nt you?
  It would be clearer, but RH (at least non ancient versions) does *not*
have anything in /etc/network, neither a file nor a directory.
But Debian family distros have a /etc/network/ directory..
  I know.  But this does not cause any ambiguity, because RH does not
have anything in /etc/network.
And:

$ [[ '/etc/network' = '/etc/sysconfig/network' ]] && echo True || echo False
False
$


QED
I think the idea is to cover both the RH and Debian directory structures.
Harald Maaßen already answered this.
He pointed out that this had already been taken care of:

http://wiki.lpi.org/wiki/LPIC-2#205.3_Troubleshooting_network_issues_.28weight:_4.29

205.3 Troubleshooting network issues (weight: 4)
[...]

The following is a partial list of the used files, terms and utilities:
[...]
/etc/network, /etc/sysconfig/network-scripts/

What else do you think is needed and why?
-- 
Alessandro Selli <[email protected]>
Tel. portatile: 340.839.73.05
VOIP SIP: [email protected]
Sito web: http://alessandro.route-add.net/
Chiave firma PGP/GPG signing key: B7FD89FD
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
-- 
Alessandro Selli <[email protected]>
Tel. portatile: 340.839.73.05
VOIP SIP: [email protected]
Sito web: http://alessandro.route-add.net/
Chiave firma PGP/GPG signing key: B7FD89FD
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

--
Bryan J Smith - http://www.linkedin.com/in/bjsmith

_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Re: [lpi-examdev] LPI 201 - 205.3 and /etc/network

205.3 Troubleshooting network issues (weight: 4)

Reply via email to