Re: unexplained high load

2001-01-10 Thread Hacksaw
Could someone maybe explain this ? (top output, but same load is given with 'uptime') there is no cpu or disk activity kernel is 2.2.18pre9 on sun ultra10-300 (ultrasparc IIi) 9:25pm up 112 days, 1:52, 1 user, load average: 1.24, 1.05, 1.02 91 processes: 90 sleeping, 1 running, 0

Re: unexplained high load

2001-01-10 Thread Hacksaw
don't think w,uptime,top give the same value The fact that they all give the same value does not indicate that you have not been cracked. Obviously, part of the hacking is to cover trails; it'd be a pretty poor job if they reported different values. The mm stuff from your other message is, I

Re: unexplained high load

2001-01-10 Thread Hacksaw
Ahh, a D state. D means disk wait, which the only thing that can postpone a -9. Basic, the process is stuck in a loop inside a routine that needs to be atomic. You'll have to reboot to clear it. I believe this is a kernel bug. Try going back to 2.2.14, or maybe up to 2.2.19pre2. - To

Re: unexplained high load

2001-01-10 Thread Hacksaw
.nfs00ca40250006 so i think there is some lock from the nfs server or client will try to restart nfs client and see if this fixes it. Most likely you will have to restart the nfs server on the other side as well, but it's worth a try. Tripwire watches the checksum of the

Re: Not a typewriter

2001-05-10 Thread Hacksaw
I disagree. Not a typewriter is part of Unix tradition, and ought to be retained as a historical reference. It's also an opportunity for the uninitiated to learn a little more and move a little closer to becoming the initiated. Heaven help us when tradition is more important than clarity.

Re: Not a typewriter

2001-05-11 Thread Hacksaw
If clarity is the most important consideration, then other things should be changed as well. For instance, the command we use to search for text strings in files should be called textsearch. That's a lot more clear than grep. Well, I can't disagree. Unix's biggest turn off was the stupid

Re: LANANA: To Pending Device Number Registrants

2001-05-16 Thread Hacksaw
So what is your solution for preventing a boot failure after disks/partitions change ? volume labels/UUID ? As a sys-admin, let me add a vote for this. Having (one day) a prom monitor program that looks at all the disks, and gives a menu of which one to boot from would make life so nice. I

Re: LANANA: To Pending Device Number Registrants

2001-05-16 Thread Hacksaw
This is the problem with all sorts of ID-based naming. In this case the kernel could simply change the conflicting names a bit, and leave the cleanup to the administrator. (Who probably is around as he just inserted those disks) NO, NO, NO, NO, NO. The kernel, when asked to report on the

2.2.17 memory bug?

2000-10-13 Thread Hacksaw
I apologize if this is a known issue. I am running Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 SMP Sun Oct 8 02:37:43 EDT 2000 On a dual Pentium III with 256M of SDRAM, aix-7xxx, sblive, kingston tulip, 3c905, 3dfx Voodoo3 AGP.

Re: Topic for discussion: OS Design

2000-10-23 Thread Hacksaw
Another linux caveat. Scads of undocumented and virtually undiscoverable behaviours :-) Undiscoverable? You have the source code, what more do you want? Start documenting! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: Index of Kernel Configuration Options

2001-03-05 Thread Hacksaw
latest Linux kernel? I am waiting on a kernel mode driver for my USB digital camera, but I don't want to go ahead and download the full 24Mb For USB stuff, try: http://www.linux-usb.org/ I like the idea of the hardware index, though... - To unsubscribe from this list: send the line

Re: someody help me out

2001-05-01 Thread Hacksaw
I am just a beginner in linux programming and I want to write a script for disconnecting users in cisco router. This would be the wrong list to ask such a question. It is for the discussion of the inner workings of the Linux kernel, not for questions about applications which can be run on a

Re: GCC3.0 Produce REALLY slower code!

