From s.ellis at fastmail.co.uk Sun Nov 7 10:49:42 2004 From: s.ellis at fastmail.co.uk (Stuart Ellis) Date: Sun, 07 Nov 2004 10:49:42 +0000 Subject: Installation Guide v 0.2 In-Reply-To: <1099121549.21313.11.camel@hermione.soho.bytebot.net> References: <20041026202541.1703.qmail@web8509.mail.in.yahoo.com> <1098921586.31505.207416086@webmail.messagingengine.com> <1099042340.4720.3.camel@anu.eridu> <1099121549.21313.11.camel@hermione.soho.bytebot.net> Message-ID: <1099824582.15813.208125634@webmail.messagingengine.com> On Sat, 30 Oct 2004 17:32:29 +1000, "Colin Charles" said: > On Fri, 2004-10-29 at 10:32 +0100, Paul Nasrat wrote: > > > > Unfortunately, it would probably take me as long to prepare a complete > > > set of bad screenshots as for somebody else with more experience to make > > > the good set. > > > > I'll get either myself or one of the installer team to do this for next > > week sometime. It is fairly straightforward with kickstart and: > > > > autostep --autoscreenshot > > Didn't do it that way, but I've got lots of screenshots that I took for > the book, that would be usable I'm sure: > > http://www.bytebot.net/universe/fedora/installation/ > > Happy usage. Thanks to you both for the offers. The structure is complete enough for screenshots to be dropped in whenever. I'm working on a couple of bits this weekend and will probably do another build after FC3 comes out. -- Stuart Ellis s.ellis at fastmail.co.uk From mjohnson at redhat.com Mon Nov 8 19:00:13 2004 From: mjohnson at redhat.com (Mark Johnson) Date: Mon, 08 Nov 2004 14:00:13 -0500 Subject: Re-using material from Red Hat Docs In-Reply-To: <1098660224.25361.207157082@webmail.messagingengine.com> References: <1098660224.25361.207157082@webmail.messagingengine.com> Message-ID: <418FC23D.2000204@redhat.com> Stuart Ellis wrote: > Would it be possible to re-use an exerpt in Fedora documentation without > a licencing problem ? Hi Stuart, I believe you would indeed run into a licensing problem using content from the Red Hat manuals. The only possible exception I can imagine would be if you included a snippet in quotes, complete with the proper attributions. I doubt that this is what you'd like to do, though. Sorry:-/ Cheers, Mark -- ---------------------------------------------------------- Mark Johnson OS Product Documentation Engineering, Red Hat, Inc. Tel: 919.754.4151 Fax: 919.754.3708 GPG fp: DBEA FA3C C46A 70B5 F120 568B 89D5 4F61 C07D E242 From s.ellis at fastmail.co.uk Mon Nov 8 20:42:30 2004 From: s.ellis at fastmail.co.uk (Stuart Ellis) Date: Mon, 08 Nov 2004 20:42:30 +0000 Subject: Re-using material from Red Hat Docs In-Reply-To: <418FC23D.2000204@redhat.com> References: <1098660224.25361.207157082@webmail.messagingengine.com> <418FC23D.2000204@redhat.com> Message-ID: <1099946550.4879.208222308@webmail.messagingengine.com> On Mon, 08 Nov 2004 14:00:13 -0500, "Mark Johnson" said: > Stuart Ellis wrote: > > > Would it be possible to re-use an exerpt in Fedora documentation without > > a licencing problem ? > > Hi Stuart, > > I believe you would indeed run into a licensing problem using content > from the > Red Hat manuals. The only possible exception I can imagine would be if > you > included a snippet in quotes, complete with the proper attributions. I > doubt > that this is what you'd like to do, though. Sorry:-/ Thanks for confirming that - I found the OPL a little tricky to interpret. The word exerpt was probably a bit misleading. The issue I've hit is that both kickstart and the anaconda boot prompt have many options - several pages worth for each, which as far as I know are only listed in OPL documentation (the Red Hat manuals and the text files installed in /usr/share/doc). The Table of Contents proposed for the (FDL licenced) Fedora Core Installation Guide specifies appendices for Kickstart and Additional Boot Options, which presumably would list exactly the same program options. Even if it wasn't just a copy and paste job, I guess that the result would be close enough to be "copying" in a legal sense. It is just a guess, because I don't know enough about this area. All comments gratefully received... -- Stuart Ellis s.ellis at fastmail.co.uk From pnasrat at redhat.com Thu Nov 11 22:17:45 2004 From: pnasrat at redhat.com (Paul Nasrat) Date: Thu, 11 Nov 2004 17:17:45 -0500 Subject: doc book wiki Message-ID: <1100211465.2753.31.camel@dhcp83-102.boston.redhat.com> Has anyone played with: http://doc-book.sourceforge.net/homepage/ Looks interesting. Paul From s.ellis at fastmail.co.uk Tue Nov 16 23:01:08 2004 From: s.ellis at fastmail.co.uk (Stuart Ellis) Date: Tue, 16 Nov 2004 23:01:08 +0000 Subject: Software Management Tutorial Message-ID: <1100646068.23249.208820711@webmail.messagingengine.com> Setting up FC3 this weekend I noticed that the Keeping Up to Date tutorial written for the FC2 version of yum, and is fairly terse. So I've written up a more comprehensive tutorial on up2date and yum. I think that this is complete (perhaps too complete ?), so I'm submitting it for review - HTML: http://www.se.clara.net/fedora/software-management-en/index.html DocBook: http://www.se.clara.net/fedora/software-management-0.1.tar.gz -- Stuart Ellis s.ellis at fastmail.co.uk From rahulsundaram at yahoo.co.in Tue Nov 16 23:18:36 2004 From: rahulsundaram at yahoo.co.in (Rahul Sundaram) Date: Tue, 16 Nov 2004 15:18:36 -0800 (PST) Subject: Software Management Tutorial In-Reply-To: <1100646068.23249.208820711@webmail.messagingengine.com> Message-ID: <20041116231836.81169.qmail@web8501.mail.in.yahoo.com> --- Stuart Ellis wrote: > Setting up FC3 this weekend I noticed that the > Keeping Up to Date > tutorial written for the FC2 version of yum, and is > fairly terse. So > I've written up a more comprehensive tutorial on > up2date and yum. this is nice. a few points provide screenshots wherever applicable. I would like the whole document filled with it to look like a tutorial you should explain old yum behavior too which doesnt have invidual repos and probably the advantages of this setup as a note explain yum remove and put a warning on rpm -ivh section not to force install packages unless they know what they are doing clearly. what happened to the installation guide btw. I was hoping it would be in the final form when fc3 was finished. if you arent revising it alteast push for its inclusion in the current form with screenshots so that we can revise it later on. the mailing lists are frequently filled with questions about installation and it would nice to just point them to the installation guide instead of answering the same stuff repeatedly. I have just lost count of how many times I have posted the release notes to the list. it has finally been added to the docs section. regards Rahul Sundaram ===== Regards Rahul Sundaram __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com From rahulsundaram at yahoo.co.in Tue Nov 16 23:18:42 2004 From: rahulsundaram at yahoo.co.in (Rahul Sundaram) Date: Tue, 16 Nov 2004 15:18:42 -0800 (PST) Subject: Software Management Tutorial In-Reply-To: <1100646068.23249.208820711@webmail.messagingengine.com> Message-ID: <20041116231842.66070.qmail@web8502.mail.in.yahoo.com> --- Stuart Ellis wrote: > Setting up FC3 this weekend I noticed that the > Keeping Up to Date > tutorial written for the FC2 version of yum, and is > fairly terse. So > I've written up a more comprehensive tutorial on > up2date and yum. this is nice. a few points provide screenshots wherever applicable. I would like the whole document filled with it to look like a tutorial you should explain old yum behavior too which doesnt have invidual repos and probably the advantages of this setup as a note explain yum remove and put a warning on rpm -ivh section not to force install packages unless they know what they are doing clearly. what happened to the installation guide btw. I was hoping it would be in the final form when fc3 was finished. if you arent revising it alteast push for its inclusion in the current form with screenshots so that we can revise it later on. the mailing lists are frequently filled with questions about installation and it would nice to just point them to the installation guide instead of answering the same stuff repeatedly. I have just lost count of how many times I have posted the release notes to the list. it has finally been added to the docs section. regards Rahul Sundaram ===== Regards Rahul Sundaram __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com From dmalcolm at redhat.com Wed Nov 17 21:59:16 2004 From: dmalcolm at redhat.com (David Malcolm) Date: Wed, 17 Nov 2004 16:59:16 -0500 Subject: Adding boilerplate errata/CVS instructions Message-ID: <1100728757.3803.16.camel@cassandra.boston.redhat.com> Attached is a file that supplies boilerplate instructions for reporting errors/patches with a document. Also attached is a patch to my Stateless Linux tutorial which pulls in the file and uses it, with the various sub-entities given sane definitions. You can see a usage of this file in an unofficial copy of that tutorial, located here: http://people.redhat.com/dmalcolm/stateless/stateless-linux-HOWTO- en/#errata-tip I propose adding the first file as "fedora-docs/common/errata-en.xml" Any thoughts/rewrites? Perhaps the heading should read "About This Document" instead? Dave Malcolm -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stateless-linux-errata.patch Type: text/x-patch Size: 2330 bytes Desc: not available URL: From kwade at redhat.com Thu Nov 18 00:39:06 2004 From: kwade at redhat.com (Karsten Wade) Date: Wed, 17 Nov 2004 16:39:06 -0800 Subject: Adding boilerplate errata/CVS instructions In-Reply-To: <1100728757.3803.16.camel@cassandra.boston.redhat.com> References: <1100728757.3803.16.camel@cassandra.boston.redhat.com> Message-ID: <1100738345.3619.3758.camel@erato.phig.org> On Wed, 2004-11-17 at 13:59, David Malcolm wrote: > Attached is a file that supplies boilerplate instructions for reporting > errors/patches with a document. This is a stellar idea, thanks! I suggest a few changes, new file attached. * Added a explaining how to obtain and format the URL from bugzilla/ * Some fill-column because I can't help myself. :) * Changed the code to match the current FDP style (flush left, on same line, not in block). > I propose adding the first file as "fedora-docs/common/errata-en.xml" Recommend an RFE bug report. Might also want to patch fedora-entities-en.xml to have it make the entity declaration: > Any thoughts/rewrites? Perhaps the heading should read "About This > Document" instead? Yes, that is more of an accurate title. Changed that in the attachment. ________________________________________________________________________ - Karsten -- Karsten Wade, RHCE, Tech Writer a lemon is just a melon in disguise http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmalcolm at redhat.com Thu Nov 18 20:45:07 2004 From: dmalcolm at redhat.com (David Malcolm) Date: Thu, 18 Nov 2004 15:45:07 -0500 Subject: Adding boilerplate errata/CVS instructions In-Reply-To: <1100738345.3619.3758.camel@erato.phig.org> References: <1100728757.3803.16.camel@cassandra.boston.redhat.com> <1100738345.3619.3758.camel@erato.phig.org> Message-ID: <1100810707.3803.52.camel@cassandra.boston.redhat.com> On Wed, 2004-11-17 at 16:39 -0800, Karsten Wade wrote: > On Wed, 2004-11-17 at 13:59, David Malcolm wrote: > > Attached is a file that supplies boilerplate instructions for reporting > > errors/patches with a document. > > This is a stellar idea, thanks! > > I suggest a few changes, new file attached. Thanks! > > * Added a explaining how to obtain and format the URL > from bugzilla/ Good idea. > > * Some fill-column because I can't help myself. :) Fair enough. > > * Changed the code to match the current FDP style (flush left, > on same line, not in block). OK > > > I propose adding the first file as "fedora-docs/common/errata-en.xml" > > Recommend an RFE bug report. Done, as this one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139931 Should this go on a tracker bug somewhere? > > Might also want to patch fedora-entities-en.xml to have it make the > entity declaration: > > Would doing this require that any files using fedora-entities-en.xml define the various entities referred to in errata-en.xml ? (and hence break all the existing docs, until they get fixed?) > > > Any thoughts/rewrites? Perhaps the heading should read "About This > > Document" instead? > > Yes, that is more of an accurate title. Changed that in the attachment. Perhaps the file should have a different name; perhaps "about-this-document-en.xml" ? > > ________________________________________________________________________ > - Karsten > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > http://www.redhat.com/mailman/listinfo/fedora-docs-list From kwade at redhat.com Fri Nov 19 00:26:31 2004 From: kwade at redhat.com (Karsten Wade) Date: Thu, 18 Nov 2004 16:26:31 -0800 Subject: Adding boilerplate errata/CVS instructions In-Reply-To: <1100810707.3803.52.camel@cassandra.boston.redhat.com> References: <1100728757.3803.16.camel@cassandra.boston.redhat.com> <1100738345.3619.3758.camel@erato.phig.org> <1100810707.3803.52.camel@cassandra.boston.redhat.com> Message-ID: <1100823990.3619.5323.camel@erato.phig.org> On Thu, 2004-11-18 at 12:45, David Malcolm wrote: > On Wed, 2004-11-17 at 16:39 -0800, Karsten Wade wrote: > > > > Done, as this one: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139931 > > Should this go on a tracker bug somewhere? I don't think there is one, just falls in the "all open fedora-docs bugs" category. > > Might also want to patch fedora-entities-en.xml to have it make the > > entity declaration: > > > > > > Would doing this require that any files using fedora-entities-en.xml > define the various entities referred to in errata-en.xml ? (and hence > break all the existing docs, until they get fixed?) Good question. I _think_ it would only come into play if explicitly called by the document. Here's a test. I added this to my fedora-entities-en.xml: then built a document without any error. It also validated: cd /home/kwade/Documents/projects/fedora/fedora-docs/selinux-apache/ nsgmls -wxml -s /home/kwade/lib/psgmlx-0.5/lib/xml.dcl selinux-apache-en.xml nsgmls:/home/kwade/lib/psgmlx-0.5/lib/xml.dcl:1:W: SGML declaration was not implied SGML validation finished at Thu Nov 18 16:24:42 FWIW, that's the way it normally appears when I validate (in Emacs using C-c C-v). > > > > > Any thoughts/rewrites? Perhaps the heading should read "About This > > > Document" instead? > > > > Yes, that is more of an accurate title. Changed that in the attachment. > > Perhaps the file should have a different name; perhaps > "about-this-document-en.xml" ? How about about-doc-en.xml? - Karsten -- Karsten Wade, RHCE, Tech Writer a lemon is just a melon in disguise http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 From dmalcolm at redhat.com Fri Nov 19 00:54:18 2004 From: dmalcolm at redhat.com (David Malcolm) Date: Thu, 18 Nov 2004 19:54:18 -0500 Subject: Adding boilerplate errata/CVS instructions In-Reply-To: <1100823990.3619.5323.camel@erato.phig.org> References: <1100728757.3803.16.camel@cassandra.boston.redhat.com> <1100738345.3619.3758.camel@erato.phig.org> <1100810707.3803.52.camel@cassandra.boston.redhat.com> <1100823990.3619.5323.camel@erato.phig.org> Message-ID: <1100825658.3803.90.camel@cassandra.boston.redhat.com> On Thu, 2004-11-18 at 16:26 -0800, Karsten Wade wrote: > On Thu, 2004-11-18 at 12:45, David Malcolm wrote: > > On Wed, 2004-11-17 at 16:39 -0800, Karsten Wade wrote: > > > > > > > Done, as this one: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139931 > > > > Should this go on a tracker bug somewhere? > > I don't think there is one, just falls in the "all open fedora-docs > bugs" category. > > > > Might also want to patch fedora-entities-en.xml to have it make the > > > entity declaration: > > > > > > > > > > Would doing this require that any files using fedora-entities-en.xml > > define the various entities referred to in errata-en.xml ? (and hence > > break all the existing docs, until they get fixed?) > > Good question. I _think_ it would only come into play if explicitly > called by the document. Here's a test. > > I added this to my fedora-entities-en.xml: > > > > then built a document without any error. > > It also validated: > > cd /home/kwade/Documents/projects/fedora/fedora-docs/selinux-apache/ > nsgmls -wxml -s /home/kwade/lib/psgmlx-0.5/lib/xml.dcl > selinux-apache-en.xml > nsgmls:/home/kwade/lib/psgmlx-0.5/lib/xml.dcl:1:W: SGML declaration was > not implied > > SGML validation finished at Thu Nov 18 16:24:42 > > FWIW, that's the way it normally appears when I validate (in Emacs using > C-c C-v). OK, great; good idea. Is xmllint happy with such a setup? If so, then the ABOUT-DOC-EN probably _should_ get added to the main entities file. > > > > > > > > Any thoughts/rewrites? Perhaps the heading should read "About This > > > > Document" instead? > > > > > > Yes, that is more of an accurate title. Changed that in the attachment. > > > > Perhaps the file should have a different name; perhaps > > "about-this-document-en.xml" ? > > How about about-doc-en.xml? Yes, that's much better. Maybe even "about-fedora-doc-en.xml", to make it clear that this relates to a Fedora doc? (as opposed to RHEL) Can I go ahead and commit this (assuming I have access rights)? Or should someone else on the list comment first? I'm just a lowly desktop developer :-) Dave From s.ellis at fastmail.co.uk Fri Nov 19 01:17:02 2004 From: s.ellis at fastmail.co.uk (Stuart Ellis) Date: Fri, 19 Nov 2004 01:17:02 +0000 Subject: Software Management Tutorial In-Reply-To: <20041116231842.66070.qmail@web8502.mail.in.yahoo.com> References: <20041116231842.66070.qmail@web8502.mail.in.yahoo.com> Message-ID: <1100827022.22406.209001315@webmail.messagingengine.com> On Tue, 16 Nov 2004 15:18:42 -0800 (PST), "Rahul Sundaram" said: > > this is nice. a few points > > provide screenshots wherever applicable. The general advice is actually to avoid screenshots wherever possible. I think that this may be to reduce maintenance. The Installation Guide is exceptional, AFAIK. > > you should explain old yum behavior too which doesnt > have invidual repos and probably the advantages of > this setup as a note I've now added notes about the older versions of yum to the configuration and repository sections. > explain yum remove and put a warning on rpm -ivh > section not to force install packages unless they know > what they are doing clearly. Good point - I've added the warning. What extra explanation do you feel is needed for yum remove ? > what happened to the installation guide btw. I was > hoping it would be in the final form when fc3 was > finished. Until recently the Installation Guide was really just a collection of chapters that I put into Bugzilla, several sections are unwritten or have outstanding FIXMEs. The issue is that the advice in the Guide must be good, so it has to be tested - particularly for things that can fail in complicated or dangerous ways like upgrades or partitioning. At the moment I need to check the text against the final release of FC3, integrate the screenshots provided by Colin Charles and tidy up various other bits before doing another build. After that, the sections relating to partitioning and RAID are probably the most critical missing pieces. I had to revise all my yum notes for FC3 final, so I thought that I'd put some more effort in and try to produce a proper guide. Hopefully this is now complete. > the mailing lists are > frequently filled with questions about installation > and it would nice to just point them to the > installation guide instead of answering the same stuff > repeatedly. I know what you mean. It was the experience of providing support on a forum that finally pushed me to start writing documentation. -- Stuart Ellis s.ellis at fastmail.co.uk From s.ellis at fastmail.co.uk Fri Nov 19 01:18:51 2004 From: s.ellis at fastmail.co.uk (Stuart Ellis) Date: Fri, 19 Nov 2004 01:18:51 +0000 Subject: Software Management Tutorial v 0.2 Message-ID: <1100827131.22489.209003972@webmail.messagingengine.com> HTML: http://www.se.clara.net/fedora/software-management-en/index.html DocBook: http://www.se.clara.net/fedora/software-management-0.2.tar.gz -- Stuart Ellis s.ellis at fastmail.co.uk From rahulsundaram at yahoo.co.in Fri Nov 19 02:27:49 2004 From: rahulsundaram at yahoo.co.in (Rahul Sundaram) Date: Thu, 18 Nov 2004 18:27:49 -0800 (PST) Subject: Software Management Tutorial In-Reply-To: <1100827022.22406.209001315@webmail.messagingengine.com> Message-ID: <20041119022749.79775.qmail@web8508.mail.in.yahoo.com> Hi > The general advice is actually to avoid screenshots > wherever possible. > I think that this may be to reduce maintenance. The > Installation Guide > is exceptional, AFAIK. in general we should favor end users over maintainers. can fedora docs teamt reconsider this advice. while it might be true for previous redhat or current redhat el releases, fedora aims are different and we should be more accomodating. > > Good point - I've added the warning. What extra > explanation do you feel > is needed for yum remove ? well yum remove as is the same for other operations asks for confirmation before doing removing the packages. Also unlike rpm -e, it can reverse resolve dependencies. You should be providing working examples of every command rather than simply stating them. add a note somewhere to refer to man pages and yum -h for more options and help > At the moment I need to check the text against the > final release of FC3, > integrate the screenshots provided by Colin Charles > and tidy up > various other bits before doing another build. > After that, the sections > relating to partitioning and RAID are probably the > most critical missing > pieces. I suggest you present the installation guide to the users mailing list with a warning that its in a draft stage and collect all feedback from the huge amount of newbies there. This will get you much better understanding of what users want from a guide like this . I suspect most of us in the docs have enough experience with this to actually put ourselves in a newbie perspective > > I had to revise all my yum notes for FC3 final, so I > thought that I'd > put some more effort in and try to produce a proper > guide. Hopefully > this is now complete. its a great start but probably requires a couple of revisions. a few more points Have a section to explain how to get rid of the alerts icon. Its a memory hog currently and is one of the FAQ's the section on managing up2date channels should mention that up2date can *use* both apt and yum repositories but not act as a general frontend for either of these commands 7. Authorizing Package Sources This section might have a few references to explain what gpg is(gnupg is the actual package) and also a warning against disabling gpg keys while letting the users know that there is a option to do so. "8.1. Automatic Updates" " There is no separate yum service. The command given above enables the yum control script in /etc/rc.d/init.d/. This control script activates the script /etc/cron.daily/yum.cron, so that the cron service will perform the system update as part of it's daily schedule." users typically dont care how this works. if you need to explain this please do so as note. the dummies series of book does this well. it has humour titles like "techno whizbang" or something like that which clearly gets the point across that this is not a required reading. You might want to add that cron is a task scheduler for Linux "yum provides MTA" this is actually a meta package and probably requires a explanation as note " The Website for the official Fedora Extras repositories is here: http://www.fedora.us/ " this is actually a temporary status(hopefully). You might want to link to http://fedora.redhat.com/participate/terminology.html "12. Adding Repositories as Package Sources" It would be useful to add that one of the advantages of the new format is that a new repository can be added as a rpm package. for example freshrpms does this. Also try adding a warning that users shouldnt mix random repositories together freshrpms and dags are not compatible with fedora.us and livna (I am not very sure of the exact details) " Do not use the options to override this dependency checking. Instead, use yum to find and install the packages needed to meet the dependency requirements." do not use the options to override dependancies unless you are an expert. Use yum or download the required packages manually. use rpmfind.net to find the package having the required dependancy if a package is not explicitly suggested "You will need to install the Development Tools group of packages on your system in order to compile software from source code." you might explain yum groupinstall and how to use the cds here. the warning can also add the information that compiling software from random untrusted sources are potentialy dangerous reminder: for more details users should read the man pages and do explain every command with live examples Try presenting the result to users list for more feedback note: This feedback might sound critical but I have been doing such tech reviews for LDP for sometime and its a good document regardless of this. Congrats regards Rahul Sundaram ===== Regards Rahul Sundaram __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com From rahulsundaram at yahoo.co.in Fri Nov 19 17:13:53 2004 From: rahulsundaram at yahoo.co.in (Rahul Sundaram) Date: Fri, 19 Nov 2004 09:13:53 -0800 (PST) Subject: more feedback on the updates guide Message-ID: <20041119171353.39851.qmail@web8504.mail.in.yahoo.com> Hi I have a few more points to add to the guide --- A section on managing updates with the suggestion that users should keep the amount of software installed in their system to the minimum necessary to keep updates manageable there are in general three types of updates 1) security fedoranews.org has a [security] tag for important security updates. a reference to this website would be useful 2) bugfixes 3) new features - this is a optional type of update which users need not apply if they dont want the additional features Announcements on updates are delayed by Redhat inorder for mirrors to be synced. this is a faq which is to be answered in the guide.such updates are tagged with [missing] in fedoranews.org. a changelog is part of the redhat announcements and can be found in rpm -q packagename --changelog Rahul Sundaram ===== Regards Rahul Sundaram __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com From jkinz at kinz.org Fri Nov 19 19:20:36 2004 From: jkinz at kinz.org (Jeff Kinz) Date: Fri, 19 Nov 2004 14:20:36 -0500 Subject: [rahulsundaram@gmail.com: Re: List etiquette question] Message-ID: <20041119142036.A19149@redline.comcast.net> > ----- Forwarded message from Rahul Sundaram ----- > > From: Rahul Sundaram > To: For users of Fedora Core releases > Hi > > > > > here's a solution -- can we post the mailing list etiquette rules > > somewhere under fedora.redhat.com? that way, any time some dimwit > > joins this club and decides he likes his personal way of doing things, > > he can be pointed in short order at the *fedora*-approved etiquette > > list. at which point, that should be the end of the debate. > > > Please do this. Write a set of guidelines and submit it to the docs > list. we can have a format set of guidelines approved by Redhat. > Everyone else lets kill this thread. I am pretty sure everything that > is supposed to be covered has already been done so. > > -- > Regards, > Rahul Sundaram Please see the attached file. This version is in html. I will convert it to the required format, and remove the extraneous references to the RedHat hat install, replacing them with "fedora" as needed. Is there any document I should read in order to understand what guideline, formats and specifications are being applied to the Fedora docs? Jeff Kinz -- Linux/Open Source. Your base belongs to you, free, forever. Idealism: "Realism applied over a longer time period" http://www.scaled.com/projects/tierone/ http://kinz.org http://www.quotedb.com/quotes/2763 Jeff Kinz, Emergent Research, Hudson, MA. ~ ~ ~ ~ From jkinz at kinz.org Fri Nov 19 19:21:56 2004 From: jkinz at kinz.org (Jeff Kinz) Date: Fri, 19 Nov 2004 14:21:56 -0500 Subject: [rahulsundaram@gmail.com: Re: List etiquette question] In-Reply-To: <20041119142036.A19149@redline.comcast.net>; from jkinz@kinz.org on Fri, Nov 19, 2004 at 02:20:36PM -0500 References: <20041119142036.A19149@redline.comcast.net> Message-ID: <20041119142156.B19149@redline.comcast.net> > ----- Forwarded message from Rahul Sundaram ----- > > From: Rahul Sundaram > To: For users of Fedora Core releases > Hi > > > > > here's a solution -- can we post the mailing list etiquette rules > > somewhere under fedora.redhat.com? that way, any time some dimwit > > joins this club and decides he likes his personal way of doing things, > > he can be pointed in short order at the *fedora*-approved etiquette > > list. at which point, that should be the end of the debate. > > > Please do this. Write a set of guidelines and submit it to the docs > list. we can have a format set of guidelines approved by Redhat. > Everyone else lets kill this thread. I am pretty sure everything that > is supposed to be covered has already been done so. > > -- > Regards, > Rahul Sundaram File actually attached this time. Sorry. Please see the attached file. This version is in html. I will convert it to the required format, and remove the extraneous references to the RedHat hat install, replacing them with "fedora" as needed. Is there any document I should read in order to understand what guideline, formats and specifications are being applied to the Fedora docs? Jeff Kinz -- nux/Open Source. Your base belongs to you, free, forever. Idealism: "Realism applied over a longer time period" http://www.scaled.com/projects/tierone/ http://kinz.org http://www.quotedb.com/quotes/2763 Jeff Kinz, Emergent Research, Hudson, MA. ~ ~ ~ ~ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rahulsundaram at yahoo.co.in Fri Nov 19 19:25:11 2004 From: rahulsundaram at yahoo.co.in (Rahul Sundaram) Date: Fri, 19 Nov 2004 11:25:11 -0800 (PST) Subject: list guidelines In-Reply-To: <20041119142036.A19149@redline.comcast.net> Message-ID: <20041119192511.50298.qmail@web8507.mail.in.yahoo.com> Hi > Is there any document I should read in order to > understand what > guideline, formats and specifications are being > applied to the Fedora > docs? > > > Jeff Kinz yes. there is lots of info @ http://fedora.redhat.com/projects/docs/ Make the changes as required and do try and present a online link instead of attaching the document regards Rahul Sundaram ===== Regards Rahul Sundaram __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com From jkinz at kinz.org Fri Nov 19 19:30:35 2004 From: jkinz at kinz.org (Jeff Kinz) Date: Fri, 19 Nov 2004 14:30:35 -0500 Subject: list guidelines In-Reply-To: <20041119192511.50298.qmail@web8507.mail.in.yahoo.com>; from rahulsundaram@yahoo.co.in on Fri, Nov 19, 2004 at 11:25:11AM -0800 References: <20041119142036.A19149@redline.comcast.net> <20041119192511.50298.qmail@web8507.mail.in.yahoo.com> Message-ID: <20041119143035.B19072@redline.comcast.net> On Fri, Nov 19, 2004 at 11:25:11AM -0800, Rahul Sundaram wrote: > > Is there any document I should read in order to understand what > > guideline, formats and specifications are being applied to the > > Fedora docs? > > yes. there is lots of info @ > > http://fedora.redhat.com/projects/docs/ > > Make the changes as required and do try and present a > online link instead of attaching the document http://www.rhil.org/docs/rhil-guide.html Will convert and format as described asap. -- Linux/Open Source. Your base belongs to you, free, forever. Idealism: "Realism applied over a longer time period" http://www.scaled.com/projects/tierone/ http://kinz.org http://www.quotedb.com/quotes/2763 Jeff Kinz, Emergent Research, Hudson, MA. ~ ~ ~ ~ From kwade at redhat.com Fri Nov 19 20:49:20 2004 From: kwade at redhat.com (Karsten Wade) Date: Fri, 19 Nov 2004 12:49:20 -0800 Subject: Adding boilerplate errata/CVS instructions In-Reply-To: <1100825658.3803.90.camel@cassandra.boston.redhat.com> References: <1100728757.3803.16.camel@cassandra.boston.redhat.com> <1100738345.3619.3758.camel@erato.phig.org> <1100810707.3803.52.camel@cassandra.boston.redhat.com> <1100823990.3619.5323.camel@erato.phig.org> <1100825658.3803.90.camel@cassandra.boston.redhat.com> Message-ID: <1100897360.16858.14.camel@erato.phig.org> On Thu, 2004-11-18 at 16:54, David Malcolm wrote: > On Thu, 2004-11-18 at 16:26 -0800, Karsten Wade wrote: > > cd /home/kwade/Documents/projects/fedora/fedora-docs/selinux-apache/ > > nsgmls -wxml -s /home/kwade/lib/psgmlx-0.5/lib/xml.dcl > > selinux-apache-en.xml > > nsgmls:/home/kwade/lib/psgmlx-0.5/lib/xml.dcl:1:W: SGML declaration was > > not implied > > > > SGML validation finished at Thu Nov 18 16:24:42 > > > > FWIW, that's the way it normally appears when I validate (in Emacs using > > C-c C-v). > > OK, great; good idea. Is xmllint happy with such a setup? If so, then > the ABOUT-DOC-EN probably _should_ get added to the main entities file. As far as I can tell, it works fine. I just ran xmllint against it (without options), with only FEDORA-ENTITIES-EN and the various PUBLISHED-HTML-URL etc. defined in a document, and it validates, builds, and does not error. > > > > > Any thoughts/rewrites? Perhaps the heading should read "About This > > > > > Document" instead? > > > > > > > > Yes, that is more of an accurate title. Changed that in the attachment. > > > > > > Perhaps the file should have a different name; perhaps > > > "about-this-document-en.xml" ? > > > > How about about-doc-en.xml? > Yes, that's much better. > > Maybe even "about-fedora-doc-en.xml", to make it clear that this relates > to a Fedora doc? (as opposed to RHEL) No need, everything is separate ... although it is not improper, and is certainly future proofing. Do as you wish, since I'm wishy-washy. :) > Can I go ahead and commit this (assuming I have access rights)? Or > should someone else on the list comment first? I'm just a lowly desktop > developer :-) Nah, youse a riter, now. I suggest you file a bug (RFE) against fedora-docs (tfox will get it, she has write perms and the buck-stops-here for stuff like what goes in fedora-docs/common), attach a patch to fedora-entities-en.xml, attach the about{-fedora}-doc-en.xml file. We'll also need to fix the fedora-docs/example-tutorial to include the new entity call(s) and sample definitions for the 4 entities required by - Karsten -- Karsten Wade, RHCE, Tech Writer a lemon is just a melon in disguise http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 From reynierpm at yahoo.es Sat Nov 20 18:55:43 2004 From: reynierpm at yahoo.es (=?iso-8859-1?q?Reynier=20P=E9rez=20Mira?=) Date: Sat, 20 Nov 2004 19:55:43 +0100 (CET) Subject: Fedora Core 3 and NTFS and MP3 and Video Codecs Message-ID: <20041120185543.35241.qmail@web20108.mail.yahoo.com> I have already running Fedora Core 3 but I not know how to mount partitions formated on NTFS or listen music recorded in WMA or MP3 format and view some movies codified by XVid or DivX or another codecs. What can I do for this ? ===== Reynier P?rez Mira ______________________________________________ Renovamos el Correo Yahoo!: ?100 MB GRATIS! Nuevos servicios, m?s seguridad http://correo.yahoo.es From rahulsundaram at yahoo.co.in Sun Nov 21 09:10:30 2004 From: rahulsundaram at yahoo.co.in (Rahul Sundaram) Date: Sun, 21 Nov 2004 01:10:30 -0800 (PST) Subject: Fedora Core 3 and NTFS and MP3 and Video Codecs In-Reply-To: <20041120185543.35241.qmail@web20108.mail.yahoo.com> Message-ID: <20041121091030.28250.qmail@web8510.mail.in.yahoo.com> --- Reynier P?rez Mira wrote: > I have already running Fedora Core 3 but I not know > how to mount partitions formated on NTFS or listen > music recorded in WMA or MP3 format and view some > movies codified by XVid or DivX or another codecs. > What can I do for this ? > you should be asking the users mailing list this question. This is the documentation list only meant for document authors and reviewers. please ask in the right list. these questions are already answered in detail in fedorafaq.org which will be updated for fedora core 3 in sometime. Meanwhile search the users list for answers regards Rahul Sundaram ===== Regards Rahul Sundaram __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com From quarlewm at jmu.edu Sat Nov 27 04:50:07 2004 From: quarlewm at jmu.edu (William M. Quarles) Date: Fri, 26 Nov 2004 23:50:07 -0500 Subject: Release notes on project website Message-ID: Considering that some people might still want to download Fedora Core 1 (i.e. since those paying attention might have noticed that the 2.4 kernel still performs better than 2.6), I think that it would be a good idea to have the release notes for Fedora Core 1 on the website, even if only for historical purposes. Red Hat always left old documentation for Red Hat Linux up on their website, and I don't see why The Fedora Project should behave any differently. Peace, William From paul at frields.com Sat Nov 27 15:01:52 2004 From: paul at frields.com (Paul W. Frields) Date: Sat, 27 Nov 2004 10:01:52 -0500 Subject: Release notes on project website In-Reply-To: References: Message-ID: <1101567713.13309.2.camel@bettie.internal.frields.org> On Fri, 2004-11-26 at 23:50 -0500, William M. Quarles wrote: > Considering that some people might still want to download Fedora Core 1 > (i.e. since those paying attention might have noticed that the 2.4 > kernel still performs better than 2.6), I think that it would be a good > idea to have the release notes for Fedora Core 1 on the website, even if > only for historical purposes. Red Hat always left old documentation for > Red Hat Linux up on their website, and I don't see why The Fedora > Project should behave any differently. Tammy, do you have any insight into this? Is the documentation for FC1 perhaps better suited to reside at the Legacy Project along with other upkeep? And would it then "vanish" when FC1 is abandoned by the Legacy Project? OK, that's enough questions for one morning. :-) -- Paul W. Frields, RHCE