Re: yellowdog-general Digest 22 Aug 2001 09:35:18 -0000 Issue 502

Subject: Re: yellowdog-general Digest 22 Aug 2001 09:35:18 -0000 Issue 502
spam_filter@linuxfreemail.com
Date: Wed Aug 22 2001 - 04:29:13 MDT

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Next message: spam_filter@linuxfreemail.com: "Re: yellowdog-general Digest 22 Aug 2001 09:37:37 -0000 Issue 503"
Previous message: Gavin Hemphill: "Upgrading to 9.2 on a NW machine with YDL2.0 installed"

>--fdnlkohfjjelbbkfbada
>Content-Type: text/plain; charset=us-ascii

>yellowdog-general Digest 22 Aug 2001 09:35:18 -0000 Issue 502

>Topics (messages 13677 through 13699):

>yellowdog-general Digest 20 Aug 2001 23:26:08 -0000 Issue 501
> 13677 by: spam_filter@linuxfreemail.com
> 13679 by: ABrady <kcsmart@kc.rr.com>
> 13685 by: Alan Orth <aorth@mac.com>

>KDE 2.2 for YDL 2.0
> 13678 by: Mark Jaffe <wizards@wizdev.net>
> 13681 by: Dan Burcaw <dburcaw@terraplex.com>

>failed to install iptables rpm
> 13680 by: "Timothy A. Seufert" <tas@mindspring.com>
> 13684 by: Murias O'Ceallagh <linux@dragonsblood.net>
> 13689 by: "Timothy A. Seufert" <tas@mindspring.com>

>Xinetd 2.3.2
> 13682 by: Darron Froese <darron@froese.org>

>Can't start X Server in 6400 installation.
> 13683 by: Michael Alexander Owens <endymionmichael@mac.com>

>rpm failure
> 13686 by: Iain Stevenson <iain@IainStevenson.com>

>making Yaboot indefinite
> 13687 by: Bookem <bookem@totalise.co.uk>
> 13688 by: spam_filter@linuxfreemail.com

>mol on ydl kernel 2.4.4-1a
> 13690 by: Trevor Marshall <trevor@risk2risk.com>

>2.4.x SMP kernels...
> 13691 by: Mark Jaffe <wizards@wizdev.net>
> 13693 by: Trevor Marshall <trevor@risk2risk.com>

>Good read
> 13692 by: Robert Brandtjen <rob@prometheusmedia.com>

>FTP Help
> 13694 by: Brian Watson <bcwatso1@uiuc.edu>

>ProFTPD 1.2.2 (and ftp login problems)
> 13695 by: mike <mike@mercuryrising.mine.nu>

>More frequent Powerbook wake-up failures
> 13696 by: "Paul J. Lucas" <pauljlucas@mac.com>

>[OT] Mailing list manager reco's?
> 13697 by: Sam Moore <samiwas@macconnect.com>
> 13698 by: Chuq Von Rospach <chuqui@plaidworks.com>

>Upgrading to 9.2 on a NW machine with YDL2.0 installed
> 13699 by: Gavin Hemphill <hemphill@drea.dnd.ca>

>Administrivia:

>To subscribe to the digest, e-mail:
> yellowdog-general-digest-subscribe@lists.yellowdoglinux.com

>To unsubscribe from the digest, e-mail:
> yellowdog-general-digest-unsubscribe@lists.yellowdoglinux.com

>To post to the list, e-mail:
> yellowdog-general@lists.yellowdoglinux.com

>----------------------------------------------------------------------

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13677"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Mon, 20 Aug 2001 17:19:45 -0700
>Message-Id: <200108210019.f7L0Jj829740@superglide.netfx-2000.net>
>To: yellowdog-general@lists.yellowdoglinux.com
>From: spam_filter@linuxfreemail.com
>Subject: Re: yellowdog-general Digest 20 Aug 2001 23:26:08 -0000 Issue 501

>>--clhhghaipaigjbnbbmnp
>>Content-Type: text/plain; charset=us-ascii

>>yellowdog-general Digest 20 Aug 2001 23:26:08 -0000 Issue 501

>>Topics (messages 13647 through 13676):

>>FTP Again
>> 13647 by: Brian Watson <bcwatso1@uiuc.edu>

>>another new user with PPP trouble
>> 13648 by: Ben Stallings <Ben@WorksCited.Net>
>> 13650 by: "eric hernandez" <hnz.eric@freesurf.fr>

>>making Yaboot indefinite
>> 13649 by: Bookem <bookem@totalise.co.uk>
>> 13651 by: spam_filter@linuxfreemail.com
>> 13654 by: Dan Burcaw <dburcaw@terraplex.com>
>> 13656 by: spam_filter@linuxfreemail.com
>> 13657 by: "Pete Peters" <ppeters914@home.com>
>> 13660 by: Chuq Von Rospach <chuqui@plaidworks.com>

>>nfs export mystery solved (partly)
>> 13652 by: Neil Jolly <neil@jollycom.ca>

>>Precompiled Kernel w/ 3D accel and Dual Process Support
>> 13653 by: cdowns@amanet.org
>> 13655 by: Dan Burcaw <dburcaw@terraplex.com>
>> 13661 by: Jose M. <josemanuel@valux.org>
>> 13662 by: "Ruprecht, Chris" <cruprech@compucom.com>
>> 13663 by: Robert Vogt IV <robert@arborhost.com>

>>SendMail Question
>> 13658 by: "Howard Shere" <hshere@greendragon.com>
>> 13659 by: Robert Brandtjen <rob@prometheusmedia.com>

>>Yellowdog Linux on RS/6000
>> 13664 by: Derek Richardson <derek.richardson@pgs.com>

>>failed to install iptables rpm
>> 13665 by: Murias O'Ceallagh <linux@dragonsblood.net>
>> 13666 by: "Iain Stevenson" <iain@iainstevenson.com>
>> 13667 by: Dan Burcaw <dburcaw@terraplex.com>
>> 13671 by: Murias O'Ceallagh <linux@dragonsblood.net>
>> 13673 by: Bryn Hughes <linux@demian.shacknet.nu>

>>Kernel compiling process
>> 13668 by: Donovan Warren <aramis_@Bacil.DYNDNS.ORG>
>> 13669 by: Bryn Hughes <linux@demian.shacknet.nu>
>> 13670 by: John Norair <splinemodel@mac.com>
>> 13672 by: Murias O'Ceallagh <linux@dragonsblood.net>

>>rpm failure
>> 13674 by: Murias O'Ceallagh <linux@dragonsblood.net>

>>KDE 2.2 for YDL 2.0
>> 13675 by: Phil <pdarling@voyager.net>
>> 13676 by: Dan Burcaw <dburcaw@terraplex.com>

>>Administrivia:

>>To subscribe to the digest, e-mail:
>> yellowdog-general-digest-subscribe@lists.yellowdoglinux.com

>>To unsubscribe from the digest, e-mail:
>> yellowdog-general-digest-unsubscribe@lists.yellowdoglinux.com

>>To post to the list, e-mail:
>> yellowdog-general@lists.yellowdoglinux.com

>>----------------------------------------------------------------------

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13647"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Mime-Version: 1.0
>>Message-Id: <a05101000b7a5eba89e54@[192.168.1.4]>
>>Date: Sun, 19 Aug 2001 17:41:57 -0500
>>To: yellowdog-general@lists.yellowdoglinux.com
>>From: Brian Watson <bcwatso1@uiuc.edu>
>>Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>>Subject: FTP Again

>>I am having a problem connecting to my ftp server with I'm not on my
>>local network. I have the YDL box as the DMZ behind my router, but
>>any attempt to connect to the server tries to access it from its
>>internal IP. Example:

>>I connect from:

>>12:34:56:78

>>to my server