2001-06-25 Thread Hacksaw
Here is link to Intel C compiler, that provide really faster code. http://developer.intel.com/software/products/compilers/linuxbeta.htm A quote from the site: * Not all of the GNU C language extensions, including the GNU inline assembly format, are currently supported and, due to this, one

Re: GCC3.0 Produce REALLY slower code!

2001-06-25 Thread Hacksaw
Well, I haven't gone and looked at every line of assembler, but I'd bet this is a hasty characterization. According to someones recent count there are around 144000 lines of assembler in the 2.4.2 kernel. It seems to me you'd have to jump through a lot of hoops to test this compiler. Then

Re: GCC3.0 Produce REALLY slower code!

2001-06-26 Thread Hacksaw
Apart from questions of optimization, compiling the same code with two different compilers is a very good way to find bugs, both in the code and in the compilers. I agree that this is a workable idea. On the other hand, I'd bet Linus would put that idea right up there with shipping a debugger

Re: Cosmetic JFFS patch.

2001-06-28 Thread Hacksaw
Given that seeing as much as possible on a potentially small screen would be good, maybe tighter would be nice. In example: kswapd:v1.8 ptyDevices: 256 Unix98 ptys configured serial:v5.05b (2001-05-03) with Options: MANY_PORTS SHARE_IRQ SERIAL_PCI Devices:

Re: Cosmetic JFFS patch.

2001-06-29 Thread Hacksaw
No 'debug=' could then simply cause the kernel to kprint any info from drivers/modules that failed to load, else keep schtum. My idea is that the driver announces itself, and then what it has found/initialized, in the minimum number of screen lines possible. I'd want that to be the default,

Re: [OT] Major Clock Drift

2001-02-04 Thread Hacksaw
Technical explanations aside, some sort of clock drift exists in all computers. My experience with Sun hardware, for instance, was that the hardware and software clocks rarely agreed. You should set up your machines to use some sort of time synchronization software, such as ntp or rdate. When

Re: [OT] Major Clock Drift

2001-02-04 Thread Hacksaw
I've discovered that heavy use of vesafb can be a major source of clock drift on my system, especially if I don't specify "ypan" or "ywrap". On my This is extremely interesting. What version of ntp are you using? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

Re: Disk is cheap?

2001-02-06 Thread Hacksaw
On Sam, 03 Feb 2001 you wrote: Actually, most of that time is spent running bash/sleep 1. Startup scripts tend to be poorly designed. Yes! I'm not so sure. I'm using RedHat 6.2, and it seems the only time a startup script calls sleep is when it gives you a chance to do interactive

Re: To Linus: kdb in 2.4?

2001-02-13 Thread Hacksaw
S! Do not nudge sleeping penguin. Here is blow-by-blow of last incident: http://kt.linuxcare.com/kernel-traffic/kt20001002_87.epl#1 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: Ideas for the oom problem

2001-03-28 Thread Hacksaw
a. don't kill any task with a uid 100 b. if uid between 100 to 500 or CAP-SYS equivalent enabled set it too a lower priority, so if it is at fault it will happen slower giving more time before the system collapses Deciding what not to kill

Re: Ideas for the oom problem

2001-03-28 Thread Hacksaw
--On Wednesday, March 28, 2001 09:38:04 -0500 Hacksaw [EMAIL PROTECTED] wrote: Deciding what not to kill based on who started it seems like a bad idea. Root can start netscape just as easily as any user, but if the choice of processes to kill is root's netscape or a user's

Re: Ideas for the oom problem

2001-03-28 Thread Hacksaw
On Wed, Mar 28, 2001 at 06:33:04PM -0500, Hacksaw wrote: Why are they logged in as root in the first place? Is there something they can't do over sudo? I have the "Gnome workstation" version of rawhide (7.0.xxx) on my new laptop. I don't see sudo. Of course, it's rawhide, but y

Re: linux terminal type

2001-04-04 Thread Hacksaw
Look in section 4 of the man pages for entries starting with "console". console console_codes etc. - 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

