Bug#475958: where to post the updated procedure ?

2008-10-19 Thread W. Martin Borgert
On 2008-10-18 16:45, Giovanni Rapagnani wrote: you can find in attachment the patch to apply to manuals/branches/release-notes/lenny/en/upgrading.dbk rev.5421 in order to include the corrections proposed by Andrei Popescu. OK, your changes are now in rev. 5422. Many thanks! (Btw. for some

Bug#475958: where to post the updated procedure ?

2008-10-18 Thread Giovanni Rapagnani
Dear Martin, On 17/10/08 00:38, W. Martin Borgert wrote: I will put the current text into the release notes subversion archive in the next 12 hours. You could then post diffs to the debian-doc mailing list or to the BTS. Is this OK for you? you can find in attachment the patch to apply to

Processed: Re: Bug#475958: where to post the updated procedure ?

2008-10-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tags 475958 +patch Bug#475958: document procedure to recover from /dev/hda became /dev/sda boot failure Tags were: patch Tags added: patch tags 475958 +pending Bug#475958: document procedure to recover from /dev/hda became /dev/sda boot failure Tags

Bug#475958: where to post the updated procedure ?

2008-10-17 Thread W. Martin Borgert
tags 475958 +patch tags 475958 +pending thanks On 2008-10-17 00:38, W. Martin Borgert wrote: Btw. if you not have done this: Please state explicitly that you allow the distribution of your text under the terms of the GNU General Public License version 2. Or, if you prefer, say under any

Bug#475958: where to post the updated procedure ?

2008-10-16 Thread Giovanni Rapagnani
3. If this solution worked. Login to your system, make a backup of the '/boot/grub/menu.lst' file. Then generate a new '/boot/grub/menu.lst' by issuing with root privileges the command: update-grub Running update-grub before doing any changes to menu.lst is useless. 4. Edit

Bug#475958: where to post the updated procedure ?

2008-10-16 Thread W. Martin Borgert
On 2008-10-16 21:15, Giovanni Rapagnani wrote: Where is the better place to send the updated procedure ? I don't know wheter it is a good think to post this very long procedure to the BTS every time an update occurs. I will put the current text into the release notes subversion archive in