- WLUG - wlug.mailman3.com

RealPlayer and Linksys

by Michael Long

I have configured several boxes at home behind a Linksys router #BEFSR81. Both my windoze and linux boxes are able to connect through the router however Realaudio only connects through the router successfully on my windoze box. On the linux box I have installed it successfully but cannot get get it to connect through the router. What should I be looking at in order to solve this? I tried looking at preferences and tried Auto-Configure to no avail. Unfortunately I do not know what RTSP or PNA is or how to use it. Any help will be greatly appreciated. thx, mike

May 19, 2001

Re: [Wlug] Shifting partitions

by Charles R. Anderson

On Fri, 18 May 2001, Brad Noyes wrote: brad> resize partitions. It only runs on windows, but has the brad> ability to manipulate ext2 filesystems. Hope this helps, Partition Magic can be run directly from it's own boot disk as well, which is useful if you don't have Windows installed.

May 19, 2001

Re: [Wlug] Shifting partitions?

by Brad Noyes

Hi, I'm too clear on what you are looking for, so i'm guessing that you want to resize/move a partition. In that case, you may be interested in looking at gnu-parted. A free program that can resize/move partitions. It has a rough interface from what i remember, but it got the job done for me. If you are looking for an easy to use solution there is partition magic, which is a commercial product, that can resize partitions. It only runs on windows, but has the ability to manipulate ext2 filesystems. Hope this helps, On Friday 18 May 2001 12:58, gwlt(a)ma.ultranet.com wrote: > A fast question: > Anyone have experience with the stability of and general > wisdom of shifting the Linux partition on a hard drive on > a dual boot machine? I am trying to upgrade to a newer > kernel and am presented with not enough memory on the > Linux side of the drive. > Encountered error message: > <<An error occurred. Tour system has not enough space > left for installation or upgrade (366821583>188726600)>> > If the endeavor is too risky I can sacrifice the current > Linux install, wipe the partition and install from > scratch. (That does undermine the whole benefit of > purchasing the proprietary upgrade package though.) > Thanks. > Colin ---------------------------------------- Content-Type: application/rtf; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: base64 Content-Description: filename="text1.rtf" ----------------------------------------

May 19, 2001

Shifting partitions?

by gwlt＠ma.ultranet.com

A fast question: Anyone have experience with the stability of and general wisdom of shifting the Linux partition on a hard drive on a dual boot machine? I am trying to upgrade to a newer kernel and am presented with not enough memory on the Linux side of the drive. Encountered error message: <<An error occurred. Tour system has not enough space left for installation or upgrade (366821583>188726600)>> If the endeavor is too risky I can sacrifice the current Linux install, wipe the partition and install from scratch. (That does undermine the whole benefit of purchasing the proprietary upgrade package though.) Thanks. Colin

May 18, 2001

Re: [Wlug] compaq deskpro

by doug waud

Hi > 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. As several responses have indicated already, you are probably driving the monitor at the wrong frequency. This can be very dangerous (you can cook a monitor this way) but perhaps not in your case since that "popping sound" is probably the monitor being new enough to cut itself off when mistreated. In any case, what you have to do is find out the allowable hsync and vsync frequencies of the monitor. Since the computer is second hand (I assume) you may not have the manual. In that case, look on the monitor for some sort of manufacturer/model number and feed that into google. With luck and a bit of poking around you should be able to find a spec sheet or table and get the hsync and vsync frequencies (I found Compaq was not too shabby when faced with the same issue with my daughter's computer and a Linux install). Once you have those values, you can tell the install program what to use (I don't use Red Hat, so I can't give you chapter and verse here; XF86Config is more generic but a tad cryptic. If you have to go the latter route, feel free to touch base with me (probably directly to save traffic to the whole group) and we can, if necessary, walk through the various steps in XF86Config. Incidentally, I vaguely remember that my daughter's Compaq (a Presario) had a bastard video chip which confused SuSE 6.3 but which 7.0 was able to deal with. I suspect your box is old enough that this will not be a problem. Finally, Compaq is good about providing manuals. I went into google and entered compaq deskpro and got to the Compaq site which, in turn, had a link to a downloadable pdf manual. I suspect you may have to be a bit more specific as to model of compaq deskpro but you should be able to get the equivalent for your particular box. Ditto for monitor. This way you can give the install program hints as to both the video chip and the sync frequencies. Hope this helps a little. > 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 don't think this is anywhere near the mbr. doug PS I agree with John Huber's point that X is unnecessary (and perhaps even in the way) on a server. However, I can also understand why you might want to get X going simply because, like Mount Everest, it's there :-) -- Douglas R Waud 17 Lantern Lane, Shrewsbury, MA, 01545-2006 http://www.ummed.edu/pub/d/drw/

May 18, 2001

Re: [Wlug] compaq deskpro

by Josh Huber

Jim Stith <stith2(a)earthlink.net> writes: [snip] In addition to what other people are saying, I have to ask -- why would you want to install X on a server? Save disk space, save memory, and keep things simple. If the console works, just use it. :) -- Josh Huber

May 17, 2001

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