* Re: [Fwd: [Bug 1692] New: System do a kernel panic in ip_push_pending_frames]
From: David S. Miller @ 2003-12-17 21:13 UTC (permalink / raw)
To: Nivedita Singhvi; +Cc: netdev
In-Reply-To: <3FE0C366.1080208@us.ibm.com>
On Wed, 17 Dec 2003 12:58:14 -0800
Nivedita Singhvi <niv@us.ibm.com> wrote:
> Any ideas?
I bet the problem doesn't occur if he disables preemption in
his kernel config...
^ permalink raw reply
* Re: udev.rules.devfs + symlinks & a question
From: Svetoslav Slavtchev @ 2003-12-17 21:13 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <marc-linux-hotplug-107105799027697@msgid-missing>
> On Sat, Dec 13, 2003 at 10:33:08PM +0100, Svetoslav Slavtchev wrote:
> > what are the advantages/ disadvantages
> > to compile using klibc ?
>
> A very tiny static executable is created using klibc. That's necessary
> for early boot, and people who care about the size of things.
>
hm
one more note
udev.permissions seems to be tottaly ignored by udev
compiled against klibc ?
all devices are owned by root:root,
with libc udev i do have root:video, root:audio, ....
best,
svetljo
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply
* Quota / SMP / IRQBalance
From: McGuffin, Tim @ 2003-12-17 21:16 UTC (permalink / raw)
To: netfilter-devel
I currently have a Dual P3/800 and a Dual Xeon 2GHz experiencing the
same behavior with multiple kernels and thought I would mention it to
the list. The -devel list seemed a little more appropriate than the
standard netfilter list.
On the Dual 800 running Redhat 9 or Fedora Core 1, the quota match is
completely broken by enabling the irqbalance service. With irqbalance
enabled, the box is able to transfer roughly twice the amount of data
before the quota is exhausted (11437662 bytes out of a 5000000 byte
quota).
On the Dual Xeon 2G with Hyperthreading enabled, they're able to
transfer roughly 4 times the traffic, and the quota counter doesn't
decrement like it should.
When IRQBalance is not loaded from boot, the quota functions work as
they should. After its started they're hosed until the box is rebooted
again.
It seems the quota patch is tied to a single processor handling IRQs and
the load balancing of IRQBalance throws everything off.
I have plenty of trial and error attempts if anyone would like more
information. :)
Thanks,
-Tim McGuffin
^ permalink raw reply
* Re: dmix and full-duplex
From: David Lloyd @ 2003-12-17 21:18 UTC (permalink / raw)
To: Peter Kirk; +Cc: Alsa-devel
In-Reply-To: <200312172155.59061.pwk.linuxfan@gmx.de>
On Wed, 17 Dec 2003, Peter Kirk wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am Mittwoch, 17. Dezember 2003 21:11 schrieb David Lloyd:
> > Otherwise, if you all think this is not a worthwhile avenue to pursue, I
> > will try to convince my wife to let me buy a sblive and call it a day. :)
>
> its a very worth while avenue - in my personal and biased opinion (as
> being heavily involved with teamspeak and its linux problems). You might
> want to read the lengthy thread I created by asking for smart dmix and
> dsnooping - Title is "smart and automatic use of dmix and dsnoop -
> feature suggestion."
I read the thread, it was very informative. Actually that thread was
pretty much my initial reference for learing how dmix works. :) But it
didn't directly address the full-duplex software issue, mostly it talked
about using cards with hardware mixing. I'm hoping to address the issue
directly, and beat it to a bloody conclusion in time for a clan match!
Now *that* is coding under pressure :)
- D
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
^ permalink raw reply
* Re: [Fwd: [Bug 1692] New: System do a kernel panic in ip_push_pending_frames]
From: Nivedita Singhvi @ 2003-12-17 21:29 UTC (permalink / raw)
To: David S. Miller; +Cc: netdev
In-Reply-To: <20031217131312.5625814c.davem@redhat.com>
David S. Miller wrote:
> I bet the problem doesn't occur if he disables preemption in
> his kernel config...
Ah! Hope thats it..
thanks, Dave!
Nivedita
^ permalink raw reply
* RE: Home web server using front firewall
From: Erick Sanz @ 2003-12-17 21:30 UTC (permalink / raw)
To: Antony Stone, Netfilter
In-Reply-To: <200312102340.14210.Antony@Soft-Solutions.co.uk>
Anthony,
This are the entries I had to add to make it work:
iptables -P INPUT DROP
iptables -P OUTPUT DROP
iptables -P FORWARD DROP
iptables -t nat -A PREROUTING -p tcp -d 172.16.1.33 --dport 80 \
-j DNAT --to 10.10.1.240
iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE
iptables -A INPUT -i eth0 -p tcp -d 172.16.1.33 --dport 80 -m state \
--state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -i eth1 -p tcp -s 10.10.1.240 --sport 80 -m state \
--state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -i eth0 -p tcp -d 10.10.1.240 --dport 80 -m state \
--state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -i eth1 -p tcp -s 10.10.1.0/24 --source-port 80 \
-j ACCEPT
iptables -A FORWARD -o eth1 -p tcp -s 10.10.1.240 --sport 80 -m state \
--state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -o eth1 -j ACCEPT
I have read the FAQ on forwarding; however, I can still not understand
the 3 forwarding statements needed; one of them is for input on eth0
(172.16.1.33) to 10.10.1.240. The other one is for data received from
eth1 (10.10.1.240); however, I don't understand the third forward (can't
be taken out as it won't work then)... I see the difference as -i to
-o ... Is there a newby explanation on why?
Also, I would like to "lock" my OUTPUT chain to avoid Netbios and other
protocols to go out... any recommendations?
Thank you VERY much for your time!
Best regards,
Erick Sanz
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Antony Stone
> Sent: Wednesday, December 10, 2003 5:40 PM
> To: Netfilter
> Subject: Re: Home web server using front firewall
>
>
> On Wednesday 10 December 2003 11:24 pm, Erick Sanz wrote:
>
> > All,
> >
> > I am trying to install a small web server at home in order
> > to display some family pictures and some other personal
> > topics (hobbies, interests ...)
> >
> > For this I need port forwarding and probably NAT to change
> > the outgoing IP address.
>
> If you do DNAT for incoming packets, you will get automatic SNAT on the
> outgoing reply packets - you do not need to set up your own rule
> to handle
> these.
>
> > I want the real server to be completely blocked for
> > any other port than http and https on the web server
> > (I am planning to accept requests only from the internal
> > network).
>
> Um, do you really mean what that last bit says? You only want to accept
> requests from the internal network - ie not from the Internet???
>
> > Am I forgetting anything else?
>
> The only thing I can see missing from the rules you posted is:
>
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
>
> That rule will allow the reply packet to traverse your firewall,
> and return to
> the outside world (assuming that's what you really want to happen....).
>
> If you have any problems with the ruleset you posted (with the
> above addition)
> feel free to post here again, but please be as specific as you
> can about what
> the problem is, and how you have tested for it.
>
> Hope you have a good time with netfilter.
>
> Antony.
>
> --
> Success is a lousy teacher. It seduces smart people into
> thinking they can't
> lose.
>
> - William H Gates III
>
> Please reply
> to the list;
> please
> don't CC me.
>
>
>
>
> This email message has been scanned for viruses.
>
>
This email message has been scanned for viruses.
^ permalink raw reply
* Re: [LARTC] imq crash investigation
From: Roy @ 2003-12-17 21:32 UTC (permalink / raw)
To: lartc
In-Reply-To: <marc-lartc-107165245312033@msgid-missing>
> > so I suspect that there is problem with shaper itself or netfilter, or
linux
> > dont like when packets are reordered.
> This could be. BTW, today experimenting I got a crash, which says this
> is kernel bug, file skbuff.c, line 92.
How do you get C code error line?
I can only get function name and asm code offset.
also I got diferent errors with original imq, usualy it was in
tcp_retransmit_skb
> > Now I am going to try completely diferent idea, I thing I should name it
not
> > IMQ but NFD because it will be netfilter interface( the part of
netfilter
> > core itself) so EVERYTHING will pass this interface.
> Ok, do you have a website?
I dont have website for now, I only have http server where I can put
something
I have made htb web interface like in docum.org but it have much more
features( all I was able to find about htb) but not finished completely
As about this imq driver I had no luck to make it at least abit more usable
my server addres is http://pupa.da.ru
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* Re: usb midi devices.
From: Patrick Shirkey @ 2003-12-17 21:36 UTC (permalink / raw)
To: Clemens Ladisch; +Cc: alsa-devel
In-Reply-To: <Pine.HPX.4.33n.0312171510340.4515-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
> Martin Langer wrote:
>
>>And there are some other cards (Sonica, ...) which need a firmware download,
>>but there's no linux loader available.
>
>
> MobilePre, Sonica, Transit, Ozone (all from M-Audio).
>
Thanks.
>
> BTW: Patrick, what would be the preferred format for submitting
> changed to the soundcard list? (There's no file to send a patch for.)
>
For now just make additions to each manufacturer. I am working on a more
simple backend but haven't finished it yet.
ATM I have just split each manufacturer into their own file and parse it
when the user asks to see it.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
^ permalink raw reply
* Re: 2.6.0-test9 - poor swap performance on low end machines
From: Andrew Morton @ 2003-12-17 21:41 UTC (permalink / raw)
To: Roger Luethi; +Cc: riel, andrea, wli, kernel, chris, linux-kernel, mbligh
In-Reply-To: <20031217194950.GA9375@k3.hellgate.ch>
Roger Luethi <rl@hellgate.ch> wrote:
>
> FWIW akpm posted a patch to initialize min_free_kbytes depending on
> available RAM which seemed to make sense but it hasn't made it into
> mainline yet.
Yup. ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test11/2.6.0-test11-mm1/broken-out/scale-min_free_kbytes.patch
Also, note that setup_per_zone_pages_min() plays games to ensure that the
highmem zone's free pages limit is small: there's not a lot of point in
keeping lots of highmem pages free.
^ permalink raw reply
* Re: Catching NForce2 lockup with NMI watchdog
From: George Anzinger @ 2003-12-17 21:41 UTC (permalink / raw)
To: ross, Maciej W. Rozycki; +Cc: linux-kernel
In-Reply-To: <200312180414.17925.ross@datscreative.com.au>
I really want to thank you both for all this information. It will make the code
and comments much easier to understand.
Thanks again
George
Ross Dickson wrote:
>>On Tue, 16 Dec 2003, George Anzinger wrote:
>
>
>
>
>
>>>How confusing :( Could you give me some idea how this works? I have tried
>>>disable_irq(0) and, as best as I can tell, it does not do the trick. The
>>>confusion I have is understanding where in the chain of hardware each of these
>>>thing is taking place.
>
>
> Here is where to find Intel's MP arch spec Maceij mentions.
> I had to find it recently wrt nforce2 issues
>
> http://www.intel.com/design/pentium/datashts/24201606.pdf
>
> Section 3.6.1 Apic Architecture is relevant
> particularly
> Section 3.6.2.2 Virtual Wire Mode
>
> <snip>
> great diagram!
>
> <snip>
>
>>If the above variant does not work, as a last resort, the path for the
>>8254 timer interrupt is via the 8259 reconfigured back into its usual mode
>>and then LINT0 of the BSP reconfigured for an ExtINTA APIC interrupt.
>>Additionally, since at this point the glue logic has probably already
>>locked up due to the messing done above, a few artiffical sets of double
>>INTA cycles are sent to the system bus using the RTC chip and INTIN8
>>reconfigured temporarily to send ExtINTA APIC interrupts via the
>>inter-APIC bus.
>
>
>
>>I do hope a thorough read of the description will make the available
>>variants clear. The I/O APIC input numbers may differ but so far they are
>>almost always as noted above.
>
>
>
>> Maciej
>
>
> All good.
>
> I would like to add a footnote to highlight a potential gotcha as I understand it.
>
> To clarify, the xt pic 8259A does not in itself have a transparent mode as would
> a logic buffer or inverter. It always needs inta cycles to function. In PIC mode
> it is wired to processor pins as per old 8086 and original cpu architecture
> provides the inta cycles to it (bypasses apic, apic seems off).
>
> In virtual wire mode with the 8259A output wired either to a local apic pin on cpu
> or through the io-apic. In this mode it is the local apic which has to provide the
> inta cycles on the bus back to the 8259A for it to function correctly.
>
> The delivery mode has to be set to ExtInt for the register associated with the pin
> that the 8259A output (int on Maceij diagram) is connected to. This is the only
> way to force the apic to deliver the inta cycles to the 8259A and that is how it
> appears transparent to the system. Spec says there can only be one source
> register (local apic) or redirection register (ioapic) of mode ExtInt per system
> regardless of how many local apic and io-apic pins it (int on Maceij diagram)
> is connected to.
>
> Gotcha: If none are set to ExtInt then the 8259A will hang for lack of IntA
> cycles.
>
> Section 7.5.11 covers it
> 24319202.pdf available here
>
> http://www.intel.com/design/pentiumii/manuals/243192.htm
>
> Why only one Extint source in virtual wire mode?:
>
> The 8259A in X86 architecture systems needs two inta cycles per interrupt event.
> Do not confuse them with the EOI which is software, the inta is purely hardware.
> It only works properly with one source causing inta cycles. Docs I have do not
> say what happens with more than one source.
>
> How 8259A works in a nutshell (it is more complex in cascade mode).
>
> First the 8259A gets a request from H/ware and if unmasked etc generates its int
> (int on Maceij diagram) out. 8259A then sits there waiting for Inta from cpu
> (PIC mode) or local apic (Virtual wire mode). When the inta arrives the 8259A
> latches its internal ISR bit and waits for second inta. When second inta arrives
> it outputs a vector onto the data bus indicating which ISR bit was set.
>
> If the request from H/ware is still active when the first inta arrives then we get
> the correct vector number.
>
> If it is NOT still exerted then its tough luck and the vector we get 7 for the first
> 8259A or 15 for the second 8259A and it is too late to try and find out where
> the real source was, hence the spurious irq7 messages and corresponding
> irq 7 count increase.
>
> It is pretty bad when the apic system that is handling the 8259A in virtual
> wire mode cannot get the inta to the 8259A in time while the int request
> hardware is still exerting but it happens.
>
> I certainly agree with Marceij's comments that mixed mode of having 8254 PIT
> routed via the 8259A was never meant to occur alongside ioapic handling of
> the other interrupts. It is very problematic not to mention confusing.
>
> I do not know how smoothly the apic handles the 8259A if you would be turning
> that source on and off frequently.
>
> Regards
> Ross Dickson
>
>
>
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
^ permalink raw reply
* [uml-devel] [UML patch] fix 2.6.0-test11 compilation problem
From: Ingo Molnar @ 2003-12-17 21:40 UTC (permalink / raw)
To: user-mode-linux-devel; +Cc: Jeff Dike
In-Reply-To: <Pine.LNX.4.58.0312171924290.12482@earth>
the simple patch below fixes 2.6.0-test11+uml-patch-2.6.0-test9-1
compilation if TT mode is disabled.
Ingo
--- linux/arch/um/sys-i386/semaphore.c.orig
+++ linux/arch/um/sys-i386/semaphore.c
@@ -14,6 +14,7 @@
*/
#include <linux/config.h>
#include <linux/sched.h>
+#include <linux/errno.h>
#include <asm/semaphore.h>
/*
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: 2.6.0-test9 - poor swap performance on low end machines
From: Roger Luethi @ 2003-12-17 21:41 UTC (permalink / raw)
To: Rik van Riel, Andrew Morton, Andrea Arcangeli, wli, kernel, chris,
linux-kernel, mbligh
In-Reply-To: <20031217194950.GA9375@k3.hellgate.ch>
On Wed, 17 Dec 2003 20:49:51 +0100, Roger Luethi wrote:
> right now just to make sure. It's going to take a couple of hours,
> I'll follow up with results.
For efax, a benchmark run with mem=32M, the difference in run time
between values 256 and 1024 for /proc/sys/vm/min_free_kbytes is noise
(< 1%).
Roger
^ permalink raw reply
* Re: PCI Express support for 2.4 kernel
From: Martin Mares @ 2003-12-17 21:44 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux Kernel Development
In-Reply-To: <Pine.GSO.4.58.0312171105200.24864@waterleaf.sonytel.be>
> For the record: PCI Express is _not_ PCI-X.
Yes, that was just a typo, sorry for the confusion.
Have a nice fortnight
--
Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
A. G. Bell is alive and well in New York and still waiting for the dial tone.
^ permalink raw reply
* Re: Catching NForce2 lockup with NMI watchdog
From: George Anzinger @ 2003-12-17 21:48 UTC (permalink / raw)
To: ross; +Cc: Maciej W. Rozycki, linux-kernel
In-Reply-To: <200312180414.17925.ross@datscreative.com.au>
Ross Dickson wrote:
>
> Section 7.5.11 covers it
> 24319202.pdf available here
I wonder if you might know the difference between the 243190/1/2 and the
245470/1/2 manuals. I have hard copies of the ladder.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
^ permalink raw reply
* [udev] bug in udev-remove.c
From: Kay Sievers @ 2003-12-17 21:53 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
Uups, we have a bug in udev-remove.c.
udev segfaults with NULL-pointer, if the device is not in the database:
./test.block: line 29: 4844 Segmentation fault $BIN block
Dec 17 22:47:42 pim udev[4882]: udev_remove_device: '/block/sdy' not found in database, falling back on default name
Dec 17 22:47:42 pim udev[4882]: udev_remove_device: name is '(null)'
thanks,
Kay
[-- Attachment #2: 01-bug-in-remove.diff --]
[-- Type: text/plain, Size: 731 bytes --]
--- ../udev/udev-remove.c 2003-12-10 03:40:14.000000000 +0100
+++ udev-remove.c 2003-12-17 22:45:09.000000000 +0100
@@ -118,8 +118,8 @@
*/
int udev_remove_device(char *path, char *subsystem)
{
- char name[100];
struct udevice *dev;
+ struct udevice device;
char *temp;
dev = udevdb_get_dev(path);
@@ -128,13 +128,15 @@
temp = strrchr(path, '/');
if (temp == NULL)
return -ENODEV;
- strncpy(name, &temp[1], sizeof(name));
+ memset(&device, 0, sizeof(device));
+ dev = &device;
+ strncpy(device.name, &temp[1], sizeof(device.name));
}
dbg("name is '%s'", dev->name);
udevdb_delete_dev(path);
- sysbus_send_remove(name, path);
+ sysbus_send_remove(dev->name, path);
return delete_node(dev);
}
^ permalink raw reply
* [uml-devel] [bug] uml segfaults if forcing static link, 2.6.0-test11
From: Ingo Molnar @ 2003-12-17 21:54 UTC (permalink / raw)
To: user-mode-linux-devel; +Cc: Jeff Dike
In-Reply-To: <Pine.LNX.4.58.0312171924290.12482@earth>
the attached .config produces an UML binary that segfaults much the same
way as before the ALIGN fixes. The thing that seems to cause it is the
CONFIG_STATIC_LINK=y option. The kernel is 2.6.0-test11 +
uml-patch-2.6.0-test9-1 + align_fix.
Program received signal SIGSEGV, Segmentation fault.
0xa0174578 in _dl_non_dynamic_init ()
(gdb) bt
#0 0xa0174578 in _dl_non_dynamic_init ()
#1 0xa0174746 in __libc_init_first ()
#2 0xa0164a1d in __libc_start_main ()
Ingo
#
# Automatically generated make config: don't edit
#
CONFIG_USERMODE=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
#
# UML-specific options
#
# CONFIG_MODE_TT is not set
CONFIG_STATIC_LINK=y
CONFIG_MODE_SKAS=y
CONFIG_NET=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_HOSTFS=y
# CONFIG_HPPFS is not set
CONFIG_MCONSOLE=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_HOST_2G_2G is not set
# CONFIG_UML_SMP is not set
# CONFIG_SMP is not set
CONFIG_NEST_LEVEL=0
CONFIG_KERNEL_HALF_GIGS=1
# CONFIG_HIGHMEM is not set
# CONFIG_PROC_MM is not set
CONFIG_KERNEL_STACK_ORDER=2
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
# CONFIG_STANDALONE is not set
CONFIG_BROKEN=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 is not set
# 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
#
# Loadable module support
#
# CONFIG_MODULES is not set
#
# Generic Driver Options
#
#
# Character Devices
#
CONFIG_STDIO_CONSOLE=y
CONFIG_SSL=y
CONFIG_FD_CHAN=y
CONFIG_NULL_CHAN=y
CONFIG_PORT_CHAN=y
CONFIG_PTY_CHAN=y
CONFIG_TTY_CHAN=y
CONFIG_XTERM_CHAN=y
CONFIG_CON_ZERO_CHAN="fd:0,fd:1"
CONFIG_CON_CHAN="xterm"
CONFIG_SSL_CHAN="pty"
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
# CONFIG_WATCHDOG is not set
CONFIG_UML_SOUND=y
CONFIG_SOUND=y
CONFIG_HOSTAUDIO=y
#
# Block Devices
#
CONFIG_BLK_DEV_UBD=y
# CONFIG_BLK_DEV_UBD_SYNC is not set
CONFIG_BLK_DEV_COW_COMMON=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_MMAPPER is not set
CONFIG_NETDEVICES=y
#
# UML Network Devices
#
CONFIG_UML_NET=y
CONFIG_UML_NET_ETHERTAP=y
CONFIG_UML_NET_TUNTAP=y
CONFIG_UML_NET_SLIP=y
CONFIG_UML_NET_DAEMON=y
CONFIG_UML_NET_MCAST=y
# CONFIG_UML_NET_PCAP is not set
CONFIG_UML_NET_SLIRP=y
#
# Networking support
#
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# 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_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 is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_DUMMY=y
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET is not set
#
# Ethernet (1000 Mbit)
#
#
# Ethernet (10000 Mbit)
#
CONFIG_PPP=y
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
# CONFIG_PPP_DEFLATE is not set
# CONFIG_PPP_BSDCOMP is not set
# CONFIG_PPPOE is not set
CONFIG_SLIP=y
# CONFIG_SLIP_COMPRESSED is not set
# CONFIG_SLIP_SMART is not set
# CONFIG_SLIP_MODE_SLIP6 is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# 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
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
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 is not set
CONFIG_MINIX_FS=y
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS 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 is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# 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
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
#
# SCSI support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Kernel hacking
#
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_INFO is not set
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* [PATCH] Get modpost to work properly with vmlinux in a different directory
From: Bryan O'Sullivan @ 2003-12-17 21:56 UTC (permalink / raw)
To: kai, sam; +Cc: Andrew Morton, linux-kernel
This is pretty trivial. The current version of modpost breaks if
invoked from outside the build tree. This patch fixes that, and
simplifies the code a bit while it's at it.
Since it's not critical, I'd call it a contender for -mm and 2.6.1.
<b
scripts/modpost.c | 23 ++++++++++++++++-------
1 files changed, 16 insertions(+), 7 deletions(-)
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1509 -> 1.1510
# scripts/modpost.c 1.15 -> 1.16
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/12/17 bos@serpentine.pathscale.com 1.1510
# Make detection of whether a module is really vmlinux work regardless of its location.
# --------------------------------------------
#
diff -Nru a/scripts/modpost.c b/scripts/modpost.c
--- a/scripts/modpost.c Wed Dec 17 13:51:25 2003
+++ b/scripts/modpost.c Wed Dec 17 13:51:25 2003
@@ -324,6 +324,19 @@
}
}
+int
+is_vmlinux(const char *modname)
+{
+ const char *myname;
+
+ if ((myname = strrchr(modname, '/')))
+ myname++;
+ else
+ myname = modname;
+
+ return strcmp(myname, "vmlinux") == 0;
+}
+
void
read_symbols(char *modname)
{
@@ -335,8 +348,7 @@
/* When there's no vmlinux, don't print warnings about
* unresolved symbols (since there'll be too many ;) */
- if (strcmp(modname, "vmlinux") == 0)
- have_vmlinux = 1;
+ have_vmlinux = is_vmlinux(modname);
parse_elf(&info, modname);
@@ -460,10 +472,7 @@
int first = 1;
for (m = modules; m; m = m->next) {
- if (strcmp(m->name, "vmlinux") == 0)
- m->seen = 1;
- else
- m->seen = 0;
+ m->seen = is_vmlinux(m->name);
}
buf_printf(b, "\n");
@@ -543,7 +552,7 @@
}
for (mod = modules; mod; mod = mod->next) {
- if (strcmp(mod->name, "vmlinux") == 0)
+ if (is_vmlinux(mod->name))
continue;
buf.pos = 0;
^ permalink raw reply
* Re: Home web server using front firewall
From: Ian Hunter @ 2003-12-17 21:56 UTC (permalink / raw)
To: Erick Sanz; +Cc: netfilter
In-Reply-To: <HFEBJMKNPOCPPMGFHDMCAEJBCDAA.esanz@minorplanetusa.com>
> iptables -A FORWARD -i eth0 -p tcp -d 10.10.1.240 --dport 80 -m state \
> --state NEW,ESTABLISHED,RELATED -j ACCEPT
>
> iptables -A FORWARD -i eth1 -p tcp -s 10.10.1.0/24 --source-port 80 \
> -j ACCEPT
>
> iptables -A FORWARD -o eth1 -p tcp -s 10.10.1.240 --sport 80 -m state \
> --state NEW,ESTABLISHED,RELATED -j ACCEPT
The first forward allows inbound traffic from eth0 (net?) to hit the
webserver on 10.10.1.240
The second forward allows any traffic FROM any webserver in the 10.10.1.0/24
network out to anywhere (ODD!)
The third forward specifically allows the web server at 10.10.1.240 to
respond to web requests, and should be redundant with the second rule
Here's my question -- which interface is which? Assuming eth0 is the
internet side, and eth1 is your DMZ side, you should have these:
iptables -A FORWARD -i eth0 -p tcp -d 10.10.1.240 --dport 80 -j ACCEPT
iptables -A FORWARD -i eth1 -p tcp -s 10.10.1.240 --sport 80 -m
state --state ESTABLISHED,RELATED -j ACCEPT
and that should do it.
Are you logging dropped packets?
> Also, I would like to "lock" my OUTPUT chain to avoid Netbios and other
> protocols to go out... any recommendations?
To drop netbios (137-139 tcp & udp), you'd probably want to drop it going
out AND being forwarded, like this:
iptables -A FORWARD -o eth0 -p tcp --dport 137 -j DROP
iptables -A FORWARD -o eth0 -p tcp --dport 138 -j DROP
iptables -A FORWARD -o eth0 -p tcp --dport 139 -j DROP
iptables -A FORWARD -o eth0 -p udp --dport 137 -j DROP
iptables -A FORWARD -o eth0 -p udp --dport 138 -j DROP
iptables -A FORWARD -o eth0 -p udp --dport 139 -j DROP
iptables -A OUTPUT -o eth0 -p tcp --dport 137 -j DROP
iptables -A OUTPUT -o eth0 -p tcp --dport 138 -j DROP
iptables -A OUTPUT -o eth0 -p tcp --dport 139 -j DROP
iptables -A OUTPUT -o eth0 -p udp --dport 137 -j DROP
iptables -A OUTPUT -o eth0 -p udp --dport 138 -j DROP
iptables -A OUTPUT -o eth0 -p udp --dport 139 -j DROP
> Thank you VERY much for your time!
You get what you pay for... lol
^ permalink raw reply
* Re: no atapi cdrecord burning with 2.6.0-test11-bk10 / bk13
From: bill davidsen @ 2003-12-17 21:47 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <200312171227.53913.gene.heskett@verizon.net>
In article <200312171227.53913.gene.heskett@verizon.net>,
Gene Heskett <gene.heskett@verizon.net> wrote:
| I'm using /dev/hdc for burning in the k3b configuration screens,
| however that path may actually be defined. I haven't quite "grok"ed
| all the details, but it works, and works with <10% of the cpu
| involved when burning.
|
| To me, thats a roaring success :-)
I'm burning on a 2.4 kernel, using ide-scsi, and taking <1% CPU at 16x
burn, so you might check if your CD is set to use DMA, or if it's still
doing PIO. I use about 10% doing an audio burn, which does use PIO in
2.4 AFAIK.
You may be able to drop the CPU a good bit more.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
^ permalink raw reply
* Re: 2.6.0-test11-mm1
From: Andrew Morton @ 2003-12-17 22:01 UTC (permalink / raw)
To: Diego Calleja García; +Cc: linux-kernel, Paul Mackerras
In-Reply-To: <20031217192225.58842400.aradorlinux@yahoo.es>
Diego Calleja García <aradorlinux@yahoo.es> wrote:
>
> local_bh_enable() was called in hard irq context. This is probably a bug
> Call Trace:
> [<c0127b96>] local_bh_enable+0x96/0xa0
> [<e08fc4d8>] ppp_asynctty_receive+0x78/0xd0 [ppp_async]
> [<c01cec6c>] flush_to_ldisc+0xdc/0x130
> [<c01ecc17>] receive_chars+0x227/0x240
> [<c01eccd5>] transmit_chars+0xa5/0xe0
> [<c01ecf7c>] serial8250_interrupt+0x12c/0x130
> [<c010c9f9>] handle_IRQ_event+0x49/0x80
> [<c010cdc8>] do_IRQ+0xb8/0x180
> [<c02ca760>] common_interrupt+0x18/0x20
ppp_asynctty_receive() is called from hard IRQ context and hence may not use
spin_unlock_bh(). The patch converts ppp to use an IRQ-safe spinlock.
25-akpm/drivers/net/ppp_async.c | 9 +++++----
1 files changed, 5 insertions(+), 4 deletions(-)
diff -puN drivers/net/ppp_async.c~ppp-locking-fix drivers/net/ppp_async.c
--- 25/drivers/net/ppp_async.c~ppp-locking-fix Wed Dec 17 13:57:33 2003
+++ 25-akpm/drivers/net/ppp_async.c Wed Dec 17 13:58:27 2003
@@ -321,12 +321,13 @@ ppp_asynctty_receive(struct tty_struct *
char *flags, int count)
{
struct asyncppp *ap = ap_get(tty);
+ unsigned long flags;
if (ap == 0)
return;
- spin_lock_bh(&ap->recv_lock);
+ spin_lock_irqsave(&ap->recv_lock, flags);
ppp_async_input(ap, buf, flags, count);
- spin_unlock_bh(&ap->recv_lock);
+ spin_unlock_irqrestore(&ap->recv_lock, flags);
ap_put(ap);
if (test_and_clear_bit(TTY_THROTTLED, &tty->flags)
&& tty->driver->unthrottle)
@@ -396,9 +397,9 @@ ppp_async_ioctl(struct ppp_channel *chan
if (get_user(val, (int *) arg))
break;
ap->flags = val & ~SC_RCV_BITS;
- spin_lock_bh(&ap->recv_lock);
+ spin_lock_irq(&ap->recv_lock);
ap->rbits = val & SC_RCV_BITS;
- spin_unlock_bh(&ap->recv_lock);
+ spin_unlock_irq(&ap->recv_lock);
err = 0;
break;
_
^ permalink raw reply
* Re: Firewalling non-IPsec connections
From: Peter Hoeg @ 2003-12-17 22:02 UTC (permalink / raw)
To: Netfilter List
In-Reply-To: <GFEPJIHHFOJDOFDMNAJDIEAGEKAA.mark@npsl.co.uk>
Mark Weaver wrote:
>I have to guess so. I've no idea TBH where the packets actually go, but
>this definitely works for me. I'm more of a cook than a chef when it comes
>to netfilter. I've tried looking around the source, but I'm pretty
>clueless, and the native ipsec doesn't seem to be documented at all. It's
>not even got a maintainer listed, and virtually nothing in
>linux/Documentation. (If anyone could point me in the right direction that
>would be great!).
>
mark, you simply rule! this fixed my problem. now, since i was going
nuts trying to figure it out and i couldn't find ANY info on ANYWHERE
(you guys were my last resort), so i have decided to make a small guide
(i needed to learn docbook anyway so this seemed like a good chance)
which can be found here:
http://hoeg.org/lri/
but one thing - to be honest i actually was thinking briefly about the
MARK solution myself but came to the conclusion that since it is similar
to the TOS marks you can set, then technically somebody else could tag
the packets themselves before entering my system which would bypass the
solution. and thats why i didnt take it further. can anybody shed any
light on that?
but in order for the search engines to pick up this message: racoon
linux kernel 2.6 ipsec vpn tunnel firewall iptables netfilter
>It kind of makes sense, because without this we'd have no possibility of
>handling packets that came in via an IPSC tunnel separately.
>
agree
^ permalink raw reply
* [PATCH] Fix 2.4 EFI RTC oops
From: Bjorn Helgaas @ 2003-12-17 22:02 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: trini, linux-kernel
This recent change to 2.4:
ChangeSet@1.1069.155.3, 2003-12-10 18:30:50-02:00, trini@mvista.com
[PATCH] Fix rtc leak
===== arch/cris/drivers/ds1302.c 1.6 vs edited =====
broke efirtc.c (it causes a null pointer dereference on ia64).
The fix is below. Please apply.
Bjorn
P.S. The changeset above doesn't appear to be in 2.6 yet. If/when
you submit it for 2.6, you might consider using this style:
memset(&wtime, 0, sizeof(wtime));
memset(wtime, 0, sizeof(*wtime));
which is more obviously correct than:
memset(&wtime, 0, sizeof(struct rtc_time));
memset(wtime, 0, sizeof(struct rtc_time));
===== drivers/char/efirtc.c 1.6 vs edited =====
--- 1.6/drivers/char/efirtc.c Fri Oct 24 04:35:10 2003
+++ edited/drivers/char/efirtc.c Wed Dec 17 14:33:08 2003
@@ -118,7 +118,7 @@
static void
convert_from_efi_time(efi_time_t *eft, struct rtc_time *wtime)
{
- memset(&wtime, 0, sizeof(struct rtc_time));
+ memset(wtime, 0, sizeof(struct rtc_time));
wtime->tm_sec = eft->second;
wtime->tm_min = eft->minute;
wtime->tm_hour = eft->hour;
^ permalink raw reply
* Re: [Bluez-devel] Getting in touch with libs2 and utils2
From: Marcel Holtmann @ 2003-12-17 22:02 UTC (permalink / raw)
To: Charles Bueche; +Cc: BlueZ Mailing List
In-Reply-To: <1071695000.6361.13.camel@bluez.bueche.ch>
Hi Charles,
> success !!! Works much better than the hacked bthid under gentoo
> 2.6test11.
>
> I followed your guide below (preceded by a cvs checkout of course). I
> then ran
>
> - hcid (from the gentoo bluez packages)
> - /opt/bluetooth/sbin/bthid --daemon
> - moving mouse --> discover message in syslog : WORKS. YOUPI !!!
this is good to hear.
> I don't have any other Bluetooth hardware (beside my Ericsson T68 which
> isn't a HID device AFAIK), so I can't make much more tests.
I have and even 7 HID devices in one piconet are working fine.
> Apparently, gentoo creates the uinput device in /dev/misc instead of the
> usual /dev/input. Thanks to Marcel for testing both in parser.c !
It is the normal way of doing this ;)
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply
* [Bluez-users] HOWTO: Logitech MX900 Bluetooth Optical Mouse on Linux
From: Charles Bueche @ 2003-12-17 22:04 UTC (permalink / raw)
To: bluez-users
Hi,
With the help of Marcel, Olivier and a few other =FCbergeeks of the
Bluez-devel mailing list, I have been able to get my Logitech MX900
mouse working with my Dell Inspiron 8600 equiped with internal
Bluetooth.
I have made a small document to help other MX900 owners. It works for
me, but be prepared to suffer a bit :
- it's probably buggy
- it run CVS code
- it run on Gentoo with 2.6test kernel
- my english is ashaming
http://www.bueche.ch/comp/mx900/mx900.html
Comments welcome. Regards,
Charles
--=20
Charles Bueche <charles@bueche.ch>
sand, snow, wave, wind and net -surfer
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply
* Re: raid0 slower than devices it is assembled of?
From: bill davidsen @ 2003-12-17 21:55 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <Pine.LNX.4.58.0312170758220.8541@home.osdl.org>
In article <Pine.LNX.4.58.0312170758220.8541@home.osdl.org>,
Linus Torvalds <torvalds@osdl.org> wrote:
|
|
| On Wed, 17 Dec 2003, Peter Zaitsev wrote:
| >
| > I'm pretty curious about this argument,
| >
| > Practically as RAID5 uses XOR for checksum computation you do not have
| > to read the whole stripe to recompute the checksum.
|
| Ahh, good point. Ignore my argument - large stripes should work well. Mea
| culpa, I forgot how simple the parity thing is, and that it is "local".
|
| However, since seeking will be limited by the checksum drive anyway (for
| writing), the advantages of large stripes in trying to keep the disks
| independent aren't as one-sided.
There is no "the" parity drive, remember the RAID-5 parity is
distributed. A write takes two seeks, a read, a data write, and a parity
write, but the parity isn't a bottleneck, and as noted above the size
only need be the blocks containing the modified data.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
^ 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.