devel September 2003

devel@lists.fedoraproject.org

139 participants
90 discussions

LVM PE size and Anaconda
by Jos Vos 07 Sep '03

07 Sep '03

Hi, Is the possibility to set the PE size of a LVM VG at installation time planned (also in kickstart)? I am facing the 256 GB limit of a LV after installing RHL and the PE size can only be set at VG creation time... Thanks, -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204

3 2

RSH Tools
by Chuck Wolber 05 Sep '03

05 Sep '03

Why haven't the RSH tools been removed from the current Beta distribution? -Chuck -- Quantum Linux Laboratories - ACCELERATING Business with Open Technology * Education | -=^ Ad Astra Per Aspera ^=- * Integration | http://www.quantumlinux.com * Support | chuckw(a)quantumlinux.com

9 11

Re: RSH Tools
by Nils O. Selåsdal 05 Sep '03

05 Sep '03

On Thu, 2003-09-04 at 21:39, Chuck Wolber wrote: > > > Why haven't the RSH tools been removed from the current Beta > > > distribution? > > > > Because that would be a bad move... > > > > Lots of software assumes that those utilities are available. For > > example, the Informix database cluster utilities automatically invoke > > rsh. > > Indeed. I meant the post more as a troll to see what sort of issues would > be raised. So far I haven't seen anything that, at least at first glance, > couldn't be done with ssh and a symbolic link. Is the issue: > > 1) Users who can't or won't change? I have to boot some silly boxes running vxworks. It uses rsh and similar to log onto the boot server to fetch files it needs. Please don't remove rsh ;) -- Vennlig hilsen/Best Regards Nils Olav Selåsdal System Engineer UtelSystems a/s w w w . u t e l s y s t e m s . c o m

1 0

Howto use "splittree.py" tools?
by Steven Wang 05 Sep '03

05 Sep '03

Hai everyone I want to recreate redhat 9.0.93,but I don't know how to use "splittree.py" tools,does it can auto build 6 redhat iso discs? 　　　　　　　　Steven Wang 　　　　　　　　wzhjbj(a)ccoss.com.cn 　　　　　　　　　　2003-09-05

1 0

RH 2.4.18 vs RH 2.4.20 performance slowdown
by Dax Kelson 04 Sep '03

04 Sep '03

We have a room full of *identical* boxes that we have run Red Hat Linux classes (6.x, 7.x, 8.0 and 9) on over the past 4 years. These are 500Mhz Intel 440BX motherboard boxes. No problems until RHL9 came out. On about 50% of the machines (identical hardware remember, including BIOS settings) kernel system calls on RH 2.4.20 kernels run about 4x - 10x slower. Of course with this problem the whole system runs dog slow and is painful to use. The vanilla kernel.org kernels and the RH 2.4.18 kernels (from RHL8.0) do NOT exhibit the slowdown. The problem can be easily quantified using strace. Take a look at the following (especially the third column): First with vanilla ftp.kernel.org 2.4.20 compiled using kernel-2.4.20-i686.config from RH. [root@station9 root]# uname -r 2.4.20 [root@station9 root]# strace -c ls -al /etc > /dev/null execve("/bin/ls", ["ls", "-al", "/etc"], [/* 30 vars */]) = 0 % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 41.25 0.002895 10 289 lstat64 12.92 0.000907 36 25 read 12.61 0.000885 22 41 14 open 5.34 0.000375 21 18 readlink 5.27 0.000370 12 31 old_mmap 5.14 0.000361 52 7 getdents64 5.06 0.000355 15 23 munmap 2.82 0.000198 7 30 close 2.11 0.000148 5 28 fstat64 1.44 0.000101 3 31 fcntl64 1.44 0.000101 51 2 socket 1.42 0.000100 50 2 2 connect 1.27 0.000089 5 17 brk 0.80 0.000056 56 1 mmap2 0.57 0.000040 8 5 write 0.19 0.000013 4 3 2 rt_sigaction 0.17 0.000012 4 3 3 ioctl 0.13 0.000009 9 1 uname 0.06 0.000004 4 1 gettimeofday ------ ----------- ----------- --------- --------- ---------------- 100.00 0.007019 558 21 total Now the latest RHL9 errata kernel. All RHL9 kernels and RHL8.0 kernels >= 2.4.20 perform the same: [root@station9 root]# uname -r; strace -c ls -al /etc > /dev/null 2.4.20-20.9 execve("/bin/ls", ["ls", "-al", "/etc"], [/* 30 vars */]) = 0 % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 43.57 0.019390 67 289 lstat64 10.88 0.004841 194 25 read 9.82 0.004369 109 40 13 open 5.84 0.002601 145 18 readlink 5.78 0.002574 112 23 munmap 4.51 0.002007 72 28 fstat64 4.17 0.001857 265 7 getdents64 3.12 0.001387 45 31 fcntl64 2.53 0.001124 37 30 close 2.42 0.001078 98 11 old_mmap 1.87 0.000834 49 17 brk 1.07 0.000475 238 2 2 connect 1.06 0.000473 237 2 socket 1.00 0.000446 20 22 mmap2 0.91 0.000405 81 5 write 0.52 0.000233 78 3 2 rt_sigaction 0.44 0.000197 66 3 3 ioctl 0.44 0.000197 197 1 uname 0.02 0.000011 11 1 set_thread_area 0.01 0.000003 3 1 gettimeofday ------ ----------- ----------- --------- --------- ---------------- 100.00 0.044502 559 20 total I'm posting this message to see if anyone else has seen anything similar or has any ideas. This same problem is 100% reproducible on multiple machines in the classroom. You may want to add comments or add your self to the CC list here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90116 The machines in this classroom are being replaced in two weeks with P4 2.8Ghz HyperThreaded boxes, so ideally we can get this problem nailed down soon. Dax Kelson

