> Leave the copyright messages alone is all I can say. And as to your flag,
> well we've got one. Try the 'quiet' boot option
YOU> Leaving copyright messages also saves the purpose of motivating - not
all but
YOU> many - developers. People who _see_ the printk copyright messages is a
_very_
YOU>
[...]
>A signal number cannot be opened more than once concurrently;
>sigopen() thus provides a way to avoid signal usage clashes
>in large programs.
YOU> Signals are a pretty dopey API anyway -
Exactly. When signals were made up, signalhandlers were supposed to
not so mu
>> x86 only (and similar, e.g. Crusoe)
> Again, Linux is the only system that CAN run on anything from PDA thorough
> supercomputer clusters.
What about NetBSD? :o)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More m
> TCP is NOT a guaranteed protocol -- you can't just blast data from one
port
> to another and expect it to work.
Isn't it? Are you really sure about that? I thought UDP was the
not-guaranteed-one and TCP was the one guaranting that all data reaches the
other end in order and all. Please enlighte
Yeah, and while you're at it: make it closed source and ask big time $$
for every single line of update.
If your stupid idea will be followed, a lot of african people will not
be happy. (me neither. proud owner of a 486 (at home))
-Original Message-
From: Daniel [mailto:[EMAIL PROTECTED]]
(This message was BCC'd to multiple people)
Hi,
A sad event occured today; I accidently managed to get a virus sent trough
my pc.
Because of that, I'm sending this message to everyone in my addressbook
since I'm
not totally sure who got one (the virus), and who not.
I'll take all care that this
On my dual pii system, I get these messages:
May 9 15:53:18 marlboro.intranet.vanheusden.com kernel: KERNEL: assertion
(tp->lost_out == 0) failed at tcp_input.c(1202):tcp_remove_reno_sacks
Is this worrying?
More info:
marlboro:~$ uname -a
Linux marlboro 2.4.3 #4 SMP Sun May 6 13:23:49 GMT+1 2001
See this program:
int main(int argc, char *argv[])
{
int h;
char buffer[16];
int nbytes=16,nbits=16*8;
int nin;
h=open("/dev/random", O_RDONLY);
if (h==-1) exit(1);
/* see how many bits there are in it */
printf("returned: %d\n", i
Would anyone be intrested (besides me) in a kernel which can page
out certain parts of itself? The kernel should be in some kind of
vmlinux-ish (as in: uncompressed) format on disk for on-demand
re-loading of pages which are discarded.
Certain parts of drivers could get the __pageable prefix or so
Hi,
I have a dec alpha 300 with a scsi disk which is doing nothing 100% of
the time. Actually; nothing usefull, apart from the seti@home process :o)
I like to do a continues stress-test of the ext3 filesystem which aborts
when something fails. Am I helping anyone with that? In that case: what
app
> AB> 2. Given that otherwise in at least my application (and machine
> AB> without keyboard and mouse can't be too uncommon) there is *no*
> AB> entropy otherwise, which is rather easier for a hacker. At least
> Put a soundcard in your system and install audio-entropyd.
> Works pretty nice.
I> Do
AP> Do you think it worth an effort ?
One could ask this question for all optimalisations.
In fact; for every project.
-
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-
Hi,
I have an idea: I have a couple of linux-systems running in a intranet which
is not connected to do outside world in any way. Since they're only used for
calculations for which there is no harm if anyone would tamper with them,
security is not neccessary. The only thing important, is performa
>> However, only 3 drivers in drivers/net actually set
>> SA_SAMPLE_RANDOM when calling request_irq(). I believe
>> all of them should.
> No, because an attacker can potentially control input and make it
> non-random.
AB> 2. Given that otherwise in at least my application (and machine
AB> without
> Finished & tested my random PID kernel/fork.c:get_pid() replacement.
> > This one keeps track of the last N (default is 64) pids who have exited.
> > These are then not used. So, one cannot have more then 32767 - (64 + 1
> > (init) + 1 (idle)) = 32761 processes :o)
> DW> Huh, should be 3270
> Finished & tested my random PID kernel/fork.c:get_pid() replacement.
> This one keeps track of the last N (default is 64) pids who have exited.
> These are then not used. So, one cannot have more then 32767 - (64 + 1
> (init) + 1 (idle)) = 32761 processes :o)
DW> Huh, should be 32701, right?!
Y
Finished & tested my random PID kernel/fork.c:get_pid() replacement.
This one keeps track of the last N (default is 64) pids who have exited.
These are then not used. So, one cannot have more then 32767 - (64 + 1
(init) + 1 (idle)) = 32761 processes :o)
I know that it was all implemented before,
People,
Somehow I must have lost my brain.
In exit.c I introduced some array:
pid_t pidarray[100];
in fork.c I refer to this array:
extern pid_t pidarray[100];
(or something like that. looked it up in K&R, couldn't
find what I did wrong)
for some reason the kernel build process complains
abo
Hi,
This very small patches re-orders 2 if-statements so that in the
most common case 1 less if-statement is executed, in the worst
case the same number of if-statements is executed (doesn't matter
though: it's would be the fault-situation anyway).
diff -ur --minimal linux-vanilla/kernel/exit.c
> That's not the OOM killer however, but init dying because it
> couldn't get the memory it needed to satisfy a page fault or
> somesuch...
Ehrm, I would like to re-state that it still would be nice if
some mechanism got introduced which enables one to set certain
processes to "cannot be killed".
> Since the system will panic if the init process is chosen by
> the OOM killer, the following patch prevents select_bad_process()
> from picking init.
Hmmm, wouldn't it be nice to make this all configurable? Like; have
some list of PIDs that can be killed?
I would hate it the daemon that checks
> Ok, the question is: does anyone know a place on the web where I can find
> specifications of ISA-slots? I need to know what is supposed to be
connected
> to
> the pins (1, 2, 6, etc.)
AO> It is supposed to do that!
Yes, I guess so!
AO> That sounds like the card that came with an old DOS debug
Hi,
I have this mysterious 8 bit ISA card with nothing more then 2 smb-mounted
ic's
and a button. It seems to be something that should force a system memory
dump.
I think I can handle the code-writing, but since there's no documentation I
have
to find out how things are working.
Ok, the question
> Translators for providing per user private directories and restricting
> visibility of files and directories using the translation filesystem are
> available now at
> http://trfs.sourceforge.net/
> Per user private directories:
> Files created in a per user private directory are not visible to u
> memory area has to be accessed. In some memory management systems,
> the allocated area has to be actually written (demand zero paging).
> If you execute from a user account, not root, with ulimits enabled,
> you should be able to do:
> char *p;
> for(;;)
> {
> if(
> > When running a script (perl in this case) that has DOS-style newlines
> > (\r\n), Linux 2.4.2 can't find an interpreter because it doesn't
> > recognize the \r. The following patch should fix this (untested).
> _should_ it work with the \r in it?
IV> IMHO, yes. This set of files were created
> When running a script (perl in this case) that has DOS-style newlines
> (\r\n), Linux 2.4.2 can't find an interpreter because it doesn't
> recognize the \r. The following patch should fix this (untested).
_should_ it work with the \r in it?
There might be a problem with your patch: at the '*)
> I have already written a 2.2 implementation which does not suffer from
these
> problems.
Yes, someone pointed me at it. To be honest (and with all due respect): I
found
it to be a bit over-complicated. Like; in my opinion it's only usefull to
have
absolute random chosen PIDs, or not. Not all t
Hi,
On http://helllabs.org/~claudio/awebd/awe_ram.c I found some code which
transforms the
RAM on an AWE32/64 into a block-device. I tried to compile it, but I did not
succeed.
The writer of this code doesn't respond to e-mails.
Anyone out there who has a clue what is going wrong with it? (using
>> My code runs trough the whole task_list to see if a chosen pid is already
>> in use or not.
> But it doesn't check for a recently used PID. Lets say your system is
> exhausting 1000 PIDs/second, and that there is a window of 20ms between
you
> determining which PID to send to, and the recip
>> I wrote a patch against 2.2.18 and 2.4.1 to have the kernel generate
>> random PIDs. You can find it at http://vanheusden.com/Linux/security.php3
>> (amongst other patches). Beware: pretty much experimental and likely to
>> make your linux-pc perform like a win95 platform.
> Well - I'm not
Hi,
I wrote a patch against 2.2.18 and 2.4.1 to have the kernel generate random
PIDs.
You can find it at http://vanheusden.com/Linux/security.php3 (amongst other
patches).
Beware: pretty much experimental and likely to make your linux-pc perform
like a
win95 platform.
Greetings,
Folkert van He
> Excellent!
> Got any URLs?
RML> its been in 2.4 for a year or so, although only in the last few tests
as
RML> it supported i815. it has been in 2.2 since 2.2.17 or the current
2.2.18.
2.2.18 I think, or some undetected disk-error must have swept it away from
the local sourcetree :o)
RML> take
> I wrote a daemon that fetches (as root-user) random numbers from the RNG
in
> the i82808 (found on 815-chipsets).
> You can download it from http://www.vanheusden.com/Linux/random.php3 .
> Currently, I'm trying to rewrite things into a kernel-module so that one
has
> a standard character device
> I wrote a daemon that fetches (as root-user) random numbers from the RNG
in
> the i82808 (found on 815-chipsets).
> You can download it from http://www.vanheusden.com/Linux/random.php3 .
> Currently, I'm trying to rewrite things into a kernel-module so that one
has
> a standard character device
Hi,
I wrote a daemon that fetches (as root-user) random numbers from the RNG in
the i82808 (found on 815-chipsets).
You can download it from http://www.vanheusden.com/Linux/random.php3 .
Currently, I'm trying to rewrite things into a kernel-module so that one has
a standard character device which
Forgoto my previous question (threading in kernel); got an other question:
how do I access memory-mapped hardware from userspace?
thank you
-
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
what would be the way of starting a sub-process in a module which then would
run in the background? I guess plain fork() won't work?
-
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/lkm
Is an 2.2.16 system that suddenly out of the blue (always! like; every time
the system is started) uses all memory and all swap-space and then crashes
of any intrest?
Or should I just ignore it and install 2.2.17?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
Hi,
ADC> why not
ADC> #include
ADC> Amit
Since that is not cross-platform. I like a solution which does the #include
transparantly
for alpha/i386/etc.
"Heusden, Folkert van" wrote:
>
> I need to include (in a driver) a header-file from arch//subdir. I
> coul
I need to include (in a driver) a header-file from arch//subdir. I
could, of course,
do something like #include "../../arch/i386/{etc}" with a couple of #ifdef's
to get things
working for each environment. I guess that's now the way to do it cleanly.
What would be _the_ way to do it?
Thanks.
Fol
> Yesterday I tried to install 2.2.17 on a pentium-mmx. Nothing fancy;
3c509,
[snip]
> What should I do as the next problem-determinationstep?
YOU> Check if you didn't accidentally build a Pentium Pro/II kernel
YOU> (see the .config file, or with "make menuconfig" / "make xconfig")
That was o
Hi,
Yesterday I tried to install 2.2.17 on a pentium-mmx. Nothing fancy; 3c509,
3c905B, ide disk+cdrom, 32MB ram.
2.0.38 runs fine.
system crashes (hangs) after it decompressed the kernel, after the "Now
booting the kernel"-message.
I tried both an bzImage and the zImage.
Couldn't find anything
43 matches
Mail list logo
