- WLUG - wlug.mailman3.com

Re: [Wlug] problem hardware?

by Charles R. Anderson

On Tue, Oct 14, 2003 at 03:55:02PM -0400, Baris Hasdemir wrote: > no. The region should be "1" I got this dvd from the shrewsbury public > library. and actually it is playing the dvd without any problems. I am > using xine to play it. the only problem is those error messages. Well, if it works I wouldn't worry about it. It is likely that xine is trying "region 0" for playing DVDs from any region, although this is just a guess. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Oct. 14, 2003

Re: [Wlug] problem hardware?

by Baris Hasdemir

no. The region should be "1" I got this dvd from the shrewsbury public library. and actually it is playing the dvd without any problems. I am using xine to play it. the only problem is those error messages. On Tue, 2003-10-14 at 15:33, gboyce(a)badbelly.com wrote: > The error given here "Media region code is mismatched to logical unit" > sounds like the drive believes that it's not allowed to read content of > that type. Are you trying to view a non-US/Canada movie in the drive? > > On Tue, 14 Oct 2003, Baris Hasdemir wrote: > > > Hello all, > > > > Today I received my slot loading pioneer dvd rom drive from newegg.com. > > But linux tells me there are problems with it. The problem is my new > > hardware right? Or should I upgrade my kernel? I wanted to be sure > > before sending it back. > > > > kernel 2.4.22(slackware 9.1) > > > > thanks, > > baris > > > > # tail -f /var/log/syslog > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " > > Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:47 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:47 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 " > > > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Oct. 14, 2003

Re: [Wlug] problem hardware?

by gboyce＠badbelly.com

The error given here "Media region code is mismatched to logical unit" sounds like the drive believes that it's not allowed to read content of that type. Are you trying to view a non-US/Canada movie in the drive? On Tue, 14 Oct 2003, Baris Hasdemir wrote: > Hello all, > > Today I received my slot loading pioneer dvd rom drive from newegg.com. > But linux tells me there are problems with it. The problem is my new > hardware right? Or should I upgrade my kernel? I wanted to be sure > before sending it back. > > kernel 2.4.22(slackware 9.1) > > thanks, > baris > > # tail -f /var/log/syslog > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " > Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:47 penguen kernel: ATAPI device hdd: > Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:47 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 " > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Oct. 14, 2003

problem hardware?

by Baris Hasdemir

Hello all, Today I received my slot loading pioneer dvd rom drive from newegg.com. But linux tells me there are problems with it. The problem is my new hardware right? Or should I upgrade my kernel? I wanted to be sure before sending it back. kernel 2.4.22(slackware 9.1) thanks, baris # tail -f /var/log/syslog Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:45 penguen kernel: ATAPI device hdd: Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:45 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:45 penguen kernel: ATAPI device hdd: Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:45 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:47 penguen kernel: ATAPI device hdd: Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:47 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 "

Oct. 14, 2003

RE: [Wlug] Fw: RE: show

by mlong＠datalong.com

That sounds like a great topic. This could be expanded to include mini tutorials scattered about in subsequent shows explaining how to achieve the same functionality in the various apps. Cheers, Mike > Yury, > > You can count me in. I also know my way around a TV production studio. > > We had talked about doing an introduction to linux. As an aside to that I > was thinking that possibly we could do a show on equivalent pieces of > software on the linux side of things that could replace (perceived) > missing > functionality. This would include stuff like Evolution, Mozilla, GnuCash, > OpenOffice, mplayer, xmms, etc. > > What do people think?

Oct. 14, 2003

RE: [Wlug] Fw: RE: show

by Keller, Tim

Yury, You can count me in. I also know my way around a TV production studio. We had talked about doing an introduction to linux. As an aside to that I was thinking that possibly we could do a show on equivalent pieces of software on the linux side of things that could replace (perceived) missing functionality. This would include stuff like Evolution, Mozilla, GnuCash, OpenOffice, mplayer, xmms, etc. What do people think? Thanks, Tim. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Tuesday, October 14, 2003 12:56 PM To: wlug(a)mail.wlug.org Cc: wlug(a)wlug.org Subject: [Wlug] Fw: RE: show hi, everyone. since we talked about producing an educational show about linux and putting it 'in-the-air' at the last wlug meeting and i saw a very enthusiastic response so i've reserved the studio for oct.21(see below). there's a problem with a converter but i'm sure we can find a laptop with a video output. for the show we need two cameramen(anyone can do that; very simple duties and can be learned within 3-5 min), a show host and guests. please, bring any suggestions or/and recommendations. thanks. yury --------- Forwarded message ---------- From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> To: 'Yury I Vashugin' <vashugins(a)juno.com> Date: Fri, 10 Oct 2003 13:42:56 -0400 Subject: RE: show Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> Yes. Does anybody in the group have access to a scan converter or can you use a computer with a video card output? Since we spoke about it, our last scan converter was put into service to be used on one of our channel's for our bulletin board. For you to use it, we would have to take a channel off the air. I know that a lot of laptops have video out. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Friday, October 10, 2003 11:48 AM To: mserra(a)ci.shrewsbury.ma.us Subject: show marc, can i reserve the studio for half-an-hour show on tuesday, october 21 at 6:30 (actually it will not be a show; just a preliminary stuff- what light, what background, what settings we want for 'linux show', to try a scanner converter etc)? yury ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today! _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Oct. 14, 2003

Fw: RE: show

by Yury I Vashugin

hi, everyone. since we talked about producing an educational show about linux and putting it 'in-the-air' at the last wlug meeting and i saw a very enthusiastic response so i've reserved the studio for oct.21(see below). there's a problem with a converter but i'm sure we can find a laptop with a video output. for the show we need two cameramen(anyone can do that; very simple duties and can be learned within 3-5 min), a show host and guests. please, bring any suggestions or/and recommendations. thanks. yury --------- Forwarded message ---------- From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> To: 'Yury I Vashugin' <vashugins(a)juno.com> Date: Fri, 10 Oct 2003 13:42:56 -0400 Subject: RE: show Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> Yes. Does anybody in the group have access to a scan converter or can you use a computer with a video card output? Since we spoke about it, our last scan converter was put into service to be used on one of our channel's for our bulletin board. For you to use it, we would have to take a channel off the air. I know that a lot of laptops have video out. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Friday, October 10, 2003 11:48 AM To: mserra(a)ci.shrewsbury.ma.us Subject: show marc, can i reserve the studio for half-an-hour show on tuesday, october 21 at 6:30 (actually it will not be a show; just a preliminary stuff- what light, what background, what settings we want for 'linux show', to try a scanner converter etc)? yury ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!