>>My ftp server sends back the ip for 192.168.1.2 (the server's internal IP)

>>Where would this problem be? Is there some way to bind proftpd to
>>the external IP address?

>>--Brian

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13648"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Message-Id: <l03130301b7a62dfb7b38@[216.160.33.19]>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="us-ascii"
>>Date: Sun, 19 Aug 2001 22:12:46 -0500
>>To: yellowdog-general@lists.yellowdoglinux.com
>>From: Ben Stallings <Ben@WorksCited.Net>
>>Subject: another new user with PPP trouble

>>Hi, folks. From the look of the archives, I'm not alone in having trouble
>>getting PPP to run reliably in a fresh YDL installation. It worked
>>flawlessly the first time I used it, but hasn't worked since... even though
>>I wiped the Linux partitions and reinstalled YDL from scratch, and *that*
>>didn't help, and even though it still works fine under Mac OS.

>>I've tried a half dozen different fixes that people suggested in the
>>archives, but since I tried them one after another, I'm afraid I may have
>>scrambled things up hopelessly by now, and I'd just like to start over. I
>>figure if I could start with a fresh install of PPP, I could follow the
>>steps in PPP-HOWTO. But first I have a couple of questions for you:

>>1. How do I reinstall PPP alone? Which RPM is it in? Do I need to delete
>>existing files prior to running 'rpm -i' to get a clean install? Which
>>ones?

>>2. What lock file(s) are used by pppd? If the connection drops and pppd
>>doesn't realize it, do I need to manually delete the lock file(s)?

>>3. My modem is internal (PowerBook G3 "Wallstreet"). Could it be holding a
>>grudge against YDL that might be cleared by cutting all power (zapping the
>>PRAM 3 to 5 times)? Or does the fact that it still works under Mac OS
>>prove that the modem is fine?

>>4. Do any of you folks live in the Twin Cities, Minnesota? I'll take you
>>out for lunch if you'll look at my PowerBook... There's a local Linux user
>>group, but I don't know if any of them use YDL.

>>Many thanks!
>>Ben Stallings
>>Minneapolis, MN

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13650"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <000201c1297a$284a6e40$c4c82bd4@computer>
>>From: "eric hernandez" <hnz.eric@freesurf.fr>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Date: Mon, 20 Aug 2001 10:41:32 +0200
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>Subject: Re: another new user with PPP trouble

>>Hi Ben,

>>I have only one answer to your questions. Kppp is included in the kdenetwork
>>package.
>>You will find in a french website the installation journal of YDL on a
>>powerbook
>>http://www.lea-linux.org.
>>Type in the research window "modem configuration" you will find all the
>>experiments for installing YDL on a powerbook. There is a modem section. The
>>author mention how he configured his internal modem. The text is in french
>>but I think that you will be able to translate it on the internet. The bash
>>commands are "ininglishinzetext".
>>Hope that you'll find a solution
>>best regards

>>eric

>>----- Original Message -----
>>From: Ben Stallings <Ben@WorksCited.Net>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Sent: Monday, August 20, 2001 5:12 AM
>>Subject: another new user with PPP trouble

>>> Hi, folks. From the look of the archives, I'm not alone in having trouble
>>> getting PPP to run reliably in a fresh YDL installation. It worked
>>> flawlessly the first time I used it, but hasn't worked since... even
>>though
>>> I wiped the Linux partitions and reinstalled YDL from scratch, and *that*
>>> didn't help, and even though it still works fine under Mac OS.
>>>
>>> I've tried a half dozen different fixes that people suggested in the
>>> archives, but since I tried them one after another, I'm afraid I may have
>>> scrambled things up hopelessly by now, and I'd just like to start over. I
>>> figure if I could start with a fresh install of PPP, I could follow the
>>> steps in PPP-HOWTO. But first I have a couple of questions for you:
>>>
>>> 1. How do I reinstall PPP alone? Which RPM is it in? Do I need to delete
>>> existing files prior to running 'rpm -i' to get a clean install? Which
>>> ones?
>>>
>>> 2. What lock file(s) are used by pppd? If the connection drops and pppd
>>> doesn't realize it, do I need to manually delete the lock file(s)?
>>>
>>> 3. My modem is internal (PowerBook G3 "Wallstreet"). Could it be holding
>>a
>>> grudge against YDL that might be cleared by cutting all power (zapping the
>>> PRAM 3 to 5 times)? Or does the fact that it still works under Mac OS
>>> prove that the modem is fine?
>>>
>>> 4. Do any of you folks live in the Twin Cities, Minnesota? I'll take you
>>> out for lunch if you'll look at my PowerBook... There's a local Linux
>>user
>>> group, but I don't know if any of them use YDL.
>>>
>>> Many thanks!
>>> Ben Stallings
>>> Minneapolis, MN
>>>
>>>

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13649"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 14:16:10 +0100
>>From: Bookem <bookem@totalise.co.uk>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <3BA7DB79@mail.totalise.co.uk>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="ISO-8859-1"
>>Content-Transfer-Encoding: 7bit
>>Subject: making Yaboot indefinite

>>Is there any way to make yaboot stay at the os prompt indefinitely?

>>Totalise - the Users ISP

>>-----------------------
>>The Totalise Email system, probably the most flexible email system in the
>>world. To register for an account goto http://www.totalise.net

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13651"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 06:17:45 -0700
>>Message-Id: <200108201317.f7KDHjF17103@superglide.netfx-2000.net>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>From: spam_filter@linuxfreemail.com
>>Subject: Re: making Yaboot indefinite

>>>Is there any way to make yaboot stay at the os prompt indefinitely?

>>>Totalise - the Users ISP

>>>-----------------------
>>>The Totalise Email system, probably the most flexible email system in the
>>>world. To register for an account goto http://www.totalise.net

>>*** Your message did not reach its recipient ***
>>It was caught by the mailing system as spam.
>>If this message is not spam and you feel that
>>this message was caught in error, please email
>>a note to spam_filter@netfx-2000.net.
>>If this message is spam, knock it off!
>>This server is in California where it is illegal
>>to spam! We do not accept spam here!
>>We will go after all spammers to the maximum
>>extent of the law!

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13654"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Dan Burcaw <dburcaw@terraplex.com>
>>To: yellowdog-general@lists.yellowdoglinux.com,
>> Bookem <bookem@totalise.co.uk>
>>Date: Mon, 20 Aug 2001 09:49:13 -0600
>>MIME-Version: 1.0
>>Message-Id: <01082009491303.00665@tantive.terraplex.com>
>>Content-Transfer-Encoding: 8bit
>>Subject: Re: making Yaboot indefinite

>>There is a 'delay=' option
>>in your /etc/yaboot.conf file...

>>On Monday 20 August 2001 07:16, Bookem wrote:
>>> Is there any way to make yaboot stay at the os prompt indefinitely?
>>>
>>> Totalise - the Users ISP
>>>
>>> -----------------------
>>> The Totalise Email system, probably the most flexible email system in the
>>> world. To register for an account goto http://www.totalise.net

>>--

>>Regards,
>>Dan Burcaw
>>Terra Soft Solutions, Inc.

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13656"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 08:43:39 -0700
>>Message-Id: <200108201543.f7KFhde26231@superglide.netfx-2000.net>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>From: spam_filter@linuxfreemail.com
>>Subject: Re: making Yaboot indefinite

>>>There is a 'delay=' option
>>>in your /etc/yaboot.conf file...

>>>On Monday 20 August 2001 07:16, Bookem wrote:
>>>> Is there any way to make yaboot stay at the os prompt indefinitely?
>>>>
>>>> Totalise - the Users ISP
>>>>
>>>> -----------------------
>>>> The Totalise Email system, probably the most flexible email system in the
>>>> world. To register for an account goto http://www.totalise.net

>>>--

>>>Regards,
>>>Dan Burcaw
>>>Terra Soft Solutions, Inc.

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13657"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>From: "Pete Peters" <ppeters914@home.com>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Date: Mon, 20 Aug 2001 09:01:23 -0700
>>Message-ID: <000f01c12991$5cfd85c0$549a0c41@sttln1.wa.home.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>Subject: RE: making Yaboot indefinite

>>Ahhhh, nothing starts a Monday like email from spam_filter. :-(

>>Hmmmm, since they're essentially 'spamming' us, I guess they can take
>>themselves to court for violating the law.

>>Pete
>>"Windows 2000 not found: (C)heer, (P)arty, (D)ance?"

>>-----Original Message-----
>>From: spam_filter@linuxfreemail.com
>>[mailto:spam_filter@linuxfreemail.com]
>>Sent: Monday, August 20, 2001 8:44 AM
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Subject: Re: making Yaboot indefinite

>>[snip]

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13660"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 10:08:42 -0700
>>From: Chuq Von Rospach <chuqui@plaidworks.com>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Message-ID: <B7A6922A.4E91%chuqui@plaidworks.com>
>>Mime-version: 1.0
>>Content-type: text/plain; charset="US-ASCII"
>>Content-transfer-encoding: 7bit
>>Subject: Re: making Yaboot indefinite

>>Even better -- I tried to write their abuse account to tell them to fix
>>their filter, and it bounced as user unknown.

>>I suggest we ALL set up filters to forward all this stuff back to them,
>>every time it happens, and maybe they'll figure it out...

>>On 8/20/01 9:01 AM, "Pete Peters" <ppeters914@home.com> wrote:

>>> Ahhhh, nothing starts a Monday like email from spam_filter. :-(

>>--
>>Chuq Von Rospach, Internet Gnome <http://www.chuqui.com>
>>[<chuqui@plaidworks.com> = <me@chuqui.com> = <chuq@apple.com>]
>>Yes, yes, I've finally finished my home page. Lucky you.

>>I wish I could say your enthusiasm was contagious...

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13652"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <20010820134145.13326.qmail@biathlon.jollycomp>
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Neil Jolly <neil@jollycom.ca>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Date: Mon, 20 Aug 2001 07:41:45 -0600
>>MIME-Version: 1.0
>>Content-Transfer-Encoding: 8bit
>>Subject: nfs export mystery solved (partly)

>>It appears that the uid must be the same on both systems for full access to
>>the shared directory. Once I changed the uid to on my OS X system to be
>>identical to that on the ydl machine I was able to access my home directory
>>alright. I'm still not sure why I have access to some directories where the
>>uid is different though.

>>Neil

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13653"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <OFEA62B8E1.77F3BB86-ON85256AAE.00527302@nyc.amanet.org>
>>From: cdowns@amanet.org
>>Date: Mon, 20 Aug 2001 10:02:36 -0500
>>MIME-Version: 1.0
>>Content-type: text/plain; charset=us-ascii
>>Subject: Precompiled Kernel w/ 3D accel and Dual Process Support

>>Does anyone have a precompiled 2.4.x kernel for a dual processor with 3d
>>acceleration. I tried to compile one this weekend, but kept getting agp
>>errors, and flush cache errors, and keyboard errors. If anyone could help
>>it would be appreciated!

>> Charles Downs
>>Padgett-Thompson Products

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13655"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Dan Burcaw <dburcaw@terraplex.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 09:50:07 -0600
>>MIME-Version: 1.0
>>Message-Id: <01082009500704.00665@tantive.terraplex.com>
>>Content-Transfer-Encoding: 8bit
>>Subject: Re: Precompiled Kernel w/ 3D accel and Dual Process Support

>>Take a look at my 2.4.8 kernel...
>>ftp://ftp.penguinppc.org/users/dburcaw/kernel-2.4.8/

>>On Monday 20 August 2001 09:02, cdowns@amanet.org wrote:
>>> Does anyone have a precompiled 2.4.x kernel for a dual processor with 3d
>>> acceleration. I tried to compile one this weekend, but kept getting agp
>>> errors, and flush cache errors, and keyboard errors. If anyone could help
>>> it would be appreciated!
>>>
>>> Charles Downs
>>> Padgett-Thompson Products

>>--

>>Regards,
>>Dan Burcaw
>>Terra Soft Solutions, Inc.

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13661"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Jose M. <josemanuel@valux.org>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 20:17:59 +0200
>>MIME-Version: 1.0
>>Message-Id: <01082020175903.00877@localhost.localdomain>
>>Content-Transfer-Encoding: 8bit
>>Subject: Re: Precompiled Kernel w/ 3D accel and Dual Process Support

>>El dia Monday 20 August 2001 17:50, escribiste:
>>>% Take a look at my 2.4.8 kernel...
>>>% ftp://ftp.penguinppc.org/users/dburcaw/kernel-2.4.8/
>>>%
>>>%
>>>%
>>>% On Monday 20 August 2001 09:02, cdowns@amanet.org wrote:
>>>% > Does anyone have a precompiled 2.4.x kernel for a dual processor with
>>> 3d % > acceleration. I tried to compile one this weekend, but kept
>>> getting agp % > errors, and flush cache errors, and keyboard errors. If
>>> anyone could help % > it would be appreciated!
>>>% >
>>>% > Charles Downs
>>>% > Padgett-Thompson Products
>>>%
>>Please, which file contains kernel source?
>>kernel-source-2.4.8-0.4c.ppc.rpm
>>or
>>kernel-2.4.8-0.4c.src.rpm

>>Thanks in advance.
>>--
>>Salu2.
>>.-
>>-.-.-.-.-.-
>>'First they ignore you. Then they laugh at
>>you. Then they fight you. Then you win.' Evidently, we are
>>getting close to winning." Gandhi
>>-.-.-.-.-.-

>>Visit http://www.valux.org
>>**************************
>>Jose M. Laveda
>>josemanuel@valux.org
>>P.O.Box. 70
>>CULLERA - Valencia (Spain)
>>**************************

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13662"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: quoted-printable
>>Date: Mon, 20 Aug 2001 14:52:18 -0400
>>Message-ID: <5363693F6365114CB50D4090541289108A7930@va2-cmpucm-cn6.compucom.mail>
>>From: "Ruprecht, Chris" <cruprech@compucom.com>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Subject: RE: Re: Precompiled Kernel w/ 3D accel and Dual Process Support

>>Is this a trick question?

>>> -----Original Message-----
>>> From: Jose M. [mailto:josemanuel@valux.org]
>>> Sent: Monday, August 20, 2001 1:18 PM
>>> To: yellowdog-general@lists.yellowdoglinux.com
>>> Subject: Re: Precompiled Kernel w/ 3D accel and Dual Process Support
>>>=20

>>[snip]

>>> Please, which file contains kernel source?
>>> kernel-source-2.4.8-0.4c.ppc.rpm=20
>>> or
>>> kernel-2.4.8-0.4c.src.rpm=20
>>>=20

>>which of the two above has the words "kernel" and "source" in it?

>>Ciao,
>>Chris

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13663"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 15:17:20 -0400 (EDT)
>>From: Robert Vogt IV <robert@arborhost.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <Pine.LNX.4.21.0108201515570.27274-100000@saturn.arborhost.com>
>>MIME-Version: 1.0
>>Content-Type: TEXT/PLAIN; charset=US-ASCII
>>Subject: RE: Re: Precompiled Kernel w/ 3D accel and Dual Process Support

>>> > Please, which file contains kernel source?
>>> > kernel-source-2.4.8-0.4c.ppc.rpm
>>> > or
>>> > kernel-2.4.8-0.4c.src.rpm
>>> >
>>>
>>> which of the two above has the words "kernel" and "source" in it?

>> Wrong. They both contain kernel source. But the source RPM is
>>packaged for compilation as an RPM, while the kernel-source RPM is kernel
>>source ready to be placed in /usr/src automagically. (Use the first, even
>>though both will work...)

>> -Robert Vogt IV

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13658"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 11:17:42 -0500
>>From: "Howard Shere" <hshere@greendragon.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Mime-version: 1.0
>>Content-type: text/plain; charset="US-ASCII"
>>Content-transfer-encoding: 7bit
>>Message-Id: <S.0006393836@watervalley.net>
>>Subject: SendMail Question

>>I know there is a way to do this, but I cannot figure out what it is.

>>I'd like to have sendmail only be allowed to send mail to an address which
>>resolves to a particular IP address. If the mail is supposed to be sent
>>elsewhere, I'd like it to be dumped.

>>The IP I want to send it to is our mail server (on another machine) and the
>>only thing we want to run sendmail on our yellow dog machine (our webserver)
>>is to handle forms. All the forms will be setup to send to an address on our
>>mail server.

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13659"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 11:46:56 -0500
>>From: Robert Brandtjen <rob@prometheusmedia.com>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Message-ID: <B7A6A930.90AA%rob@prometheusmedia.com>
>>Mime-version: 1.0
>>Content-type: text/plain; charset="US-ASCII"
>>Content-transfer-encoding: 7bit
>>Subject: Re: sendmail Question

>>on 8/20/01 11:17 AM, Howard Shere at hshere@greendragon.com wrote:

>>> The IP I want to send it to is our mail server (on another machine) and the
>>> only thing we want to run sendmail on our yellow dog machine (our webserver)
>>> is to handle forms. All the forms will be setup to send to an address on our
>>> mail server.

>>http://groups.google.com/groups?oi=djq&as_ugroup=comp.mail.sendmail

>>Look here - anything you want to do with sendmail has already been
>>asked/answered there.

>> Robert Brandtjen
>> --------------------------------------
>> Web Site Creation and Hosting Services
>> Hostmaster@prometheusmedia.com
>> www.prometheusmedia.com

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13664"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>From: Derek Richardson <derek.richardson@pgs.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain
>>Content-Transfer-Encoding: 7bit
>>Date: 20 Aug 2001 14:54:23 -0500
>>Message-Id: <998337263.2911.4349.camel@idoru.hstn.tensor.pgs.com>
>>Mime-Version: 1.0
>>Subject: Yellowdog Linux on RS/6000

>>All,
>>Does YDL run on IBM RS/6000 3BT workstations? If so, which version
>>works best? Thanks in advance...
>>Regards,
>>Derek R.
>>--
>>Junior Linux Geek
>>713-817-1197 (cell)
>>713-781-4000 x2267 (office)
>>""If the personal freedoms guaranteed by the Constitution inhibit the
>>government's ability to govern the people, we should look to limit those
>>guarantees."
>>-- President Bill Clinton, August 12, 1993
>>"Huh?" --collective consciousness of America

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13665"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 13:53:09 -0700
>>From: Murias O'Ceallagh <linux@dragonsblood.net>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="US-ASCII"
>>Message-ID: <auto-000000390093@phreaki.radiogoth.com>
>>Subject: failed to install iptables rpm

>>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>>Hello all,

>>Trying to install the iptables-1.2.2.-1 rpm. I have just compiled a new
>>kernel and it is running rather nicely. Kernel I am running is
>>2.4.9-benh0.

>>The command I use for the install is;
>>rpm --install iptables-1.2.2-1.ppc.rpm

>>But then it comes back telling me;
>>error: failed dependencies:
>> kernel >= 2.4.0 is needed by iptables-1.2.2-1

>>So, I checked a few things,
>>dmesg tells me: Linux version 2.4.9-benh0
>>rpm -v kernel tells me: kernel-2.2.17-0.6.1

>>I do indeed have the 2.2.17 kernel on my machine, but it is not being
>>used. I keep it around cause it works. and it is the last kernel I was
>>ruinning before attempting the new 2.4 trees.

>>So, I then attempted doing;
>>rpm --force --install iptables-1.2.2-1.ppc.rpm

>>and got the same failed dependencies message.

>>Is there a way around this? Do I need to get rid of the 2.2.17 kernel
>>altogether now?

>>Any ideas/suggestions woudl be great.
>>TIA.

>>Murias

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13666"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <49166.192.168.1.220.998341819.squirrel@wallace>
>>Date: Mon, 20 Aug 2001 22:10:19 +0100 (BST)
>>From: "Iain Stevenson" <iain@iainstevenson.com>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain; charset=iso-8859-1
>>Content-Transfer-Encoding: 8bit
>>Subject: Re: failed to install iptables rpm

>>Hi Murias,

>>... is /usr/src/linux pointing to your new kernel sources? If not, you
>>need to fix up the symlink. First remove the old symlink. Then,
>>assuming the new kernel is in /build/kernel, you would type ln -s
>>/build/kernel /usr/src/linux

>> Iain

>>> *This message was transferred with a trial version of
>>CommuniGate(tm)
>>> Pro* Hello all,
>>>
>>> Trying to install the iptables-1.2.2.-1 rpm. I have just compiled a
>>> new kernel and it is running rather nicely. Kernel I am running is
>>> 2.4.9-benh0.
>>>
>>> The command I use for the install is;
>>> rpm --install iptables-1.2.2-1.ppc.rpm
>>>
>>> But then it comes back telling me;
>>> error: failed dependencies:
>>> kernel >= 2.4.0 is needed by iptables-1.2.2-1
>>>
>>> So, I checked a few things,
>>> dmesg tells me: Linux version 2.4.9-benh0
>>> rpm -v kernel tells me: kernel-2.2.17-0.6.1
>>>
>>> I do indeed have the 2.2.17 kernel on my machine, but it is not being
>>> used. I keep it around cause it works. and it is the last kernel I
>>> was ruinning before attempting the new 2.4 trees.
>>>
>>> So, I then attempted doing;
>>> rpm --force --install iptables-1.2.2-1.ppc.rpm
>>>
>>> and got the same failed dependencies message.
>>>
>>> Is there a way around this? Do I need to get rid of the 2.2.17 kernel
>>> altogether now?
>>>
>>> Any ideas/suggestions woudl be great.
>>> TIA.
>>>
>>> Murias

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13667"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Dan Burcaw <dburcaw@terraplex.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 15:24:46 -0600
>>MIME-Version: 1.0
>>Message-Id: <01082015244607.00665@tantive.terraplex.com>
>>Content-Transfer-Encoding: 8bit
>>Subject: Re: failed to install iptables rpm

>>This is a result of you not using an RPM-based kernel.

>>As I see it, you have two options:

>>1) run an rpm kernel such as:
>>ftp://ftp.penguinppc.org/users/dburcaw/kernel-2.4.8/
>>2) install with --nodeps

>>#2 is not advised.

>>>
>>> The command I use for the install is;
>>> rpm --install iptables-1.2.2-1.ppc.rpm
>>>
>>> But then it comes back telling me;
>>> error: failed dependencies:
>>> kernel >= 2.4.0 is needed by iptables-1.2.2-1
>>>
>>> So, I checked a few things,
>>> dmesg tells me: Linux version 2.4.9-benh0
>>> rpm -v kernel tells me: kernel-2.2.17-0.6.1
>>>
>>> I do indeed have the 2.2.17 kernel on my machine, but it is not being
>>> used. I keep it around cause it works. and it is the last kernel I was
>>> ruinning before attempting the new 2.4 trees.
>>>
>>> So, I then attempted doing;
>>> rpm --force --install iptables-1.2.2-1.ppc.rpm
>>>
>>> and got the same failed dependencies message.
>>>
>>> Is there a way around this? Do I need to get rid of the 2.2.17 kernel
>>> altogether now?
>>>
>>> Any ideas/suggestions woudl be great.
>>> TIA.
>>>
>>> Murias

>>--

>>Regards,
>>Dan Burcaw
>>Terra Soft Solutions, Inc.

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13671"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 14:39:35 -0700
>>From: Murias O'Ceallagh <linux@dragonsblood.net>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="US-ASCII"
>>Message-ID: <auto-000000390103@phreaki.radiogoth.com>
>>Subject: Re: failed to install iptables rpm

>>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>>1) the symlinks are there, and double checked several times. (I am always
>>extremely paranoid on this one to begin with)

