From: Karel Zak <kzak@redhat.com>
To: Felix Miata <mrmazda@earthlink.net>
Cc: util-linux@vger.kernel.org
Subject: Re: global fdisk colors disable
Date: Thu, 16 Jan 2014 10:59:27 +0100 [thread overview]
Message-ID: <20140116095927.GO12700@x2.net.home> (raw)
In-Reply-To: <52D7A542.70805@earthlink.net>
On Thu, Jan 16, 2014 at 04:24:18AM -0500, Felix Miata wrote:
> On 2014-01-15 10:21 (GMT-0500) Mike Frysinger composed:
>
> >On Wednesday 15 January 2014 09:10:19 Felix Miata wrote:
>
> >>I have many logins on many installations. In what global config file (e.g.
> >>Debian, Fedora, Gentoo, Knoppix, Mageia, openSUSE, Slackware, etc.) can I
> >>make never the default for all users?
>
> >/etc/profile
>
> That always seems to have a rather recent date, even though I never touch
> it. Are you sure you don't mean /etc/profile.local?
For example Fedora uses /etc/profile where is:
for i in /etc/profile.d/*.sh ; do
if [ -r "$i" ]; then
if [ "${-#*i}" != "$-" ]; then
. "$i"
else
. "$i" >/dev/null
fi
fi
done
and in the /etc/profile.d/ directory are many scripts, for example
/etc/profile.d/colorls.sh with --color=auto alias for ls(1).
It's pretty common that people and packages add/modify the stuff in
the /etc/profile.d/ directory.
IMHO it's elegant way how to maintain global configuration for shells.
The files like ~/.bash_profile are users' playground and I don't think
that good admin touches these ~/ files.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-01-16 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 6:47 global fdisk colors disable Felix Miata
2014-01-15 8:27 ` Karel Zak
2014-01-15 9:30 ` Pádraig Brady
2014-01-15 10:24 ` Karel Zak
2014-01-15 14:14 ` Felix Miata
2014-01-15 14:10 ` Felix Miata
2014-01-15 15:21 ` Mike Frysinger
2014-01-16 9:24 ` Felix Miata
2014-01-16 9:59 ` Karel Zak [this message]
2014-01-15 17:11 ` Karel Zak
2014-01-16 9:06 ` Felix Miata
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140116095927.GO12700@x2.net.home \
--to=kzak@redhat.com \
--cc=mrmazda@earthlink.net \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox