Re: [Cooker] installation and errata
On Sat, Jul 19, 2003 at 12:58:07AM +0200, Buchan Milne wrote: On Sat, 19 Jul 2003, Olivier Blin wrote: Hi Would it be possible to show the errata url at the beginning of the installation ? It would have been useful for Mandrake 9.1 users with more than 1GB of memory. Today, I've helped a new user that didn't know why the installation hanged. The errata url is showed at the end of Mandrake 9.1 installation, so he couldn't know that the problem was the big amount of memory. If the errata url was showed at the beginning of the installation, he could have found it himself ... Another way of doing things was to early on in the install process to ask whether errata should be installed, that is, before installing all the packages. That would mean that errors in the distribution could be remedied. I had an error with the drakx install script that it was in the wrong charset, this was highly annoying - if the script could go out and ask if errata should be applied very early then errors like these could be avoided. And it would save quite some time in a network install if you do not need to first download the erroneous packages and then the coorections. best regards Keld
Re: [Cooker] installation and errata
On Sun, 20 Jul 2003, Keld [iso-8859-1] Jørn Simonsen wrote: Another way of doing things was to early on in the install process to ask whether errata should be installed, that is, before installing all the packages. That would mean that errors in the distribution could be remedied. I had an error with the drakx install script that it was in the wrong charset, this was highly annoying - if the script could go out and ask if errata should be applied very early then errors like these could be avoided. Aren't these usually addressed by patch floppy images? You image a floppy, boot the installation disk, type 'patch' at the syslinux prompt, and put the floppy in later. And it would save quite some time in a network install if you do not need to first download the erroneous packages and then the coorections. Of course, it would also be useful if you could specify the updates mirror to use, or if it would also check the mirror you are installing from for the standard updates location (since that is probably the nearest/fastest mirror anyway). Regards, Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
Re: [Cooker] installation and errata
On Sun, Jul 20, 2003 at 12:40:31PM +0200, Buchan Milne wrote: On Sun, 20 Jul 2003, Keld [iso-8859-1] Jørn Simonsen wrote: Another way of doing things was to early on in the install process to ask whether errata should be installed, that is, before installing all the packages. That would mean that errors in the distribution could be remedied. I had an error with the drakx install script that it was in the wrong charset, this was highly annoying - if the script could go out and ask if errata should be applied very early then errors like these could be avoided. Aren't these usually addressed by patch floppy images? You image a floppy, boot the installation disk, type 'patch' at the syslinux prompt, and put the floppy in later. Yes, that is true, but it would be more convenient if there was a possibility to also use the network for this. I do not think the patch possibility is well known, at least not for newbies, and it is cumbersome to make the patch floppy, and even to disseminate the information that a patch is available. And it would save quite some time in a network install if you do not need to first download the erroneous packages and then the coorections. Of course, it would also be useful if you could specify the updates mirror to use, or if it would also check the mirror you are installing from for the standard updates location (since that is probably the nearest/fastest mirror anyway). Yes, it would be nice to have the information on updates be pushed to the users. I am advocating for a secure system that is easy to install even for newbies, and automatic updating to fix security patches and such is important. Having the current install site as the default would be fine, or some mirror dependent on the languagei chosen would also be good. best regards keld
Re: [Cooker] installation and errata
On Sunday 20 July 2003 09:15 am, Keld Jørn Simonsen wrote: On Sun, Jul 20, 2003 at 12:40:31PM +0200, Buchan Milne wrote: Aren't these usually addressed by patch floppy images? You image a floppy, boot the installation disk, type 'patch' at the syslinux prompt, and put the floppy in later. Yes, that is true, but it would be more convenient if there was a possibility to also use the network for this. I do not think the patch possibility is well known, at least not for newbies, and it is cumbersome to make the patch floppy, and even to disseminate the information that a patch is available. I have had a machine that needed three of the errata patches at once. I never did figure out how to apply more than one per install when all the patch files are named patch.pl. -- /g Outside of a dog, a man's best friend is a book, inside a dog it's too dark to read -Groucho Marx
Re: [Cooker] installation and errata
B == Buchan Milne [EMAIL PROTECTED] writes: B Maybe the syslinux boot screen should tell the user to read the B docs if anything goes wrong? Or is it wrong to expect a user to B read instructions nowadays? It's likely sufficient to mention where the docs are located and would be good ettiquette to note which of the core install docs have changed since the previous release. -- Gary Lawrence Murphy [EMAIL PROTECTED]: office voice/fax: 01 519 4222723 Business Advantage through Community Software - http://teledyn.com what I need is a job that doesn't interfere with my work -gary murphy
Re: [Cooker] installation and errata
On Sat, 19 Jul 2003, Olivier Blin wrote: Hi Would it be possible to show the errata url at the beginning of the installation ? It would have been useful for Mandrake 9.1 users with more than 1GB of memory. Today, I've helped a new user that didn't know why the installation hanged. The errata url is showed at the end of Mandrake 9.1 installation, so he couldn't know that the problem was the big amount of memory. If the errata url was showed at the beginning of the installation, he could have found it himself ... This would have to be on the syslinux splash screen? AFAIK, with the 1GB bug, you don't really seen anything but that? Of course, the errata site *is* listed in the installation instructions, easily accessible on the CD, but who would think to look there ;-). Maybe the syslinux boot screen should tell the user to read the docs if anything goes wrong? Or is it wrong to expect a user to read instructions nowadays? Regards, Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
[Cooker] installation and errata
Hi Would it be possible to show the errata url at the beginning of the installation ? It would have been useful for Mandrake 9.1 users with more than 1GB of memory. Today, I've helped a new user that didn't know why the installation hanged. The errata url is showed at the end of Mandrake 9.1 installation, so he couldn't know that the problem was the big amount of memory. If the errata url was showed at the beginning of the installation, he could have found it himself ... -- Olivier Blin
