* RE: Trouble rejecting connections
From: Ben @ 2004-01-28 21:39 UTC (permalink / raw)
To: netfilter
In-Reply-To: <00b801c3e583$fc73cd70$6a02a8c0@klemen>
Perhaps I explained incorrectly. I want to be able to specifically deny an
IP address all access to the server at all. I'm doing this with a line that
looks something like this
$IPTABLES -A INPUT -s blocked.ip.address.here -j DROP
However, when I do that, I am able to still connect from from
blocked.ip.address.here. That's the main thing I am concerned with.
Otherwise, my logging and lo lines work, so I'm going to stick with leaving
well enough alone.
Thanks for your help,
Ben Prince
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Klemen Kecman
Sent: Wednesday, January 28, 2004 4:49 AM
To: netfilter@lists.netfilter.org
Cc: Ben
Subject: Re: Trouble rejecting connections
Place log target above all rules or create LOG chain.
Why use double drop?
If the default policy is set to DROP, there is no need for aditional drop
rules.
Allso fix the lo line .. it can be writen much simpler like $IPT -A INPUT -p
ALL -i $IF_LO -j ACCEPT $IPT -A OUTPUT -p ALL -o $IF_LO -j ACCEPT
----- Original Message -----
From: "Ben" <nigma@nigma.info>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, January 28, 2004 10:19 AM
Subject: Trouble rejecting connections
> Hello all,
>
> I'm having trouble rejecting connections using iptables. I am using
cPanel
> / WHM on a RedHat 7.3 a machine and iptables installed from
> iptables-1.2.8-8.72.3.i386.rpm . I am using a script for my policy,
> it looks like this.
>
>
> //Start script
> IPTABLES="/sbin/iptables"
>
> #Flush everything, start from scratch
> $IPTABLES -F
>
> #Set default policies to DROP
> $IPTABLES -P INPUT DROP
> $IPTABLES -P FORWARD DROP
>
> #Allow all lo traffic
> $IPTABLES -A INPUT -i lo -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT
>
> #Allow all related and established connections $IPTABLES -A INPUT -m
> state --state RELATED,ESTABLISHED -j ACCEPT
>
> #Set default OUTPUT policy to ACCEPT
> $IPTABLES -P OUTPUT ACCEPT
>
> # Open ports for server/services
> $IPTABLES -A INPUT -p tcp --dport 20 -j ACCEPT $IPTABLES -A INPUT -p
> tcp --dport 21 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 22 -j
> ACCEPT $IPTABLES -A INPUT -p tcp --dport 25 -j ACCEPT $IPTABLES -A
> INPUT -p tcp --dport 37 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 43
> -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 53 -j ACCEPT $IPTABLES -A
> INPUT -p udp --dport 53 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 80
> -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 110 -j ACCEPT $IPTABLES -A
> INPUT -p tcp --dport 113 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport
> 143 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 443 -j ACCEPT
> $IPTABLES -A INPUT -p tcp --dport 465 -j ACCEPT $IPTABLES -A INPUT -p
> udp --dport 465 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 873 -j
> ACCEPT $IPTABLES -A INPUT -p udp --dport 873 -j ACCEPT $IPTABLES -A
> INPUT -p tcp --dport 993 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport
> 995 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 2082 -j ACCEPT
> $IPTABLES -A INPUT -p tcp --dport 2083 -j ACCEPT $IPTABLES -A INPUT -p
> tcp --dport 2086 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 2087 -j
> ACCEPT $IPTABLES -A INPUT -p tcp --dport 2089 -j ACCEPT $IPTABLES -A
> INPUT -p tcp --dport 2095 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport
> 3306 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 6666 -j ACCEPT
>
> #Enable Blogger support (non-standards compliant piece of dogshit that
> it
> is)
> $IPTABLES -A INPUT -s 66.102.15.83 -j ACCEPT $IPTABLES -A INPUT -s
> 216.34.7.186 -j ACCEPT
>
> #Add passive-mode people here
> #$IPTABLES -A INPUT -s xxx.xxx.xxx.xxx -j ACCEPT
>
> #Add DENY people here
> #$IPTABLES -A INPUT -s 000.000.000.000 -j DROP $IPTABLES -A INPUT -s
> blocked.ip.address.here -j DROP
>
> #Logging
> $IPTABLES -A INPUT -j LOG --log-prefix "INPUTDEFAULT: "
>
> #Save rules
> iptables-save > /etc/sysconfig/iptables
>
> #Restart for rules to take effect
> service iptables restart
> //End script
>
> The problem is that I can still connect from blocked.ip.address.here.
What
> did I miss?
>
> Ben Prince
> Cyber Pixels
> Systems Administrator
> ben@cyberpixels.com
>
>
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 21:39 UTC (permalink / raw)
To: Grant Grundler; +Cc: ishii.hironobu, linux-kernel, linux-ia64, anton
In-Reply-To: <20040128211405.GG5722@cup.hp.com>
On Wed, 28 Jan 2004 13:14:05 -0800
Grant Grundler <iod00d@hp.com> wrote:
>
> > I believe ppc64 has adopted it too. Of course most drivers don't
> > use it yet.
>
> <search 2.6.2-rc2 source tree>
> grundler <502>find -name '*.[chS]' | xargs fgrep pci_dma_error
> ./include/asm-x86_64/pci.h:#define pci_dma_error(x) ((x) ==
> bad_dma_address)
> grundler <503>
>
> That explains why most drivers don't use it yet.
> It's only supported on one arch.
> Maybe propose this to linux-pci mailing list?
It was discussed on linux-arch and ppc64 at least agreed on it.
The other architectures can get it via a comptibility #define that
is always 0.
There was a patch for that somewhere, but apparently it was never merged
or not merged yet.
Anton, what was the state of that?
-Andi
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 21:39 UTC (permalink / raw)
To: Grant Grundler; +Cc: ishii.hironobu, linux-kernel, linux-ia64, anton
In-Reply-To: <20040128211405.GG5722@cup.hp.com>
On Wed, 28 Jan 2004 13:14:05 -0800
Grant Grundler <iod00d@hp.com> wrote:
>
> > I believe ppc64 has adopted it too. Of course most drivers don't
> > use it yet.
>
> <search 2.6.2-rc2 source tree>
> grundler <502>find -name '*.[chS]' | xargs fgrep pci_dma_error
> ./include/asm-x86_64/pci.h:#define pci_dma_error(x) ((x) =
> bad_dma_address)
> grundler <503>
>
> That explains why most drivers don't use it yet.
> It's only supported on one arch.
> Maybe propose this to linux-pci mailing list?
It was discussed on linux-arch and ppc64 at least agreed on it.
The other architectures can get it via a comptibility #define that
is always 0.
There was a patch for that somewhere, but apparently it was never merged
or not merged yet.
Anton, what was the state of that?
-Andi
^ permalink raw reply
* Re: boot partitions
From: caszonyi @ 2004-01-28 21:37 UTC (permalink / raw)
To: S. Barret Dolph; +Cc: linux-newbie
In-Reply-To: <200401290325.00669.wheds8@ms66.hinet.net>
On Thu, 29 Jan 2004, S. Barret Dolph wrote:
> Are these really necessary? I never had problems without one but I only have
> Linux on my box and no other users.
>
no
usually it's better to have a separate boot partition in a multiuser
environment
> How about Swapfiles instead of a swap partition? Does this really work?
>
yes
you can even have a combination of swap files and swap partitions
> Cordially,
> S. Barret Dolph
> Taipei Taiwan
> -
--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: [PATCH] crypto/sha256.c crypto/sha512.c
From: Jean-Luc Cooke @ 2004-01-28 21:30 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <20040127221229.GA16413@certainkey.com>
Humm,
Pardon my ignorance, but does silence mean "yes"?
Didn't see any changes to http://samba.org/~jamesm/crypto/
JLC
On Tue, Jan 27, 2004 at 05:12:29PM -0500, Jean-Luc Cooke wrote:
> I updated the faster_sha2.c to include a quick performance test, same URL.
>
> The Ch/sec and Maj/sec can't be easily compared, however instruction
> count can to some extent.
>
> http://jlcooke.ca/lkml/faster_sha2_x86.s
> http://jlcooke.ca/lkml/faster_sha2_ppc.s
> http://jlcooke.ca/lkml/faster_sha2_alpha.s
> http://jlcooke.ca/lkml/faster_sha2_sparc.s
>
> Hope this helps, I'll know better next time I ask for patch-blessing. :)
>
> JLC
>
>
> On Tue, Jan 27, 2004 at 01:05:04PM -0800, David S. Miller wrote:
> > On Tue, 27 Jan 2004 15:22:25 -0500
> > Jean-Luc Cooke <jlcooke@certainkey.com> wrote:
> >
> > > The Ch() and Maj() operations are used a lot in sha256/512.
> >
> > Your analysis is great, but James was really asking for numbers :-)
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> http://www.certainkey.com
> Suite 4560 CTTC
> 1125 Colonel By Dr.
> Ottawa ON, K1S 5B6
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
http://www.certainkey.com
Suite 4560 CTTC
1125 Colonel By Dr.
Ottawa ON, K1S 5B6
^ permalink raw reply
* 2.6.1 oops
From: Voicu Liviu @ 2004-01-28 21:33 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 5024 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Settings:
- -------------
liviu@starshooter mnt $ uname -a
Linux starshooter 2.6.1-gentoo #2 Wed Jan 28 22:23:52 IST 2004 i686
AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux
liviu@starshooter mnt $
My .config is attached
- ------------------------------
My lspci output:
- ----------------------
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different
version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1
(rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4
(rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3
(rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2
(rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5
(rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
Controller (rev a1)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97
Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge
(rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:09.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:0d.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 61)
02:00.0 VGA compatible controller: ATI Technologies Inc: Unknown
device 4150
02:00.1 Display controller: ATI Technologies Inc: Unknown device 4170
This is from /etc/fstab
- ------------------------------
/dev/fd0 /mnt/floppy supermount
user,rw,fs=auto,dev=/dev/fd0 0 0
While I tried to access a floppy I got on dmesg:
++++++++++++++++++++++++++++++++++++
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
Unable to handle kernel NULL pointer dereference at virtual address
00000000
~ printing eip:
c024df24
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c024df24>] Tainted: P
EFLAGS: 00210297
EIP is at parse_options+0xf4/0x1f0
eax: 00000000 ebx: ce133015 ecx: 00000005 edx: c03678c2
esi: de8d9e7c edi: cedd31c0 ebp: d4ff8a00 esp: de8d9e6c
ds: 007b es: 007b ss: 0068
Process mount (pid: 17519, threadinfo=de8d8000 task=df049980)
Stack: ce133015 c0396740 de8d9e7c 00200292 ce13300c ce133014 dffef290
000000d0
~ dffef548 000000d0 bf51b57f 00000006 d4ff8a00 cedd31c0 fffffff4
00000000
~ c024e157 00000000 d4ff8a00 00000000 fffffff4 d4ff8a00 00000000
fffffff4
Call Trace:
~ [<c024e157>] supermount_read_super+0x47/0x210
~ [<c015bc94>] get_sb_nodev+0x64/0xa0
~ [<c015be3e>] do_kern_mount+0x8e/0x100
~ [<c024e110>] supermount_read_super+0x0/0x210
~ [<c0171dd5>] do_add_mount+0x95/0x190
~ [<c0172151>] do_mount+0x171/0x1d0
~ [<c0171f5c>] copy_mount_options+0x8c/0x110
~ [<c0172567>] sys_mount+0xd7/0x140
~ [<c010949b>] syscall_call+0x7/0xb
Code: 80 38 00 75 0a ba ea ff ff ff e9 35 ff ff ff 89 04 24 e8 95
~ <1>Unable to handle kernel NULL pointer dereference at virtual
address 00000000
~ printing eip:
c024df24
*pde = 00000000
Oops: 0000 [#2]
CPU: 0
EIP: 0060:[<c024df24>] Tainted: P
EFLAGS: 00210297
EIP is at parse_options+0xf4/0x1f0
eax: 00000000 ebx: cff29015 ecx: 00000005 edx: c03678c2
esi: de8d9e7c edi: d3c7d8c0 ebp: c32e6600 esp: de8d9e6c
ds: 007b es: 007b ss: 0068
Process mount (pid: 17520, threadinfo=de8d8000 task=df049980)
Stack: cff29015 c0396740 de8d9e7c 00200292 cff2900c cff29014 dffef290
000000d0
~ dffef548 000000d0 bf51b57f 00000006 c32e6600 d3c7d8c0 fffffff4
00000000
~ c024e157 00000000 c32e6600 00000000 fffffff4 c32e6600 00000000
fffffff4
Call Trace:
~ [<c024e157>] supermount_read_super+0x47/0x210
~ [<c015bc94>] get_sb_nodev+0x64/0xa0
~ [<c015be3e>] do_kern_mount+0x8e/0x100
~ [<c024e110>] supermount_read_super+0x0/0x210
~ [<c0171dd5>] do_add_mount+0x95/0x190
~ [<c0172151>] do_mount+0x171/0x1d0
~ [<c0171f5c>] copy_mount_options+0x8c/0x110
~ [<c0172567>] sys_mount+0xd7/0x140
~ [<c010949b>] syscall_call+0x7/0xb
Code: 80 38 00 75 0a ba ea ff ff ff e9 35 ff ff ff 89 04 24 e8 95
~ <7>request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAGCrAkj4I0Et8EMgRAhkbAKDba/fgt0Z+T/5FyWC3JaUlWkrWRgCePm5T
jk0Skcd9g/AGcTH1NxyrUSk=
=ozuw
-----END PGP SIGNATURE-----
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 22465 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# 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 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 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_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
# CONFIG_X86_UP_IOAPIC is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ 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_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
CONFIG_PNPBIOS=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD 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_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
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_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
#
# 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 is not set
# CONFIG_SCSI_LOGGING is not set
#
# 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_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA 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_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_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 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_SYM53C416 is not set
# CONFIG_SCSI_DC395x 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
# CONFIG_SCSI_DEBUG 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 is not set
CONFIG_BLK_DEV_DM=y
CONFIG_DM_IOCTL_V4=y
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
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 is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set
#
# 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_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_NET_BROADCOM is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# Bluetooth support
#
# CONFIG_BT is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# 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_PCIPS2 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=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
CONFIG_I2C_ISA=y
CONFIG_I2C_NFORCE2=y
# CONFIG_I2C_PIIX4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIAPRO is not set
#
# I2C Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=y
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_EEPROM=y
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_VIA686A is not set
CONFIG_SENSORS_W83781D=y
#
# Linux InfraRed Controller
#
# CONFIG_LIRC_SUPPORT is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
CONFIG_AGP_NVIDIA=m
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
CONFIG_SPEAKUP_DEFAULT="none"
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# ISA devices
#
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
# CONFIG_USB is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_JFS_FS is not set
CONFIG_XFS_FS=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_SUPERMOUNT=y
# CONFIG_SUPERMOUNT_DEBUG is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
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
#
# Profiling support
#
# CONFIG_PROFILING 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_PAGEALLOC is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_TEST=m
#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
^ permalink raw reply
* [U-Boot-Users] U-boot for MIPS - problem using latest gcc
From: Wolfgang Denk @ 2004-01-28 21:33 UTC (permalink / raw)
To: u-boot
In-Reply-To: <603BA0CFF3788E46A0DB0918D9AA95100A0E2F18@sj580004wcom.int.lantronix.com>
In message <603BA0CFF3788E46A0DB0918D9AA95100A0E2F18@sj580004wcom.int.lantronix.com> you wrote:
> For "-mcpu=" I substituted "-march=mips32" - is this correct?
If this is a MIPS32 processor, yes.
> For -mabicall - what should I substitute?
Dunno. Does your compiler documentation mention this keyword?
> Also - I get an error building cpu/mips/start.s
>
> On line 242 there is a label "memsetup" - the error is "cannot branch to
> undefined symbol". Any ideas?
Yes. The file board/<yourname>/memsetup.S is missing / incorrect.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
Einstein argued that there must be simplified explanations of nature,
because God is not capricious or arbitrary. No such faith comforts
the software engineer. - Fred Brooks, Jr.
^ permalink raw reply
* Re: [Alsa-devel] Re: copy pcm plugin
From: Florian Schmidt @ 2004-01-28 21:30 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-user, alsa-devel
In-Reply-To: <s5hbronucb8.wl@alsa2.suse.de>
On Wed, 28 Jan 2004 20:02:03 +0100
Takashi Iwai <tiwai@suse.de> wrote:
> At Wed, 28 Jan 2004 18:37:32 +0100,
> I wrote:
> >
> > At Wed, 28 Jan 2004 18:05:46 +0100,
> > Florian Schmidt wrote:
> > >
> > >
> > > Hi, as far as i understand it, the copy plugin does nothing but
> > > copy its input to its output. I wonder if it would be easily
> > > possible to extend this plugin to copy to multiple slave pcms.
> > > This way it would be(easily?) possible to "distribute" a stereo
> > > signal to 4 or even 6 channels.
> >
> > route (and plug) plugin already can do that.
> > for example,
>
> ah, in your question, multiple slave pcms are assumed.
> in such a case, combine the multiple pcms via multi plugin at first,
> then use route plugin over it.
Well, i thought i would need to somehow copy to front/rear, etc,
manually. But just using the surround51 or surround40 as slave pcm
sounds just as good. Thanks, Takashi and Jaroslav for the quick infos :)
I will add them to the wiki soon..
Flo
--
signature :)
-------------------------------------------------------
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: NetBSD port and a couple of remarks
From: Kip Macy @ 2004-01-28 21:28 UTC (permalink / raw)
To: Ian Pratt; +Cc: xen-devel
In-Reply-To: <E1AluyH-00066n-00@wisbech.cl.cam.ac.uk>
I understand people's concern. However, Bitmover is no Rambus.
As I already stated in a private mail to Christian, Larry's
only agenda is feeding his family and paying his employees.
-Kip
On Wed, 28 Jan 2004, Ian Pratt wrote:
> > > Are you doing development work on subversion, arch, or another revision
> > > control system? If not, what is the concern?
> >
> > I've worked in the past on cvs for a client. I usually don't care much
> > about licences but there's been so much noise about this one and I take that
> > as an indication that the bitkeeper people have some agenda with that
> > licence and I'd rather not be subject to it.
>
> I've just gone looking for the current version of the license --
> it's not actually easy to find from the web pages:
> http://www.bitkeeper.com/bkl.txt
>
> We certainly had concerns when we embarked on using bk, but
> there's no denying that it's a damn good tool, considerably
> better than cvs/arch/subversion. Different people in the group
> have tried using both arch and subversion for other large
> projects, but the experience hasn't been good.
>
> I'm no lawyer, but from my reading of the license there should be
> no *legal* problem with *anyone* using it for Xen development,
> providing that a) you don't mind having your ChangeLog entries
> logged and viewable to the whole world and b) you intend to make
> the source "publicly available".
>
> The latter point made us slightly nervous as some of the
> ChangeLog entries for a previous large project were somewhat
> 'colourful', but in practice this hasn't been a problem, so far.
>
> Anyhow, I've been meaning to write a script to make the nightly
> src and builds available for download as a tar ball.
>
> Best,
> Ian
>
> =========================================================================
>
>
> BitKeeper License version 1.40, 08/23/02
>
> 1. DEFINITIONS
>
> BKL: This license in its entirety, also known as the BitKeeper License.
>
> You: The licensee of the BitKeeper Software.
>
> BitMover: The licensor of the BitKeeper Software.
>
> BitKeeper Software: The complete set of executable programs and any accom-
> panying files, such as documentation, known as the BitKeeper Soft-
> ware. The set of programs and files must include all files and pro-
> grams distributed by BitMover as part of the BitKeeper Software.
>
> BitKeeper Package: A set of files managed by the same BitKeeper ChangeSet
> file. There may be multiple instances of the package; each instance
> is called a repository.
>
> Single user BitKeeper Package: A BitKeeper Package wherein all changes to
> all files are made by the same person and the total number of files
> does not exceed 1000.
>
> Metadata: Information about the data managed by the BitKeeper Software in a
> BitKeeper Package, such as
>
> + The ChangeSet file;
>
> + The messages which annotate modifications of the data (also known
> as check in comments, ChangeLog entries, and/or log messages);
>
> + All files contained below the top level BitKeeper directory in a
> BitKeeper Package, in particular the BitKeeper/html directory and
> the BitKeeper/etc/config file.
>
> Open Logging: The transmission of Metadata about the data managed by the
> BitKeeper Software, to a functioning Open Logging server in the open-
> logging.org domain (or an alternative domain as posted on www.bit-
> keeper.com/logging). Examples of such collected information may be
> seen at http://www.openlogging.org.
>
> Conforming Software: BitKeeper Software that:
>
> (i) passes all of the current, unmodified, regression tests for the
> BitKeeper Software;
>
> (ii) performs all licensing functions, such as Open Logging, identically
> to the current version of the BitKeeper Software as distributed by
> BitMover, Inc.
>
> 2. LICENSE GRANTS
>
> Licensees may freely install, use, copy, and distribute Conforming Soft-
> ware.
>
> 3. LICENSEE OBLIGATIONS
>
> (a) Maintaining Open Logging Feature: You hereby warrant that you will not
> take any action to disable or otherwise interfere with the Open Log-
> ging feature of the BitKeeper Software. You hereby warrant that you
> will take any necessary actions to ensure that the BitKeeper Software
> successfully transmits the Metadata to an Open Logging server within
> 21 days of the creation of said Metadata. By transmitting the Meta-
> data to an Open Logging server, You hereby grant BitMover, or any
> other operator of an Open Logging server, permission to republish the
> Metadata sent by the BitKeeper Software to the Open Logging server.
>
> (b) Accessing Others' BitKeeper Package: You may only use the BitKeeper
> Software to access a BitKeeper Package created by BitMover or third
> parties if you comply with the license of the BitKeeper Package, which
> can be found at the BitKeeper/etc/REPO LICENSE file within the Bit-
> Keeper Package and/or by running bk repo license.
>
> (c) Maintaining Open Source: It is the intent of BitMover that Your use of
> BitKeeper under this license is for the purpose of maintaining Open
> Source. By accepting this license, You agree that You are prepared to
> demonstrate Your conformance, at the request of BitMover, by making
> your BitKeeper repositories publicly available via the BitKeeper pro-
> tocol within 15 days from the time of such request. In the event that
> You do not wish to make BitKeeper repositories publicly available, You
> have 15 days in which to negotiate a waiver, convert said repositories
> to closed use, or cease use of said repositories.
>
> (c) Notwithstanding any other terms in this License, this License is not
> available to You if You and/or your employer develop, produce, sell,
> and/or resell a product which contains substantially similar capabili-
> ties of the BitKeeper Software, or, in the reasonable opinion of Bit-
> Mover, competes with the BitKeeper Software.
>
> (d) Inclusion with another product having source and/or configuration man-
> agement features: Inclusion of the BitKeeper Software for use with a
> system having substantially similar capabilities of the BitKeeper
> Software requires prior written permission from BitMover.
>
> 4. NON-CONFORMING USE
>
> 4.1. Single user packages
>
> For single user BitKeeper Packages, Open Logging is optional.
>
> 4.2. Closed Use
>
> Closed use is the use of the BitKeeper Software without participating in
> BKL licensing restrictions such as Open Logging. Closed use of the Bit-
> Keeper Software requires that you (or your organization) purchase closed
> use licenses for all users of the BitKeeper Software within your organiza-
> tion. This license, the BKL, does not convey authority to make closed use
> of the BitKeeper Software.
>
> 4.3. Logging Waivers
>
> Certain sites which do not wish to participate in Open Logging, such as
> educational or research institutes, may apply for, and may be granted, a
> written waiver from BitMover, Inc. After applying for a written waiver,
> such an institution may use the BitKeeper Software without Open Logging,
> for up to 90 days, or until a response is received from BitMover, Inc.,
> whichever comes first. Should BitMover not grant your waiver request, you
> have the option of converting to Open Logging, immediately terminating your
> use of the BitKeeper Software or continuing your use after purchasing
> closed use license[s].
>
> 4.4. Damages
>
> Use, copying, or distribution of non-conforming software is a violation of
> copyrights held by BitMover on the BitKeeper Software. Damages for copy-
> right infringement are the greater of actual damages or statutory damages,
> which are currently up to $150,000 per infringement.
>
> This license is not available to You if You and/or your company have any
> unresolved copyright disputes with BitMover.
>
> 5. DISCLAIMER OF WARRANTY
>
> COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, WITHOUT
> WARRANTY OR INDEMNIFICATION OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
> INCLUDING, WITHOUT LIMITATION, WARRANTIES OR INDEMNITIES CONCERNING INTEL-
> LECTUAL PROPERTIES (E.G. PATENTS OR COPYRIGHTS), WARRANTIES THAT THE COV-
> ERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
> NON-INFRINGING. SHOULD ANY PORTION OF BITKEEPER SOFTWARE PROVE DEFECTIVE
> IN ANY RESPECT, YOU ASSUME THE COST OF ANY RESULTING DAMAGES, NECESSARY
> SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN
> ESSENTIAL PART OF THIS LICENSE. NO USE OF BITKEEPER SOFTWARE IS AUTHORIZED
> HEREUNDER EXCEPT SUBJECT TO THIS DISCLAIMER.
>
> 6. TERMINATION
>
> + This License and the rights granted hereunder will terminate automati-
> cally if you fail to comply with terms herein. Provisions which, by
> their nature, should remain in effect beyond the termination of this
> License shall survive.
>
> + If any of the licensing requirements, such as Open Logging, are found to
> be unenforceable, then this license automatically terminates unless You
> continue to comply with all of the licensing requirements.
>
> + Should You or your organization choose to institute patent, copyright,
> and/or intellectual property litigation against BitMover, Inc. with
> respect to the BitKeeper Software, then this License and the rights
> granted hereunder will terminate automatically as of the date such liti-
> gation is filed.
>
> + If this License is terminated for any reason, You must delete all copies
> of the BitKeeper Software and cease using the BitKeeper Software.
>
> 7. LIMITATION OF LIABILITY
>
> TO THE FULL EXTENT ALLOWED BY APPLICABLE LAW, BITMOVER'S LIABILITY TO YOU
> FOR CLAIMS RELATING TO THIS LICENSE, WHETHER FOR BREACH OR IN TORT, SHALL
> BE LIMITED TO ONE HUNDRED PERCENT (100%) OF THE AMOUNT HAVING THEN ACTUALLY
> BEEN PAID BY YOU TO BITMOVER FOR ALL COPIES LICENSED HEREUNDER OF THE PAR-
> TICULAR ITEMS GIVING RISE TO SUCH CLAIM, IF ANY.
>
> IN NO EVENT WILL BITMOVER BE LIABLE FOR ANY INDIRECT, PUNITIVE, SPECIAL,
> INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING OUT OF
> THIS LICENSE (INCLUDING, WITHOUT LIMITATION, LOSS OF PROFITS, USE, DATA, OR
> OTHER ECONOMIC ADVANTAGE), HOWEVER IT ARISES AND ON ANY THEORY OF LIABIL-
> ITY, WHETHER IN AN ACTION FOR CONTRACT, STRICT LIABILITY OR TORT (INCLUDING
> NEGLIGENCE) OR OTHERWISE, WHETHER OR NOT SUCH PARTY HAS BEEN ADVISED OF THE
> POSSIBILITY OF SUCH DAMAGE AND NOTWITHSTANDING THE FAILURE OF ESSENTIAL
> PURPOSE OF ANY REMEDY.
>
> 8. MISCELLANEOUS
>
> 8.1. Merger
>
> This License represents the complete agreement between You and BitMover
> regarding the BitKeeper Software covered by this License.
>
> 8.2. Assignment
>
> BitMover may assign this License, and its rights and obligations hereunder,
> at its sole discretion.
>
> 8.3. Severability
>
> If any provision of this License is held to be unenforceable, such provi-
> sion shall be reformed only to the extent necessary to make it enforceable.
>
> 8.4. Governing Law/Jurisdiction
>
> This License shall be governed by the laws of the US and the State of Cali-
> fornia, as applied to contracts entered into and to be performed in Cali-
> fornia between California residents. By using this product, you submit to
> the jurisdiction of the courts in the Northern District of California.
>
> BKL Copyright (C) 1999-2002 BitMover, Inc. Page 1
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
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: 2.2 kernel and ext3 filesystems
From: Andreas Dilger @ 2004-01-28 21:28 UTC (permalink / raw)
To: Chuck Campbell, Theodore Ts'o, linux-kernel
In-Reply-To: <20040128205810.GA8287@helium.inexs.com>
On Jan 28, 2004 14:58 -0600, Chuck Campbell wrote:
> I mounted this ext3 filesystem as ext2 on my 2.2.16 kernel system. I made
> some changes to some files (simple edits), and now when I reboot the box in
> 2.2.16, I get the following:
>
> mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
> or too many mounted filesystems
>
> in /var/log/messages I see:
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
> EXT2-fs: ide0(3,66): couldn't mount because of unsupported optional features.
>
>
> I'm reticent to run any e2fsck as old as 2.2.16 kernel version against
> this filesystem, in fear of damaging it. Is this a sane thing to consider,
> or do I need to put this disk back into a more recent box and try to mount it/
> fsck it there?
e2fsck is not tied to any particular kernel version. You should be able to
see the features that ext2 is complaining about with "dumpe2fs -h /dev/hdb2"
in the "Features" line. I'm guessing it's "needs_recovery" that ext2 doesn't
like. That means that you didn't unmount the ext3 filesystem cleanly and
now ext2 can't mount it. Running any non-prehistoric version of e2fsck
will fix it, but as always newer versions are better. Once e2fsck has
cleaned up the journal, it can be mounted by older kernels as ext2 again.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
^ permalink raw reply
* Re: [linux-lvm] LVM and Linux quotas
From: Herbert Poetzl @ 2004-01-28 21:28 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20040127231733.GA25501@oddprocess.org>
On Tue, Jan 27, 2004 at 06:17:33PM -0500, Matthew Daubenspeck wrote:
> First off, please excuse the the newbie question :)
>
> Does LVM work with the standard Linux quotas? I did some googling and
> found nothing other then people having problems. Does it work?
although there is nothing like 'standard Linux quotas',
because (almost) every filesystem, either brings a bunch
of quota routines, if not an entire quota system (like xfs)
with it, or doesn't support quota at all (like jfs), but
in any case the quota stuff lies somewhere between blocklevel
and filelevel access, and I don't think that there are many
possibilities for collisions with something like raid or
lvm/devmapper (which is basically slightly below block level).
the 'standard' filesystem is ext2 (or ext3 nowadays ;) and
the ext2/ext3 quota had some issues for a while, mainly
because it is fairly complex and not widely used. AFAIK
none of those issues where ever related to lvm or md.
to answer your question, yes ext2/ext3 quota and the
journaled quota xfs provides do work on lvm (over raid5)
(at least for me ;)
HTH,
Herbert
> --
> :wq!
>
> Matthew Daubenspeck
> http://www.oddprocess.org
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
^ permalink raw reply
* Re: Debian libc6 upgrade
From: Michael Scondo @ 2004-01-28 21:27 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <200401281652.39190.micha@topsurf.com>
> > > > Hi to all,
> > > > I'm running a mixed Debian Woody, with a few backports and libc6
> > > > 2.3.1-16. Now I would like to upgrade to libc6 2.3.2.ds1-10.
> > > > Anything runs fine - until I try to compile a program :
> The current version of libc6 for woody is 2.2.5-11.5, mixed system, because
> I already upgraded libc6 and a few other packages.
> However, I had first an woody testing system. Then I upgraded the libc6
> from 2.2.4-7 to 2.3.1-16 via aptitude, this was the testing release this
> time. But everything run fine, beside the fact, using the praeprocessor for
> compiling a program didn't succeed.. :-)
> But the compiler did his job.
> Now I did again this upgrade of libc6, also of libc6-dev and
> linux-kernel-headers using aptitude.
> Maybe, I've got the wrong version of gcc (2.95.4-9 now ) ?
>
It drives me crazy - I upgraded now gcc and g++ and the depending librarys -
gcc compiles fine, but the praeprocessor still doesn't make his job at least
it seems to me to be the praeprocessor.
micha@betageuze:~/prog/test/t2$ gcc -o hallo hallo.c
micha@betageuze:~/prog/test/t2$ ./hallo
Hallo !
micha@betageuze:~/prog/test/t2$ gcc -o hallo hallo.cpp
/tmp/ccUmthd6.o(.eh_frame+0x11): undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status
micha@betageuze:~/prog/test/t2$
Anyone has a tip ?
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Andrew Morton @ 2004-01-28 21:25 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: linux-kernel, linux-mm
In-Reply-To: <20040128073237.6e53d999.rddunlap@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> About kernel-janitors patches:
>
> Do you want to continue reviewing/merging the KJ patches one by one
> or just grab the complete patchset?
Please just send them to me in the usual manner when you think they're
ready. The reject rate has been fairly high, so we need to go through them
carefully.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply
* [parisc-linux] fyi: parted now creates parisc boot partitions
From: Richard Hirst @ 2004-01-28 21:25 UTC (permalink / raw)
To: parisc-linux; +Cc: debian-hppa
As of parted-1.6.6-7 from your debian mirror you can now use it to set a
partition type to 'F0' for palo use. This is done via "set N palo on",
where N is the partition number. Thanks to Sven Luther for accepting my
patch and uploading.
Richard
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Andrew Morton @ 2004-01-28 21:25 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: linux-kernel, linux-mm
In-Reply-To: <20040128073237.6e53d999.rddunlap@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> About kernel-janitors patches:
>
> Do you want to continue reviewing/merging the KJ patches one by one
> or just grab the complete patchset?
Please just send them to me in the usual manner when you think they're
ready. The reject rate has been fairly high, so we need to go through them
carefully.
^ permalink raw reply
* [linux-lvm] combining two vg's into one
From: Chris Conn @ 2004-01-28 21:24 UTC (permalink / raw)
To: linux-lvm
I've got 2 vg's on two different partitions on
different disks, one is my root vg and the other
has /usr, /var and /tmp filesystems. I'd like to
keep them on separate disks but use the same vg
if I can, but I'm unsure how to combine them. Do
I have to move the lv's on disk2 out of their vg
or can I just expand the vg on disk1 to include
them? The filesystems are all ReiserFS, system
is Slackware Linux 9.1.
Thanks for any advice,
=====
Chris Conn
cmcgoat@swbell.net http://storm.cadcam.iupui.edu/~cmcgoat
Austin, TX
^ permalink raw reply
* salinfo-0.4 patch
From: Ben Woodard @ 2004-01-28 21:22 UTC (permalink / raw)
To: linux-ia64
Here is a tiny patch for salinfo-0.4. There is a problem with when it
deals with multiple errors. The decoded error messages fill up with
progressively more white space.
The problem seems to be that the indent variable doesn't get cleared
between errors and so the indent level gets progressively deeper until
the file grows to astronomical purportions. My understanding from the
sys admins is that when we first booted up some machines with a salinfo
daemon about half of them crashed because the backlog of errors that had
accumulated in the SAL. As the salinfo_decode daemon processed these
sequentially, and the level of indenting grew, the size of the decoded
files in /var/log/salinfo grew to several megabytes each and quickly
filled up /var and then bad things happened.
While poking around in the iprint function, I also found an error
message that looks like it is better suited for stderr rather than
stdout so I retargetted it.
diff -ru salinfo-0.4/mca.c salinfo-0.4-ben/mca.c
--- salinfo-0.4/mca.c 2003-12-04 12:03:18.000000000 -0800
+++ salinfo-0.4-ben/mca.c 2004-01-27 16:47:44.000000000 -0800
@@ -104,8 +104,9 @@
fputs(" ", stdout);
startofline = 0;
if (++iprintf_count > 1000000 /* arbitrary */) {
- printf("\n\nError: iprintf line count exceeded, aborting output\n\n");
- fflush(stdout);
+ fprintf(stderr,
+ "\n\nError: iprintf line count exceeded, aborting output\n\n");
+ fflush(stderr);
exit(1);
}
}
@@ -1502,7 +1503,7 @@
decode_oem_cpu = cpu;
decode_oem_oemdata_fd = oemdata_fd;
- iprintf_count = 0;
+ iprintf_count = indent = 0;
if (debug > 1)
prt_record_header(lh);
^ permalink raw reply
* Re: [PATCH] PC300 update
From: Christoph Hellwig @ 2004-01-28 21:21 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: torvalds, linux-kernel
In-Reply-To: <Pine.LNX.4.58L.0401281741120.2088@logos.cnet>
> - Mark pci_device_id list with __devinitdata
This is bogus and can crash the kernel if you're unlucky.
> - Add #ifdef DEBUG around debug printk()
What about dprintk or friends instead?
^ permalink raw reply
* Re: Who is listening on port xxx?
From: caszonyi @ 2004-01-28 21:20 UTC (permalink / raw)
To: rgomez@bancomer.com; +Cc: linux-newbie
In-Reply-To: <4011C87400001C22@mail-bcm02.alestra.net.mx>
yOn Wed, 28 Jan 2004, rgomez@bancomer.com wrote:
> Hi, here's the network newbie again...
>
> How or Where can I find which process is listening on specific port?
>
netstat -a
--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: [PATCH] - Improve SN2 TLB flushing algorithms
From: Christoph Hellwig @ 2004-01-28 21:17 UTC (permalink / raw)
To: linux-ia64
In-Reply-To: <20040128205912.GA27401@sgi.com>
On Wed, Jan 28, 2004 at 02:59:12PM -0600, Jack Steiner wrote:
> +#ifdef CONFIG_NUMA
> + cpus_clear(mm->cpu_vm_mask);
> +#endif
I really hate this ifdefs all over the place. Does this really hurt that
much on non-NUMA systems? Also SN2 seems to use this code always so
CONFIG_NUMA looks like the wrong ifdef to me.
> +#ifdef CONFIG_NUMA
> + if (!cpu_isset(smp_processor_id(), mm->cpu_vm_mask))
> + cpu_set(smp_processor_id(), mm->cpu_vm_mask);
cpu_test_and_set()?
> +/* When nodemask_t is available, delete the following definitions */
> +#define NODEMASK_WORDCOUNT ((NR_NODES+(BITS_PER_LONG-1))/BITS_PER_LONG)
> +#define NODE_MASK_ALL { [0 ... ((NR_NODES+BITS_PER_LONG-1)/BITS_PER_LONG)-1] = ~0UL }
> +#define NODE_MASK_NONE { [0 ... ((NR_NODES+BITS_PER_LONG-1)/BITS_PER_LONG)-1] = 0 }
> +typedef unsigned long nodemask_t[NODEMASK_WORDCOUNT];
Don't we have the generic bitmask code merged now?
>
> + for (i=0, cpu=find_first_bit(&mm->cpu_vm_mask, NR_CPUS); cpu < NR_CPUS;
> + i++, cpu=find_next_bit(&mm->cpu_vm_mask, NR_CPUS, ++cpu)) {
This assumes a specific cpumask_t implementation. You should just use
for_each_cpu_mask()
> @@ -218,3 +265,4 @@
>
> sn_send_IPI_phys(physid, vector, delivery_mode);
> }
> +EXPORT_SYMBOL(sn2_send_IPI);
What's this?
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Grant Grundler @ 2004-01-28 21:14 UTC (permalink / raw)
To: Andi Kleen; +Cc: ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128201701.045670db.ak@suse.de>
On Wed, Jan 28, 2004 at 08:17:01PM +0100, Andi Kleen wrote:
> This would likely
> improve the quality of linux drivers long term and make your
> job as maintainer of an "anal IO error" platform easier.
yup. The key drivers we deal with reached that point last year.
Drivers could always be better. But those issues have been discussed
and presented:
o LinuxTag 2002 keynote by Alan Cox, "Submitting new Kernel drivers"
(http://gsyprf11.external.hp.com/porting_zx1/mgp/Code.mgp)
o OLS 2002 talk by Arjan van de Ven, "How not to write kernel drivers"
o OLS 2002 talk by Greg K-H, "Documentation/CodingStyle and Beyond"
o OLS 2002 talk by myself, "Porting Drivers to HP ZX1"
It helps to "enforce" driver quality through "anal IO Error containment"
but it's too late when it happens on a customer box.
> Just it should not be enabled by default in production kernels.
> And finding out where it works reliably will be some work.
agreed.
> There is no reason pci_map_single() has to panic on overflow. On x86-64
> it returns an unmapped address that is guaranteed to cause an bus abort
> for 128KB.
parisc and ia64 will also bus abort. And then HPMC/MCA respectively.
We could reserve a "safe page" and then hand that back I guess.
But that sounds like a very broken error containment strategy to me.
(ie outbound data will be garbage).
This really isn't an issue for HP ZX1/IA64 since most drivers (64-bit)
can bypass the IOMMU and directly address memory. parisc-linux still
isn't commercially interesting.
> And you have an macro to test for it (pci_dma_error()).
I didn't know about pci_dma_error.
Google found two references: One is:
http://www.x86-64.org/lists/discuss/msg03841.html
> I believe ppc64 has adopted it too. Of course most drivers don't
> use it yet.
<search 2.6.2-rc2 source tree>
grundler <502>find -name '*.[chS]' | xargs fgrep pci_dma_error
./include/asm-x86_64/pci.h:#define pci_dma_error(x) ((x) =
bad_dma_address)
grundler <503>
That explains why most drivers don't use it yet.
It's only supported on one arch.
Maybe propose this to linux-pci mailing list?
grant
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Grant Grundler @ 2004-01-28 21:14 UTC (permalink / raw)
To: Andi Kleen; +Cc: ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128201701.045670db.ak@suse.de>
On Wed, Jan 28, 2004 at 08:17:01PM +0100, Andi Kleen wrote:
> This would likely
> improve the quality of linux drivers long term and make your
> job as maintainer of an "anal IO error" platform easier.
yup. The key drivers we deal with reached that point last year.
Drivers could always be better. But those issues have been discussed
and presented:
o LinuxTag 2002 keynote by Alan Cox, "Submitting new Kernel drivers"
(http://gsyprf11.external.hp.com/porting_zx1/mgp/Code.mgp)
o OLS 2002 talk by Arjan van de Ven, "How not to write kernel drivers"
o OLS 2002 talk by Greg K-H, "Documentation/CodingStyle and Beyond"
o OLS 2002 talk by myself, "Porting Drivers to HP ZX1"
It helps to "enforce" driver quality through "anal IO Error containment"
but it's too late when it happens on a customer box.
> Just it should not be enabled by default in production kernels.
> And finding out where it works reliably will be some work.
agreed.
> There is no reason pci_map_single() has to panic on overflow. On x86-64
> it returns an unmapped address that is guaranteed to cause an bus abort
> for 128KB.
parisc and ia64 will also bus abort. And then HPMC/MCA respectively.
We could reserve a "safe page" and then hand that back I guess.
But that sounds like a very broken error containment strategy to me.
(ie outbound data will be garbage).
This really isn't an issue for HP ZX1/IA64 since most drivers (64-bit)
can bypass the IOMMU and directly address memory. parisc-linux still
isn't commercially interesting.
> And you have an macro to test for it (pci_dma_error()).
I didn't know about pci_dma_error.
Google found two references: One is:
http://www.x86-64.org/lists/discuss/msg03841.html
> I believe ppc64 has adopted it too. Of course most drivers don't
> use it yet.
<search 2.6.2-rc2 source tree>
grundler <502>find -name '*.[chS]' | xargs fgrep pci_dma_error
./include/asm-x86_64/pci.h:#define pci_dma_error(x) ((x) ==
bad_dma_address)
grundler <503>
That explains why most drivers don't use it yet.
It's only supported on one arch.
Maybe propose this to linux-pci mailing list?
grant
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 21:09 UTC (permalink / raw)
To: Linus Torvalds; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401281221320.28145@home.osdl.org>
On Wed, 28 Jan 2004 12:28:56 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
>
> Alternatively, if you get a lot of information at MCE time (CPU that did
> the access + some device data), just queue up the information in a per-CPU
> queue. You don't have to worry about overflow - you can just drop if if
That assumes that the access happened with preempt off ?
That's fine if it's guaranteed that the MCE still happened inside
readl/writel. But if it's delayed longer for some reason there is no guarantee
that you can find back to the CPU that caused the fault.
Putting it into the pci_dev and using RCU would be probably better.
-Andi
^ permalink raw reply
* Re: [Bluez-users] hci0 problem after timeout
From: Marcel Holtmann @ 2004-01-28 21:10 UTC (permalink / raw)
To: Rafael Vidal Aroca; +Cc: BlueZ Mailing List
In-Reply-To: <40182452.2040509@3WT.com.br>
Hi Rafael,
> Unfortunatly, i don't have access to any other bluetooth dongle :-(
this is actually bad. Maybe a friend or a colleague has one that you can
borrow for testing.
Regards
Marcel
-------------------------------------------------------
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
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 21:09 UTC (permalink / raw)
To: Linus Torvalds; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401281221320.28145@home.osdl.org>
On Wed, 28 Jan 2004 12:28:56 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
>
> Alternatively, if you get a lot of information at MCE time (CPU that did
> the access + some device data), just queue up the information in a per-CPU
> queue. You don't have to worry about overflow - you can just drop if if
That assumes that the access happened with preempt off ?
That's fine if it's guaranteed that the MCE still happened inside
readl/writel. But if it's delayed longer for some reason there is no guarantee
that you can find back to the CPU that caused the fault.
Putting it into the pci_dev and using RCU would be probably better.
-Andi
^ 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.