Re: Why system call need to copy the date from the userspace before using it

2005-04-13 Thread Hacksaw
Why not use it directly Some of these reasons are: It seems like you gave reason why userland pointers shouldn't be trusted, not why userland data should be copied into kernel land. All the problems you mentioned would have to be solved by the kernel regardless of copying the data around.

Re: Why system call need to copy the date from the userspace before using it

2005-04-15 Thread Hacksaw
Sorry if this bugs anyone, but I'm learning things here. What I would expect the kernel to do is this: system_call_data_prep (userdata, size){ if !4G/4G { for each page from userdata to userdata+size { if the page is swapped out, swap it in if the page is not

Re: Why system call need to copy the date from the userspace before using it

2005-04-16 Thread Hacksaw
if you want actual concrete examples, let me know. I'd love a few, but maybe privately? I can certainly see where always copying is simpler; I certainly consider this to be an optimization, which must be looked at carefully, lest you end up with that which speed things up a little, but adds a

indirect lcall without `*'

2005-03-12 Thread Hacksaw
In compiling 2.4.29 I get this during the compilation of pci-pc.c: Warning: indirect lcall without `*' I note from looking around the net that this is an old problem, dating back at least to 2.4.18, if not earlier. What does it mean? Should I care? If I shouldn't, shouldn't there be a message

