similar to: [RFC] Controlling the auto-route setting behaviour of the kernel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello! I have a problem with a duplicate route entry, when using a pre-installed route and automatic take-over by the "heartbeat" daemon, which adds an address and the kernel adds an route automatically. Maybe anyone has an explanation... > ip addr 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue inet 127.0.0.1/8 scope host lo

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to be able to use kerberos for samba authentication from linux and windows, without having to create a domain/ad. From what I've read and seen, native kerberos authentication only works for windows clients inside a active directory context, while pam authentication only works with unencrypted passwords which aren't supported by

Hi, I compiled drm & xf86-video-nouveau to test nouveau yesterday -- the X server couldn't start. Today, Telek pointed me to drm/linux-core/drm_pciids.h, where I added my card. This made nouveau detect my card, and the xerver started successfully. I didn't test further -- for example I didn't compile the mesa nouveau code to enable 3D. So what should I test ? Snark PS1:

Hi folks, i spent my whole day trying to set up my linux router using load balancing with multiple uplinks. I mainly focused on the nano howto, but somewhere I have a big mistake within my head. Basically the load-balancing is working, but not on a per-connection basis - just on a per packet basis. Practically this is not usable of course <g> But as far as I understood it should work..

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.samba.org/archive/samba/attachments/20080826/7ffc52c8/signature.bin