You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article What would you like to see changed in Debian?:

#1 Re: What would you like to see changed in Debian? Posted by Anonymous (213.164.xx.xx) on Tue 8 Nov 2005 at 15:02 Debian Stable is stable because it is well tested, however bugs do get in. For example, bind9 has an annoying bug when not used with a forwarder. A four second delay is present if the server is on an ipv4 only network. Judging by past bug reports, this bug will be closed without a fix. RHEL on the other hand tends to fix these kind of things (in fact they did) AS WELL as providing security updates, which is what Debian tends to do. Debian needs a time-based release schedule to enable businesses to plan. The current "Use Debian" rule falls flat on its face as soon as you mix Stable and testing/whatever repos. A time-based release schedule would help to reduce this. "Test on testing, release when the platform is declared stable". Apt updates need to be signed, but this is being addressed. Secure by default would be good too. The default permissions on /root/ are ridiculous, as are /home/* (yes this can be configured, but only for adduser not useradd). Hostnames shouldn't be intertwined with config files. $(hostname) should either change /etc/hostname and /etc/motd, etc, or these files should be generated at boot. Web apps should be in /var/www/ to allow proper lockdown, not hidden away in /usr/share. php safe mode should be default.

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account