>>2) not that crazy about the rpm kernels. (no offence to the ones that
>>build them) just like to limit the over head that some of them have and
>>make sure that certain things are in it.

>>3) installing with nodeps is not advised... reasoning here. I am quite
>>sure that I have all the deps installed. Been over the iptables help
>>pages at http://ipmasq.cjb.net/ and
>>http://www.e-infomax.com/ipmasq/howto/beta/c-html/index.html several
>>times. Having never even tried a nodeps install, I am quite curious as
>>to the reasons.

>>Thank you, both Iain and Dan. ;)

>>Murias

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13673"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 14:49:06 -0700
>>From: Bryn Hughes <linux@demian.shacknet.nu>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <B7A6D3E2.5E55%linux@demian.shacknet.nu>
>>Mime-version: 1.0
>>Content-type: text/plain; charset="US-ASCII"
>>Content-transfer-encoding: 7bit
>>Subject: Re: failed to install iptables rpm

>>There's also a switch you can pass rpm that will 'install' the RPM without
>>actually writing any files. It will write to the database that it's
>>installed, but it won't actually DO anything. If you download a 2.4.x
>>kernel and do it this way, RPM will think 2.4.x is installed but you'll be
>>using your version of 2.4.x. man rpm for info

>>Bryn

>>on 8/20/01 2:39 PM, Murias O'Ceallagh at linux@dragonsblood.net wrote:

