From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12635 invoked by uid 1002); 4 Nov 2003 23:06:47 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 26496 invoked from network); 4 Nov 2003 23:06:46 -0000 From: Steven Elling To: gentoo-dev@gentoo.org Date: Tue, 4 Nov 2003 17:06:38 -0600 User-Agent: KMail/1.5.4 References: <3FA5AF6F.5030501@codewordt.co.uk> <3FA5B6EA.8050901@mcve.com> In-Reply-To: <3FA5B6EA.8050901@mcve.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311041706.38185.ellings@kcnet.com> Subject: Re: [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email) X-Archives-Salt: 8e8897c7-eec2-44f1-b9f0-20e2e7e0c450 X-Archives-Hash: 724d613f4c6c9fa5ea0c09d21d316965 On Sunday 02 November 2003 20:01, Brad House wrote: > Commenting below: > >> -------------------------------- > >> Scenario 1: slocate and updatedb > >> -------------------------------- > >> > >> 1) Remove slocate from base system > >> 2) Remove makewhatis from daily cron duties > >> 3) Remove updatedb from daily cron duties > >> > >> I'm probably not alone in the fact that I never use slocate and given > >> fixed location of package files and other files in gentoo finding > >> things is easier than other distros especially given qpkg -l and > >> etcat -f. > > I do not agree with removing this stuff. I think it should be default. > This is basic stuff that I've seen every other distro do as well, and > I would consider this to be standardized. Though maybe what I would > recommend doing is adding documentation in the install guide that > will allow you to prevent this from being added to the cron, or > removing from the cron. For those people who obviously don't know > how to remove a cron job without complaining. I think the Gentoo team should consider giving the user a way of configuring packages to not install certain cron jobs upon install. For instance, I have a Tecra 8000 laptop that I use every once in a while. After the laptop completes booting, I cannot use it for 30 minutes to a hour because the makewhatis and updatedb (or slocate) cron jobs kick off after booting and drag the system to a crawl. And yes, I know I can just remove the cron jobs but by the time I'm done with the laptop I forget to remove them. Also, the cron jobs will get installed again when their packages are upgraded. Better yet. Why not do some magic in portage to run makewhatis and updatedb automagically after a world or system update -- maybe as a FEATURES setting -- and remove the cron jobs altogether. After all, 90% - 99% of the time files and man pages are only added to Gentoo systems when emerging packages (Hmm. deja-Vu). I think it is pointless to run programs to update databases that don't need it, which is for the most part the current configuration. Note, Gentoo isn't the only distro using package management tools that does this. -- gentoo-dev@gentoo.org mailing list