Oct. 14, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > >>Lowres won't work. The problem is it sees the S3Virge chip on the vid >>card and wants to use the s3virge driver, when it should really be using >>the 3DLabs driver. In the old sax, it tries to run in lowres first, and >>it comes up very large and hanging way over the edge of my screen. What >>I've found to work is this - >>sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs > > > The "very large and hanging way over the edge of my screen" problem is most > likely a funky "modelines" line in your XF86Config file. This can often be > remedied by manually adjusting your monitor, or by running (carefully!) > xvidtune and noting the new mode line once the screen is properly adjusted. > This new mode line would then be hand edited into your XF86Config file. If > the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to > fuss with the v4.x XFree86 driver. > > >>I've read the help screen for sax2 a bunch of times, and I don't >>understand how to give it the same information. >> >>sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom >>half of my screen and bleeds way off the right edge. >> >>sax2 -m 0=glint quits and gives me error messages (no device found - the >>card has a glint 500tx accelerator) >> >>sax2 -m 0=s3virge goes black and locks up, only reset button gets me out >> > > > Which version of XFree86 4.x are you trying to use? If you are having > problems like this, you most likely need the latest and greatest. However, I > have seen cases where XFree86 v3.x works better than v4.x, especially on > "weird" video cards that are getting on in years. > > Later, > > Andy I'm trying to use 4.1.0. The 3Dlabs driver didn't come with 3.3.6. I had to find it online and unpack it. I also ran the Xinstall script that came with the 4.1.0 tarballs. I thought it had replaced all my files, so I can't tell you for sure which version is really running. I just tried again to run sax2 -m 0=vga, and it ran fine at 640x480. I'm not sure what's different now, but I did install some other packages this afternoon, like openmotif devel and some font packages. Anyway, sax2 does not list my vid card, but sax does. Maybe I should just leave this alone for now, since it works. If it's the source of the kde problem, I can live with it as long as my function keys work. BTW, I had asked you about my other machine, which wouldn't let me switch virtual screens. Turns out my nifty new keyboard has about 10 special buttons for web surfing, and one of them turns off the function keys. Thanks, Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > > Lowres won't work. The problem is it sees the S3Virge chip on the vid > card and wants to use the s3virge driver, when it should really be using > the 3DLabs driver. In the old sax, it tries to run in lowres first, and > it comes up very large and hanging way over the edge of my screen. What > I've found to work is this - > sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs The "very large and hanging way over the edge of my screen" problem is most likely a funky "modelines" line in your XF86Config file. This can often be remedied by manually adjusting your monitor, or by running (carefully!) xvidtune and noting the new mode line once the screen is properly adjusted. This new mode line would then be hand edited into your XF86Config file. If the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to fuss with the v4.x XFree86 driver. > > I've read the help screen for sax2 a bunch of times, and I don't > understand how to give it the same information. > > sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom > half of my screen and bleeds way off the right edge. > > sax2 -m 0=glint quits and gives me error messages (no device found - the > card has a glint 500tx accelerator) > > sax2 -m 0=s3virge goes black and locks up, only reset button gets me out > Which version of XFree86 4.x are you trying to use? If you are having problems like this, you most likely need the latest and greatest. However, I have seen cases where XFree86 v3.x works better than v4.x, especially on "weird" video cards that are getting on in years. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > >> > >>I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). > >>Sax2 won't run on this machine - it goes to a black screen that won't > >>respond to any keystrokes except the reset button. I had to setup XFree > >>4.1 with the old sax, passing monitor and server parameters to it on the > >>command line for it to run correctly (hsync, vsync, screen resolution > >>and server). Sax2 doesn't seem to have the same switches. Is it bad to > >>setup newer versions of X with sax instead of sax2? > >> > >>BTW, I had a lot of trouble setting up the older version of XFree from > >>the CD's, too. > >> > >>Greg > > > > HI Greg, > > > > I think sax2 has a command line switch to force it to run in a low res > > mode, and I believe it is "-l" (minus ell). I've succeeded in using this > > with all sorts of strange hardware. This switch is not the default. > > > > sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. > > SuSE seems to be geared to more easily handle XFree86 4.x. > > > > See if you can get this graphics card to run in 640x480 8-bit color mode > > first, and if you succeed, then get brave and attempt higher resolutions > > afterwards. > > > > Later, > > > > Andy > > Andy, > > Lowres won't work. The problem is it sees the S3Virge chip on the vid > card and wants to use the s3virge driver, when it should really be using > the 3DLabs driver. In the old sax, it tries to run in lowres first, and > it comes up very large and hanging way over the edge of my screen. What > I've found to work is this - > sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs > > I've read the help screen for sax2 a bunch of times, and I don't > understand how to give it the same information. > > sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom > half of my screen and bleeds way off the right edge. > > sax2 -m 0=glint quits and gives me error messages (no device found - the > card has a glint 500tx accelerator) > > sax2 -m 0=s3virge goes black and locks up, only reset button gets me out > > Can't figure out the proper syntax for the --xmode option to set the > screen resolution or hsync, and setting vsync doesn't seem to be an > option. If you know this secret, I'll buy you a beer. > > > Greg > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

RE: [Wlug] FW: Authentication on outgoing SMTP, how to set with postfix?

by Jim & Toni