>>> *This message was transferred with a trial version of CommuniGate(tm) Pro*
>>> 1) the symlinks are there, and double checked several times. (I am always
>>> extremely paranoid on this one to begin with)
>>>
>>> 2) not that crazy about the rpm kernels. (no offence to the ones that
>>> build them) just like to limit the over head that some of them have and
>>> make sure that certain things are in it.
>>>
>>> 3) installing with nodeps is not advised... reasoning here. I am quite
>>> sure that I have all the deps installed. Been over the iptables help
>>> pages at http://ipmasq.cjb.net/ and
>>> http://www.e-infomax.com/ipmasq/howto/beta/c-html/index.html several
>>> times. Having never even tried a nodeps install, I am quite curious as
>>> to the reasons.
>>>
>>> Thank you, both Iain and Dan. ;)
>>>
>>> Murias
>>>
>>>
>>>

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13668"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Donovan Warren <aramis_@Bacil.DYNDNS.ORG>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 14:30:20 -0700
>>MIME-Version: 1.0
>>Message-Id: <01082014302001.07661@yellowdog-linux.bacil.dyndns.org>
>>Content-Transfer-Encoding: quoted-printable
>>Subject: Kernel compiling process

>>on ix86, the basic process to roll a kernel is

>>- make mrproper
>>- make menuconfig
>>- make dep
>>- make bzImage

>>I can do the first three on my 7600, but make bzImage doesn't appear to b=
>>e a=20
>>rule in the 2.4.9 Makefile (downloaded from kernel.org).

>>What do I need to do on the Powermac to get the kernel actually built?

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13669"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 14:37:04 -0700
>>From: Bryn Hughes <linux@demian.shacknet.nu>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Message-ID: <B7A6D110.5E4E%linux@demian.shacknet.nu>
>>Mime-version: 1.0
>>Content-type: text/plain; charset="US-ASCII"
>>Content-transfer-encoding: 7bit
>>Subject: Re: Kernel compiling process

>>on 8/20/01 2:30 PM, Donovan Warren at aramis_@Bacil.DYNDNS.ORG wrote:

>>> on ix86, the basic process to roll a kernel is
>>>
>>> - make mrproper
>>> - make menuconfig
>>> - make dep
>>> - make bzImage
>>>
>>> I can do the first three on my 7600, but make bzImage doesn't appear to be a
>>> rule in the 2.4.9 Makefile (downloaded from kernel.org).
>>>
>>> What do I need to do on the Powermac to get the kernel actually built?
>>>

>>make zImage (no 'b')

>>Bryn

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13670"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Message-Id: <200108202136.OAA09842@smtpout.mac.com>
>>Date: Mon, 20 Aug 2001 17:36:56 -0400
>>Content-Type: text/plain;
>> format=flowed;
>> charset=us-ascii
>>From: John Norair <splinemodel@mac.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Mime-Version: 1.0 (Apple Message framework v388)
>>Content-Transfer-Encoding: 7bit
>>Subject: Re: Kernel compiling process

>>It would be a bit of a long email for me to write, so I'll just point
>>you to a link:

>>http://www.powermaclinux.net/php/powermaclinux_g_h.php3?single=4

>>try that,
>>John Norair

>>On Monday, August 20, 2001, at 05:30 PM, Donovan Warren wrote:

>>> on ix86, the basic process to roll a kernel is
>>>
>>> - make mrproper
>>> - make menuconfig
>>> - make dep
>>> - make bzImage
>>>
>>> I can do the first three on my 7600, but make bzImage doesn't appear to
>>> be a
>>> rule in the 2.4.9 Makefile (downloaded from kernel.org).
>>>
>>> What do I need to do on the Powermac to get the kernel actually built?
>>>

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13672"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 14:44:53 -0700
>>From: Murias O'Ceallagh <linux@dragonsblood.net>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="US-ASCII"
>>Message-ID: <auto-000000390107@phreaki.radiogoth.com>
>>Subject: Re: Kernel compiling process

>>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>>>on ix86, the basic process to roll a kernel is
>>>
>>>- make mrproper
>>>- make menuconfig
>>>- make dep
>>>- make bzImage
>>>
>>>I can do the first three on my 7600, but make bzImage doesn't appear to be a
>>>rule in the 2.4.9 Makefile (downloaded from kernel.org).
>>>
>>>What do I need to do on the Powermac to get the kernel actually built?

