n".
Signed-Off-By: Peter Samuelson <[EMAIL PROTECTED]>
--- drivers/input/mouse/logips2pp.c
+++ drivers/input/mouse/logips2pp.c
@@ -220,6 +220,7 @@
{ 66, PS2PP_KIND_MX, /*
MX3100 reciver */
PS2PP_WHEEL | PS2PP
Adds the ID to recognise my PS/2 TrackMan Marble.
This is purely cosmetic: this is standard 3-button, no wheel or other
such features, so it already _worked_ just fine. This patch suppresses
a warning about the unknown model, and changes the printk from Mouse
to TrackMan.
Signed-Off-By: Peter
I know this is a bit late to be reporting this, as it happened before
2.6.18, but my PowerPC CHRP machine (RS/6000 43p-150, 604e CPU) no
longer boots. From the console:
instantiating rtas at 0x1ffe5000 ... done
copying OF device tree ...
Building dt strings...
Building dt structure...
I know this is a bit late to be reporting this, as it happened before
2.6.18, but my PowerPC CHRP machine (RS/6000 43p-150, 604e CPU) no
longer boots. From the console:
instantiating rtas at 0x1ffe5000 ... done
copying OF device tree ...
Building dt strings...
Building dt structure...
[Peter Samuelson]
> AIX curses.h defines macros 'clear_screen' and 'color_names' but does
> not define 'scroll()'.
I should mention that 'make menuconfig' on AIX 4.3 also required 'ln -s
libxcurses.a /usr/lib/libncurses.a' but a patch to detect *that* seemed
too intrusive to be worthwhile.
[Peter Samuelson]
AIX curses.h defines macros 'clear_screen' and 'color_names' but does
not define 'scroll()'.
I should mention that 'make menuconfig' on AIX 4.3 also required 'ln -s
libxcurses.a /usr/lib/libncurses.a' but a patch to detect *that* seemed
too intrusive to be worthwhile. Also
AIX curses.h defines macros 'clear_screen' and 'color_names' but does
not define 'scroll()'.
Signed-Off-By: Peter Samuelson <[EMAIL PROTECTED]>
diff -urN 2.6.11-rc5/scripts/lxdialog/checklist.c.old
2.6.11-rc5/scripts/lxdialog/checklist.c
--- 2.6.11-rc5/scripts/lxdialog/checklist.c.old 2
AIX curses.h defines macros 'clear_screen' and 'color_names' but does
not define 'scroll()'.
Signed-Off-By: Peter Samuelson [EMAIL PROTECTED]
diff -urN 2.6.11-rc5/scripts/lxdialog/checklist.c.old
2.6.11-rc5/scripts/lxdialog/checklist.c
--- 2.6.11-rc5/scripts/lxdialog/checklist.c.old 2005-02-27
[Kai Germaschewski]
> However, I don't think it's hard to verify that my patch works as
> well, it's about ten lines added to Rules.make. It's particularly
> easy to verify that it doesn't change behavior for objects listed in
> $(list-multi) at all.
Yes, we can say this, but people are right
[Kai Germaschewski]
However, I don't think it's hard to verify that my patch works as
well, it's about ten lines added to Rules.make. It's particularly
easy to verify that it doesn't change behavior for objects listed in
$(list-multi) at all.
Yes, we can say this, but people are right to
[esr]
> Besides, right now the configurator has a simple invariant. It will
> only accept consistent configurations
So you are saying that the old 'vi .config; make oldconfig' trick is
officially unsupported? That's too bad, it was quite handy.
Peter
-
To unsubscribe from this list: send the
[esr]
Besides, right now the configurator has a simple invariant. It will
only accept consistent configurations
So you are saying that the old 'vi .config; make oldconfig' trick is
officially unsupported? That's too bad, it was quite handy.
Peter
-
To unsubscribe from this list: send the
[Peter Samuelson]
> > Introduced in 2.4.4pre4, I believe. $(export-objs) need not be
> > conditional, and the if statement was not really correct either,
> > although in this case it probably worked.
[Tom Rini]
> Er, are you sure changing the test for !"nn"
Introduced in 2.4.4pre4, I believe. $(export-objs) need not be
conditional, and the if statement was not really correct either,
although in this case it probably worked.
Peter
--- 2.4.4pre6/lib/Makefile~ Mon Apr 23 09:51:17 2001
+++ 2.4.4pre6/lib/Makefile Mon Apr 23 17:11:04 2001
@@
Introduced in 2.4.4pre4, I believe. $(export-objs) need not be
conditional, and the if statement was not really correct either,
although in this case it probably worked.
Peter
--- 2.4.4pre6/lib/Makefile~ Mon Apr 23 09:51:17 2001
+++ 2.4.4pre6/lib/Makefile Mon Apr 23 17:11:04 2001
@@
[Peter Samuelson]
Introduced in 2.4.4pre4, I believe. $(export-objs) need not be
conditional, and the if statement was not really correct either,
although in this case it probably worked.
[Tom Rini]
Er, are you sure changing the test for !nn is correct here? I
_think_ at least
[esr]
> > CONFIG_SOUND_YMPCI: arch/ppc/configs/power3_defconfig
>arch/arm/def-configs/footbridge arch/arm/def-configs/rpc arch/arm/def-configs/lart
>arch/arm/def-configs/shark
[jgarzik]
> typo, that should be ...YMFPCI.
Actually it's not a typo (although the fix is the same). The old
[esr]
CONFIG_SOUND_YMPCI: arch/ppc/configs/power3_defconfig
arch/arm/def-configs/footbridge arch/arm/def-configs/rpc arch/arm/def-configs/lart
arch/arm/def-configs/shark
[jgarzik]
typo, that should be ...YMFPCI.
Actually it's not a typo (although the fix is the same). The old
[John Cowan]
> The whole point of CML2 is to make kernel configuration something
> that Aunt Tillie (or a reasonable facsimile thereof) can do, and we
> are all Aunt Tillies from time to time. That includes differing
> standards of readability,
Come on, that's absolutely a red herring. There
[John Cowan]
The whole point of CML2 is to make kernel configuration something
that Aunt Tillie (or a reasonable facsimile thereof) can do, and we
are all Aunt Tillies from time to time. That includes differing
standards of readability,
Come on, that's absolutely a red herring. There are
[esr]
> If there were already a library in ths stock Python distribution to
> digest .Xdefaults files I might consider this. Perhaps I'll write
> one. But I'm not going to bulk up the CML2 code with this marginal
> feature.
Wait ... I thought you were just using Python bindings to Tk. Are you
[esr]
If there were already a library in ths stock Python distribution to
digest .Xdefaults files I might consider this. Perhaps I'll write
one. But I'm not going to bulk up the CML2 code with this marginal
feature.
Wait ... I thought you were just using Python bindings to Tk. Are you
[Jeff Garzik]
> > It stays "8139too". Donald Becker's rtl8139.c continues to exist
> > outside the kernel.
Honestly, Jeff, I don't see how it matters -- because if you are
downloading an external driver, you are not going through the config
system anyway.
But ... "maintanicus selector est"
[esr]
> CONFIG_8139TOOCONFIG_RTL8139TOO
> CONFIG_8139TOO_PIOCONFIG_RTL8139TOO_PIO
> CONFIG_8139TOO_TUNE_TWISTER CONFIG_RTL8139TOO_TUNE_TWISTER
The -TOO suffix was to distinguish between this and the former 8139
driver, as the two coexisted in 2.2 and 2.3.
[esr]
CONFIG_8139TOOCONFIG_RTL8139TOO
CONFIG_8139TOO_PIOCONFIG_RTL8139TOO_PIO
CONFIG_8139TOO_TUNE_TWISTER CONFIG_RTL8139TOO_TUNE_TWISTER
The -TOO suffix was to distinguish between this and the former 8139
driver, as the two coexisted in 2.2 and 2.3. As
[Jeff Garzik]
It stays "8139too". Donald Becker's rtl8139.c continues to exist
outside the kernel.
Honestly, Jeff, I don't see how it matters -- because if you are
downloading an external driver, you are not going through the config
system anyway.
But ... "maintanicus selector est" (my
[kaos]
> In 2.4.2-ac18 there are 130 CONFIG options that are always derived
> from other options, the user has no control over them.
I've thought about these before ... but never got around to doing
anything about them. I agree they should have a separate namespace.
However, I would vote the
[kaos]
In 2.4.2-ac18 there are 130 CONFIG options that are always derived
from other options, the user has no control over them.
I've thought about these before ... but never got around to doing
anything about them. I agree they should have a separate namespace.
However, I would vote the
[Jörn Nettingsmeier, quoting Robert Muller]
> Just create a shell script called yacc with the following content
> ---
> #!/bin/sh
> bison --yacc $*
> ---
> i ran into the same problem with a school proiject here yesterday
Why does nobody learn shell anymore?
[Jörn Nettingsmeier, quoting Robert Muller]
Just create a shell script called yacc with the following content
---
#!/bin/sh
bison --yacc $*
---
i ran into the same problem with a school proiject here yesterday
Why does nobody learn shell anymore? (Just
[T.L.Madhu]
> I want to add a function defined in my loadeble kernel module as
> system call.
You can't. At least not without hackery -- anything is possible with a
bit of hackery.
And there are at least two good reasons for this. First: adding
syscalls at runtime is a recipe for chaos in
[Jeremy Jackson]
> try command 'man mkinitrd' under redhat for hints about initial
> ramdisk.
I have been puzzled about this for quite some time. Why exactly does
everyone always recommend using 'mkinitrd' on Red Hat systems? It
seems to me that if you are compiling a kernel for a specific
[Dr. Kelsey Hudson]
> umm, last i checked a carriage return wasn't whitespace... space,
> horizontal tab, vertical tab, form feed constitute whitespace IIRC...
Where and when did you check? Several sources disagree with you.
Peter
-
To unsubscribe from this list: send the line "unsubscribe
[Jeff Coy]
> this issue came up frequently with customers uploading scripts in
> binary mode trying to run #!/usr/bin/perl^M. The solution for me was
> to just do the following:
>
> cd /usr/bin
> sudo ln -s perl^V^M perl
So none of your customers tried '#!/usr/bin/perl -w^M'?
[Jeff Coy]
this issue came up frequently with customers uploading scripts in
binary mode trying to run #!/usr/bin/perl^M. The solution for me was
to just do the following:
cd /usr/bin
sudo ln -s perl^V^M perl
So none of your customers tried '#!/usr/bin/perl -w^M'? (Come on,
[Dr. Kelsey Hudson]
umm, last i checked a carriage return wasn't whitespace... space,
horizontal tab, vertical tab, form feed constitute whitespace IIRC...
Where and when did you check? Several sources disagree with you.
Peter
-
To unsubscribe from this list: send the line "unsubscribe
[Jeremy Jackson]
try command 'man mkinitrd' under redhat for hints about initial
ramdisk.
I have been puzzled about this for quite some time. Why exactly does
everyone always recommend using 'mkinitrd' on Red Hat systems? It
seems to me that if you are compiling a kernel for a specific
[T.L.Madhu]
I want to add a function defined in my loadeble kernel module as
system call.
You can't. At least not without hackery -- anything is possible with a
bit of hackery.
And there are at least two good reasons for this. First: adding
syscalls at runtime is a recipe for chaos in
[Steven Friedrich]
> The questions I have are difficult to research because so little info
> exists about 2.4 design philosophy.
I guess the ORA "Linux Device Drivers" 2nd edition is due out Real Soon
Now. It will cover 2.4.
Peter
-
To unsubscribe from this list: send the line "unsubscribe
[Steven Friedrich]
The questions I have are difficult to research because so little info
exists about 2.4 design philosophy.
I guess the ORA "Linux Device Drivers" 2nd edition is due out Real Soon
Now. It will cover 2.4.
Peter
-
To unsubscribe from this list: send the line "unsubscribe
[Kai Germaschewski]
> +list-multi := fore_200e
> +fore_200e-objs := fore200e.o $(FORE200E_FW_OBJS)
list-multi := fore_200e.o
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[Kai Germaschewski]
+list-multi := fore_200e
+fore_200e-objs := fore200e.o $(FORE200E_FW_OBJS)
list-multi := fore_200e.o
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[Ivan Stepnikov]
> I tried to call getrlimit(). It shows only 2G available memory and
> there is no way to increase it.
Right. Architectural limit. There needs to be some room in the
address space for kernel stuff, I/O, etc -- in Linux at least, having
to play with your page tables every
[Ivan Stepnikov]
I tried to call getrlimit(). It shows only 2G available memory and
there is no way to increase it.
Right. Architectural limit. There needs to be some room in the
address space for kernel stuff, I/O, etc -- in Linux at least, having
to play with your page tables every single
[Pierfrancesco Caci]
> Hi there, can someone please tell me what's going wrong with my
> compilation of 2.4.2 ?
Change '-oformat' to '--oformat' 4 places in arch/i386/boot/Makefile.
> Binutils 2.10.91.0.2
This version of binutils no longer accepts the old 'ld -oformat' form
of
[Pierfrancesco Caci]
Hi there, can someone please tell me what's going wrong with my
compilation of 2.4.2 ?
Change '-oformat' to '--oformat' 4 places in arch/i386/boot/Makefile.
Binutils 2.10.91.0.2
This version of binutils no longer accepts the old 'ld -oformat' form
of
[Drew Bertola]
> Feb 23 20:48:24 babylon modprobe: modprobe: Can't locate module binfmt-464c
> Although I've looked through the documentation, I can't find any
> reference to binfmt-464c.
binfmt-464c is ELF -- it means your kernel came across an ELF
executable and was unable to execute it so
[Jon Hart]
> 1. I am unable to mount loopback block devices using kernel 2.4.2.
Apparently fixed in -ac3.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[Jon Hart]
1. I am unable to mount loopback block devices using kernel 2.4.2.
Apparently fixed in -ac3.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[Drew Bertola]
Feb 23 20:48:24 babylon modprobe: modprobe: Can't locate module binfmt-464c
Although I've looked through the documentation, I can't find any
reference to binfmt-464c.
binfmt-464c is ELF -- it means your kernel came across an ELF
executable and was unable to execute it so it
[Peter Bergner]
> The following is a boot log for a 64 bit port of Linux for IBM's 64
> bit PowerPC processors. This log was made on a pSeries model 270
> which uses a POWER3 microprocessor.
Impressive. One question, though --
> starting cpu /cpus/PowerPC,[EMAIL PROTECTED]
> starting cpu
[Peter Bergner]
The following is a boot log for a 64 bit port of Linux for IBM's 64
bit PowerPC processors. This log was made on a pSeries model 270
which uses a POWER3 microprocessor.
Impressive. One question, though --
starting cpu /cpus/PowerPC,[EMAIL PROTECTED]
starting cpu
[John Heil]
> Which -ac series patch does this match up with or superceed ie should
> this be considered superior to -ac19 ?
Neither "supercedes" the other -- they are different trees. The -ac
series has some patches that Linus may never get because they are
experimental, or still buggy.
If
[Christoph Hellwig]
> It would be really good to have something devfs-like just for LVM in
> setups that don't use LVM, so we could avoid mounting root read/write
^^^devfs?
> for device-creation.
For most people, read/write access to /dev is rarely needed -- how
often do
[Christoph Hellwig]
It would be really good to have something devfs-like just for LVM in
setups that don't use LVM, so we could avoid mounting root read/write
^^^devfs?
for device-creation.
For most people, read/write access to /dev is rarely needed -- how
often do
[John Heil]
Which -ac series patch does this match up with or superceed ie should
this be considered superior to -ac19 ?
Neither "supercedes" the other -- they are different trees. The -ac
series has some patches that Linus may never get because they are
experimental, or still buggy.
If you
[Peter Bergner]
> Hopefully someone can point me in the right direction here.
> I need to use different CFLAGS options depending on whether
> I'm compiling arch dependent code or arch independent code.
Use the per-directory $(EXTRA_CFLAGS), and/or the per-file
$(CFLAGS_foo.o). See also
[BERECZ Szabolcs]
> The conclusion: it's cannot be implemented without slowdown.
Or: it cannot be implemented 100% safely and correctly without slowdown.
If you know the use you wish to put this to, and are willing to risk a
permission check somewhere being confused momentarily by a non-atomic
[Alan Cox]
> There is an assumption in the kernel that only the task changes its
> own uid and other related data.
Fair enough but could you explain the potential problems? And how is
it different from sys_setpriority?
Peter
-
To unsubscribe from this list: send the line "unsubscribe
[Peter Samuelson]
> > Race -- you need to make sure the task_struct doesn't disappear out
> > from under you.
> >
> > Anyway, why not use the interface 'chown uid /proc/pid'? No new
> > syscall, no arch-dependent part, no user-space tool, etc.
[Martin Dalecki]
[BERECZ Szabolcs]
> > Race -- you need to make sure the task_struct doesn't disappear out
> > from under you.
>
> Yes, but we need a write_lock, not a read_lock.
No, it's a read_lock because it is locking the task *list*, which is
not being changed. The only thing being changed is data within
[BERECZ Szabolcs]
Race -- you need to make sure the task_struct doesn't disappear out
from under you.
Yes, but we need a write_lock, not a read_lock.
No, it's a read_lock because it is locking the task *list*, which is
not being changed. The only thing being changed is data within a
[Peter Samuelson]
Race -- you need to make sure the task_struct doesn't disappear out
from under you.
Anyway, why not use the interface 'chown uid /proc/pid'? No new
syscall, no arch-dependent part, no user-space tool, etc.
[Martin Dalecki]
Becouse of exactly the same race
[Alan Cox]
There is an assumption in the kernel that only the task changes its
own uid and other related data.
Fair enough but could you explain the potential problems? And how is
it different from sys_setpriority?
Peter
-
To unsubscribe from this list: send the line "unsubscribe
[BERECZ Szabolcs]
The conclusion: it's cannot be implemented without slowdown.
Or: it cannot be implemented 100% safely and correctly without slowdown.
If you know the use you wish to put this to, and are willing to risk a
permission check somewhere being confused momentarily by a non-atomic
[Peter Bergner]
Hopefully someone can point me in the right direction here.
I need to use different CFLAGS options depending on whether
I'm compiling arch dependent code or arch independent code.
Use the per-directory $(EXTRA_CFLAGS), and/or the per-file
$(CFLAGS_foo.o). See also
[BERECZ Szabolcs]
> Here is a new syscall. With this you can change the owner of a running
> procces.
> + if (current->euid)
> + return -EPERM;
Use capable().
> + p = find_task_by_pid(pid);
> + p->fsuid = p->euid = p->suid = p->uid = uid;
Race -- you need to
[Justin Gibbs]
> I've verified the driver's functionality on 25 different cards thus
> far covering the full range of chips from aic7770->aic7899.
That's very good to hear. I know the temptation of only testing on new
hardware; that's why I was concerned.
> Lots of people here at Adaptec look
[Justin Gibbs]
I've verified the driver's functionality on 25 different cards thus
far covering the full range of chips from aic7770-aic7899.
That's very good to hear. I know the temptation of only testing on new
hardware; that's why I was concerned.
Lots of people here at Adaptec look at
[BERECZ Szabolcs]
Here is a new syscall. With this you can change the owner of a running
procces.
+ if (current-euid)
+ return -EPERM;
Use capable().
+ p = find_task_by_pid(pid);
+ p-fsuid = p-euid = p-suid = p-uid = uid;
Race -- you need to make sure
[Jacob Luna Lundberg]
> Just out of curiosity, why can't the specification be along the lines
> of a vendor data file saying ``if you want the printer to do x then
> say y'' and ``if the printer says x then it means y''. That ought to
> add a lot of functionality right there.
Think about it.
[Dennis]
> For example, if there were six different companies that marketed
> ethernet drivers for the eepro100, you'd have a choice of which one
> to buy..perhaps with different "features" that were of value to
> you. Instead, you have crappy GPL code that locks up under load, and
> its not
[Nathan Black]
> This really improved the performance of my dual PIII-866 w/512MB Ram
> and AIC7899 scsi.
[...]
> I would suggest, if at all possible, putting this in the 2.4.2
> kernel.
Have you any idea the breadth of cards and chips that aic7xxx supports?
Sure, Justin's driver does great
[Manfred Spraul]
> > Unless you modify the ABI and pass the array bounds around you won't
> > catch such problems,
[Eric W. Biederman]
> Of course. But this is linux and you have the source. And I did
> mention you needed to recompile the libraries your trusted
> applications depended on.
[Manfred Spraul]
Unless you modify the ABI and pass the array bounds around you won't
catch such problems,
[Eric W. Biederman]
Of course. But this is linux and you have the source. And I did
mention you needed to recompile the libraries your trusted
applications depended on.
So by
[Nathan Black]
This really improved the performance of my dual PIII-866 w/512MB Ram
and AIC7899 scsi.
[...]
I would suggest, if at all possible, putting this in the 2.4.2
kernel.
Have you any idea the breadth of cards and chips that aic7xxx supports?
Sure, Justin's driver does great with
[Dennis]
For example, if there were six different companies that marketed
ethernet drivers for the eepro100, you'd have a choice of which one
to buy..perhaps with different "features" that were of value to
you. Instead, you have crappy GPL code that locks up under load, and
its not worth
[Jacob Luna Lundberg]
Just out of curiosity, why can't the specification be along the lines
of a vendor data file saying ``if you want the printer to do x then
say y'' and ``if the printer says x then it means y''. That ought to
add a lot of functionality right there.
Think about it. A
[Kai Henningsen]
> > There *is* a good way to do this, and it would be really nice if
> > vger could be taught to do it: add a List-Id: header
> > (draft-chandhok-listid-04.txt RFC-to-be, implemented in lots of
> > mailing list managers already).
[Eli Carter]
> Have you looked at the headers
[Kai Henningsen]
There *is* a good way to do this, and it would be really nice if
vger could be taught to do it: add a List-Id: header
(draft-chandhok-listid-04.txt RFC-to-be, implemented in lots of
mailing list managers already).
[Eli Carter]
Have you looked at the headers in an LK
[ac]
> Vast amounts of debian included code contains suggestions about use.
I'll not dispute your word because I know you for an objective person.
But I don't remember coming across any such examples at least recently.
Maybe I just don't remember them because they didn't sound like, well,
[Roberto Diaz]
> > I am trying to make a manifesto in order to attach it to all my
> > gpl'd developments..
[Rik van Riel]
> Quoted from the GPL:
> ---
> 6. Each time you redistribute the Program (or any work based on the
> Program), the recipient automatically receives a license from
[ac]
Vast amounts of debian included code contains suggestions about use.
I'll not dispute your word because I know you for an objective person.
But I don't remember coming across any such examples at least recently.
Maybe I just don't remember them because they didn't sound like, well,
[Michael D. Crawford]
> I found I could mount three partitions on /mnt
Yes. New feature, appeared in the 2.4.0test series, or shortly before.
> and they'd all show up as mounted at /mnt in the "mount" command, but
> if I unmounted one of them (only tried with the currently visible
> one),
[Ishikawa <[EMAIL PROTECTED]>]
> I have no idea why I invoked ver_linux using "." : I must have seen
> it somewhere and just followed it somehow.
Who knows. Anyway, the following works in 'bash' at least -- don't
know about other shells -- but it's quite a hack
Peter
---
[Ishikawa]
> I just noticed that running
>
> . /usr/src/linux/script/ver_linux
>
> prints out strange libc version
[...]
> I found that if the command "ls" is aliased to "ls -aF"
So ... don't use '.' to execute scripts. If there is some
documentation somewhere that told you to do
[Ishikawa]
I just noticed that running
. /usr/src/linux/script/ver_linux
prints out strange libc version
[...]
I found that if the command "ls" is aliased to "ls -aF"
So ... don't use '.' to execute scripts. If there is some
documentation somewhere that told you to do this,
[Ishikawa [EMAIL PROTECTED]]
I have no idea why I invoked ver_linux using "." : I must have seen
it somewhere and just followed it somehow.
Who knows. Anyway, the following works in 'bash' at least -- don't
know about other shells -- but it's quite a hack
Peter
--- scripts/ver_linux~
[Michael D. Crawford]
I found I could mount three partitions on /mnt
Yes. New feature, appeared in the 2.4.0test series, or shortly before.
and they'd all show up as mounted at /mnt in the "mount" command, but
if I unmounted one of them (only tried with the currently visible
one), then it
[Admin Mailing Lists]
> i have no bits directory
Really? What version of libc, and on what Linux distro? I thought all
versions of glibc2 had /usr/include/bits/.
If you are using libc4 or libc5, it is not surprising if the BIND
people didn't notice the problem -- they probably didn't try it.
[John Jasen]
> E upon careful reading of the devfs/devfsd documentation,
> you'll find that it says to put /sbin/devfsd /dev in amongst the
> first lines in rc.sysinit.
> In looking through rc.sysinit, / is not mounted rw until much later.
Who said anything about *re*-mounting '/'?
[Michael J. Dikkema]
> > I went from 2.4.0 to 2.4.1 and was surprised that either the root
> > filesystem wasn't mounted, or it couldn't be read. I'm using devfs.. I'm
> > thinking there might have been a change with regards to the devfs
> > tree.. is the legacy /dev/hda1 still
[me]
> > Richard Gooch (devfs author, from Australia) to switch to the American
> > spelling of the word, for consistency with the rest of the kernel, and
[ac]
> Pardon
>
> include/linux/console_struct.h: unsigned char vc_palette[16*3]; /*
>Colour palette for VGA+ */
>
[William Knop]
> How can DevFS know which devices to add to /dev/scsi/... without
> loading the module and scanning the bus first? Or do you manually
> insert the scsi module when you need it?
If you do 'cd /dev/scsi', the kernel looks it up and finds it missing,
which generates a "lookup"
[Jeremy M. Dolan]
> Disk is spelled 'disk' except for Compact Disc and Digital Versatile
> Disc. If it wasn't 3:30 in the morning, a patch would be attached.
It wouldn't do any good. Many months ago, Ted Ts'o pleaded with
Richard Gooch (devfs author, from Australia) to switch to the American
[Rupa Schomaker]
> In my case, I have two identical Maxtor drives, but they reported
> different geometry.
[...]
> I'm doing RAID1 and it is really nice to have the same geometry so
> that the partition info is the same between the two drives. Makes
> life easier.
If that's what you needed,
[Rupa Schomaker]
In my case, I have two identical Maxtor drives, but they reported
different geometry.
[...]
I'm doing RAID1 and it is really nice to have the same geometry so
that the partition info is the same between the two drives. Makes
life easier.
If that's what you needed, you
[Jeremy M. Dolan]
Disk is spelled 'disk' except for Compact Disc and Digital Versatile
Disc. If it wasn't 3:30 in the morning, a patch would be attached.
It wouldn't do any good. Many months ago, Ted Ts'o pleaded with
Richard Gooch (devfs author, from Australia) to switch to the American
[William Knop]
How can DevFS know which devices to add to /dev/scsi/... without
loading the module and scanning the bus first? Or do you manually
insert the scsi module when you need it?
If you do 'cd /dev/scsi', the kernel looks it up and finds it missing,
which generates a "lookup" event
[me]
Richard Gooch (devfs author, from Australia) to switch to the American
spelling of the word, for consistency with the rest of the kernel, and
[ac]
Pardon
include/linux/console_struct.h: unsigned char vc_palette[16*3]; /*
Colour palette for VGA+ */
1 - 100 of 579 matches
Mail list logo