Well, found the answer here. http://sdb.suselinux.hu/en/sdb/html/rsimai_imap_smtp_auth.html -----Original Message----- From: Jim & Toni [mailto:jntdibb@bellatlantic.net] Sent: Monday, October 13, 2003 2:28 PM To: 'wlug(a)wlug.org' Subject: Authentication on outgoing SMTP, how to set with postfix? I've almost got postfix setup as a mail relay from my local linux box to 'outgoing.verizon.net'. But, the postfix howto doesn't specify how to provide login/password authentication for smtp servers that require it. The error was '554: Authentication required' Going to search more, but appreciate any help. Thanks.

Oct. 13, 2003

FW: Authentication on outgoing SMTP, how to set with postfix?

by Jim & Toni

Sorry if you get multiples, like it says, having trouble with outgoing. Thanks. -----Original Message----- From: Jim & Toni [mailto:jntdibb@bellatlantic.net] Sent: Monday, October 13, 2003 2:28 PM To: 'wlug(a)wlug.org' Subject: Authentication on outgoing SMTP, how to set with postfix? I've almost got postfix setup as a mail relay from my local linux box to 'outgoing.verizon.net'. But, the postfix howto doesn't specify how to provide login/password authentication for smtp servers that require it. The error was '554: Authentication required' Going to search more, but appreciate any help. Thanks.

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Monday 13 October 2003 9:13 am, Gregory Avedissian wrote: > >>Same thing happens with any user, and the problem spans two consecutive >>installations on the same machine. The problem doesn't exist on my other >>machine, even though I intalled the same stuff. >> >>I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). >>Sax2 won't run on this machine - it goes to a black screen that won't >>respond to any keystrokes except the reset button. I had to setup XFree >>4.1 with the old sax, passing monitor and server parameters to it on the >>command line for it to run correctly (hsync, vsync, screen resolution >>and server). Sax2 doesn't seem to have the same switches. Is it bad to >>setup newer versions of X with sax instead of sax2? >> >>BTW, I had a lot of trouble setting up the older version of XFree from >>the CD's, too. >> >>Greg > > > HI Greg, > > I think sax2 has a command line switch to force it to run in a low res mode, > and I believe it is "-l" (minus ell). I've succeeded in using this with all > sorts of strange hardware. This switch is not the default. > > sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. SuSE > seems to be geared to more easily handle XFree86 4.x. > > See if you can get this graphics card to run in 640x480 8-bit color mode > first, and if you succeed, then get brave and attempt higher resolutions > afterwards. > > Later, > > Andy > > Andy, Lowres won't work. The problem is it sees the S3Virge chip on the vid card and wants to use the s3virge driver, when it should really be using the 3DLabs driver. In the old sax, it tries to run in lowres first, and it comes up very large and hanging way over the edge of my screen. What I've found to work is this - sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs I've read the help screen for sax2 a bunch of times, and I don't understand how to give it the same information. sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom half of my screen and bleeds way off the right edge. sax2 -m 0=glint quits and gives me error messages (no device found - the card has a glint 500tx accelerator) sax2 -m 0=s3virge goes black and locks up, only reset button gets me out Can't figure out the proper syntax for the --xmode option to set the screen resolution or hsync, and setting vsync doesn't seem to be an option. If you know this secret, I'll buy you a beer. Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 9:13 am, Gregory Avedissian wrote: > > Same thing happens with any user, and the problem spans two consecutive > installations on the same machine. The problem doesn't exist on my other > machine, even though I intalled the same stuff. > > I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). > Sax2 won't run on this machine - it goes to a black screen that won't > respond to any keystrokes except the reset button. I had to setup XFree > 4.1 with the old sax, passing monitor and server parameters to it on the > command line for it to run correctly (hsync, vsync, screen resolution > and server). Sax2 doesn't seem to have the same switches. Is it bad to > setup newer versions of X with sax instead of sax2? > > BTW, I had a lot of trouble setting up the older version of XFree from > the CD's, too. > > Greg HI Greg, I think sax2 has a command line switch to force it to run in a low res mode, and I believe it is "-l" (minus ell). I've succeeded in using this with all sorts of strange hardware. This switch is not the default. sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. SuSE seems to be geared to more easily handle XFree86 4.x. See if you can get this graphics card to run in 640x480 8-bit color mode first, and if you succeed, then get brave and attempt higher resolutions afterwards. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Sunday 12 October 2003 2:25 pm, Gregory Avedissian wrote: > >>At the meeting last Thursday, I asked about a problem I'm having with >>KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' >>in another terminal while loading KDE. > > > Hi Greg, > > What happens if you create a brand new user, and then log in as that user and > fire up KDE? I'm wondering if there is a system problem or if something is > fubar in one of your user specific KDE files. > > Later, > > Andy Hi Andy, Same thing happens with any user, and the problem spans two consecutive installations on the same machine. The problem doesn't exist on my other machine, even though I intalled the same stuff. I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). Sax2 won't run on this machine - it goes to a black screen that won't respond to any keystrokes except the reset button. I had to setup XFree 4.1 with the old sax, passing monitor and server parameters to it on the command line for it to run correctly (hsync, vsync, screen resolution and server). Sax2 doesn't seem to have the same switches. Is it bad to setup newer versions of X with sax instead of sax2? BTW, I had a lot of trouble setting up the older version of XFree from the CD's, too. Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Sunday 12 October 2003 2:25 pm, Gregory Avedissian wrote: > At the meeting last Thursday, I asked about a problem I'm having with > KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' > in another terminal while loading KDE. Hi Greg, What happens if you create a brand new user, and then log in as that user and fire up KDE? I'm wondering if there is a system problem or if something is fubar in one of your user specific KDE files. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

