Re: [PATCH v2] epoll: Support for disabling items, and a self-test app.
On 10/23/2012 07:23 PM, Paton J. Lewis wrote:
[Re-sending without HTML formatting; all vger.kernel.org destination
addresses bounced my original response.]
On 10/16/12 8:12 AM, Michael Kerrisk (man-pages) wrote:
[CC += linux-api@]
Thank you; is this sufficient to coordinate the required changes to the
glibc version of epoll.h?
Paton, we normally review the diffs between kernel versions but noticing
us via libc-alpha is great.
So, you ask to get this added to ?
#define EPOLL_CTL_DISABLE 4
Once 3.7 is out and contains it, we will add it. A friendly reminder
once the patch is in would be nice so that we don't miss it during the
review.
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v2] epoll: Support for disabling items, and a self-test app.
On 10/23/2012 07:23 PM, Paton J. Lewis wrote:
[Re-sending without HTML formatting; all vger.kernel.org destination
addresses bounced my original response.]
On 10/16/12 8:12 AM, Michael Kerrisk (man-pages) wrote:
[CC += linux-api@]
Thank you; is this sufficient to coordinate the required changes to the
glibc version of epoll.h?
Paton, we normally review the diffs between kernel versions but noticing
us via libc-alpha is great.
So, you ask to get this added to sys/epoll.h?
#define EPOLL_CTL_DISABLE 4
Once 3.7 is out and contains it, we will add it. A friendly reminder
once the patch is in would be nice so that we don't miss it during the
review.
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [discuss] pci_get_device_reverse(), why does Calgary need this?
Greg KH <[EMAIL PROTECTED]> writes: > How does the patch below look? I didn't want to remove the whole config > option, as there is more to the logic than just the "reverse order" > stuff there. I think you miss Documentation - it's mentioned in ide.txt and kernel-parameters.txt, Andreas -- Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED] SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpnl8pXxObM5.pgp Description: PGP signature
Re: [discuss] pci_get_device_reverse(), why does Calgary need this?
Greg KH [EMAIL PROTECTED] writes: How does the patch below look? I didn't want to remove the whole config option, as there is more to the logic than just the reverse order stuff there. I think you miss Documentation - it's mentioned in ide.txt and kernel-parameters.txt, Andreas -- Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED] SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpnl8pXxObM5.pgp Description: PGP signature
N_HCI for S390x missing in 2.4.5
Looking at the patch for 2.4.5, I noticed that all architectures use N_HCI - except s390x which has N_BT. Why is this different? I propose to use N_HCI everywhere, Andreas diff -u --recursive --new-file v2.4.5/linux/include/asm-s390/termios.h linux/include/asm-s390/termios.h --- v2.4.5/linux/include/asm-s390/termios.h Tue Feb 13 14:13:44 2001 +++ linux/include/asm-s390/termios.hMon Jun 11 19:15:27 2001 @@ -63,6 +63,7 @@ #define N_IRDA 11 /* Linux IR - http://irda.sourceforge.net/ */ #define N_SMSBLOCK 12 /* SMS block mode - for talking to GSM data cards about SMS messages */ #define N_HDLC 13 /* synchronous HDLC */ +#define N_HCI 15 /* Bluetooth HCI UART */ diff -u --recursive --new-file v2.4.5/linux/include/asm-s390x/termios.h linux/include/asm-s390x/termios.h --- v2.4.5/linux/include/asm-s390x/termios.hWed Apr 11 19:02:29 2001 +++ linux/include/asm-s390x/termios.h Mon Jun 11 19:15:27 2001 @@ -63,6 +63,7 @@ #define N_IRDA 11 /* Linux IR - http://irda.sourceforge.net/ */ #define N_SMSBLOCK 12 /* SMS block mode - for talking to GSM data cards about SMS messages */ #define N_HDLC 13 /* synchronous HDLC */ +#define N_BT 15 /* bluetooth */ -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
N_HCI for S390x missing in 2.4.5
Looking at the patch for 2.4.5, I noticed that all architectures use N_HCI - except s390x which has N_BT. Why is this different? I propose to use N_HCI everywhere, Andreas diff -u --recursive --new-file v2.4.5/linux/include/asm-s390/termios.h linux/include/asm-s390/termios.h --- v2.4.5/linux/include/asm-s390/termios.h Tue Feb 13 14:13:44 2001 +++ linux/include/asm-s390/termios.hMon Jun 11 19:15:27 2001 @@ -63,6 +63,7 @@ #define N_IRDA 11 /* Linux IR - http://irda.sourceforge.net/ */ #define N_SMSBLOCK 12 /* SMS block mode - for talking to GSM data cards about SMS messages */ #define N_HDLC 13 /* synchronous HDLC */ +#define N_HCI 15 /* Bluetooth HCI UART */ diff -u --recursive --new-file v2.4.5/linux/include/asm-s390x/termios.h linux/include/asm-s390x/termios.h --- v2.4.5/linux/include/asm-s390x/termios.hWed Apr 11 19:02:29 2001 +++ linux/include/asm-s390x/termios.h Mon Jun 11 19:15:27 2001 @@ -63,6 +63,7 @@ #define N_IRDA 11 /* Linux IR - http://irda.sourceforge.net/ */ #define N_SMSBLOCK 12 /* SMS block mode - for talking to GSM data cards about SMS messages */ #define N_HDLC 13 /* synchronous HDLC */ +#define N_BT 15 /* bluetooth */ -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Aaron Lehmann <[EMAIL PROTECTED]> writes: > On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote: > > Should we file bug reports against glibc? > > invsqrtpi= 5.64189583547756279280e-01 > Inverted square root of pi. Want to file a bug on Pi? > > tpi = 6.36619772367581382433e-01, > R0/S0 on [0, 2.00] > > I'm not sure what R and S are, but the glibc developers probably are. We have comments in the code that state how j0 is build, and R0/S0 come from some expansion: * Bessel function of the first and second kinds of order zero. * Method -- j0(x): * 1. For tiny x, we use j0(x) = 1 - x^2/4 + x^4/64 - ... * 2. Reduce x to |x| since j0(x)=j0(-x), and * for x in (0,2) * j0(x) = 1-z/4+ z^2*R0/S0, where z = x*x; * (precision: |j0-1+z/4-z^2R0/S0 |<2**-63.67 ) Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Aaron Lehmann [EMAIL PROTECTED] writes: On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote: Should we file bug reports against glibc? invsqrtpi= 5.64189583547756279280e-01 Inverted square root of pi. Want to file a bug on Pi? tpi = 6.36619772367581382433e-01, R0/S0 on [0, 2.00] I'm not sure what R and S are, but the glibc developers probably are. We have comments in the code that state how j0 is build, and R0/S0 come from some expansion: * Bessel function of the first and second kinds of order zero. * Method -- j0(x): * 1. For tiny x, we use j0(x) = 1 - x^2/4 + x^4/64 - ... * 2. Reduce x to |x| since j0(x)=j0(-x), and * for x in (0,2) * j0(x) = 1-z/4+ z^2*R0/S0, where z = x*x; * (precision: |j0-1+z/4-z^2R0/S0 |2**-63.67 ) Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: >2G Files
Bill Wendling <[EMAIL PROTECTED]> writes: > Hi all, > > Question: Does Linux support >2G files and, if so, how do I implement > this? It does in 2.4, for details check: http://www.suse.de/~aj/linux_lfs.html Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2G Files
Bill Wendling [EMAIL PROTECTED] writes: Hi all, Question: Does Linux support 2G files and, if so, how do I implement this? It does in 2.4, for details check: http://www.suse.de/~aj/linux_lfs.html Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: FPU and exceptions
Send me a small program (10s of lines) that shows the problem. Installing a signal handler on SIGFPE should do the right thing. Btw. I do think this is off-topic to linux-kernel, Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: FPU and exceptions
Send me a small program (10s of lines) that shows the problem. Installing a signal handler on SIGFPE should do the right thing. Btw. I do think this is off-topic to linux-kernel, Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Semi-OT] Dual Athlon support in kernel
Joseph Carter <[EMAIL PROTECTED]> writes: > On Tue, Apr 24, 2001 at 01:18:57PM +0300, Ville Herva wrote: > > There's also AthlonLinux http://athlonlinux.org/ and AthlonGCC > > http://athlonlinux.org/agcc/about.shtml, but I have no experience with those > > (I have no Athlon ;( ). > > A warning about agcc, I've discovered that it does not always compile code > quite the way you expect it. This is unsurprising given it's based on > pgcc which is known to change alignments on you in ways that sometimes > break things subtly. > > > I do not know if agcc actually can produce code which simply does not work > as is reported with pgcc (I suspect the alignment differences account for > many of those cases), but I recall reading in the past few days that agcc > is not supported for compiling the kernel. > > It also fails to properly compile certain other programs, notably anything > that includes asm functions. As a result, my own experience suggests you > consider agcc in the same class as gcc 3.0 at the moment - experimental. > Hopefully the k7 optimizations that work well will find their way into a > nice athlon subarch options in standard gcc and agcc won't be necessary. Note that gcc 3.0 will have support for Athlons, -mcpu=athlon and -march=athlon are both supported and will do the right thing. For details you should ask Jan Hubicka who implemented this some time ago, Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Semi-OT] Dual Athlon support in kernel
Joseph Carter [EMAIL PROTECTED] writes: On Tue, Apr 24, 2001 at 01:18:57PM +0300, Ville Herva wrote: There's also AthlonLinux http://athlonlinux.org/ and AthlonGCC http://athlonlinux.org/agcc/about.shtml, but I have no experience with those (I have no Athlon ;( ). A warning about agcc, I've discovered that it does not always compile code quite the way you expect it. This is unsurprising given it's based on pgcc which is known to change alignments on you in ways that sometimes break things subtly. I do not know if agcc actually can produce code which simply does not work as is reported with pgcc (I suspect the alignment differences account for many of those cases), but I recall reading in the past few days that agcc is not supported for compiling the kernel. It also fails to properly compile certain other programs, notably anything that includes asm functions. As a result, my own experience suggests you consider agcc in the same class as gcc 3.0 at the moment - experimental. Hopefully the k7 optimizations that work well will find their way into a nice athlon subarch options in standard gcc and agcc won't be necessary. Note that gcc 3.0 will have support for Athlons, -mcpu=athlon and -march=athlon are both supported and will do the right thing. For details you should ask Jan Hubicka who implemented this some time ago, Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: FPE's
ISO C demands that at process startup all FPU traps are masked. You can set specific traps with the functions in from the C library, for details read the manual: info libc Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: FPE's
ISO C demands that at process startup all FPU traps are masked. You can set specific traps with the functions in fenv.h from the C library, for details read the manual: info libc Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-s390x progress
[EMAIL PROTECTED] writes: > I've been using the "Linux from Scratch" (LFS) document as a guide for building > a basic Linux system. The only things I've done outside the instructions > include: > > 1. Built 32 bit version of binutils, gcc, glibc for s390x > 2. Built kernel > 3. Created /root64 and populated it with /usr /bin etc. > 4. Built 64-bit libncurses > > I've now built statically linked 64-bit versions of: > 1. bash > 2. bzip2 > 3. diffutils > 4. fileutils > > These are all installed in the /root64 tree. > > According to the LFS instructions I should now build grep, gzip, make, > sed, shellutils, tar, and textutils, before going onto the next phase. > However, I cannot find grep, sed, or tar srpms on the SuSE CDs. this is getting off-topic but from SuSE 7.1: $ rpm -q -f `which grep` base-2001.1.15-0 You'll find in the base rpm also the sources of sed and tar. Hope this helps - and have fun with Linux on your small;-) machine, Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-s390x progress
[EMAIL PROTECTED] writes: I've been using the "Linux from Scratch" (LFS) document as a guide for building a basic Linux system. The only things I've done outside the instructions include: 1. Built 32 bit version of binutils, gcc, glibc for s390x 2. Built kernel 3. Created /root64 and populated it with /usr /bin etc. 4. Built 64-bit libncurses I've now built statically linked 64-bit versions of: 1. bash 2. bzip2 3. diffutils 4. fileutils These are all installed in the /root64 tree. According to the LFS instructions I should now build grep, gzip, make, sed, shellutils, tar, and textutils, before going onto the next phase. However, I cannot find grep, sed, or tar srpms on the SuSE CDs. this is getting off-topic but from SuSE 7.1: $ rpm -q -f `which grep` base-2001.1.15-0 You'll find in the base rpm also the sources of sed and tar. Hope this helps - and have fun with Linux on your small;-) machine, Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Patch to support also new binutils versions
Hi Linus,
newer binutils (current CVS version and the soon to be release 2.11)
don't support "ld -oformat binary" anymore. Instead two dashes should
be used ("ld --oformat binary"). This works with both old and new
binutils.
Please apply the appended patch which fixes all occurences in the
kernel.
Thanks,
Andreas
--- arch/i386/boot/Makefile Tue Dec 21 05:00:53 1999
+++ /usr/src/linux-2.4.2-pre3/arch/i386/boot/Makefile Sat Feb 10 12:56:36 2001
@@ -43,7 +43,7 @@
$(HOSTCC) $(HOSTCFLAGS) -o $@ $< -I$(TOPDIR)/include
bootsect: bootsect.o
- $(LD) -Ttext 0x0 -s -oformat binary -o $@ $<
+ $(LD) -Ttext 0x0 -s --oformat binary -o $@ $<
bootsect.o: bootsect.s
$(AS) -o $@ $<
@@ -52,7 +52,7 @@
$(CPP) $(CPPFLAGS) -traditional $(SVGA_MODE) $(RAMDISK) $< -o $@
bbootsect: bbootsect.o
- $(LD) -Ttext 0x0 -s -oformat binary $< -o $@
+ $(LD) -Ttext 0x0 -s --oformat binary $< -o $@
bbootsect.o: bbootsect.s
$(AS) -o $@ $<
@@ -61,7 +61,7 @@
$(CPP) $(CPPFLAGS) -D__BIG_KERNEL__ -traditional $(SVGA_MODE) $(RAMDISK) $< -o
$@
setup: setup.o
- $(LD) -Ttext 0x0 -s -oformat binary -e begtext -o $@ $<
+ $(LD) -Ttext 0x0 -s --oformat binary -e begtext -o $@ $<
setup.o: setup.s
$(AS) -o $@ $<
@@ -70,7 +70,7 @@
$(CPP) $(CPPFLAGS) -traditional $(SVGA_MODE) $(RAMDISK) $< -o $@
bsetup: bsetup.o
- $(LD) -Ttext 0x0 -s -oformat binary -e begtext -o $@ $<
+ $(LD) -Ttext 0x0 -s --oformat binary -e begtext -o $@ $<
bsetup.o: bsetup.s
$(AS) -o $@ $<
--
Andreas Jaeger
SuSE Labs [EMAIL PROTECTED]
private [EMAIL PROTECTED]
http://www.suse.de/~aj
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Patch to support also new binutils versions
Hi Linus,
newer binutils (current CVS version and the soon to be release 2.11)
don't support "ld -oformat binary" anymore. Instead two dashes should
be used ("ld --oformat binary"). This works with both old and new
binutils.
Please apply the appended patch which fixes all occurences in the
kernel.
Thanks,
Andreas
--- arch/i386/boot/Makefile Tue Dec 21 05:00:53 1999
+++ /usr/src/linux-2.4.2-pre3/arch/i386/boot/Makefile Sat Feb 10 12:56:36 2001
@@ -43,7 +43,7 @@
$(HOSTCC) $(HOSTCFLAGS) -o $@ $ -I$(TOPDIR)/include
bootsect: bootsect.o
- $(LD) -Ttext 0x0 -s -oformat binary -o $@ $
+ $(LD) -Ttext 0x0 -s --oformat binary -o $@ $
bootsect.o: bootsect.s
$(AS) -o $@ $
@@ -52,7 +52,7 @@
$(CPP) $(CPPFLAGS) -traditional $(SVGA_MODE) $(RAMDISK) $ -o $@
bbootsect: bbootsect.o
- $(LD) -Ttext 0x0 -s -oformat binary $ -o $@
+ $(LD) -Ttext 0x0 -s --oformat binary $ -o $@
bbootsect.o: bbootsect.s
$(AS) -o $@ $
@@ -61,7 +61,7 @@
$(CPP) $(CPPFLAGS) -D__BIG_KERNEL__ -traditional $(SVGA_MODE) $(RAMDISK) $ -o
$@
setup: setup.o
- $(LD) -Ttext 0x0 -s -oformat binary -e begtext -o $@ $
+ $(LD) -Ttext 0x0 -s --oformat binary -e begtext -o $@ $
setup.o: setup.s
$(AS) -o $@ $
@@ -70,7 +70,7 @@
$(CPP) $(CPPFLAGS) -traditional $(SVGA_MODE) $(RAMDISK) $ -o $@
bsetup: bsetup.o
- $(LD) -Ttext 0x0 -s -oformat binary -e begtext -o $@ $
+ $(LD) -Ttext 0x0 -s --oformat binary -e begtext -o $@ $
bsetup.o: bsetup.s
$(AS) -o $@ $
--
Andreas Jaeger
SuSE Labs [EMAIL PROTECTED]
private [EMAIL PROTECTED]
http://www.suse.de/~aj
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Compile dnotify example w/o glibc 2.2 headers
Daniel Phillips <[EMAIL PROTECTED]> writes: > dnotify is cool, check it out > > If you want to compile the example in Documentation/dnotify.txt and > you don't have glibc 2.2 headers installed you have 3 choices: > > 1) Upgrade to glibc 2.2 > 2) Hunt for the missing symbols in the 2.4 source tree > 3) Apply this patch > > Option (1) is recommended of course, but if you're lazy (like me) > then... > > --- 2.4.0/Documentation/dnotify.txt~ Mon Jan 22 16:04:32 2001 > +++ 2.4.0/Documentation/dnotify.txt Mon Jan 22 16:04:25 2001 > @@ -63,6 +63,17 @@ > #include > #include > > + #ifndef F_NOTIFY/* pre-glibc 2.2? */ If you're checking for glibc 2.2 or newer, better use: #if __GLIBC__ == 2 && __GLIBC_MINOR__ >= 2 Andreas > + #define F_NOTIFY1026 > + #define DN_ACCESS 0x0001 /* File accessed */ > + #define DN_MODIFY 0x0002 /* File modified */ > + #define DN_CREATE 0x0004 /* File created */ > + #define DN_DELETE 0x0008 /* File removed */ > + #define DN_RENAME 0x0010 /* File renamed */ > + #define DN_ATTRIB 0x0020 /* File changed attibutes */ > + #define DN_MULTISHOT0x8000 /* Don't remove notifier */ > + #endif > + > static volatile int event_fd; > > static void handler(int sig, siginfo_t *si, void *data) -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Compile dnotify example w/o glibc 2.2 headers
Daniel Phillips [EMAIL PROTECTED] writes: plugdnotify is cool, check it out/plug If you want to compile the example in Documentation/dnotify.txt and you don't have glibc 2.2 headers installed you have 3 choices: 1) Upgrade to glibc 2.2 2) Hunt for the missing symbols in the 2.4 source tree 3) Apply this patch Option (1) is recommended of course, but if you're lazy (like me) then... --- 2.4.0/Documentation/dnotify.txt~ Mon Jan 22 16:04:32 2001 +++ 2.4.0/Documentation/dnotify.txt Mon Jan 22 16:04:25 2001 @@ -63,6 +63,17 @@ #include stdio.h #include unistd.h + #ifndef F_NOTIFY/* pre-glibc 2.2? */ If you're checking for glibc 2.2 or newer, better use: #if __GLIBC__ == 2 __GLIBC_MINOR__ = 2 Andreas + #define F_NOTIFY1026 + #define DN_ACCESS 0x0001 /* File accessed */ + #define DN_MODIFY 0x0002 /* File modified */ + #define DN_CREATE 0x0004 /* File created */ + #define DN_DELETE 0x0008 /* File removed */ + #define DN_RENAME 0x0010 /* File renamed */ + #define DN_ATTRIB 0x0020 /* File changed attibutes */ + #define DN_MULTISHOT0x8000 /* Don't remove notifier */ + #endif + static volatile int event_fd; static void handler(int sig, siginfo_t *si, void *data) -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: sigcontext on Linux-ppc in user space
John Kacur <[EMAIL PROTECTED]> writes: > Does anyone know how to get at the struct sigcontext in a signal handler > on Linux for powerpc? sigaction of course lets you create a signal > handler as a function with the prototype void(*)(int, siginfo_t *, void > *) > where the last argument, a pointer to void, is the sigcontext. I believe > that the last argument is NOT defined by POSIX and so is implementation > dependent. > > On Intel it seems sufficient to use #include > to get the definition of struct sigcontext, and then get the values > you'd like out of the signal handler. But on Linux for powerpc, the same > thing doesn't work. Does anyone know what the trick is here to > accomplish this? You should never include kernel headers in user space. If you have a glibc 2.1 (or newer) based system, just include which will include with the struct (this works on all architectures). Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: sigcontext on Linux-ppc in user space
John Kacur [EMAIL PROTECTED] writes: Does anyone know how to get at the struct sigcontext in a signal handler on Linux for powerpc? sigaction of course lets you create a signal handler as a function with the prototype void(*)(int, siginfo_t *, void *) where the last argument, a pointer to void, is the sigcontext. I believe that the last argument is NOT defined by POSIX and so is implementation dependent. On Intel it seems sufficient to use #include asm/sigcontext.h to get the definition of struct sigcontext, and then get the values you'd like out of the signal handler. But on Linux for powerpc, the same thing doesn't work. Does anyone know what the trick is here to accomplish this? You should never include kernel headers in user space. If you have a glibc 2.1 (or newer) based system, just include signal.h which will include bits/sigcontext.h with the struct (this works on all architectures). Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with elf and dynamic loading ...
>>>>> Damien TOURAINE writes: > Hi ! > I'm using dynamic library to load some part of a big software (that > use several differents modules). > The main program fully use the symboles of the shared object (through > the dlsym command), however, the functions available in the module are > not able to use the symbols of the main program. > Is-it a bug of the kernel ? > Is-it to avoid a potential hole of security ? That's a question for glibc - it has nothing to do with the kernel. To get it to work, your program should be compiled with -Bdynamic. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with elf and dynamic loading ...
Damien TOURAINE writes: Hi ! I'm using dynamic library to load some part of a big software (that use several differents modules). The main program fully use the symboles of the shared object (through the dlsym command), however, the functions available in the module are not able to use the symbols of the main program. Is-it a bug of the kernel ? Is-it to avoid a potential hole of security ? That's a question for glibc - it has nothing to do with the kernel. To get it to work, your program should be compiled with -Bdynamic. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: suggest: diff-2.4.0-test12_to_2.4.0
>>>>> Ulrich Windl writes: > I thought I'd find a diff between 2.4.0test12 (last test release) to > the final 2.4.0 release, but did not. Wouldn't it be (have been) a good > idea? Apply: patch-2.4.0-prerelease.bz2 and then prerelease-to-final.bz2 to test12 and you get 2.4.0 final. You'll find both in ftp.*.kernel.org/...kernel/v2.4/test-kernels/ Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: suggest: diff-2.4.0-test12_to_2.4.0
Ulrich Windl writes: I thought I'd find a diff between 2.4.0test12 (last test release) to the final 2.4.0 release, but did not. Wouldn't it be (have been) a good idea? Apply: patch-2.4.0-prerelease.bz2 and then prerelease-to-final.bz2 to test12 and you get 2.4.0 final. You'll find both in ftp.*.kernel.org/...kernel/v2.4/test-kernels/ Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Arg. File > 2GB removal
>>>>> Damacus Porteng writes: > For grins, I did `dd if=/dev/zero of=testfile bs=1024 count=400` > Obviously, with the limits of ext2, this isn't allowed, however, dd continued > marrily on its way, tho it spouted an error... With 2.4 it's allowed. > I cancelled the dd and went to remove the file, though the following occured: > root@obfuscated:/home/ftp# rm testfile > rm: cannot remove `testfile': Value too large for defined data type > 'ls' complains about the same. I ran e2fsck -f /dev/hde6 (the partition of > /home) and it didn't 'find' the problem. You need an rm that's using the LFS interface. > How do I remove this file and reclaim the HDD space? Try: echo > testfile Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Arg. File 2GB removal
Damacus Porteng writes: For grins, I did `dd if=/dev/zero of=testfile bs=1024 count=400` Obviously, with the limits of ext2, this isn't allowed, however, dd continued marrily on its way, tho it spouted an error... With 2.4 it's allowed. I cancelled the dd and went to remove the file, though the following occured: root@obfuscated:/home/ftp# rm testfile rm: cannot remove `testfile': Value too large for defined data type 'ls' complains about the same. I ran e2fsck -f /dev/hde6 (the partition of /home) and it didn't 'find' the problem. You need an rm that's using the LFS interface. How do I remove this file and reclaim the HDD space? Try: echo testfile Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Large filesystem?
>>>>> Timothy A DeWees writes: > Hello kernel hackers, > Can anyonw point me to doc on how to setup large filesytem support on > 2.2? Use 2.4 - or apply Andrea's patches (somewhere on ftp.*.kernel.org) - and then rebuild glibc. For details check also: http://www.suse.de/~aj/linux_lfs.html Andreas > We are using linux to do network backups with Microlite and some of our > backups are growing above 2 Gb. Thanks is advance! -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Large filesystem?
Timothy A DeWees writes: Hello kernel hackers, Can anyonw point me to doc on how to setup large filesytem support on 2.2? Use 2.4 - or apply Andrea's patches (somewhere on ftp.*.kernel.org) - and then rebuild glibc. For details check also: http://www.suse.de/~aj/linux_lfs.html Andreas We are using linux to do network backups with Microlite and some of our backups are growing above 2 Gb. Thanks is advance! -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
struct acct uses 16bit uids :-(
Hi, is anybody maintaining the BSD process accounting? It's currently broken since it still uses 16 bit uids :-( struct acct in contains: /* * No binary format break with 2.0 - but when we hit 32bit uid we'll * have to bite one */ __u16 ac_uid; /* Accounting Real User ID */ __u16 ac_gid; /* Accounting Real Group ID */ Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Defective Red Hat Distribution poorly represents Linux
>>>>> Charles Turner, Ph D writes: > I tried to help a friend this weekend convert to Linux. > He lives in Upstate New York, so it was a long trip from > Cambridge, Massachusetts. > I was terribly wrong. This Red Hat version is irrevocably defective. This list is about problems with the Linux kernel and not with specific distributions. Please report this directly to the distribution maker, it's totally off-topic here. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
struct acct uses 16bit uids :-(
Hi, is anybody maintaining the BSD process accounting? It's currently broken since it still uses 16 bit uids :-( struct acct in linux/acct.h contains: /* * No binary format break with 2.0 - but when we hit 32bit uid we'll * have to bite one */ __u16 ac_uid; /* Accounting Real User ID */ __u16 ac_gid; /* Accounting Real Group ID */ Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Defective Red Hat Distribution poorly represents Linux
Charles Turner, Ph D writes: I tried to help a friend this weekend convert to Linux. He lives in Upstate New York, so it was a long trip from Cambridge, Massachusetts. I was terribly wrong. This Red Hat version is irrevocably defective. This list is about problems with the Linux kernel and not with specific distributions. Please report this directly to the distribution maker, it's totally off-topic here. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Large File Support
>>>>> Andreas Jaeger writes: >>>>> Andreas S Kerber writes: >> We need to handle files which are about 10GB large. >> Is there any way to do this with Linux? Some pointers would be nice. > Yes, with recent 2.4 kernels or a patched 2.2 kernel - and a > recompiled glibc. For details check: Upps, there was a typo in the URL - please try this one - or go to it via my homepage: http://www.suse.de/~aj/linux_lfs.html Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Large File Support
>>>>> Andreas S Kerber writes: > We need to handle files which are about 10GB large. > Is there any way to do this with Linux? Some pointers would be nice. Yes, with recent 2.4 kernels or a patched 2.2 kernel - and a recompiled glibc. For details check: http://www.suse.de/~aj/linux-lfs.html Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Large File Support
Andreas S Kerber writes: We need to handle files which are about 10GB large. Is there any way to do this with Linux? Some pointers would be nice. Yes, with recent 2.4 kernels or a patched 2.2 kernel - and a recompiled glibc. For details check: http://www.suse.de/~aj/linux-lfs.html Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Large File Support
Andreas Jaeger writes: Andreas S Kerber writes: We need to handle files which are about 10GB large. Is there any way to do this with Linux? Some pointers would be nice. Yes, with recent 2.4 kernels or a patched 2.2 kernel - and a recompiled glibc. For details check: Upps, there was a typo in the URL - please try this one - or go to it via my homepage: http://www.suse.de/~aj/linux_lfs.html Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: files bigger than 2 GB
>>>>> Petr Vandrovec writes: > On 12 Sep 00 at 19:02, Matti Aarnio wrote: >> ReiserFS: Propably works >> EXT2: works >> Coda: Not (local cache issues, protocol is ok.) >> UFS: works (although not complete vs. O_LARGEFILE flag use.) >> NFSv2:protocol is limited to 2G-1 >> NFSv3:protocol is ok, not sure of Linux implementation status. >> SAMBA:works (but linux kernel SMBFS might be another story) > Matti, > if you are maintaining such table, you can add > NCPfs:protocol is limited to 4G-1, Linux implementation to 2G-1 > I do not plan any change until Novell discloses 64bit NCP file api. Petr, have a look at my (work in progress) page <http://www.suse.de/~aj/linux_lfs.html>, it contains the table now. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: files bigger than 2 GB
>>>>> Arnaud Installe writes: > First of all, thanks to all of you for your responses. :-) I was under > the impression 2.4 still didn't have large file support, as I seem to > recall ssize_t still was 32 bits. off64_t is the type you want to look at. > On Tue, Sep 12, 2000 at 04:25:02PM +0200, Andreas Jaeger wrote: >> >>>>> Arnaud Installe writes: >> >> > Hello, >> > I need support for files larger than 2GB. What's the status for that ? >> > AFAIK neither 2.2 nor 2.4-test support that out of the box. Can anyone >> > point me to a good link for patches ? Apart from the kernel, does >> > anything else need changes for large file support ? >> >> 2.4.0test7 has all the LFS (large file support) in it. It will work >> on ext2 - but e.g. not on NFSv2. > So how about ReiserFS ? And Coda ? The 2.2 version of ReiserFS as distributed with SuSE 7.0 doesn't support LFS. The 2.4 should - but better ask on the list. You need to find out for every file system. I have no information about coda. Andreas [...] -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: files bigger than 2 GB
>>>>> Arnaud Installe writes: > Hello, > I need support for files larger than 2GB. What's the status for that ? > AFAIK neither 2.2 nor 2.4-test support that out of the box. Can anyone > point me to a good link for patches ? Apart from the kernel, does > anything else need changes for large file support ? 2.4.0test7 has all the LFS (large file support) in it. It will work on ext2 - but e.g. not on NFSv2. You need a new glibc (no need to recompile your programs). glibc 2.2 will support the kernel LFS interfaces, a beta quality test release is available as glibc 2.1.93 (search the mailing list archives at http://sources.redhat.com/glibc for the announcement). Some distributions, like SuSE 7.0 (RedHat might also, I'm not sure), come with a glibc 2.1.3 that has LFS support in it that works with 2.4.0testX. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: files bigger than 2 GB
Arnaud Installe writes: Hello, I need support for files larger than 2GB. What's the status for that ? AFAIK neither 2.2 nor 2.4-test support that out of the box. Can anyone point me to a good link for patches ? Apart from the kernel, does anything else need changes for large file support ? 2.4.0test7 has all the LFS (large file support) in it. It will work on ext2 - but e.g. not on NFSv2. You need a new glibc (no need to recompile your programs). glibc 2.2 will support the kernel LFS interfaces, a beta quality test release is available as glibc 2.1.93 (search the mailing list archives at http://sources.redhat.com/glibc for the announcement). Some distributions, like SuSE 7.0 (RedHat might also, I'm not sure), come with a glibc 2.1.3 that has LFS support in it that works with 2.4.0testX. Andreas -- Andreas Jaeger SuSE Labs [EMAIL PROTECTED] private [EMAIL PROTECTED] http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
