-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Fri, Jun 17, 2005 at 02:33:47PM -0400, Ugo Bellavance wrote:

Rodrigo Barbosa wrote:

...

Do we have the ntfs kernel module (readyonly is ok) prebuilt avaliable anywhere for the stock CentOS 4.(0|1) kernel ?

Any other options ? Maybe some userspace tool.

http://linux-ntfs.sourceforge.net/

Ahhh, they even have a prebuilt module for 4.1.

Thank you. I didn't even check that URL because I thought I would only find ntfsprogs there. Serves me well.

- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Fri, Jun 17, 2005 at 05:19:38PM -0500, Johnny Hughes wrote:

On Fri, 2005-06-17 at 15:42 -0300, Rodrigo Barbosa wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Fri, Jun 17, 2005 at 02:33:47PM -0400, Ugo Bellavance wrote:

...

Rodrigo Barbosa wrote:

...

Do we have the ntfs kernel module (readyonly is ok) prebuilt avaliable anywhere for the stock CentOS 4.(0|1) kernel ?

Any other options ? Maybe some userspace tool.

http://linux-ntfs.sourceforge.net/

Ahhh, they even have a prebuilt module for 4.1.

Thank you. I didn't even check that URL because I thought I would only find ntfsprogs there. Serves me well.

This is also built into the centosplus kernels.

http://mirror.centos.org/centos/4/centosplus

Yes, I noticed that. But I was trying first for just a module, so I could keep the stock kernel.

[]s

- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)

On Sun, 2005-06-19 at 02:17 +1200, Tom wrote:

Hi all.

does anyone know if this has been resolved?

Important Notice Users updating to CentOS 3.5 from CentOS 3.4 may experience a problem with /etc/named.conf reverting to the default state. This is due to a problem with the new caching-nameserver rpm provided with CentOS 3.5. If the problem does occur, it can be easily corrected by running the following command in a root shell:

mv /etc/named.conf /etc/named.conf.CENTOS35UPDATE;mv /etc/named.conf.rpmsave /etc/named.conf;/scripts/restartsrv_named

For more information, please refer to this thread on the cPanel Forums: http://forums.cpanel.net/showthread.php?p=191301#post191301 _______________________________________________

It has not been fixed, because it is the normal behavior for upgrading caching-nameserver.

RH has addressed this issue many times, here are some: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145244

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145094

RH says that people should not use the /etc/named.conf or any other files produced by caching-nameserver (or even use caching-nameserver) on a machine that also contains named primary zones and leave caching- nameserver installed.

Since it is the default behavior in RHEL is it also the default behavior in CentOS-3. It will probably never be changed.

If you have your zone files in /var/named, you can use the following script to produce another named.conf file The script will print the file to the screen, you can copy and paste it if you are satisfied with the results

Note : Run only if you have primary master name server

**************BEGIN SCRIPT************** #!/bin/bash

DIRECTORY="/var/named"

#Generate /etc/rndc.key file (if you already have one in /etc/rndc.key then just run the script as non root user) rndc-confgen -a

cat /etc/rndc.key echo -e "controls { \n\t inet 127.0.0.1 allow { localhost; } keys { "rndckey"; };\n};\n" if [ -f "$DIRECTORY/named.ca" ] then echo -e "zone "." {\n\ttype hint;\n\tfile "$DIRECTORY/named.ca";\n};\n\n" fi

for file in $DIRECTORY/*.db do if [ -f "$file" ] then zonename=${file%.db} echo -e "zone "$zonename" { \n\t type master; \n\t file "$file"; \n};\n" fi done **************END SCRIPT**************

Hope this will help

----- Original Message ----- From: "Tom" admin@homemachine.net To: "CentOS mailing list" centos@centos.org Sent: Saturday, June 18, 2005 5:17 PM Subject: [CentOS] named problem with cpanel

Hi all.

does anyone know if this has been resolved?

Important Notice Users updating to CentOS 3.5 from CentOS 3.4 may experience a problem with /etc/named.conf reverting to the default state. This is due to a problem with the new caching-nameserver rpm provided with CentOS 3.5. If the problem does occur, it can be easily corrected by running the following command in a root shell:

mv /etc/named.conf /etc/named.conf.CENTOS35UPDATE;mv /etc/named.conf.rpmsave /etc/named.conf;/scripts/restartsrv_named

For more information, please refer to this thread on the cPanel Forums: http://forums.cpanel.net/showthread.php?p=191301#post191301 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos