[gentoo-user] heads-up: 2011-05-01 baselayout news

[gentoo-user] heads-up: 2011-05-01 baselayout news

[Thanasis]

I am running default/linux/amd64/10.0/no-multilib profile, and I got the
following news item, after syncing this morning:

# eselect news read

2011-05-01-baselayout-update
  Title                     Baselayout update
  Author                    Christian Faulhammer <fauli@gentoo.org>
  Author                    William Hubbs <williamh@gentoo.org>
  Posted                    2011-05-01
  Revision                  1

The baselayout package provides files which all systems must have in
order to function properly. You are currently using version 1.x, which
has several issues. The most significant of these is that the included
init scripts are written entirely in bash, which makes them slow and
not very flexible.

On 2011/05/08, you will see an update for sys-apps/baselayout to
2.x and a new package, sys-apps/openrc. It is recommended that you
perform this update as soon as possible.

Please note, after these packages are emerged, it is
__Absolutely_Critical__ that you immediately update your configuration
files with dispatch-conf, etc-update or a similar tool then follow the
steps in the migration guide located at the following URL.
http://www.gentoo.org/doc/en/openrc-migration.xml

FAILURE TO FOLLOW ALL OF THESE STEPS WILL RESULT IN AN UNBOOTABLE
SYSTEM! IF THIS SHOULD HAPPEN, YOU WILL NEED TO BOOT FROM A LIVE CD OR
DVD, MOUNT YOUR ROOT FILE SYSTEM, CHROOT INTO THAT ENVIRONMENT AND
FOLLOW THE ABOVE STEPS!

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Thanasis]

Let me add that my system defaults to the _stable_ software branch.

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 405 bytes --]

On Monday 02 May 2011 10:11:06 Thanasis wrote:
> Let me add that my system defaults to the _stable_ software branch.

Thanks for the heads up.  :)

It seems then that Baselayout2/OpenRC is being rolled out to stable.  I'll be 
unmasking and updating a couple of boxen today, taking advantage of some spare 
time and finishing the rest off next weekend.

Hope all goes well.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mark Knecht]

On Mon, May 2, 2011 at 2:31 AM, Mick <michaelkintzios@gmail.com> wrote:
> On Monday 02 May 2011 10:11:06 Thanasis wrote:
>> Let me add that my system defaults to the _stable_ software branch.
>
> Thanks for the heads up.  :)
>
> It seems then that Baselayout2/OpenRC is being rolled out to stable.  I'll be
> unmasking and updating a couple of boxen today, taking advantage of some spare
> time and finishing the rest off next weekend.
>
> Hope all goes well.
> --
> Regards,
> Mick
>

How will you / did you decide what versions to unmask? The news
message seems quite vague and I see lots of versions of things. Two
2.X versions of baselayout and four versions of OpenRC.

I'd potentially start updating a stable machine today but I'd prefer
to only unmask what is actually going to become the stable version and
nothing higher.

- Mark

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1143 bytes --]

On Monday 02 May 2011 18:11:01 Mark Knecht wrote:
> On Mon, May 2, 2011 at 2:31 AM, Mick <michaelkintzios@gmail.com> wrote:
> > On Monday 02 May 2011 10:11:06 Thanasis wrote:
> >> Let me add that my system defaults to the _stable_ software branch.
> > 
> > Thanks for the heads up.  :)
> > 
> > It seems then that Baselayout2/OpenRC is being rolled out to stable.
> >  I'll be unmasking and updating a couple of boxen today, taking
> > advantage of some spare time and finishing the rest off next weekend.
> > 
> > Hope all goes well.
> > --
> > Regards,
> > Mick
> 
> How will you / did you decide what versions to unmask? The news
> message seems quite vague and I see lots of versions of things. Two
> 2.X versions of baselayout and four versions of OpenRC.
> 
> I'd potentially start updating a stable machine today but I'd prefer
> to only unmask what is actually going to become the stable version and
> nothing higher.
> 
> - Mark

I've unmasked the latest available after reading the changelogs:

 sys-apps/baselayout-2.0.2

 sys-apps/openrc-0.8.2-r1

All seems to work fine here.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mark Knecht]

