SEO

So, if any of you are like me you have been sitting there asking yourself
what can be done to help PV and Slackware. The only thing that I can
think of (not being medically inclined) is to develop Slackware while
he is gone. I figure we can test and submit bugs and those of us with
coding ability can do our best to fix the bugs. Once we fix one send it
to The Man and hopefully save him some work. Please let me know what you
think. If you like the idea go to http://www.voidmain.net and check it
out. There isn't much there now but I setup some forums, one of which is
a Slackware forum. Post ideas there and if I get some support I will
create a seperate Thread entitiled Slackware with bugs and fixes as topics
under it so we can get started. Thanks.

-link

link wrote:
> I figure we can test and submit bugs and those of us with
> coding ability can do our best to fix the bugs. Once we fix one send it
> to The Man and hopefully save him some work. Please let me know what you
> think. If you like the idea go to http://www.voidmain.net and check it
> out. There isn't much there now but I setup some forums, one of which is
> a Slackware forum. Post ideas there and if I get some support I will
> create a seperate Thread entitiled Slackware with bugs and fixes as topics
> under it so we can get started. Thanks.

Well, most bugs should be should be the responsibility of the
programmers of the respective application. But if there's something that
looks like it's Pat's fault , I'll report it there.
Nice idea, mate!

~Mik

--
ls -l /mnt
lrwxrwxrwx 1 root root 9 2004-11-11 17:57 doom -> /dev/null

On Wed, 17 Nov 2004 17:13:40 +0100,
Mario Berger <no_damned_spam@nospam.no> wrote:
> link wrote:
>> I figure we can test and submit bugs and those of us with
>> coding ability can do our best to fix the bugs. Once we fix one send it
>> to The Man and hopefully save him some work.
>
> Well, most bugs should be should be the responsibility of the
> programmers of the respective application. But if there's something that
> looks like it's Pat's fault , I'll report it there.
> Nice idea, mate!

Not to belittle the OP's efforts, but why not post Slackware bugs here?
There's already an estabilshed user-base in the NG, with lots of people
who can work issues out.

--
Mark Hill

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

In alt.os.linux.slackware, Mark Hill dared to utter,
> Not to belittle the OP's efforts, but why not post Slackware bugs here?
> There's already an estabilshed user-base in the NG, with lots of people
> who can work issues out.

I agree with Mark on this issue. I'm going to e-mail Pat soon after I
talk with other people who've had this idea and see where the many
different groups stand. I don't think there's any reason why a number
of different groups should be doing the same work multiple times.
Having everyone work together would be better. I know some people on
IRC have already begun discussions about this.

Bug reports should come here, where things are already well entrenched
and people know to come here.

- --
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)

iD8DBQFBm5bDlKR45I6cfKARAi6LAJ9n5WZ9geQxBWNQ6oh6k1 7R8A0o1QCdESik
zA1/7kavwdS8P49GmAGQXII=
=zR4A
-----END PGP SIGNATURE-----

On Wed, 17 Nov 2004 18:21:44 +0000, +Alan Hicks+ wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Mark Hill dared to utter,
>> Not to belittle the OP's efforts, but why not post Slackware bugs here?
>> There's already an estabilshed user-base in the NG, with lots of people
>> who can work issues out.
>
> I agree with Mark on this issue. I'm going to e-mail Pat soon after I
> talk with other people who've had this idea and see where the many
> different groups stand. I don't think there's any reason why a number
> of different groups should be doing the same work multiple times.
> Having everyone work together would be better. I know some people on
> IRC have already begun discussions about this.
>
> Bug reports should come here, where things are already well entrenched
> and people know to come here.
>
> - --
> 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)
>
> iD8DBQFBm5bDlKR45I6cfKARAi6LAJ9n5WZ9geQxBWNQ6oh6k1 7R8A0o1QCdESik
> zA1/7kavwdS8P49GmAGQXII=
> =zR4A
> -----END PGP SIGNATURE-----

Okay, that sounds good to me too. With everything that PV has done for
the Slackware community I don't want him to have to go through this hard
time without support. Hopefully we can show the corporate slobs that the
open source community is stronger than they think by pulling together.
Thanks for the replies everyone...I hope that we can work together and
keep Slackware going while Patrick gets well.