You can't get there from here...

by Gregory Avedissian

At the meeting last Thursday, I asked about a problem I'm having with KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' in another terminal while loading KDE. Description of problem: KDE starts to load, tells me it's checking peripherals, and then the screen goes black. Ctrl-alt-back kills the xserver and gets me out. In running the tail, I discovered that KDE really is runnning OK, but I have to switch to another virtual console (alt-F2) and then ctrl-alt-F7 will get me to the kde desktop. I get error messages from modprobe while kde is loading. It's looking for sound-slot-1, which I think is odd, because modules.conf doesn't say anything about a sound-slot-1. I only have one sound card, and it's at sound-slot-0. I tried turning off the sound server in the kde control center, and that didn't help. I also get gpm error messages when I go in an out of an x-session. Changing GPM_PARAMS in /etc/rc.config to the correct type of mouse helped get rid of flaky mouse behavior in console, but the error messages continue. Below are the messages. Any ideas or suggestions are appreciated. Thanks, Greg Oct 12 13:54:29 linux gpm[1601]: Error in protocol Oct 12 13:55:04 linux last message repeated 38 times Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0

Oct. 12, 2003

Re: [Wlug] NIC settings -- how?

by David Goss

Hi all... hope someone can help... been away from the meetings for a while... ( like a year ) due to health reasons... then to boot my linux machine had a massive failure and i had to replace it... had it all set up the forward and masquerade a couple of windows boxes through my dsl connection... ( verizon ) have the pppoe all set up... but can't for the life of me remember how to set up the ipchains to handle the windows boxes for the wife and kids... and man they are getting hostile about not being able to get on the internet from home... i know it was not that hard to set up but for the life of me i can not find the docs i used in the first place... hoping to make some meetings soon... now that the health is getting back to "normal"... and buying beer for the helpful guy that can get my network back to normal as well... best regards to all dave goss

Oct. 11, 2003

Re: [Wlug] NIC settings -- how?

by Charles R. Anderson

On Thu, Oct 09, 2003 at 01:18:34PM -0400, Bill Mills-Curran wrote: > How can I view and alter NIC settings, like auto-negotiate, speed, > duplex on my Red Hat 8/9 boxes? mii-tool or ethtool, depending on the driver. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Oct. 9, 2003

NIC settings -- how?

by Bill Mills-Curran

How can I view and alter NIC settings, like auto-negotiate, speed, duplex on my Red Hat 8/9 boxes? Thanks, Bill

Oct. 9, 2003

