I am running debian amd64 and wondering what would be to integrate a
block list and iptables. I am thinking of using block lists similar to
this http://list.iblocklist.com/?list=bt_spyware. When I tried importing
one such block list after parsing it with the script list below I get
the following error "iptables: memory allocation problem"

BLOCKLIST="/etc/blocklist.gz"
IPTABLES="/sbin/iptables"
SED="/bin/sed"

while read line
do
ip_range=`echo -n $line | $SED -e 's/.*:\(.*\)-\(.*\)/\1-\2/'`;
$IPTABLES --append INPUT --match iprange --src-range $ip_range
--jump DROP
$IPTABLES --append OUTPUT --match iprange --dst-range $ip_range
--jump DROP
done < <(zcat ${BLOCKLIST} | iconv -f latin1 -t utf-8 - | dos2unix)

I feel that this because of the large number of rules that are being
created. My question would be what would be a good way to block large
number of ip ranges with iptables.

Hi all,

I've just had a new server built and installed in a remote datacenter.
It's a Xeon (L5410) running AMD64, with an Adaptec 5805 8-port RAID
card, running 8 SATA 2.5" drives in RAID10. I believe the driver is aacraid.

Now all of this is very nice, but there's something that has been
bugging me for a while now: How do you tell when one of those drives
goes bad and needs to be replaced? I assume something gets written to
/var/log/messages, but what exactly do I look out for?

I have tried logcheck in the past, but it tends to be very annoying,
throwing up way too many warnings, which necessitates almost constant
tweaking of the filters and rules to try to reduce the noise. It was
irritating, so I stopped using it.

All I want is to know when a drive went bad. All the info out there on
the Web is increasingly useless, since a lot of it is out of date from
2004 or before.

I know that there is an Adaptec RAID management tool in the Debian
repository, named dpt-i2o-raidutils, but this is not an i2o device so I
assume it doesn't apply here.

"
Matteo Vescovi wrote:

for me?

Are you nuts? An AMD image for an INTEL CPU?

Olli
"

Um es auswendig zu lernen, benutzen Sie so diese Methode.

I have an Intel Core2Duo Processor. Which Debian is the correct one for
me? The AMD64 or the ia64?

Thanks
Friedrich

Hello again,

I've spent most of the day trying to get this format right.
Would somebody be so kind as to look at it for me and advise what will
immediately become blazingly obvious?
Aptitude advises that the problem is in line 5 and I believe it because
aptitude is smarter than I am.
Wisdom comes with age and I'm not quite sixty yet.

I've moved things around until I'm giddy and posting the answer back to
the list is fine as, in the interim, I've cleared up the backlog of
10,000 emails.
Regards and thanks,

David Palmer.

# deb cdrom:[Debian GNU/Linux 4.0 r4 _Etch_ - Official amd64 DVD Binary-1 20080726-23:51]/ etch contrib main

deb http://ftp.au.debian.org/debian stable main contrib non-free

deb http://ftp.au.debian.org/debian dists/stable-updates/

deb http://security.debian.org/ etch/updates main contrib non-free

Having a problem - with two different releases, now, 4.0r3 and 4.0r4, on
installation.

For some reason the installer no longer includes John Hasler's pppconfig
package (although plenty of attention is given to pppoe), setserial
isn't included in the base config to assist with modem port detection,
so consequently, there's no access to a mirror and the only thing that
ends up in the sources.list file is the cdrom path.

I could probably figure things out but I'm a bit doubtful on the syntax
employed when specifying the paths in the /etc/apt/sources.list edit.

I've searched everywhere fron Martin Kraft's book, to ' Linux Rute
User's Tutorial and Exposition', the Debian site - including the amd64
installation manual, man pages and google.....amongst others, but I can
find no hard and fast specification as to whether the 'amd64' qualifier
should be included in the path and if so, how it should be qualified,
i.e. associated with forward slashes; underscores or hyphens.

Could anybody point me to a reliable source, please?

I'll have to read the answer in the archives as I've been off-line for a
while and I've got about 10,000 emails backed up on me.
With spam training on a new mail client, that's a whole separate issue

Hi, I'm having some issues trying to install etch from netinstall.

The netinstall is:
debian-40r4a-amd64-netinst.iso

Processors Information
------------------------------------------------------------------------------------
Processor 1 (ID = 0)
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name AMD Athlon 64 X2 4000+
Codename Brisbane
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
Package Socket AM2 (940)
CPUID F.B.1
Extended CPUID F.6B

Chipset
------------------------------------------------------------------------------

Hi all,

as there are many java versions installable, what is the best one to use in
amd64-systems ? What are the differences ? I saw gcj, gij, gdk, java. Can
someone tell me, which should be used ? Ia ma very confused.
Update-alternatives is giving me these choices:

There are 8 alternatives which provide `java'.

Selection Alternative
-----------------------------------------------
1 /usr/bin/gij-4.1
2 /usr/lib/jvm/ia32-java-6-sun/jre/bin/java
3 /usr/lib/jvm/java-gcj/jre/bin/java
4 /usr/bin/gij-4.3
* 5 /usr/lib/jvm/java-6-sun/jre/bin/java
6 /usr/bin/gij-4.2
7 /usr/lib/jvm/ia32-java-1.5.0-sun/jre/bin/java
+ 8 /usr/lib/jvm/java-6-openjdk/jre/bin/java

Press enter to keep the default[*], or type selection number:

I choose 5. What is this "+"-sign meaning ?

Questions, questions, questions....

Hy,

I tryed to configure Samba as a Domain controller but I just can't make it work.
I still get wierd errors in in logs as:
[2008/09/16 12:34:25, 0] auth/auth_util.c:create_builtin_users(751)
create_builtin_users: Failed to create Users
[2008/09/16 13:06:27, 0] auth/auth_util.c:create_builtin_administrators(785)
create_builtin_administrators: Failed to create Administrators
[2008/09/16 13:06:27, 0] auth/auth_util.c:create_builtin_users(751)
create_builtin_users: Failed to create Users
[2008/09/16 13:06:28, 0] auth/auth_util.c:create_builtin_administrators(785)
create_builtin_administrators: Failed to create Administrators
[2008/09/16 13:06:28, 0] auth/auth_util.c:create_builtin_users(751)
create_builtin_users: Failed to create Users

I googled, but I found just other users with the same issues, and no answers to those posts.

My SMB.conf looks like:

[global]
workgroup = SOFTRUST
server string = server %%v
interfaces = 192.168.1.0/24, eth1
passdb backend = tdbsam
passwd program = /usr/bin/passwd %%u
passwd...

Hi all,

I have a little problem with sysklogd + kdm. I do not know, if this is pure
amd64-related, but I found it only on my amd64-machine.

Problem: sysklogd is using tty7 for some stdout. Thus kdm is thinking, the
console is used and starts on tty9. But it should be on tty7 (as normal in
Debian).

Question: How can I force sysklogd not to send stdout to the console or to
another console (for example tty9), so it is free to use for kdm.

I searched all configurations and found no settings. This behaviour appeared
after an upgrade, although I changed nothing. Weired things......

Thans for any help.

regards

Hans