* Notification of Removed Attachment - please read for details
From: SAS Postmaster 62 @ 2004-01-28 3:48 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f,
NotificationRecipient, postmaster62-LVvIjLR0h5w
Please read this notification carefully. Almost certainly, you need *not* contact your Help Desk at this time.
An attachment was removed because it was of a type prohibited by our email policies. If a business need exists to transfer this file type by email, the sender/recipient within SAS should refer to http://sww.sas.com/helpdesk/pc/EmailAttachmentPolicy.htm.
This notification does not necessarily mean that a virus-infected attachment was removed. However, the type of file that was being emailed is one that is, unfortunately, commonly used to transfer viruses. It is our policy to restrict the free flow of this type of attachment via email in order to protect ourselves and our external customers from the damage that can be caused by viruses that are sometimes transported in these files.
++++++++++++++++++++++++++++++++++++++
Sender: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Recipient(s): larry.isaacs-LVvIjLR0h5w@public.gmane.org
Received: Tue Jan 27 22:48:43 2004
Subject of Message:
Attachment file name: document.scr:HEADER
Action on Attachment: STRIP
++++++++++++++++++++++++++++++++++++++
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* Re: RFC: Trailing blanks in source files
From: jw schultz @ 2004-01-28 3:49 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <20040127160214.69850c9c.akpm@osdl.org>
On Tue, Jan 27, 2004 at 04:02:14PM -0800, Andrew Morton wrote:
> "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> >
> > So please don't bother with just whitespace changes unless you
> > are going to cleanup a <driver | fs | module | etc> completely.
>
> And if you're going to do that, do the whitespace cleanup _first_, so the
> substantive changes to the driver/fs/module/etc can be sanely understood
> and reverted if necessary.
>
> I frequently sneakily remove all newly-added trailing whitespace from the
> patches people send me. In 15 years it'll all be gone.
This would maybe warrant a bk option to remove trailing
whitespace from modified lines. Preferably with an
notification that it is happening so if for some reason you
do want trailing whitespace you could abort or override.
A patch filter that removed trailing whitespace from + lines
could also be used.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
^ permalink raw reply
* Re: devfs 199.17 not in 2.4 (was Re:2.4.22 devfs/zlib outstanding updates ...)
From: Frédéric L. W. Meunier @ 2004-01-28 3:52 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <Pine.LNX.4.58.0401280110530.949@pervalidus.dyndns.org>
On Wed, 28 Jan 2004, Frédéric L. W. Meunier wrote:
> Herbert Pötzl wrote on Sat, 12 Jul 2003 00:22:07 +0200
>
> > just wanted to remind/state that the final? v199.17 devfs
> > patch and the 1.1.4 zlib update are not in 2.4.22-pre5.
>
> About the devfs patch.
>
> Yes, I already reported it a long time ago -
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0306.2/1655.html
> and have no idea why it hasn't been merged in 2.4, after all
> it's supposed to fix some things and there have been no changes
> since then in the kernel.
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103474534430016&w=2
>
> Can someone clarify this ? I've been applying this patch since
> its release and it didn't broke anything.
And you can find a patch from Andrey Borzenkov at
http://www.cs.helsinki.fi/linux/linux-kernel/2003-18/1161.html
http://www.cs.helsinki.fi/linux/linux-kernel/2003-25/0100.html
Nobody bothered to review and submit it ?
--
http://www.pervalidus.net/contact.html
^ permalink raw reply
* Re: RFC: Trailing blanks in source files
From: Randy.Dunlap @ 2004-01-28 3:55 UTC (permalink / raw)
To: jw schultz; +Cc: linux-kernel
In-Reply-To: <20040128034939.GE15979@pegasys.ws>
On Tue, 27 Jan 2004 19:49:39 -0800 jw schultz <jw@pegasys.ws> wrote:
| On Tue, Jan 27, 2004 at 04:02:14PM -0800, Andrew Morton wrote:
| > "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| > >
| > > So please don't bother with just whitespace changes unless you
| > > are going to cleanup a <driver | fs | module | etc> completely.
| >
| > And if you're going to do that, do the whitespace cleanup _first_, so the
| > substantive changes to the driver/fs/module/etc can be sanely understood
| > and reverted if necessary.
| >
| > I frequently sneakily remove all newly-added trailing whitespace from the
| > patches people send me. In 15 years it'll all be gone.
|
| This would maybe warrant a bk option to remove trailing
| whitespace from modified lines. Preferably with an
| notification that it is happening so if for some reason you
| do want trailing whitespace you could abort or override.
|
| A patch filter that removed trailing whitespace from + lines
| could also be used.
AFAIK Andrew already uses a script to check for trailing spaces,
and I do also. Yes, it could be modified to be a conversion filter,
but it doesn't happen frequently, and when it does, I want to let
the poster know about it, so I like to have the evidence handy. :)
--
~Randy
^ permalink raw reply
* Passing packet to IP layer
From: suresh k @ 2004-01-28 4:00 UTC (permalink / raw)
To: netfilter
Hi,
I am capturing packets using netfilters. I am modifying the packets and I want to give
it "up the linux IP stack" in the kernel. The implementation has to been done as a
loadable module. I have a problem here, I don't find any kernel exported symbol which
can be used to send the modified stack up the stack and give it to the IP module. Kindly
tell me if there is any way to do that. I thought abt compiling the code which I have
written along with the kernel and use the kernel functions directly, but it is not
portable. Kindly tell me how to proceed.
cheers
Suresh
^ permalink raw reply
* [ALSA - driver 0000007]: alsa-kernel/pci does NOT contain bt87x driver
From: noreply @ 2004-01-28 4:01 UTC (permalink / raw)
To: alsa-devel
The following NEW bug has been ADDED.
======================================================================
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000007
======================================================================
Reporter: yahoo
Handler:
======================================================================
Project: ALSA - driver
Bug ID: 7
Category: OTHERS
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version:
======================================================================
Date Submitted: 01-28-2004 05:01 CET
Last Modified: 01-28-2004 05:01 CET
======================================================================
Summary: alsa-kernel/pci does NOT contain bt87x driver
Description:
alsa-kernel/pci does NOT contain bt87x driver it is however
present in alsa-driver/pci.
======================================================================
Bug History
Date Modified Username Field Change
======================================================================
01-28-04 05:01 yahoo New Bug
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* IP address of the interface
From: suresh k @ 2004-01-28 4:04 UTC (permalink / raw)
To: netfilter
Hi,
I want to get the IP address of the interface in the kernel. I have seen the mail list
archives discussing this. I want to implement the code as a loadable module. I don't
think the suggested in the archives work, as those functions are not exported. Is there
any other way to handle this. Kindly help me out.
regards
Suresh
^ permalink raw reply
* Re: [uml-devel] Mapping con=pts to a port instead of con=port
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: Dan Shearer; +Cc: user-mode-linux-devel
In-Reply-To: <20040124050440.GF4203@erizo.shearer.org>
dan@shearer.org said:
> The same effect can be achieved with termnetd, with the advantage of
> your in.telnetd solution that you aren't building in complexity that
> doesn't belong to UML, but without the clomp-clomp finesse telnetd
> achieves :-)
Yeah, but it has uncleanlinesses of its own (like the need to generate a config
file on the fly), but it's cleaner than what I have now.
My major problem with it is that attaching consoles to ports will stop working
for some number of users if I switch to termnetd, and I'm willing to put up
with some amount of nastiness inside UML if it increases the size of the
userbase that UML works for out of the box.
That concern would be somewhat assuaged if UML were generally installed with
packages that could be made to depend on termpkg, but I think that's not the
case.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [uml-devel] [patch] uml fixes, 2.6.1-mm5-A2
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: nsb034; +Cc: user-mode-linux-devel
In-Reply-To: <20040123061842.GA5292@localhost>
nsb034@lostrealm.com said:
> This fixes the bug "skas mode panic - ltrace strace" that occurs in
> uml-patch-2.4.23-2 and below. Could this patch please be applied to
> the 2.4.x kernels as well?
I did, and it will be in the next patch.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [uml-devel] [Sebastian.Koch@metatool.de: Re: ps u failed with signal 8 (FPE)]
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: Gerd Knorr; +Cc: uml devel
In-Reply-To: <20040122114858.GH11029@bytesex.org>
kraxel@bytesex.org said:
> The problem is that the proc file system of the UML shows a wrong /
> proc/meminfo. Especially the MemTotal:
Nice catch. I was wondering about that SIGFPE crash. Try the patch below.
Jeff
===== arch/um/kernel/mem.c 1.21 vs edited =====
--- 1.21/arch/um/kernel/mem.c Thu Jan 8 07:43:01 2004
+++ edited/arch/um/kernel/mem.c Mon Jan 26 11:02:13 2004
@@ -30,7 +30,6 @@
int kmalloc_ok = 0;
static unsigned long brk_end;
-static unsigned long totalram_pages = 0;
void unmap_physmem(void)
{
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [uml-devel] Swapping directly to host swap area?
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: William Stearns; +Cc: ML-uml-devel
In-Reply-To: <Pine.LNX.4.44.0401251827030.2766-100000@sparrow>
wstearns@pobox.com said:
> When a VM needs to swap out, is there some way the UML kernel could
> send that sector directly to the host swap area instead of running its
> own swap?
No, but this isn't the real question.
> In the current setup, the host kernel sees this as a normal
> write to an open file, caching it in the process and so not truly
> freeing up the ram for a bit.
This is, and this could be done by setting O_DIRECT on UML swap devices. That
way, writes go directly (and asynchronously) to the device without landing
in the cache.
With mmap in effect, this can also be done with a MADVISE_DONTNEED on the
relevant pages of the swap file.
Patches cheerfully accepted.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [uml-devel] PATCH check for sys_sendfile() in port_user.c
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: Dan Shearer; +Cc: user-mode-linux-devel
In-Reply-To: <20040127045014.GZ4203@erizo.shearer.org>
> Some kernels (including SuSE 2.4.20, according to http://
> marc.theaimsgroup.com/?l=user-mode-linux-user&m=107437381718023&w=2)
> don't have sys_sendfile, in which case the port console driver should
> refuse to start up because there is no way for telnetd to get the fd.
sendfile has nothing to do with passing descriptors across unix sockets.
It is a relatively new performance tweak which allows files to be copied
without the data flowing through userspace.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [uml-devel] Re: [PATCH] mconsole fixes
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: Dan Shearer; +Cc: user-mode-linux-devel
In-Reply-To: <20040128021652.GP4203@erizo.shearer.org>
dan@shearer.org said:
> My idea was that there's a difference between an error on a connection
> and no connection at all. Having no connection at all can happen very
> easily, especially if you happen to use uml_dir on the cmdline which
> triggers a bug that puts the file in the wrong place.
OK, that being the case, it's better to complain before sending anything to
UML rather than after you've tried and failed.
> Minor portability potential. See http://www.eskimo.com/~scs/C-faq/
> q11.16.html. (I looked it up once long ago and supposedly _exit is
> more likely to work on more systems than exit.)
You talked me into it. I fixed that.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [uml-devel] Kernel idles in loop after loading IPv4
From: Jeff Dike @ 2004-01-28 4:39 UTC (permalink / raw)
To: Steven James; +Cc: Phil Nadeau, user-mode-linux-devel
In-Reply-To: <Pine.LNX.4.58.0401272326020.25787@ucontrol.mobiledns.com>
pyro@linuxlabs.com said:
> I ran into that as well, but didn't have time to do much about it. As
> a further datapoint, if I disable all net support and pass it init=/
> bin/bash, I get the bash prompt (ubd filesystems do get checked/
> mounted) but then it goes into the idle loop and stays there.
Hmmm.
If you could get a stack trace from the last call to schedule, that would be
handy. You could automate it with
comm <n>
bt
c
end
with breakpoint <n> attached to schedule().
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* PROBLEM: CPU lockup during halt for Shuttle SB61G2 p4 with hyperthreading 2.4.24
From: Tom Epperly @ 2004-01-28 4:26 UTC (permalink / raw)
To: linux-smp
[1.] CPU lockup during halt for Shuttle SB61G2 p4 with hyperthreading
[2.] Full description
I've got a Shuttle SB61G2 purchased 12/31/03 with a 2.6GHz P4 with
hyperthreading. Sometimes when shutting down, I get the "Power down."
message, but it doesn't actually power down the system. It just sits
there indefinitely. I tried enabling nmi_watchdog=1, and I
intermittently get kernel oopses. I only started having problems when I
compiled the kernel with SMP enabled. A non-SMP kernel never locks up.
I transcribed the oops message from my screen and ran ksymoops on it. I
am running a vanilla 2.4.24 downloaded from kernel.org compiled with
gcc-2.95.
Please Cc me on replies as I am not subscribed to linux-smp.
[3.] Keywords: Lockup SMP
[4.] Linux version 2.4.24-vanilla (root@faerun) (gcc version 2.95.4
20011002 (Debian prerelease)) #3 SMP Fri Jan 16 07:30:34 PST 2004
[5.]
I had to write this on paper and then type it in by hand. I was very
careful, but transcription errors are always a possibility:
ksymoops 2.4.9 on i686 2.4.24-vanilla. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.24-vanilla/ (default)
-m /boot/System.map-2.4.24-vanilla (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (regular_file): read_system_map stat
/boot/System.map-2.4.24-vanilla failed
ksymoops: No such file or directory
Warning (compare_maps): mismatch on symbol _nv000173rm , nvidia says
f8e4bb20, /lib/modules/2.4.24-vanilla/kernel/drivers/video/nvidia.o says
f8e4b900. Ignoring
/lib/modules/2.4.24-vanilla/kernel/drivers/video/nvidia.o entry
NMI Watchdog detected LOCKUP on CPU1, eip c01a6757, registers:
EIP: 0010: [<c01a6757>] Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00000046
eax: 00000011 ebx: f7cc9e48 ecx: f7cc9e48 edx: 00000400
esi: 00000010 edi: 00000000 ebp: bffffbc8 esp: f7cc9e08
ds: 0018 es: 0018 ss: 0018
Process halt (pid: 1220, stackpage=f7cc9000)
Stack: 00000018 c01b29cb 00000400 f7cc9e48 00000010 00002001 c02e5e18
00000011
c02e5e18 c01b26d7 00000010 f7cc9e48 c1c32114 00002001 00000000
00000000
00000000 c01b24b9 00000000 00000001 f7cc9e68 00002001 c02e5e40
c02e5e40
Call Trace: [<c01b29cb>] [<c01b26d7>] [<c01b24b9>] [<c01b2d5e>]
[<c01c1394>]
[<c0105523>] [<c012487d>] [<c0122d8a>] [<c0122e11>] [<c01231067>]
[<c01239a5>]
[<c0141864>] [<c014954d>] [<c0106f27>]
Code: 66 89 01 eb 11 eb 11 8d 74 26 00 ed 89 01 eb 08 0f 0b 4f 01 ec ff
>>EIP; c01a6757 <acpi_os_stall_R__ver_acpi_os_stall+67/17c> <=====
>>ebx; f7cc9e48 <_end+3794bfe4/385cf1fc>
>>ecx; f7cc9e48 <_end+3794bfe4/385cf1fc>
>>esp; f7cc9e08 <_end+3794bfa4/385cf1fc>
Trace; c01b29cb <acpi_set_register_R__ver_acpi_set_register+4db/6cc>
Trace; c01b26d7 <acpi_set_register_R__ver_acpi_set_register+1e7/6cc>
Trace; c01b24b9 <acpi_get_register_R__ver_acpi_get_register+51/88>
Trace; c01b2d5e
<acpi_enter_sleep_state_R__ver_acpi_enter_sleep_state+1a2/1bc>
Trace; c01c1394
<acpi_pci_irq_enable_R__ver_acpi_pci_irq_enable+bb4/2868>
Trace; c0105523 <machine_power_off+b/314>
Trace; c012487d <unregister_reboot_notifier+365/11a4>
Trace; c0122d8a <dequeue_signal+432/438>
Trace; c0122e11 <send_sig_info+81/98>
Trace; c01231067 <END_OF_CODE+b083c2710/????>
Trace; c01239a5 <notify_parent+685/edc>
Trace; c0141864 <blkdev_put+148/154>
Trace; c014954d <kill_fasync+4f5/528>
Trace; c0106f27 <__read_lock_failed+115f/1520>
Code; c01a6757 <acpi_os_stall_R__ver_acpi_os_stall+67/17c>
00000000 <_EIP>:
Code; c01a6757 <acpi_os_stall_R__ver_acpi_os_stall+67/17c> <=====
0: 66 89 01 mov %ax,(%ecx) <=====
Code; c01a675a <acpi_os_stall_R__ver_acpi_os_stall+6a/17c>
3: eb 11 jmp 16 <_EIP+0x16>
Code; c01a675c <acpi_os_stall_R__ver_acpi_os_stall+6c/17c>
5: eb 11 jmp 18 <_EIP+0x18>
Code; c01a675e <acpi_os_stall_R__ver_acpi_os_stall+6e/17c>
7: 8d 74 26 00 lea 0x0(%esi,1),%esi
Code; c01a6762 <acpi_os_stall_R__ver_acpi_os_stall+72/17c>
b: ed in (%dx),%eax
Code; c01a6763 <acpi_os_stall_R__ver_acpi_os_stall+73/17c>
c: 89 01 mov %eax,(%ecx)
Code; c01a6765 <acpi_os_stall_R__ver_acpi_os_stall+75/17c>
e: eb 08 jmp 18 <_EIP+0x18>
Code; c01a6767 <acpi_os_stall_R__ver_acpi_os_stall+77/17c>
10: 0f 0b ud2a
Code; c01a6769 <acpi_os_stall_R__ver_acpi_os_stall+79/17c>
12: 4f dec %edi
Code; c01a676a <acpi_os_stall_R__ver_acpi_os_stall+7a/17c>
13: 01 ec add %ebp,%esp
Code; c01a676c <acpi_os_stall_R__ver_acpi_os_stall+7c/17c>
15: ff 00 incl (%eax)
2 warnings and 1 error issued. Results may not be reliable.
[6.]
I booted my machine. gdm (X11) fires up using nVidia drivers. Choose
shutdown from gdm menu. Oops. It happens every once in a while when I
shutdown.
[7.]
[7.1]
faerun:/usr/src/linux-2.4.24# sh scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux faerun 2.4.24-vanilla #3 SMP Fri Jan 16 07:30:34 PST 2004 i686
GNU/Linux
Gnu C 3.3.3
Gnu make 3.80
util-linux 2.12
mount 2.12
modutils 2.4.26
e2fsprogs 1.35-WIP
PPP 2.4.2
Linux C Library 2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.1.15
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.0.91
Modules Loaded nvidia joydev mousedev hid input binfmt_misc uhci
ide-scsi scsi_mod it87 i2c-proc i2c-isa i2c-core v_midi sound i810_audio
ehci-hcd
I used "make CC=gcc-2.95 HOSTCC=gcc-2.95" when compiling the kernel and
its modules.
faerun:/usr/src/linux-2.4.24#
[7.2.]
faerun:/usr/src/linux-2.4.24# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.60GHz
stepping : 9
cpu MHz : 2605.987
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips : 5203.55
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.60GHz
stepping : 9
cpu MHz : 2605.987
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips : 5203.55
Intel 865G chipset
faerun:/usr/src/linux-2.4.24#
[7.3.]
faerun:/usr/src/linux-2.4.24# cat /proc/modules
nvidia 1969376 14 (autoclean)
joydev 7104 0 (unused)
mousedev 3864 1
hid 13864 0 (unused)
input 3456 0 [joydev mousedev hid]
binfmt_misc 5896 1
uhci 24752 0 (unused)
ide-scsi 8976 0
scsi_mod 87496 1 [ide-scsi]
it87 9768 0 (unused)
i2c-proc 5972 0 [it87]
i2c-isa 788 0 (unused)
i2c-core 14788 0 [it87 i2c-proc i2c-isa]
v_midi 4996 0 (unused)
sound 56428 0 [v_midi]
i810_audio 24312 1
ehci-hcd 15880 0 (unused)
faerun:/usr/src/linux-2.4.24#
[7.4.]
faerun:/usr/src/linux-2.4.24# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0290-0297 : it87
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0500-051f : Intel Corp. 82801EB SMBus Controller
0cf8-0cff : PCI conf1
9000-90ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
9000-90ff : 8139too
9400-947f : VIA Technologies, Inc. IEEE 1394 Host Controller
a000-a01f : Intel Corp. 82801EB USB
a000-a01f : usb-uhci
a400-a41f : Intel Corp. 82801EB USB
a400-a41f : usb-uhci
a800-a81f : Intel Corp. 82801EB USB
a800-a81f : usb-uhci
ac00-ac1f : Intel Corp. 82801EB USB
ac00-ac1f : usb-uhci
b400-b4ff : Intel Corp. 82801EB AC'97 Audio Controller
b400-b4ff : Intel ICH5
b800-b83f : Intel Corp. 82801EB AC'97 Audio Controller
b800-b83f : Intel ICH5
f000-f00f : Intel Corp. 82801EB Ultra ATA Storage Controller
f000-f007 : ide0
f008-f00f : ide1
faerun:/usr/src/linux-2.4.24# cat /proc/iomem
00000000-0009f7ff : System RAM
0009f800-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-3ffeffff : System RAM
00100000-00281001 : Kernel code
00281002-0031e83f : Kernel data
3fff0000-3fff2fff : ACPI Non-volatile Storage
3fff3000-3fffffff : ACPI Tables
40000000-400003ff : Intel Corp. 82801EB Ultra ATA Storage Controller
e8000000-efffffff : PCI Bus #01
e8000000-efffffff : PCI device 10de:0322 (nVidia Corporation)
f0000000-f3ffffff : Intel Corp. 82865G/PE/P Processor to I/O Controller
f4000000-f5ffffff : PCI Bus #01
f4000000-f4ffffff : PCI device 10de:0322 (nVidia Corporation)
f7000000-f70000ff : Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+
f7000000-f70000ff : 8139too
f7001000-f70017ff : VIA Technologies, Inc. IEEE 1394 Host Controller
f8000000-f80003ff : Intel Corp. 82801EB USB2
f8000000-f80003ff : ehci_hcd
f8001000-f80011ff : Intel Corp. 82801EB AC'97 Audio Controller
f8001000-f80011ff : ich_audio MMBAR
f8002000-f80020ff : Intel Corp. 82801EB AC'97 Audio Controller
f8002000-f80020ff : ich_audio MBBAR
fec00000-ffffffff : reserved
faerun:/usr/src/linux-2.4.24#
[7.5.]
faerun:/usr/src/linux-2.4.24# lspci -vvv
00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller
(rev 02)
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [e4] #09 [0106]
Capabilities: [a0] AGP version 3.0
Status: RQ=32 Iso- ArqSz=2 Cal=2 SBA+ ITACoh- GART64-
HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=2 SBA+ AGP+ GART64- 64bit- FW-
Rate=x8
00:01.0 PCI bridge: Intel Corp. 82865G/PE/P Processor to AGP Controller
(rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f4000000-f5ffffff
Prefetchable memory behind bridge: e8000000-efffffff
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00
[UHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 4: I/O ports at ac00 [size=32]
00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00
[UHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 4: I/O ports at a000 [size=32]
00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00
[UHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 4: I/O ports at a400 [size=32]
00:1d.3 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00
[UHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 4: I/O ports at a800 [size=32]
00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02) (prog-if 20
[EHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin D routed to IRQ 23
Region 0: Memory at f8000000 (32-bit, non-prefetchable)
[size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 00009000-00009fff
Memory behind bridge: f6000000-f7ffffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev
02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller
(rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at <unassigned>
Region 1: I/O ports at <unassigned>
Region 2: I/O ports at <unassigned>
Region 3: I/O ports at <unassigned>
Region 4: I/O ports at f000 [size=16]
Region 5: Memory at 40000000 (32-bit, non-prefetchable)
[size=1K]
00:1f.3 SMBus: Intel Corp. 82801EB SMBus Controller (rev 02)
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device fb61
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 17
Region 4: I/O ports at 0500 [size=32]
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio
Controller (rev 02)
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown
device c09d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at b400 [size=256]
Region 1: I/O ports at b800 [size=64]
Region 2: Memory at f8001000 (32-bit, non-prefetchable)
[size=512]
Region 3: Memory at f8002000 (32-bit, non-prefetchable)
[size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX
5200] (rev a1) (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f4000000 (32-bit, non-prefetchable)
[size=16M]
Region 1: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 3.0
Status: RQ=32 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64-
HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=32 ArqSz=2 Cal=0 SBA+ AGP+ GART64- 64bit-
FW- Rate=x8
02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at 9000 [size=256]
Region 1: Memory at f7000000 (32-bit, non-prefetchable)
[size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
02:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. IEEE 1394 Host Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (8000ns max), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at f7001000 (32-bit, non-prefetchable)
[size=2K]
Region 1: I/O ports at 9400 [size=128]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA
PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
faerun:/usr/src/linux-2.4.24#
[7.6.]
faerun:/usr/src/linux-2.4.24# cat /proc/scsi/scsi
Attached devices: none
[7.7.]
faerun:/usr/src/linux-2.4.24# cat /proc/acpi/info
version: 20031002
states: S0 S1 S4 S5
faerun:/usr/src/linux-2.4.24# cat /proc/acpi/alarm
2004-01-27 11:00:10
--
Tom Epperly <tomepperly@comcast.net>
^ permalink raw reply
* Re: subject-prefixing of ml postings (was Re: A humble request)
From: Kiran Kumar @ 2004-01-28 4:33 UTC (permalink / raw)
To: Harald Welte, Zeeshan Ali; +Cc: netfilter-devel
In-Reply-To: <20040127105451.GF11761@sunbeam.de.gnumonks.org>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
--- Harald Welte <laforge@netfilter.org> wrote:
> P.P.S.: Would anybody be willing to make a
> docbook-website XML document
> for our new homepage about 'how to use the
> netfilter/iptables
> mailinglists' with content like the above one? That
> would be really
> appreciated.
I have built up some content based on the rules of
another list that I am on (most of which are, I guess,
relevant here as well). The patch for the homepage
module of cvs is attached.
=====
Regards,
Kiran Kumar Immidi
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
[-- Attachment #2: contact.patch --]
[-- Type: application/octet-stream, Size: 4450 bytes --]
diff -urN homepage/xml/contact.xml homepage.new/xml/contact.xml
--- homepage/xml/contact.xml 2004-01-17 18:59:07.000000000 +0530
+++ homepage.new/xml/contact.xml 2004-01-28 09:58:18.266406080 +0530
@@ -25,6 +25,52 @@
you will minimize the burden on the project members, and thus minimize the potential delay until you will receive a reply to your inquiry.
</para>
+<section id="list-rules">
+<title>Netfilter list rules</title>
+<para>
+You are strongly advised to go through these set of rules before posting to any
+of the netfilter lists.
+</para>
+<itemizedlist mark="bullet">
+
+<title>List Rules</title>
+
+<listitem>
+Subject Line <para>Make sure that your post contains a valid subject line containing a gist of your post rather than things like 'Help!!!' or even bad 'HELP ME PLEEEEEASE' </para>
+</listitem>
+
+<listitem>
+Top-posts <para>Do not "top-post" (reply to a message by adding text to the top of the message instead of below), as it loses the reader and the flow of the message and can annoy other readers. </para>
+</listitem>
+
+<listitem>
+Overquoting <para>If you are replying to another message, quote only the portions of that message that you are specifically responding to, and insert your comments after those quotes. Do not simply quote back the entire message! Trim off everything apart from the 2-3 most relevant lines of the original message.</para>
+
+<para>In general, your reply should contain at least as much text as the amount of text you are quoting, if not more. Never quote back dozens of lines of text and simply add a single line of text to the bottom - people will *hate* you for that!</para>
+</listitem>
+
+<listitem>
+HTML Messages <para>HTML is not email, and email doesn't contain HTML, so please turn HTML formatting OFF in your email client. Do not use italics, colors, bold, fonts, pictures, sounds, or other HTML elements. Providing HREF (link) elements is allowed. Please use only 7-bit text when sending email to the lists.</para>
+</listitem>
+
+<listitem>
+Message recycling <para>Do not start a New message or thread by hitting "Reply" in your mail client and changing the subject. When you do this, you mess up other participant's ability to read mail in a threaded fashion. When you mean to post a new message, use New, and when you want to reply to an existing message, hit Reply. </para>
+</listitem>
+
+<listitem>
+Pseudo-legal disclaimers <para>Do not attach obnoxious pseudo-legal, nonsensical disclaimers to your messages. People on open source lists do not like to be threatened with these. If your company insists on attaching such disclaimers to messages going out to mailing lists (where, by definition, the sender has *NO* control over who gets to see the message), then either use a webmail system, or just don't post.</para>
+</listitem>
+
+<listitem>
+Off-topic <para>Stay on-topic for the list. This isn't a good place to discuss automobiles, politics, music, or anything that is not related to Netfilter. Sometimes topics will diverge from the general discussion, but please try to keep it relevant to the list topic. Do not ask usage questions in the devel list, or vice versa</para>
+</listitem>
+
+<listitem>
+Message time and date <para>Please make sure the date and time on your computer is always current. When your date is set to something such as the year 2006, messages posted by you will get sorted based on that date, which may put them outside of the related month or year they belong in.</para>
+</listitem>
+
+</itemizedlist>
+
<section id="ml-announce">
<title>The netfilter-announce mailinglist</title>
<para>
diff -urN homepage/xml/layout.xml homepage.new/xml/layout.xml
--- homepage/xml/layout.xml 2004-01-10 03:41:52.000000000 +0530
+++ homepage.new/xml/layout.xml 2004-01-28 09:57:09.691831000 +0530
@@ -111,6 +111,10 @@
<tocentry page="security/2003-08-01-nat-sack.xml" filename="2003-08-01-nat-sack.html"/>
</tocentry>
<tocentry page="contact.xml" filename="contact.html">
+ <tocentry id="list-rules" href="/contact.html#list-rules">
+ <title>The netfilter mailinglist rules</title>
+ <titleabbrev>List Rules</titleabbrev>
+ </tocentry>
<tocentry id="toc-contact-ml-announce" href="/contact.html#ml-announce">
<title>The netfilter announce mailinglist</title>
<titleabbrev>netfilter-announce list</titleabbrev>
^ permalink raw reply
* [linux-lvm] RE:LVM Snapshots for remote archiving.
From: C R Ritson @ 2004-01-28 4:35 UTC (permalink / raw)
To: linux-lvm
>I want to use 24-hour snap shots as an archival tool.
>I have 2 identical file servers, one primary and one as an off-site=20
>mirror. I'd like the primary system to generate a transaction
>log that=20
>rolls over every 24-hours and gets transmitted to the remote site.
I do something similar but with tapes, not a second server. Every
evening, about 15 minutes before the backups, I delete an old snapshot
and create a new one. As this snapshot is mounted and exported via NFS I
have to undo this first (which has caused slight problems,
occasionally). I then backup the newly created snapshot to tape using
amanda. Using the snapshot ensures that amanda and dump (even though
working at the block level) is guaranteed not to see a changing
filesystem, and the snapshot remains available for most of the next 24
hours for a user-initiated recovery of yesterday's version of a file.
Any longer than that, and we have to go to the tapes, but amanda's
indexing makes it quite easy to step back in time and see the filenames
that were previously on disk (though not change dates). Such as it is, I
can make the snapshot script available.
Chris Ritson (Computing Officer)
Rm 618, Claremont Bridge, EMAIL: C.R.Ritson@newcastle.ac.uk
School of Computing Science, PHONE: +44 191 222 8175
University of Newcastle, FAX : +44 191 222 8232
Newcastle on Tyne, UK NE1 7RU. http://www.cs.ncl.ac.uk/~c.r.ritson/
^ permalink raw reply
* Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
From: Dmitry Torokhov @ 2004-01-28 4:37 UTC (permalink / raw)
To: Andrew Morton, Alessandro Suardi; +Cc: linux-kernel, linux-acpi
In-Reply-To: <20040127184228.3a0b8a86.akpm@osdl.org>
On Tuesday 27 January 2004 09:42 pm, Andrew Morton wrote:
> Alessandro Suardi <alessandro.suardi@oracle.com> wrote:
> > Already reported, but I'll do so once again, since it looks like
> > in a short while I won't be able to boot official kernels in my
> > current config...
> >
> > Original report here:
> >
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0312.3/0442.html
>
> Divide by zero. Looks like ACPI is now passing bad values into the
> frequency change notifier.
It is a common problem with Dell's DSDT implementation which does not
follow ACPI spec and it's been going on for ages. From the original
report:
cpufreq: CPU0 - ACPI performance management activated
cpufreq: *P0: 1Mhz, 0 mW, 0 uS
cpufreq: P1: 0Mhz, 0 mW, 0 uS
divide error: 0000 [#1]
As you can see all data is bogus... Patching DSDT cures it for sure,
sometimes CONFIG_ACPI_RELAXED_AML helps as well.
I suppose ACPI P-states driver could check frequencies/latencies and
refuse to activate if the are bogus.
--
Dmitry
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Paul Mackerras @ 2004-01-28 4:44 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Hironobu Ishii, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401271847440.10794@home.osdl.org>
Linus Torvalds writes:
> Does anybody see any downsides to something like this?
Looks OK to me.
On pSeries (ppc64) machines, we don't get an asynchronous machine
check, but instead the read will return all 1s, and the system will
isolate the slot and arrange that all further reads return all 1s.
If you get all 1s back on a read, you are supposed to do a firmware
call to find out if there was actually an error.
With your design, I would make readX_check set a bit somewhere
(associated with the dev argument) if it saw all 1s, and then make
read_pcix_errors do the firmware call if the bit is set.
The only thing to be careful of is that drivers cope correctly with an
all-1s value returned. E.g. they shouldn't do:
while (readb_check(dev, offset) & BUSY)
udelay(1);
But of course they shouldn't do that anyway. :)
Paul.
^ permalink raw reply
* Re: virus warning
From: Nilesh @ 2004-01-28 4:46 UTC (permalink / raw)
To: Alexis; +Cc: netfilter
In-Reply-To: <002901c3e4d7$fb73fcd0$0200000a@heretic>
How do u add rule in iptable firewall for this
in my mail server there are two cards
eth0 for internet and eth1 for lan
please let me know ASAP
thanks
--- Alexis <alexis@attla.net.ar> wrote:
> In this case, we are protected !!!!!
>
> We are all using a firewall with netfilter and input
> policy drop
>
> :))))
>
>
>
> ----- Original Message -----
> From: "Fritz Mesedilla"
> <fritz.mesedilla@overturemedia.com>
> To: "Netfilter Mailing List (E-mail)"
> <netfilter@lists.netfilter.org>
> Sent: Tuesday, January 27, 2004 4:30 AM
> Subject: RE: virus warning
>
>
>
> I forgot to send the details.
>
>
> W32.Novarg.A@mm is a mass-mailing worm. The worm
> will arrive as an
> attachment with a file extension of .bat, .cmd,
> .exe, .pif, .scr, or .zip.
>
> When the machine gets infected, the worm will set up
> a backdoor into the
> system by opening TCP ports 3127 thru 3198. This
> will potentially allow a
> hacker to connect to the machine and utilize it as a
> proxy to gain access to
> it's network resources. In addition, the backdoor
> has the ability to
> download and execute arbitrary files.
>
> The worm will perform a DoS starting on February 1,
> 2004. On February 12,
> 2004 the worm has a trigger date to stop spreading.
>
>
>
http://securityresponse.symantec.com/avcenter/venc/data/w32.novarg.a@mm.html
>
>
>
> Cheers,
>
> fritz <www.mesedilla.com>
> ---
> + Basta Ikaw Lord
>
>
>
>
> -----Original Message-----
> From:
> Sent: Tuesday, January 27, 2004 2:45 PM
> To: Netfilter Mailing List (E-mail)
> Subject: Re: virus warning
>
>
>
> Obviously this is a really new one ... F-prot didn't
> catch it .. and mines
> up to date ...
> However ... since kmail and linux don't much like 7
> bit mime ... *grin*
>
> I'm handing this one up to the folks at F-Prot to
> see why they didn't catch
> it...
>
>
> Alistair.
>
> On January 27, 2004 12:44 am, Fritz Mesedilla wrote:
> > friends,
> >
> > we got a virus in our list.
> > clamav warned me about it.
> > it's now spreading like fire even on other lists.
> >
> > thought you might like to be warned.
> >
> >
> > Cheers,
> >
> > fritz <www.mesedilla.com>
> > ---
> > + Basta Ikaw Lord
> >
> >
> >
> >
> >
>
----------------------------------------------------------------------
> > This email and any files transmitted with it are
> confidential and
> > intended solely for the use of the individual or
> entity to whom they
> > are addressed. If you have received this email in
> error please notify
> > the sender immediately by e-mail and delete this
> e-mail from your
> > system. Please note that any views or opinions
> presented in this
> > email are solely those of the author and do not
> necessarily represent
> > those of the company. Finally, the recipient
> should check this email
> > and any attachments for the presence of viruses.
> The company accepts
> > no liability for any damage caused by any virus
> transmitted by this
> > email.
> >
> > Overture Media, Inc.
> > Direct Line: (632) 635-4785
> > Trunkline: (632) 631-8971 Local 146
> > Fax: (632) 637-2206
> > Level 1 Summit Media Offices, Robinsons Galleria
> EDSA Cor. Ortigas Ave.,
> > Quezon City 1100
>
>
>
----------------------------------------------------------------------
> This email and any files transmitted with it are
> confidential and
> intended solely for the use of the individual or
> entity to whom they
> are addressed. If you have received this email in
> error please notify
> the sender immediately by e-mail and delete this
> e-mail from your
> system. Please note that any views or opinions
> presented in this
> email are solely those of the author and do not
> necessarily represent
> those of the company. Finally, the recipient should
> check this email
> and any attachments for the presence of viruses. The
> company accepts
> no liability for any damage caused by any virus
> transmitted by this
> email.
>
> Overture Media, Inc.
> Direct Line: (632) 635-4785
> Trunkline: (632) 631-8971 Local 146
> Fax: (632) 637-2206
> Level 1 Summit Media Offices, Robinsons Galleria
> EDSA Cor. Ortigas Ave.,
> Quezon City 1100
>
>
>
>
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Paul Mackerras @ 2004-01-28 4:44 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Hironobu Ishii, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401271847440.10794@home.osdl.org>
Linus Torvalds writes:
> Does anybody see any downsides to something like this?
Looks OK to me.
On pSeries (ppc64) machines, we don't get an asynchronous machine
check, but instead the read will return all 1s, and the system will
isolate the slot and arrange that all further reads return all 1s.
If you get all 1s back on a read, you are supposed to do a firmware
call to find out if there was actually an error.
With your design, I would make readX_check set a bit somewhere
(associated with the dev argument) if it saw all 1s, and then make
read_pcix_errors do the firmware call if the bit is set.
The only thing to be careful of is that drivers cope correctly with an
all-1s value returned. E.g. they shouldn't do:
while (readb_check(dev, offset) & BUSY)
udelay(1);
But of course they shouldn't do that anyway. :)
Paul.
^ permalink raw reply
* Re: RFC: Trailing blanks in source files
From: Pragnesh Sampat @ 2004-01-28 4:53 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: jw schultz, linux-kernel, rv
In-Reply-To: <20040127195558.342dba6c.rddunlap@osdl.org>
> | > I frequently sneakily remove all newly-added trailing whitespace from the
> | > patches people send me. In 15 years it'll all be gone.
> |
> | This would maybe warrant a bk option to remove trailing
> | whitespace from modified lines. Preferably with an
> | notification that it is happening so if for some reason you
> | do want trailing whitespace you could abort or override.
> |
> | A patch filter that removed trailing whitespace from + lines
> | could also be used.
>
> AFAIK Andrew already uses a script to check for trailing spaces,
> and I do also. Yes, it could be modified to be a conversion filter,
> but it doesn't happen frequently, and when it does, I want to let
> the poster know about it, so I like to have the evidence handy. :)
Recent versions of emacs, for those that use it, have whitespace.el (for
cleaning up as you go along). It can cleanup different kinds of
whitespace based on settings. Check C-h f whitespace-describe for more
details. Got used to that heavily at one point, these days I am kind of
neutral, sometimes I do it, sometimes I don't bother.
-Pragnesh
^ permalink raw reply
* Re: subject-prefixing of ml postings (was Re: A humble request)
From: Kiran Kumar @ 2004-01-28 4:54 UTC (permalink / raw)
To: Harald Welte, Zeeshan Ali; +Cc: netfilter-devel
In-Reply-To: <20040128043326.45988.qmail@web14003.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
--- Kiran Kumar <immidi_kiran@yahoo.com> wrote:
> I have built up some content based on the rules of
> another list that I am on (most of which are, I
> guess,
> relevant here as well). The patch for the homepage
> module of cvs is attached.
Sorry, seems the previous one had a problem..
resending it.
=====
Regards,
Kiran Kumar Immidi
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
[-- Attachment #2: contact.patch --]
[-- Type: application/octet-stream, Size: 4366 bytes --]
diff -urN homepage/xml/contact.xml homepage.new/xml/contact.xml
--- homepage/xml/contact.xml 2004-01-17 18:59:07.000000000 +0530
+++ homepage.new/xml/contact.xml 2004-01-28 10:18:32.526810440 +0530
@@ -25,6 +25,54 @@
you will minimize the burden on the project members, and thus minimize the potential delay until you will receive a reply to your inquiry.
</para>
+<section id="list-rules">
+<title>Netfilter list rules</title>
+<para>
+You are strongly advised to go through these set of rules before posting to any
+of the netfilter lists.
+</para>
+<itemizedlist mark="bullet">
+
+<title>List Rules</title>
+
+<listitem>
+Subject Line <para>Make sure that your post contains a valid subject line containing a gist of your post rather than things like 'Help!!!' or even bad 'HELP ME PLEEEEEASE' </para>
+</listitem>
+
+<listitem>
+Top-posts <para>Do not "top-post" (reply to a message by adding text to the top of the message instead of below), as it loses the reader and the flow of the message and can annoy other readers. </para>
+</listitem>
+
+<listitem>
+Overquoting <para>If you are replying to another message, quote only the portions of that message that you are specifically responding to, and insert your comments after those quotes. Do not simply quote back the entire message! Trim off everything apart from the 2-3 most relevant lines of the original message.</para>
+
+<para>In general, your reply should contain at least as much text as the amount of text you are quoting, if not more. Never quote back dozens of lines of text and simply add a single line of text to the bottom - people will *hate* you for that!</para>
+</listitem>
+
+<listitem>
+HTML Messages <para>HTML is not email, and email doesn't contain HTML, so please turn HTML formatting OFF in your email client. Do not use italics, colors, bold, fonts, pictures, sounds, or other HTML elements. Providing HREF (link) elements is allowed. Please use only 7-bit text when sending email to the lists.</para>
+</listitem>
+
+<listitem>
+Message recycling <para>Do not start a New message or thread by hitting "Reply" in your mail client and changing the subject. When you do this, you mess up other participant's ability to read mail in a threaded fashion. When you mean to post a new message, use New, and when you want to reply to an existing message, hit Reply. </para>
+</listitem>
+
+<listitem>
+Pseudo-legal disclaimers <para>Do not attach obnoxious pseudo-legal, nonsensical disclaimers to your messages. People on open source lists do not like to be threatened with these. If your company insists on attaching such disclaimers to messages going out to mailing lists (where, by definition, the sender has *NO* control over who gets to see the message), then either use a webmail system, or just don't post.</para>
+</listitem>
+
+<listitem>
+Off-topic <para>Stay on-topic for the list. This isn't a good place to discuss automobiles, politics, music, or anything that is not related to Netfilter. Sometimes topics will diverge from the general discussion, but please try to keep it relevant to the list topic. Do not ask usage questions in the devel list, or vice versa</para>
+</listitem>
+
+<listitem>
+Message time and date <para>Please make sure the date and time on your computer is always current. When your date is set to something such as the year 2006, messages posted by you will get sorted based on that date, which may put them outside of the related month or year they belong in.</para>
+</listitem>
+
+</itemizedlist>
+
+</section>
+
<section id="ml-announce">
<title>The netfilter-announce mailinglist</title>
<para>
diff -urN homepage/xml/layout.xml homepage.new/xml/layout.xml
--- homepage/xml/layout.xml 2004-01-10 03:41:52.000000000 +0530
+++ homepage.new/xml/layout.xml 2004-01-28 10:18:32.527810288 +0530
@@ -111,6 +111,10 @@
<tocentry page="security/2003-08-01-nat-sack.xml" filename="2003-08-01-nat-sack.html"/>
</tocentry>
<tocentry page="contact.xml" filename="contact.html">
+ <tocentry id="list-rules" href="/contact.html#list-rules">
+ <title>The netfilter mailinglist rules</title>
+ <titleabbrev>List Rules</titleabbrev>
+ </tocentry>
<tocentry id="toc-contact-ml-announce" href="/contact.html#ml-announce">
<title>The netfilter announce mailinglist</title>
<titleabbrev>netfilter-announce list</titleabbrev>
^ permalink raw reply
* Re: [uml-devel] Re: more on COW (long)
From: Jeff Dike @ 2004-01-28 5:18 UTC (permalink / raw)
To: James W McMechan; +Cc: user-mode-linux-devel
In-Reply-To: <20040119.155346.-522689.0.mcmechanjw@juno.com>
mcmechanjw@juno.com said:
> above the ubd device is the request queue where the LVM system lives,
> it should be possible to have a LVM module that can understand the COW
> format, I think it would work best, from what I have seen, as part of
> the device mapper LVM, in 2.6 and there is a backport to 2.4
> apparently
Ah, that's something I hadn't considered.
> Well yes, I want to be able to read real disk images either from a raw
> device, yes we could stick in a special case ioctl to check for a real
> device and read its geometry but ick it is easier to specify it, or
> from a dd'ed image file of a hard disk which would not work even with
> the ioctl, so ubd1C102H15S16 is better from my view :)
OK, build it and maybe people will come :-)
> Um, no the header of the COW is tried first and it was not a multiple
> of 512 that is why the raw device broke it tried to read the V2 header
> and had a I/O error
Yeah, the driver needs to round up to 512 bytes when reading the header.
> Ok how about D -- direct (also uppercase)
That's going to get confused with O_DIRECT, especially if the memnonic is
'direct'. I was also thing 'd', but it meant 'data'.
> Why not, we already have a type field the cow_version why do we need
> another integer to express that it is a new format plus the data in
> the header changes
Because version changes reflect incompatible changes in the format. You
bump the version number when old UMLs can't read the new format. When you
add ISAM, old UMLs won't be able to read it, but they will still be able
to read the normal COW bitmaps. So, this calls for the assignment of a
new cow_format, not a new version.
> the current variable for ISAM does not really map to anything similar
> in a COW file the index and the cow bitmap resemble each other but the
> length computation is very different sector count/8 vs sector count*8
> so there is not much code in common between a COW & ISAM how it is
> laid out on disk is different, how you find a sector is different,
> when you need to update the header is different etc.
This means we need to separate out the stuff that's specific to cow_format
0 from what's not. This may require COW V4, but it doesn't call for a new
version just for ISAM.
> To not follow symlinks like we do now and allow that person who wanted
> symlinks pointing to where the backing files are kept to not show up
> as fixed paths in the COW file
OK, I think that sounds reasonable.
> It had not occurred to me that someone would want to generate a COW
> file on a mounted system at runtime, but now it seems clear that could
> be very useful.
>
> That is why really I like general solutions, they allow strange things
> you did not think of initially to be put in without too much trouble
> once it becomes clear why it would be useful.
I agree, but I'd like to see at least a plausible use for something before
writing it up.
> AIO was a pain to auto detect, the compile time check will find it in
> some cases where glibc emulates it with threads
So libc provides emulation of the aio syscalls, not just aio emulation with
its own interface? In that case, the syscalls can be tested with syscall().
> The new request queue has what I think are the JBD barriers sent in
> the queue and I was thinking that would be nice to sync when we got
> them, much less overhead than the ubd=sync option and it should work
> properly with little effort
Yeah, that would be a good thing. It would also be a good thing to be able
to pass them into the host kernel, so it respects barriers as well. That way
we'd get journalling consistency from the UML filesystem down to the host disk
without needing to turn on O_SYNC.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [LARTC] RE: LARTC digest, Vol 1 #1558 - 9 msgs
From: Roy @ 2004-01-28 4:57 UTC (permalink / raw)
To: lartc
In-Reply-To: <50F73B338A7FD943B7937BBCF99BFBDE33B0D5@mail.sofaware.com>
> As was mentioned before: the netfilter framework itself is able to drop
> packets without negative side effects. So this should also be possible
> for IMQ (or any other network device driver).
>
Well, this needs to be tested. I will try nerfilter module which can drop
each n-th packet.
I wonder what will happen.
At least policer was not sucessfull for dropping packets.
Basicaly all this could be fixed if to find a way to tell kernel that
device is busy and dont want more data.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.