http://forums.suselinuxsupport.de/index.php?showtopic=7568 This one elaborates a bit more. On Sun, 14 Nov 2004 18:34:59 +0000, martin mcleod wrote:

http://forums.suselinuxsupport.de/index.php?showtopic=8187

Try this thread.Careful with spelling by poster.It's Packman.

On Sun, 14 Nov 2004 16:57:25 +0000, michael norman wrote:

...

Recently somebody gave a link describing how to add Packman as a source to yast which I though i'd kept. Have now lost it and can't find it again, my googling skills not being that good, could someone repeat it for me please.

Thanks

Mike

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

hi- Has anyone else been having problems with write speeds across the network with SuSE 9.2? Is there some sort of network write/transfer limit setup on 9.2? I mean it's really weird. I can share a drive from the 9.2 box, NFS mount it onto a second box and do scp transfers from a 3rd box to the 2nd box and things seem to go ok. When I do an scp directly onto the 9.2 box, it usually stalls at a round 132k. I got one scp of a large file to complete to the 9.2 box. A 2.2meg file across a 100BaseT network took 1:35 That's NOT right. Sending to another box took only 0.424 seconds. FTP, basically does the same thing. Now, I'm not a network admin, but I can tell you that this problem DOES NOT exist on the 9.1 boxes we have, nor on the RHAS 3 boxes. Any ideas? BTW, some of the disks on the 9.2 box are standard partitions with reiserfs on them and some are logical volumes with reiserfs on them. ethtool on the network card shows Speed: 100Mb/s Duplex: Full so, that looks good. I don't think this is a NIC card issue because the network based NFS mount writes seem to be working. thanks, brian -- Brian Jackson Photo Sports ~ Editorial ~ People ~ Travel ~ Events http://www.BrianJacksonPhoto.com

On Tuesday 16 November 2004 00:21, Johan Nielsen wrote:

Tirsdag 16 november 2004 01:49 skrev Brian Jackson:

...

hi-

Has anyone else been having problems with write speeds across the network with SuSE 9.2?

YES ....

and

Plz start a seperate thread for this issue.

Umm, I did start a separate thread.

And do provide info on you motherboard / chipset / NIC.

Here's the NIC card I was using. 11: PCI 0b.0: 0200 Ethernet controller [Created at pci.243] Unique ID: gZD2.IQxIdIhhuH7 SysFS ID: /devices/pci0000:00/0000:00:0b.0 SysFS BusID: 0000:00:0b.0 Hardware Class: network Model: "Realtek RT8139" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8139 "RTL-8139/8139C/8139C+" SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." SubDevice: pci 0x8139 "RT8139" Revision: 0x10 Driver: "8139too" I/O Ports: 0xb800-0xb8ff (rw) Memory Range: 0xf2800000-0xf28000ff (rw,non-prefetchable) IRQ: 11 (8515285 events) HW Address: 00:40:f4:6e:dc:d3 Driver Info #0: Driver Status: 8139too is active Driver Activation Cmd: "modprobe 8139too" Config Status: cfg=no, avail=yes, need=no, active=unknown I switched to the onboard NIC and things were great after that. I was using the PCI network card because that's the way the system was setup by the previous admin, so I assumed there was a reason for not using the onboard card. Funny thing is that I have the Realtek card in another system (suse 8.2) and it works like a champ. Hmm... oh well. thanks, brian -- Brian Jackson Photo Sports ~ Editorial ~ People ~ Travel ~ Events http://www.BrianJacksonPhoto.com

On Tuesday 16 November 2004 22:34, Vince Littler wrote:

On Tuesday 16 November 2004 8:25 pm, Brian Jackson wrote:

...

On Tuesday 16 November 2004 00:21, Johan Nielsen wrote:

...

Plz start a seperate thread for this issue.

Umm, I did start a separate thread.

You thought you did, but actually you started composing your email by replying to a random mail on another topic and then clearing out the Subject and body, thinking that is sufficient. If you do this, many people will know that this is what you have done, because for their email client it will appear in the thread you randomly chose to reply to.

What happens is that every reply contains information that refers to the message you "replied" to: the 'References' header and the 'In-Reply-To' header. These are from the message I replied to: References: <200411141657.25620.michaeltnorman@ukfsn.org> <200411160921.01491.yep@osterbo-net.dk> <200411161225.58978.brian@brianjacksonphoto.com> In-Reply-To: <200411161225.58978.brian@brianjacksonphoto.com> (actually they are just two lines) Whith this information, several newsreaders (KMail) can display messages in a tree like way: Subject1 | +-- Re: Subject1 | +-- Some different subject that does not belong here | +-- Re: Subject1 I like this very much. Sometimes people (yes, me too) get a bit upset if the threading is disrupted by a 'thread-hijacker'. ;) The way I prevent myself from hijacking threads is: In KMail, I click on the email-address of the list that usually is displayed in the 'To:' header of the mail I'm viewing. In KMail this is click-able, and a click opens a 'New email' with the right address already inserted.

People will tell you that you have hijacked a thread, but never actually explain how they know or why this is bad. There, I have said too much already.

Vince: I don't think you said too much. Perhaps it is good to explain this once in a while. :) Cheers, Leen