On Thu, Aug 14, 2003 at 11:37:59PM +0200, Buchan Milne wrote: > <quote who="Keld J�rn Simonsen"> > > In cooker drakx I had a problem with not being able to do ftp connect to > > get possible updates. > > There is no updates source for cooker. They normally add a directory for > the new release during RC time just to test.
Yes, I can imagine that. But I never had it working, and the guidelies I have seen in Danish actually recommends not to use this option, indicating that it never worked for those authors either. So I think it would be nice if this possibility can be tested now. And we are approaching beta 3 fast, nicht wahr? > > This is at the end of the installation process. > > The pb was also there in mdk 9.1 > > I can't comment on 9.1, some people said it worked, see below why I can't > test ... I tried it for the default - in the USA, and also for sunet.se - no luck. > > > - and it is annoying and a security > > breach, as this is a good opportunity for people to get patches, and > > apparrantly it does not work at all. > > > > I would also like my own mirror site, klid.dk be listed in the list of > > sites for updates. We do carry all updates. > > But a better option would be to allow the user to enter the updates site, > and even better to be able to save the option when saving an autoinst > floppy. Yes, that would be good possibilities too. I suggest something like: A list of sites to choose from as of now. If the install is a network install (via ftp or http) and the site is listed with an updates service, then give that site as the default, else give a default related to the locale or timezone. There should also be an option to enter it yourself, and a possibility to save your choices for autoinstall. > BTW, with the recent Blaster worm for Windows, it would be nice to be able > to punt "easy-to-setup, reliable, secure update mechanism", since that is > the only reason Windows machines on our campus were compromised. We have > an internal Windowsupdate mirror, but very few machines were configured > for it. > > Of course, and easy way to setup automated, unsupervised updates (ie via > cron) would also help ... Yes, that would be wonderful. In the light of recent Windows worms I think everything that we can do thru defaults during the installation to enhance security would be really appreciated. (Or: people will not really notice it as they are less likely to get damaged, but it could avoid horror stories for many mandrake users.) The updates site chosen as described before should of cause go into the mandrakeupdate media database as the update-source and some cron job should be activated, of cause after asking the user, but I think it should on by default (giving network access). And then some explanation about what is going on, "this enhances security, makes intrusion via broken packages harder, means that a job is run automatically every night to update all the packages ion the system..." Best regards keld