On Mon, May 2, 2011 at 10:36 AM, Mick <michaelkintzios@gmail.com> wrote:
<SNIP>
>
> I've unmasked the latest available after reading the changelogs:
>
>  sys-apps/baselayout-2.0.2
>
>  sys-apps/openrc-0.8.2-r1
>
> All seems to work fine here.
> --
> Regards,
> Mick
>

baselayout-2.0.2 seems like the obvious choice.

openrc-0.8.2-r1 I'm not so sure about.

It would be nice if the news message actually said these things
instead of leaving us guessing...

Thanks Mick. I'm going to do this first in a Gentoo VM. If it dies I
can easily go back to a backup and start over. It's not possible for
me to recover from a mistake on a remote machine as there's no way to
boot from a CD.

Order of work:
1) Gentoo VM
2) 4 local Gentoo boxes
3) 2 remote Gentoo boxes

Cheers,
Mark

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[William Hubbs]

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

On Mon, May 02, 2011 at 06:36:58PM +0100, Mick wrote:
> I've unmasked the latest available after reading the changelogs:
> 
>  sys-apps/baselayout-2.0.2
> 
>  sys-apps/openrc-0.8.2-r1

http://bugs.gentoo.org/show_bug.cgi?id=295613

You are correct about the versions.

William

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

On Mon, 2 May 2011 10:11:01 -0700, Mark Knecht wrote:

> How will you / did you decide what versions to unmask?

Does stable portage support the --autounmask option to emerge?


-- 
Neil Bothwick

"Do not handicap your children by making their lives easy."
 -- Robert Heinlein

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mark Knecht]

On Mon, May 2, 2011 at 11:02 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 2 May 2011 10:11:01 -0700, Mark Knecht wrote:
>
>> How will you / did you decide what versions to unmask?
>
> Does stable portage support the --autounmask option to emerge?
>

I use ~amd64 portage so I have supports that feature but what command
do I run today to unmask the version level they will make stable next
week? (For instance 0.7 instead of 0.8) I don't think that feature
looks into the future like that.

- Mark

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 544 bytes --]

On Mon, 2 May 2011 11:16:36 -0700, Mark Knecht wrote:

> > Does stable portage support the --autounmask option to emerge?

> I use ~amd64 portage so I have supports that feature but what command
> do I run today to unmask the version level they will make stable next
> week? (For instance 0.7 instead of 0.8) I don't think that feature
> looks into the future like that.

The latest version of baselayout is over six weeks old, so I'd go for
that.


-- 
Neil Bothwick

Celery is not food. It is a member of the plywood family.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mark Knecht]

On Mon, May 2, 2011 at 11:48 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 2 May 2011 11:16:36 -0700, Mark Knecht wrote:
>
>> > Does stable portage support the --autounmask option to emerge?
>
>> I use ~amd64 portage so I have supports that feature but what command
>> do I run today to unmask the version level they will make stable next
>> week? (For instance 0.7 instead of 0.8) I don't think that feature
>> looks into the future like that.
>
> The latest version of baselayout is over six weeks old, so I'd go for
> that.
>
>
> --
> Neil Bothwick

Life's a crap shoot. (As are all my index futures trades today.) Sounds good.

Cheers,
Mark

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mark Knecht]

On Mon, May 2, 2011 at 11:54 AM, Mark Knecht <markknecht@gmail.com> wrote:
> On Mon, May 2, 2011 at 11:48 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
>> On Mon, 2 May 2011 11:16:36 -0700, Mark Knecht wrote:
>>
>>> > Does stable portage support the --autounmask option to emerge?
>>
>>> I use ~amd64 portage so I have supports that feature but what command
>>> do I run today to unmask the version level they will make stable next
>>> week? (For instance 0.7 instead of 0.8) I don't think that feature
>>> looks into the future like that.
>>
>> The latest version of baselayout is over six weeks old, so I'd go for
>> that.
>>
>>
>> --
>> Neil Bothwick
>
> Life's a crap shoot. (As are all my index futures trades today.) Sounds good.
>
> Cheers,
> Mark
>

OK, I'm writing this from an updated Gentoo VM running in Virtualbox
on my (as yet) not updated Gentoo server. Things went well. The only
semi-issue that came up for me so far was the rc-sys="" variable not
being set. The way upgrade doc is written I had the impression that
this only mattered if I was in a machine that ran VMs on it and not to
be done in the VM itself. Seems that you really want rc_sys to be set
for any Gentoo install I guess.

