11:45 a.m.
Hi all,
I am new to the list, although not new to Red Hat Linux. I am
interested in writing docs for anaconda, so, is anyone was already
working on them?
Taking a look at the Documentation project site, I see that I need
Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
learning curve for these? I have never done XML, and I am not an Emacs
user (sorry to start a flamewar). Perhaps I could write the text and
someone with more knowledge of XML/Emacs could put it into the right
format. I am not unwilling to learn XML/Emacs, but my time might be
spent better elsewhere.
Let me know what you all think.
Forrest
12:02 p.m.
On Thu, 20 Nov 2003, Taylor, ForrestX wrote:
Hi all,
I am new to the list, although not new to Red Hat Linux. I am
interested in writing docs for anaconda, so, is anyone was already
working on them?
Taking a look at the Documentation project site, I see that I need
Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
learning curve for these? I have never done XML, and I am not an Emacs
user (sorry to start a flamewar). Perhaps I could write the text and
someone with more knowledge of XML/Emacs could put it into the right
format. I am not unwilling to learn XML/Emacs, but my time might be
spent better elsewhere.
Are there non-Emacs solutions available for this??
...................Tom
1:36 p.m.
On Thu, 2003-11-20 at 10:02, Tom Diehl wrote:
On Thu, 20 Nov 2003, Taylor, ForrestX wrote:
> Hi all,
>
> I am new to the list, although not new to Red Hat Linux. I am
> interested in writing docs for anaconda, so, is anyone was already
> working on them?
>
> Taking a look at the Documentation project site, I see that I need
> Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
> learning curve for these? I have never done XML, and I am not an Emacs
> user (sorry to start a flamewar). Perhaps I could write the text and
> someone with more knowledge of XML/Emacs could put it into the right
> format. I am not unwilling to learn XML/Emacs, but my time might be
> spent better elsewhere.
Are there non-Emacs solutions available for this??
Any editor will suffice, but unless you have an intimate knowledge of
DocBook XML, you will find it difficult to use an editor which does not
have a mode similar to PSGML or nXML.
If you know how to indent properly, etc., it's really less of an issue
which editor you use and more of an issue for collaboration if you use
the tab character instead of spaces for tabs. :)
One editor I am keeping my eye on is http://www.conglomerate.org/. They
are thinking in novel ways that make using a GUI editor tempting.
At Red Hat, we have a relatively standardized way of doing things. We
can share .emacs changes and keep everyone able to edit each other's
projects, etc. It will be interesting to see how we resolve the lack of
homogeneity in Fedora Project docs. These are, after all, open
standards, so if you can accomplish the same thing using other tools,
more power to you.
- Karsten
--
Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664
kwade(a)redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995
Red Hat Enterprise Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
2:14 p.m.
Took my lunch break to look into the creation of fedora-docs. And I have to
agree with Taylor:
"Taking a look at the Documentation project site, I see that I need
Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
learning curve for these? I have never done XML, and I am not an Emacs
user (sorry to start a flamewar). Perhaps I could write the text and
someone with more knowledge of XML/Emacs could put it into the right
format. I am not unwilling to learn XML/Emacs, but my time might be
spent better elsewhere."
This is very discouraging!!
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Karsten Wade
Sent: 20 November 2003 14:36
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
On Thu, 2003-11-20 at 10:02, Tom Diehl wrote:
On Thu, 20 Nov 2003, Taylor, ForrestX wrote:
> Hi all,
>
> I am new to the list, although not new to Red Hat Linux. I am
> interested in writing docs for anaconda, so, is anyone was already
> working on them?
>
> Taking a look at the Documentation project site, I see that I need
> Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
> learning curve for these? I have never done XML, and I am not an Emacs
> user (sorry to start a flamewar). Perhaps I could write the text and
> someone with more knowledge of XML/Emacs could put it into the right
> format. I am not unwilling to learn XML/Emacs, but my time might be
> spent better elsewhere.
Are there non-Emacs solutions available for this??
Any editor will suffice, but unless you have an intimate knowledge of
DocBook XML, you will find it difficult to use an editor which does not
have a mode similar to PSGML or nXML.
If you know how to indent properly, etc., it's really less of an issue
which editor you use and more of an issue for collaboration if you use
the tab character instead of spaces for tabs. :)
One editor I am keeping my eye on is http://www.conglomerate.org/. They
are thinking in novel ways that make using a GUI editor tempting.
At Red Hat, we have a relatively standardized way of doing things. We
can share .emacs changes and keep everyone able to edit each other's
projects, etc. It will be interesting to see how we resolve the lack of
homogeneity in Fedora Project docs. These are, after all, open
standards, so if you can accomplish the same thing using other tools,
more power to you.
- Karsten
--
Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664
kwade(a)redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995
Red Hat Enterprise Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
2:45 p.m.
On Thu, 2003-11-20 at 12:14, Alexander Rau (work) wrote:
Took my lunch break to look into the creation of fedora-docs. And I
have to
agree with Taylor:
"Taking a look at the Documentation project site, I see that I need
Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
learning curve for these? I have never done XML, and I am not an Emacs
user (sorry to start a flamewar). Perhaps I could write the text and
someone with more knowledge of XML/Emacs could put it into the right
format. I am not unwilling to learn XML/Emacs, but my time might be
spent better elsewhere."
This is very discouraging!!
Indeed. Let's focus on the actual documentation, and hopefully someone
will step forward that can put it into XML. Otherwise, I'll try to read
the docs on setting up XML/Emacs this weekend and try it out.
Alexander, can you post your ideas for a Table of Contents?
Forrest
3:27 p.m.
Here are my suggestions for a Table of Contents (TOC)
Just a brain storm and working copy:
1. Introduction
2. How anaconda works
2a) boot process
2b) actual anaconda process
2ba) probing for hardware (what is happening behind the
scenes/what programs are doing what)
2bb) language selection
2bc) harddrive setup
.
.
.
.
.
.
2. Installation
3. What is needed to re-build anaconda (disk space, packages)
4. Tree structure
5. binaries (just quick explanation with details in later chapters)
5a) buildinstall
.
.
.
6. mini how to editing and making rpms from source
7. Set up your build environment (tree structures needed and so on)
8. The comps.xml chapter (explanation and making your own comps.xml)
9. Step by step walkthrough the whole buildinstall process
10. Splitting distros
11. burning distros mkisofs
12. Links and useful tools
13. Acknowledgements
====================================
And here is the start for the Introduction chapter (straight from the fedora
anaconda project site http://fedora.redhat.com/projects/anaconda-installer/)
1. Introduction
Red Hat Installation Program (Anaconda)
Anaconda is the installation program for Red Hat distributions. During
installation, the system's hardware is identified and configured, and the
appropriate file systems for the system's architecture are created. Finally,
it allows the user to install the operating system software on the system.
Optionally, it can upgrade existing Red Hat installations. Anaconda can run
in a fully interactive mode (text or graphical), or in a kickstart mode,
which is allows the installation to be scripted for unattended operation.
This makes deploying hundreds or thousands of systems very easy.
Anaconda is written in Python and C, and is distributed under the GPL. The
graphical frontend is written with PyGtk. Using a scripting language
(Python) for the majority of the code allows for easily distribution of
updates and the quick development of new features.
AR
PS/ Hope this is a good start
3:44 p.m.
On Thu, 2003-11-20 at 13:27, Alexander Rau (work) wrote:
Here are my suggestions for a Table of Contents (TOC)
Just a brain storm and working copy:
<snip>
AR
PS/ Hope this is a good start
This is great--more than I would have thought of!
I think that we also need a 'Required updates' section that will list
updates required to get things functioning (such as the patch to
buildinstall).
Let's split this up as it is, and start writing some documentation. AR,
pantz (others?) which sections do you want to start with?
Forrest
4:08 p.m.
1. Well, I will check my notes from when I went through the whole process
and then I will see what I can contribute. I will let you know tomorrow.
2. I would also appreciate honest feedback from you guys on my writing and
grammar since English is not my first language. Maybe I can, once we are
finished!!, translate the whole caboodle into German.
3. I am wondering if it wouldn't be helpful to get Jeremy on board!?
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Taylor, ForrestX
Sent: 20 November 2003 16:44
To: Alexander Rau (work)
Cc: fedora-docs-list(a)redhat.com
Subject: RE: Anaconda documents
On Thu, 2003-11-20 at 13:27, Alexander Rau (work) wrote:
Here are my suggestions for a Table of Contents (TOC)
Just a brain storm and working copy:
<snip>
AR
PS/ Hope this is a good start
This is great--more than I would have thought of!
I think that we also need a 'Required updates' section that will list
updates required to get things functioning (such as the patch to
buildinstall).
Let's split this up as it is, and start writing some documentation. AR,
pantz (others?) which sections do you want to start with?
Forrest
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
5:25 p.m.
On Thu, 2003-11-20 at 14:08, Alexander Rau (work) wrote:
1. Well, I will check my notes from when I went through the whole
process
and then I will see what I can contribute. I will let you know tomorrow.
Okay.
2. I would also appreciate honest feedback from you guys on my
writing and
grammar since English is not my first language. Maybe I can, once we are
finished!!, translate the whole caboodle into German.
No problem. You write better than most native English speakers.
3. I am wondering if it wouldn't be helpful to get Jeremy on
board!?
Yes, it would. Although, he just posted to the anaconda list explaining
why he hasn't. He did say, however, he would look over the documents
once they exist.
I'll look over your TOC, expand on it, and write up a few notes
tonight. I guess that I'll post it to the list for now.
Tammy/Karsten/Tim/etc.,
Does Red Hat have a method to collaborate on documents yet (CVS, web,
etc.)? This is something that needs to be discussed if the documents
are being written by more than one person.
Thanks,
Forrest
1:10 p.m.
>>>> "Taylor," == Taylor, ForrestX
<forrestx.taylor(a)intel.com> writes:
Taylor,> Tammy/Karsten/Tim/etc.,
Well, I guess I'm "etc", but you can call me "Ed" :-)
Taylor,> Does Red Hat have a method to collaborate on documents yet (CVS,
Taylor,> web, etc.)? This is something that needs to be discussed if the
Taylor,> documents are being written by more than one person.
We use CVS internally (on the Red Hat Enterprise Linux documentation). My
understanding is that CVS will be used for the Fedora project as well...
Ed
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
1:33 p.m.
On Fri, 2003-11-21 at 11:10, Edward C. Bailey wrote:
>>>>> "Taylor," == Taylor, ForrestX
<forrestx.taylor(a)intel.com> writes:
Taylor,> Tammy/Karsten/Tim/etc.,
Well, I guess I'm "etc", but you can call me "Ed" :-)
Sorry, Ed. I didn't mean to leave you out. I never was a good speller
;o)
Taylor,> Does Red Hat have a method to collaborate on documents yet (CVS,
Taylor,> web, etc.)? This is something that needs to be discussed if the
Taylor,> documents are being written by more than one person.
We use CVS internally (on the Red Hat Enterprise Linux documentation). My
understanding is that CVS will be used for the Fedora project as well...
Alright. Thanks.
Forrest
--
3:21 p.m.
On Thu, Nov 20, 2003 at 03:25:11PM -0800, Taylor, ForrestX wrote:
On Thu, 2003-11-20 at 14:08, Alexander Rau (work) wrote:
> 1. Well, I will check my notes from when I went through the whole process
> and then I will see what I can contribute. I will let you know tomorrow.
Okay.
> 2. I would also appreciate honest feedback from you guys on my writing and
> grammar since English is not my first language. Maybe I can, once we are
> finished!!, translate the whole caboodle into German.
No problem. You write better than most native English speakers.
> 3. I am wondering if it wouldn't be helpful to get Jeremy on board!?
Yes, it would. Although, he just posted to the anaconda list explaining
why he hasn't. He did say, however, he would look over the documents
once they exist.
I'll look over your TOC, expand on it, and write up a few notes
tonight. I guess that I'll post it to the list for now.
Tammy/Karsten/Tim/etc.,
Does Red Hat have a method to collaborate on documents yet (CVS, web,
etc.)? This is something that needs to be discussed if the documents
are being written by more than one person.
http://fedora.redhat.com/participate/
This page was recently updated to let people know that the external
CVS server will be available by the end of the year. I wish it was
available now because everyone is eager to start and it is much easier
to colloborate if you can see other people's changes instantly.
Tammy
Thanks,
Forrest
6:05 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
On Fri, 2003-11-21 at 13:21, Tammy Fox wrote:
http://fedora.redhat.com/participate/
This page was recently updated to let people know that the external
CVS server will be available by the end of the year. I wish it was
available now because everyone is eager to start and it is much easier
to colloborate if you can see other people's changes instantly.
For easing transition of external CVS maintained projects, is there
anything about the construction of the Fedora Project CVS which is
unique? Suggestions for module naming, construction, and practices,
repository structure, branching dangers, etc.? Nothing is obvious to me
from reading:
http://fedora.redhat.com/participate/documentation-guide/ch-cvs.html
This information would be useful creating standalone CVS repositories
which are easily integrated when the main FP CVS is available.
On a related topic, if anyone does put together a CVS repository of
documentation and you make it available for anonymous CVS access, I'll
be happy to mirror your repository until the main FP CVS is available.
- Karsten
--
Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664
kwade(a)redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995
Red Hat Enterprise Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
6:09 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Karsten Wade wrote:
On a related topic, if anyone does put together a CVS repository of
documentation and you make it available for anonymous CVS access, I'll
be happy to mirror your repository until the main FP CVS is available.
I have finished setting up the CVS repository for Anaconda docs.
As a heads up, it is a pserver that uses stunnel to encrypt the traffic.
I have created an RPM to help you install the stunnel bridge (it is very
easy :) ) I will also put up the SRPM for those who need to rebuild on
something other than Fedora.
I'll send a link to a page of setup instructions, plus my GPG key so you
can encrypt the username and password that you want me to add to the cvs
users list. BTW, you can cut and paste your encrypted password from
/etc/shadow, but please create a new cvs only password.
Thanks,
Akbar
1:18 a.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Hi,
CVS is setup and ready to go. I think we should be able to get
everything into CVS today without any problems. All we need now is a CVS
directory structure and to decide who will do what. I'll also add
anonymous access soon for mirroring purposes.
Here's the scoop. There are 5 easy steps to get you setup to connect to
the CVS server.
1. Please send me an email with your desired username and password. Use
the crypt() function to encrypt your password, or just take one out of
/etc/shadow.
It would probably be best if you could import my PGP key to your email
client and send me an encrypted email with the user name and password. I
have placed my public key at the end of this file, you can also get it
from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search
String".
At this point I'll add you to the CVS users list.
2. Go to http://www.delixus.com/downloads/ccvssh/ (sorry about the
advertisement on the page) and read the directions. Just download
ccvssh-0.9.1-1.i586.rpm and install it. I followed 3rd party practice
and put the binary in a subdirectory of /opt.
The RPM and SRPM are signed with the Delixus corporate GPG key so you
can verify the integrity of the packages (assuming you trust me as a
reliable source).
Please note: I only created an RPM for Fedora, but I also put up the
SRPM so you can easily rebuild the CCVSSH client. It is GPL BTW. Also,
let me know if you need it rebuilt for another OS and I'll try to get it
done.
3. Setup environment variables in your .bash_profile file.
See http://www.delixus.com/downloads/ccvssh/ for instructions.
4. Login to the CVS server.
5. Use standard CVS commands to interact with the server, but enjoy
encrypted communication with the server
FYI: I'll be out of the office until approx. 9:30 AM PST tomorrow, but
will get to the username/password requests ASAP.
This software is fairly cool. It redirects pserver traffic over SSL
using stunnel. It gives the best of both pserver and the SSH ext method.
It should be very easy to setup, but if not just send me a complaint
email and I'll see if I can help.
Thanks,
Akbar
My personal public key:
Public key for 0xCF3FC7AB4FF3176F
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.3 (MingW32)
mQGiBD/C0u8RBACmfRBaKBC1qrmTz18XcsP0NOgZRzFeE1aC85DcyO56MhQGxiI5
r3tApdMmKrq8n6K/0X16A8ilH45vi9vv4hjhD/qVrmhz0ko8sr7mEk7xA7dATX/Z
QMMqdpQl1fc5X+3sYzgL1ZoOH7RQaV8f1WDVWpKJt/vkISkoXYk/dq6yIwCg4jTZ
f7SnVG35Y/VSxNg5ZHz6AIkEAKSeNnoo6jgYv1Uk5CS+Pk0Laema5j/ZgYUhz3cC
tAk4f9GaFWpx3X5WkolCz4jsj6zv4OSe8UQocqTwxEw6nV1sTavg9oi6l9qPnjjz
XUNy6EzmrW9f3ggNptur10TTYT0aZLzScZyzyfs+IbQoaLu9rq0DERRBpN10YoXJ
Pb2wBACW6DWzgR4V1/1t6vdA2b8LzOetTPNNPGbUHiVU18u6kwMCcd7chu1rcDAK
Paobb6o0UUPic5JymOLR/KPg7kj1t2ZaiNSxeZdWS8ZcMumzMEzMwwoiEIomLgUB
NH7Eb9YPuz0dXdK1blR9Co2eBCw/M+FVrjU3krd81YcRlbrJr7ROQWtiYXIgUy4g
QWhtZWQgKFBlcnNvbmFsIEdQRyBrZXkgZm9yIEFrYmFyIFMuIEFobWVkKSA8YWti
YXI1MDFAZHNsZXh0cmVtZS5jb20+iFsEExECABsFAj/C0u8GCwkIBwMCAxUCAwMW
AgECHgECF4AACgkQzz/Hq0/zF2+b7wCgrzu6peifPwlM3QJsISgWeHlQQW4AoL0x
FQEzrtVxFTsMfDASTBC6T5QSuQENBD/C0vEQBADeRkAO2j7yAiNVvPMKrrG7Bscq
dhJbzG6uxeuN8Gxc8thHb7f95Yzqa/jOpfuY3vbj+0/jGQkoKTdszkDkPSEmvMxi
snLCrFBuOGLCBVUICf4Z8LI5XfBWnrvG6QTCyfVd3Vyz86XgSrv4W7O71tKhBdey
bHjPDKad2Y2hkvF/jwADBwQAulAk39fHLOaXkABIYv+oWmKYKvOOgX5JCA+ZN5yK
UcZWwogkWVlhL78XeXQjdlZOLif3WsDDX3EMw87y0fpUj2FMVPcrMHLzh00RnBQV
RJvJHQNjBNBhyom+9ObqNGuIMir8aY3kLTi6ABc9vvZ7U1qZ2lAAqNmFklCeeAcF
SiqIRgQYEQIABgUCP8LS8QAKCRDPP8erT/MXb/MBAKCjsBc+ZRnwXjxQrzCk/ANv
NcBR3QCgkXWYeRo3J++pzWDPwfj8wl9eHvk=
=O2m5
-----END PGP PUBLIC KEY BLOCK-----
12:55 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote:
1. Please send me an email with your desired username and password.
Use
the crypt() function to encrypt your password, or just take one out of
/etc/shadow.
/sbin/grub-md5-crypt will encrypt your password admirably.
--
Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664
kwade(a)redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995
Red Hat Enterprise Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
3:11 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
On Mon, Nov 24, 2003 at 11:18:02PM -0800, Akbar S. Ahmed wrote:
Hi,
CVS is setup and ready to go. I think we should be able to get
everything into CVS today without any problems. All we need now is a CVS
directory structure and to decide who will do what. I'll also add
anonymous access soon for mirroring purposes.
To answer Karsten's earlier question about the current CVS structure:
The directory structure looks like the following:
|-- common
|-- css
|-- developer-guide
|-- documentation-guide
|-- example-tutorial
|-- install-guide
|-- stylesheet-images
`-- xsl
common: contains any DocBook XML and image files shared between 2 or
more documents; for example, cvs-en.xml is shared between the
Developer Guide and the Documentation Guide; legalnotice-en.xml should
be included in all docs
css: contains the common CSS file used for the HTML versions of the
documents
stylesheet-images: contains the admonition graphics used in the
documents
xsl: contains the XSLT stylesheets used for processing the DocBook XML
into different formats
A directory should exist for each document, and the parent file should
be the same name as the directory with the -<lang>.xml added on to
it. This directory should contain a Makefile
Images for each document should be in a figs directory under the
directory for the document.
Each document directory should contain a po directory for the
translation files. (pgampe is working on this for the existing ones)
All DocBook XML files should use the format
<descriptive-name>-<lang>.xml.
If you use this structure and use the shared file in common, we should
be able to plug your files into fedora-docs once we have public access
to it. A great place to start is the example-tutorial directory. It
contains a template document you can start from.
(Since I took the time to write this up, I'll add it to the
Documentation Guide. ;-) )
Tammy
Here's the scoop. There are 5 easy steps to get you setup to
connect to
the CVS server.
1. Please send me an email with your desired username and password. Use
the crypt() function to encrypt your password, or just take one out of
/etc/shadow.
It would probably be best if you could import my PGP key to your email
client and send me an encrypted email with the user name and password. I
have placed my public key at the end of this file, you can also get it
from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search
String".
At this point I'll add you to the CVS users list.
2. Go to http://www.delixus.com/downloads/ccvssh/ (sorry about the
advertisement on the page) and read the directions. Just download
ccvssh-0.9.1-1.i586.rpm and install it. I followed 3rd party practice
and put the binary in a subdirectory of /opt.
The RPM and SRPM are signed with the Delixus corporate GPG key so you
can verify the integrity of the packages (assuming you trust me as a
reliable source).
Please note: I only created an RPM for Fedora, but I also put up the
SRPM so you can easily rebuild the CCVSSH client. It is GPL BTW. Also,
let me know if you need it rebuilt for another OS and I'll try to get it
done.
3. Setup environment variables in your .bash_profile file.
See http://www.delixus.com/downloads/ccvssh/ for instructions.
4. Login to the CVS server.
5. Use standard CVS commands to interact with the server, but enjoy
encrypted communication with the server
FYI: I'll be out of the office until approx. 9:30 AM PST tomorrow, but
will get to the username/password requests ASAP.
This software is fairly cool. It redirects pserver traffic over SSL
using stunnel. It gives the best of both pserver and the SSH ext method.
It should be very easy to setup, but if not just send me a complaint
email and I'll see if I can help.
Thanks,
Akbar
My personal public key:
Public key for 0xCF3FC7AB4FF3176F
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.3 (MingW32)
mQGiBD/C0u8RBACmfRBaKBC1qrmTz18XcsP0NOgZRzFeE1aC85DcyO56MhQGxiI5
r3tApdMmKrq8n6K/0X16A8ilH45vi9vv4hjhD/qVrmhz0ko8sr7mEk7xA7dATX/Z
QMMqdpQl1fc5X+3sYzgL1ZoOH7RQaV8f1WDVWpKJt/vkISkoXYk/dq6yIwCg4jTZ
f7SnVG35Y/VSxNg5ZHz6AIkEAKSeNnoo6jgYv1Uk5CS+Pk0Laema5j/ZgYUhz3cC
tAk4f9GaFWpx3X5WkolCz4jsj6zv4OSe8UQocqTwxEw6nV1sTavg9oi6l9qPnjjz
XUNy6EzmrW9f3ggNptur10TTYT0aZLzScZyzyfs+IbQoaLu9rq0DERRBpN10YoXJ
Pb2wBACW6DWzgR4V1/1t6vdA2b8LzOetTPNNPGbUHiVU18u6kwMCcd7chu1rcDAK
Paobb6o0UUPic5JymOLR/KPg7kj1t2ZaiNSxeZdWS8ZcMumzMEzMwwoiEIomLgUB
NH7Eb9YPuz0dXdK1blR9Co2eBCw/M+FVrjU3krd81YcRlbrJr7ROQWtiYXIgUy4g
QWhtZWQgKFBlcnNvbmFsIEdQRyBrZXkgZm9yIEFrYmFyIFMuIEFobWVkKSA8YWti
YXI1MDFAZHNsZXh0cmVtZS5jb20+iFsEExECABsFAj/C0u8GCwkIBwMCAxUCAwMW
AgECHgECF4AACgkQzz/Hq0/zF2+b7wCgrzu6peifPwlM3QJsISgWeHlQQW4AoL0x
FQEzrtVxFTsMfDASTBC6T5QSuQENBD/C0vEQBADeRkAO2j7yAiNVvPMKrrG7Bscq
dhJbzG6uxeuN8Gxc8thHb7f95Yzqa/jOpfuY3vbj+0/jGQkoKTdszkDkPSEmvMxi
snLCrFBuOGLCBVUICf4Z8LI5XfBWnrvG6QTCyfVd3Vyz86XgSrv4W7O71tKhBdey
bHjPDKad2Y2hkvF/jwADBwQAulAk39fHLOaXkABIYv+oWmKYKvOOgX5JCA+ZN5yK
UcZWwogkWVlhL78XeXQjdlZOLif3WsDDX3EMw87y0fpUj2FMVPcrMHLzh00RnBQV
RJvJHQNjBNBhyom+9ObqNGuIMir8aY3kLTi6ABc9vvZ7U1qZ2lAAqNmFklCeeAcF
SiqIRgQYEQIABgUCP8LS8QAKCRDPP8erT/MXb/MBAKCjsBc+ZRnwXjxQrzCk/ANv
NcBR3QCgkXWYeRo3J++pzWDPwfj8wl9eHvk=
=O2m5
-----END PGP PUBLIC KEY BLOCK-----
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
--
4:47 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote:
Hi,
CVS is setup and ready to go. I think we should be able to get
everything into CVS today without any problems. All we need now is a CVS
directory structure and to decide who will do what. I'll also add
anonymous access soon for mirroring purposes.
Great job, Akbar. Will you be able to host this until at least the end
of the year? If not, let's go to Brian's kickstart-tools repository and
set it up there.
I still haven't heard back from savannah.
It looks like the directory structure will be just like the Red Hat CVS
repository for fedora-docs:
http://fedora.redhat.com/participate/documentation-guide/ch-getting-files...
Just download the files and import them into the new repository. Tammy
gave an explanation about what each of the files are and where we should
put new files.
Forrest
11:53 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Taylor, ForrestX wrote:
Will you be able to host this until at least the end
of the year? If not, let's go to Brian's kickstart-tools repository and
set it up there.
I could host it till the end of the year, but Brian's kickstart-tools
repository on sf.net would probably be better. sf.net has better
bandwidth than I have here.
If we switch to sf.net, when will this be done?
Should we start on my system and then switch or just start with sf.net?
Personally, either way is fine with me.
I have a system up and running, but nobody except Alexander has send
their CVS username/password. There are a few kinks that Alexander and I
are working out, but I'm sure everything can be fixed.
Thanks,
Akbar
10:30 a.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Hello everybody and a happy new year.
The holiday season is over and I am wondering if you guys are up to reviving
the anaconda documentation project?
Anybody any idea where we are at?
I saw Manilal has published a little how-to.
https://www.redhat.com/archives/anaconda-devel-list/2004-January/msg00021.ht
ml
Might be useful
Thoughts?
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Akbar S. Ahmed
Sent: 26 November 2003 00:53
To: fedora-docs-list(a)redhat.com
Subject: Re: CVS in the meantime (was Re: Anaconda documents)
Taylor, ForrestX wrote:
Will you be able to host this until at least the end
of the year? If not, let's go to Brian's kickstart-tools repository and
set it up there.
I could host it till the end of the year, but Brian's kickstart-tools
repository on sf.net would probably be better. sf.net has better
bandwidth than I have here.
If we switch to sf.net, when will this be done?
Should we start on my system and then switch or just start with sf.net?
Personally, either way is fine with me.
I have a system up and running, but nobody except Alexander has send
their CVS username/password. There are a few kinks that Alexander and I
are working out, but I'm sure everything can be fixed.
Thanks,
Akbar
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
1:08 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Alexander Rau (work) wrote:
Hello everybody and a happy new year.
The holiday season is over and I am wondering if you guys are up to reviving
the anaconda documentation project?
Anybody any idea where we are at?
I saw Manilal has published a little how-to.
https://www.redhat.com/archives/anaconda-devel-list/2004-January/msg00021.ht
ml
Might be useful
Thoughts?
Happy new year to you too Alexander!
After my bad start - I'm back in the action ... I am right in the middle
of an anaconda/Fedora customisation project and I am documenting
everything that I am doing. I am interested in getting something
together to make it alot easier on people than the current mix and match
documentation that exists spread out all over the place.
The thing that scared me off is the tools needed to do the doc 'redhat
style'. I know its probably easy once you get into it - but the trick is
someones gotta take the time to 'get into it'. If it was simply a matter
of copy/paste what we already have, into some nice easy gui program that
formats the text, etc. - that would be much more inviting!!
Anyhoo - my own personal doc is growing daily as I learn more about the
customisation process so call on me when you need help ...
pantz
--
Before you criticize someone, walk a mile in their shoes ...
That way when you do criticize them, you're a mile away and you have their shoes!
1:31 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Cool!
I have my notes, too (and I am sure everybody else does, too). Any idea how
we can exchange notes so we do not have to double our efforts?
I am also not too fond of the red-hat style formatting.
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Paul Pianta
Sent: 13 January 2004 14:09
To: fedora-docs-list(a)redhat.com
Subject: Re: CVS in the meantime (was Re: Anaconda documents)
Alexander Rau (work) wrote:
Hello everybody and a happy new year.
The holiday season is over and I am wondering if you guys are up to
reviving
the anaconda documentation project?
Anybody any idea where we are at?
I saw Manilal has published a little how-to.
https://www.redhat.com/archives/anaconda-devel-list/2004-January/msg00021.h
t
ml
Might be useful
Thoughts?
Happy new year to you too Alexander!
After my bad start - I'm back in the action ... I am right in the middle
of an anaconda/Fedora customisation project and I am documenting
everything that I am doing. I am interested in getting something
together to make it alot easier on people than the current mix and match
documentation that exists spread out all over the place.
The thing that scared me off is the tools needed to do the doc 'redhat
style'. I know its probably easy once you get into it - but the trick is
someones gotta take the time to 'get into it'. If it was simply a matter
of copy/paste what we already have, into some nice easy gui program that
formats the text, etc. - that would be much more inviting!!
Anyhoo - my own personal doc is growing daily as I learn more about the
customisation process so call on me when you need help ...
pantz
--
Before you criticize someone, walk a mile in their shoes ...
That way when you do criticize them, you're a mile away and you have their
shoes!
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
2:44 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
On Tue, 13 Jan 2004, Stefan Waidele jun. wrote:
Alexander Rau (work) wrote:
> Cool!
>
> I have my notes, too (and I am sure everybody else does, too). Any idea how
> we can exchange notes so we do not have to double our efforts?
Wiki, Twiki, Kwiki,...
This would be a great way to at least collaberate and get initial docs.
Also, for those of us that don't have time to write entire sections, we
might be able to easily review and make minor additions/edits.
Cheers...james
Just an idea,
Stefan
3:02 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Wiki, Twiki, Kwiki,...
I'm clueless on wikis - never been a big fan - but if someone sets one
up somewhere I am ready to add/modify/read/whatever it - and in the
process - learn how they work lol.
I guess we could wiki it for a while - get all the separate docs
integrated into something that everyone agrees on - and then when we
have a complete doc (read over many times by many people) - then we can
maybe find some poor innocent fool that will do the dirty job of
squeezing it into a format that redhat are gonna accept.
Any wiki-aware people with some spare server-space out there? (actually
i have a mega-slow server that might do the job if needed ...)
pantz
--
Before you criticize someone, walk a mile in their shoes ...
That way when you do criticize them, you're a mile away and you have their shoes!
1:01 a.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
Stefan Waidele jun. wrote:
Wiki, Twiki, Kwiki,...
Just an idea,
Stefan
What happened with Savannah? Should we create a new project?
I had a set up a cvs server here, but there were some connection
establishment problems. I could setup another server here and we could
give it another go from my site. It'll take me till Sunday or so to get
to it b/c we are shipping some s/w this week.
I also think that Stefan's idea of wiki/twiki etc. is a good one. It's
the easiest collaboration environment to use that gives us versioning.
Thanks,
Akbar
7:03 a.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
I am playing with wiki on my server at home. I let you guys know once I get
it to work.
Does this sound like an alternative we can settle for or should we explore
other alternatives?
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Akbar S. Ahmed
Sent: 14 January 2004 02:01
To: fedora-docs-list(a)redhat.com
Subject: Re: CVS in the meantime (was Re: Anaconda documents)
Stefan Waidele jun. wrote:
Wiki, Twiki, Kwiki,...
Just an idea,
Stefan
What happened with Savannah? Should we create a new project?
I had a set up a cvs server here, but there were some connection
establishment problems. I could setup another server here and we could
give it another go from my site. It'll take me till Sunday or so to get
to it b/c we are shipping some s/w this week.
I also think that Stefan's idea of wiki/twiki etc. is a good one. It's
the easiest collaboration environment to use that gives us versioning.
Thanks,
Akbar
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
5:05 p.m.
New subject: CVS in the meantime (was Re: Anaconda documents)
On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote:
1. Please send me an email with your desired username and password.
Use
the crypt() function to encrypt your password, or just take one out of
/etc/shadow.
It would probably be best if you could import my PGP key to your email
client and send me an encrypted email with the user name and password. I
have placed my public key at the end of this file, you can also get it
from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search
String".
Does anyone know how to get evolution to use Akbar's PGP key? I cannot
seem to find a way to import it.
Thanks,
Forrest
10:05 a.m.
New subject: CVS in the meantime
>>>> "Karsten" == Karsten Wade
<kwade(a)redhat.com> writes:
Karsten> On Fri, 2003-11-21 at 13:21, Tammy Fox wrote:
> http://fedora.redhat.com/participate/
>
> This page was recently updated to let people know that the external CVS
> server will be available by the end of the year. I wish it was available
> now because everyone is eager to start and it is much easier to
> colloborate if you can see other people's changes instantly.
Karsten> For easing transition of external CVS maintained projects, is
Karsten> there anything about the construction of the Fedora Project CVS
Karsten> which is unique? Suggestions for module naming, construction, and
Karsten> practices, repository structure, branching dangers, etc.? Nothing
Karsten> is obvious to me from reading:
Karsten> http://fedora.redhat.com/participate/documentation-guide/ch-cvs.html
Karsten> This information would be useful creating standalone CVS
Karsten> repositories which are easily integrated when the main FP CVS is
Karsten> available.
...
I'll go out on a limb here and give my two cents on the matter. It would
seem to me that it would be best to put some sort of hierarchy in place on
the CVS server(s). At the least, put modules under something like
"fedora-docs". That would at least eliminate the possibility of collisions
with the software folks on the project's CVS box.
As for eliminating collisions between separate docs projects, the most
obvious solution is just to have everyone use the same interim CVS
server... :-)
Ed
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
10:39 a.m.
At 23:25 20/11/2003, Taylor, ForrestX wrote:
Does Red Hat have a method to collaborate on documents yet (CVS, web,
etc.)? This is something that needs to be discussed if the documents
are being written by more than one person.
Anyone thought of using a wiki for this?
regards DaveP
3:57 p.m.
Alexander Rau (work) wrote:
Here are my suggestions for a Table of Contents (TOC)
Just a brain storm and working copy:
1. Introduction
very nice and comprehensive TOC - good stuff.
i just thought to myself ....
what is it that most people want to do when customizing
redhat/fedora/anaconda?
these are some things i came up with that could maybe somehow be
incorporated into the doc ...
* creating a single cd from the 3 cd set with a cutdown version of
packages and comps.xml and a kickstart file to automate the whole install
* remove/replace all occurences of the words redhat/fedora from the
anaconda install process (text and graphical) with their own custom
text, logos, etc...
* replace original redhat/fedora rpm packages with updated rpm packages
(security updates or whatever) and reburn the cds so that they can have
a version of RedHat 9 - six months after its release - with all security
updates applied (and other packages updated)
* add functionality to anaconda that didn't previously exist - eg.
adding a new filesystem support, adding support for a new NIC, etc.
(this one is more technical and would be rather difficult to incorporate
into a generic anaconda doc.) (infact forget about this last one for
inclusion ...)
well they are my ideas thrown into the pile - lets go!
pantz
8:55 p.m.
On Thu, 20 Nov 2003, Paul Pianta wrote:
Alexander Rau (work) wrote:
>Here are my suggestions for a Table of Contents (TOC)
>
>Just a brain storm and working copy:
>
>1. Introduction
>
>
very nice and comprehensive TOC - good stuff.
i just thought to myself ....
what is it that most people want to do when customizing
redhat/fedora/anaconda?
these are some things i came up with that could maybe somehow be
incorporated into the doc ...
* creating a single cd from the 3 cd set with a cutdown version of
packages and comps.xml and a kickstart file to automate the whole install
* remove/replace all occurences of the words redhat/fedora from the
anaconda install process (text and graphical) with their own custom
text, logos, etc...
* replace original redhat/fedora rpm packages with updated rpm packages
(security updates or whatever) and reburn the cds so that they can have
a version of RedHat 9 - six months after its release - with all security
updates applied (and other packages updated)
* add functionality to anaconda that didn't previously exist - eg.
adding a new filesystem support, adding support for a new NIC, etc.
(this one is more technical and would be rather difficult to incorporate
into a generic anaconda doc.) (infact forget about this last one for
inclusion ...)
Actually, what is required documentation wise with this last one is
something that at a high level describes the architecture of anaconda (how
it all fits together, what python modules exist, what service they
provide. Also, things like something that actually describes anaconda's
install process from boot to re-boot). A lot of this actually would be
usefull for not only extending anaconda, but also for things like
troubleshooting installs and better understanding how to interact with it
from a kickstart perspective (for instance part of its install process is
it reads the kickstart file initially, and then it re-reads it after post.
This is of course really usefull for making kickstarts that use %pre to
essentially query the system and then tailor the kickstart after this
to the specific needs at hand).
On, the other hand actually document the actual api of the various python
modules should definately not be a first pass thing (though, it certainly
could be a goal).
Anyway, I think your last category is ultimately still quite usefull when
you look at it from the architectual perspective rather than just giving
examples or specifics of how to add particular bits of functionality.
Just by 2 cents.
Cheers...james
8:01 a.m.
On Thu, 2003-11-20 at 15:14, Alexander Rau (work) wrote:
Took my lunch break to look into the creation of fedora-docs. And I
have to
agree with Taylor:
"Taking a look at the Documentation project site, I see that I need
Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
learning curve for these? I have never done XML, and I am not an Emacs
user (sorry to start a flamewar). Perhaps I could write the text and
someone with more knowledge of XML/Emacs could put it into the right
format. I am not unwilling to learn XML/Emacs, but my time might be
spent better elsewhere."
This is very discouraging!!
Alexander,
Don't get discouraged; it's not nearly as hard as it seems... and
believe me, my first reaction was *exactly* the same. I am more than
happy to help move stuff to XML, but I would encourage you to give this
a try. All you need to do is:
1. Make sure you have the "Authoring and Publishing" component (from
redhat-config-packages), Emacs (in the "Editors" component), and the
psgml package installed.
2. Follow the Documentation Guide to set up your ~/.emacs,
parse/save/load the DTD, etc. I found it easiest to simply make a copy
of the example-tutorial/ folder and then strip out the content and start
from there.
There's not that many keystrokes you need to learn to use Emacs
effectively in this way, but I will be the first to admit I still find
it cumbersome. I tend to use... er, that other editor. :-) In any case,
if I was better at this sort of thing I would try and make this work in
LyX, which is so much easier to use it's ridiculous. As Karsten (I
think) mentioned, the hard part is getting your tool of choice to write
everything to file the same way as everyone else, so that when we move
to a community repository, no one is stepping on others' toes.
To reiterate though, I will be happy to edit XML if you decide this is
too painful. :-)
--
Paul W. Frields, RHCE
8:12 a.m.
That's great thanks.
But the anaconda docs volunteer group needs to agree on a way of doing it:
1. Are we going to use the documentation project way or
2. are we using Akbar's sourceforge page?
Any thoughts?
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Paul W. Frields
Sent: 21 November 2003 09:01
To: fedora-docs-list(a)redhat.com
Subject: RE: Anaconda documents
On Thu, 2003-11-20 at 15:14, Alexander Rau (work) wrote:
Took my lunch break to look into the creation of fedora-docs. And I
have
to
agree with Taylor:
"Taking a look at the Documentation project site, I see that I need
Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
learning curve for these? I have never done XML, and I am not an Emacs
user (sorry to start a flamewar). Perhaps I could write the text and
someone with more knowledge of XML/Emacs could put it into the right
format. I am not unwilling to learn XML/Emacs, but my time might be
spent better elsewhere."
This is very discouraging!!
Alexander,
Don't get discouraged; it's not nearly as hard as it seems... and
believe me, my first reaction was *exactly* the same. I am more than
happy to help move stuff to XML, but I would encourage you to give this
a try. All you need to do is:
1. Make sure you have the "Authoring and Publishing" component (from
redhat-config-packages), Emacs (in the "Editors" component), and the
psgml package installed.
2. Follow the Documentation Guide to set up your ~/.emacs,
parse/save/load the DTD, etc. I found it easiest to simply make a copy
of the example-tutorial/ folder and then strip out the content and start
from there.
There's not that many keystrokes you need to learn to use Emacs
effectively in this way, but I will be the first to admit I still find
it cumbersome. I tend to use... er, that other editor. :-) In any case,
if I was better at this sort of thing I would try and make this work in
LyX, which is so much easier to use it's ridiculous. As Karsten (I
think) mentioned, the hard part is getting your tool of choice to write
everything to file the same way as everyone else, so that when we move
to a community repository, no one is stepping on others' toes.
To reiterate though, I will be happy to edit XML if you decide this is
too painful. :-)
--
Paul W. Frields, RHCE
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
1:14 p.m.
>>>> "Alexander" == Alexander Rau (work)
<arau(a)schleese.com> writes:
Alexander> That's great thanks. But the anaconda docs volunteer group
Alexander> needs to agree on a way of doing it:
Alexander> 1. Are we going to use the documentation project way or 2. are
Alexander> we using Akbar's sourceforge page?
Alexander> Any thoughts?
Well, since you asked, here's my $0.02... ;-)
My feeling is that if you want to get started *right now*, you could go
with Akbar's solution. Long-term, though, you'd probably want to move to
the project's CVS server, as this would simplify integrating your
documentation with the distribution proper...
Ed
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
1:33 p.m.
Ed:
Thanks for your $0.02 and I think you are right to think longterm if the
project should succeed.
Here is a problem I have and I know I will get ripped apart for that:
I mostly have time in between projects at work (while the network is doing
maintenance or the server is being backed up...). Unfortunately, I have not
been able to convince management to implement Linux in our workstations (we
have one server running linux). So when I get a window of opportunity to
participate I am sitting on M$ windowz machine. Are/is the tools/software
available for M$ XP?
In order for me to participate the submission process needs to be hassle
free and hopefully available for a M$ environment.
Thanks
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Edward C. Bailey
Sent: 21 November 2003 14:15
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
>>>> "Alexander" == Alexander Rau (work)
<arau(a)schleese.com> writes:
Alexander> That's great thanks. But the anaconda docs volunteer group
Alexander> needs to agree on a way of doing it:
Alexander> 1. Are we going to use the documentation project way or 2. are
Alexander> we using Akbar's sourceforge page?
Alexander> Any thoughts?
Well, since you asked, here's my $0.02... ;-)
My feeling is that if you want to get started *right now*, you could go
with Akbar's solution. Long-term, though, you'd probably want to move to
the project's CVS server, as this would simplify integrating your
documentation with the distribution proper...
Ed
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
1:51 p.m.
On Fri, 2003-11-21 at 11:33, Alexander Rau (work) wrote:
Ed:
Thanks for your $0.02 and I think you are right to think longterm if the
project should succeed.
Here is a problem I have and I know I will get ripped apart for that:
I mostly have time in between projects at work (while the network is doing
maintenance or the server is being backed up...). Unfortunately, I have not
been able to convince management to implement Linux in our workstations (we
have one server running linux). So when I get a window of opportunity to
participate I am sitting on M$ windowz machine. Are/is the tools/software
available for M$ XP?
In order for me to participate the submission process needs to be hassle
free and hopefully available for a M$ environment.
If, like Ed said, they are going to use a CVS repository, you will be
able to get the tools for Microsoft Windows. I recommend you get cygwin
from http://www.cygwin.com, and install cvs. Cygwin is a command-line
terminal for MS Windows. You can install ssh, vi, emacs, cvs, etc. on
your workstation. I have also seen people use WinCVS
(http://www.wincvs.org/), which is a GUI frontend for CVS.
Forrest
--
11:59 a.m.
At 19:51 21/11/2003, you wrote:
> In order for me to participate the submission process needs to
be hassle
> free and hopefully available for a M$ environment.
If, like Ed said, they are going to use a CVS repository, you will be
able to get the tools for Microsoft Windows. I recommend you get cygwin
from http://www.cygwin.com, and install cvs.
CVS can be driven from win32 OS's.
Cygwin is an option,
there are others for those that are Redmond bound, for whatever reason.
emacs, docbook etc all work well too surprisingly.
regards DaveP
2 p.m.
Alexander Rau (work) wrote:
Are/is the tools/software
available for M$ XP?
vmware? m$ virtual pc? (running linux)
and does anyone know if 'conglomerate' is at a useable state yet for
working on the doc? It looks like a promising project and it seems like
it could make things alot easier regarding writing the doc.
i would also like to say that i would probably serve the project better
as a proof-reader, rather than creating sections for the doc. My
experience with anaconda was limited and it was a while ago. However i'm
keen to learn more and offer my help in whatever way i can. Call on me
when you need me ...
2:06 p.m.
>>>> "Alexander" == Alexander Rau (work)
<arau(a)schleese.com> writes:
Alexander> Ed: Thanks for your $0.02 and I think you are right to think
Alexander> longterm if the project should succeed.
Well, I'm a bit more hopeful than that. :-) Besides, whether people
outside of Red Hat believe it or not, the Fedora project is considered
*vitally* important to Red Hat's future. I've have seen comments by people
claiming that Fedora Core is "abandonware", but I can state that this is
categorically untrue.
Alexander> Here is a problem I have and I know I will get ripped apart for
Alexander> that:
Alexander> I mostly have time in between projects at work (while the
Alexander> network is doing maintenance or the server is being backed
Alexander> up...). Unfortunately, I have not been able to convince
Alexander> management to implement Linux in our workstations (we have one
Alexander> server running linux). So when I get a window of opportunity to
Alexander> participate I am sitting on M$ windowz machine. Are/is the
Alexander> tools/software available for M$ XP?
A quick google on "windows cvs client" returns some interesting hits. ;-)
I have also seen posts on various Emacs-related newsgroups about people
using Emacs under Windows, so the basics are covered.
As for validating and/or producing HTML from XML on your Windows box, I
don't know, but even if you couldn't do this yourself, I would imagine that
you could pair up with someone with the necessary environment to help
you...
And to be honest, if you let psgml-mode (or that other mode mentioned here
whose name I don't recall) handle insertion of tags and atrributes for you,
validation errors should be relatively few and far between.
Ed
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
4:29 p.m.
Besides, whether people outside of Red Hat believe it or not, the
Fedora project is considered *vitally* important to Red Hat's >future.
From what I've seen, alot of these are scoffers who have not even
seen a
single Fedora screenshot. When I installed yarrow, I was amazed and
still am at how much RedHat it is. From my use, I don't see any changes
except for enhancements. I use it as my day to day OS in a Windows
environment at work, which includes document collaboration, development,
and meetings.
Alexander>I have not been able to convince management to implement
Alexander>Linux in our workstations (we have one server running
Alexander>linux). So when I get a window of opportunity to
Alexander>participate...
I salute you... That is what I have been trying to. I have helped with
some dual boot installations and some people have even taken my
installation CD's home to install at home, but I'm trying to show that a
linux workstation can plug right in.
On Fri, 2003-11-21 at 14:06, Edward C. Bailey wrote:
>>>>> "Alexander" == Alexander Rau (work)
<arau(a)schleese.com> writes:
Alexander> Ed: Thanks for your $0.02 and I think you are right to think
Alexander> longterm if the project should succeed.
Well, I'm a bit more hopeful than that. :-) Besides, whether people
outside of Red Hat believe it or not, the Fedora project is considered
*vitally* important to Red Hat's future. I've have seen comments by people
claiming that Fedora Core is "abandonware", but I can state that this is
categorically untrue.
Alexander> Here is a problem I have and I know I will get ripped apart for
Alexander> that:
Alexander> I mostly have time in between projects at work (while the
Alexander> network is doing maintenance or the server is being backed
Alexander> up...). Unfortunately, I have not been able to convince
Alexander> management to implement Linux in our workstations (we have one
Alexander> server running linux). So when I get a window of opportunity to
Alexander> participate I am sitting on M$ windowz machine. Are/is the
Alexander> tools/software available for M$ XP?
A quick google on "windows cvs client" returns some interesting hits. ;-)
I have also seen posts on various Emacs-related newsgroups about people
using Emacs under Windows, so the basics are covered.
As for validating and/or producing HTML from XML on your Windows box, I
don't know, but even if you couldn't do this yourself, I would imagine that
you could pair up with someone with the necessary environment to help
you...
And to be honest, if you let psgml-mode (or that other mode mentioned here
whose name I don't recall) handle insertion of tags and atrributes for you,
validation errors should be relatively few and far between.
Ed
5:48 p.m.
Alexander Rau (work) wrote:
In order for me to participate the submission process needs to be
hassle
free and hopefully available for a M$ environment.
There is no problem in using these tools from Windows AFAIK. You can
download GNU Emacs for Windows from here:
http://ftp.gnu.org/gnu/windows/emacs/
I also like Textpad. It's not free, but at $25 who's complaining. It has
the ability to do Unix \r\n end of line characters.
Also, you can setup WinCVS for CVS access. All of the Windows developers
at Delixus (my company) use WinCVS and find it very easy to use.
You can download WinCVS from here:
http://www.wincvs.org/download.html
- Akbar
2:13 a.m.
On Fri, 2003-11-21 at 11:33, Alexander Rau (work) wrote:
In order for me to participate the submission process needs to be
hassle
free and hopefully available for a M$ environment.
Well, that's a difficult request; however, if M$ would just release
their source code under a truly free license, then we could make
building Fedora documentation under Windows hassle free. :-) ;-)
If you have access to a Linux box from remote, such as one running at
your home on broadband, you could try this method:
1. If you don't have an SSH client supplied on your Windows machine by
your employer, grab a copy of PuTTY
(http://www.chiark.greenend.org.uk/~sgtatham/putty/); this FL/OSS
application has an SSH client, does SFTP, SCP and can support SSH tricks
such as tunneling.
2. Shell into a remote Linux box (such as a Fedora Core install) where
you have the FDP toolchain running.
3. Run your Emacs session as 'emacs -nw'; if you run it in a screen
session, you provide yourself good protection against network or Windows
problems messing up your work (see the screen manual page for more
information).
The best things about this method?
* Your work is protected from any number of problems which are more
likely to occur than a Fedora box going down -- network problems, power
outages, Windows BSOD, etc.
* The setup is considerably easier than getting cygwin, Emacs, cvs and
ssh running under Win32.
* You are safely doing your personal volunteer work on a remote system
under your control, and not belonging to your employer. Then they have
a harder time, for example, claiming copyright over anything you write
while "on the clock".
Of course, IANAL, so don't take this as advice on how to work on
personal projects while on your employer's time. ^o_O^
- Karsten
--
Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664
kwade(a)redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995
Red Hat Enterprise Applications : WAF, CMS, Portal Server
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
12:06 p.m.
At 08:13 24/11/2003, Karsten Wade wrote:
On Fri, 2003-11-21 at 11:33, Alexander Rau (work) wrote:
> In order for me to participate the submission process needs to be hassle
> free and hopefully available for a M$ environment.
Well, that's a difficult request;
I've never found sharing XML instances with Linux users and windows users
hard work.
Its one advantage of XML.
If you have access to a Linux box from remote, such as one running at
your home on broadband, you could try this method:
3. Run your Emacs session as 'emacs -nw'; if you run it in a
screen
session, you provide yourself good protection against network or Windows
problems messing up your work (see the screen manual page for more
information).
Putty is pretty good at screwing up a display. Particularly if
utf-8 is used.
* The setup is considerably easier than getting cygwin, Emacs, cvs
and
ssh running under Win32.
emacs runs happily under windows.
If anyone has a problem setting it up I've been there done that.
Both for psgml and nxml-mode
regards DaveP
1:34 p.m.
On Fri, 2003-11-21 at 11:14, Edward C. Bailey wrote:
>>>>> "Alexander" == Alexander Rau (work)
<arau(a)schleese.com> writes:
Alexander> That's great thanks. But the anaconda docs volunteer group
Alexander> needs to agree on a way of doing it:
Alexander> 1. Are we going to use the documentation project way or 2. are
Alexander> we using Akbar's sourceforge page?
Alexander> Any thoughts?
Well, since you asked, here's my $0.02... ;-)
My feeling is that if you want to get started *right now*, you could go
with Akbar's solution. Long-term, though, you'd probably want to move to
the project's CVS server, as this would simplify integrating your
documentation with the distribution proper...
I agree. For now, let's go with Akbar's SourceForge repository, and we
will move it over to Fedora Project CVS when Red Hat gets it setup.
Forrest
--
3:58 p.m.
I basically wrote my notes in the TOC, but this is what I have. I added
the notes from Alexander, and I have question marks near the things that
I don't know about.
Forrest
TOC
I.Introduction
Red Hat Installation Program (Anaconda)
Anaconda is the installation program for Red Hat distributions. During
installation, the system's hardware is identified and configured, and
the appropriate file systems for the system's architecture are created.
Finally, it allows the user to install the operating system software on
the system. Optionally, it can upgrade existing Red Hat installations.
Anaconda can run in a fully interactive mode (text or graphical), or in
a kickstart mode, which is allows the installation to be scripted for
unattended operation. This makes deploying hundreds or thousands of
systems very easy. Anaconda is written in Python and C, and is
distributed under the GPL. The graphical frontend is written with
PyGtk. Using a scripting language (Python) for the majority of the code
allows for easily distribution of updates and the quick development of
new features.
II.How anaconda works
A. boot process
B. actual anaconda process
i. probing for hardware (what is happening behind the scenes/what
programs are doing what)
ii. language selection
iii. harddrive setup
III. Installation
IV. What is needed to rebuild anaconda
A. Disk space 30-45 MB
B. Required packages
i. rpm-build (for /usr/src/redhat/*)
ii. pump-devel (add something for RHEL about missing -devel
packages)
iii. kudzu-devel, pciutils-devel, bzip2-devel, e2fsprogs-devel,
python-devel, gtk2-devel, rpm-python, newt-devel, rpm-devel, gettext,
modutils-devel, rhpl, booty, libxml2-python, zlib-devel, bogl-devel,
bogl-bterm, elfutils-devel, beecrypt-devel, dietlibc, parted (plus
dependencies: Xfree86-devel, atk-devel, glib2-devel, pango-devel, bogl,
gd, fontconfig-devel, freetype-devel)
C. Required patches
i. Patch for buildinstall (dies when trying to run buildinstall the
second time)
ii. Patch for changing RedHat to Fedora
iii. Patch for new files (build-fc1, mkfedora-cd*, etc.)
D. Time (on my Intel Pentium III 600 Mhz processor 256 MB RAM)
i. rpmbuild -bp anaconda.spec – 0:11
ii. rpmbuild -bb anaconda.spec – 4:48
iii. rpmbuild -ba anaconda.spec – 4:49
V. Tree structure – about 2GB for the distribution without SRPMS (4GB
with SRPMS), plus another 2GB (4GB with SRPMS) for the iso images.
A. /fedora (I usually create a directory in a partition that has
room, and then create a symlink for /fedora)
B. /fedora/i386 – RPM packages
C. /fedora/SRPMS – SRPM packages
D. /fedora/build-fc1 – build script
E. /fedora/new/new – directory for new and updated packages
F. /fedora/RHupdates – directory for testing updated anaconda files
VI. Anaconda binaries (just quick explanation with details in later
chapters)
A. buildinstall – script that builds the distribution
B. checkcards.py – ??
C. checkisomd5 – see implantiosmd5
D. check-repository.py – old script that was used to check the
repository for missing dependencies – we need to check if this still
works FIX-ME It does not work for me even after changing RedHat to
Fedora. It seems to need the original comps file (not comps.xml). Talk
to Jeremy about getting it removed or replaced.
E. filtermoddeps – ??
F. genhdlist – script that generated the hdlist (you must use the
full path to your directories)
G. getkeymaps – ??
H. implantiosmd5/checkisomd5 – script to implant/check the md5 sum
used during installation to verify the discs (mediacheck boot option)
I. libunicode-lite.so.1 – some library
J. loader/ – directory that contains the loader programs
K. makestamp.py – script that makes the .discinfo?
L. mapshdr – ??
M. mk-images* – architecture-specific scripts that are called by
buildinstall
N. mk-rescueimage.i386 – creates the rescue image?
O. moddeps – modify dependencies?
P. modlist – modify list?
Q. pkgorder – creates a package order—now called by buildinstall
R. pyiosmd5sum.so – used by implantiosmd5/checkisomd5?
S. pythondeps – python dependencies
T. readmap – Read map?
U. screenfont-i386.gz – fonts for the installer?
V. scrubtree – scrub the installation tree—called by buildinstall
W. splittree.py – formerly splitdistro—used to split the distribution
into discs
X. trimmodmap/trimpcitable – trim the modmap/pcitable?
Y. upd-instroot – called by buildinstall—actual function??
Z. EXTRAS (that I use)
i. build-fc1 – runs the needed scripts to generate a distribution
ii. mkdvd – creates a DVD iso image
iii. mkfedora-cd* – creates CD iso images
iv. rpmupdates – copies the new/updated RPMs in /fedora/new/new to
the installation area and moves out the old RPMs.
VII. Mini HowTo editing and making rpms from source
A. We need to decide if we are going to encourage using root to
rebuild, or if we should document how to setup a build environment for a
standard user. We have to be root to install rpms, so I guess that we
should just do it as root
B. Remove debug packages
i. echo "%debug_package %{nil}" >> /root/.rpmmacros
C. Let's show an example for anaconda
i. Install the source rpm file
a) rpm -ivh anaconda-9.2-2.src.rpm (notice the src.rpm
extension)
ii. Rebuild the original anaconda with any patches included
a) cd /usr/src/redhat/SPEC
b) rpmbuild -bp anaconda.spec
iii. Go to the BUILD directory and make a copy of the original
directory
a) cd /usr/src/redhat/BUILD
b) cp -a anaconda-9.0 anaconda-9.0.orig
iv. Make your changes in the anaconda-9.0 directory
v. Return to the BUILD directory and make a patch of the changes
a) cd /usr/src/redhat/BUILD
b) diff -urN anaconda-9.0.orig anaconda-9.0 > \
../SOURCES/my-changes.patch
vi. Edit the spec file and rebuild
a) cd /usr/src/redhat/SPECS
b) Edit anaconda.spec
Below Source: anaconda-%{PACKAGE_VERSION}.tar.bz2, add this
line:
Patch1: my-changes.patch
Below %setup -q, add this line:
%patch1 -p1
Below %changelog, add a few lines about what you did, using
the same format as you see there. You will need to change
the %{date} (if it exists) to a real date. To get the real
date that it was created, run this command and replace the
%{date} line with this output (this is the output that I get)
rpm -qp --changelog anaconda-9.2-2.src.rpm | head -1
* Thu Oct 30 2003 Anaconda team <bugzilla(a)redhat.com>
c) rpmbuild -ba anaconda.spec
This will create the anaconda source rpm in
/usr/src/redhat/SPMS, and the anaconda and
anaconda-runtime i386.rpm files in
/usr/src/redhat/RPMS/i386 (assuming that you use x86)
d) Copy the binary files to /fedora/new/new, and the source file
to /fedora/SRPMS. Run rpmupdates to copy the new files to
the installation tree.
VIII. Set up your build environment (tree structures needed and so on)
A. Look at V.
IX. The comps.xml chapter (explanation and making your own comps.xml)
A. Formerly, we had the comps tarball as explained on the anaconda
site, but now, it looks like we should just edit
/fedora/i386/base/comps.xml directly.
X. Step by step walkthrough the whole buildinstall process
A. Running build-fc1
B. Time to build (35 minutes on my Dual Intel Pentium III 500MHz with
1GB RAM)
XI. Splitting distros
A. I have a seperate script for this.
i. rm -rf i386-disc[123456789] (otherwise splittree.py will
complain)
ii. splittree.py --arch=i386 --total-discs=3 --bin-discs=3 \
--src-discs=1 --release-string=”Fedora Core 1”
--pkgorderfile=pkgfile --distdir=i386 --srcdir=SRPMS
--productpath=Fedora
XII. burning distros mkisofs
A. I use a script for mkisofs
i. genhdlist --withnumbers --fileorder pkgfile \
/fedora/i386-disc[123]
ii. mkisofs -b isolinux/isolinux.bin -c isolinux/boot.cat -J -p \
“my(a)email.address.xn--com-9o0a -V “Fedora Core 1 with updates disc 1” \
-r -T -v -A “Fedora Core Linux/i386 1” \
fedoracore1-disc1.iso -no-emul-boot -boot-load-size 4 \
-boot-info-table i386-disc1
iii. implantisomd5 --supported-iso fedoracore1-disc1.iso
B. I use xcdroast to burn the iso images—recommend using CD-RWs
XIII. How to test anaconda without burning discs
A. anaconda --test -m nfs:/fedora/i386 (you don't need to run an
NFS server for this to work, although it is easy to setup NFS and it is
easy to do a network installation)
XIV. Links and useful tools
XV. Acknowledgements
A. Jeremy Katz, et al.
B. Alexander Rau
11:11 a.m.
Taylor:
Your TOC is fantastic. It gets better by the minute.
We desperately need a central repository to get properly started. It looks
like everybody is highly motivated but without the proper setup I am worried
the wind in our sails will be dying down soon.
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Taylor, ForrestX
Sent: 21 November 2003 16:59
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
I basically wrote my notes in the TOC, but this is what I have. I added
the notes from Alexander, and I have question marks near the things that
I don't know about.
Forrest
TOC
I.Introduction
Red Hat Installation Program (Anaconda)
Anaconda is the installation program for Red Hat distributions. During
installation, the system's hardware is identified and configured, and
12:09 p.m.
Yes, I agree. Our enthusiasm will curb shortly. I have requested a new
project on savannah.gnu.org. They should let us know today if we can
host it there. I'll let you know as soon as I hear anything. Hopefully
we'll be able to find a site to host this on so that Akbar does not have
to host it individually.\
Forrest
--
On Mon, 2003-11-24 at 09:11, Alexander Rau (work) wrote:
Taylor:
Your TOC is fantastic. It gets better by the minute.
We desperately need a central repository to get properly started. It looks
like everybody is highly motivated but without the proper setup I am worried
the wind in our sails will be dying down soon.
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Taylor, ForrestX
Sent: 21 November 2003 16:59
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
I basically wrote my notes in the TOC, but this is what I have. I added
the notes from Alexander, and I have question marks near the things that
I don't know about.
Forrest
TOC
I.Introduction
Red Hat Installation Program (Anaconda)
Anaconda is the installation program for Red Hat distributions. During
installation, the system's hardware is identified and configured, and
12:41 p.m.
Guys,
I missed the initial discussion about Abkar and Sourceforge, but I could
create a new directory in my CVS repository at kickstart-tools.sf.net.
I would then have to add folks to the kickstart-tools project and allow
you to commit into that new directory.
Thoughts?
/Brian/
On Mon, 2003-11-24 at 12:11, Alexander Rau (work) wrote:
Taylor:
Your TOC is fantastic. It gets better by the minute.
We desperately need a central repository to get properly started. It looks
like everybody is highly motivated but without the proper setup I am worried
the wind in our sails will be dying down soon.
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Taylor, ForrestX
Sent: 21 November 2003 16:59
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
I basically wrote my notes in the TOC, but this is what I have. I added
the notes from Alexander, and I have question marks near the things that
I don't know about.
Forrest
TOC
I.Introduction
Red Hat Installation Program (Anaconda)
Anaconda is the installation program for Red Hat distributions. During
installation, the system's hardware is identified and configured, and
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
--
Brian Long | | |
Americas IT Hosting Sys Admin | .|||. .|||.
Cisco Linux Developer | ..:|||||||:...:|||||||:..
Phone: (919) 392-7363 | C i s c o S y s t e m s
1:26 p.m.
Let's wait till Taylor hears back from savannah.gnu.org!?
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Brian Long
Sent: 24 November 2003 13:42
To: fedora-docs-list(a)redhat.com
Cc: forrestx.taylor(a)intel.com
Subject: RE: Anaconda documents
Guys,
I missed the initial discussion about Abkar and Sourceforge, but I could
create a new directory in my CVS repository at kickstart-tools.sf.net.
I would then have to add folks to the kickstart-tools project and allow
you to commit into that new directory.
Thoughts?
/Brian/
1:52 p.m.
Alexander Rau (work) wrote:
Let's wait till Taylor hears back from savannah.gnu.org!?
Brian Long wrote:
I missed the initial discussion about Abkar and Sourceforge, but I
could
create a new directory in my CVS repository at kickstart-tools.sf.net.
I would then have to add folks to the kickstart-tools project and allow
you to commit into that new directory.
Just let me know what you'd like to do. I have the hardware ready and
the OS installed. CVS pserver is up and running and I'm just working on
locking it down. Should be finished today, but the gnu or sf sites would
probably be better hosts. So, if either of those are possibilities then
they would take priority over my solution.
Thanks,
Akbar
2:09 p.m.
Could we get started on yours and then transfer it over to whoever is able
to host the project?
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Akbar S. Ahmed
Sent: 24 November 2003 14:52
To: fedora-docs-list(a)redhat.com
Cc: forrestx.taylor(a)intel.com; 'Brian Long'
Subject: Re: Anaconda documents
Alexander Rau (work) wrote:
Let's wait till Taylor hears back from savannah.gnu.org!?
Brian Long wrote:
I missed the initial discussion about Abkar and Sourceforge, but I
could
create a new directory in my CVS repository at kickstart-tools.sf.net.
I would then have to add folks to the kickstart-tools project and allow
you to commit into that new directory.
Just let me know what you'd like to do. I have the hardware ready and
the OS installed. CVS pserver is up and running and I'm just working on
locking it down. Should be finished today, but the gnu or sf sites would
probably be better hosts. So, if either of those are possibilities then
they would take priority over my solution.
Thanks,
Akbar
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
2:20 p.m.
On Mon, 2003-11-24 at 11:52, Akbar S. Ahmed wrote:
Alexander Rau (work) wrote:
> Let's wait till Taylor hears back from savannah.gnu.org!?
Brian Long wrote:
> I missed the initial discussion about Abkar and Sourceforge, but I could
> create a new directory in my CVS repository at kickstart-tools.sf.net.
> I would then have to add folks to the kickstart-tools project and allow
> you to commit into that new directory.
Just let me know what you'd like to do. I have the hardware ready and
the OS installed. CVS pserver is up and running and I'm just working on
locking it down. Should be finished today, but the gnu or sf sites would
probably be better hosts. So, if either of those are possibilities then
they would take priority over my solution.
If you can get your solution setup today, let's start it there, and we
can move it to savannah if/when it gets approved. As Alexander pointed
out, the sooner we get this started, the better.
Thanks,
Forrest
5:41 p.m.
Taylor, ForrestX wrote:
I agree. For now, let's go with Akbar's SourceForge
repository, and we
will move it over to Fedora Project CVS when Red Hat gets it setup.
So here's the scoop, Sourceforge rejected the project for some reason
(their site does not say why). I'm going to setup a server here, but
I'll need a day or two to get hardware, configure everything, etc.
Sorry about the delay.
Thanks,
Akbar
8:26 p.m.
On Fri, 2003-11-21 at 06:36, Karsten Wade wrote:
One editor I am keeping my eye on is http://www.conglomerate.org/.
They
are thinking in novel ways that make using a GUI editor tempting.
OpenOffice.org can export as an XML based document, as long as you have
the Java stuff compiled in (so a default Fedora install will not be able
to do it; either get the src.rpm's and recompile, or go ahead and
download from www.openoffice.org).
Is the support from OpenOffice.org's DocBook XML export feature good
enough?
--
Colin Charles, byte(a)aeon.com.my
http://www.bytebot.net/
11:49 a.m.
At 19:36 20/11/2003, Karsten Wade wrote:
> Are there non-Emacs solutions available for this??
Any editor will suffice, but unless you have an intimate knowledge of
DocBook XML, you will find it difficult to use an editor which does not
have a mode similar to PSGML or nXML.
What might help is
www.docbook.org
http://www.docbook.org/tdg/en/html/docbook.html
specifically.
Helps with markup.
regards DaveP
2:52 p.m.
On Thu, 2003-11-20 at 13:02, Tom Diehl wrote:
> Taking a look at the Documentation project site, I see that I
need
> Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the
> learning curve for these? I have never done XML, and I am not an Emacs
> user (sorry to start a flamewar). Perhaps I could write the text and
> someone with more knowledge of XML/Emacs could put it into the right
> format. I am not unwilling to learn XML/Emacs, but my time might be
> spent better elsewhere.
Are there non-Emacs solutions available for this??
I hadn't used Emacs or PSGML before trying them for this project; it is
not too hard to learn. If you follow the Documentation Guide up at the
Fedora pages, that's the best intro available right now for that
toolbox, at least insofar as it concerns FDP. Also you can try out the
RPM available at:
ftp://people.redhat.com/twaugh/docbook/nxml-mode
This makes the process a little easier and more automated, apparently. I
don't particularly enjoy writing markup like this, and think it would be
great if someone got templates for OO.o or LyX that worked correctly for
the FDP, but I've got the hang of it under Emacs at this point. I've
already written a very short updfstab tutorial. If someone would like me
to edit their document and do the markup, let me know and I'll be happy
to help. Furthermore, if anyone is interested in making OO.o or LyX work
for FDP, we could try that too.
The hardest part of the process, IMHO, is remembering where you need to
use the markups. The way I'm getting used to it is assuming that anytime
I need to make a point, there's probably a markup available. Then it
just becomes a task of (1) finding the most appropriate one, and (2)
trying to remember it for next time.
--
Paul W. Frields, RHCE
3:30 p.m.
On Thu, 2003-11-20 at 12:52, Paul W. Frields wrote:
I hadn't used Emacs or PSGML before trying them for this project;
it is
not too hard to learn. If you follow the Documentation Guide up at the
Fedora pages, that's the best intro available right now for that
toolbox, at least insofar as it concerns FDP. Also you can try out the
RPM available at:
ftp://people.redhat.com/twaugh/docbook/nxml-mode
This makes the process a little easier and more automated, apparently. I
don't particularly enjoy writing markup like this, and think it would be
great if someone got templates for OO.o or LyX that worked correctly for
the FDP, but I've got the hang of it under Emacs at this point. I've
already written a very short updfstab tutorial. If someone would like me
to edit their document and do the markup, let me know and I'll be happy
to help. Furthermore, if anyone is interested in making OO.o or LyX work
for FDP, we could try that too.
The hardest part of the process, IMHO, is remembering where you need to
use the markups. The way I'm getting used to it is assuming that anytime
I need to make a point, there's probably a markup available. Then it
just becomes a task of (1) finding the most appropriate one, and (2)
trying to remember it for next time.
Thanks for your experience and volunteering to help. We may take you up
on your offer to markup the document ;o)
Since you didn't think that it was too difficult, I'll grab the docs and
try out Emacs/XML.
For those who want to help with anaconda, let's start with Alexander's
TOC, and go from there.
Forrest
3:54 p.m.
It would be great if we had one destination where we could collect on
publish our working documents
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Taylor, ForrestX
Sent: 20 November 2003 16:30
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
On Thu, 2003-11-20 at 12:52, Paul W. Frields wrote:
I hadn't used Emacs or PSGML before trying them for this project;
it is
not too hard to learn. If you follow the Documentation Guide up at the
Fedora pages, that's the best intro available right now for that
toolbox, at least insofar as it concerns FDP. Also you can try out the
RPM available at:
ftp://people.redhat.com/twaugh/docbook/nxml-mode
This makes the process a little easier and more automated, apparently. I
don't particularly enjoy writing markup like this, and think it would be
great if someone got templates for OO.o or LyX that worked correctly for
the FDP, but I've got the hang of it under Emacs at this point. I've
already written a very short updfstab tutorial. If someone would like me
to edit their document and do the markup, let me know and I'll be happy
to help. Furthermore, if anyone is interested in making OO.o or LyX work
for FDP, we could try that too.
The hardest part of the process, IMHO, is remembering where you need to
use the markups. The way I'm getting used to it is assuming that anytime
I need to make a point, there's probably a markup available. Then it
just becomes a task of (1) finding the most appropriate one, and (2)
trying to remember it for next time.
Thanks for your experience and volunteering to help. We may take you up
on your offer to markup the document ;o)
Since you didn't think that it was too difficult, I'll grab the docs and
try out Emacs/XML.
For those who want to help with anaconda, let's start with Alexander's
TOC, and go from there.
Forrest
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
4:17 p.m.
Alexander Rau (work) wrote:
It would be great if we had one destination where we could collect
on
publish our working documents
I can think of three possible solutions:
1. Red Hat could open rw access to a CVS or Subversion repository (but
from the site it will be a while b4 this happens)
2. One of us could setup a server and give access to the others (I may
be able to help out here)
3. We could use a publicly accessible revision control repository such
as sourceforge
- Akbar
4:44 p.m.
On Thu, 2003-11-20 at 14:17, Akbar S. Ahmed wrote:
Alexander Rau (work) wrote:
> It would be great if we had one destination where we could collect on
> publish our working documents
I can think of three possible solutions:
1. Red Hat could open rw access to a CVS or Subversion repository (but
from the site it will be a while b4 this happens)
2. One of us could setup a server and give access to the others (I may
be able to help out here)
3. We could use a publicly accessible revision control repository such
as sourceforge
Yes, this is something that we need. Like you said, I don't think that
number 1 will happen anytime soon. Akbar, if you can set something up
for us, that would probably be the quickest. Do you want to use CVS or
a web page?
Forrest
--
5:36 p.m.
Hi Taylor,
Taylor, ForrestX wrote:
Akbar, if you can set something up
for us, that would probably be the quickest. Do you want to use CVS or
a web page?
I actually just setup a page for us on SourceForge.
Please sign up for an account here:
https://sourceforge.net/account/register.php
I have submitted a project and will email this list when we are given
approval. The reason I chose Sourceforge instead of setting up a server
myself is that this will give us greater visablity and I live in
Northern CA (the power does go out here ;). Plus we get everything we
need: CVS, web site, managed hosting, etc.
Our project is:
Descriptive name: Anaconda Documentation Project
Project name: anacondadocs
License: GNU Free Documentation License (FDL)
Public description: This project contains detailed documentation of
Anaconda, a Linux installer program, used by multiple Linux
distributions including Fedora, Mandrake, Delixus Linux, and RHEL.
Detailed instructions covering Anaconda usage and customization are
included.
Thanks,
Akbar
6:17 p.m.
That is fantastic!
Thanks Akbar
I am going through my notes now and we can reconvene tomorrow.
I guess our logo will be an anaconda (duuuh!) Any ideas?
I have a feeling that we are off to a good start and I am positive about the
project. There is a good caliber of people here.
AR
-----Original Message-----
From: fedora-docs-list-admin(a)redhat.com
[mailto:fedora-docs-list-admin@redhat.com] On Behalf Of Akbar S. Ahmed
Sent: Thursday, November 20, 2003 6:36 PM
To: fedora-docs-list(a)redhat.com
Subject: Re: Anaconda documents
Hi Taylor,
Taylor, ForrestX wrote:
Akbar, if you can set something up
for us, that would probably be the quickest. Do you want to use CVS or
a web page?
I actually just setup a page for us on SourceForge.
Please sign up for an account here:
https://sourceforge.net/account/register.php
I have submitted a project and will email this list when we are given
approval. The reason I chose Sourceforge instead of setting up a server
myself is that this will give us greater visablity and I live in
Northern CA (the power does go out here ;). Plus we get everything we
need: CVS, web site, managed hosting, etc.
Our project is:
Descriptive name: Anaconda Documentation Project
Project name: anacondadocs
License: GNU Free Documentation License (FDL)
Public description: This project contains detailed documentation of
Anaconda, a Linux installer program, used by multiple Linux
distributions including Fedora, Mandrake, Delixus Linux, and RHEL.
Detailed instructions covering Anaconda usage and customization are
included.
Thanks,
Akbar
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-docs-list
3:50 a.m.
On Thu, 2003-11-20 at 23:17, Akbar S. Ahmed wrote:
I can think of three possible solutions:
1. Red Hat could open rw access to a CVS or Subversion repository (but
from the site it will be a while b4 this happens)
This is a good idea... There's already a CVS repository intended for
translation purpouses, so maybe this one could be used for developing
new documentarion papers.
3:55 a.m.
On Fri, Nov 21, 2003 at 10:50:42AM +0100, Felipe Alfaro Solana wrote:
On Thu, 2003-11-20 at 23:17, Akbar S. Ahmed wrote:
> I can think of three possible solutions:
> 1. Red Hat could open rw access to a CVS or Subversion repository (but
> from the site it will be a while b4 this happens)
This is a good idea... There's already a CVS repository intended for
translation purpouses, so maybe this one could be used for developing
new documentarion papers.
This will happen AFAIK - see Sopwiths request for a few scripts on
fedora-devel-list to provide cvs/ssh/auth stuff.
Paul
1:07 p.m.
>>>> "Akbar" == Akbar S Ahmed
<akbar501(a)dslextreme.com> writes:
Akbar> Alexander Rau (work) wrote:
> It would be great if we had one destination where we could
collect on
> publish our working documents
Akbar> I can think of three possible solutions: 1. Red Hat could open rw
Akbar> access to a CVS or Subversion repository (but from the site it will
Akbar> be a while b4 this happens)
This is in the works (the hardware has been procured, and
configuration/location/etc is being worked on).
However, it is still going to take some time, as some big hurdles remain --
how to manage things on this machine, and how to keep things in sync with
existing internal Red Hat infrastructure, for instance...
Ed
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
7401
days inactive
7456
days old
65 comments
17 participants
participants (17)
-
Akbar S. Ahmed -
Alexander Rau (work) -
Brian Long (brilong) -
Colin Charles -
Dave Pawson -
Edward C. Bailey -
Felipe Alfaro Solana -
James Olin Oden -
Jonathan Villa -
Karsten Wade -
Paul Nasrat -
Paul Pianta -
Paul W. Frields -
Stefan Waidele jun. -
Tammy Fox -
Taylor, ForrestX -
Tom Diehl