[EMAIL PROTECTED] said:
> As a producer of free software myself (Icarus Verilog) I've come to
> the conclusion that the mass media is perfectly capable of turning
> away the idiots that you don't really want as customers anyhow:-)
Actually, I didn't intend that to go out to a public forum, as I
On Fri, 15 Dec 2000 15:37:29 +0100,
Ingo Oeser <[EMAIL PROTECTED]> wrote:
>> Trace; c01091d8
>
>> Trace; c0105000
>> Trace; c0100191
>
>Once again we have these two symbols on the stack.
Probably spurious. Remember that ix86 show stack prints anything that
looks like a kernel address, wheth
hi!
Using nmapfe/nmap as root locks or reboots the kernel at once. No logs,
nothing...
Nmap version was nmap-2.54BETA16.tar.bz2
If I can do more, please give me a hint...currently I dont know,
what I can do without any log...
Meino
-
To unsubscribe from this list: send the line "unsubsc
Hello Michael, I wonder about this patch which only fixes an Id/author but no
code. It may be perfectly normal, but could also come from a mangled file in
one of your trees. Just for info anyway...
Cheers,
Willy
> diff -r -u -x CVS -x *.o linux-2.2.18pre25-VIRGIN/fs/proc/openpromfs.c
zinux/fs/p
On Fri, 15 Dec 2000 19:37:49 -0800 (PST),
[EMAIL PROTECTED] wrote:
>Do you have an alternative reccomendation? I've shown where the symlink
>method WILL fail. You disagree that having the configured headers copied
>is a workable idea. What else is there?
Use the pcmcia-cs method. Ask where the
[EMAIL PROTECTED] said:
> FYI Guys, This just went over the wire from CSN. Might need some
> damage control.
... and I wonder about the press that MSVC 6.0 got before the first
few service packs got released. (Weren't there a few difficulties
with MFC42.dll? Correct me if I'm wrong.)
As a pr
"Barry K. Nathan" wrote:
>
> I got the same error with the ipchains-compatible netfilter compiled as
> modules.
This works for me:
--- linux-2.4.0-test13-pre2/net/ipv4/netfilter/Makefile Sat Dec 16 14:23:48 2000
+++ linux-akpm/net/ipv4/netfilter/Makefile Sat Dec 16 15:01:23 2000
@@ -61,6 +
In article <[EMAIL PROTECTED]>,
Barry K. Nathan <[EMAIL PROTECTED]> wrote:
>I got the same error with the ipchains-compatible netfilter compiled as
>modules. Compiling into the kernel instead, I also get an error. I've
>included the error and my .config below.
Try removing "$(ip_conntrack-objs) $
On Thu, 14 Dec 2000 14:55:59 -0500,
Gerard Beekmans <[EMAIL PROTECTED]> wrote:
>Every time I try to copy a specific directory to a mounted loop file system,
>Linux freezes up on me. I've tried this several times and it freezes up at
>the same place every time. When I copy that same directory to
I got the same error with the ipchains-compatible netfilter compiled as
modules. Compiling into the kernel instead, I also get an error. I've
included the error and my .config below.
-Barry K. Nathan <[EMAIL PROTECTED]>
ld -m elf_i386 -r -o netfilter.o ipchains.o ip_nf_compat.o
ip_nf_compat.o:
Hi,
The sound (emu10k1) seems to be broken under 2.2.18.
If I do:
cat x > /dev/dsp
I get:
bash: /dev/dsp: No such device
But an ls -l shows:
crw-rw-rw- 1 root sys 14, 3 Dec 15 21:25 dsp
crw-rw-rw- 1 root sys 14, 19 Dec 15 21:25 dsp1
Same thing with
I got this also, but the compile worked with nfs/nfsd compiled in. Same
thing with netfilters. Problem now is ACPI hung after
initialization...not a hard hang (ctrl/alt/del still worked) but it was
waiting for something it never got.
-dwild
On Sat, 16 Dec 2000, Jon Akers wrote:
> Date: Sat, 1
This appears to be a problem with the Makefile changes and NFS/NFSD/lockd
and module compilation.
Using egcs-2.91.66, modutils version 2.3.18, GNU Make version 3.77, GNU ld
version 2.10.91 (with BFD 2.10.0.33)
make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
cd /lib/modules/2.4.0-test1
ld -m elf_i386 -r -o ip_nf_compat.o ipfwadm_core.o ip_fw_compat.o
ip_fw_compat_redir.o ip_fw_compat_masq.o ip_conntrack_standalone.o
ip_conntrack_core.o ip_conntrack_proto_generic.o
ip_conntrack_proto_tcp.o ip_conntrack_proto_udp.o
ip_conntrack_proto_icmp.o ip_nat_standalone.o ip_nat_rule.o
ip_nat
On Sat, 16 Dec 2000, infernix wrote:
> Hi,
>
> After compiling 2.4.0-test12 on my (P2-266, 440LX) Debian 2.2 system (make
> bzdisk), i am unable to boot the kernel. When I boot up with the floppy
> disk, I do get the Loading.. screen (I think it does load completely),
> but afterwards I get t
On Fri, 15 Dec 2000, richard offer wrote:
> In article <91e0vj$b6alr$[EMAIL PROTECTED]> you write:
> >In article <[EMAIL PROTECTED]>,
> >LA Walsh <[EMAIL PROTECTED]> wrote:
> >>It was at that
> >>point, the externally compiled module "barfed", because like many modules,
> >>it expected, like ma
On Fri, 15 Dec 2000, J . A . Magallon wrote:
>
> On 2000/12/15 Werner Almesberger wrote:
> > LA Walsh wrote:
> >
> > Exception: opaque types; there one would have to go via a __ identifier,
> > i.e.
> >
> > /foo.h defines struct __foo ...;
> > /bar.h includes /foo.h
> >and u
On 15 Dec 2000, Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>,
> LA Walsh <[EMAIL PROTECTED]> wrote:
> >It was at that
> >point, the externally compiled module "barfed", because like many modules,
> >it expected, like many externally compiled modules, that it could simply
> >ac
On Fri, 15 Dec 2000, Ingo Oeser wrote:
> On Fri, Dec 15, 2000 at 09:31:57AM -0800, [EMAIL PROTECTED] wrote:
> > > Maybe you did not notice, but for months we have
> > > /lib/modules/`uname -r`/build/include, which points to kernel headers,
> > > and which should be used for compiling out-of-tre
Hello all,
One of my linux servers crash with a 'kernal panic: VFS: LRU block list
corrupted' message on my screen.
I reboot with a boot disk - it was find, then rebooted of the hard drive
and it was fine. The systems is runing fine
now, but i thought maybe someone on this list could explain t
[skip to the end for syslog snippet, full dmesg and lspci -v -v -v output &
.config]
Hi,
I'm fighting my PPro200 desktop to get it to support the USB pci card I just
bought. At first the entire computer became instable but choosing CMD640
chipset support solved that problem.
But now I find that
In article <91e0vj$b6alr$[EMAIL PROTECTED]> you write:
>In article <[EMAIL PROTECTED]>,
>LA Walsh <[EMAIL PROTECTED]> wrote:
>>It was at that
>>point, the externally compiled module "barfed", because like many modules,
>>it expected, like many externally compiled modules, that it could simply
>>ac
I got the following errors compiling the kernel 2.4.0-test12
mga_dma.c: In function `mga_irq_install':
mga_dma.c:821: structure has no member named `next'
make[3]: *** [mga_dma.o] Error 1
make[3]: Leaving directory `/u2/src/linux-2.4.0/drivers/char/drm'
i810_dma.c: In function `i810_irq_instal
This is mostly still Makefile updates. Right now there are still
architecture-specific Makefiles that haven't been updated, but x86 and
sparc are done, along with the drivers you can enable for those
architectures. Expect the other architectures to follow soonish.
The other large part is the ACP
On Fri, 15 Dec 2000, Linus Torvalds wrote:
> Please instead do the same thing /dev/tty does, namely a sane interface
> that shows it as a symlink in /proc (or even in /dev)
There you go... (/proc/tty/console -> /dev/tty; may very well
be dangling, but then you have a current VC even if your /
FYI Guys, This just went over the wire from CSN. Might need some damage
control.
Jeff
- Forwarded message from PaperBoy <[EMAIL PROTECTED]> -
Return-Path: <[EMAIL PROTECTED]>
Received: from stmpy-1.cais.net (stmpy-1.cais.net [205.252.14.71])
by vger.timpanogas.org (8.9.3/8.9
> It's not in the X tree or anything, but here's a personal example.
> Machine: Dual P3 550
> HDD: Dual Ultra2Wide Seagate 18GB Hdd
> OS: RedHat 7
> Compile Target: Linux Kernel 2.2.17
> Result with gcc 2.96: Failure (syntax errors in the i386 branch of the
> arch tree)
> Result with compat-egcs-6
On Thu, 14 Dec 2000, Linus Torvalds wrote:
> Yes.
>
> And I realize that somebody inside RedHat really wanted to use a snapshot
> in order to get some C++ code to compile right.
>
> But it at the same time threw C stability out the window, by using a
> not-very-widely-tested snapshot for a maj
> Hi Linus, Alan,
>
> some applications do need to know where the console (/dev/console)
> actually maps to. For processes with a controlling terminal, you may see
> it in /proc/$$/stat. However, daemons are supposed to run detached (they
> don't want to get killed by ^C) and some processes lik
On Sat, 16 Dec 2000, Jeff Chua wrote:
>
> > Now, I also agree that we should be able to clean this up properly for
> > 2.5.x, and actually do exactly this for the anonymous buffers, so that
> > the VM no longer needs to worry about buffer knowledge, and fs/buffer.c
> > becomes just another user
On Sat, 16 Dec 2000, Kurt Garloff wrote:
>
> The kernel provides this information -- sort of:
> It contains the TIOCTTYGSTRUCT syscall which returns a struct. Of course,
> it changes between different kernel archs and revisions, so using it is
> an ugly hack. Grab for TIOCTTYGSTRUCT_HACK in the
Hi,
After compiling 2.4.0-test12 on my (P2-266, 440LX) Debian 2.2 system (make
bzdisk), i am unable to boot the kernel. When I boot up with the floppy
disk, I do get the Loading.. screen (I think it does load completely),
but afterwards I get this error:
0224
AX:0212
BX:BC00
CX:5101
DX:000.
> Now, I also agree that we should be able to clean this up properly for
> 2.5.x, and actually do exactly this for the anonymous buffers, so that
> the VM no longer needs to worry about buffer knowledge, and fs/buffer.c
> becomes just another user of the writepage functionality. That is not
> all
Hi Linus, Alan,
some applications do need to know where the console (/dev/console)
actually maps to. For processes with a controlling terminal, you may see
it in /proc/$$/stat. However, daemons are supposed to run detached (they
don't want to get killed by ^C) and some processes like init or boo
Harley Anderson wrote:
> Howdy again folks, I have another oops for ya's to look over...
>
> Yesterday when I was about to patch and build the new (test12) kernel I found
> the ominous message:
> Kernel panic: attempted to kill init!
> Something like that anyway. No other info, just locked up sol
Alan Cox wrote:
>
> > Both of these methods have problems, especially with the proposed
> > preemptions changes. The first case causes the thread to run with the
> > BKL for the whole time. This means that any other task that wants the
> > BKL will be blocked. Surly the needed protections don'
Russell King wrote:
>
> Rogier Wolff writes:
> > Alan Cox wrote:
> > > What better interactivity ;)
> > Thus to me, 2.4 FEELS much less interactive. When I move windows they
> > don't follow the mouse in real-time.
>
> Interesting observation: in a scrolling rxvt, kernel 2.0 is smoother than
> 2
> Both of these methods have problems, especially with the proposed
> preemptions changes. The first case causes the thread to run with the
> BKL for the whole time. This means that any other task that wants the
> BKL will be blocked. Surly the needed protections don't require this.
The BKL i
> From: Borislav Deianov [mailto:[EMAIL PROTECTED]]
>
> In article <[EMAIL PROTECTED]> you wrote:
> >> > oWe tell vendors to build RPMv3 , glibc 2.1.x
> >> Curious HOW do you tell vendors??
>
> > When they ask. More usefully Dan Quinlann and most vendors
> put together a
> > recommended
> > I guess that when you mmap large files over nfs and write to them, you get
> > similar problems.
> >
> > > Oh, and try to eat atomic memory by ping -f kORBit-ized box.
> >
> > When linux is out of atomic memory, it will die anyway.
>
> Not unless your driver is broken.
ok_to_allocate:
Hi,
why is pci_match_device supposed to return a _const_ struct
pci_device_id?What are the implications of defining it this way?
Is it just a contract or the compiler/linker does smt special with it if
its const?
Sorry if the second part of the question is a bit OT.
Jani
-
To unsubscri
On Fri, 15 Dec 2000, Linus Torvalds wrote:
> I'm surprised: "yenta_init()" will re-initialize the yenta
> PCI_BASE_ADDRESS_0 register, but maybe there's something wrong there. Try
right - but it is just writing back the bogus 0xe6000 thing.
> adding a pci_enable_device() to turn the device on a
Jason Wohlgemuth wrote:
>
> In an effort to stay consistent with the community, I migrated some code
> to a driver to use the daemonize() routine in the function specified by
> the kernel_thread() call.
>
> However, in looking at a few drivers in the system (drivers/usb/hub.c ,
> drivers/md/md.c
In article <[EMAIL PROTECTED]> you wrote:
>> > o We tell vendors to build RPMv3 , glibc 2.1.x
>> Curious HOW do you tell vendors??
> When they ask. More usefully Dan Quinlann and most vendors put together a
> recommended set of things to build with and use. It warns about library
> pitfalls, ker
Joe deBlaquiere wrote:
> but actually the best thing about it is
> that the compiler people of the work might make generating a proper
> cross-toolchain less difficult by one or two magnitudes...
You have a point here ... particularly gcc-glibc interdependencies are
a little irritating (not sur
J . A . Magallon wrote:
> Easier: public kernel interfaces only work through pointers.
Requires more elaborate wrappers or a new layer of wrapper functions
around system calls, if you want to make this completely general.
Also, doesn't provide FOOSIZE to "public" space.
> Too kind-of-classroom-n
Thanks for all the reponses.
I happened to have /home in its own partition, so I reinstalled from
scratch via CD and installed all the security updates, among a
myriad of other security measures.
I decided not to restore /usr/local from backups, but instead to
rebuild everything in /usr/local fr
John Summerfield <[EMAIL PROTECTED]> writes:
[...]
> 3) When I then switch back to a virtual console, the screen blanks
> and switches to power-saving mode.
Which powersave mode? There are three, IIRC. You can tell them apart
by the color of or whether the light blinks on some monitors.
If th
On Fri, 15 Dec 2000, Dana Lacoste wrote:
> We really need a documented way to deal with this! It's getting silly
> the number of questions that people ask!
Please, that would be helpful - I'm still using a heavily mutated
slackware 3.1 that's been hacked up to the same level (if not beyond) as
R
Hi,
Im running Redhat 6.2 i386 and Ive recently upgraded to the 2.2.17 kernel.
The reason for the kernel upgrade was that the select() call in one of the
programs I wrote, crashes periodically (once a day in the evening). I was
wondering if anyone has heard of anything like that, and if so, w
Lukasz Trabinski wrote:
> include/linux/pci_ids.h:#define PCI_DEVICE_ID_OXSEMI_16PCI954 0x9501
>
> (IMHO that is correct), but in kernel 2.2.18 we have:
> (include/kernel/pci.h)
> #define PCI_DEVICE_ID_OXSEMI_16PCI954PP0x9513
> ^^
>
> Please correct
On Fri, Dec 15, 2000 at 11:53:58PM +0100, Philipp Schmid wrote:
>
> i'm going to buy a notebook in the near future, which supports bluetooth.
> so my question is: is anyone working on bluetooth drivers or do i have to
> forget about it ?
There's a bluetooth USB driver already in the kernel, and
Werner Almesberger wrote:
> Joe deBlaquiere wrote:
>
>> My solution to this has always been to make a cross compiler environment
>
>
> ;-))) I think lots of people would really enjoy to have "build a
> cross-gcc" added to the prerequisites for installing some driver
> module ;-)
>
> I know,
On 2000/12/15 Werner Almesberger wrote:
> LA Walsh wrote:
>
> Exception: opaque types; there one would have to go via a __ identifier,
> i.e.
>
> /foo.h defines struct __foo ...;
> /bar.h includes /foo.h
>and uses #define FOOSIZE sizeof(struct __foo)
> /foo.h either typedef st
> I am not sure it is a big deal. If you read the
> comment it was more of an off-the-cuff remark.
>
> I doubt anyone would testify in court that McNealy
> said this. The only way it is something to worry
> about is if they used it in a printed format (IANAL)
Law isn't an all-or-nothing thing.
Is anyone besides me getting multiple copies of Jeff Epler's message? I've
gotten at least a couple of dozen copies of this (and another long message by
Ted T'so with the subject "Re: Serial cardbus code for testing, please.
") since yesterday. They arrive once or twice an hour, all da
On Fri, Dec 15, 2000 at 03:56:52PM -0600, Jesse Pollard wrote:
> [..] A null expression, specified with
> the ";" is a small price to pay for simplifying the error detection. [..]
I'm not convinced this is a significant simplification (also considering the
"hard" way is just working fine). I thin
> I guess that when you mmap large files over nfs and write to them, you get
> similar problems.
>
> > Oh, and try to eat atomic memory by ping -f kORBit-ized box.
>
> When linux is out of atomic memory, it will die anyway.
Not unless your driver is broken.
Alan
-
To unsubscribe from this lis
--- Dana Lacoste <[EMAIL PROTECTED]> wrote:
> I don't think he did that at all :
> (Devil's Advocate time :)
Always a fun occupation. :)
> What he did was say that, while everyone was looking
> at Linux as the solution to modern computing
> problems,
> he didn't need to : he already has Solaris.
I Previously Wrote:
> Could someone explain why send is failing with EPIPE on the 2.4.x
> kernel, while it is working with the 2.2.x kernels.
It turns our the socket family was not being set to AF_INET :/
It was working in 2.2.x because in our situation the sock family was being
initialized to A
- Received message begins Here -
> From: Andrea Arcangeli <[EMAIL PROTECTED]>
> On Fri, Dec 15, 2000 at 11:18:35AM -0800, Ulrich Drepper wrote:
> > Andrea Arcangeli <[EMAIL PROTECTED]> writes:
> >
> > > x()
> > > {
> > >
> > > switch (1) {
> > > case 0:
> > > case 1:
> >
Gnome vs kde2: ja ich verwende kde2 auf debian, na und ?
MIME-Version: 1.0
Message-Id: <00121523535800.06182@dagobert>
Content-Transfer-Encoding: 8bit
hi,
i'm going to buy a notebook in the near future, which supports bluetooth.
so my question is: is anyone working on bluetooth drivers or do i h
Hi,
Linux-2.4.0-test12 doesn't boot on VAIO PCG-N505SN,
whereas linux-2.2.10 works fine (both booted by lilo-21).
It just hangs after printing:
Uncompressing Linux... Ok, booting the kernel.
HANG
Btw. Raw bzImage booted over USB-floppy just reboots...
Can this be infamous A20 again ?
Regards,
Greetings,
I just built test13-pre1 and have some unresolved nfs symbols.
Here's the relevant portion of .config:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
"make oldconfig dep bzImage modules" ran file.
"make modules_install" generated the follo
Matt D. Robinson wrote:
> I personally think the definition of an environment variable to point to
> a header file location is the right way to go.
I see two disadvantages of this, compared to a script:
- need to hard-code a default (unless we assume the variables are always
set)
- the way h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
[...please CC me on replies, as I generally only read the list via the
archives...]
I've asked the list before on a similar topic and haven't gotten any
replies, but it's happening again with a different k
> From: Werner Almesberger [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 1:21 PM
> I don't think restructuring the headers in this way would cause
> a long period of instability. The main problem seems to be to
> decide what is officially private and what isn't.
---
If someo
LA Walsh wrote:
> I think in my specific case, perhaps, linux/malloc.h *is* a public
> interface that is to be included by module writers and belongs in the
> 'public interface dir -- and that's great. But it includes files like
> 'slab.h' which are kernel mm-specific that may change in the
Joe deBlaquiere wrote:
> My solution to this has always been to make a cross compiler environment
;-))) I think lots of people would really enjoy to have "build a
cross-gcc" added to the prerequisites for installing some driver
module ;-)
I know, it's not *that* bad. But it still adds quite a f
In article <[EMAIL PROTECTED]>,
LA Walsh <[EMAIL PROTECTED]> wrote:
>It was at that
>point, the externally compiled module "barfed", because like many modules,
>it expected, like many externally compiled modules, that it could simply
>access all of it's needed files through /usr/include/linux whic
Hello
I'm tring to use serial driver 5.05 with kernel in version
2.2.18. There is a little problem with vendor definition in kernel source.
In serial dirver from Theodore Ts'o we have:
{ PCI_VENDOR_ID_SPECIALIX, PCI_DEVICE_ID_OXSEMI_16PCI954,
PCI_VENDOR_ID_SPECIALI
On Fri, Dec 15, 2000 at 07:51:04PM +, Alan Cox wrote:
> Ok this is the first block of changes before we merge the VM stuff. This is
> mostly the bits left over from the 2.2.18 port that were deferred as too
> risky near the end of a prerelease set and some bug swats
I believe Brad Douglas h
The following new items have been added to the Scheduling
Scalability project on SourceForge:
- Description of a priority queue scheduler implementation.
- Description of a multi-queue scheduler implementation.
- Prototype code for the above implementations.
- Preliminary benchmark results.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob Landley <[EMAIL PROTECTED]> writes:
> Heads up everybody. Scott McNealy has apparently been
> calling Solaris Sun's implementation of Linux.
> Trademark violation time.
Yeah... isn't he a moron :)
> Assuming the quote is accurate (which, bei
> > > > For one of our demos, we ran a file server on a remote linux box (that we
> > > > just had a user account on), mounted it on a kORBit'ized box, and ran
> > > > programs on SPARC Solaris that accessed the kORBit'ized linux box's file
> > > > syscalls. If nothing else, it's pretty nifty wh
My solution to this has always been to make a cross compiler environment
(even if it is the same processor family). Thusly i386-linux-gcc knows
that the target system's include files are in:
/usr/local/-tools/i386-linux/include (/linux, /asm)
The other advantage to this is that I can switch my
Rob Landley wrote :
> Sun feels that their core product, Solaris, is
> threatened by Linux. They have several options:
> A) Jump on board and use Linux on their hardware.
> B) Improve Solaris until it can compete on its own
> merits.
> C) Market Solaris better, to make people want Solaris
> inst
Jens Petersohn writes:
> I have an application in which it would be useful to have access to
> remote serial ports as if they where local ports.
>
> Machine A has several serial ports on it connected to various
> special types of devices in a locked machine room.
>
> Developers on workstation B
Hi!
> > > For one of our demos, we ran a file server on a remote linux box (that we
> > > just had a user account on), mounted it on a kORBit'ized box, and ran
> > > programs on SPARC Solaris that accessed the kORBit'ized linux box's file
> > > syscalls. If nothing else, it's pretty nifty what
On Fri, Dec 15, 2000 at 07:54:33PM +0100, Andrea Arcangeli wrote:
> On Fri, Dec 15, 2000 at 06:59:24PM +0100, Franz Sirl wrote:
> > It's required by ISO C, and since that's the standard now, gcc spits out a
> > warning. Just adding a ; is enough and already done for most stuff in
> > 2.4.0-test1
On Fri, Dec 15, 2000 at 06:09:16PM -0200, Rik van Riel wrote:
> On Fri, 15 Dec 2000, Andrea Arcangeli wrote:
>
> > And yes I can see that the whole point of the change is that
> > they want to also forbids this:
> >
> > x()
> > {
> > goto out;
> > out:
> > }
> >
> > and I dislike not being
Hi.
> > For one of our demos, we ran a file server on a remote linux box (that we
> > just had a user account on), mounted it on a kORBit'ized box, and ran
> > programs on SPARC Solaris that accessed the kORBit'ized linux box's file
> > syscalls. If nothing else, it's pretty nifty what you can
On Fri, Dec 15, 2000 at 05:55:08PM -0200, Rik van Riel wrote:
> On Fri, 15 Dec 2000, Andrea Arcangeli wrote:
>
> > x()
> > {
> >
> > switch (1) {
> > case 0:
> > case 1:
> > case 2:
> > case 3:
> > ;
> > }
> > }
> >
> > Why am I required to put a `;' only in the last
On Fri, Dec 15, 2000 at 04:06:36PM -0300, Horst von Brand wrote:
> "Richard B. Johnson" <[EMAIL PROTECTED]> said:
>
> [...]
>
> > Both examples allow an extern declaration inside a function scope
> > which is also contrary to any (even old) 'C' standards. 'extern'
> > is always file
On Fri, 15 Dec 2000, Andrea Arcangeli wrote:
> And yes I can see that the whole point of the change is that
> they want to also forbids this:
>
> x()
> {
> goto out;
> out:
> }
>
> and I dislike not being allowed to do the above as well infact ;).
What's wrong with the - more readable -
Hi!
> >[David Feuer]
> > > Perhaps it would be good to put a check in unlink to make sure that
> > > this is not the last link to a swapfile.
> >
> >Much better to add code to /sbin/swapon and /sbin/swapoff to set and
> >clear immutable bit. Sure it only works on ext2 but how far do you
> >want
On Fri, 15 Dec 2000, Matt Bernstein wrote:
> In the file net/ipv4/ipconfig.c is a variable called ic_enabled which is
> initialised to zero and never set anywhere. a check is made and bootp
> isn't run if its not set. Setting it to 1 before the check makes it appear
> to work.
If I change the ic
Alan Cox wrote:
> Ok this is the first block of changes before we merge the VM stuff. This is
> mostly the bits left over from the 2.2.18 port that were deferred as too
> risky near the end of a prerelease set and some bug swats
And here is the 64-bit printk patch -- a backport of the 2.4.0 code
Alan Cox wrote:
> Ok this is the first block of changes before we merge the VM stuff. This is
> mostly the bits left over from the 2.2.18 port that were deferred as too
> risky near the end of a prerelease set and some bug swats
Here's the procfs patch again... :) Because the 2.2.18 procfs api i
On Fri, Dec 15, 2000 at 11:18:35AM -0800, Ulrich Drepper wrote:
> Andrea Arcangeli <[EMAIL PROTECTED]> writes:
>
> > x()
> > {
> >
> > switch (1) {
> > case 0:
> > case 1:
> > case 2:
> > case 3:
> > ;
> > }
> > }
> >
> > Why am I required to put a `;' only in the la
On Fri, 15 Dec 2000, Andrea Arcangeli wrote:
> x()
> {
>
> switch (1) {
> case 0:
> case 1:
> case 2:
> case 3:
> ;
> }
> }
>
> Why am I required to put a `;' only in the last case and not in
> all the previous ones?
That `;' above is NOT in just the l
Ok this is the first block of changes before we merge the VM stuff. This is
mostly the bits left over from the 2.2.18 port that were deferred as too
risky near the end of a prerelease set and some bug swats
2.2.19pre1
o Basic page aging(Neil Schemenauer)
--- Larry McVoy <[EMAIL PROTECTED]> wrote:
> Yup, that's Scooter (all the Sun old timers call him
> Scooter, I dunno where
> it came from, I wasn't enough of an old timer).
> And, yeah, he does a lot
> of marketing. But in many respects, he's the
> perfect CEO. He's always
> out in public, pu
Werner Almesberger wrote:
>
> Alexander Viro wrote:
> > In the situation above they should have -I/include
> > in CFLAGS. Always had to. No links, no pain in ass, no interference with
> > userland compiles.
>
> As long as there's a standard location for "",
> this is fine. In most cases, the tre
--- Rik van Riel <[EMAIL PROTECTED]> wrote:
> On Thu, 14 Dec 2000, Rob Landley wrote:
> > >people just don't get it, do you? All Linux
> > >applications run on Solaris, which is our
> > >implementation of Linux. Now ask the question
> again,"
>
> I wouldn't worry about this. It's only a quest
--- "Jon 'maddog' Hall, Executive Director, Linux
International" <[EMAIL PROTECTED]> wrote:
> [Warning: Highly controversial topic ahead.
> Messenger does not want to be shot]
Aw come on, it's traditional. :)
> This does bring up an interesting situation.
>
> The Linux community keeps saying t
Andrea Arcangeli <[EMAIL PROTECTED]> writes:
> x()
> {
>
> switch (1) {
> case 0:
> case 1:
> case 2:
> case 3:
> ;
> }
> }
>
> Why am I required to put a `;' only in the last case and not in all
> the previous ones? Or maybe gcc-latest is forgetting to
> Now we know when we can block so we can run f_ops->write ourselfs that's also
> more efficient in terms of both performance and also memory pressure during
> swap of course.
Yep
> As said reiserfs AFIK didn't need any change, so only VFS is using
> fs_down/fs_up from the point of view of reise
On Fri, Dec 15, 2000 at 06:46:32PM +, Alan Cox wrote:
> so the actual problem is either - the returning 1 when it is the wrong answer
> - or the failure to block somewhere else (where its safe) based on a kpiod
> maintained semaphore ?
The problem is not to find a safe place where to wait, th
"Richard B. Johnson" <[EMAIL PROTECTED]> said:
[...]
> Both examples allow an extern declaration inside a function scope
> which is also contrary to any (even old) 'C' standards. 'extern'
> is always file scope, there's no way to make it otherwise.
AFAIR (rather dimly... no K&
1 - 100 of 204 matches
Mail list logo
