From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] coda auto-login
Date: Sat, 24 Feb 2007 04:47:25 -0600 [thread overview]
Message-ID: <200702240447.25219.bss03@volumehost.net> (raw)
In-Reply-To: <1172290736.31614.10.camel@yatahaze.skynet.local>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On Friday 23 February 2007 22:18, Jürgen Geuter wrote:
> On Sat, 2007-02-24 at 02:39 +0100, Enrico Weigelt wrote:
> > > If you need to execute something put it to
> > > /etc/conf.d/local.start or
> > > /etc/conf.d/local.stop
> >
> > Does not fully work, since some services require the coda
> > volumes mounted. So my only idea was to change /etc/init.d/venus
Modify those init scripts, adding or changing a 'depends' line. By default
init scripts are config protected so your changes will not be overwritten
willy-nilly.
> > But: there's another problem. Every user has to log into coda
> > by its own. This is bad if all user's homedirs should sit on coda.
>
> Put the login thingy as first line in a .-File that is executed upon
> login for every user. .bashrc or something.
If it is really something every local user needs to do, throw it
in /etc/profile.d -- those files are sourced by /etc/profile, which is read
by sh, bash, and zsh (at least), for all (?) shells.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
New GPG Key! Old key expires 2007-03-25. Upgrade NOW!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-24 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 19:58 [gentoo-user] coda auto-login Enrico Weigelt
2007-02-23 20:19 ` Neil Bothwick
2007-02-23 21:03 ` Ivan Perez
2007-02-23 20:46 ` Jürgen Geuter
2007-02-24 1:39 ` Enrico Weigelt
2007-02-24 4:18 ` Jürgen Geuter
2007-02-24 10:47 ` Boyd Stephen Smith Jr. [this message]
2007-02-26 6:56 ` Dirk Heinrichs
2007-03-18 16:57 ` Enrico Weigelt
2007-03-19 13:10 ` Dirk Heinrichs
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=200702240447.25219.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-user@lists.gentoo.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