2 2

Samsung USB floppy
by Jos Vos 04 Sep '03

04 Sep '03

Hi, I have tried a new Samsung USB floppy drive with RH 8 and RH 9 and it is not working: when I access it (e.g., reading I do with dd if=/dev/sda) the floppy starts rotating, but at the end it says that it cannot open /dev/sda. This is what I get when plugging in the drive with a preformatted floppy in it: Sep 4 19:57:09 cherry kernel: hub.c: new USB device 00:0e.2-1, assigned address 6 Sep 4 19:57:12 cherry /etc/hotplug/usb.agent: Setup usb-storage for USB product 55d/2020/210 Sep 4 19:57:17 cherry kernel: Device not ready. Make sure there is a disc in the drive. Sep 4 19:57:17 cherry kernel: sda : READ CAPACITY failed. Sep 4 19:57:17 cherry kernel: sda : status = 1, message = 00, host = 0, driver = 08 Sep 4 19:57:17 cherry kernel: Current sd00:00: sense key Not Ready Sep 4 19:57:17 cherry kernel: Additional sense indicates Medium not present Sep 4 19:57:17 cherry kernel: sda : block size assumed to be 512 bytes, disk size 1GB. Sep 4 19:57:17 cherry kernel: sda: I/O error: dev 08:00, sector 0 Sep 4 19:57:17 cherry kernel: I/O error: dev 08:00, sector 0 Sep 4 19:57:17 cherry kernel: unable to read partition table Sep 4 19:57:17 cherry devlabel: devlabel service started/restarted Is there anything I do wrong or is my drive just defect? Thanks, -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204

1 0

Re: Red Hat 8.2 - Enabling Backing store
by Chris Kloiber 03 Sep '03

03 Sep '03

On Wed, 2003-09-03 at 16:26, Fred Bartholomai wrote: > We are currently porting our system from HP-UX to Linux red hat 8.2. > > It is going very well. Hmmm. That's interesting. Need to let us know how you managed to upgrade to a non-existent OS. :) > One question: How do we enable backing store for use with X Windows, > or rather > > The XFree86 binary. I’ve seen plenty of documentation but it doesn’t > really tell me how > > To enable it. I believe you add '+bs' to the end of the /etc/X11/xdm/Xservers file, so it looks something like: :0 local /usr/X11R6/bin/X +bs I haven't actually tried it, mind you. > Any help or pointers would really help. Google is my ally, and a powerful ally it is! -- Chris Kloiber Red Hat, Inc.

1 0

How to package execute-on-stack programs?
by Enrico Scholz 03 Sep '03

03 Sep '03

Hello, what is the way to package programs which are containing code which will be executed on stack? Since this "feature" conflicts with exec-shield, the package-build may fail in the %check stage, or on the user-side. A program suffering from this is qemu[1]; I tried the chstk tool[2], but it fails with | ./qemu: Unknown file type which is probably caused by a "strange" (but required) linking. I read the RELEASE-NOTES also which state that | NOTE: Binary marking (the ability to identify those binaries that | should run with Exec-shield enabled/disabled) is not yet implemented. Does there exist a clean way to mark execute-on-stack programs in the meantime? Enrico Footnotes: [1] http://fabrice.bellard.free.fr/qemu/ https://bugzilla.fedora.us/show_bug.cgi?id=623 [2] http://people.redhat.com/mingo/exec-shield/chstk.c

3 3

Problem while running stack in Linux kernel space
by Ranjitsinh Wable 02 Sep '03

02 Sep '03

Hello All, I have got my own IPv6 stack (not the Linux native IPv6). Legend: NUT - Node Under Test - Where my stack runs TN - Testing Node - Where Linux native IPv6 stack runs When i insert IPv6 stack (compiled as a module) in to the NUT kernel, it gets inserted in very smoothly. However, when i do ping6 from TN with -f (FLOOD) option to NUT, the NUT's kernel seems to be hanging. But, i observed that IPv4 part of the NUT's kernel still working (because ping from TN to NUT still works). I am controlling NUT's kernel with KGDB (through serial cable). If i see 'bt' in gdb, it shows that it is waiting in sys_read. PS : I skipped the KGDB back trace in the above description for clarity.

1 1

dlinfo function on Solaris
by Ajay Bansal 01 Sep '03

01 Sep '03

Hi All I have used a function dlinfo on Solaris. But I am not able to find any cooresponding implemention on Linux AS 2.1. basicall, man page of dlinfo says following (on solaris) ---------------------------------------------------------- NAME dlinfo - dynamic load information SYNOPSIS cc [ flag ... ] file ... -ldl [ library ... ] #include <dlfcn.h> #include <link.h> #include <limits.h> int dlinfo(void *handle, int request, void *p); DESCRIPTION The dlinfo() function extracts information about a dynamically-loaded object. This function is loosely modeled after the ioctl() function. The request argument and a third argument of varying type are passed to dlinfo(). The action taken by dlinfo() depends on the value of the request pro-vided. A handle argument, required for all requests except RTLD_DI_CONFIGADDR, is either the value returned from a dlo-pen() or dlmopen() call, or the special handle RTLD_SELF. If handle is the value returned from a dlopen() or dlmopen() call, the information returned by the dlinfo() call pertains to the specified object. If handle is the special handle RTLD_SELF, the information returned by the dlinfo() call pertains to the caller itself. ---------------------------------------------------------- We are using dlinfo for fething the file name of the specified llibrary. can somebody pls tell me, what should I do on Linux for the same? Regards Ajay

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel September 2003