Anselm Lingnau ha scritto:
> Alessandro Selli wrote:
>
>> I just think that it would take a bare minute telling people
>> that:
>>
>> 1) there are more attributes than ls or stat show you;
>> 2) they can be seen with lsattr and set/uset with chattr;
>> 3) the really useful and fully implemented/supported ones are the
>> immutable and append-only attribs;
>> 4) for a full list of supported attributes see man chattr(1).
> I wouldn't bother putting file attributes in LPIC-1 because they're not used
> a
> lot, because the set of file attributes that do something actually useful and
> are in fact implemented is pretty small, and because it depends on the file
> system being used whether they're supported at all, and on the tools being
> used whether they get copied along/archived/… with the rest of the file
> they're attached to. IMHO they're generally more trouble than they're worth.
I'm just playing the devil's advocate here.
Most modern distributions use the ext4 driver to handle all ext*
filesystems. ext4 does support the most often used attributes, the LPIC
objective could only consider those.
I don't think we should worry about attributes' permanence between
filesystems or across archival tools, at least no more than we already
do about the vfat filesystem. Just assume the candidate is aware that
they could disappear under particular circumstances.
Worthiness of tools is a difficult matter to evaluate. Everything is
worthelss until you need it. Something is worthier than something else
even if you use it 1/100 the times. I do think the burden of
considering the append-only and immutable attributes to be pretty low,
and those attributes are supported by all the filesystems distributions
format installation storage by default.
[...]
[About wireless]
> If we wanted to do this topic right it ought to get its own objective
> and its own weight. Sticking it into 205.1, »basic networking
> configuration«, which at weight 3 covers a massive swathe of material
> makes it into one of those open- ended issues where you spend half a
> day in class to cover (probably) one question's worth of exam time.
> (The same problem applies to the mention of IPv6 in the same
> objective.) I suppose it is too late now to fix this.
I agree here. I'm thinking of inserting a new, wireless specific
objective. We now have:
Topic 205: Networking Configuration
205.1 Basic networking configuration (*)
205.2 Advanced Network Configuration and Troubleshooting
205.3 Troubleshooting network issues
205.4 Notify users on system-related issues
(*) Right now this explicitly includes the /sbin/iwconfig and
/sbin/iwlist commands
We might have:
Topic 205: Networking Configuration
205.1 Basic networking configuration (generic)
205.2_new Basic wireless settings and configuration
205.3 Advanced Network Configuration and Troubleshooting
205.4 Troubleshooting network issues
205.5 Notify users on system-related issues
A possible 205.2_new description could run:
**Candidates should be able to configure a wireless network device to be
able to connect to an access-point in infrastructure mode (ESS) or to
other wireless devices in ad-hoc mode (IBSS). This objective includes
being able to detect present hardware settings (including national
regulatory compliance) and to set it in the appropriate way to be able
to communicate between various wireless devices.
I would keep the settings and the configuring separated items because
some settings prevent some configuration settings from being
accepted/available.
I cannot make up my mind if wpa_supplicant needs to be covered or if
the objective should only assume knowledge of the iw (iwconfig) command.
--
Alessandro Selli <[email protected]>
Tel. portatile: 340.839.73.05
VOIP SIP: [email protected]
Sito web: http://alessandro.route-add.net/
Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
