May 2001 - WLUG - wlug.mailman3.com

RE: [Wlug] Compaq deskpro

by Bob Brown

Check out http://www.tru64unix.compaq.com/linux/documentation.htm It may be the X configuration settings. What monitor are you using? The MBR on many Compaq PCs point to a diagnostic partition that contains some basic utilities. I have my Armada 7400 set up for RH Linux and Windows. My MBR points to the Compaq diagnostic partition. I originally removed that partition without a problem. However, I later decided the diagnostics were worth 12/15 MBs. I used the Compaq diagnostic floppy (or download from their site) to create the diagnostic partition and load the diagnostics. Linux fdisk knows about the Compaq partition. Bob -----Original Message----- From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On Behalf Of Jim Stith Sent: Thursday, May 17, 2001 11:09 AM To: wlug(a)mail.wlug.org Subject: [Wlug] compaq deskpro well here goes... i got an old compaq deskpro (yes, a stupid mistake... but it was cheap) and wanted to load red hat 7.0 on it and possibly use the deskpro as a intranet server so that i could learn how to set a server up. everything loads fine but when the system tries to go into x and give me a login screen, the monitor makes a poping sound and the screen goes blank. same thing with mandrake and caldera. the screen stays blank. i have gone into the bios and disabled pnp and energy saver but that does not help. i have been going through the faq's and the only thing i have found out is that compaq did some strange things around the mbr. i have no other options open to me and would appreciate any help anyone can give concerning this. thanks jim s. _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 17, 2001

Re: [Wlug] compaq deskpro

by Scott Venier

