after many moons and a long time I am back

as a joke I instaled slack 7.1 last week on a p100 with 64Mb ram console
only it's running apache and ftp well thats about it, Mandrake 9.2 was
pissing me off so I took some time to own load some ISO's mounted them
on my e-smith boxen (mail bagging and mp3 streameer) and boot the cd and
off I go 2hrs later slack is up and running Xwindow and sorta configured.

The last time I ran Slackware was with a 2.2.19 Kernal on a P233 machine
since then I have mucked arround with REDHAT, Mandrake & DamnSmall and
seriously using E-Smith and IPCOP. Talk about being at home no nasty
supprises REDHAT, Mandrake & DamnSmall and no mollycolliding or Pain
REDHAT.

Now My hard ware has changed a lot since 2.2.19 All of the ISA stuff has
gone into oter boxen (Sound blaster AWE ect ect ect) and now I am using
ps2 not serial and at conectors for mouse and keybrd,

Ok the last thing I did was to copy my old mandrake /etc for the just in
cace serernero but I dont realy want to use it as I wont lurn what I
want to lurn

my Problems are gpm failes (my fault I mis configuered it)

how do I use the setup program again ir is it run from cdrom?

Sound seems to be a problem I have the approperate module loaded but not
used (cmpci) I used to rember there was a permissions thing in previous
versions but even as root there are problems

ALSA mixer_oss.c:1261: unable to register OSS mixer device 0:0
ALSA pcm_oss.c:2419: unable to register OSS PCM device 0:0


USB works and network time proticals are just some reading

so places to look for information wwould be helpful, and comments about
hardening?

Robert Cooze

AKA

RecyclerMan

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Robert Cooze dared to utter,
> as a joke I instaled slack 7.1 last week on a p100 with 64Mb ram console
>
> how do I use the setup program again ir is it run from cdrom?

# setup

Later versions of Slackware no longer include setup per say. You must
run pkgtool and select it from the menu (note that requires ncurses to
be installed), but the setup shell script was still in $PATH way back
in 7.1.

> Sound seems to be a problem I have the approperate module loaded but not
> used (cmpci) I used to rember there was a permissions thing in previous
> versions but even as root there are problems
>
> ALSA mixer_oss.c:1261: unable to register OSS mixer device 0:0
> ALSA pcm_oss.c:2419: unable to register OSS PCM device 0:0

