Okay I have just modified the file.  Basically I renamed it so that it no 
longer has the ia64 in the filename and added the line wrap which Thomas 
suggested.

If nobody objects, I will also modify the release-notes.tex and simply wipe out 
the whole thing regard RHEL 3 and tell the user to read the README.RHAS3.txt 
file found in the source tarball.  In that case we only need to update one file.

What do you guys think?

Alternatively, I can copy the contents of README.RHAS3.txt to the release notes 
and simply delete that file from SVN.

Cheers,

Bernard

P.S. How goes RHEL 3 testing on i386/Itanium?

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Thomas Naughton
> Sent: Tuesday, December 14, 2004 13:33
> To: Fernando Laudares Camargos
> Cc: OSCAR-DEVEL
> Subject: Re: [Oscar-devel] README.RHAS3.iA64 (final) and 
> elilo problems
> 
> Hello all,
> 
> Sorry to be a bit anal-retentive on this text but on the long 
> lines, it might help to include the "\" (line wrap) character 
> in the examples since some users might type the commands literally.
> 
> Just a suggestions,
> --tjn
> 
> PS  Glad to see others notice these things too, i.e., <= 79 
> column lines!
> 
>   
> ______________________________________________________________
> ___________
>    Thomas Naughton                                      
> [EMAIL PROTECTED]
>    Research Associate                                   (865) 576-4184
> 
> 
> On Tue, 14 Dec 2004, Fernando Laudares Camargos wrote:
> 
> > Hello Bernard, David,
> >
> >       I formated the README.RHAS3.IA64 to a maximum of 79 column 
> > lines, renamed and updated it with Bernard's modifications. I kept 
> > ia64 and the
> > Intel(R) SR870BH2 tags out of the title.
> >       I don't known about the consistency of this README 
> and the docs, 
> > so I won't commit those changes to the branch and am sending it 
> > attached (as it'is a small txt).
> >       Cheers,
> >              Fernando
> >
> > Bernard Li a �crit :
> >> This README is getting more and more generic - perhaps we 
> should take 
> >> out .ia64 and the Intel(R) SR870BH2 tag?
> >> 
> >> Also, shouldn't this README be kept consistent with the 
> documentation?
> >> 
> >> Cheers,
> >> 
> >> Bernard
> >> 
> >> 
> >>> -----Original Message-----
> >>> From: Lombard, David N [mailto:[EMAIL PROTECTED] Sent: 
> >>> Tuesday, December 14, 2004 9:45
> >>> To: Bernard Li; OSCAR-DEVEL
> >>> Subject: RE: [Oscar-devel] README.RHAS3.iA64 (final) and elilo 
> >>> problems
> >>> 
> >>> From: Bernard Li;  Monday, December 13, 2004 3:57 PM
> >>> 
> >>>> Hey Fernando:
> >>>> 
> >>>> Looks good, I just got 2 questions:
> >>>> 
> >>>> 1) mysql-server
> >>>>  ------------
> >>>> 
> >>>> You will need to obtain a mysql-server rpm and put it into
> >>> 
> >>> /tftpboot/rpm
> >>> 
> >>>> before starting the OSCAR Wizard. The easiest way is to get the 
> >>>> SRPM
> >>> 
> >>> and
> >>> 
> >>>> rebuild,
> >>>> 
> >>>>   rpmbuild --rebuild mysql-3.23.58-1.src.rpm
> >>>>   cp /usr/src/redhat/RPMS/ia64/mysql-server-3.23.58-1.ia64.rpm
> >>>> /tftpboot/rpm
> >>>> 
> >>>> If you can't get that SRPM, make sure you also save the 
> other RPMS,
> >>> 
> >>> e.g.,
> >>> 
> >>>>   rpmbuild --rebuild mysql-3.23.58-2.3.src.rpm
> >>>>   cp /usr/src/redhat/RPMS/ia64/mysql*-3.23.58-1.ia64.rpm
> >>> 
> >>> /tftpboot/rpm
> >>> 
> >>>> - I am not sure what you mean in the second part...  how come the
> >>> 
> >>> src.rpm
> >>> 
> >>>> file versions are different?  Are you saying that the top one is 
> >>>> the recommended version and if you can't find that 
> specific version 
> >>>> make
> >>> 
> >>> sure
> >>> 
> >>>> that the other support RPM files are included in
> >>> 
> >>> /tftpboot/rpm as well?
> >>> 
> >>>> But how come the version #s are different in the second part
> >>> 
> >>> (3.23.58-2.3
> >>> 
> >>>> first line vs 3.23.58-1 second line).
> >>> 
> >>> I wrote that bit.  So, the version provided by RH is 
> 3.23.58-1.  If 
> >>> you go the Internet, you might find, say, 3.23.58-2.3.  
> This is fine 
> >>> if and only if you also build the other mysql rpms.  That is, you 
> >>> can't mix the mysql-3.23.58-1.arch.rpm w/ 
> mysql-server-3.23.58-2.3.arch.rpm.
> >>> 
> >>> So, should the second sentence say:
> >>> 
> >>>  If you can't get the 3.23.58-1 source rpm, you must save 
> all the  
> >>> RPMs when you build the mysql-server, that is, all mysql 
> versions  
> >>> must be consistent.  For example, you could do
> >>> 
> >>> Is this better?  If not, can you suggest some changes?
> >>> 
> >>> --
> >>> David N. Lombard
> >>> 
> >>> My comments represent my opinions, not those of Intel Corporation.
> >>> 
> >> 
> >> 
> >> 
> >> -------------------------------------------------------
> >> SF email is sponsored by - The IT Product Guide Read 
> honest & candid 
> >> reviews on hundreds of IT Products from real users.
> >> Discover which products truly live up to the hype. Start 
> reading now. 
> >> http://productguide.itmanagersjournal.com/
> >> _______________________________________________
> >> Oscar-devel mailing list
> >> [EMAIL PROTECTED]
> >> https://lists.sourceforge.net/lists/listinfo/oscar-devel
> >
> > --
> > Fernando Laudares Camargos
> >
> >      R�volution Linux       http://www.revolutionlinux.com 
> > ---------------------------------------
> > * Tout opinion et prise de position exprim�e dans ce 
> message est celle 
> > de son auteur et pas n�cessairement celle de R�volution Linux.
> > ** Any views and opinion presented in this e-mail are 
> solely those of 
> > the author and do not necessarily represent those of 
> R�volution Linux.
> >
> >
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to