Re: [opensuse] Systemd and fstab

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-12-14 03:51, Rüdiger Meier wrote:
On Wednesday 14 December 2011, Cristian Rodríguez wrote:
On 13/12/11 19:26, Carlos E. R. wrote:
What documentation?

There is plenty of documentation, probably even more than what
sysvinit ever had :)

But we look for mount options in fstab and mount manuals, not on systemd
(and systemv) manuals - which are pretty difficult read, by the way.

And the sysvinit was documented on the openSUSE PDF big manual, an entire
chapter of well written documentation. Systemd is not.


Obviously /etc/fstab is out of sysvinit's focus so no need to be
documented there.

either in the man pages, in Lennart's blog or
fedora wikis.

Don't blame users for not reading random blogs and random wikis.
Changing syntax of such fundamental config files like fstab should have
been mentioned in ReleaseNotes. There is a note about encrypted
partitions. Why not about nfs?

Exactly.

Many things have changed in this release, and documentation is scarce,
unless one is prepared to dig it out from all over internet - which may not
apply to openSUSE. Yes, I have been told that in a bugzilla, that those
docs do not apply to oS necessarily.

The people that have prepared the distro and made the decisions should have
taken time to document all that they did. And if they did not have time,
the release should have been delayed so that they got the time.

BTW is comment=systemd.automount added for nfs partitions on zypper dup?
If not then it would be a another bug.

Nor is it added by the YaST nfs module. I used it the other day and it did
not add such an option. I reported a bug on it, and now I see two more that
should be added.

- --
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk7oHeMACgkQtTMYHG2NR9WU2QCgjrkDva/JYj+LLJIzkEtrzJTe
MVwAn0IUgevIFuwLiJWk6QRgAuJDFCjn
=JJDx
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

Relevant Pages

  • Man vs. Info: documenting the software
    ... How do I make a hard copy of the documentation for the GNU Libc ... The Info manuals are much closer to a “single document” ideal ... S> As long as a large number of packages have man pages, ...
    (comp.unix.shell)
  • Re: Hyperref queries
    ... TeX documentation really does need to be re-written for people who are ... Indeed - I can work with car maintenance manuals, ... Another difference with TeX is that it's not just a toolbox - it's more ...
    (comp.text.tex)
  • Re: Man vs. Info: documenting the software
    ... S> search with a single search command is more useful to me. ... And again, I already addressed this: Manuals like that, sure, make them ... And this is why the GNU attitude is harmful; ... for which the documentation is in an awful state. ...
    (comp.unix.shell)
  • Re: Man vs. Info: documenting the software
    ... IS> How do I make a hard copy of the documentation for the GNU Libc ... S> And again, I already addressed this: Manuals like that, sure, make ... IS> tutorials as well. ...
    (comp.unix.shell)
  • Re: DTV antennas?
    ... of the customer base has some form of written or on-screen learning or ... How about they can't find the documentation to read? ... It's not easy, rough reading, totally ... Manuals that are full of illustration and examples work ...
    (sci.electronics.design)