-link

link wrote:

> On Wed, 17 Nov 2004 18:21:44 +0000, +Alan Hicks+ wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> In alt.os.linux.slackware, Mark Hill dared to utter,
>>> Not to belittle the OP's efforts, but why not post Slackware bugs here?
>>> There's already an estabilshed user-base in the NG, with lots of people
>>> who can work issues out.
>>
>> I agree with Mark on this issue. I'm going to e-mail Pat soon after I
>> talk with other people who've had this idea and see where the many
>> different groups stand. I don't think there's any reason why a number
>> of different groups should be doing the same work multiple times.
>> Having everyone work together would be better. I know some people on
>> IRC have already begun discussions about this.
>>
>> Bug reports should come here, where things are already well entrenched
>> and people know to come here.
>>
>>


OK then lets start that ball rolling.

Has anyone got Apache to run with Slack10. ? The standard install fails as
mod_vhost_alias is not where it's expected (/usr/libexec - it's actually
in /usr/libexec/apache).

I spotted it first with the initial issue 1.3.31, but upgrading to 1.3.33
makes no difference.

BTW this system has ben upgraded from 9.1.

I'm going to rebuild from source tomorrow (I hope), but in the meantime has
anyone tripped across this ?

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

In alt.os.linux.slackware, link dared to utter,
>> Bug reports should come here, where things are already well entrenched
>> and people know to come here.
>
> Okay, that sounds good to me too. With everything that PV has done for
> the Slackware community I don't want him to have to go through this hard
> time without support.

That is the idea. A little bit of an update. Some of the regulars here
and on IRC are starting to pull together a website at
http://slacksec.fredemmott.co.uk/

we're hoping to have ftp space on a fat pipe soon enough and begin
rolling out security fixes. I'll post more here when I know more.

- --
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)

iD8DBQFBm8VtlKR45I6cfKARApuTAJ41tQG8+P7pvNc7kjNZjX RCpmC6SgCgpfh9
9RfWR+MhvZqxa+O8hjV/BSo=
=eB0H
-----END PGP SIGNATURE-----

On Wed, 17 Nov 2004 14:54:04 -0500, link wrote:


>
> Okay, that sounds good to me too. With everything that PV has done for
> the Slackware community I don't want him to have to go through this hard
> time without support. Hopefully we can show the corporate slobs that the
> open source community is stronger than they think by pulling together.
> Thanks for the replies everyone...I hope that we can work together and
> keep Slackware going while Patrick gets well.
>
> -link

While I am not really able to offer any support in a coding/programing
capacity, I will be opening my checkbook and paying for slack. Under the
circumstances, this is likely as helpful as anything. Perhaps others feel
the same?

I know most here already have a subscription, but for those who don't this
may be the time to pony up.

The way I see it, Pat has "saved" me 1 year of SuSE. That's worth at
least $80.00 regardless of what the "official" slack subscription price is.

My 2 cents (and then some ;-) )

Keith Matthews wrote:

> Has anyone got Apache to run with Slack10. ? The standard install
> fails as mod_vhost_alias is not where it's expected (/usr/libexec -
> it's actually in /usr/libexec/apache).

I had the same issue. Solved it by placing symlinking from /usr/libexec
to /usr/libexec/apache


> BTW this system has ben upgraded from 9.1.

Same here.

Cheerz Lars

"Keith Matthews" <invalid@frequentous.co.uk> wrote in message
news:99CdnTZV49ouKwbcRVnysQ@eclipse.net.uk...
>
> Has anyone got Apache to run with Slack10. ? The standard install fails as
> mod_vhost_alias is not where it's expected (/usr/libexec - it's actually
> in /usr/libexec/apache).
>
> I spotted it first with the initial issue 1.3.31, but upgrading to 1.3.33
> makes no difference.
>
> BTW this system has ben upgraded from 9.1.

When upgrading you need to compare /etc/apache/http.conf with
/etc/apache/httpd.conf.default and change some things over