Re: Old Hardware (Re: Re: Debian question)

by Bob George

"Chuck Homic" <chuck(a)vvisions.com> wrote: > [...] > Currently it is an excuse to own the domain underpowered.net. Hah, great name! > [...] > - How can I get on this list? That sounds cool. Info is at http://groups.yahoo.com/group/survpc/ . Be forewarned however: It's an often contentious place, with a few hard-core DOS holdouts. Not all that it could be, but success stories for using "old stuff" are always welcome. > - I chose Debian for three reasons. 1. familiarity, 2. laziness, 3. the > aforementioned 240M hard drive. Since Debian would install a working > base system in around 50M, I figured it could conserve well. That's why I wound up on Debian, although with a *bit* more disk space! > Currently > I'm running DNS, HTTP, FTP, & IMAP with ~100M free for data. I have to > erase the HTTP logs of virus attacks on a fairly regular basis to keep > that free space, though. ;) Great to hear that it keeps up with all that. A few folks on the list have asked about using various distributions on limited hardware, and I've generally recommended Debian as worth considering. I've installed it on 486en, but usually with 32M or more memory. I wasn't sure about less being practical (recogizing practical depends on the individual). > - In retrospect, it would be nice to have a package manager with more > modest RAM requirements. However, I'll decide this for real when I > install the second hard drive. With one HD just for swap, it might not > matter so much. Are you using dpkg or apt? > - I have no problem saturating my 10Mbit ethernet with a 486-25, so I'm > sure it would make a fine firewall/gateway if you don't use it for > anything else, and you might have to go easy on the firewall rules. Or > it might do fine with fancy firewall rules, who knows? Experience > running NAT (for a T1) on similar hardware indicates that that would be > no problem. I did notice that old NE2000 clone NICs caused my CPU utilization to spike, especially ISA versions. My 486-66 did fine with PCI cards, though that was a couple of kernels ago. > - Although installing packages is a pain (which would be fixed up for > $0.50 of RAM, I presume) it just hums along in the interim. I don't > know how much RAM the motherboard can take, and I wouldn't know who to > buy 30/72-pin SIMMs from. :) Although experience shows I wouldn't have > to buy them, they would be given to me if I express interest. (That's a > big bonus for old hardware! Hmm. If I didn't toss 'em before the big move, I might actually HAVE some 4M 30 pin SIMMs. I think I'm out of 72 pin though. I get sad thinking about what I had to toss in Phoenix due to no time prior to my move. I did give away a couple of trunkloads of old stuff. > [...] > - It's a good box just to have hooked up to a wire, but if you have such a > thing and you ever find yourself thinking about adding a second 486 to > boost resources, you've gone off the deep end. After the novelty value > subsides, you have to think about the energy cost. How many services > can you provide per watt? How would that compare to a 50W power supply > on an old P-100 thinkpad or something? Yeah, I finally started consolidating boxes. A real problem in Phoenix was heat, where my "den" easily ran 10 degrees hotter than the rest of the house. 'Course, here that's not quite the issue it was. Still, I don't like waste, and the quiet hum of my current systems is much nicer than the roar of fans I had (as well as the AC working overtime to keep up.) > (I'd often thought about using > aging laptops as servers, to simplify the UPS situation. I figure a > ~$40 car battery plugged into the AC jack could provide backup power for > quite a long time, but that's just insanity.) I wanted to do the same thing! Quiet, low power, and UPS built-in. Oh, and small too. Thanks for the info! - Bob

Oct. 9, 2003

Old Hardware (Re: [Wlug] Re: Debian question)

by Chuck Homic

