Well, stupid me. makewhatis is already a cron job. Didn't notice until I
finished the install and actually looked.
But Ron still had a point, it should be run during the installation process,
or on the first boot after the installation.
Don Head
Linux Mentor
[EMAIL PROTECTED]
[AIM - Don Wave][ICQ - 18804935]
[IRC - EFnet, #WaveTech, Don-Wave]
-----Original Message-----
From: Don Head [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 27, 1999 7:27 PM
To: '[EMAIL PROTECTED]'; Mandrake Cooker
Subject: RE: [Cooker] updatedb and makewhatis missing from install!
Running them at the end of the install, or on the first bootup after an
install, sounds like a winning plan.
I would also consider them eligable for a weekly or monthly cron job,
installed by default (if the software packages are installed). In my 6
years with Linux, I didn't know these existed until a few months ago. I'm
sure many other people don't know, especially newbies. Having the updating
of these databases automated on a regular basis would make things a little
easier.
Don Head
Linux Mentor
[EMAIL PROTECTED]
[AIM - Don Wave][ICQ - 18804935]
[IRC - EFnet, #WaveTech, Don-Wave]
-----Original Message-----
From: Ron Stodden [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 27, 1999 7:03 PM
To: Mandrake Cooker
Subject: [Cooker] updatedb and makewhatis missing from install!
Sirs,
The new graphical install (just like all its predecessors) continues to omit
the necessary final step of running updatedb and makewhatis.
Until such time as these are run, the 'locate'. 'whatis' and 'apropos'
commands function but produce no results, and, double whammy, they do not
produce any complaint that their databases have not been set up.
This is extremely misleading, deceptive, and abusive to the new user.
This should be added as a final step for all modes of the install, with
its own LED at the bottom of the left column.
--
Regards,
Ron. [AU] - sent by Linux.