>>This is how I do things
>>make mrproper
>>make menuconfig
>>make dep
>>make vmlinux
>>make modules
>>make modules_install
>>copy things to the /boot
>>create appropriate symlinks in /boot
>>then mount the mac partition and cp the kernel to the appropriate folder
>>in the System Folder
>>reboot
>>pray. ;)

>>Murias

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13674"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 15:46:07 -0700
>>From: Murias O'Ceallagh <linux@dragonsblood.net>
>>To: <yellowdog-general@lists.yellowdoglinux.com>
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="US-ASCII"
>>Message-ID: <auto-000000390126@phreaki.radiogoth.com>
>>Subject: rpm failure

>>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>>I tried to do a;
>>rpm --install --justdb kernel-2.4.8-0.4c.ppc.rpm

>>and got;
>>only packages with major numbers <= 3 are supported by this version of RPM

>>i have never seen this before. Anyone know what this means?

>>Murias

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13675"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Phil <pdarling@voyager.net>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 19:50:09 -0400
>>MIME-Version: 1.0
>>Message-Id: <01082019500900.00711@localhost.localdomain>
>>Content-Transfer-Encoding: 8bit
>>Subject: KDE 2.2 for YDL 2.0

>>Any one know when precompiled RPM's will be available? I know the source
>>code is out but...

>>Thanks,

>>Phil

>>--clhhghaipaigjbnbbmnp
>>Content-Type: message/rfc822
>>Content-Disposition: inline; filename="yellowdog-general.13676"

>>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>From: Dan Burcaw <dburcaw@terraplex.com>
>>To: yellowdog-general@lists.yellowdoglinux.com
>>Date: Mon, 20 Aug 2001 18:24:27 -0600
>>MIME-Version: 1.0
>>Message-Id: <01082018242708.00665@tantive.terraplex.com>
>>Content-Transfer-Encoding: 8bit
>>Subject: Re: KDE 2.2 for YDL 2.0

>>Probably within the week..

>>On Monday 20 August 2001 17:50, you wrote:
>>> Any one know when precompiled RPM's will be available? I know the source
>>> code is out but...
>>>
>>> Thanks,
>>>
>>> Phil

>>--

>>Regards,
>>Dan Burcaw
>>Terra Soft Solutions, Inc.

>>--clhhghaipaigjbnbbmnp--

>*** Your message did not reach its recipient ***
>It was caught by the mailing system as spam.
>If this message is not spam and you feel that
>this message was caught in error, please email
>a note to spam_filter@netfx-2000.net.
>If this message is spam, knock it off!
>This server is in California where it is illegal
>to spam! We do not accept spam here!
>We will go after all spammers to the maximum
>extent of the law!

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13679"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Mon, 20 Aug 2001 19:38:17 -0500
>From: ABrady <kcsmart@kc.rr.com>
>To: yellowdog-general@lists.yellowdoglinux.com
>Message-Id: <20010820193817.0661356e.kcsmart@kc.rr.com>
>Mime-Version: 1.0
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: 7bit
>Subject: Re: yellowdog-general Digest 20 Aug 2001 23:26:08 -0000 Issue 501

>On Mon, 20 Aug 2001 17:19:45 -0700 spam_filter@linuxfreemail.com
>imparted to us:

>For anyone really annoyed by the repeated spam bouncing we've been
>receiving here, I did a whois, got the email address below, and asked
>them (nicely) to put an end to the bouncing. I explained that this is a
>mailing list and that someone obviously subscribed from their domain,
>but that it is now all bouncing several times daily. I would suggest
>others do the same and maybe we can get some action.

>op3@linuxfreemail.com

>--
>Most people have two reasons for doing anything: a good reason,
>and the real reason.

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13685"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 00:43:41 -0700
>From: Alan Orth <aorth@mac.com>
>To: yellowdog-general@lists.yellowdoglinux.com
>Message-id: <B7A75F3C.2DA%aorth@mac.com>
>MIME-version: 1.0
>Content-type: text/plain; charset="ISO-8859-1"
>Content-transfer-encoding: quoted-printable
>Subject: Re: yellowdog-general Digest 20 Aug 2001 23:26:08 -0000 Issue 501

>On 8/20/01 5:38 PM, "ABrady" <kcsmart@kc.rr.com> wrote:

>> On Mon, 20 Aug 2001 17:19:45 -0700 spam_filter@linuxfreemail.com
>> imparted to us:
>>=20
>> For anyone really annoyed by the repeated spam bouncing we've been
>> receiving here, I did a whois, got the email address below, and asked
>> them (nicely) to put an end to the bouncing. I explained that this is a
>> mailing list and that someone obviously subscribed from their domain,
>> but that it is now all bouncing several times daily. I would suggest
>> others do the same and maybe we can get some action.
>>=20
>> op3@linuxfreemail.com

>I would, but I'm not sure what happened... I don't understand what's going
>on. ;) I see a few 'spams' from that address, but for me, when I read the
>new mail from the list, if the Subject isn't interesting to me, or anything
>I can help with, I immediately delete. ;)
>--=20
>Alan Orth
>aorth@mac.com
>Macintosh =FCberhacker extraordinaire

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13678"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Mon, 20 Aug 2001 17:27:30 -0700
>From: Mark Jaffe <wizards@wizdev.net>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <B7A6F902.A09B%wizards@wizdev.net>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Re: KDE 2.2 for YDL 2.0

>On 8/20/01 5:24 PM, "Dan Burcaw" <dburcaw@terraplex.com> wrote:

>>
>> Probably within the week..

>Dan,

>Any updates on smp-2.4.x kernels? Where should I be looking? I still don't
>have one that will work on my dual-604e machine...

>Mark
>============================================================
>Mark Jaffe | (408) 972-9638 (home)
>Chief Wizard | (408) 807-1530 (cell/page/voicemail)
>Computer Wizards | (425) 795-6421 (FAX)
>wizards@wizdev.net | http://www.wizdev.net/

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13681"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Content-Type: text/plain;
> charset="iso-8859-1"
>From: Dan Burcaw <dburcaw@terraplex.com>
>To: yellowdog-general@lists.yellowdoglinux.com
>Date: Mon, 20 Aug 2001 21:22:04 -0600
>MIME-Version: 1.0
>Message-Id: <0108202122040F.00665@tantive.terraplex.com>
>Content-Transfer-Encoding: 8bit
>Subject: Re: KDE 2.2 for YDL 2.0

>Did you try the 2.4.8 (kernel-smp varient) kernel
>that I posted earlier?

>ftp://ftp.penguinppc.org/users/dburcaw/kernel-2.4.8/

>On Monday 20 August 2001 18:27, Mark Jaffe wrote:
>> On 8/20/01 5:24 PM, "Dan Burcaw" <dburcaw@terraplex.com> wrote:
>> > Probably within the week..
>>
>> Dan,
>>
>> Any updates on smp-2.4.x kernels? Where should I be looking? I still don't
>> have one that will work on my dual-604e machine...
>>
>> Mark
>> ============================================================
>> Mark Jaffe | (408) 972-9638 (home)
>> Chief Wizard | (408) 807-1530 (cell/page/voicemail)
>> Computer Wizards | (425) 795-6421 (FAX)
>> wizards@wizdev.net | http://www.wizdev.net/

>--

>Regards,
>Dan Burcaw
>Terra Soft Solutions, Inc.

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13680"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Mime-Version: 1.0
>Message-Id: <p05100301b7a76e3bb3f5@[10.0.0.42]>
>Date: Mon, 20 Aug 2001 19:09:32 -0700
>To: yellowdog-general@lists.yellowdoglinux.com
>From: "Timothy A. Seufert" <tas@mindspring.com>
>Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>Subject: Re: failed to install iptables rpm

>At 2:39 PM -0700 8/20/01, Murias O'Ceallagh wrote:

>>2) not that crazy about the rpm kernels. (no offence to the ones that
>>build them) just like to limit the over head that some of them have and
>>make sure that certain things are in it.

>You can have it both ways -- install the RPM kernel to satisfy the
>RPM dependencies, then use your own custom compiled kernel anyways.
>If you need to avoid name conflicts with a RPM kernel, edit the Linux
>kernel Makefile before building and define a value for EXTRAVERSION.

>For example, you could make EXTRAVERSION "murias", which will make
>the version string of a 2.4.8 kernel become "2.4.8-murias". In this
>scenario, after compiling the kernel and modules, "make
>modules_install" will put the modules under
>/lib/modules/2.4.8-murias/. The kernel itself should be copied to
>/boot/vmlinux-2.4.8-murias, and the System.map should be copied to
>/boot/System.map-2.4.8-murias. Then edit /etc/yaboot.conf and set it
>up to load vmlinux-2.4.8-murias, run ybin, and you're ready to go.
>(Or use whatever other bootloader setup is required -- old world Macs
>use BootX for example.)

>It's good to keep RPM dependencies sane. If you go about breaking
>dependencies between packages, RPM may not do the right thing some
>time in the future.

>That said, if you know what you're doing you can get away with it.

>One last point of advice -- most people put their own kernel source
>under /usr/src/linux, and compile kernels as root. There is actually
>no need to do this. You can put the kernel source tree under your
>own directory, and compile it as a regular user. You only need to be
>root to install the compiled kernel and its modules.

