Nothinman
Elite Member
- Sep 14, 2001
- 30,672
- 0
- 0
That is not true. udev is the following and it is taken directly from udev's site.
"Udev provides a dynamic /dev directory, and hooks userspace into kernel device events."
The kernel has the autodetectoin. Also there is dbus and hal to enhance the autodetection. The /sys directory is the main area where devices are shown, but they are not easy to use. udev is used to provide backwards compatibility and translates what it reads in /sys into human device nodes. Basically like syslog, udev listens to kernel events and fills up /dev.
It's possible that udev doesn't do the module loading itself and that it's a function of the initramfs scripts, I haven't been following lkml lately. But the kernel doesn't load modules. If you've got the drivers built in statically, then yes it'll initialize them with the rest of the kernel but that's non-standard these days.
Sure I can, but try telling a novice user to do that during the installation process and the user say huh. The Ubuntu installer or any distributions designed for novice Linux user should be require to include an option select either labels or UUID. I can not recommend Ubuntu to novice users because of this problem. Sabayon is better at this although their installation requires a DVD disc.
I never said tell a novice user to do that, I told you to do that because you don't like UUIDs. Most users will just let Ubuntu use UUIDs and have no problems. While I like options, I don't see the problem. Ubuntu decided that UUIDs make the most sense for them. If you don't like it you can always change it after the fact with very little work. But UUIDs work just fine despite your statement to the contrary.
Gentoo includes aids to do the steps of compiling. It still gives you what the developer provides for the desire program that you are installing. In Debian the steps to compile are proprietary. It requires additional attention to compile the program. Gentoo does not because it complies to BSD rules of compiling which are ./configure && make && make install. Debian requires make depend before make. That is proprietary.
I don't think the term proprietary means what you think it means.
Not all Debian packages build in the same manner so saying 'Debian requires make depend before make.' is a flat out lie. And if you use dpkg-buildpackage, like you're supposed to, you don't have to worry about each package's individual build steps. And that even assumes that you're building a Debian package from the source code, if you just want to build the code from upstream with autoconf and make you can do that just fine as well, nothing's stopping you from mucking up your system that way.
And once again, none of it is proprietary. It's all completely open source, not restricted by any trademarks or copyrights and can be used by anyone who wants.
USE flags does not change the compilation rules. They enforce what is require or in your cast to be consistent. Sure I can use LFS, but it takes more work because I have to figure out what library to install first and what will come second and so forth before a desire program to be installed. Then I have to list the capable features for each program by doing ./configure --help. Not all programs uses the names for each version they include in the program. Gentoo does all these checks, but they do checks on all dependencies and reverse dependencies then creates a list in chronological order based on what has the fewest dependencies and what has the longest dependencies.
They most certainly do change the compilation rules. You pick whether ALSA, GTK, etc is enabled in the build and thus the binary and it's dependencies are different. And Gentoo's ebuilds support 3rd party patches, http://en.gentoo-wiki.com/wiki/Writing_Ebuilds#Adding_a_patch so I guarantee there's at least 1 package in there that's not 100% identical to upstream as you seem to think.
Last time I checked Gentoo's package manager (term used very lightly) didn't check dependencies on removal which in my mind makes it completely worthless.
Yes they are called ebuilds. ebuilds are recipes or scripts to do the installation process. To install a program, emerge is used. To output a binary, you include -k on the same line to create a binary as you are installing. revdep-rebuild is used to double check the linking of libraries to the main program. If a library is re-installed or upgraded with different features, the program that relies on it will not load or will crash.
I.e. it's an ugly hack required because they don't have a real package management system. If I install an updated package that requires newer versions of it's dependencies those dependencies should be updated as well. Doing otherwise is just plain stupid.
I rarely do software upgrades when it upgrades software that are valuable to how my setup works. My coreutils is 7.5-r1 and why does it matter. It does not matter. I never seen any problem relating to coreutils. All problems I have seen is when people uses the latest software release and/or improper settings with the config files. Gentoo goes with what is stable for production systems. Then you compare to me based on your unstable release.
I just picked coreutils because it's something I knew you had to have installed. The fact that you're adverse to upgrading further enforces that Gentoo's package management is crap. Minor updates like that should be stupid simple to install, like they are in Debian. Gentoo and stable are virtually antonyms.
I choose to run sid/unstable on my workstations because it's a rolling release and I never have to worry about major upgrades. I install whatever updates are available every few days and I always have the latest packages available. Obviously, For a server I would run stable and only apply security updates.
BTW, I suggested something that could be used for a server, but everybody here went on their high horse and bitched. It seems in this forum that everybody does this to every new comer. It shows how congested and cruel the computer industry is, so this one of the reason why I am not in it.
Because it was probably the worst suggestion possible. Gentoo's only real use is as an example of what not to do with a Linux distribution.
None of my posts were directed at you personally or even cruel, but if you can't take some criticism and debate it's probably a good thing that you're not in the computer industry.