On Sunday 23 September 2007, John R. Graham wrote:
On Thursday 20 September 2007, Mike Frysinger wrote:
no, this cannot live in baselayout (the package that creates /root/),
because it cannot be run everytime a user upgrades the baselayout
package. no, it cannot be tied to USE=build (used
On Friday 21 September 2007, Chris Gianelloni wrote:
On Fri, 2007-09-21 at 17:45 -0400, Mike Frysinger wrote:
the compromise is simple: catalyst runs --config at the end of stage3 for
appropriate packages, but as to what those things actually do is left in
the ebuilds.
I've already stated
Mike Frysinger wrote:
we should really rename build to stage1, bootstrap to stage2, and then
have catalyst add USE=stage3 during the stage3 step ... that would allow
packages to automatically key off of the environment
I like this idea (hurray clarity!), but it would add an extra possibly
On Thursday 20 September 2007, Mike Frysinger wrote:
no, this cannot live in baselayout (the package that creates /root/), because
it cannot be run everytime a user upgrades the baselayout package. no, it
cannot be tied to USE=build (used to make stage1) or USE=bootstrap (use to
make
On Thu, 2007-09-20 at 20:52 -0400, Mike Frysinger wrote:
On Thursday 20 September 2007, Chris Gianelloni wrote:
Also, my plan for this would be add the copying of the .bash* files
from /etc/skel if and only if USE=build *and* the files do not already
exist, done during
On Fri, 2007-09-21 at 11:37 -0700, Chris Gianelloni wrote:
ebuild when it is being merged. If this really is so objectionable, I'd
just assume WONTFIX the request and move on with it.
+1
--
[EMAIL PROTECTED] mailing list
On Friday 21 September 2007, Chris Gianelloni wrote:
On Thu, 2007-09-20 at 20:52 -0400, Mike Frysinger wrote:
On Thursday 20 September 2007, Chris Gianelloni wrote:
Also, my plan for this would be add the copying of the .bash* files
from /etc/skel if and only if USE=build *and* the files
On Fri, 2007-09-21 at 17:45 -0400, Mike Frysinger wrote:
the compromise is simple: catalyst runs --config at the end of stage3 for
appropriate packages, but as to what those things actually do is left in the
ebuilds.
I've already stated my preference for not doing *anything* outside of
John R. Graham wrote:
Why can't the simple little default
.bash_profile from /etc/skel be put into /root as well?
$HOME directories shouldn't be touched by emerge. This is the user's turf.
signature.asc
Description: OpenPGP digital signature
On Wednesday 19 September 2007, Andrew Gaffney wrote:
John R. Graham wrote:
On the forums, I've seen the question, Why isn't my .bashrc being
executed when I log in as root but is being executed when I log in as a
normal user?, asked half a dozen times on the forums. Heck, I even
asked it
On Wednesday 19 September 2007, Mike Doty wrote:
John R. Graham wrote:
like sys-apps/miscfiles. But where it should or shouldn't come from
doesn't answer the fundamental question, Shouldn't it be there, from
*some* source?
Easy answer: no. Do you really want any script to automatically
Am Donnerstag, 20. September 2007 schrieb ext Alin Năstac:
John R. Graham wrote:
Why can't the simple little default
.bash_profile from /etc/skel be put into /root as well?
$HOME directories shouldn't be touched by emerge.
And especially not root's $HOME.
Bye...
Dirk
--
Dirk
I didn't say anything about emerge; I was talking about the Stage
tarballs. I know, I know: Catalyst uses emerge.
But, hasn't anyone realized that bash is _broken_ if this file doesn't
exist? Quoting from the upstream-provided man page, When an
interactive shell that is not a login shell is
John R. Graham wrote:
I didn't say anything about emerge; I was talking about the Stage
tarballs. I know, I know: Catalyst uses emerge.
But, hasn't anyone realized that bash is _broken_ if this file doesn't
exist? Quoting from the upstream-provided man page, When an
interactive shell that
Mike, I agree. But, the file that _must_ exist isn't ~/.bashrc but
~/.bash_profile. That's where the that particular bit of
man-page-defined behavior is implemented. If ~/.bash_profile doesn't
exist, then ~/.bashrc won't be sourced whether it exists or not.
- John
--
[EMAIL PROTECTED] mailing
Andrew. Sorry 'bout the top posting; won't do it again. For the rest,
please see my reply to Mike Auty on the same topic.
- John
--
[EMAIL PROTECTED] mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John R. Graham wrote:
Mike, I agree. But, the file that _must_ exist isn't ~/.bashrc but
~/.bash_profile. That's where the that particular bit of
man-page-defined behavior is implemented. If ~/.bash_profile doesn't
exist, then ~/.bashrc won't
On Wed, 2007-09-19 at 21:57 -0400, John R. Graham wrote:
Why can't the simple little default
.bash_profile from /etc/skel be put into /root as well
/etc/skel is for users created by the add user commands.
root is inherently added *before* bash is installed, thus
doesn't get anything from skel.
On Thu, 20 Sep 2007 08:09:08 -0400 John R. Graham [EMAIL PROTECTED]
wrote:
Mike, I agree. But, the file that _must_ exist isn't ~/.bashrc but
~/.bash_profile.
That's wrong. Quote:
When bash is invoked as an interactive login shell, or as a non-inter-
active shell with the --login option, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You could add '[ -n ${BASH} -a -f ~/.bashrc ] . ~/.bashrc' to
/etc/profile.d/bash.sh. This file could be installed by app-shells/bash.
- --
Arfrever Frehtes Taifersar Arahesis
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
On Thu, 2007-09-20 at 03:03 -0400, Mike Frysinger wrote:
what catalyst should do is just before cleaning up the stage3 root and
packing
it up is run `rsync -a /etc/skel/ /root/`
It definitely should not. One of my primary motivations with catalyst
is to ensure that the users get *exactly*
On Thu, 2007-09-20 at 13:29 +0100, Roy Marples wrote:
Also, don't assume that the root user uses the bash shell.
The root user does *default* to the bash shell on Linux, at least.
Of course, we could do whatever is appropriate for other targets.
--
Chris Gianelloni
Release Engineering
On Thursday 20 September 2007, Chris Gianelloni wrote:
On Thu, 2007-09-20 at 03:03 -0400, Mike Frysinger wrote:
what catalyst should do is just before cleaning up the stage3 root and
packing it up is run `rsync -a /etc/skel/ /root/`
It definitely should not. One of my primary motivations
On Thu, 2007-09-20 at 12:34 -0400, Mike Frysinger wrote:
what catalyst should do is just before cleaning up the stage3 root and
packing it up is run `rsync -a /etc/skel/ /root/`
It definitely should not. One of my primary motivations with catalyst
is to ensure that the users get
Renat Golubchyk wrote:
That's wrong. Quote:
When bash is invoked as an interactive login shell, or as a non-inter-
active shell with the --login option, it first reads and executes com-
mands from the file /etc/profile, if that file exists. After reading
that file, it looks for
On Thursday 20 September 2007, Chris Gianelloni wrote:
On Thu, 2007-09-20 at 12:34 -0400, Mike Frysinger wrote:
what catalyst should do is just before cleaning up the stage3 root
and packing it up is run `rsync -a /etc/skel/ /root/`
It definitely should not. One of my primary
Roy Marples wrote:
Looking over the bash man page, I cannot see the word recommended
anywhere near .bash_profile. Could you clarify where you think bash
recommends this?
Thanks
Roy
Why, sure. It's my interpretation, but a reasonable one, I think. It
recommends it in its
On Thu, 2007-09-20 at 19:17 -0400, John R. Graham wrote:
Rats. I checked the source and you're right. My problem domain is
smaller than I thought but still valid, I think. Basically the problem
is only with interactive login shells and /root. Not *broken*, per se:
just contrary to
On Thu, 2007-09-20 at 21:22 -0400, John R. Graham wrote:
Roy Marples wrote:
Looking over the bash man page, I cannot see the word recommended
anywhere near .bash_profile. Could you clarify where you think bash
recommends this?
Why, sure. It's my interpretation, but a reasonable
Roy Marples wrote:
No it's not. bash does not recommend anything of the sort. It just
states what files are optionally used during initialisation.
What I'm driving at is that you're making claims that things are broken
or recommended when in fact they are not. Try reading some RFC's and
then
John R. Graham wrote:
On the forums, I've seen the question, Why isn't my .bashrc being
executed when I log in as root but is being executed when I log in as a
normal user?, asked half a dozen times on the forums. Heck, I even
asked it myself a few years ago. Now, two years later, from a
Andrew Gaffney wrote:
When catalyst builds a stage tarball, it doesn't add any additional
files. All files in any stage tarball are created by one of the
packages contained within. In order to do this, a package such as
baselayout would have to install the file.
Looking at my local
John R. Graham wrote:
like sys-apps/miscfiles. But where it should or shouldn't come from
doesn't answer the fundamental question, Shouldn't it be there, from
*some* source?
Easy answer: no. Do you really want any script to automatically run
when you login as root? think of exploits and the
Mike, that exploit is neither easier nor harder if a default
.bash_profile exists. Or, am I missing something?
- John
Mike Doty wrote:
John R. Graham wrote:
like sys-apps/miscfiles. But where it should or shouldn't come from
doesn't answer the fundamental question, Shouldn't it be there,
34 matches
Mail list logo