Not sure at this point how I'd tell if there was some other problem,
but as far as a simple VM goes it only took about 15 minutes to
complete the upgrade and it booted first time.

Cheers,
Mark

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2401 bytes --]

On Monday 02 May 2011 23:07:00 Mark Knecht wrote:
> On Mon, May 2, 2011 at 11:54 AM, Mark Knecht <markknecht@gmail.com> wrote:
> > On Mon, May 2, 2011 at 11:48 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> >> On Mon, 2 May 2011 11:16:36 -0700, Mark Knecht wrote:
> >>> > Does stable portage support the --autounmask option to emerge?
> >>> 
> >>> I use ~amd64 portage so I have supports that feature but what command
> >>> do I run today to unmask the version level they will make stable next
> >>> week? (For instance 0.7 instead of 0.8) I don't think that feature
> >>> looks into the future like that.
> >> 
> >> The latest version of baselayout is over six weeks old, so I'd go for
> >> that.
> >> 
> >> 
> >> --
> >> Neil Bothwick
> > 
> > Life's a crap shoot. (As are all my index futures trades today.) Sounds
> > good.
> > 
> > Cheers,
> > Mark
> 
> OK, I'm writing this from an updated Gentoo VM running in Virtualbox
> on my (as yet) not updated Gentoo server. Things went well. The only
> semi-issue that came up for me so far was the rc-sys="" variable not
> being set. The way upgrade doc is written I had the impression that
> this only mattered if I was in a machine that ran VMs on it and not to
> be done in the VM itself. Seems that you really want rc_sys to be set
> for any Gentoo install I guess.

Ah! I forgot to mention this - it showed up on mine too.  You need to read 
this /etc/rc.conf section:
====================================================
# This is the subsystem type. Valid options on Linux:
# ""        - nothing special
# "lxc"     - Linux Containers
# "openvz"  - Linux OpenVZ
# "prefix"  - Prefix
# "uml"     - Usermode Linux
# "vserver" - Linux vserver
# "xen0"    - Xen0 Domain
# "xenU"    - XenU Domain
# If this is commented out, automatic detection will be attempted.
# Note that autodetection will not work in a prefix environment or in a
# linux container.
#
# This should be set to the value representing the environment this file is
# PRESENTLY in, not the virtualization the environment is capable of.
#rc_sys=""
rc_sys=""
====================================================

I've used the "nothing special" option, but yours might need to be something 
different on the VMhost.  The guest would be "nothing special" I would think.  
(Not sure what the "prefix" is ...
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Felix Leif Keppmann]

Hey Mark,

the news item does not tell the exact version because there might be sub/rc-
versions until release. so on release date the devs will remove keywords of 
the right versions. i read the dev mailing list a bit and it should be

baselayout-2.0.2 + openrc-0.8.2-r1

if no further -rc will be introduced till release. already installed it 
yesterday, followed the migration guide and it works fine for me.

or just wait until it is offical released and use those versions.


Cheers
Felix Leif



On Monday 02 May 2011 10:11:01 Mark Knecht wrote:
> On Mon, May 2, 2011 at 2:31 AM, Mick <michaelkintzios@gmail.com> wrote:
> > On Monday 02 May 2011 10:11:06 Thanasis wrote:
> >> Let me add that my system defaults to the _stable_ software branch.
> > 
> > Thanks for the heads up.  :)
> > 
> > It seems then that Baselayout2/OpenRC is being rolled out to stable.
> >  I'll be unmasking and updating a couple of boxen today, taking
> > advantage of some spare time and finishing the rest off next weekend.
> > 
> > Hope all goes well.
> > --
> > Regards,
> > Mick
> 
> How will you / did you decide what versions to unmask? The news
> message seems quite vague and I see lots of versions of things. Two
> 2.X versions of baselayout and four versions of OpenRC.
> 
> I'd potentially start updating a stable machine today but I'd prefer
> to only unmask what is actually going to become the stable version and
> nothing higher.
> 
> - Mark

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Dale]

Thanasis wrote:
> Let me add that my system defaults to the _stable_ software branch.
>
>
>    