well, it sounds to me like your monitor is the problem. It probably doesn't support the resolution you're trying to drive it at. Hit Crtl-Alt-F1, log in as root, type 'init 3', run the Xconfigurator (I think that's still in redhat 7) and pick a lower resolution and/or refresh rate. And next time, be sure to click the "Test This Configuration" button in the installer. :) Scott On Thu, 17 May 2001, Jim Stith wrote: > well here goes... i got an old compaq deskpro (yes, a stupid mistake... > but it was cheap) and wanted to load red hat 7.0 on it and possibly use > the deskpro as a intranet server so that i could learn how to set a > server up. > > everything loads fine but when the system tries to go into x and give me > a login screen, the monitor makes a poping sound and the screen goes > blank. > > same thing with mandrake and caldera. > > the screen stays blank. i have gone into the bios and disabled pnp and > energy saver but that does not help. > > i have been going through the faq's and the only thing i have found out > is that compaq did some strange things around the mbr. > > i have no other options open to me and would appreciate any help anyone > can give concerning this. > > thanks > > jim s. > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 17, 2001

compaq deskpro

by Jim Stith

well here goes... i got an old compaq deskpro (yes, a stupid mistake... but it was cheap) and wanted to load red hat 7.0 on it and possibly use the deskpro as a intranet server so that i could learn how to set a server up. everything loads fine but when the system tries to go into x and give me a login screen, the monitor makes a poping sound and the screen goes blank. same thing with mandrake and caldera. the screen stays blank. i have gone into the bios and disabled pnp and energy saver but that does not help. i have been going through the faq's and the only thing i have found out is that compaq did some strange things around the mbr. i have no other options open to me and would appreciate any help anyone can give concerning this. thanks jim s.

May 17, 2001

Re: [Wlug] newbie seeks help with kernel upgrade

by Chad Pytel

> libdb-3 is in the db3 package. This is not easy to determine, > unfortunately. The Red Hat up2date service can figure this out > automatically, I believe. I find that http://www.rpmfind.net works well for finding the rpm that provides a a certain executable or library. For example, if you go there and type in 'libdb-3' into the search box, it'll come up with a list of RPM's for different distributions and versions that provide that library - then you just have to pick the most recent one (or the version you need) for your distribution. -Chad +--[ Chad Pytel ]----------------------------------+ (508)756-1329 http://www.chadpytel.com +-------------------------------[ cpytel(a)wpi.edu ]-+ On Thu, 17 May 2001, Charles R. Anderson wrote: > On Thu, 17 May 2001, Dan Crooks wrote: > > dancro> While trying to install the kernel upgrade with rpm I > dancro> received error messages: 1) failed dependencies: > dancro> rpmlib(PayloadFilesHavePrefix) <= 4.0.1 is needed by > dancro> kernel-2.2.19-6.2.1 2) mount < 2.10r conflicts with > dancro> kernel-2.2... 3) nfs-utils < 0.3.1 conflicts with > dancro> kernel-2.2... > dancro> > dancro> Where can I find libdb? How could I determine that for > dancro> myself if I run into another dependency? > > libdb-3 is in the db3 package. This is not easy to determine, > unfortunately. The Red Hat up2date service can figure this out > automatically, I believe. > > You shouldn't need the --replacefiles option to rpm. A conflict usually > means you should use the -U option to rpm so the package is Upgraded, > instead of Installed. Here is the order you will need to follow for the > kernel upgrade. I'm doing this from memory, so I may have forgotten some > dependencies. > > First upgrade rpm. You really should upgrade to all the latest packages > in the Red Hat updates tree, since many security problems are fixed and > the latest packages are required for other updates, as you have > discovered. For instance, I believe there is a new gnorpm that works with > the new rpm-4.0.2. > > The -F option means to only upgrade if an older package of the same name > is already installed (Freshen). > > rpm -Uvh db3-*3.1.17-4.6x.i386.rpm > rpm -Fvh rpm-*4.0.2-6x.i386.rpm popt-1.6.2-6x.i386.rpm > > rpm --rebuilddb (to convert to rpm 4 database files) > > Now install files required by the new kernel: > > rpm -Fvh mount-2.10r-0.6.x.i386.rpm nfs-utils-0.3.1-0.6.x.1.i386.rpm > > Upgrade all the kernel packages except the main one and smp one: > > rpm -Fvh kernel-BOOT-2.2.19-6.2.1.i386.rpm > kernel-doc-2.2.19-6.2.1.i386.rpm kernel-headers-2.2.19-6.2.1.i386.rpm > kernel-ibcs-2.2.19-6.2.1.i386.rpm kernel-pcmcia-cs-2.2.19-6.2.1.i386.rpm > kernel-source-2.2.19-6.2.1.i386.rpm kernel-utils-2.2.19-6.2.1.i386.rpm > > Now choose the right main kernel package for your architecture (i386, > i586, i686, regular or smp), and install that (don't upgrade it so you can > keep the old one around if the new one gives you problems). The i586 and > i686 versions are in their own subdirectories of the updates tree, not in > the i386 subdirectory. > > rpm -ivh kernel-2.2.19-6.2.1.i686.rpm > > (notice the -i option to install instead of upgrade. This leaves the > older versions around for emergencies.) > > Edit /etc/lilo.conf and make a new stanza and edit it for the new version > (copy a stanza from another one in the file). Make sure to change the old > stanza(s) to different labels (like linux.old or something): > > image=/boot/vmlinuz-2.2.19-6.2.1 > label=linux > initrd=/boot/initrd-2.2.19-6.2.1.img > read-only > root=/dev/hda2 > > If you have an initrd line in lilo.conf that isn't empty, you need to > create a new initial ram disk: > > /sbin/mkinitrd /boot/initrd-2.2.19-6.2.1.img 2.2.19-6.2.1 > > Re-run lilo: > > /sbin/lilo > > Now you should be set to "shutdown -r now" and boot the new kernel. > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 17, 2001

Re: [Wlug] newbie seeks help with kernel upgrade

by Charles R. Anderson

On Thu, 17 May 2001, Dan Crooks wrote: dancro> While trying to install the kernel upgrade with rpm I dancro> received error messages: 1) failed dependencies: dancro> rpmlib(PayloadFilesHavePrefix) <= 4.0.1 is needed by dancro> kernel-2.2.19-6.2.1 2) mount < 2.10r conflicts with dancro> kernel-2.2... 3) nfs-utils < 0.3.1 conflicts with dancro> kernel-2.2... dancro> dancro> Where can I find libdb? How could I determine that for dancro> myself if I run into another dependency? libdb-3 is in the db3 package. This is not easy to determine, unfortunately. The Red Hat up2date service can figure this out automatically, I believe. You shouldn't need the --replacefiles option to rpm. A conflict usually means you should use the -U option to rpm so the package is Upgraded, instead of Installed. Here is the order you will need to follow for the kernel upgrade. I'm doing this from memory, so I may have forgotten some dependencies. First upgrade rpm. You really should upgrade to all the latest packages in the Red Hat updates tree, since many security problems are fixed and the latest packages are required for other updates, as you have discovered. For instance, I believe there is a new gnorpm that works with the new rpm-4.0.2. The -F option means to only upgrade if an older package of the same name is already installed (Freshen). rpm -Uvh db3-*3.1.17-4.6x.i386.rpm rpm -Fvh rpm-*4.0.2-6x.i386.rpm popt-1.6.2-6x.i386.rpm rpm --rebuilddb (to convert to rpm 4 database files) Now install files required by the new kernel: rpm -Fvh mount-2.10r-0.6.x.i386.rpm nfs-utils-0.3.1-0.6.x.1.i386.rpm Upgrade all the kernel packages except the main one and smp one: rpm -Fvh kernel-BOOT-2.2.19-6.2.1.i386.rpm kernel-doc-2.2.19-6.2.1.i386.rpm kernel-headers-2.2.19-6.2.1.i386.rpm kernel-ibcs-2.2.19-6.2.1.i386.rpm kernel-pcmcia-cs-2.2.19-6.2.1.i386.rpm kernel-source-2.2.19-6.2.1.i386.rpm kernel-utils-2.2.19-6.2.1.i386.rpm Now choose the right main kernel package for your architecture (i386, i586, i686, regular or smp), and install that (don't upgrade it so you can keep the old one around if the new one gives you problems). The i586 and i686 versions are in their own subdirectories of the updates tree, not in the i386 subdirectory. rpm -ivh kernel-2.2.19-6.2.1.i686.rpm (notice the -i option to install instead of upgrade. This leaves the older versions around for emergencies.) Edit /etc/lilo.conf and make a new stanza and edit it for the new version (copy a stanza from another one in the file). Make sure to change the old stanza(s) to different labels (like linux.old or something): image=/boot/vmlinuz-2.2.19-6.2.1 label=linux initrd=/boot/initrd-2.2.19-6.2.1.img read-only root=/dev/hda2 If you have an initrd line in lilo.conf that isn't empty, you need to create a new initial ram disk: /sbin/mkinitrd /boot/initrd-2.2.19-6.2.1.img 2.2.19-6.2.1 Re-run lilo: /sbin/lilo Now you should be set to "shutdown -r now" and boot the new kernel.

May 17, 2001

sorry about that

by Dan Crooks

I put it on the WLUG WWWBoard, where it obviously belongs. Sorry for the inconvenience. -- Thank you, Dan Crooks

May 17, 2001

newbie seeks help with kernel upgrade

by Dan Crooks

Hi, and thank you in advance for your patience. This deals with upgrading kernel In attempting to install vmware 2.0 in Red Hat 6.2, I was notified that I needed an upgrade to RH6.2 kernel. While trying to install the kernel upgrade with rpm I received error messages: 1) failed dependencies: rpmlib(PayloadFilesHavePrefix) <= 4.0.1 is needed by kernel-2.2.19-6.2.1 2) mount < 2.10r conflicts with kernel-2.2... 3) nfs-utils < 0.3.1 conflicts with kernel-2.2... I understand that I can ignore the conflicts (2,3) by specifying --replacefiles in the rpm command. I decided to upgrade rpm assuming that rpmlib would be included. Using gnorpm I downloaded rpm 4.0-4 and received another error: only packages with major numbers <=3 are supported by this release of rpm. Presumably this message is issued by the currently version of rpm 3.0.4-0.48. This may be a red herring and not important as I continued. I used ncftp to download by specifying "mget rpm-*.rpm" and received four files rpm-4.0.2-6x.i386.rpm, also -build-, -devel-, -python- from RH site. When I tried to install rpm-4.0.2-6x I received an error: failed dependency libdb-3.1.so. Where can I find libdb? How could I determine that for myself if I run into another dependency? Do you have any suggestions/recommendations regarding updating kernel? I am using instructions retrieved from RH titled "Upgrading the Linus Kernel on Red Hat Linux systems" by Red Hat Support last updated 2000 May 17 -- Thank you, Dan Crooks