>This has the advantage of allowing you to leave whatever the
>distribution put under /usr/src/linux (frequently kernel headers)
>alone. In some cases you may need to symlink /usr/src/linux to point
>at your build tree, but this only applies when compiling software
>that depends far too heavily on kernel headers for its own good.
>(Theoretically, user space programs should never include kernel
>headers at all, and the core kernel hackers, including Linus
>Torvalds, are trying to discourage it. But in practice some programs
>do include them, and sometimes you may need to get the headers from
>the kernel you're actually running rather than the placeholders from
>the distribution's kernel source or kernel header packages.)

>The really cool thing about doing everything in your home dir is that
>if you should need to reinstall Linux, or move your environment to
>another computer, your environment is neatly encapsulated in
>basically two places: your home dir, and /etc. Tarball 'em both,
>move the home dir over, unpack the clone of /etc under the new home
>dir, and go to work redoing your new distribution's /etc config files
>by comparing old with new. This is especially useful when moving
>between distributions from different vendors.
>--
>Tim Seufert

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13684"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Mon, 20 Aug 2001 23:31:03 -0700
>From: Murias O'Ceallagh <linux@dragonsblood.net>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="US-ASCII"
>Message-ID: <auto-000000390213@phreaki.radiogoth.com>
>Subject: Re: failed to install iptables rpm

>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>Tim,
>Thank you so much for your explanation. It rocked. I am one of those
>that lieks to understand why I can or can't do something.

>Your explanation though raises two questions.
>1) in reference to the stuff below that I snipped in.. How is this done?
>I thought with a rpm you just rpm --install <package> .... If it requires
>a source rpm.. I have actually been looking for docs on how to use those
>appropriately and not found all that much. ie the man page and the
>how-to's at linuxdoc.

>>>2) not that crazy about the rpm kernels. (no offence to the ones that
>>>build them) just like to limit the over head that some of them have and
>>>make sure that certain things are in it.
>>
>>You can have it both ways -- install the RPM kernel to satisfy the
>>RPM dependencies, then use your own custom compiled kernel anyways.
>>If you need to avoid name conflicts with a RPM kernel, edit the Linux
>>kernel Makefile before building and define a value for EXTRAVERSION.
>>
>>For example, you could make EXTRAVERSION "murias", which will make
>>the version string of a 2.4.8 kernel become "2.4.8-murias". In this
>>scenario, after compiling the kernel and modules, "make
>>modules_install" will put the modules under
>>/lib/modules/2.4.8-murias/. The kernel itself should be copied to
>>/boot/vmlinux-2.4.8-murias, and the System.map should be copied to
>>/boot/System.map-2.4.8-murias. Then edit /etc/yaboot.conf and set it
>>up to load vmlinux-2.4.8-murias, run ybin, and you're ready to go.
>>(Or use whatever other bootloader setup is required -- old world Macs
>>use BootX for example.)

>second question, I have tried to install the kernel in rpm format and got
>an error (stated in one of my previous postings) the exact error that
>machine spewed forth to me;
>only packages with major numbers <= 3 are supported by this version of RPM

>thus I was unable to install a kernel from rpm.

>thanx.

>Murias

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13689"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Mime-Version: 1.0
>Message-Id: <p05100300b7a87a32b060@[10.0.0.42]>
>Date: Tue, 21 Aug 2001 13:56:50 -0700
>To: yellowdog-general@lists.yellowdoglinux.com
>From: "Timothy A. Seufert" <tas@mindspring.com>
>Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>Subject: Re: failed to install iptables rpm

>At 11:31 PM -0700 8/20/01, Murias O'Ceallagh wrote:
>>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>>Tim,
>>Thank you so much for your explanation. It rocked. I am one of those
>>that lieks to understand why I can or can't do something.
>>
>>Your explanation though raises two questions.
>>1) in reference to the stuff below that I snipped in.. How is this done?
>>I thought with a rpm you just rpm --install <package> .... If it requires
>>a source rpm.. I have actually been looking for docs on how to use those
>>appropriately and not found all that much. ie the man page and the
>>how-to's at linuxdoc.

>Ah -- I think we have got our wires crossed. My explanation was for
>how one can install a precompiled RPM kernel and/or sources (to
>satisfy RPM dependencies), while actually using an entirely different
>kernel compiled from non-RPM kernel sources. I guess it's been too
>long since I've even thought about compiling kernels from RPM source
>packages. :)

>>second question, I have tried to install the kernel in rpm format and got
>>an error (stated in one of my previous postings) the exact error that
>>machine spewed forth to me;
>>only packages with major numbers <= 3 are supported by this version of RPM
>>
>>thus I was unable to install a kernel from rpm.

>The only thing that comes to mind is that perhaps the packager used
>RPM build tools that are more recent than your version of RPM. But
>I've never seen that error before, and am not sure exactly what it
>means.
>--
>Tim Seufert

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13682"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Mon, 20 Aug 2001 22:24:49 -0600
>From: Darron Froese <darron@froese.org>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <B7A73EB0.CCA4%darron@froese.org>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Xinetd 2.3.2

>>From <http://xinetd.org/>:

>Warning: a bug was found in xinetd's string handling routines. All versions
>of xinetd prior to 2.3.1 are vulnerable. Please upgrade to xinetd 2.3.2.

><ftp://ftp.froese.org/rpms/ydl-2.0/xinetd/2.3.2/>

>It seems to work just fine for me.
>--
>darron
>darron@froese.org

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13683"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Message-Id: <200108210523.WAA13328@smtpout.mac.com>
>Date: Tue, 21 Aug 2001 01:16:02 -0400
>Content-Type: text/plain;
> format=flowed;
> charset=us-ascii
>Mime-Version: 1.0 (Apple Message framework v388)
>From: Michael Alexander Owens <endymionmichael@mac.com>
>To: yellowdog-general@lists.yellowdoglinux.com
>Content-Transfer-Encoding: 7bit
>Subject: Can't start X Server in 6400 installation.

>I recently tried installing YDL 2.0 in my 6400. I have 104 physical
>megabytes and a 240MHz G3, 20GB Maxtor hard disk and a 4GB IBM SCSI-2 in
>the upper bay. Installation of YDL was for the IBM SCSI. I followed all
>manual instructions but the first thing I noticed was that whichever RAM
>disk that I chose from BootX for the installation, the text installer
>came up instead of the graphical one. (At least the Red/Blue screens I
>saw were very different from the yellow/brown windows on the support
>site.) Anyway I went ahead and installed the default Home/Office
>install. At the end of the progress bar I was informed the installer
>found no network device, and so I hit the OK button. Then on to
>configuring the monitors.

>In Mac OS I ordinarily use 800x600 at 60Hz with this 6400's built-in
>video, /valkyrie is its chip as I've read elsewhere. This configuration,
>at least in the Mac OS, always gave me thousands of colours (16-bit
>video?) so I thought selecting that would be no problem,
>800x600/60Hz/16-bit. (I could not find my monitor in the list.) So then
>I come up to the part where it asks me to delete unused resolutions. Try
>as I might I couldn't figure out how to do this so I just selected the
>resolution I'd use, and continued. Then the installer told me it
>couldn't finish since no network device was installed. If I pressed
>cancel nothing happened, if I hit OK the installer quit.

>Now it gets interesting. I restart and as per manual to go BootX to
>uncheck RAM disk in Options, only for the fact that the RAM disk option
>is not checked in that window any longer. (?) So I hit cancel and then
>enter the /dev/sda6 configuration the installer informed me of and it
>looks like I am good to go to start up from the IBM SCSI. And it starts.
>And then I see the login: prompt... and then the screen blanks while
>starting up X Windows graphics... and then after two seconds I get the
>text again, which has several resolutions listed, all of which say they
>have failed.

>I tried running the X86Config and selected the desired resolution again.
>This failed when initiating startx, as well as a complete boot. So I
>installed again from the YDL CD. And I got the same thing I've detailed
>above. Does anybody have any ideas on this one? I have a spare graphics
>card, an ATI Rage128 Orion. I hadn't really wanted to use it for this
>but if it isn't possible to use thousands of colours with the standard
>video...

>Thanks for any help in advance.

>~Michael Alexander Owens

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13686"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 09:02:43 +0100
>From: Iain Stevenson <iain@IainStevenson.com>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <B7A7D432.9904%iain@IainStevenson.com>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Re: rpm failure

>I think you may need a newer version of rpm ...

> Iain

>on 20/8/01 11:46 pm, Murias O'Ceallagh at linux@dragonsblood.net wrote:

>> *This message was transferred with a trial version of CommuniGate(tm) Pro*
>> I tried to do a;
>> rpm --install --justdb kernel-2.4.8-0.4c.ppc.rpm
>>
>> and got;
>> only packages with major numbers <= 3 are supported by this version of RPM
>>
>> i have never seen this before. Anyone know what this means?
>>
>> Murias

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13687"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 14:58:58 +0100
>From: Bookem <bookem@totalise.co.uk>
>To: yellowdog-general <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <3BBF5329@mail.totalise.co.uk>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="ISO-8859-1"
>Content-Transfer-Encoding: 7bit
>Subject: RE: making Yaboot indefinite

