[EMAIL PROTECTED] (Lennart Sorensen) writes:
> On Fri, Dec 21, 2007 at 12:55:16PM +0100, Jan Engelhardt wrote:
>> o_O I better continue believing it is the subject. Because with
>> one extra word at the front, you can make this a "complete sentence":
>>
>> Please initialize [the] current of
> "DM" == David Miller <[EMAIL PROTECTED]> writes:
>> Reply:
>> Opcode: reply (0x0002)
>> Sender HW: 00:AA.00:AA:00:AA
>> Sender IP: 192.168.0.1
>> Target HW: 00:AA:00:AA:00:AA
>> Target IP:192.168.0.1
DM> And this is exactly a sensible response in my opinion.
Why send the reply at al
> "AK" == Kok, Auke <[EMAIL PROTECTED]> writes:
AK> actually the impact can be quite negative, imagine doing a tcpdump
AK> on a 10gig interface with vlan's enabled - all of a sudden you
AK> might accidentally flood the system with a 100-fold increase in
AK> traffic and force the stack to dump
> "MM" == Matt Mackall <[EMAIL PROTECTED]> writes:
MM> Well there are things we can do, yes, but I'd be worried that
MM> they've give up the deterministic behavior we rely on quite
MM> heavily for debugging. If event A happens before event B, we must
MM> see the message from A before the one f
> "CN" == Carlos Narváez <[EMAIL PROTECTED]> writes:
CN> - IP Forwarding has been enabled on the router via "echo 1 >
CN> /proc/sys/net/ipv4/ip_forward"
Try cat /proc/sys/net/ipv4/conf/*/forwarding. If any of them are 0,
then echo 1 > /proc/sys/net/ipv4/conf/all/forwarding.
/Benny
-
To un
> "WT" == Willy Tarreau <[EMAIL PROTECTED]> writes:
WT> Under unix, the shell resolves "*" and passes the 1 file names
WT> to the "rm" command. Now, execve() may fail because 1 names in
WT> arguments can require too much memory. That's why find and xargs
WT> were invented!
It would be
> "ON" == Oliver Neukum <[EMAIL PROTECTED]> writes:
ON> Because we will be unable to escape that job. Let's assume that we
ON> remove the freezer from the STR path. The next complaint would be
ON> that we cannot do STD with fuse. "Then don't do that" would not be
ON> taken kindly as answer.
A
> "AC" == Alan Cox <[EMAIL PROTECTED]> writes:
AC> A few innovations that afaik first appeared the Linux kernel
The clone() call and the efficient 1:1 threading it brought was
definitely innovative. None of the other Unices had anything similar.
splice() is innovative as well, even though it
> "AC" == Alan Cox <[EMAIL PROTECTED]> writes:
AC> Provided they don't get within about 5-10% of full a lot of the
AC> time Unix file systems generally don't
That's a big if right there. For servers it isn't a problem, few
people can get capacity right to withing 10%, so you never let a
serve
> "BD" == Bill Davidsen <[EMAIL PROTECTED]> writes:
BD> In practice Linux has had lots of practice mounting garbage, and
BD> isn't likely to suffer terminal damage.
These days, with exposed USB ports and automount, it is rather
important that the kernel doesn't suffer terminal damage when mou
> "GM" == Gerhard Mack <[EMAIL PROTECTED]> writes:
GM> On Wed, 4 Apr 2007, Alan Cox wrote:
>> You don't get machines with 64 ethernet ports on add-in cards.
>> There are good reasons for the naming schemes in use.
GM> If they made them I'd build one.
Indeed, port density is disappointingly p
> "PM" == Pavel Machek <[EMAIL PROTECTED]> writes:
PM> ACPI AML is probably turing-complete: I'm afraid you are trying to
PM> solve the halting problem (-> impossible).
If you can restrict the virtual machine which AML runs in to a limited
amount of memory/storage, you can solve halting for i
> "JE" == Jörn Engel <[EMAIL PROTECTED]> writes:
JE> Being good where log-structured filesystems usually are horrible
JE> is a challenge. And I'm sure many people are more interested in
JE> those performance number than in the ones you shine at. :)
Anything that helps performance when untarri
> "JDL" == Jan De Luyck <[EMAIL PROTECTED]> writes:
JDL> I think a nice example of that might be the Linksys WRT54G
JDL> routers.
They don't ship with Linux anymore, except the WRT54GL. Apparently
switching was worth it to save 2MB flash.
/Benny
-
To unsubscribe from this list: send the l
>>>>> "DK" == Dave Kleikamp <[EMAIL PROTECTED]> writes:
DK> On Sun, 2007-01-28 at 10:17 +0100, Benny Amorsen wrote:
>> Perhaps nntp://news.gmane.org/gmane.linux.kernel can help, even if
>> it isn't exactly what you asked for.
DK> I like to
> "DB" == Dirk Behme <[EMAIL PROTECTED]> writes:
DB> Any chance to have anything like an auto-update mbox archive of
DB> LKML? Would be nice for people not permanently subscribed to LKML.
Perhaps nntp://news.gmane.org/gmane.linux.kernel can help, even if it
isn't exactly what you asked for.
> "DS" == David Schwartz <[EMAIL PROTECTED]> writes:
DS> If you are right, a "512MB" RAM stick is mislabelled and is more
DS> correctly labelled as "536.8MB". (With 512MiB being equally
DS> correct.)
DS> Isn't that obviously not just wrong but borderline crazy?
No. It is not obvious to me wh
> "BE" == Bodo Eggert <[EMAIL PROTECTED]> writes:
BE> 1) This change isn't nescensary - any sane person will know that
BE> it's not a SI unit. You wouldn't talk about megabananas == 100
BE> bananas and expect to be taken seriously.
What about megaparsec? I have also seen graphs delimited
> "AvdV" == Arjan van de Ven <[EMAIL PROTECTED]> writes:
AvdV> even if you have NO power savings you still don't meet your
AvdV> criteria. That's basic ethernet for you
AvdV> That's what I was trying to say; your criteria is unrealistic
AvdV> regardless of what the kernel does, ethernet a
> "CP" == Cal Peake <[EMAIL PROTECTED]> writes:
CP> I saw this with kernels v2.6.16, v2.6.17, and v2.6.18. Windows XP
CP> however didn't seem to have any problems. So unless Windows
CP> doesn't have window scaling on by default (or uses a workaround)
CP> it could be a broken kernel.
XP doesn'
20 matches
Mail list logo
