linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: module mess in -CURRENT
       [not found] ` <Pine.LNX.4.44.0211131655580.6810-100000@home.transmeta.com.suse.lists.linux.kernel>
@ 2002-11-14 10:19   ` Andi Kleen
  2002-11-14 17:32     ` John Alvord
  0 siblings, 1 reply; 20+ messages in thread
From: Andi Kleen @ 2002-11-14 10:19 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-kernel

Linus Torvalds <torvalds@transmeta.com> writes:

> (There are some other patches I'm still thinking about, notably kprobes
> and posix timers, but other than that my plate is fairly empty froma
> feature standpoint. And the kexec stuff I want others to test, at least
> now it's palatable to me).

How about the nanosecond stat stuff? It is needed for reliable make.

If I sent you a patch would you still consider it? It is not that intrusive, 
but needs straightforward editing in all file systems.

-Andi

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14 10:19   ` module mess in -CURRENT Andi Kleen
@ 2002-11-14 17:32     ` John Alvord
  2002-11-14 17:40       ` Andi Kleen
  0 siblings, 1 reply; 20+ messages in thread
From: John Alvord @ 2002-11-14 17:32 UTC (permalink / raw)
  To: Andi Kleen; +Cc: Linus Torvalds, linux-kernel

On 14 Nov 2002, Andi Kleen wrote:

> Linus Torvalds <torvalds@transmeta.com> writes:
> 
> > (There are some other patches I'm still thinking about, notably kprobes
> > and posix timers, but other than that my plate is fairly empty froma
> > feature standpoint. And the kexec stuff I want others to test, at least
> > now it's palatable to me).
> 
> How about the nanosecond stat stuff? It is needed for reliable make.
> 
> If I sent you a patch would you still consider it? It is not that intrusive, 
> but needs straightforward editing in all file systems.
> 
Owens' kbuild-2.5 handled it a different way and didn't need exact
timings. That is especially important since nanosecond time accuracy is
impossible if you are handling a collection of machines doing the
work. NTP is accurate, but not that accurate.

john


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14 17:32     ` John Alvord
@ 2002-11-14 17:40       ` Andi Kleen
  2002-11-14 18:01         ` Andrea Arcangeli
  0 siblings, 1 reply; 20+ messages in thread
From: Andi Kleen @ 2002-11-14 17:40 UTC (permalink / raw)
  To: John Alvord; +Cc: Andi Kleen, Linus Torvalds, linux-kernel

> Owens' kbuild-2.5 handled it a different way and didn't need exact
> timings. That is especially important since nanosecond time accuracy is

You may not believe it, but there are projects other than the kernel
that do use make too.

> impossible if you are handling a collection of machines doing the
> work. NTP is accurate, but not that accurate.

The patch does not actually implement nanosecond resolution, but
jiffies resolution (1ms on 2.5), which is easily reachable with NTP.

-Andi

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14 17:40       ` Andi Kleen
@ 2002-11-14 18:01         ` Andrea Arcangeli
  2002-11-14 18:18           ` Andi Kleen
  2002-11-15  0:27           ` Jamie Lokier
  0 siblings, 2 replies; 20+ messages in thread
From: Andrea Arcangeli @ 2002-11-14 18:01 UTC (permalink / raw)
  To: Andi Kleen; +Cc: John Alvord, Linus Torvalds, linux-kernel

On Thu, Nov 14, 2002 at 06:40:49PM +0100, Andi Kleen wrote:
> > Owens' kbuild-2.5 handled it a different way and didn't need exact
> > timings. That is especially important since nanosecond time accuracy is
> 
> You may not believe it, but there are projects other than the kernel
> that do use make too.
> 
> > impossible if you are handling a collection of machines doing the
> > work. NTP is accurate, but not that accurate.
> 
> The patch does not actually implement nanosecond resolution, but
> jiffies resolution (1ms on 2.5), which is easily reachable with NTP.

1msec still leave a reasonable window open IMHO. this problem would need
sequence numbers updated atomically to be solved correctly without
regard to the timing that may vary depending on the hardware IMHO (so
that it could still work on a 1Thz cpu even if it's not a pratical
matter for at least this decade).

Andrea

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14 18:01         ` Andrea Arcangeli
@ 2002-11-14 18:18           ` Andi Kleen
  2002-11-15  0:27           ` Jamie Lokier
  1 sibling, 0 replies; 20+ messages in thread
From: Andi Kleen @ 2002-11-14 18:18 UTC (permalink / raw)
  To: Andrea Arcangeli; +Cc: Andi Kleen, John Alvord, Linus Torvalds, linux-kernel

On Thu, Nov 14, 2002 at 07:01:17PM +0100, Andrea Arcangeli wrote:
> On Thu, Nov 14, 2002 at 06:40:49PM +0100, Andi Kleen wrote:
> > > Owens' kbuild-2.5 handled it a different way and didn't need exact
> > > timings. That is especially important since nanosecond time accuracy is
> > 
> > You may not believe it, but there are projects other than the kernel
> > that do use make too.
> > 
> > > impossible if you are handling a collection of machines doing the
> > > work. NTP is accurate, but not that accurate.
> > 
> > The patch does not actually implement nanosecond resolution, but
> > jiffies resolution (1ms on 2.5), which is easily reachable with NTP.
> 
> 1msec still leave a reasonable window open IMHO. this problem would need
> sequence numbers updated atomically to be solved correctly without
> regard to the timing that may vary depending on the hardware IMHO (so
> that it could still work on a 1Thz cpu even if it's not a pratical
> matter for at least this decade).
> 

The API is ready for nanoseconds so when you feel the need you can 
convert it to using do_gettimeofday()

-Andi

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14 18:01         ` Andrea Arcangeli
  2002-11-14 18:18           ` Andi Kleen
@ 2002-11-15  0:27           ` Jamie Lokier
  2002-11-15  0:46             ` Linus Torvalds
  1 sibling, 1 reply; 20+ messages in thread
From: Jamie Lokier @ 2002-11-15  0:27 UTC (permalink / raw)
  To: Andrea Arcangeli; +Cc: Andi Kleen, John Alvord, Linus Torvalds, linux-kernel

Andrea Arcangeli wrote:
> 1msec still leave a reasonable window open IMHO. this problem would need
> sequence numbers updated atomically to be solved correctly without
> regard to the timing

I agree 100% - it would be nice to be correct instead of "usually
works".

Once you're talking about nanoseconds, you can have both: each time
you store an mtime, make sure the value is at least 1 nanosecond
greater than the previously stored mtime for any file in the
serialisation domain.  If it is not, simply _wait_ for up to a
nanosecond until the value has advanced enough.

-- Jamie

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-15  0:27           ` Jamie Lokier
@ 2002-11-15  0:46             ` Linus Torvalds
  2002-11-15  3:38               ` Andi Kleen
  2002-11-15 18:14               ` Linux 2.5.47 -- Trouble booting Xwindows Mark Hamblin
  0 siblings, 2 replies; 20+ messages in thread
From: Linus Torvalds @ 2002-11-15  0:46 UTC (permalink / raw)
  To: Jamie Lokier; +Cc: Andrea Arcangeli, Andi Kleen, John Alvord, linux-kernel


On Fri, 15 Nov 2002, Jamie Lokier wrote:
> 
> Once you're talking about nanoseconds, you can have both: each time
> you store an mtime, make sure the value is at least 1 nanosecond
> greater than the previously stored mtime for any file in the
> serialisation domain.  If it is not, simply _wait_ for up to a
> nanosecond until the value has advanced enough.

Note that the fields already _are_ nanoseconds, it's just not updated at a
nanosecond rate. We're updating xtime only at a rate of HZ, where the 1 ms
comes from in 2.5.x.

And doing a full "gettimeofday()" sounds just a bit too expensive for the
stuff that needs to just update an inode time field.

But the thing is, we don't actually care about the exact time, we only
care about it being monotonically increasing, so I suspect we could just
have something like

	static unsigned long xtime_count;

	static struct timespec current_time(void)
	{
		struct timespec val;
		unsigned long extra;

		read_lock_irq(&xtime_lock);
		val = xtime;
		extra = xtime_count;
		xtime_count = extra+1;
		read_unlock_irq(&xtime_lock);

		val.nsec += count;
		if (val.tv_nsec > 1000000000) {
			val.tv_nsec -= 1000000000;
			val.tv_sec ++;
		}
		return val;
	}

and then have the timer clear "xtime_count" every time it updates it.  

This obviously doesn't give us nanosecond resolution, but it _does_ give
us "unique" timestamps (assuming a system call takes longer than a
nanosecond, which is likely true for the next decade or so - after that we
can start worrying about whether the users might be outrunning the clock).

		Linus


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-15  0:46             ` Linus Torvalds
@ 2002-11-15  3:38               ` Andi Kleen
  2002-11-15 18:26                 ` Kai Henningsen
  2002-11-15 18:14               ` Linux 2.5.47 -- Trouble booting Xwindows Mark Hamblin
  1 sibling, 1 reply; 20+ messages in thread
From: Andi Kleen @ 2002-11-15  3:38 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Jamie Lokier, Andrea Arcangeli, Andi Kleen, John Alvord, linux-kernel

> and then have the timer clear "xtime_count" every time it updates it.  

Problem is that you cannot easily synchronize such a monotonously increasing
timer in a network. But make needs synchronized times.

-Andi

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Linux 2.5.47 -- Trouble booting Xwindows
  2002-11-15  0:46             ` Linus Torvalds
  2002-11-15  3:38               ` Andi Kleen
@ 2002-11-15 18:14               ` Mark Hamblin
  1 sibling, 0 replies; 20+ messages in thread
From: Mark Hamblin @ 2002-11-15 18:14 UTC (permalink / raw)
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 394 bytes --]

I am trying to set up 2.5.47.  This is my first time building a kernel from
scratch, and I've managed to boot as far as runlevel 3.  However, when I
attempt to boot at runlevel 5, the screen goes black and I have to cycle
power.  I'm guessing I have something set wrong for my video card.  I have
included output from dmesg, lspci, and my config.  I would appreciate any
help.

Thank you.
Mark

[-- Attachment #2: demsg.txt --]
[-- Type: text/plain, Size: 7402 bytes --]

Linux version 2.4.18-3 (bhcompile@daffy.perf.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 Thu Apr 18 07:37:53 EDT 2002
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
 BIOS-e820: 000000000fff0000 - 000000000fff8000 (ACPI data)
 BIOS-e820: 000000000fff8000 - 0000000010000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 65520
zone(0): 4096 pages.
zone(1): 61424 pages.
zone(2): 0 pages.
Kernel command line: ro root=/dev/hde2
Initializing CPU#0
Detected 996.578 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1985.74 BogoMIPS
Memory: 255440k/262080k available (1119k kernel code, 6252k reserved, 775k data, 280k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0383fbff 00000000 00000000 00000000
CPU:             Common caps: 0383fbff 00000000 00000000 00000000
CPU: Intel Pentium III (Coppermine) stepping 0a
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfdb01, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router VIA [1106/0686] at 00:07.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Starting kswapd
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10e
block: 496 slots per queue, batch=124
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
PDC20265: IDE controller on PCI bus 00 dev 80
PCI: Found IRQ 11 for device 00:10.0
PDC20265: chipset revision 2
ide: Found promise 20265 in RAID mode.
PDC20265: not 100% native mode: will probe irqs later
PDC20265: ROM enabled at 0xdffc0000
PDC20265: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode.
    ide2: BM-DMA at 0xcc00-0xcc07, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdg:DMA, hdh:pio
hdc: SR243T, ATAPI CD/DVD-ROM drive
hde: WDC WD400BB-32BSA0, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xdc00-0xdc07,0xd802 on irq 11
blk: queue c035ed6c, I/O limit 4095Mb (mask 0xffffffff)
hde: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
 hde: hde1 hde2 hde3
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 122k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 280k freed
Adding Swap: 524152k swap-space (priority -1)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 07:43:07 Apr 18 2002
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 5 for device 00:07.3
PCI: Sharing IRQ 5 with 00:07.2
PCI: Sharing IRQ 5 with 00:0f.0
usb-uhci.c: USB UHCI at I/O 0xc000, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 5 for device 00:07.2
PCI: Sharing IRQ 5 with 00:07.3
PCI: Sharing IRQ 5 with 00:0f.0
usb-uhci.c: USB UHCI at I/O 0xbc00, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide2(33,2), internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide2(33,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ide-floppy driver 0.99.newide
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdc: DMA disabled
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport_pc: Via 686A parallel port: io=0x378
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
PCI: Found IRQ 5 for device 00:0f.0
PCI: Sharing IRQ 5 with 00:07.3
PCI: Sharing IRQ 5 with 00:07.2
eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:ED:06:9B:B7, IRQ 5.
  Board assembly 727095-004, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
PCI: Found IRQ 3 for device 00:0e.0
eth1: OEM i82557/i82558 10/100 Ethernet, 00:20:ED:06:9B:B6, IRQ 3.
  Board assembly 727095-004, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).

[-- Attachment #3: lspci.txt --]
[-- Type: text/plain, Size: 834 bytes --]

00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:0e.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
00:0f.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
00:10.0 RAID bus controller: Promise Technology, Inc. 20265 (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage XL AGP 2X (rev 27)

[-- Attachment #4: .config --]
[-- Type: application/octet-stream, Size: 20712 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set

#
# General setup
#
CONFIG_NET=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_CPU_FREQ is not set
CONFIG_TOSHIBA=m
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y

#
# Power management options (ACPI, APM)
#

#
# ACPI Support
#
# CONFIG_ACPI is not set
# CONFIG_PM is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
CONFIG_EISA=y
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
CONFIG_CARDBUS=y
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m

#
# PCI Hotplug Support
#

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
# CONFIG_PNP_NAMES is not set
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_GENERIC is not set
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_AMD74XX_OVERRIDE is not set
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_CY82C693=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_HPT34X=y
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NFORCE is not set
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_SVWKS=y
# CONFIG_BLK_DEV_SIIMAGE is not set
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI device support
#
CONFIG_SCSI=m

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_SCSI_PCMCIA is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
CONFIG_MD_MULTIPATH=m
# CONFIG_BLK_DEV_DM is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
# CONFIG_NETFILTER is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_LARGE_TABLES=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
CONFIG_VLAN_8021Q=m
# CONFIG_LLC is not set
CONFIG_DECNET=m
CONFIG_DECNET_SIOCGIFCONF=y
# CONFIG_BRIDGE is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=m
# CONFIG_NET_SCH_HTB is not set
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL1=m
CONFIG_EL2=m
CONFIG_ELPLUS=m
CONFIG_EL3=m
CONFIG_3C515=m
CONFIG_VORTEX=m
CONFIG_LANCE=m
CONFIG_NET_VENDOR_SMC=y
CONFIG_WD80x3=m
CONFIG_ULTRA=m
CONFIG_ULTRA32=m
CONFIG_SMC9194=m
CONFIG_NET_VENDOR_RACAL=y
CONFIG_NI52=m
CONFIG_NI65=m

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
CONFIG_DEPCA=m
CONFIG_HP100=m
CONFIG_NET_ISA=y
CONFIG_E2100=m
CONFIG_EWRK3=m
CONFIG_EEXPRESS=m
CONFIG_EEXPRESS_PRO=m
CONFIG_HPLAN_PLUS=m
CONFIG_HPLAN=m
CONFIG_LP486E=m
CONFIG_ETH16I=m
CONFIG_NE2000=m
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_APRICOT=m
CONFIG_CS89x0=m
CONFIG_DGRS=m
CONFIG_EEPRO100=m
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
# CONFIG_PPP_BSDCOMP is not set
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m

#
# Old SIR device drivers
#
# CONFIG_IRTTY_OLD is not set
CONFIG_IRPORT_SIR=m

#
# Old Serial dongle support
#
# CONFIG_DONGLE_OLD is not set

#
# FIR device drivers
#
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
# CONFIG_TOSHIBA_OLD is not set
CONFIG_TOSHIBA_FIR=m

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
CONFIG_PHONE=m
CONFIG_PHONE_IXJ=m
CONFIG_PHONE_IXJ_PCMCIA=m

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=2048
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
# CONFIG_TIPAR is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
CONFIG_BUSMOUSE=m
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_SOFT_WATCHDOG=m
CONFIG_WDT=m
CONFIG_WDTPCI=m
# CONFIG_WDT_501 is not set
CONFIG_PCWATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_I810_TCO=m
# CONFIG_MIXCOMWD is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_60XX_WDT is not set
CONFIG_W83877F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_INTEL_RNG=m
CONFIG_AMD_RNG=m
CONFIG_NVRAM=m
CONFIG_RTC=y
CONFIG_DTLK=m
CONFIG_R3964=m
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_I810=y
CONFIG_AGP_VIA=y
CONFIG_AGP_AMD=y
CONFIG_AGP_SIS=y
CONFIG_AGP_ALI=y
CONFIG_AGP_SWORKS=y
# CONFIG_AGP_AMD_8151 is not set
CONFIG_DRM=y
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=y
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_MGA=m

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_CRAMFS=m
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_JFS_FS=m
# CONFIG_JFS_POSIX_ACL is not set
CONFIG_JFS_DEBUG=y
# CONFIG_JFS_STATISTICS is not set
CONFIG_MINIX_FS=m
CONFIG_VXFS_FS=m
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_SYSV_FS=m
CONFIG_UDF_FS=m
CONFIG_UFS_FS=m
# CONFIG_XFS_FS is not set

#
# Network File Systems
#
CONFIG_CODA_FS=m
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
# CONFIG_CIFS is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_ZISOFS_FS=y
CONFIG_FS_MBCACHE=y

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
# CONFIG_EFI_PARTITION is not set
CONFIG_SMB_NLS=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y

#
# Sound
#
CONFIG_SOUND=m

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_LONG_TIMEOUT=y

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_OHCI_HCD is not set
# CONFIG_USB_UHCI_HCD_ALT is not set

#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=m
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT is not set
# CONFIG_USB_HIDDEV is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
CONFIG_USB_SCANNER=m
CONFIG_USB_MICROTEK=m

#
# USB Multimedia devices
#
CONFIG_USB_DABUSB=m

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network adaptors
#
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_USBNET=m

#
# USB port drivers
#
CONFIG_USB_USS720=m

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_EDGEPORT=m
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_XIRCOM=m

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI26=m
# CONFIG_USB_TIGL is not set
# CONFIG_USB_LCD is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_KALLSYMS=y

#
# Security options
#
CONFIG_SECURITY_CAPABILITIES=y

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-15  3:38               ` Andi Kleen
@ 2002-11-15 18:26                 ` Kai Henningsen
  0 siblings, 0 replies; 20+ messages in thread
From: Kai Henningsen @ 2002-11-15 18:26 UTC (permalink / raw)
  To: linux-kernel

ak@suse.de (Andi Kleen)  wrote on 15.11.02 in <20021115043827.A20764@wotan.suse.de>:

> > and then have the timer clear "xtime_count" every time it updates it.
>
> Problem is that you cannot easily synchronize such a monotonously increasing
> timer in a network. But make needs synchronized times.

That's really a make problem. It gets much worse when you count in times  
going backwards because you restore a file from backup, or whatever.

What I'd really like make to do - but it can't with the current design -  
is to note the exact time stamp of each dependency when creating a target,  
and when reconsidering that target, finding out if any of those time  
stamps have changed in any way (and, while we're at it, probably check the  
size as well). *Changed since last time*, not younger than the target.

But of course to do that, you need a persistent repository for those time  
stamps - which, I think, kbuild-Owen does.

If you think about the more tricky things to do with make, this is almost  
always what you would need to make a solution much easier.

Take network time shift, for example. Once you no longer need a younger- 
older relation, that time shift is actually completely irrelevant!

One of these days, when I have lots of time (as if!) ...

MfG Kai

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  0:59 ` Linus Torvalds
  2002-11-14  1:05   ` Christoph Hellwig
  2002-11-14  2:27   ` Alan Cox
@ 2002-11-14 18:54   ` Roman Zippel
  2 siblings, 0 replies; 20+ messages in thread
From: Roman Zippel @ 2002-11-14 18:54 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-kernel

Hi,

On Wed, 13 Nov 2002, Linus Torvalds wrote:

> (There are some other patches I'm still thinking about, notably kprobes
> and posix timers, but other than that my plate is fairly empty froma
> feature standpoint. And the kexec stuff I want others to test, at least
> now it's palatable to me).

Linus, please also consider LTT. The benefits might not be immediately 
visible, but it's great tool to the analyze system behaviour, which can 
even be used by non kernel hackers. This means as soon normal users start 
testing 2.5, they're not limited to fuzzy error messages, but they can 
tell you what actually happens, when the system doesn't "feel" right.

bye, Roman


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  4:36     ` Rusty Russell
@ 2002-11-14 14:32       ` Alan Cox
  0 siblings, 0 replies; 20+ messages in thread
From: Alan Cox @ 2002-11-14 14:32 UTC (permalink / raw)
  To: Rusty Russell
  Cc: Linus Torvalds, Christoph Hellwig, Linux Kernel Mailing List

On Thu, 2002-11-14 at 04:36, Rusty Russell wrote:
> 
> Why is PCMCIA broken?

PCMCIA is broken without modules, not broken because of the change (well
it gets rather upset about unload fails but thats a seperate matter)


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  2:32     ` Linus Torvalds
@ 2002-11-14  5:07       ` Rusty Russell
  0 siblings, 0 replies; 20+ messages in thread
From: Rusty Russell @ 2002-11-14  5:07 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Alan Cox, Christoph Hellwig, rusty, Linux Kernel Mailing List

In message <Pine.LNX.4.44.0211131828480.6810-100000@home.transmeta.com> you wri
te:
> 
> > The biggest need though is documentation so people can actually fix all
> > the drivers for this stuff.
> 
> I think Al convinced Rusty that most drivers don't need to worry and that
> Rusty was a bit over-eager (ie sound, much of char, all of block and fs
> should all be handled by upper layers without the races)

Not really.  The Kernel Summit and an audit of drivers convinced me
that changing every driver simply wasn't feasible.

*You* convinced me not to break any driver source code: every time you
dropped my patches I went back and implemented another compat macro 8)

Cheers,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  2:27   ` Alan Cox
  2002-11-14  2:32     ` Linus Torvalds
@ 2002-11-14  4:36     ` Rusty Russell
  2002-11-14 14:32       ` Alan Cox
  1 sibling, 1 reply; 20+ messages in thread
From: Rusty Russell @ 2002-11-14  4:36 UTC (permalink / raw)
  To: Alan Cox, Linus Torvalds; +Cc: Christoph Hellwig, Linux Kernel Mailing List

In message <1037240840.14393.4.camel@irongate.swansea.linux.org.uk> you write:
> On Thu, 2002-11-14 at 00:59, Linus Torvalds wrote:
> > People who find the current module situation difficult can just compile in 
> > the stuff they need for now.
> 
> That makes driver debugging almost impossible. It also makes building a
> test kernel set for a lot of boxes impractical.

Sorry, I know I've been feeding Linus too slowly, but I've just flown
into Spain and I have a tutorial to deliver.  I'm solving it my not
sleeping, but that doesn't scale.

> The completely broken unload stuff is going to be a real pig, PCMCIA
> only works modular and doesn't work now the unloads are all broken.

Agreed, that's what "rmmod --force" is for.  Patch in the queue, I
promise.  That gives more breathing room for fixing the "marked
unsafe" issue.

> OTOH the module rewrite has some nice features and a combo modutils
> is going to sort some of the problem out fairly easily.

Patches welcome, of course.  I didn't do any work on the modutils once
they passed "backwards compat exec works, basic features work".

Trying to test both the entire stack of patches, and just the first
three I was sending to Linus, as every tree came out: well, you can
tell my testing wasn't thorough enough for .47.

> The biggest need though is documentation so people can actually fix all
> the drivers for this stuff.

I posted a document previously (again) and it recieved (valid) harsh
criticism for being opaque.  I'll rework it.  Basically, its an
expansion of the old try_inc_modcount to be a first-class citizen
(hence called try_module_get()).  As previously, should be called
(successfully!)  before calling through a function ptr which might be
in a module (ie. most code which exposes a "register_xxx" should use
it).  Exceptions if that function cannot sleep (and can't be
preemped).

Why is PCMCIA broken?
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  0:02 module mess in -CURRENT Christoph Hellwig
  2002-11-14  0:59 ` Linus Torvalds
@ 2002-11-14  4:06 ` Rusty Russell
  1 sibling, 0 replies; 20+ messages in thread
From: Rusty Russell @ 2002-11-14  4:06 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: linux-kernel

In message <20021114000206.A8245@infradead.org> you write:
> Linus, Rusty,
> 
> what the hell is going on with the modules code in 2.5-CURRENT?
> 
> Rusty's monsterpatch breaks basically everything (and remember we're
> in feature freeze!) instead of doing one thing at a time [1], and it
> is doing three things that are absolutely separate issues.

<sigh>.  I did do it one at a time.  I replaced the module loading
code as stage I.

> We had an almost useable 2.5 and now exactly when we're feature freezing
> and people are expected to test it we break everything?
> 
> Linus, please backout that patch until we a) have modutils that support
> both the new and old code

It works for me.  This is becoming an FAQ, but I thought the code was
obvious: eg. insmod execvp "insmod.old" when it detects an older
kernel, and "make install" moves insmod to insmod.old etc. if
insmod.old doesn't already exist.

> and b) support at least such basic features
> as parsing modules.conf and supporting parameters.

I'm sorry if I'm feeding the patches to Linus too slowly for you, but
you know where to find them, I've posted the URL often enough.  It
hasn't even hit a release yet, so I wasn't worried.

I implemented an in-kernel module loader, implemented the linking code
for 6 architectures, re-implemented all the module cruft cleanly on
top of it, and kept it uptodate through all the changes in Linus'
tree.

And you wonder why I held back fleshing out the implementation of
modprobe, until (if) the code was in the kernel?

> The inkernel loader, generic boot-time option and your - umm - strange
> idea of module unload race reduction are absolute separate things.

I rewrote module.c to make it an in-kernel linker so insmod was 20
lines.  And you think I should have re-implemented races in the
loading and unloading stages too, so I could remove them in a future
patch?

What an odd concept!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  2:27   ` Alan Cox
@ 2002-11-14  2:32     ` Linus Torvalds
  2002-11-14  5:07       ` Rusty Russell
  2002-11-14  4:36     ` Rusty Russell
  1 sibling, 1 reply; 20+ messages in thread
From: Linus Torvalds @ 2002-11-14  2:32 UTC (permalink / raw)
  To: Alan Cox; +Cc: Christoph Hellwig, rusty, Linux Kernel Mailing List


On 14 Nov 2002, Alan Cox wrote:
> 
> That makes driver debugging almost impossible. It also makes building a
> test kernel set for a lot of boxes impractical. The completely broken
> unload stuff is going to be a real pig, PCMCIA only works modular and
> doesn't work now the unloads are all broken.

Yeah, I forgot about the old 16-bit pcmcia crud. Ugh. At least 32-bit 
cardbus works fine.

> The biggest need though is documentation so people can actually fix all
> the drivers for this stuff.

I think Al convinced Rusty that most drivers don't need to worry and that
Rusty was a bit over-eager (ie sound, much of char, all of block and fs
should all be handled by upper layers without the races)

I think Rusty has most of the pieces, but he's apparently flying around 
the world right now ;)

		Linus


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  0:59 ` Linus Torvalds
  2002-11-14  1:05   ` Christoph Hellwig
@ 2002-11-14  2:27   ` Alan Cox
  2002-11-14  2:32     ` Linus Torvalds
  2002-11-14  4:36     ` Rusty Russell
  2002-11-14 18:54   ` Roman Zippel
  2 siblings, 2 replies; 20+ messages in thread
From: Alan Cox @ 2002-11-14  2:27 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Christoph Hellwig, rusty, Linux Kernel Mailing List

On Thu, 2002-11-14 at 00:59, Linus Torvalds wrote:
> People who find the current module situation difficult can just compile in 
> the stuff they need for now.

That makes driver debugging almost impossible. It also makes building a
test kernel set for a lot of boxes impractical. The completely broken
unload stuff is going to be a real pig, PCMCIA only works modular and
doesn't work now the unloads are all broken. OTOH the module rewrite has
some nice features and a combo modutils is going to sort some of the
problem out fairly easily.

The biggest need though is documentation so people can actually fix all
the drivers for this stuff.





^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  0:59 ` Linus Torvalds
@ 2002-11-14  1:05   ` Christoph Hellwig
  2002-11-14  2:27   ` Alan Cox
  2002-11-14 18:54   ` Roman Zippel
  2 siblings, 0 replies; 20+ messages in thread
From: Christoph Hellwig @ 2002-11-14  1:05 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Christoph Hellwig, rusty, linux-kernel

On Wed, Nov 13, 2002 at 04:59:35PM -0800, Linus Torvalds wrote:
> 
> On Thu, 14 Nov 2002, Christoph Hellwig wrote:
> > 
> > Linus, please backout that patch until we a) have modutils that support
> > both the new and old code and b) support at least such basic features
> > as parsing modules.conf and supporting parameters.
> 
> Quite frankly, at this time a backout means that the thing doesn't go in 
> _at_all_.

Probably.  Or just the non-intrusive parts.

> It came in before the feature freeze, but I decided that instead of having 
> a totally hectic time I woul dmerge stuff that I got before the freeze at 
> my own leisure, but backing it out now would be basically saying it's not 
> going into 2.6.x. And I think it's worth it.

I don't think it's a must have and absolutely don't think it's worth
breaking about everything at this stage.  Please tell me why rusty can't
send a large number of non-intrusive patches that do one thing at a
time just like everyone else?  

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: module mess in -CURRENT
  2002-11-14  0:02 module mess in -CURRENT Christoph Hellwig
@ 2002-11-14  0:59 ` Linus Torvalds
  2002-11-14  1:05   ` Christoph Hellwig
                     ` (2 more replies)
  2002-11-14  4:06 ` Rusty Russell
  1 sibling, 3 replies; 20+ messages in thread
From: Linus Torvalds @ 2002-11-14  0:59 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: rusty, linux-kernel


On Thu, 14 Nov 2002, Christoph Hellwig wrote:
> 
> Linus, please backout that patch until we a) have modutils that support
> both the new and old code and b) support at least such basic features
> as parsing modules.conf and supporting parameters.

Quite frankly, at this time a backout means that the thing doesn't go in 
_at_all_.

It came in before the feature freeze, but I decided that instead of having 
a totally hectic time I woul dmerge stuff that I got before the freeze at 
my own leisure, but backing it out now would be basically saying it's not 
going into 2.6.x. And I think it's worth it.

(There are some other patches I'm still thinking about, notably kprobes
and posix timers, but other than that my plate is fairly empty froma
feature standpoint. And the kexec stuff I want others to test, at least
now it's palatable to me).

People who find the current module situation difficult can just compile in 
the stuff they need for now.

		Linus


^ permalink raw reply	[flat|nested] 20+ messages in thread

* module mess in -CURRENT
@ 2002-11-14  0:02 Christoph Hellwig
  2002-11-14  0:59 ` Linus Torvalds
  2002-11-14  4:06 ` Rusty Russell
  0 siblings, 2 replies; 20+ messages in thread
From: Christoph Hellwig @ 2002-11-14  0:02 UTC (permalink / raw)
  To: torvalds, rusty; +Cc: linux-kernel

Linus, Rusty,

what the hell is going on with the modules code in 2.5-CURRENT?

Rusty's monsterpatch breaks basically everything (and remember we're
in feature freeze!) instead of doing one thing at a time [1], and it
is doing three things that are absolutely separate issues.

We had an almost useable 2.5 and now exactly when we're feature freezing
and people are expected to test it we break everything?

Linus, please backout that patch until we a) have modutils that support
both the new and old code and b) support at least such basic features
as parsing modules.conf and supporting parameters.

Rusty, the next time please submit stuff one feature at a time instead
of a monster patch that is cool but breaks everything but looks cool.

The inkernel loader, generic boot-time option and your - umm - strange
idea of module unload race reduction are absolute separate things.

[1] e.g. kbuild2.5 was rejected due to the must change everything criteria.
not that I actually liked the kbuild2.5 design, but this is exactly the
same thing.

^ permalink raw reply	[flat|nested] 20+ messages in thread

end of thread, other threads:[~2002-11-15 19:33 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20021114000206.A8245@infradead.org.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.44.0211131655580.6810-100000@home.transmeta.com.suse.lists.linux.kernel>
2002-11-14 10:19   ` module mess in -CURRENT Andi Kleen
2002-11-14 17:32     ` John Alvord
2002-11-14 17:40       ` Andi Kleen
2002-11-14 18:01         ` Andrea Arcangeli
2002-11-14 18:18           ` Andi Kleen
2002-11-15  0:27           ` Jamie Lokier
2002-11-15  0:46             ` Linus Torvalds
2002-11-15  3:38               ` Andi Kleen
2002-11-15 18:26                 ` Kai Henningsen
2002-11-15 18:14               ` Linux 2.5.47 -- Trouble booting Xwindows Mark Hamblin
2002-11-14  0:02 module mess in -CURRENT Christoph Hellwig
2002-11-14  0:59 ` Linus Torvalds
2002-11-14  1:05   ` Christoph Hellwig
2002-11-14  2:27   ` Alan Cox
2002-11-14  2:32     ` Linus Torvalds
2002-11-14  5:07       ` Rusty Russell
2002-11-14  4:36     ` Rusty Russell
2002-11-14 14:32       ` Alan Cox
2002-11-14 18:54   ` Roman Zippel
2002-11-14  4:06 ` Rusty Russell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).