>I can't seem to make it go beyond 30 seconds. Is there an option for making
>it stay at the yaboot prompt until I tell it which os to boot into? Sorry for
>being a bit dim.

>>===== Original Message From Dan Burcaw <dburcaw@terraplex.com> =====
>>There is a 'delay=' option
>>in your /etc/yaboot.conf file...
>>
>>
>>On Monday 20 August 2001 07:16, Bookem wrote:
>>> Is there any way to make yaboot stay at the os prompt indefinitely?
>>>
>>> Totalise - the Users ISP
>>>
>>> -----------------------
>>> The Totalise Email system, probably the most flexible email system in the
>>> world. To register for an account goto http://www.totalise.net
>>
>>--
>>
>>Regards,
>>Dan Burcaw
>>Terra Soft Solutions, Inc.

>Totalise - the Users ISP

>-----------------------
>The Totalise Email system, probably the most flexible email system in the
>world. To register for an account goto http://www.totalise.net

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13688"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 06:59:56 -0700
>Message-Id: <200108211359.f7LDxuU08702@superglide.netfx-2000.net>
>To: yellowdog-general@lists.yellowdoglinux.com
>From: spam_filter@linuxfreemail.com
>Subject: RE: making Yaboot indefinite

>>I can't seem to make it go beyond 30 seconds. Is there an option for making
>>it stay at the yaboot prompt until I tell it which os to boot into? Sorry for
>>being a bit dim.

>>>===== Original Message From Dan Burcaw <dburcaw@terraplex.com> =====
>>>There is a 'delay=' option
>>>in your /etc/yaboot.conf file...
>>>
>>>
>>>On Monday 20 August 2001 07:16, Bookem wrote:
>>>> Is there any way to make yaboot stay at the os prompt indefinitely?
>>>>
>>>> Totalise - the Users ISP
>>>>
>>>> -----------------------
>>>> The Totalise Email system, probably the most flexible email system in the
>>>> world. To register for an account goto http://www.totalise.net
>>>
>>>--
>>>
>>>Regards,
>>>Dan Burcaw
>>>Terra Soft Solutions, Inc.

>>Totalise - the Users ISP

>>-----------------------
>>The Totalise Email system, probably the most flexible email system in the
>>world. To register for an account goto http://www.totalise.net

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13690"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Message-ID: <3B82D2F8.C0E63CBE@risk2risk.com>
>Date: Tue, 21 Aug 2001 22:30:32 +0100
>From: Trevor Marshall <trevor@risk2risk.com>
>MIME-Version: 1.0
>To: "yellowdog-general@lists.yellowdoglinux.com"
> <yellowdog-general@lists.yellowdoglinux.com>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>Subject: mol on ydl kernel 2.4.4-1a

>Hiya all - decided that it was time to try 2.4 so took the quickest
>route for the first test and installed the yellowdog 2.4.4-1a off of the
>cd. Great kernel; now i need new mol.
>grabbed the 0.9.58 2.4 rpm from maconlinux.org, installed, reran the
>config. Now I get:

>[root@rose trevor]# startmol
>=================================================================
> Mac-on-Linux 0.9.58 <www.maconlinux.org>
> (C) 1997-2001 Samuel Rydh <samuel@ibrium.se>
>=================================================================

>Version 0.9.58
>Resource file: /etc/molrc
>Library directory: /usr/lib/mol
>SESSION 0
>lockfile /var/lock/mol-0
>OF device tree: oftrees/oftree.nw
>DEC frequency: 24 MHz, 249:10 mticks/usec
>128MB RAM mapped at 0x40000000
>Running in PowerPC G4 mode
>Using Linux keycodes
>Using nvram-image 'nvram/nvram.nw'
>Video module 'xvideo' installed.
>Running on VT 8.
>Using console mouse driver
>Cache enabled for console-video
>Video module 'console_video' installed.

>MODE: 640* 480, depth 8,15 { 0.0 } Hz
>MODE: 800* 600, depth 8,15 { 0.0 } Hz
>MODE: 1024* 768, depth 8,15 { 0.0 } Hz
>MODE: 1152* 768, depth 8,15,32 { 54.7 } Hz
>MODE: 1152* 864, depth 8,15 { 0.0 } Hz
>MODE: 1280*1024, depth 8,15 { 0.0 } Hz
>MODE: 1600*1200, depth 8,15 { 0.0 } Hz

>No video mode match the default one.
>Starting in video mode 640*480, depth 8, 0.0 Hz [offs:0, rb:640]
>Ethernet Interface (port 1) 'sheep-<eth0>' @ FE:FD:DE:AD:BE:EF

>HFS disk: 0 MB, images/moldisk.im [read-only]
>HFS disk: 18095 MB, /dev/hda [read-write] start: 1544,
>len: 37059709
>HFS disk: 32 MB, /dev/hda [read-write] start: 37061253,
>len: 65536

>newworld: elf32_getehdr failed
>cleaning up...
>Terminating threads...
>RVEC 00 NOP - : 0
>RVEC 01 Init - : 0
>RVEC 03 EnableFPU - : 0
>RVEC 06 Trace : 0
>RVEC 09 Soft ISI Trap : 0
>RVEC 10 Soft DSI Trap : 0
>RVEC 11 Alignment Trap : 0
>RVEC 13 SPR Read : 0
>RVEC 14 SPR Write : 0
>RVEC 15 Privileged Instruction : 0
>RVEC 16 Illegal Instruction : 0
>RVEC 17 Unusual Program Excep : 0
>RVEC 18 Altivec Unavail Trap : 0
>RVEC 19 Altivec Assist : 0
>RVEC 20 EnableAltivec - : 0
>RVEC 21 Exit - : 0
>RVEC 22 Interrupt : 0
>RVEC 23 OSI SysCall : 0
>RVEC 25 IO Read : 0
>RVEC 26 IO Write : 0
>RVEC 27 MSR POW (DOZE) : 0
>RVEC 28 Unusual DSISR Bits : 0
>RVEC 29 MMU IO Segment Access : 0
>RVEC 30 Internal Error : 0
>RVEC 31 Debugger : 0
>RVEC 32 Break : 0
>RVEC 33 Bad NIP : 0
>DONE

>anyone seen this before or successfully gotten mol working on a G4
>laptop with a 2.4 kernel?
>Maybe I should just build my own kernel?
>btw i tried building mol from source - same deal.

>cheers,
>-Trevor

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13691"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 14:56:19 -0700
>From: Mark Jaffe <wizards@wizdev.net>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <B7A82712.A168%wizards@wizdev.net>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Re: 2.4.x SMP kernels...

>On 8/20/01 8:22 PM, "Dan Burcaw" <dburcaw@terraplex.com> wrote:

>>
>>
>> Did you try the 2.4.8 (kernel-smp varient) kernel
>> that I posted earlier?
>>
>> ftp://ftp.penguinppc.org/users/dburcaw/kernel-2.4.8/
>>
>>
>> On Monday 20 August 2001 18:27, Mark Jaffe wrote:
>>> On 8/20/01 5:24 PM, "Dan Burcaw" <dburcaw@terraplex.com> wrote:
>>>> Probably within the week..
>>>
>>> Dan,
>>>
>>> Any updates on smp-2.4.x kernels? Where should I be looking? I still don't
>>> have one that will work on my dual-604e machine...
>>>
>>> Mark

>Dan,