They are giving a heads up that the update is coming.  I think it is 
going stable in a few days, about a week since the package was added to 
stable.

I'm just hoping this will be a clean upgrade.  They been working on it 
long enough.  o_O  I'm hoping for better than my hal upgrade for sure.  lol

Dale

:-)  :-)

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2029 bytes --]

On Monday 02 May 2011 10:03:11 Thanasis wrote:
> I am running default/linux/amd64/10.0/no-multilib profile, and I got the
> following news item, after syncing this morning:
> 
> # eselect news read
> 
> 2011-05-01-baselayout-update
>   Title                     Baselayout update
>   Author                    Christian Faulhammer <fauli@gentoo.org>
>   Author                    William Hubbs <williamh@gentoo.org>
>   Posted                    2011-05-01
>   Revision                  1
> 
> The baselayout package provides files which all systems must have in
> order to function properly. You are currently using version 1.x, which
> has several issues. The most significant of these is that the included
> init scripts are written entirely in bash, which makes them slow and
> not very flexible.
> 
> On 2011/05/08, you will see an update for sys-apps/baselayout to
> 2.x and a new package, sys-apps/openrc. It is recommended that you
> perform this update as soon as possible.
> 
> Please note, after these packages are emerged, it is
> __Absolutely_Critical__ that you immediately update your configuration
> files with dispatch-conf, etc-update or a similar tool then follow the
> steps in the migration guide located at the following URL.
> http://www.gentoo.org/doc/en/openrc-migration.xml
> 
> FAILURE TO FOLLOW ALL OF THESE STEPS WILL RESULT IN AN UNBOOTABLE
> SYSTEM! IF THIS SHOULD HAPPEN, YOU WILL NEED TO BOOT FROM A LIVE CD OR
> DVD, MOUNT YOUR ROOT FILE SYSTEM, CHROOT INTO THAT ENVIRONMENT AND
> FOLLOW THE ABOVE STEPS!

I've been through the migration guide.  In the section about udev it mentions 
/etc/runlevels/sysinit.  Is this something added by baselayout2/OpenRC?  I 
don't seem to have this in my runlevels:

$ ls -l /etc/runlevels/
total 16
drwxr-xr-x 2 root root 4096 Jan 18 20:39 boot
drwxr-xr-x 2 root root 4096 Jun  8  2010 default
drwxr-xr-x 2 root root 4096 Jan 21  2010 nonetwork
drwxr-xr-x 2 root root 4096 Jan 21  2010 single
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2953 bytes --]

On Monday 02 May 2011 10:43:59 Mick wrote:
> On Monday 02 May 2011 10:03:11 Thanasis wrote:
> > I am running default/linux/amd64/10.0/no-multilib profile, and I got the
> > following news item, after syncing this morning:
> > 
> > # eselect news read
> > 
> > 2011-05-01-baselayout-update
> > 
> >   Title                     Baselayout update
> >   Author                    Christian Faulhammer <fauli@gentoo.org>
> >   Author                    William Hubbs <williamh@gentoo.org>
> >   Posted                    2011-05-01
> >   Revision                  1
> > 
> > The baselayout package provides files which all systems must have in
> > order to function properly. You are currently using version 1.x, which
> > has several issues. The most significant of these is that the included
> > init scripts are written entirely in bash, which makes them slow and
> > not very flexible.
> > 
> > On 2011/05/08, you will see an update for sys-apps/baselayout to
> > 2.x and a new package, sys-apps/openrc. It is recommended that you
> > perform this update as soon as possible.
> > 
> > Please note, after these packages are emerged, it is
> > __Absolutely_Critical__ that you immediately update your configuration
> > files with dispatch-conf, etc-update or a similar tool then follow the
> > steps in the migration guide located at the following URL.
> > http://www.gentoo.org/doc/en/openrc-migration.xml
> > 
> > FAILURE TO FOLLOW ALL OF THESE STEPS WILL RESULT IN AN UNBOOTABLE
> > SYSTEM! IF THIS SHOULD HAPPEN, YOU WILL NEED TO BOOT FROM A LIVE CD OR
> > DVD, MOUNT YOUR ROOT FILE SYSTEM, CHROOT INTO THAT ENVIRONMENT AND
> > FOLLOW THE ABOVE STEPS!
> 
> I've been through the migration guide.  In the section about udev it
> mentions /etc/runlevels/sysinit.  Is this something added by
> baselayout2/OpenRC?  I don't seem to have this in my runlevels:
> 
> $ ls -l /etc/runlevels/
> total 16
> drwxr-xr-x 2 root root 4096 Jan 18 20:39 boot
> drwxr-xr-x 2 root root 4096 Jun  8  2010 default
> drwxr-xr-x 2 root root 4096 Jan 21  2010 nonetwork
> drwxr-xr-x 2 root root 4096 Jan 21  2010 single

