3/21 Seriously guys, can you please start using motdedit? It's pretty
rude not to.
\_ The motd is a commons, while most people respect the
rights of others to use a commons some people do not.
And those few spoil the commons for everyone. Its a
tragedy that we must all live with.
\_ Uhm, no. Let's get this straight -- clobbering content is rude.
Using motdedit is just ONE way to avoid doing that. Equating
motdedit with common courtesy is just stupid. -mice
\_ Apologies to the authors, but fuck motdedit in the ear.
\_ because?
\_ Because it's a solution to a problem I don't have, and
\_ Why should I show any respect for you since you obviously
don't care about anyone but yourself?
because I'm irritated by the holier than thou preachy
assholes that insist I'm rude/stupid/selfish if I don't use
it. I don't overwrite other people's entries, and I can't
seem to recall getting mine overwritten either. I use vi.
\_ Um.. case in point. My reply to your eloquently stated
"fuck motdedit..." was overwritten. --scotsman
\_ Uhm, yeah and...? You say this as though it's my
fault. I find it highly unlikely that I was
responsible as you seem to be implying. cf "vi",
"respecting locks", etc
\_ society's to blame. But your insecurities are in
\_ you rude shit. you motdedited out stuff that's been sitting here
for 20 minutes. using motdedit doesn't excuse smashing other's
content.
\_ path?
\_ /csua/bin/me
the way of getting the point.
\_ So, lacking anything relevant to say, you trot
out personal insults. Uhm, yeah, whatever.
\_ this is someone else talking, but vi guy:
have you tried "me"? It's the same as
motdedit, requires less typing than
"vi /etc/motd.public" and uses an editor
agnostic locking scheme. I don't know about
preachiness, but it seems like a simple
compromise. Is there anything that vi offers
that "me" doesn't?
\_ Dude, motdedit is a technical solution to a difficult usage
problem. If you don't like someone overwriting your entries,
you should start using it. I would bet that most of the
overwritten entries are caused when someone using emacs or
jove makes an entry while someone is using motdedit. The
person not using motdedit loses out. Use it or don't, but
quit the complaining. --scotsman
\_ I use motdedit w/ vi and my entries are routinely
overwritten.
\_ I don't use it. I also don't over write other's entries and
don't complain when other's over write mine.
And btw, what do you have against vi users? Can't they get
their edits smushed too? Or pine? Don't pine users count?
How to edit motd in pine??
\_ If you have to ask, you don't know. The problem is that
editors such as emacs and pico don't tell you that there's
a lock on the file (at least by default), so you very
well could be overwriting someone else's entry without
knowing it. And I use vi myself, so I have no idea what
you're talking about. If you use vi, it respects those
locks anyway, so motdedit becomes a convenience in terms
of getting your own lock. motdedit isn't a replacement
for common courtesy. Using it, however, _is_ common
courtesy. --scotsman
\_ I don't know about pico, but emacs always warns me
that I'm about to change a file that has changed on
disk. When it does that, I copy my changes to
*scratch* and merge them back.
\_ Not the issue. --scotsman
\_ huh? you can use whatever editor you want. just set
EDITOR.
\_ And ED! What about the ED! users?
\_ Stick you head in a pig.
\_ how about root just makes /etc/motd.public writeable by motdedit
only? |