Hello.

The instructions in

http://gentoo-wiki.com/HOWTO_Wireles...on_and_Startup

say I would need to install baselayout-1.11.10

(I am currently using sys-apps/baselayout-1.9.4-r6).

and that before 'emerge' will let me do that,
I would have to change my '/etc/portage/package.keywords' file

from:
--------------------------
media-libs/svgalib ~x86
--------------------------

to:
---------------------------
media-libs/svgalib ~x86
sys-apps/baselayout ~x86
sys-libs/readline ~x86
sys-apps/sysvinit ~x86
app-shells/bash ~x86
------------------------

And indeed, if I do a pretend emerge with this new
'/etc/portage/package.keywords' file in place,
I get

..$ emerge -p -u baselayout

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild U ] app-shells/bash-3.0-r8 [2.05b-r9]
[ebuild U ] sys-libs/readline-5.0-r2 [4.3-r5]
[ebuild N ] sys-apps/sysvinit-2.86
[ebuild U ] sys-apps/baselayout-1.11.10-r2 [1.9.4-r6]

However, AFAIK, my sysem is already up to date,
so I ask myself, if it would be a good idea for me to
do this, why didn't the last

emerge -u world

I ran do it already?

Given that it did not, is it safe for me to jump ahead and do it anyway?

(worrier)

student wrote:
> Hello.
>
> The instructions in
>
> http://gentoo-wiki.com/HOWTO_Wireles...on_and_Startup
>
> say I would need to install baselayout-1.11.10
>
> (I am currently using sys-apps/baselayout-1.9.4-r6).
>
>
> However, AFAIK, my sysem is already up to date,
> so I ask myself, if it would be a good idea for me to
> do this, why didn't the last
>
> emerge -u world
>
> I ran do it already?
>
> Given that it did not, is it safe for me to jump ahead and do it anyway?
>
> (worrier)

If you install packages marked ~x86 (test), there is a slight risk for that
the packages will have problems. But if you can't install the package you need
to get your WLAN to work, then you don't have much of an option.


//Aho

student wrote:
> Hello.
>
> The instructions in
>
> http://gentoo-wiki.com/HOWTO_Wireles...on_and_Startup
>
> say I would need to install baselayout-1.11.10
>
> (I am currently using sys-apps/baselayout-1.9.4-r6).
>
> and that before 'emerge' will let me do that,
> I would have to change my '/etc/portage/package.keywords' file
>
> from:
> --------------------------
> media-libs/svgalib ~x86
> --------------------------
>
> to:
> ---------------------------
> media-libs/svgalib ~x86
> sys-apps/baselayout ~x86
> sys-libs/readline ~x86
> sys-apps/sysvinit ~x86
> app-shells/bash ~x86
> ------------------------
>
> And indeed, if I do a pretend emerge with this new
> '/etc/portage/package.keywords' file in place,
> I get
>
> .$ emerge -p -u baselayout
>
> These are the packages that I would merge, in order:
>
> Calculating dependencies ...done!
> [ebuild U ] app-shells/bash-3.0-r8 [2.05b-r9]
> [ebuild U ] sys-libs/readline-5.0-r2 [4.3-r5]
> [ebuild N ] sys-apps/sysvinit-2.86
> [ebuild U ] sys-apps/baselayout-1.11.10-r2 [1.9.4-r6]
>
> However, AFAIK, my sysem is already up to date,
> so I ask myself, if it would be a good idea for me to
> do this, why didn't the last
>
> emerge -u world
>
> I ran do it already?
>
> Given that it did not, is it safe for me to jump ahead and do it anyway?
>
> (worrier)
Do you really need wireless? If yes, then upgrade, if no, then don't.
I've done this exact upgrade before and it was fine. I too was a bit
scared at the number of ~x86s I had to add, but these days I have
ACCEPT_KEYWORDS="~x86" in my make.conf and couldn't be happier.

Ben O'Brien wrote:
>
> Do you really need wireless? If yes, then upgrade, if no, then don't.
> I've done this exact upgrade before and it was fine. I too was a bit
> scared at the number of ~x86s I had to add, but these days I have
> ACCEPT_KEYWORDS="~x86" in my make.conf and couldn't be happier.

I have in fact been using some inexpensive Atmel-based USB
wireless adapters for several months. However, the excellent driver
that I am using (berlios) has not yet worked its way into the standard
Linux distro, so to bring the network up, I have to run visit each node and
run a simple-minded startup script that I made up, whereas I would of course
prefer to have wlan0 come up automatically as each node boots up.

(I am running Gentoo on the host but the nodes are running canned
Slackware.)

I guess what I don't like about the upgrade
that was suggested to me is that if I use

/etc/portage/package.mask
--------------------------
media-libs/svgalib ~x86
sys-apps/baselayout ~x86
sys-libs/readline ~x86
sys-apps/sysvinit ~x86
app-shells/bash ~x86
------------------------

then sysvinit gets dragged back into the picture,
and the fact that it seemed to me to have done away with sysvinit
was one of the things I liked most about Gentoo.

What's that about?

student wrote:
> Ben O'Brien wrote:
>
>>
>> Do you really need wireless? If yes, then upgrade, if no, then don't.
>> I've done this exact upgrade before and it was fine. I too was a bit
>> scared at the number of ~x86s I had to add, but these days I have
>> ACCEPT_KEYWORDS="~x86" in my make.conf and couldn't be happier.
>
>
> I have in fact been using some inexpensive Atmel-based USB
> wireless adapters for several months. However, the excellent driver
> that I am using (berlios) has not yet worked its way into the standard
> Linux distro, so to bring the network up, I have to run visit each node and
> run a simple-minded startup script that I made up, whereas I would of
> course
> prefer to have wlan0 come up automatically as each node boots up.

Edit your /etc/conf.d/local-start to run the startup script.
Another way would be to make your own init script and add that to your default
runlevel.

> (I am running Gentoo on the host but the nodes are running canned
> Slackware.)

Slacware may have different name for it's local-stat file and would most
likely be found in /etc/rc.d.


//Aho

J.O. Aho wrote:
> student wrote:
>
>> Ben O'Brien wrote:
>>
>>>
>>> Do you really need wireless? If yes, then upgrade, if no, then don't.
>>> I've done this exact upgrade before and it was fine. I too was a bit
>>> scared at the number of ~x86s I had to add, but these days I have
>>> ACCEPT_KEYWORDS="~x86" in my make.conf and couldn't be happier.
>>
>>
>>
>> I have in fact been using some inexpensive Atmel-based USB
>> wireless adapters for several months. However, the excellent driver
>> that I am using (berlios) has not yet worked its way into the standard
>> Linux distro, so to bring the network up, I have to run visit each
>> node and
>> run a simple-minded startup script that I made up, whereas I would of
>> course
>> prefer to have wlan0 come up automatically as each node boots up.
>
>
> Edit your /etc/conf.d/local-start to run the startup script.

Wow, that wasn't near as hard as I thought it wold be, thanks!

> Another way would be to make your own init script and add that to your
> default runlevel.
>
>> (I am running Gentoo on the host but the nodes are running canned
>> Slackware.)
>
>
> Slacware may have different name for it's local-stat file and would most
> likely be found in /etc/rc.d.
>
>
> //Aho

Ok, will try it.

Thanks again!