Another thing I found, is some incongruity about the file in which the $EDITOR 
and $PAGER should be defined.

The migration guide says:

"The EDITOR variable is no longer found in /etc/rc.conf. Both EDITOR and PAGER 
are set by default in /etc/profile. You should change this as needed in your 
~/.bashrc (or equivalent) file or create */etc/env.d/99editor* and set the 
system default there."

On the other hand the /etc/profile file seems to recommend /etc/profile.d/

"# You should override these in your ~/.bashrc (or equivalent) for per-user
# settings.  For system defaults, you can add a new file in /etc/profile.d/.
export EDITOR=${EDITOR:-/bin/nano}
export PAGER=${PAGER:-/usr/bin/less}"

Which one is the authoritative place to define a system wide editor?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Thanasis]

on 05/02/2011 01:05 PM Mick wrote the following:
> Another thing I found, is some incongruity about the file in which the $EDITOR 
> and $PAGER should be defined.
>
> The migration guide says:
>
> "The EDITOR variable is no longer found in /etc/rc.conf. Both EDITOR and PAGER 
> are set by default in /etc/profile. You should change this as needed in your 
> ~/.bashrc (or equivalent) file or create */etc/env.d/99editor* and set the 
> system default there."
>
> On the other hand the /etc/profile file seems to recommend /etc/profile.d/
>
> "# You should override these in your ~/.bashrc (or equivalent) for per-user
> # settings.  For system defaults, you can add a new file in /etc/profile.d/.
> export EDITOR=${EDITOR:-/bin/nano}
> export PAGER=${PAGER:-/usr/bin/less}"
>
> Which one is the authoritative place to define a system wide editor?
All above are consistent. The system default is set in a file like
/etc/env.d/99editor
I use eselect (app-admin/eselect) to set the system defaults.
eg I have:
# cat /etc/env.d/99editor
# Configuration file for eselect
# This file has been automatically generated.
EDITOR="/usr/bin/vi"
VISUAL="/usr/bin/vi"

But on a per user basis, a user should define those environment
variables in his ~/.bashrc or ~/.bash_profile (or equivalent) shell
initialization files.

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1662 bytes --]

On Monday 02 May 2011 11:26:27 you wrote:
> on 05/02/2011 01:05 PM Mick wrote the following:
> > Another thing I found, is some incongruity about the file in which the
> > $EDITOR and $PAGER should be defined.
> > 
> > The migration guide says:
> > 
> > "The EDITOR variable is no longer found in /etc/rc.conf. Both EDITOR and
> > PAGER are set by default in /etc/profile. You should change this as
> > needed in your ~/.bashrc (or equivalent) file or create
> > */etc/env.d/99editor* and set the system default there."
> > 
> > On the other hand the /etc/profile file seems to recommend
> > /etc/profile.d/
> > 
> > "# You should override these in your ~/.bashrc (or equivalent) for
> > per-user # settings.  For system defaults, you can add a new file in
> > /etc/profile.d/. export EDITOR=${EDITOR:-/bin/nano}
> > export PAGER=${PAGER:-/usr/bin/less}"
> > 
> > Which one is the authoritative place to define a system wide editor?
> 
> All above are consistent. The system default is set in a file like
> /etc/env.d/99editor
> I use eselect (app-admin/eselect) to set the system defaults.
> eg I have:
> # cat /etc/env.d/99editor
> # Configuration file for eselect
> # This file has been automatically generated.
> EDITOR="/usr/bin/vi"
> VISUAL="/usr/bin/vi"
> 
> But on a per user basis, a user should define those environment
> variables in his ~/.bashrc or ~/.bash_profile (or equivalent) shell
> initialization files.

