You think politicans are bad? Now amazon.fr are spamming mailing lists. This appeared on linux-xfs.
Received: from mm-outgoing-101.amazon.com (mm-outgoing-101.amazon.com [207.171.188.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g99HuQtG004395 for <linux-xfs@oss.sgi.com>; Wed, 9 Oct 2002 10:56:28 -0700 Received: from mail-ems-102.amazon.com by mm-outgoing-101.amazon.com with ESMTP (crosscheck: mail-ems-102.amazon.com [10.16.42.229]) id KAA-21335150-16130; Wed, 9 Oct 2002 10:19:15 -0700 Received: by mail-ems-102.amazon.com id AAA-21335150-25209,3530; 9 Oct 2002 19:18:31 +0200 Message-id: <.AAA-21335150-25209,3530.1034183911@mail-ems-102. amazon.com>
Faites-vous plaisir!
Ok2mail.com vous offre un cheque-cadeau de 7 euros, a depenser illico sur Amazon.fr!!!
Valable sur tout le catalogue Amazon.fr: Livres, Musique, DVD, Video, Logiciels, Jeux Video.
This is a notorious Australian spammer, they are even suing people who complain about them. Don't bother complaining to the company, complain to the ISP that they are using. So far this spammer has been thrown off uu.net, iprimus.net.au and a couple of.es ISPs.
See my Q&A mail.
In particular Q08, Q09, Q10, Q12.
These problem have been around for a long time and were not fixed in the existing system. Some of them cannot be fixed using pure make rules, they are deficencies in make itself. The pre-processor code is to work around make problems that cannot be solved any other way.
The change to a pre-processor and from recursive make to a global view of the kernel build cannot be done in pieces. There is no sensible way to do part of the build using the old system and part of the build using the new system.
XFS only code. Approx 4Mb of new files for XFS only.
Easy patches to existing files. These add new functions and definitions which are only used by XFS, plus changes to existing Makefiles. It also changes some VM functions to cater for delayed block allocation which only XFS supports. These changes have no affect on VM except for XFS pages.
Tricky patches to existing files. The extra facilities of XFS require extra parameters on some existing VM functions.
LVM updates. The lvm code in 2.4.x has bugs which XFS trips, so we have to include lvm updates in the XFS patch. With the recent announcment of LVM 1.0 this patch should disappear.
Kernel Debugger. SGI maintain kdb and it is included in the XFS tree for ease of use by the XFS developers.
Miscellaneous patches. These include adding XFS to defconfig, setting EXTRAVERSION, workarounds for kernel bugs such as min/max not handling pointers. It also includes kbuild 2.5 changes, XFS is ready for kbuild 2.5.
Extended attributes and ACLs. XFS optionally supports extended attributes and Attribute Control Lists. This is not a core requirement for XFS and there is at least one other group working on ACLs, so this code is separated from the core XFS.
Only the first three patch sets are required to get the core XFS functionality. The other four are nice to have but not mandatory. SGI have repeatedly sent the first three sets to Linus, without any response.
If any kernel distributor (including -ac) wants the individual XFS patches, just ask. SGI do not make them generally available because they are snapshots which are only created as required. The normal method of getting XFS is from CVS or as a release, both of which include all the patch sets.
Part of the design of IPv6 was "avoid lots of little class C adverts in the backbone routers". Each router only needs to hold local information, instead of the 40,000+ IPv4 entries in the top level routers. If you change provider you also change your IPv6 addresses, v6 has built in support for easy renumbering.
When my work VPN is up, dnsmasq redirects some (not all) DNS queries to the resolvers at work. Sounds like FF is going to break my work VPN.
You think politicans are bad? Now amazon.fr are spamming mailing lists. This appeared on linux-xfs.
. amazon.com>
Received: from mm-outgoing-101.amazon.com (mm-outgoing-101.amazon.com [207.171.188.101])
by oss.sgi.com (8.12.5/8.12.5) with SMTP id g99HuQtG004395
for <linux-xfs@oss.sgi.com>; Wed, 9 Oct 2002 10:56:28 -0700
Received: from mail-ems-102.amazon.com by mm-outgoing-101.amazon.com with ESMTP
(crosscheck: mail-ems-102.amazon.com [10.16.42.229])
id KAA-21335150-16130; Wed, 9 Oct 2002 10:19:15 -0700
Received: by mail-ems-102.amazon.com
id AAA-21335150-25209,3530; 9 Oct 2002 19:18:31 +0200
Message-id: <.AAA-21335150-25209,3530.1034183911@mail-ems-102
Faites-vous plaisir!
Ok2mail.com vous offre un cheque-cadeau de 7 euros, a depenser illico sur
Amazon.fr!!!
Valable sur tout le catalogue Amazon.fr:
Livres, Musique, DVD, Video, Logiciels, Jeux Video.
....
This is a notorious Australian spammer, they are even suing people who complain about them. Don't bother complaining to the company, complain to the ISP that they are using. So far this spammer has been thrown off uu.net, iprimus.net.au and a couple of .es ISPs.
These problem have been around for a long time and were not fixed in the existing system. Some of them cannot be fixed using pure make rules, they are deficencies in make itself. The pre-processor code is to work around make problems that cannot be solved any other way.
The change to a pre-processor and from recursive make to a global view of the kernel build cannot be done in pieces. There is no sensible way to do part of the build using the old system and part of the build using the new system.
Only the first three patch sets are required to get the core XFS functionality. The other four are nice to have but not mandatory. SGI have repeatedly sent the first three sets to Linus, without any response.
If any kernel distributor (including -ac) wants the individual XFS patches, just ask. SGI do not make them generally available because they are snapshots which are only created as required. The normal method of getting XFS is from CVS or as a release, both of which include all the patch sets.
Part of the design of IPv6 was "avoid lots of little class C adverts in the backbone routers". Each router only needs to hold local information, instead of the 40,000+ IPv4 entries in the top level routers. If you change provider you also change your IPv6 addresses, v6 has built in support for easy renumbering.