It's been a long time since I ran 7.1, but IIRC it didn't include ALSA.
Have you downloaded and compiled ALSA, or are you using OSS drivers?
This should really be as easy as modprobing the right module, and
running some utility to change the volume (I'm not sure if 7.1 comes
with rexima, but that's my volume controller of choice). You may need
to give your users read/write access to /dev/dsp, /dev/mixer, and
/dev/audio as well, but that's not necessary for root.

> so places to look for information wwould be helpful, and comments about
> hardening?

Going that far back, I recommend the original Good Book.
http://www.slackware.com/book

As for hardening, your best bet is to run a more up-to-date
distribution. If you don't need X or anything fancy like that, just
console access and a few non-intensive services, I'd recommend 10.0 for
completeness, with GUS-Br or SlackSec patches. You can google around to
find those. Good luck to you, and come back here if you get stuck.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB8wjhlKR45I6cfKARAh+3AJ9Ll/6d3oUIh9kJxLNgmLJbH4hR0QCeL8gr
YcWS3LmmyA/BGHl3nCmXfUY=
=UC0e
-----END PGP SIGNATURE-----

+Alan Hicks+ wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Robert Cooze dared to utter,
>
>>as a joke I instaled slack 7.1 last week on a p100 with 64Mb ram console
>>
>>how do I use the setup program again ir is it run from cdrom?
>
>
> # setup
>
> Later versions of Slackware no longer include setup per say. You must
> run pkgtool and select it from the menu (note that requires ncurses to
> be installed), but the setup shell script was still in $PATH way back
> in 7.1.
>

Ok now I know what I need to know there Its just a Time thing I only
get scraps of time to look at things now (wife and Kids)

>
>>Sound seems to be a problem I have the approperate module loaded but not
>>used (cmpci) I used to rember there was a permissions thing in previous
>>versions but even as root there are problems
>>
>>ALSA mixer_oss.c:1261: unable to register OSS mixer device 0:0
>>ALSA pcm_oss.c:2419: unable to register OSS PCM device 0:0
>
>
> It's been a long time since I ran 7.1, but IIRC it didn't include ALSA.
> Have you downloaded and compiled ALSA, or are you using OSS drivers?
> This should really be as easy as modprobing the right module, and
> running some utility to change the volume (I'm not sure if 7.1 comes
> with rexima, but that's my volume controller of choice). You may need
> to give your users read/write access to /dev/dsp, /dev/mixer, and
> /dev/audio as well, but that's not necessary for root.
>

ok it does not work in root I will have a look arround this week

always happy as pig in muck
working on a new system

Sorry for the confusion there are TWO machines

machine #1 called test running 7.1 (happy with what is doing)

Machine #2 this machine running Slack 10 no sound and config probs...

I will appoligise Now for spelling gramma now

>
>>so places to look for information wwould be helpful, and comments about
>>hardening?
>
>
> Going that far back, I recommend the original Good Book.
> http://www.slackware.com/book
>

Been reading that

> As for hardening, your best bet is to run a more up-to-date
> distribution. If you don't need X or anything fancy like that, just
> console access and a few non-intensive services, I'd recommend 10.0 for
> completeness, with GUS-Br or SlackSec patches. You can google around to
> find those. Good luck to you, and come back here if you get stuck.
>

I should be ok as everything is behind a farly hard firewall it is the
usal close unused ports stop un used/needed serves keep up to daate pach
and app wise I guess.

> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFB8wjhlKR45I6cfKARAh+3AJ9Ll/6d3oUIh9kJxLNgmLJbH4hR0QCeL8gr
> YcWS3LmmyA/BGHl3nCmXfUY=
> =UC0e
> -----END PGP SIGNATURE-----

Thankks A lot just a gental nuge in the correct direction.

Robert Cooze wrote:
> +Alan Hicks+ wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> In alt.os.linux.slackware, Robert Cooze dared to utter,
>>
>>> as a joke I instaled slack 7.1 last week on a p100 with 64Mb ram console
>>> how do I use the setup program again ir is it run from cdrom?
>>
>>
>>
>> # setup
>>
>> Later versions of Slackware no longer include setup per say. You must
>> run pkgtool and select it from the menu (note that requires ncurses to
>> be installed), but the setup shell script was still in $PATH way back
>> in 7.1.
>>
>
> Ok now I know what I need to know there Its just a Time thing I only
> get scraps of time to look at things now (wife and Kids)
>
>>
>>> Sound seems to be a problem I have the approperate module loaded but
>>> not used (cmpci) I used to rember there was a permissions thing in
>>> previous versions but even as root there are problems
>>>
>>> ALSA mixer_oss.c:1261: unable to register OSS mixer device 0:0
>>> ALSA pcm_oss.c:2419: unable to register OSS PCM device 0:0
>>
>>
>>
>> It's been a long time since I ran 7.1, but IIRC it didn't include ALSA.
>> Have you downloaded and compiled ALSA, or are you using OSS drivers?
>> This should really be as easy as modprobing the right module, and
>> running some utility to change the volume (I'm not sure if 7.1 comes
>> with rexima, but that's my volume controller of choice). You may need
>> to give your users read/write access to /dev/dsp, /dev/mixer, and
>> /dev/audio as well, but that's not necessary for root.
>>
>
> ok it does not work in root I will have a look arround this week
>
> always happy as pig in muck
> working on a new system
>
> Sorry for the confusion there are TWO machines
>
> machine #1 called test running 7.1 (happy with what is doing)
>
> Machine #2 this machine running Slack 10 no sound and config probs...
>
> I will appoligise Now for spelling gramma now
>
>>
>>> so places to look for information wwould be helpful, and comments
>>> about hardening?
>>
>>
>>
>> Going that far back, I recommend the original Good Book.
>> http://www.slackware.com/book
>>
>
> Been reading that
>
>> As for hardening, your best bet is to run a more up-to-date
>> distribution. If you don't need X or anything fancy like that, just
>> console access and a few non-intensive services, I'd recommend 10.0 for
>> completeness, with GUS-Br or SlackSec patches. You can google around to
>> find those. Good luck to you, and come back here if you get stuck.
>>
>
> I should be ok as everything is behind a farly hard firewall it is the
> usal close unused ports stop un used/needed serves keep up to daate pach
> and app wise I guess.
>
>> - -- It is better to hear the rebuke of the wise,
>> Than for a man to hear the song of fools.
>> Ecclesiastes 7:5
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>>
>> iD8DBQFB8wjhlKR45I6cfKARAh+3AJ9Ll/6d3oUIh9kJxLNgmLJbH4hR0QCeL8gr
>> YcWS3LmmyA/BGHl3nCmXfUY=
>> =UC0e
>> -----END PGP SIGNATURE-----
>
>
> Thankks A lot just a gental nuge in the correct direction.

Looks like I have most of the things running now

--
http://cooze.co.nz home of the RecyclerMan aka Robert Cooze

/ __/ / / / / /__ / / ___/ / __/ / / / |/ / /__ /
/ / / /_/ / / /_/ / _-' / __/ / / / /_/ / / /| / _-'
___\ ____/ ____/ /___/ /____/ /_/ ___\ ____/ /_/ /_/ |_/ /___/

On 2005-01-28, Robert Cooze <nopants66@hotmail.com> wrote:

>> Thankks A lot just a gental nuge in the correct direction.

Trim your posts, please. Thank you.

nb