Remote printer failures with 8.0
Since upgrading to 8.0, I can no longer print to a remote printer using either LPD or CUPS. In either case, what looks like a flow control problem causes raw printer code to be printed as ASCII. I'm using the gimp-print driver to connect with an Epson C80 via a print server. Anyone have similar problems or ideas on how to fix this? Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Looking for Partion Magic
Hope you find it used cheap, as you can buy it new for under $30: http://shopping.yahoo.com/shop?d=z&id=1990927233&clink=dmks/partition_magic/ctx=mid:5,pid:1990927233,pdid:5,t:3,ht:1,loc:,pos:0,spc:14489115,date:20030204,srch:kw&cf=9 I'm betting you will use Partition Magic more than once -- it's saved my system a few times over the years, and is well worth the money. Tom On Tue, 2003-02-04 at 08:05, John Nall wrote: > (Hope it is not out of line to send this. If it is, I apologize) > > I need to partition my HD on my Windows XP machine so that I can put Linux > on it. Because it uses the NTFS format it appears that the only way I am > going to be able to partition it is to use the software product "Partition > Magic." I kind of hate to buy a new copy just to do that one partition and > then probably never use it again. > > So: Is there anyone who already has Partition Magic and no longer needs > it, so that they might consider selling it to me? If so, please reply > off-line. > > Thanks, > > John > [EMAIL PROTECTED] > -- Tom Ball <[EMAIL PROTECTED]> -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: In a pickle with updating
On Fri, 2003-02-21 at 06:07, Harry Putnam wrote: > I've gotten myself into quite a pickle with todays attempt to update. One can imagine that must have been a very big pickle for you to be able to climb into it! :-) These messages go out to an international audience. While the English expertise of all posters on this list is very good, idioms in any language are usually the last to be learned, and therefore their use should be generally avoided. Otherwise you risk not getting help from the very expert you hope to reach. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: C++
On Mon, 2003-02-24 at 09:35, Thomas Dodd wrote: > I check the C++ books I had lying around and couldn't find forward > declaration. > > After the mention here, I was looking at some other code and saw it used. > Now, why didn't I see that in the code before? :( Because an important aspect of good OO design is to keep classes as loosely coupled as possible. Having two classes directly reference each other like you described indicates a potential refactoring may be needed. A good book to consider reading is "Pattern Hatching" by John Vlissides; his initial example of designing an OO filesystem abstraction sounds very similar to what your example was trying to solve, only he demonstrates several ways that design can be improved and why those changes are necessary. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Ext3 vs Ext2
I found ext3 much slower on my laptop when it was first installed. However, after adding "data=writeback" to the /etc/fstab settings for /, my system is now "fast enough". Tom On Mon, 2003-03-10 at 19:01, JD wrote: > Hallo list, > I have a "feeling" that ext3 is much slower than ext2. My hadrdrive > blinks more often after I let RH8 formatted it with its favorite ext3; > not to mention the noise from the harddrive rotation. > As I said, it's just a "feeling" so please don't flame me for feeling it. > Am I justified anyway? Is it true that ext3 fs is somehow inferior in > practice that ext2? > JD -- Tom Ball <[EMAIL PROTECTED]> -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: SV: Spam ? (RH9)
On Mon, 2003-03-24 at 14:44, Marie-Thérèse Lorentzen wrote: > I'm no expert in the area, however, my understanding of upgrades is that the > general convention for at hop from on number to another would be a 'major' > change in a kernal/a new look/ or something that separates it from the > previous number/numners. If the hop is several numbers, then this would > indicate an even greater change. A "dot" change/update/upgrade is generally > for less significant changes. As someone else commented, a release number is just that, a number created by marketing. Often they choose numbers based on the reasoning you state above, other times contracts determine it, but there is no convention. As long as a release number encourages you to upgrade, the marketing drones have done their job, regardless of how unfathomable their choice is to those of us with basic math skills. :-) Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Kernel panic with ext3 root set to writeback
Has anyone been able to boot Red Hat 8.0 with an ext3 root device with it set to writeback mode? When I add bootflags=mode=writeback to my kernel line in Grub, the kernel panics because it doesn't recognize the option. It looks like the kernel first mounts the drive as a ext2, then quickly switches over to ext3. The problem appears to be it checking the bootflags before making the switch. Any ideas on how to fix this? I'd really like to get some disk speed back, lost when I upgraded to ext3. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Kernel panic with ext3 root set to writeback
On Thu, 2002-12-19 at 23:26, Kevin McConnell wrote: > --- Tom Ball <[EMAIL PROTECTED]> wrote: > > Has anyone been able to boot Red Hat 8.0 with an > > ext3 root device with > > it set to writeback mode? When I add > > bootflags=mode=writeback to my > > kernel line in Grub, the kernel panics because it > > doesn't recognize the > > option. > > Where did you read about the writeback feature? Can we > look at your grub.conf file? Have you tried putting > this in your grub.conf file? Here's the link: http://www-106.ibm.com/developerworks/linux/library/l-fs8.html?dwzone=linux Here's my grub entry: title Red Hat Linux (2.4.18-18.8.0) - Home root (hd0,5) kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ rootflags=mode=writeback initrd /boot/initrd-2.4.18-18.8.0.img As someone previously suggested, I also tried adding this information to /etc/fstab, with the same panic. BTW, the writeback option support is in (search for "writeback"): file:///usr/src/linux-2.4/fs/ext3/super.c and its use is in: file:///usr/src/linux-2.4/fs/ext3/fsync.c Thanks in advance for any pointers. Builds sure slowed down when I upgraded to 8.0, and I'm hoping this will improve things a bit. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Kernel panic with ext3 root set to writeback
On Fri, 2002-12-20 at 12:05, Bill Rugolsky Jr. wrote: > On Fri, Dec 20, 2002 at 09:12:26AM -0800, Tom Ball wrote: > > title Red Hat Linux (2.4.18-18.8.0) - Home > > root (hd0,5) > > kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ rootflags=mode=writeback > > initrd /boot/initrd-2.4.18-18.8.0.img > > > > As someone previously suggested, I also tried adding this information to > > /etc/fstab, with the same panic. > > That's supposed to be > > rootflags=data=writeback You're right -- in reporting the problem I dummied up my grub entry since I had removed the problem entry. What you wrote is what I originally used, per that article. To be clear: specifying "rootflags=data=writeback" causes the kernel panic. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Kernel panic with ext3 root set to writeback
On Sat, 2002-12-21 at 05:57, Arjan van de Ven wrote: > > To be clear: specifying "rootflags=data=writeback" causes the kernel > > panic. > > it's also the wrong thing to do: the initrd mounts your root filesystem, > not the kernel. So the mount flag need to be set within the initrd, and > afaik, mkinitrd just uses /etc/fstab to copy the flags AT CREATION TIME > of the initrd. That fixed it. The steps to enable ext3's writeback mode are: 1. add "data=writeback" to /'s flags in /etc/fstab; 2. mkinitrd; and 3. update grub.conf to point to the new initrd image. It's probably a bug that the flags have to match in fstab and its initrd copy, but I don't care because it works! Thanks, everyone (especially Arjan) for your help and patience. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Much Slower than 7.2?
On Mon, 2002-12-23 at 10:00, Ronald W. Heiby wrote: > I've got a large data compilation application. It takes in a very > large quantity of text data and produces a resulting binary file that > is about 1.3 GB. In the mean time, it holds on the order of 2 GB of > data in memory while operating on it to produce the output file. I also found 8.0 much slower for my smaller builds. One thing that's different in 8.0 is the ext3 filesystem, which I converted to when upgrading. By default it runs in ordered data mode, which causes writes to disk to happen much more frequently than on ext2 filesystems. This is normally a goodness, because if your system crashes it takes much less time to reboot with a working filesystem. For a build system, however, it's okay to crash in the middle of a build because it is (or should be) easy to start over with a clean data set. The ext3 filesystem supports a writeback mode which works well for me. To turn writeback on, you need to add "data=writeback" to the build partition's flags in fstab. IMPORTANT: if you are setting the root partition, you need to run /sbin/mkinitrd so your initrd file has the same setting (either overwrite the one in /boot, or create a new one and change your grub or lilo file to point to it). Keep a rescue disk handy when you commit these changes! Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Much Slower than 7.2?
On Mon, 2002-12-23 at 20:08, Tim Spence wrote: > What about the different compiler versions? Is the new gcc in rh8 slower? Don't know: I was building NetBeans using javac, which didn't change. Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Re: Java ?
Sun and Blackdown work very closely together: Blackdown does the "raw" Linux port of Java from Sun's common source base, which Sun then packages, tests and distributes. If you want to tinker with the runtime, fix bugs or have a strong licensing religion then use Blackdown's version; if you want something stable and in wide use, use Sun's. BTW, the SDK download includes the JRE, so only one download is necessary. Tom On Wed, 2003-01-01 at 11:49, Mark Guzzo wrote: > Happy New Year ! > > I'm in the process of downloading the j2re-1_4_1_01 and the > j2sdk-1_4_1_01 from SUN, and was wondering which is "better", Sun's or > Blackdown? > > Just wondering ... :-) > > > -- > > > Mark Guzzo > > Sair LCA, LCP -- Tom Ball <[EMAIL PROTECTED]> -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
Rpmbuild question
Is there an easier way to install source for a module so that I can debug with it? Installing the source RPM, bunzip'ing the source bundle and then untar'ing it to a directory works, but this seems like a common-enough situation that there should be an option to do this in rpmbuild. A related question: is there a way to build a debug version of a module using rpmbuild? Thanks in advance, Tom -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list
