Subject: Re: yellowdog-general Digest 4 Nov 2001 01:08:55 -0000 Issue 568
From: Ted Branscomb (tbranscomb@mosquitonet.com)
Date: Sun Nov 04 2001 - 03:26:04 MST
On Saturday, November 3, 2001, at 04:08 PM,
yellowdog-general-digest-help@lists.yellowdoglinux.com wrote:
>
> yellowdog-general Digest 4 Nov 2001 01:08:55 -0000 Issue 568
>
> Topics (messages 15529 through 15558):
>
> What's with the ISO?
> 15529 by: Bill Vinson <billvinson@mac.com>
> 15537 by: Christopher Murtagh <christopher.murtagh@mcgill.ca>
>
> modem on iBook2001
> 15530 by: Richard Weltman <richard.weltman@mcr1.poptel.org.uk>
> 15532 by: Charlie Watts <cewatts@frontier.net>
>
> Can't get YD 2.1 to install
> 15531 by: "nathan r. hruby" <nhruby@arches.uga.edu>
> 15541 by: "Nathan A. McQuillen" <nm@steaky.dhs.org>
> 15556 by: "Timothy A. Seufert" <tas@mindspring.com>
>
> X server screen resolution
> 15533 by: cbsled@ncia.net
>
> Partition's Data Region doesn't occupy the entire partition
> 15534 by: "Lucy L. Handfield" <lucy@abyssfx.com>
>
> Xserver issues - and - Where to find Linux documentation that doesn't
> suck?
> 15535 by: John Norair <jnorair@Princeton.EDU>
> 15539 by: andu <undo@cloud9.net>
> 15540 by: "nathan r. hruby" <nhruby@arches.uga.edu>
>
> jaz drive questions
> 15536 by: Mark Brethen <marbre@dhcp-159-66>
> 15538 by: "nathan r. hruby" <nhruby@arches.uga.edu>
> 15555 by: Mark Brethen <marbre@dhcp-159-66>
>
> YDL 2.1 will not boot on my iBook Dual USB (ISO Questions)
> 15542 by: Bo Brinkman <brinkman@cs.princeton.edu>
> 15552 by: Bill Fink <billfink@mindspring.com>
> 15553 by: Bo Brinkman <brinkman@cs.princeton.edu>
>
> [OT] Apple Store T-shirts
> 15543 by: Robert Brandtjen <rob@prometheusmedia.com>
> 15548 by: Brian Watson <bcwatso1@uiuc.edu>
>
> Easy way to set up Samba and NETATALK?
> 15544 by: Wes Plate <wes@plate.net>
> 15545 by: "Darron Froese" <darron@froese.org>
> 15546 by: "Nathan A. McQuillen" <nm@steaky.dhs.org>
> 15554 by: "Timothy A. Seufert" <tas@mindspring.com>
>
> ppp and the 2.4.x kernels
> 15547 by: Pat Plummer <ppat@fmtc.com>
>
> 2.1 .iso
> 15549 by: A Maloney <amaloney@twcny.rr.com>
>
> Powerbook G4 rev. 2 (550MHz) problems with X
> 15550 by: Winston Chang <winston@stdout.org>
>
> wallstreet/lombard question
> 15551 by: Ron Smith <ronsmith28@home.com>
>
> Saga of yup update (sortof) from YDL 2.0 to 2.1
> 15557 by: Bill Fink <billfink@mindspring.com>
>
> 2 simple ?s -- smtp configuration, Open Office install
> 15558 by: Marc Stergionis <stermarc@home.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
>
>
> ----------------------------------------------------------------------
> From: Bill Vinson <billvinson@mac.com>
> Date: Sat Nov 03, 2001 03:39:53 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: What's with the ISO?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> No, not for me as I found it on iBiblio at 677+ megs earlier and the
> md5sum was right. It has now been resynced with yellowdog and is only
> 18 megs. Don't know what happened, but I don't think this is the
> problem I am having.
>
> Thanks,
> Bill
>
> On Saturday, November 3, 2001, at 12:54 AM, Ronald Hale-Evans wrote:
>
>> On Fri, Nov 02, 2001 at 09:23:52PM -0800, Timothy A. Seufert wrote:
>>> At 8:57 PM -0800 11/2/01, Ronald Hale-Evans wrote:
>>>
>>> [snip tale of woe]
>>>
>>>> And another thing: why is the disk image only 18 megs long? The 2.0
>>>> image was almost 700 megs, as you would expect. Have compression
>>>> techniques _really_ gotten that good in the past few months, or did
>>>> somebody screw up somewhere?
>>>
>>> Clearly the image got truncated somewhere along the line. I wouldn't
>>> even bother trying to burn it if it's only 18 megs.
>>> --
>>> Tim Seufert
>>
>> Well, I'm guessing that's the problem everyone else is having with it
>> then...
>>
>> --
>> Ron Hale-Evans ... rwhe@ludism.org & rwhe@apocalypse.org
>> Center for Ludic Synergy, Seattle Cosmic Game Night,
>> Kennexions Glass Bead Game & Positive Revolution FAQ:
>> http://www.ludism.org/
>> Home page & Hexagram-8 I Ching Mailing List:
>> http://www.apocalypse.org/~rwhe/
>> == You meet the most interesting people when you're a solipsist. ==
>
> From: Christopher Murtagh <christopher.murtagh@mcgill.ca>
> Date: Sat Nov 03, 2001 08:29:50 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: What's with the ISO?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Sat, 3 Nov 2001, Bill Vinson wrote:
>> No, not for me as I found it on iBiblio at 677+ megs earlier and the
>> md5sum was right. It has now been resynced with yellowdog and is only
>> 18 megs. Don't know what happened, but I don't think this is the
>> problem I am having.
>
> Well, I've been trying to rsync YDL so that I could take a load off
> their
> server and mirror it on mine. rsync would barf every time it got to the
> fuji install ISO. So, I manually ftp'd it and excluded it from the
> rsync,
> afterwards rsync barfed on:
>
> yellowdog-2.0/ppc/install/x11fs.image
> unexpected tag 92
> unexpected EOF in read_timeout
>
> Looks like there is a data problem on their server.
>
> I'll try to burn the ISO I managed to ftp, and see if it works. If so,
> I'll setup links to the mirror on my server. If not, I'll wait until it
> is
> fixed by Terra Soft.
>
> Cheers,
>
> Chris
>
>
> --
>
> Christopher Murtagh
> Webmaster / Sysadmin
> Web Communications Group
> McGill University
> Montreal, Quebec
> Canada
>
> Tel.: (514) 398-3122
> Fax: (514) 398-2017
>
>
> From: Richard Weltman <richard.weltman@mcr1.poptel.org.uk>
> Date: Sat Nov 03, 2001 04:33:16 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: modem on iBook2001
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> please, can anyone offer some advice on this ?
>
> I'm new to linux, and don't really know where
> to start with it. I think what would help would
> be to know whether it's a problem with YDL on
> iBooks, or a straightfoward getting-a-modem-to-work-
> with-linux thing. RTFMs gratefully received !
>
> thanks
> Richard
>
>> hi - is anyone on the list successfully using the iBook2001 for
>> dial-up ppp using the internal modem - is there a trick to it ?
>>
>>
>> wvdialconf eventually locks up the machine after scanning ttyS1:
>>
>> Scanning serial ports for a modem
>>
>> ttyS0<*1>: ATQ0 ...<snip>... -- nothing
>> ttyS1<*1>: ATQ0 ...<snip>... -- nothing
>> Machine check in kernel mode
>> caused by ( from SRR1=41030 ): Transfer error ack signal
>>
>>
>> and I think this is output from the debugger (?):
>>
>> vector:200 at pc = d993a004, lr = d993eb78, msr = 41030, sp =
>> d19d1cb0 [d191d1c00]
>> current = d19d0000, pid = 615, comm = modprobe
>>
>>
>> this iBook is triple booting MacOS 9.2.1, OS X 10.1, YDL 2.1 kernel
>> 2.4.10,
>> and I'm using OS X most of the time - including ppp via the internal
>> modem,
>> which works fine.
>
> From: Charlie Watts <cewatts@frontier.net>
> Date: Sat Nov 03, 2001 05:24:14 AM America/Anchorage
> To: "yellowdog-general@lists.yellowdoglinux.com" <yellowdog-
> general@lists.yellowdoglinux.com>
> Subject: Re: modem on iBook2001
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Sat, 3 Nov 2001, Richard Weltman wrote:
>
>> I'm new to linux, and don't really know where
>> to start with it. I think what would help would
>> be to know whether it's a problem with YDL on
>> iBooks, or a straightfoward getting-a-modem-to-work-
>> with-linux thing. RTFMs gratefully received !
>
> It's a particular problem to the iBook 2001.
>
> Now - I don't know about why it it is LOCKING UP. I do know that I've
> gotten my modem to work in my iBook 2001.
>
> The big secret is to set the modem volume to OFF.
>
> You'll probably have to wait for somebody else with 2.1 and a YDL kernel
> to confirm whether or not theirs is crashing.
>
> --
> Charlie Watts
> cewatts@frontier.net
> Frontier Internet, Inc.
> http://www.frontier.net/
>
>
> From: "nathan r. hruby" <nhruby@arches.uga.edu>
> Date: Sat Nov 03, 2001 05:07:52 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Can't get YD 2.1 to install
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Sat, 3 Nov 2001, Nathan A. McQuillen wrote:
>
>>
>> Except for that little Ethernet problem. :)
>>
>
> The win2k one or the g4 one?
>
> g4 problem was solved with a the latest firmware / opentransport update.
>
> I agree about 10X, except I like glowing things (but I miss spring
> loaded
> folders and window shading
>
> -n
> --
> ......
> nathan hruby - nhruby@arches.uga.edu
> computer support specialist
> department of drama and theatre
> http://www.drama.uga.edu/
> ......
>
>
> From: "Nathan A. McQuillen" <nm@steaky.dhs.org>
> Date: Sat Nov 03, 2001 09:51:48 AM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Re: Can't get YD 2.1 to install
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
>
> N,
>
> Ethernet problem is YDL on my beige G3. I don't have time right this
> minute to elaborate on the problem but point is I was using a Farallon
> 10/100 card before I upgraded the kernel and now it doesn't work. Not a
> big deal but it's a bit frustrating -- I believe I was using a 3c509
> driver before but again I don't recall exactly and I'll have to do a
> little more research and get back to you.
>
> - N.
>
> PS - I like the glowing things too, but not when they're eating
> processor
> cycles that could be spent giving me my *$&%^ console. I'm sure 10.1 is
> much better. :P
>
>
>>>
>>> Except for that little Ethernet problem. :)
>>>
>>
>> The win2k one or the g4 one?
>>
>> g4 problem was solved with a the latest firmware / opentransport
>> update.
>>
>> I agree about 10X, except I like glowing things (but I miss spring
>> loaded
>> folders and window shading
>>
>> -n
>
> From: "Timothy A. Seufert" <tas@mindspring.com>
> Date: Sat Nov 03, 2001 02:34:45 PM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Can't get YD 2.1 to install
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
>> Speaking of partitioning, I would also /really/ try to avoid using a
>> split
>> disk, like you say you are. I don't really know if this makes
>> theoretical
>> sense, but in my experience, using a dual partitioned disk one seems to
>> run into issues with the Mac driver,
>
> Linux doesn't care about the Mac drivers, they're just extra partitions
> it isn't using.
>
>> potential bad blocks that Linux can't
>> tinker with, etc.
>
> Having Mac driver and data partitions cannot interfere with bad block
> remapping in Linux. That's done within the Linux ext2 filesystem
> structures, not in the partition tables.
>
> I have been using Linux on PowerMacs for a long time (since before
> there were any real distributions) and have never needed to keep Mac
> partitions on separate disks. The only real pitfall I know of is if
> you try to have too many partitions -- as I recall there is supposed to
> be a limit of 16 partitions per block device in Linux, but I've never
> run into it.
> -- Tim Seufert
> From: cbsled@ncia.net
> Date: Sat Nov 03, 2001 05:12:58 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: X server screen resolution
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On 11/02/01, at 08:52 PM, Jim Cole <greyleaf@yggdrasill.net> said:
>
>> Granted, Linux documentation is definitely not as user-friendly
>> and convenient as some other types; but in terms of detail and
>> completeness, it is outstanding.
>
> Unless you are running something other than "a very plain-and-simple
> x86". I have been frustrated several times by misleading or nonexistant
> documentation with "fringe" distros like LinuxPPC and YDL. I understand
> why this has happened, but that doesn't get my system running.
>
> A case in point is PCMCIA support in YDL. It's there, but the
> installation doesn't set it up, so it must be done manually. You won't
> hear me gripe about that, I've been around Linux long enough to expect
> that sort of thing, especially on a system as unusual as a Linux
> Powerbook. Unfortunately, the only documentation with the package is
> written for a compile/install on an x86, has little relevance to a
> binary install on a Powerbook, and some of it is just plain wrong in
> this admittedly special case.
>
> We must remember that all Linux documentation is, like Linux and all
> its programs, written by the users. John, if you find an incomplete or
> misleading doc, one of your options is to figure out the problem, fix
> it, then write a How-To for the YDL web site. Then you will stop being
> part of the problem and become part of the solution.
>
> --
> -----------------------------------------------------------
> Carl Brown cbsled@ncia.net
> -----------------------------------------------------------
> We are Linux.
> Resistance is an indication that you missed the point.
> -Brandon S. Allbery
> From: "Lucy L. Handfield" <lucy@abyssfx.com>
> Date: Sat Nov 03, 2001 06:30:02 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Partition's Data Region doesn't occupy the entire
> partition
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> >All goes well until I get to the "edit partitions" step in the
> install. At
> >this point, I get:
> >
> >Error: The partition's data region doesn't occupy the entire partition.
>
> I know the original message for this subject was months ago, but I had
> the same problem while trying to install YDL 2.0 on my PowerMac 720/120
> while running MacOS 7.5. After a lot of frustration, I found that the
> problem went away after I installed 9.0. (Then I had to deal with my
> miniscule hard drive...)
>
> --
> http://www.morgi.net
> From: John Norair <jnorair@Princeton.EDU>
> Date: Sat Nov 03, 2001 08:09:03 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Xserver issues - and - Where to find Linux documentation that
> doesn't suck?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> Xserver part:
> Getting the XServer to work: it says no display found, where do I fix
> that?
>
> I have posted this before. I'm just going to toss it up again to see
> if anyone bites.
>
> Where is Linux documentation + unfortunate, subconsciously induced rant.
>
> My biggest problem with Linux is that it has no corporate entity that's
> really behind it, so there's no be-all/end-all documentation. It seems
> to me that the Linux user base learns and passes on knowledge through a
> verbal system more appropriate for tribal groups like Free Masons and
> Navajo. I have read quite a few "Linux Docs" (a lot) and I find them
> very unfulfilling. Where do you find this great Linux documentation?
> I suppose I could buy support from TerraSoft, but at this point I won't
> pay a cent for YDL: In terms of opportunity cost it has already cost
> thousands of dollars.
>
> I'm stuck in this bad situation, where I know quite a bit about what's
> going wrong - more than anyone I've encountered - but it's not enough
> to solve the problem. This is where it would be very nice to have
> explicit corporate documentation.
>
> Considering the time I have put into trying to get my system to work, I
> probably could have rewritten enough parts of the kernel source to
> force the damn thing to work. So please, if anyone has any idea where
> to find detailed documentation that explain how to fix it that doesn't
> ramble on about what's going on (I know what's going on), I'd be much
> obliged.
>
> Thanks,
> John Norair
>
> From: andu <undo@cloud9.net>
> Date: Sat Nov 03, 2001 08:48:40 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Xserver issues - and - Where to find Linux documentation
> that doesn't suck?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> John Norair wrote:
>>
>> Xserver part:
>> Getting the XServer to work: it says no display found, where do I fix
>> that?
>
> Sounds to me like an XFree86 4.x issue so you need to check the
> XF86Config file. This is what I have on my PC Linux which I'm in right
> now, but it should make no difference:
>
> Section "ServerLayout"
> Identifier "XFree86 Configured"
> Screen 0 "Screen0" 0 0
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
> RgbPath "/usr/X11R6/lib/X11/rgb"
> ModulePath "/usr/X11R6/lib/modules"
> FontPath "/usr/X11R6/lib/X11/fonts/misc/"
> FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
> FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
> FontPath "/usr/X11R6/lib/X11/fonts/CID/"
> FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
> FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
> EndSection
>
> Section "Module"
> Load "pex5"
> Load "type1"
> Load "freetype"
> Load "record"
> Load "extmod"
> Load "dbe"
> Load "dri"
> Load "glx"
> Load "xie"
> EndSection
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "keyboard"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "IMPS/2"
> Option "Device" "/dev/input/mice"
> EndSection
>
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "APP"
> ModelName "AppleStudio"
> HorizSync 31.0 - 56.5
> VertRefresh 56.0 - 76.0
> EndSection
>
> Section "Device"
> ### Available Driver options are:-
> ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
> ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
> ### [arg]: arg optional
> #Option "accel" # [<bool>]
> #Option "crt_screen" # [<bool>]
> #Option "composite_sync" # [<bool>]
> #Option "hw_cursor" # [<bool>]
> #Option "linear" # [<bool>]
> #Option "mmio_cache" # [<bool>]
> #Option "probe_clocks" # [<bool>]
> #Option "reference_clock" # <freq>
> #Option "shadow_fb" # [<bool>]
> #Option "sw_cursor" # [<bool>]
> Identifier "Card0"
> Driver "ati"
> VendorName "ATI"
> BoardName "Mach64 GB"
> ChipSet "ati"
> ChipId 0x4742
> ChipRev 0x5c
> BusID "PCI:1:0:0"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "Card0"
> Monitor "Monitor0"
> DefaultDepth 24
> SubSection "Display"
> Depth 1
> EndSubSection
> SubSection "Display"
> Depth 4
> EndSubSection
> SubSection "Display"
> Depth 8
> EndSubSection
> SubSection "Display"
> Depth 15
> EndSubSection
> SubSection "Display"
> Depth 16
> EndSubSection
> SubSection "Display"
> Depth 24
> EndSubSection
> EndSection
>
>
>
>>
>> I have posted this before. I'm just going to toss it up again to see
>> if
>> anyone bites.
>>
>> Where is Linux documentation + unfortunate, subconsciously induced
>> rant.
>>
>> My biggest problem with Linux is that it has no corporate entity that's
>> really behind it, so there's no be-all/end-all documentation. It seems
>> to me that the Linux user base learns and passes on knowledge through a
>> verbal system more appropriate for tribal groups like Free Masons and
>> Navajo.
>
> Couldn't have said it better, but I for one would rather interact with a
> tribal environment for 1000 years then a corporate one for 1 hour. Just
> look around at what you *really* get from corporate backed entities.
>
>> I have read quite a few "Linux Docs" (a lot) and I find them
>> very unfulfilling. Where do you find this great Linux
>> documentation? I
>> suppose I could buy support from TerraSoft, but at this point I won't
>> pay a cent for YDL: In terms of opportunity cost it has already cost
>> thousands of dollars.
>>
>> I'm stuck in this bad situation, where I know quite a bit about what's
>> going wrong - more than anyone I've encountered - but it's not enough
>> to
>> solve the problem. This is where it would be very nice to have
>> explicit
>> corporate documentation.
>>
>> Considering the time I have put into trying to get my system to work, I
>> probably could have rewritten enough parts of the kernel source to
>> force
>> the damn thing to work. So please, if anyone has any idea where to
>> find
>> detailed documentation that explain how to fix it that doesn't ramble
>> on
>> about what's going on (I know what's going on), I'd be much obliged.
>>
>> Thanks,
>> John Norair
>
> Andu
> From: "nathan r. hruby" <nhruby@arches.uga.edu>
> Date: Sat Nov 03, 2001 09:03:21 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Xserver issues - and - Where to find Linux documentation
> that doesn't suck?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Sat, 3 Nov 2001, John Norair wrote:
>
>> Xserver part:
>> Getting the XServer to work: it says no display found, where do I fix
>> that?
>>
>
> /etc/X11/XF86Config From reading the below, you already know what's
> going
> on, so I don't need to go any further :) The "No Display found" error
> is fairly common and therefore is pointless to post without the entire
> output of X's startup, please try posting that and we'll see what we can
> do.
>
>> I have posted this before. I'm just going to toss it up again to see
>> if
>> anyone bites.
>
> If the above, I bit. If the below, I bit too, but trolling for flame
> wars
> will not get you any more help from me.
>
>>
>> Where is Linux documentation + unfortunate, subconsciously induced
>> rant.
>>
>
> To name a few:
> http://www.ibiblo.org/
> http://www.linuxdoc.org/
> http://www.linux.com # Some repetion here, but also some good articles
> http://www.google.com/linux/
> http://www.linuxjournal.com/
> http://www.sysadmin.com/
> irc://irc.openprojects.net/
>
> Professionial support can be purchased from:
> http://www.redhat.com/
> http://www.yellowdoglinux.com/
> http://www.linuxcare.com/
>
> # Vendor specfic support
> http://www.dell.com/linux/
> http://www.mklinux.com/ (Former Apple linux project)
> Compaq / HP have some as does IBM, but I am not too familiar with it and
> don't know the URL's off the top of my head.
>
> # Also, pretty much every app has a mailing lsit with searchable
> archives.
>
>> My biggest problem with Linux is that it has no corporate entity that's
>> really behind it, so there's no be-all/end-all documentation.
>
> Actaully, linux documentation seems the most complete of all of the
> OS's I
> support on a daily basis. It certianly better than MS's standard "talk
> to
> your system or network administrator" and linux docs are a hell of a lot
> easier to find then MS's or Apples stupid kbases. (I miss the TIL) It
> requires some addtional searching, but what problem doesn't? IS there a
> difference between using Google to find the answer to your question
> rather
> thatn the MSFT or APPL search engines for their sites?
>
>> It seems
>> to me that the Linux user base learns and passes on knowledge through a
>> verbal system more appropriate for tribal groups like Free Masons and
>> Navajo.
>
> And Microsoft's standard "Talk to your nearest MSCE" answer isn't? The
> number of times MS's docs have told me to go "talk" to someone is
> austounding. If I ever meet this "someone," whomever he / she is, I'm
> going to wring their necks! ;-)
>
>> I have read quite a few "Linux Docs" (a lot) and I find them
>> very unfulfilling.
>
> It's typically served over a bed of wild long grain rice with a side of
> sardines. Penguins like sardines. ;-)
>
>> Where do you find this great Linux documentation? I
>> suppose I could buy support from TerraSoft, but at this point I won't
>> pay a cent for YDL: In terms of opportunity cost it has already cost
>> thousands of dollars.
>>
>
> I must not have caught all your previous threads.. How has it already
> cost
> you thousands? Time, CD's, bandwidth, brain power, hassle? There's a
> posint where you have to remain committed or give it up. You seem to
> have
> crossed that point into the land of no return, so why fight it?
>
>> I'm stuck in this bad situation, where I know quite a bit about what's
>> going wrong - more than anyone I've encountered - but it's not enough
>> to
>> solve the problem. This is where it would be very nice to have
>> explicit
>> corporate documentation.
>>
>
> Umm.. you have better, the source (which is fairly well commented). If
> you know more about the problem then anyone else, you are in the best
> postion to fix it. (and write a HOWTO for YDL and get a T-Shirt.. See
> linux is already starting to pay off!)
>
> XF86 Config can be put on the list of black arts with SCSI termination
> and
> MS SMB Domain Controllers. It's easy to get daunted, but XFree really
> has
> some of the best documentation becasue of this. Look in
> /usr/X11R6/lib/X11 and /usr/X11R6/share/Xconfigurator for some sample
> configs, and lists of know working monitors and video display adapters
> (with recommended configs) http://www.cfree86.org/ also has docs.
>
>> Considering the time I have put into trying to get my system to work, I
>> probably could have rewritten enough parts of the kernel source to
>> force
>> the damn thing to work. So please, if anyone has any idea where to
>> find
>> detailed documentation that explain how to fix it that doesn't ramble
>> on
>> about what's going on (I know what's going on), I'd be much obliged.
>>
>
> Hmm.. I don't really want to fan the flames, but.. uhh.. if you're so
> talented as to be able to rewrite parts of the kernel to solve your
> problem one would think XF86 configuration wouldn't be too difficlut.
>
> -n
> --
> ......
> nathan hruby - nhruby@arches.uga.edu
> computer support specialist
> department of drama and theatre
> http://www.drama.uga.edu/
> ......
>
>
> From: Mark Brethen <marbre@dhcp-159-66>
> Date: Sat Nov 03, 2001 08:23:01 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: jaz drive questions
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> I have a couple questions about the jaz drive in my beige G3:
>
> 1) Can I format jaz disks from within linux (i.e. 'ext2' format).
>
> 2) If I have both hfs and ext2 formatted disks, how do I set-up fstab to
> mount either? I put the following line in fstab, which works for hsf
> disks
> only:
>
> /dev/sdc /mnt/jaz hfs
> noauto,rw,user 0 0
>
> I didn't find an answer in the manual pages.
> --
>
> Mark Brethen
> mbrethen@rochester.rr.com
> From: "nathan r. hruby" <nhruby@arches.uga.edu>
> Date: Sat Nov 03, 2001 08:30:56 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: jaz drive questions
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Sat, 3 Nov 2001, Mark Brethen wrote:
>
>> I have a couple questions about the jaz drive in my beige G3:
>>
>> 1) Can I format jaz disks from within linux (i.e. 'ext2' format).
>>
>
> Yes, same as any other disk.
>
>> 2) If I have both hfs and ext2 formatted disks, how do I set-up fstab
>> to
>> mount either? I put the following line in fstab, which works for hsf
>> disks
>> only:
>>
>> /dev/sdc /mnt/jaz hfs
>> noauto,rw,user 0 0
>>
>
> # You can use any mount points you'd like, these are for ease for my
> poor
> # addled mind sometimes
> /dev/sdc /mnt/jaz/hfs hfs noauto,rw,user 0 0
> /dev/sdc /mnt/jaz/ext2 ext2 noauto,rw,user 0 0
> /dev/sdc /mnt/jaz/dos msdos noauto,rw,user 0 0
>
> # mount the ext2 partition on the Jaz
> mount /mnt/jaz/ext2
>
> # mount the hfs partition on the Jaz
> mount /mnt/jaz/hfs
>
> Etc....
>
> Also look into autofs (man autofs should tell you everything you need to
> know), which will automatically mount the drive whenever you use it,
> useful if you're flipping Jaz carts around a lot. Less load then the
> tradtional amd. It's easy to setup and should be compiled into the
> kernel
> already. Also handy for floppies :)
>
> -n
> --
>
> ......
> nathan hruby - nhruby@arches.uga.edu
> computer support specialist
> department of drama and theatre
> http://www.drama.uga.edu/
> ......
>
>
> From: Mark Brethen <marbre@dhcp-159-66>
> Date: Sat Nov 03, 2001 02:24:16 PM America/Anchorage
> To: nhruby@arches.uga.edu
> Cc: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: jaz drive questions
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Saturday 03 November 2001 12:30, nathan hruby wrote:
>
>> # You can use any mount points you'd like, these are for ease for my
>> poor
>> # addled mind sometimes
>> /dev/sdc /mnt/jaz/hfs hfs noauto,rw,user 0 0
>> /dev/sdc /mnt/jaz/ext2 ext2 noauto,rw,user 0 0
>> /dev/sdc /mnt/jaz/dos msdos noauto,rw,user 0 0
>>
>> # mount the ext2 partition on the Jaz
>> mount /mnt/jaz/ext2
>>
>> # mount the hfs partition on the Jaz
>> mount /mnt/jaz/hfs
>>
>> Etc....
>
> Thanks, that does it. However, when I try to eject a disk using 'eject
> /mnt/jaz/hfs', I get the following response:
>
> eject: unable to eject, last error: Inappropriate ioctl for device
>
> using 'eject /dev/sdc' I get:
>
> eject: unable to find or open device for: `/dev/sdc'
>
> any thoughts on this? The manual entry says that if eject does not
> work, it
> is most likely a limitation of the kernel driver for the device and not
> the
> eject program itself.
>
>> Also look into autofs (man autofs should tell you everything you need
>> to
>> know), which will automatically mount the drive whenever you use it,
>> useful if you're flipping Jaz carts around a lot. Less load then the
>> tradtional amd. It's easy to setup and should be compiled into the
>> kernel
>> already. Also handy for floppies :)
>>
>> -n
>
> I dont have a manual entry for autofs. What now?
> --
>
> Mark Brethen
> mbrethen@rochester.rr.com
> From: Bo Brinkman <brinkman@cs.princeton.edu>
> Date: Sat Nov 03, 2001 10:06:35 AM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: YDL 2.1 will not boot on my iBook Dual USB (ISO Questions)
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> I can confirm similar problems on my iBook SE (Firewire). I downloaded
> the iso, checked the md5sum, and burnt it with xcdroast. It cannot be
> recognized by OSX. I followed the exact same process which worked fine
> for YDL 2.0. Has anyone actually burned the 2.1 ISO and had it work? So
> far I actually haven't heard any successes. I got my iso from the psu
> mirror.
>
> -- William "Bo" Brinkman
> brinkman@cs.princeton.edu
> Princeton Computer Science http://www.derandomized.org/
> -- It is inferior for coffee, but it is a pretty fair tea. -- Mark Twain
>
> From: Bill Fink <billfink@mindspring.com>
> Date: Sat Nov 03, 2001 01:45:55 PM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Cc: Bill Fink <billfink@mindspring.com>, <brinkman@cs.princeton.edu>
> Subject: Re: YDL 2.1 will not boot on my iBook Dual USB (ISO Questions)
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On Sat Nov 03 2001, Bo Brinkman wrote:
>
>> I can confirm similar problems on my iBook SE (Firewire). I downloaded
>> the iso, checked the md5sum, and burnt it with xcdroast. It cannot be
>> recognized by OSX. I followed the exact same process which worked fine
>> for YDL 2.0. Has anyone actually burned the 2.1 ISO and had it work? So
>> far I actually haven't heard any successes. I got my iso from the psu
>> mirror.
>
> Hi Bo,
>
> I can confirm that the fuji 2.1 ISO on ftp.yellowdoglinux.com was
> only 18 MB previously and is only 52 MB now. There are also no 2.1
> RPMS on ftp.yellowdoglinux.com. However, working with a friend, we
> downloaded the fuji 2.1 ISO from ftp.ibiblio.org which was the full
> size (the 2.1 RPMS were also all out there), and verified the md5sum.
>
> My friend burned a CD using toast with disk image format. It is
> essential that the ISO has never ever been mounted because this will
> munge the file system structure from then on. The safest thing is
> to lock the ISO image to prevent it from ever being accidentally
> changed in any way.
>
> We then successfully installed YDL 2.1 on a G4 using this CD. So I
> can verify the veracity of the full fuji 2.1 ISO image if you have
> verfied its md5sum, but I can't say anything about the ability to
> successfully burn a CD using cdroast, but it worked fine with Toast.
>
> One other thing to mention is that you need a large enough capacity
> blank CD to hold the ISO image (unfortunately I don't recall the exact
> capacity required at the moment, but it obviously needs to be large
> enough to hold at least 677505024 bytes of data).
>
> -Hope this helps
>
> -Bill
>
> From: Bo Brinkman <brinkman@cs.princeton.edu>
> Date: Sat Nov 03, 2001 01:49:54 PM America/Anchorage
> To: Bill Fink <billfink@mindspring.com>
> Cc: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: YDL 2.1 will not boot on my iBook Dual USB (ISO Questions)
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
>> I can confirm that the fuji 2.1 ISO on ftp.yellowdoglinux.com was
>> only 18 MB previously and is only 52 MB now. There are also no 2.1
>> RPMS on ftp.yellowdoglinux.com. However, working with a friend, we
>> downloaded the fuji 2.1 ISO from ftp.ibiblio.org which was the full
>> size (the 2.1 RPMS were also all out there), and verified the md5sum.
>
>
> The psu mirror has the complete iso, and the md5sum checks, as I said
> before, so this is not my problem.
>
> <snip advice>
>
>
> Yes, I know that these are the most common newbie problems. I don't
> think that I fell into any of these traps though. :) I have been using
> YDL since 1.2.1, and have not had any problems in the past of this
> sort. I certainly don't use MacOS to burn CDs, so that should not be a
> problem.
>
> One thing about my setup: I have OS X.1 and 9.2.1 installed on my
> machine. Is it possible that something changed in open firmware or the
> disk drivers?
>
> Could people please email me 1) Whether or not they have had success
> with a burned 2.1 and 2) What the latest version of MacOS they had
> installed was?
>
> I'm grasping at straws, but I thought about the usual problems, and I
> don't seem to have any of them. :(
>
> -- William "Bo" Brinkman
> brinkman@cs.princeton.edu
> Princeton Computer Science http://www.derandomized.org/
> -- I do not avoid women Mandrake, but I do deny them my essence.
> --General Jack D. Ripper, from Doctor Strangelove
>
> From: Robert Brandtjen <rob@prometheusmedia.com>
> Date: Sat Nov 03, 2001 10:23:19 AM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Re: [OT] Apple Store T-shirts
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> on 11/2/01 10:09 AM, Brian Watson at bcwatso1@uiuc.edu wrote:
>
>> If any of you have been to Apple Store openings and have a spare
>> t-shirt
>> (tube preferred but without tube still fine) that you would like to
>> sell,
>> please mail me off list. Thank you.
>>
>> --Brian
> As I live near the famed Mall of America, which has an Apple Store, I
> could
> be persuaded to get them from there.......
>
> Robert Brandtjen
> --------------------------------------
> Web Site Creation and Hosting Services
> Hostmaster@prometheusmedia.com
> www.prometheusmedia.com
>
> From: Brian Watson <bcwatso1@uiuc.edu>
> Date: Sat Nov 03, 2001 12:34:40 PM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Re: [OT] Apple Store T-shirts
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On 11/3/01 1:23 PM, "Robert Brandtjen" <rob@prometheusmedia.com> wrote:
>
>>> If any of you have been to Apple Store openings and have a spare
>>> t-shirt
>>> (tube preferred but without tube still fine) that you would like to
>>> sell,
>>> please mail me off list. Thank you.
>>>
>>> --Brian
>> As I live near the famed Mall of America, which has an Apple Store, I
>> could
>> be persuaded to get them from there.......
>
> They're probably all out now. :(
>
> --Brian
>
> From: Wes Plate <wes@plate.net>
> Date: Sat Nov 03, 2001 11:07:55 AM America/Anchorage
> To: YellowDog list <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Re: Easy way to set up Samba and NETATALK?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> On 10/28/01 2:35 PM,
> "yellowdog-general-digest-help@lists.yellowdoglinux.com" wrote:
>
>>
>>> Second, if they're not installed, is there an easy method for getting
>>> these
>>> services up and running? If not, I can hire my UNIX-savvy father to
>>> do the
>>> installs for me, but I'd prefer not to.
>>
>> Mount the YDL CD, install the Samba and netatalk RPMs. As root in
>> the directory containing RPMs on the CD:
>>
>> rpm -Uvh samba-1.x.x.ppc.rpm
>>
>> (substitute the real name of course -- you'll have to go through the
>> directory and find the relevant RPMs)
>>
>> If you run into dependency errors, you'll have to install any RPMs
>> needed to satisfy them. You can usually figure out what needs to get
>> installed from the error.
>
> Thanks.
>
> We realized that for now, Netatalk would be fine. Samba doesn't have to
> happen yet.
>
> But we're having a BEAR of a time getting it running. Even my father,
> who
> knows UNIX like nobody's business finally threw up his hands.
>
> I've done many Google searches, and good HOW-TO INSTALL documentation
> seems
> to be very elusive.
>
> Anyone know of a good document explaining how to get netatalk up and
> running
> on YellowDog 2?
>
>
> --
> Wes Plate
> Automatic Duck, Inc.
> http://www.wesplate.com
> http://www.automaticduck.com
>
> Import OMF Compositions into After Effects 5.0. Really.
> http://www.automaticduck.com/products/index.html
>
> From: "Darron Froese" <darron@froese.org>
> Date: Sat Nov 03, 2001 12:00:44 PM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Re: Easy way to set up Samba and NETATALK?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
>> Anyone know of a good document explaining how to get netatalk up and
> running
>> on YellowDog 2?
>
> There is no such document - however, I've done it and listed the steps
> involved below.
>
> I installed netatalk like this:
>
> wget
> http://prdownloads.sourceforge.net/netatalk/netatalk-1.5pre6-1rh7.src.rpm
> rpm --rebuild netatalk*src.rpm
> rpm -i /usr/src/rpm/RPMS/ppc/netatalk-1.5pre6-1rh7.ppc.rpm
> cd /usr/include/netatalk
> cp at.h at.h.glibc-devel
> rpm -i /usr/src/rpm/RPMS/ppc/netatalk-devel-1.5pre6-1rh7.ppc.rpm --force
> touch /etc/atalk/afppasswd
> afppasswd -a darron
> /etc/rc.d/init.d/atalk start
>
> Works just fine from my Mac OS 9.2 box.
>
> NOTE: It DOESN'T seem to work properly with Mac OS X.1. I believe
> that's a
> netatalk 1.5pre6 problem because I have 1.5pre8 working on some other
> Linux
> and FreeBSD boxes at work and home.
>
> I've got the finished PPC RPM's posted here:
>
> ftp://ftp.froese.org:21/rpms/ydl-2.0/netatalk/1.5pre6
>
> What is the problem you are experiencing?
>
> Posting some logs, error messages or descriptions of the problems you
> are
> experiencing would help. Without that information we can't help.
> --
> Darron
> darron@froese.org
>
>
>
> From: "Nathan A. McQuillen" <nm@steaky.dhs.org>
> Date: Sat Nov 03, 2001 12:01:33 PM America/Anchorage
> To: YellowDog list <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Re: Easy way to set up Samba and NETATALK?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> AFAIK, the documentation will be the same as for netatalk and samba on
> x86
> Red Hat. I don't think there are any PPC-specific issues, at least for
> basic setup. Of course, the binary RPM format is different... but you
> knew
> that.
>
> Samba is admittedly a little trickier than netatalk, but there are a few
> good web-based admin tools for setting up samba shares (SWAT is included
> in the samba rpms now, I believe), and for a simple setup it shouldn't
> be
> that tough to deal with.
>
> What sorts of errors are you getting?
>
> - N
>
>> We realized that for now, Netatalk would be fine. Samba doesn't have
>> to
>> happen yet.
>>
>> But we're having a BEAR of a time getting it running. Even my father,
>> who
>> knows UNIX like nobody's business finally threw up his hands.
>>
>> I've done many Google searches, and good HOW-TO INSTALL documentation
>> seems
>> to be very elusive.
>>
>> Anyone know of a good document explaining how to get netatalk up and
>> running
>> on YellowDog 2?
>
> From: "Timothy A. Seufert" <tas@mindspring.com>
> Date: Sat Nov 03, 2001 02:02:55 PM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Easy way to set up Samba and NETATALK?
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> At 12:07 PM -0800 11/3/01, Wes Plate wrote:
>
>> Thanks.
>>
>> We realized that for now, Netatalk would be fine. Samba doesn't have
>> to
>> happen yet.
>>
>> But we're having a BEAR of a time getting it running. Even my father,
>> who
>> knows UNIX like nobody's business finally threw up his hands.
>>
>> I've done many Google searches, and good HOW-TO INSTALL documentation
>> seems
>> to be very elusive.
>>
>> Anyone know of a good document explaining how to get netatalk up and
>> running
>> on YellowDog 2?
>
> netatalk is sort of self-documented. The default configuration files
> that get installed with the package have lots of comments that explain
> just about everything required for normal setups. It also has a decent
> set of man pages.
>
> The configuration files all reside in /etc/atalk . Take a look at them
> and see if you can't figure out what needs to be done. If you need
> more information than is present in the comments, try "man
> configfilename" to see if there's a man page for that configuration
> file.
>
> Once you are satisfied with the config, you need to start the daemon.
> This can be done with the command:
>
> /etc/init.d/atalk start
>
> (Or, if it's already running and you want to force it to restart with a
> new config, use "restart" instead of "start".)
>
> If you want the AppleTalk daemon to be automatically started on boot,
> you'll have to add it to your default runlevel (probably runlevel 3 or
> runlevel 5). This can be done through the Red Hat Control Panel's
> runlevel editor, or by adding the proper symbolic link to /etc/rc3.d/
> and /etc/rc5.d/ .
> -- Tim Seufert
> From: Pat Plummer <ppat@fmtc.com>
> Date: Sat Nov 03, 2001 12:29:57 PM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: ppp and the 2.4.x kernels
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> I am trying to get ppp working with YDL 2.1 and the default 2.4.10-12a
> kernel
> on an iMac 400SE. For now I have gone back to the previous 2.2.19
> kernel as
> it works well with ppp.
>
> Near as I can tell from the archives and elsewhere, I need to have ppp
> 2.4.1,
> but cannot just update to it as I need the pam-devel-0.72-37b rpm which
> is
> not in the 2.1 release. rpm-find was not helpful as I would need to
> use a
> later release of pam, pam-devel, and glibc to install ppp2.4.1.
>
> Are there precompiled rpms available somewhere else that might help
> out? Any
> other suggestions?
>
> Pat
> --
> Embrace the penguin...
> Powered by Yellow Dog Linux 2.1
> on an Apple Network Server 700
> --
> ppat@fmtc.com
> ppat@mac.com
> From: A Maloney <amaloney@twcny.rr.com>
> Date: Sat Nov 03, 2001 12:35:49 PM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: 2.1 .iso
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> I have an order in for the book plus the disc.
> It appears that these will not ship before mid November.
>
> I have downloaded a 49.7 MB .iso document which is not recognized by
> Toast Titanium 5.
> Thus I cannot make an installation CD.
>
> What do I do now?
>
> Should I order the 3 disc set?
> Will it arrive before the book?
>
> -- Al
>
> Honi soit qui mal y pense!
> From: Winston Chang <winston@stdout.org>
> Date: Sat Nov 03, 2001 12:49:04 PM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Subject: Powerbook G4 rev. 2 (550MHz) problems with X
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> I managed to get YDL 2.1 installed on my shiny new Powerbook G4, but I'm
> having some problems with X.
>
> X only works in 8-bit color, but there seems to be a palette problem.
> White is mapped to blue, and the colors are garish in general. Does YDL
> have proper support for the Mobility Radeon? The 'fbset' command seems
> unable to set it anything other than 8 bit color. Will a new kernel or
> a new version of XFree86 fix this problem?
>
> Thanks,
> --Winston Chang
>
> From: Ron Smith <ronsmith28@home.com>
> Date: Sat Nov 03, 2001 12:55:52 PM America/Anchorage
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: wallstreet/lombard question
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> I've been lurking on this list for several months and I'm glad someone
> brought up the G3 PowerBooks. I have not been able to get a workable
> installation of Linux on mine (Black Keyboard, Wallstreet). It's the
> same problem every time. I've gotten further with YDL 2.0/2.1 I still
> have video problems.
>
> I haven't been able to get the SuSE installer to run at all. I was able
> to get the YDL 2.1 GUI installer to run and install YDL. The display
> was so faint that I was only able to do it because I know the setup
> sequence and was able to barely make out the parts of the screen I
> needed to click on. After I install and reboot is where the problem I
> *always* run into at some point of trying to put linux on the machine.
>
> In the top right corner is the penguin and text scrolling down.
> However, about halfway down the screen, centered is another penguin and
> the same scrolling text! Between the display being so dim and the two
> displays wrapping around each other, I cannot make out what the
> messages are, but this is where it stays.
>
> 1. Yes, I use the kernel append video=atybf:vmode:10
> 2. The is where the installer for SuSE dies... it doesn't actually
> start the installer
> 3. When I try the text only YDL installer the display goes blank
> 4. I have tried all the combinations I know of for the "force video"
> and "no video driver" in BootX
> 5. The display works fine in Mac OS 9, I booted into it to adjust the
> brightness/contrast, but that didn't help the linux display.
>
> I've had great success on my "new world" machines, a non-firewire iBook
> SE, and a G4/500DP (although no SMP yet). I would be happy to just get
> this Wallstreet runnin linux in a text mode, I don't need to run X on
> it for my purposes.
>
> Any suggestions?
>
> -Ron
>
> From: Bill Fink <billfink@mindspring.com>
> Date: Sat Nov 03, 2001 03:31:43 PM America/Anchorage
> To: <yellowdog-general@lists.yellowdoglinux.com>
> Cc: Bill Fink <billfink@mindspring.com>
> Subject: Saga of yup update (sortof) from YDL 2.0 to 2.1
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> Hi,
>
> I managed to upgrade my system from YDL 2.0 to 2.1 using yup together
> with some manual ftp and rpm steps, so I thought I would document what
> I did in case anyone else is interested.
>
> First, it's important to note that the YDL 2.1 distribution on
> ftp.yellowdoglinux.com is totally messed up at the moment (the
> fuji 2.1 ISO image is severely truncated and there are no YDL 2.1
> RPMS available). However, some of the mirrors are fine, and I
> chose to use ftp.ibiblio.org. Here are the steps I took to upgrade
> from YDL 2.0 to 2.1:
>
> 1. yup update, to make sure my YDL 2.0 was fully up-to-date,
> which it was.
>
> 2. Used ftp to get the latest 2.1 yup-0.7.6-6.noarch.rpm from
> a functioning 2.1 mirror (in my case ftp.ibiblio.org), and
> then used "rpm -U" to upgrade my yup to this new version.
>
> 3. yup config dist, to select the distribution and mirror to
> use. 2.1 was not a recognized distribution so I chose 2.0,
> and in my case chose ftp.ibiblio.org for the mirror.
>
> 4. yup clean yupdb, to start with a fresh yup database for
> YDL 2.1.
>
> 5. Manually edited /etc/yup.conf, and changed all occurrences
> of 2.0 to 2.1.
>
> 6. yup update, to get all the new and updated YDL 2.1 stuff.
> This came back with a small list of stuff to delete, and
> a large list of stuff to upgrade or install. The stuff
> to delete are RPMS which have been obsoleted such as ybin
> which is now part of the newer yaboot package. Wait until
> yup asks whether you want to proceed and then just answer
> "y". After this, yup starts downloading all the RPMS,
> which worked until it got to kernel-source-2.4.10-12a.ppc.rpm,
> which failed with a python error.
>
> 7. The python error was an integer overflow caused by the
> progress checking, where it multiplies the number of bytes
> transferred by 100, and the kernel-source RPM is 23513953
> bytes, which overflows a signed int (max of about 2 GB).
> I got around this by manually ftp'ing the
> kernel-source-2.4.10-12a.ppc.rpm file from the mirror
> site into the /var/cache/yup/packages cache directory.
> Subsequent checking revealed the "-q" ("--quiet") and
> "-qq" ("--really-quiet") yup options, one or the other
> of which would probably have bypassed this problem by
> eliminating the progress checking.
>
> 8. yup update, to download the rest of the RPMS and attempt
> to install them. All the remaining downloads completed
> successfully, but the install failed with another python
> error, the cause of which was not immediately obvious,
> and which I unfortunately don't remember the exact error
> message.
>
> 9. cd /var/cache/yup/packages, and ran the following command:
>
> rpm -U --test `ls -gl | grep 'Nov 3' | awk '{ print $NF }'`
>
> The 'Nov 3' above was used to select all the RPMS that
> yup downloaded that day, and should of course be changed
> to reflect the actual date that anyone else uses this
> procedure. If there were no other RPMS in the
> /var/cache/yup/packages directory previously, you could
> simply replace the whole `...` part with just *.
>
> 10. In my case, I had some conflicts with some old sane (scanner)
> packages, so I just removed them with "rpm -e" since there
> were newer sane packages in YDL 2.1. Rerunning the
> "rpm -U --test" command above showed that everything
> would upgrade/install successfully (no errors reported).
>
> 11. Reran the "rpm -U" command from step 9 above without the
> --test option (you can also change the -U option to -Uvh
> to get a nice progress status of the installation). This
> successfully upgraded my system from YDL 2.0 to YDL 2.1.
>
> 12. yup clean yupdb, to start with a fresh yup database for
> YDL 2.1 after the upgrade.
>
> 13. Reran a "yup update", to make sure yup was happy, which
> gave the following:
>
> Reading RPM database... (100%)
> Performing dependencies sanity check...
> Retrieving distribution information...
> ftp.ibiblio.org ready
> yup.db.stat: 0 KB read (97%) 1.5 KB/sRetrieving initial
> package list...
> yup.db.init: 1611 KB read (100%) 70.5 KB/s
> Downloading package list updates...
> Integrating updates into local package list...
> Reading package list... (100%)
>
> Nothing to do...
>
> 14. Fixed up my /boot/vmlinux and /boot/System.map. The upgrade
> to YDL 2.1 had installed the 2.4.10-12a versions of these
> files, and I still wanted to run my 2.4.6 BenH kernel
> (because I want to try out using a FireWire disk and I
> believe 2.4.6 was the last kernel to have a functional
> FireWire disk capability, although the very latest BenH
> kernels may also work). If you're happy with the 2.4.10-12a
> kernel, you can obviously skip this step.
>
> 15. I still need to fix up some minor system customizations
> that got undone by the upgrade process, such as some X
> customizations I had made previously. I am happy to report
> that in my case I didn't have to muck with the
> /etc/X11/XF86Config-4 file after the upgrade, and X
> is working at least as well as before the upgrade
> (including the Xv support).
>
> 16. I have subsequently successfully done a "yup install webmin".
> This points out that it may be necessary to manually
> "yup install" stuff from YDL 2.1 if it didn't even exist
> in YDL 2.0 (webmin is the only major item from the YDL 2.1
> new features list that I can remember that would fall in
> this category but there may be others).
>
> I now have a fully functional YDL 2.1 system. It really wasn't all
> that bad to do the upgrade, even with the manual steps required. It
> was certainly a lot less effort than doing a full YDL 2.1 install
> (I have also recently participated in doing that and may report on
> that experience in a separate message).
>
> I hope others find this procedure useful, although I of course can't
> guarantee success for all other cases, but it should generally work
> fine I believe.
>
> -Bill
>
> P.S. Any chance this could earn me a T-shirt? :-)
>
> From: Marc Stergionis <stermarc@home.com>
> Date: Sat Nov 03, 2001 03:57:31 PM America/Anchorage
> To: YellowDogLinux <yellowdog-general@lists.yellowdoglinux.com>
> Subject: 2 simple ?s -- smtp configuration, Open Office install
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>
> 1. I know I'm probably gonna say "Doh" when I figure this out, but I
> just got YDL2.0 installed and most everything works fine so far.
>
> I am receiving mail fine (KMail) but have not been able to send. Of
> course in Mac OS, configuring SMTP for use with the @home broadband
> service requires you only put the word "mail" in your pop/inbound setup
> field and the word "mail" in the smtp/outbound field.
>
> This, of course, does not work in KMail. Neither does smtp.home.com
> nor smtp.grtfls1.mt.home.com (what we've been given as an alternate).
>
> What *do* I put in there??? BTW, the other smtp setup field defaults
> to port 25, which I've left that way.
>
> 2. Following the instructions on the YDL site, I'm installing Open
> Office. First installed the Runtime Java from the Morsels CD, then
> ungzipped and ran the installer. it progressed through the sign in,
> highlighted each category on the left side of the installer splash
> window as it progressed ... and the install timer in the lower left
> wound down. then the Installer timer went away, and there's a little
> blue pulsating gradient in the lower left. If I try to close the
> installer window, I get the message "If you close the window now, Open
> Office will not be completely installed and will not run." (or
> something like that).
>
> This has been going on for over an hour. I do have a really slow Power
> Mac clone, and the Process Management utility reports that
> OpenOffice60.bin is getting 99.99 percent of cpu time. And the computer
> acts like it does too!!
>
> Does Open Office take an inordinately lo-o-o-nnn-n-g time to install?
> I've already aborted the install once (by closing the window) and
> trashed the Open Office folder that was created in my User directory ..
> then tried the install again. Same deal.
>
> Or is something else wrong?
>
> Thanks
>
> -ms
> -- Many have Montana envy ... the lucky get to live here!
> Marc Stergionis
> Community Relations & website author
> Benefis Healthcare -- http://www.benefis.org
> "Opinions expressed are not necessarily those of my employer"
This archive was generated by hypermail 2a24 : Sun Nov 04 2001 - 03:38:22 MST