Re: indirect lcall without `*'

2005-03-13 Thread Hacksaw
Ahh, okay. I'm just jumpy because this is a production server. Thanks for the answer. :-) -- Nothing can plugh you now http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL

Re: Linux 2.6.11.4

2005-03-15 Thread Hacksaw
+ while (dlen = 2 dlen = data[1] data[1] = 2) { Not that it matters much to me, since I don't have to maintain it, but couldn't this be: while (data[1] = 2 dlen = data[1]) { I think this captures the relationship and priority. -- http://www.hacksaw.org --

Re: LANANA: To Pending Device Number Registrants

2001-05-16 Thread Hacksaw
>So what is your solution for preventing a boot failure after disks/partitions >change ? >volume labels/UUID ? As a sys-admin, let me add a vote for this. Having (one day) a prom monitor program that looks at all the disks, and gives a menu of which one to boot from would make life so nice. I

Re: LANANA: To Pending Device Number Registrants

2001-05-16 Thread Hacksaw
>This is the problem with all sorts of ID-based naming. In this case >the kernel could simply change the conflicting names a bit, >and leave the cleanup to the administrator. (Who probably >is around as he just inserted those disks) NO, NO, NO, NO, NO. The kernel, when asked to report on

Re: unexplained high load

2001-01-10 Thread Hacksaw
> Could someone maybe explain this ? > (top output, but same load is given with 'uptime') > there is no cpu or disk activity > kernel is 2.2.18pre9 on sun ultra10-300 (ultrasparc IIi) > >9:25pm up 112 days, 1:52, 1 user, load average: 1.24, 1.05, 1.02 > 91 processes: 90 sleeping, 1

Re: unexplained high load

2001-01-10 Thread Hacksaw
>don't think >w,uptime,top give the same value The fact that they all give the same value does not indicate that you have not been cracked. Obviously, part of the hacking is to cover trails; it'd be a pretty poor job if they reported different values. The mm stuff from your other message is,

Re: unexplained high load

2001-01-10 Thread Hacksaw
Ahh, a D state. D means disk wait, which the only thing that can postpone a -9. Basic, the process is stuck in a loop inside a routine that needs to be atomic. You'll have to reboot to clear it. I believe this is a kernel bug. Try going back to 2.2.14, or maybe up to 2.2.19pre2. - To

Re: unexplained high load

2001-01-10 Thread Hacksaw
> .nfs00ca40250006 > > so i think there is some lock from the nfs server or client > > will try to restart nfs client > and see if this fixes it. > Most likely you will have to restart the nfs server on the other side as well, but it's worth a try. Tripwire watches the checksum

Re: someody help me out

2001-05-01 Thread Hacksaw
>I am just a beginner in linux programming and I want to write a >script for disconnecting users in cisco router. This would be the wrong list to ask such a question. It is for the discussion of the inner workings of the Linux kernel, not for questions about applications which can be run on a

Re: Not a typewriter

2001-05-10 Thread Hacksaw
>I disagree. "Not a typewriter" is part of Unix tradition, and ought to be >retained as a historical reference. It's also an opportunity for "the >uninitiated" to learn a little more and move a little closer to becoming "the >initiated." Heaven help us when tradition is more important than

Re: Not a typewriter

2001-05-11 Thread Hacksaw
>If clarity is the most important consideration, then other things should be >changed as well. For instance, the command we use to search for text strings in >files should be called "textsearch." That's a lot more clear than "grep." Well, I can't disagree. Unix's biggest turn off was the

Re: Index of Kernel Configuration Options

2001-03-05 Thread Hacksaw
>latest Linux kernel? I am waiting on a kernel mode driver for my USB >digital camera, but I don't want to go ahead and download the full 24Mb For USB stuff, try: http://www.linux-usb.org/ I like the idea of the hardware index, though... - To unsubscribe from this list: send the line

Re: GCC3.0 Produce REALLY slower code!

2001-06-25 Thread Hacksaw
>Here is link to Intel C compiler, that provide really faster code. > >http://developer.intel.com/software/products/compilers/linuxbeta.htm A quote from the site: * Not all of the GNU C language extensions, including the GNU inline assembly format, are currently supported and, due to this, one

Re: GCC3.0 Produce REALLY slower code!

2001-06-25 Thread Hacksaw
Well, I haven't gone and looked at every line of assembler, but I'd bet this is a hasty characterization. According to someones recent count there are around 144000 lines of assembler in the 2.4.2 kernel. It seems to me you'd have to jump through a lot of hoops to test this compiler. Then

Re: GCC3.0 Produce REALLY slower code!

2001-06-26 Thread Hacksaw
>Apart from questions of optimization, compiling the same code with two >different compilers is a very good way to find bugs, both in the code >and in the compilers. I agree that this is a workable idea. On the other hand, I'd bet Linus would put that idea right up there with shipping a

Re: Cosmetic JFFS patch.

2001-06-28 Thread Hacksaw
Given that seeing as much as possible on a potentially small screen would be good, maybe tighter would be nice. In example: kswapd:v1.8 ptyDevices: 256 Unix98 ptys configured serial:v5.05b (2001-05-03) with Options: MANY_PORTS SHARE_IRQ SERIAL_PCI Devices:

Re: Cosmetic JFFS patch.

2001-06-29 Thread Hacksaw
>No 'debug=' could then simply cause the kernel to kprint any info from >drivers/modules that failed to load, else keep schtum. My idea is that the driver announces itself, and then what it has found/initialized, in the minimum number of screen lines possible. I'd want that to be the default,

2.2.17 memory bug?

2000-10-13 Thread Hacksaw
I apologize if this is a known issue. I am running Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 SMP Sun Oct 8 02:37:43 EDT 2000 On a dual Pentium III with 256M of SDRAM, aix-7xxx, sblive, kingston tulip, 3c905, 3dfx Voodoo3 AGP.

Re: Topic for discussion: OS Design

2000-10-23 Thread Hacksaw
> Another linux caveat. Scads of undocumented and virtually undiscoverable > behaviours :-) Undiscoverable? You have the source code, what more do you want? Start documenting! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: [OT] Major Clock Drift

2001-02-04 Thread Hacksaw
Technical explanations aside, some sort of clock drift exists in all computers. My experience with Sun hardware, for instance, was that the hardware and software clocks rarely agreed. You should set up your machines to use some sort of time synchronization software, such as ntp or rdate. When

Re: [OT] Major Clock Drift

2001-02-04 Thread Hacksaw
>I've discovered that heavy use of vesafb can be a major source of clock >drift on my system, especially if I don't specify "ypan" or "ywrap". On my This is extremely interesting. What version of ntp are you using? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: Disk is cheap?

2001-02-06 Thread Hacksaw
> On Sam, 03 Feb 2001 you wrote: > > Actually, most of that time is spent running bash/sleep 1. Startup > > scripts tend to be poorly designed. > > Yes! I'm not so sure. I'm using RedHat 6.2, and it seems the only time a startup script calls sleep is when it gives you a chance to do

Re: To Linus: kdb in 2.4?

2001-02-13 Thread Hacksaw
S! Do not nudge sleeping penguin. Here is blow-by-blow of last incident: http://kt.linuxcare.com/kernel-traffic/kt20001002_87.epl#1 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: Ideas for the oom problem

2001-03-28 Thread Hacksaw
> a. don't kill any task with a uid < 100 > > b. if uid between 100 to 500 or CAP-SYS equivalent enabled > set it too a lower priority, so if it is at fault it will happen slower > > giving more time before the system collapses Deciding what not to

Re: Ideas for the oom problem

2001-03-28 Thread Hacksaw
> --On Wednesday, March 28, 2001 09:38:04 -0500 Hacksaw <[EMAIL PROTECTED]> > wrote: > > > > Deciding what not to kill based on who started it seems like a bad idea. > > Root can start netscape just as easily as any user, but if the choice of > > p

Re: Ideas for the oom problem

2001-03-28 Thread Hacksaw
> On Wed, Mar 28, 2001 at 06:33:04PM -0500, Hacksaw wrote: > Why are they logged in as root in the first place? Is there something they > can't do over sudo? I have the "Gnome workstation" version of rawhide (7.0.xxx) on my new laptop. I don't see sudo. Of course, it's rawhi

Re: "linux" terminal type

2001-04-04 Thread Hacksaw
Look in section 4 of the man pages for entries starting with "console". console console_codes etc. - 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

Re: Why system call need to copy the date from the userspace before using it

2005-04-13 Thread Hacksaw
>>Why not use it directly >Some of these reasons are: It seems like you gave reason why userland pointers shouldn't be trusted, not why userland data should be copied into kernel land. All the problems you mentioned would have to be solved by the kernel regardless of copying the data around.

Re: Why system call need to copy the date from the userspace before using it

2005-04-15 Thread Hacksaw
Sorry if this bugs anyone, but I'm learning things here. What I would expect the kernel to do is this: system_call_data_prep (userdata, size){ if !4G/4G { for each page from userdata to userdata+size { if the page is swapped out, swap it in if the page is not

Re: Why system call need to copy the date from the userspace before using it

2005-04-16 Thread Hacksaw
>if you want actual concrete examples, let me know. I'd love a few, but maybe privately? I can certainly see where always copying is simpler; I certainly consider this to be an optimization, which must be looked at carefully, lest you end up with that which speed things up a little, but adds a

indirect lcall without `*'

2005-03-12 Thread Hacksaw
In compiling 2.4.29 I get this during the compilation of pci-pc.c: Warning: indirect lcall without `*' I note from looking around the net that this is an old "problem", dating back at least to 2.4.18, if not earlier. What does it mean? Should I care? If I shouldn't, shouldn't there be a

Re: indirect lcall without `*'

2005-03-13 Thread Hacksaw
Ahh, okay. I'm just jumpy because this is a production server. Thanks for the answer. :-) -- Nothing can plugh you now http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: Linux 2.6.11.4

2005-03-15 Thread Hacksaw
+ while (dlen >= 2 && dlen >= data[1] && data[1] >= 2) { Not that it matters much to me, since I don't have to maintain it, but couldn't this be: while (data[1] >= 2 && dlen >= data[1]) { I think this captures the relationship and priority. -- http://www.hacksaw.org --