On Fri, Oct 03, 2003 at 08:31:25AM -0400, Bob George wrote: > "Chuck Homic" <chuck(a)vvisions.com> wrote: > > Oh, hey... my Debian rant reminded me of something! > > > > I have Debian running on a 486-25 with 12MB of RAM. > > [...] > > Hey, mind if I ask what you use it for? The reason I ask is that I'm on a list > dedicated to old PC hardware users, which until recently equated to a base of > fanatical DOS holdouts. Slowly though, most are inquiring about Linux, so I'd > like to give them some useful info about using Debian as a "modern" > distribution on low-resource systems. Unfortunately, I've had to dump most of > my old systems, so can't speak from first-hand experience anymore. Currently it is an excuse to own the domain underpowered.net. It doesn't do much right now, due to lack of storage. My 5G SCSI drive doesn't work with my old old Future Domain controller, so it's running 240M right now. I bought a new interface (urrm... new to me, for a 16-bit ISA SCSI adapter. $1 at eBay, woohoo) and have yet to see if it works better. Anyway, I mostly use it for file transfer, right now. Like if I'm at work and want to send a large file home, I'll drop it there. Or if I want to email friends/family digital photos, but no mail server I know of will accept a 50M attachment, I send a link to http://underpowered.net/whatever In the future I plan to put some of my hackish projects there, expecting that the low bandwidth needs of such things will match the low power available. And of course it runs primary DNS for underpowered.net. > Stephen Darnold, the guy who put Basic Linux together, used to lurk there, and > there was often extensive discussion on what could be run on older hardware. > Yours sounds like the lower end of the spectrum, so I'm wondering how well it > works. Would it work well with Debian specifically as a firewall/gateway? Would > you say the benefits of running something current offsets the inconvenience of > those delays with installs etc.? Whoa, this is like, an interview or something. Let's take it 1-by-1: - How can I get on this list? That sounds cool. - I chose Debian for three reasons. 1. familiarity, 2. laziness, 3. the aforementioned 240M hard drive. Since Debian would install a working base system in around 50M, I figured it could conserve well. Currently I'm running DNS, HTTP, FTP, & IMAP with ~100M free for data. I have to erase the HTTP logs of virus attacks on a fairly regular basis to keep that free space, though. ;) - In retrospect, it would be nice to have a package manager with more modest RAM requirements. However, I'll decide this for real when I install the second hard drive. With one HD just for swap, it might not matter so much. - I have no problem saturating my 10Mbit ethernet with a 486-25, so I'm sure it would make a fine firewall/gateway if you don't use it for anything else, and you might have to go easy on the firewall rules. Or it might do fine with fancy firewall rules, who knows? Experience running NAT (for a T1) on similar hardware indicates that that would be no problem. - Although installing packages is a pain (which would be fixed up for $0.50 of RAM, I presume) it just hums along in the interim. I don't know how much RAM the motherboard can take, and I wouldn't know who to buy 30/72-pin SIMMs from. :) Although experience shows I wouldn't have to buy them, they would be given to me if I express interest. (That's a big bonus for old hardware! That's how I got my 5M SCSI drive... it's one of those big full-height Seagate bricks, and fits in no modern case known to man.) - It's a good box just to have hooked up to a wire, but if you have such a thing and you ever find yourself thinking about adding a second 486 to boost resources, you've gone off the deep end. After the novelty value subsides, you have to think about the energy cost. How many services can you provide per watt? How would that compare to a 50W power supply on an old P-100 thinkpad or something? (I'd often thought about using aging laptops as servers, to simplify the UPS situation. I figure a ~$40 car battery plugged into the AC jack could provide backup power for quite a long time, but that's just insanity.) Well, enough rambling. Work to do. -Chuck BTW, speaking of old hardware... some folks on the list might remember my '87 Plymouth Sundance. My brother put in a new engine, and it now runs like da shiznit, and is approaching 210,000 miles. You don't get free parts for a 15 year old car like a 15 year old computer, but there are other advantages.

Oct. 9, 2003

shameless promo of Slackware by the DistroWatch guy..

by Brian McLinden

DistroWatch Weekly, Issue 17, 29 September 2003 (opinion piece article by Ladislav Bodnar, the man who runs DW itself) "A new stable version of Slackware Linux was released late on Friday. As usual, the news was greeted with plenty of enthusiasm by many die-hard Slackware fans and by much curiosity from users of other distributions. What is so special about Slackware? Unlike other commercial distribution makers, such as Red Hat, Mandrake or SuSE, Slackware doesn't come with any system administration tools, it has an amazingly unsophisticated package manager and the company rarely makes headlines in the Linux media. Yet every a new Slackware release is announced, a wave of excitement sweeps the Linux forums and new sites (this OSNews review is a good example). Slackware is to Linux distributions what vi is to UNIX text editors - many people expected vi to die after an abundance of new, more intuitive and user-friendly text editors were introduced. But instead, vi flourished. And while other Linux distributions have certainly managed to take market share away from Slackware, there are still plenty of people out there -- probably a lot more than many would led you believe -- who would never consider using anything else. If you've never tried Slackware before, give it a partition now - and be prepared to fall in love... [end of comment]" Question - does he like slack because it is more like unix than any other distro? Back in the days when men were men............... __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

Oct. 9, 2003

Re: [Wlug] I choose Slackware.. God help me! (And you guys, please?)

by Matt Higgins

Woops miss fire!! Let me get to answering your questions. 1. simple is not easy? Well this is debatable. Think simple and it mostly easy, think hard and it is always hard! Your first step to easy, is to build a command line vocabulary and familiarize yourself with a command line editor (vi,vim,emacs,etc..) the choice of which is as much philosophical as it is functional. To get you started I would recommend a few books. I love getting documentation on-line but I feel much closer to paper and ink then I do electron guns and liquid crystals, not to mention you will not have Internet access right off the bat. Learning the Unix Operating System, 5th Edition: http://www.oreilly.com/catalog/lunix5/chapter/index.html Running Linux, 4th Edition: http://www.oreilly.com/catalog/runux4/ vi Editor Pocket Reference: http://www.oreilly.com/catalog/vipr/ These all just happen to be O'Reilly books these came right off the top of my head. The Learning the Unix OS book is a great place to start! It has examples and exercises and teaches you all the basic commands you will need to navigate the file system and start editing files. These will be your 1st tools and will also be the basis for learning other commands. Further more you can get started with these books before you get your system. 2. Partitions: The vendor should layout the disk in a reasonable way. If you want to leave some free space for the testing of alternative distributions tell them to leave 10GB free, that should be enough to install a few distros and not leave you strapped for space. As for the physical layout of the data on the disk, you realistically can't control this. The IDE controller will translate the physical layout of the disk into what amounts to one contiguous block. To say that file "foo" is on platter 3 and close the the spindle is almost impossible. Further more the file system will do its best to allocate blocks contiguously and fill in unused space in the most efficient way it knows how. I am not sure how the vendor will ultimately install everything, but the link you sent leads me to a high-end Linux workstation co. they may mirror the two IDE drives leaving you with md0-n and not the traditional hd[a-z][0-n]. File system layout is a big long topic something you will learn after reading the Running Linux book. For now trust the vendor and scorn them later when you are done reading. 3. Internet: You address 2 different points here. I will start with on-line-help. Slackware will come with ton's of documentation. This is often considered on-line even if its not on the Internet. There are docs for most installed applications in /usr/share/docs and there are man pages for just about everything else. You will learn about man in the Learning Unix book. Note that man pages are like legal documents, at first they are difficult to read but once you choke down a few you get the hang of it. Do you have dial up or do you have DSL? The two are a bit different with respect to configuration. I believe there is a section for configuring both in the Running Linux book. 4 Printer: I would recommend using the cups printer daemon. It replaces the old lp/lpd/lpr progs and has a much better configuration. There are scores of drivers, including ones for the latest printers. If it is not installed by default there is a package available. Cups supports almost all HP printers deskJet and laserJet. Wow that was a mouthful, I hope this ans most of your questions. Talk you soon.. Matt

Oct. 8, 2003

Re: [Wlug] I choose Slackware.. God help me! (And you guys, please?)

by Matt Higgins

Brian, Great post! Pleas excuse me for my lack of poetic sensablility throught this response. Fisrt I would like to commend you on your choice of Slackware, a fantastic distrobution with a lot to offer and wonderfull history.

Oct. 8, 2003