Thanks.  Not sure if there is a difference between an env.d variable and a 
profile.d variable.  I've added mine to /etc/profile.d for now.  I'll see what 
gives when I reboot.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Thanasis]

on 05/02/2011 01:50 PM Mick wrote the following:
<snip>
> Not sure if there is a difference between an env.d variable and a
> profile.d variable. 
Me neither, but I think you should add it to env.d
In my system only a couple of packages (namely dev-java/java-config and
sys-fs/udisks) use profile.d
All other packages use /etc/env.d and so does sys-apps/baselayout.

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Alex Schuster]

Mick writes:

> On Monday 02 May 2011 11:26:27 you wrote:

> Thanks.  Not sure if there is a difference between an env.d variable and
> a profile.d variable.

None you will notice, both /etc/profile.env and scripts in /etc/profile.d/ 
are sourced in /etc/profile. profile.env contains all stuff in /etc/env.d/ 
after you ran env-update.
I do not manually change things in env.d, but with 'eselect editor set <n>' 
you can create a file /etc/env.d/99editor which will set the EDITOR variable 
to the editor you gave eselect as argument. Enter eselect editor list to se 
what's available, or just give the editor path as argument to eselect.

> I've added mine to /etc/profile.d for now.  I'll
> see what gives when I reboot.

A relogin would be enough. Or '. /etc/profile' in the shell, this is what 
eselects suggests to do. Or bash -l, or xterm -ls.

	Wonko

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1831 bytes --]

On Monday 02 May 2011 12:52:12 Alex Schuster wrote:
> Mick writes:
> > On Monday 02 May 2011 11:26:27 you wrote:
> > 
> > Thanks.  Not sure if there is a difference between an env.d variable and
> > a profile.d variable.
> 
> None you will notice, both /etc/profile.env and scripts in /etc/profile.d/
> are sourced in /etc/profile. profile.env contains all stuff in /etc/env.d/
> after you ran env-update.

Hmm ... I initially set up a file in /etc/profile.d/99editor with 

EDITOR="/usr/bin/vim" 

in it.  Upon reboot I still got:

echo $EDITOR
/bin/nano

So, I thought of moving it into /etc/env.d/97editor.  Upon another reboot 
(troubleshooting network problems) I again found out that nano is my default 
editor ... neither locations seem to being read at boot time?

Running env-update && source /etc/profile did not make any difference.

Is the number prefix important?  Does it have to be 99editor?  If so, how does 
one discover the correct number for each variable?


> I do not manually change things in env.d, but with 'eselect editor set <n>'
> you can create a file /etc/env.d/99editor which will set the EDITOR
> variable to the editor you gave eselect as argument. Enter eselect editor
> list to se what's available, or just give the editor path as argument to
> eselect.

# eselect editor list
Available targets for the EDITOR variable:
  [1]   /bin/nano
  [2]   /usr/bin/ex
  [3]   /usr/bin/vi
  [ ]   (free form)

What does the "[ ]   (free form)" above refer to?


> > I've added mine to /etc/profile.d for now.  I'll
> > see what gives when I reboot.
> 
> A relogin would be enough. Or '. /etc/profile' in the shell, this is what
> eselects suggests to do. Or bash -l, or xterm -ls.

Yep, setting the EDITOR using eselect works fine.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Alex Schuster]

Mick wrote:

> On Monday 02 May 2011 12:52:12 Alex Schuster wrote:
> > Mick writes:

> > > Thanks.  Not sure if there is a difference between an env.d variable
> > > and a profile.d variable.
> > 
> > None you will notice, both /etc/profile.env and scripts in
> > /etc/profile.d/ are sourced in /etc/profile. profile.env contains all
> > stuff in /etc/env.d/ after you ran env-update.
> 
> Hmm ... I initially set up a file in /etc/profile.d/99editor with
> 
> EDITOR="/usr/bin/vim"
> 
> in it.  Upon reboot I still got:
> 
> echo $EDITOR
> /bin/nano

I looked into /etc/profile, and right at the bottom it does this:

for sh in /etc/profile.d/*.sh ; do
        [ -r "$sh" ] && . "$sh"
done
unset sh

So the file needs to have the .sh suffix.

> So, I thought of moving it into /etc/env.d/97editor.  Upon another reboot
> (troubleshooting network problems) I again found out that nano is my
> default editor ... neither locations seem to being read at boot time?
> 
> Running env-update && source /etc/profile did not make any difference.
> 
> Is the number prefix important?  Does it have to be 99editor?  If so, how
> does one discover the correct number for each variable?

Maybe the 99 is what eselect wants the number to be. If you manage files in 
there yourself, I think it should not matter. The result of env-update in 
/etc/profile.env is sorted alphabetically, so the order of file in 
/etc/env.d should not matter, I think.


> > I do not manually change things in env.d, but with 'eselect editor set
> > <n>' you can create a file /etc/env.d/99editor which will set the
> > EDITOR variable to the editor you gave eselect as argument. Enter
> > eselect editor list to se what's available, or just give the editor
> > path as argument to eselect.
> 
> # eselect editor list
> Available targets for the EDITOR variable:
>   [1]   /bin/nano
>   [2]   /usr/bin/ex
>   [3]   /usr/bin/vi
>   [ ]   (free form)
> 
> What does the "[ ]   (free form)" above refer to?

That you can specify any other binary as editor if you like, with "eselect 
editor set /path/to/my/editor".

> > > I've added mine to /etc/profile.d for now.  I'll
> > > see what gives when I reboot.
> > 
> > A relogin would be enough. Or '. /etc/profile' in the shell, this is
> > what eselects suggests to do. Or bash -l, or xterm -ls.
> 
> Yep, setting the EDITOR using eselect works fine.

Hooray!

	Wonko

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Alan McKinnon]

Apparently, though unproven, at 10:25 on Thursday 05 May 2011, Alex Schuster 
did opine thusly:

> > Is the number prefix important?  Does it have to be 99editor?  If so, how
> > does one discover the correct number for each variable?
> 
> Maybe the 99 is what eselect wants the number to be. If you manage files
> in  there yourself, I think it should not matter. The result of env-update
> in /etc/profile.env is sorted alphabetically, so the order of file in
> /etc/env.d should not matter, I think.

The number is only important inasmuch as it sets the order the files will be 
read. Normally, this is not an issue but you can use it to override an earlier 
setting by putting the correct one in a file starting with a higher number.

If EDITOR is being reset and you can't find it, it's probably being done in 
~/.bashrc or ~/.bash_profile 

"grep ~" and "grep /etc" are your friends

 
-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2816 bytes --]

On Thursday 05 May 2011 09:25:18 Alex Schuster wrote:
> Mick wrote:
> > On Monday 02 May 2011 12:52:12 Alex Schuster wrote:
> > > Mick writes:
> > > > Thanks.  Not sure if there is a difference between an env.d variable
> > > > and a profile.d variable.
> > > 
> > > None you will notice, both /etc/profile.env and scripts in
> > > /etc/profile.d/ are sourced in /etc/profile. profile.env contains all
> > > stuff in /etc/env.d/ after you ran env-update.
> > 
> > Hmm ... I initially set up a file in /etc/profile.d/99editor with
> > 
> > EDITOR="/usr/bin/vim"
> > 
> > in it.  Upon reboot I still got:
> > 
> > echo $EDITOR
> > /bin/nano
> 
> I looked into /etc/profile, and right at the bottom it does this:
> 
> for sh in /etc/profile.d/*.sh ; do
>         [ -r "$sh" ] && . "$sh"
> done
> unset sh
> 
> So the file needs to have the .sh suffix.

I see!  It makes sense now.


> > So, I thought of moving it into /etc/env.d/97editor.  Upon another reboot
> > (troubleshooting network problems) I again found out that nano is my
> > default editor ... neither locations seem to being read at boot time?
> > 
> > Running env-update && source /etc/profile did not make any difference.
> > 
> > Is the number prefix important?  Does it have to be 99editor?  If so, how
> > does one discover the correct number for each variable?
> 
> Maybe the 99 is what eselect wants the number to be. If you manage files in
> there yourself, I think it should not matter. The result of env-update in
> /etc/profile.env is sorted alphabetically, so the order of file in
> /etc/env.d should not matter, I think.
> 
> > > I do not manually change things in env.d, but with 'eselect editor set
> > > <n>' you can create a file /etc/env.d/99editor which will set the
> > > EDITOR variable to the editor you gave eselect as argument. Enter
> > > eselect editor list to se what's available, or just give the editor
> > > path as argument to eselect.
> > 
> > # eselect editor list
> > 
> > Available targets for the EDITOR variable:
> >   [1]   /bin/nano
> >   [2]   /usr/bin/ex
> >   [3]   /usr/bin/vi
> >   [ ]   (free form)
> > 
> > What does the "[ ]   (free form)" above refer to?
> 
> That you can specify any other binary as editor if you like, with "eselect
> editor set /path/to/my/editor".
> 
> > > > I've added mine to /etc/profile.d for now.  I'll
> > > > see what gives when I reboot.
> > > 
> > > A relogin would be enough. Or '. /etc/profile' in the shell, this is
> > > what eselects suggests to do. Or bash -l, or xterm -ls.

Yes, but I was also testing some other issues with my network setup and also 
startup scripts.

> > Yep, setting the EDITOR using eselect works fine.
> 
> Hooray!

 :)  Thanks for your advice!

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] heads-up: 2011-05-01 baselayout news

[Thanasis]

on 05/02/2011 12:43 PM Mick wrote the following:
> <snip>
>> http://www.gentoo.org/doc/en/openrc-migration.xml
>
> I've been through the migration guide.  In the section about udev it mentions 
> /etc/runlevels/sysinit.  Is this something added by baselayout2/OpenRC?  I 
> don't seem to have this in my runlevels:
>
> $ ls -l /etc/runlevels/
> total 16
> drwxr-xr-x 2 root root 4096 Jan 18 20:39 boot
> drwxr-xr-x 2 root root 4096 Jun  8  2010 default
> drwxr-xr-x 2 root root 4096 Jan 21  2010 nonetwork
> drwxr-xr-x 2 root root 4096 Jan 21  2010 single
Looks like the update process will create the directory
/etc/runlevels/sysinit and (it should) put inside links to devfs, dmesg,
udev like so:
(# ls -l /etc/runlevels/sysinit)
lrwxrwxrwx 1 root root   17 Sep 23  2009 devfs -> /etc/init.d/devfs
lrwxrwxrwx 1 root root   17 Sep 23  2009 dmesg -> /etc/init.d/dmesg
lrwxrwxrwx 1 root root   16 Sep 23  2009 udev -> /etc/init.d/udev

[gentoo-user] Re: heads-up: 2011-05-01 baselayout news

[walt]

On 05/02/2011 02:43 AM, Mick wrote:

> I've been through the migration guide.  In the section about udev it mentions
> /etc/runlevels/sysinit.  Is this something added by baselayout2/OpenRC?  I
> don't seem to have this in my runlevels:
>
> $ ls -l /etc/runlevels/
> total 16
> drwxr-xr-x 2 root root 4096 Jan 18 20:39 boot
> drwxr-xr-x 2 root root 4096 Jun  8  2010 default
> drwxr-xr-x 2 root root 4096 Jan 21  2010 nonetwork
> drwxr-xr-x 2 root root 4096 Jan 21  2010 single

The confusion with all of this booting stuff goes back to the very dawn
of unix, long before linux appeared.  I learned at the knee of someone who
actually remembers the dawn -- but of course I'm much too young myself :p

The conflict between "environment" and "profile", the origins of ".profile"
and ".bashrc" go back IIRC to the competition between sh, csh, and bash for
dominance -- not to mention ksh, tsh, foosh, and barsh, bahsh etc, etc.

Each shell had its own private configuration file(s), which needed distinct
names, of course, to avoid chaos.  Chaos prevailed, predictably, because of
these conflicting standards, and you/we are still dealing with the problem
today.  (No, I am NOT complaining, I'd be bragging except I had nothing to do
with any of it.  But I did have the honor of meeting many very smart people
who do have real bragging rights.)

Anyway, to answer your specific question,

#equery b sysinit
  * Searching for sysinit ...
sys-apps/openrc-0.8.2-r1 (/usr/share/openrc/runlevels/sysinit)

#equery b inittab
  * Searching for inittab ...
sys-apps/sysvinit-2.88-r1 (/etc/inittab)

Why did I search for inittab?  Here's a wee hint while I'm off to bed:

#grep sysinit /etc/inittab
si::sysinit:/sbin/rc sysinit