May 17, 2001

REMINDER: Meeting Wednesday, May 16th, 7:00 PM

by Andy Stewart

Hi everybody, This is a reminder about the upcoming WLUG meeting, to be held in Kinnicutt Hall (a.k.a the usual place) at WPI at 7:00 PM on Wednesday, May 16h. The topic for discussion will be the practical use of IPCHAINS. What does that mean? This meeting, Doug Waud and I will present to you ways to use IPCHAINS to implement a firewall. This is not theory, this is practice...what to type, what it does, and why. This talk will build on the more detailed information presented by Bob Ziegler at our last meeting. Doug will start with a presentation of the simpler case of getting a firewall up which supports masquerading (that is, getting multiple machines on your home network to share one IP address, as you would for cable modem, for example), e-mail, and browsing. I will follow up with more detailed examples of IPCHAINS code from my own firewall script for allowing certain services through the firewall to the home network. Although firewalling is a complex topic, we're hoping to distill out of that complexity enough information so that a person can get started toward implementing a secure firewall. I'm looking forward to a good turnout at this meeting. Come on down! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

May 14, 2001

RE: [Wlug] charter.net & ssh

by Bill Mills-Curran

Charles, Answers below... On Thu, 10 May 2001, Charles R. Anderson wrote: > Date: Thu, 10 May 2001 15:02:41 -0400 (EDT) > From: Charles R. Anderson <cra(a)WPI.EDU> > Reply-To: wlug(a)mail.wlug.org > To: "'wlug(a)mail.wlug.org'" <wlug(a)mail.wlug.org> > Subject: RE: [Wlug] charter.net & ssh > > Are you doing uni-directional NAT on the Linksys? Are there any firewall > rules defined on the Linksys? Yes, at least I believe that's it. When I was testing, I configured port 22 to translate to my internal address. > > In addition to allowing packets from outside to port 22 on your SSH > server, do you allow outgoing packets from your SSH server on port 22 to > local ephemeral ports (1024-65535) on the outside clients? I believe that all outgoing packets are passed & translated by default. (I've never heard them called ephemeral. I've always called them transient.) Thanks, Bill

May 10, 2001

RE: [Wlug] charter.net & ssh

by Charles R. Anderson

Are you doing uni-directional NAT on the Linksys? Are there any firewall rules defined on the Linksys? In addition to allowing packets from outside to port 22 on your SSH server, do you allow outgoing packets from your SSH server on port 22 to local ephemeral ports (1024-65535) on the outside clients? Traceroute also uses either ICMP (Windows) or UDP+ICMP (Unix) to high numbered ports. On Thu, 10 May 2001, Bill Mills-Curran wrote: bcurra> It never makes it. BTW, if you're looking to try this bcurra> yourself, I've turned off the forwarding on my router. I bcurra> probably should have left it on so that I could work with bcurra> the Charter people. bcurra> 13 24-216-218-3.hsacorp.net (24.216.218.3) 5.489 ms 5.842 ms 6.198 ms bcurra> 14 10.254.1.2 (10.254.1.2) 6.192 ms 9.664 ms 6.756 ms

May 10, 2001