>No, the 2.4.8-smp did NOT work. I now have a dead server at the co-lo and
>will need to go there and resurrect again :-(

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13693"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Message-ID: <3B82DB13.6AB2B34@risk2risk.com>
>Date: Tue, 21 Aug 2001 23:05:07 +0100
>From: Trevor Marshall <trevor@risk2risk.com>
>MIME-Version: 1.0
>To: yellowdog-general@lists.yellowdoglinux.com
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>Subject: Re: 2.4.x SMP kernels...

>Sympathies there - I hate a trip to the colo.

>Mark Jaffe wrote:
>>
>> On 8/20/01 8:22 PM, "Dan Burcaw" <dburcaw@terraplex.com> wrote:
>>
>> >
>> >
>> > Did you try the 2.4.8 (kernel-smp varient) kernel
>> > that I posted earlier?
>> >
>> > ftp://ftp.penguinppc.org/users/dburcaw/kernel-2.4.8/
>> >
>> >
>> > On Monday 20 August 2001 18:27, Mark Jaffe wrote:
>> >> On 8/20/01 5:24 PM, "Dan Burcaw" <dburcaw@terraplex.com> wrote:
>> >>> Probably within the week..
>> >>
>> >> Dan,
>> >>
>> >> Any updates on smp-2.4.x kernels? Where should I be looking? I still don't
>> >> have one that will work on my dual-604e machine...
>> >>
>> >> Mark
>>
>> Dan,
>>
>> No, the 2.4.8-smp did NOT work. I now have a dead server at the co-lo and
>> will need to go there and resurrect again :-(
>>
>> Mark
>> ============================================================
>> Mark Jaffe | (408) 972-9638 (home)
>> Chief Wizard | (408) 807-1530 (cell/page/voicemail)
>> Computer Wizards | (425) 795-6421 (FAX)
>> wizards@wizdev.net | http://www.wizdev.net/

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13692"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 17:04:20 -0500
>From: Robert Brandtjen <rob@prometheusmedia.com>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <B7A84513.9202%rob@prometheusmedia.com>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Good read

>http://arstechnica.com/reviews/01q3/metadata/metadata-1.html

> Robert Brandtjen
> --------------------------------------
> Web Site Creation and Hosting Services
> Hostmaster@prometheusmedia.com
> www.prometheusmedia.com

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13694"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Mime-Version: 1.0
>Message-Id: <a05101000b7a8946837c3@[192.168.1.2]>
>Date: Tue, 21 Aug 2001 17:44:03 -0500
>To: yellowdog-general@lists.yellowdoglinux.com
>From: Brian Watson <bcwatso1@uiuc.edu>
>Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>Subject: FTP Help

>I am still having a problem connecting to my ftp server from the
>internet. I connect, but then it tries to list files using its
>internal network IP. How can I force proftpd to return the external
>IP address, not the internal one? Thanks.

>--Brian

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13695"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 22:07:36 -0400
>From: mike <mike@mercuryrising.mine.nu>
>To: yellowdog general <yellowdog-general@lists.yellowdoglinux.com>,
> Darron Froese <darron@froese.org>
>Message-ID: <B7A88C28.4068%mike@mercuryrising.mine.nu>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Re: ProFTPD 1.2.2 (and ftp login problems)

>Darron,

>Thanks for the post. I have been tearing my hair out trying to get proftpd
>to accept even the simplest login requests. I was using version 1.2.0rc2
>from the yup update, and no matter what I tried I kept getting booted out
>for an incorrect password. Changing the PAM authorization had no effect
>(even though I can login with the same password just fine)...

>...after upgrading to the 1.2.2 version and using the very same proftpd
>config file, I was able to login on the first try!

>Thanks again.
>mike

>> From: Darron Froese <darron@froese.org>
>> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>> Date: Fri, 17 Aug 2001 14:58:07 -0600
>> To: <yellowdog-general@lists.yellowdoglinux.com>
>> Subject: ProFTPD 1.2.2
>>
>> Damn,
>>
>> The day after you make new RPMS - the final version comes out.
>>
>> <ftp://ftp.froese.org/rpms/ydl-2.0/proftpd/1.2.2/>
>>
>> There were a couple of people who did download the 1.2.2rc3 rpm's from me
>> last night/today - I would definitely recommend that that they upgrade to
>> this version.
>>
>> From the NEWS file:
>>
>> 1.2.2 - Released 08/17/2001
>> ---------------------------------
>> README.mod_sql update from author
>> new mod_sql from author
>> - Bug 1285 - Documentation updates
>> - Bug 1278 - pedantic fix to access_check()
>> - Bug 1266 - Use of APPEnd could corrupt files
>> - Bug 1286 - mod_ls displays set[ug]id bits
>> - Bug 1145 - DirFakeUser now applies to STAT
>> - Bug 1216 - xferlog man page update
>> - Bug 1111 - INSTALL update
>> - Bug 1262 - Doc update
>> - Bug 1217 - Doc update
>> - Bug 1187 - Upstream update to mod_quota
>> - Bug 1232 - UserOwner no longer performs chgrp
>> - Bug 1219 - compilation fix under gcc 3.0
>> - Bug 1230 - Portability fix for Sol 8 (sparcv9)
>> - Bug 1169 - Fix bug introduced by 1098, breaking DefaultRoot other
>> than "~*"
>> - Bug 1234 - ABOR now always returns 226 (as per RFC959)
>> - New mod_sql from upstream maintainer
>>
>> NOTE: There is a security issue with a particular version of mod_sql used by
>> ProFTPD (3.2.3) - it was not compiled into any of my RPMS so there shouldn't
>> be an issue. ProFTPD 1.2.2 final fixes that issue with a new version of
>> mod_sql (3.2.4).
>> --
>> Darron
>> darron@froese.org
>>

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13696"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 20:37:58 -0700 (PDT)
>From: "Paul J. Lucas" <pauljlucas@mac.com>
>To: yellowdog-general@lists.yellowdoglinux.com
>Message-ID: <Pine.LNX.4.21.0108212035110.16734-100000@oldmac.pauljlucas.org>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Subject: More frequent Powerbook wake-up failures

> I had upgraded from kernel 2.2.17 to 2.2.19 and everything
> seems to work fine. Under 2.2.17, my Lombard Powerbook failed
> to wake up about once every few months or so. Now, with
> 2.2.19, it's about once a week.

> Anybody else experience this? Know what the problem is? Or a
> solution?

> - Paul

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13697"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Mime-Version: 1.0
>Message-Id: <p05100325b7a8dbac6ae2@[216.254.74.21]>
>Date: Tue, 21 Aug 2001 23:57:06 -0400
>To: yellowdog-general@lists.yellowdoglinux.com
>From: Sam Moore <samiwas@macconnect.com>
>Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>Subject: [OT] Mailing list manager reco's?

>Hi folks.
>Just wondering if anyone has an opinion on EZMLM, Majordomo, Listar, etc.
>Must run on our favorite distro, of course :-)
>I've got ca. 100 people, three lists, dozen posts a day at present.
>Using PostFix as my MTA.
>Would be nice to hook it into my message board (phorum)...

>Any (civil) comments appreciated.
>TIA

>--
>Sam Moore <smoo@lungta.org>

>Personal: http://www.lungta.org (not ready yet)
>For the clan: http://smhtf.lungta.org
>Work: http://www.ewcreative.com

>"Good and bad, happy and sad, all thoughts vanish into
>emptiness like the imprint of a bird in the sky."

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13698"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Date: Tue, 21 Aug 2001 22:47:55 -0700
>From: Chuq Von Rospach <chuqui@plaidworks.com>
>To: <yellowdog-general@lists.yellowdoglinux.com>
>Message-ID: <B7A8959A.5150%chuqui@plaidworks.com>
>Mime-version: 1.0
>Content-type: text/plain; charset="US-ASCII"
>Content-transfer-encoding: 7bit
>Subject: Re: [OT] Mailing list manager reco's?

>On 8/21/01 8:57 PM, "Sam Moore" <samiwas@macconnect.com> wrote:

>> Hi folks.
>> Just wondering if anyone has an opinion on EZMLM, Majordomo, Listar, etc.
>> Must run on our favorite distro, of course :-)

>Mailman. EZMLM wants to run with qMail, I believe. If you run postfix, it
>won't be hugely happy. Majordomo has fallen way behind the technology curve.
>I wouldn't recommend anyone use it today. Listar is okay. Sympa is pretty
>good, too. Mailman is my favorite. It's only real weak spot, if you can call
>it that, is that it is written in python, which bothers some folks. 2.0 is
>quite good. 2.1 (in development) is going to amazingly kick butt.

>--
>Chuq Von Rospach, Internet Gnome <http://www.chuqui.com>
>[<chuqui@plaidworks.com> = <me@chuqui.com> = <chuq@apple.com>]
>Yes, yes, I've finally finished my home page. Lucky you.

>I recommend the handyman's secret weapon: duct tape.

>--fdnlkohfjjelbbkfbada
>Content-Type: message/rfc822
>Content-Disposition: inline; filename="yellowdog-general.13699"

>Reply-To: yellowdog-general@lists.yellowdoglinux.com
>Message-ID: <3B838900.7080705@drea.dnd.ca>
>Date: Wed, 22 Aug 2001 07:27:12 -0300
>From: Gavin Hemphill <hemphill@drea.dnd.ca>
>MIME-Version: 1.0
>To: yellowdog-general@lists.yellowdoglinux.com
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>Subject: Upgrading to 9.2 on a NW machine with YDL2.0 installed

>This is just a quick message for those of you who are about to upgrade
>your machines from 9.1 to 9.2.1. When you do this (I think it has
>something to do with the upgrade to the disk drivers) you'll find that
>your Boot partition suddenly gets mounted on the desktop and you can no
>longer boot into Linux. After a number of hours of hair pulling, I
>found that it is possible to recover without too much trouble. You will
>have to have a valid kernel for your machine in /boot/vmlinux for this
>to work. Here's what I did (note. this was with the text based installer):
>1) boot from the install CD and proceed through the install to the point
>that you can edit the partitions. (N.B. make sure you select the custom
>install when that question shows up).
>2) delete the Boot partition (In my case 35MB), and add it back in.
>3) proceed to the mount screen and mount the partitions (the defaults
>should be correct but you may want to check them).
>4) skip over the steps (down arrow key) until you get to the one to
>install the bootloader, and then do that one
>5) reboot and things should be happy.

>This will install the default yaboot.conf so you'll have to re-edit it
> and run ybin if you had modified it.
> G++

>--fdnlkohfjjelbbkfbada--

*** Your message did not reach its recipient ***
It was caught by the mailing system as spam.
If this message is not spam and you feel that
this message was caught in error, please email
a note to spam_filter@netfx-2000.net.
If this message is spam, knock it off!
This server is in California where it is illegal
to spam! We do not accept spam here!
We will go after all spammers to the maximum
extent of the law!

Next message: spam_filter@linuxfreemail.com: "Re: yellowdog-general Digest 22 Aug 2001 09:37:37 -0000 Issue 503"
Previous message: Gavin Hemphill: "Upgrading to 9.2 on a NW machine with YDL2.0 installed"

This archive was generated by hypermail 2a24 : Wed Aug 22 2001 - 03:37:39 MDT