On Saturday 27 May 2006 22:39, Orn E. Hansen wrote:
Laugardaginn 27 maí 2006 11:58 skrifaði Per Jessen:
If it is truly redundant, which other function is doing the same thing? If you think the function is superfluous, just remove it.
I know I can remove it, it's not the point. The point is, whenever I update the system, they're just gonna return.
No, findutils-locate is something you installed manually and explicitly. It is not installed by default. It was before, it isn't now.
But, as we are talking about SUSE Linux, I don't believe there is a tickbox during installation that clearly says "For server use" or "For desktop use" - so SUSE should try to cover most requirements.
The latest "ideology" is to have A) Server, known as Enterprise Linux, B) Desktop environment, and C) Development environment.
On platform A, yes some of these functions may be non-reduntant. On B, they're useless. People will shutoff their machines when not using them, a few will have them up, to avoid going through long "startup" procedures. Which is another reason for "dump state to disk" shutdown. C) A "maybe".
The batch processing is an old reduntant feature, and I feel they should be put into a YaST module, where the packages "suggest" cron jobs, and a user selects which he thinks would benefit him. Of course, that's my opinion on the matter.
You seem to have trouble with the definitions of the words "useless" and "redundant". "useless" means literally "without use". It doesn't mean "Orn E Hansen has no use for it". cron is a fully justified feature on any system. And yes, there is even scheduled processing in windows "redundant" means "more than one thing in place for the same feature". For example RAID is redundant storage, as it stores the same thing on more than one disk (at least RAID 1 does) Batch processing is a term derived from the old punch cards, when the operator would put in a whole "batch" of them for processing, instead of putting in one job at a time. This sense doesn't exist today, since any computer will work on multiple "jobs" at any one time. cron is not batch processing. cron is scheduled processing. It has a use on any type of system, server or desktop or whatever.