July 2004 - docs - Fedora Mailing-Lists

by Colin Charles

Hi, We've been talking about public CVS for far too long, and I think the longer we wait, the longer Fedora Docs becomes less & less relevant Keeping in mind that the barrier of entry is already relatively high (you need to know DocBook, you need to use Emacs, etc...), this makes folk move closer to creating docs on 3rd party sites Why can't we use elvis.redhat.com ? Anaconda, translations and so on happen at elvis, so why not fedora docs? This will mean external contributors *can* commit to cvs as well Kind regards -- Colin Charles, byte(a)aeon.com.my http://www.bytebot.net/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

19 years, 9 months

11
25
0 / 0

fedora-entities - a proposal in the flesh

by Karsten Wade

This one has been on my to-do list for a while ... http://people.redhat.com/kwade/fedora-docs/common/fedora-entities-en.xml This works fine in my local tree, but since it includes entities required by the build scripts, it needs more QA. See below the Background section for implementation steps. # Background If you aren't familiar with the concept here, DocBook entities allow us to objectify common words and phrases that we want to use regularly, and be able to easily update from a single location. Entries look like this:  <!ENTITY FCVER "2">  <!ENTITY TESTVER "test1">  <!ENTITY FCTESTVER "3 &TESTVER;">  In the XML it appears like this: The information in this FAQ is specific to &FC; &FCTESTVER;. If you are looking for the FAQ for &FC; &FCVER; ... Which DocBook converts into: The information in this FAQ is specific to Fedora Core 3test1. If you are looking for the FAQ for Fedora Core 2 ... # Implementing To take advantage of this common entities file, we need to do the following: 1. If the common entities file is ready for submission, get it into CVS in fedora-docs/common. I'll be responsible for making this happen, ye gods willing. 2. Update your XML to use the common file by first removing the local versions of similar entities (leave in your true local entities), and adding this line: <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml"> %FEDORA-ENTITIES-EN; Note the relative path. Just like the build scripts, you are relying upon the various build directories in fedora-docs/ being in specific locations. The BOOKID entity is still set in each guide locally: <!ENTITY BOOKID "selinux-faq-1.3 (2004-07-30-T04:20-0800)">  I use a LOCALVER entity for the times when my guide is out of sync with the current FCVER or FCTESTVER in the common entities file. The LOCALVER would be used like this: <!ENTITY LOCALVER "3">  The information in this FAQ is relevant to &FC; &LOCALVER; only and not to the current or test release. 3. File bugzilla tickets for all the other guides in CVS that need to be updated to use the new common entities file. ## 30 - Karsten -- Karsten Wade, RHCE, Tech Writer this .signature subject to random changes http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41

19 years, 9 months

2
2
0 / 0

[Fwd: Creating a Fedora instllation boot floppy]

by Colin Charles

David, Consider dropping this to the fedora-docs-list(a)redhat.com as this is possibly a guide Regards -- Colin Charles, byte(a)aeon.com.my http://www.bytebot.net/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

19 years, 9 months

2
1
0 / 0

[Fwd: USB Key and Fedora Core 2/Gnome2.6 How-To]

by Colin Charles

Don't know if we can make this of use in the Docs Project, but it might be handy The author, and Tim has been CC'ed as well This adds to Tim Waugh's guide http://cyberelk.net/tim/usb-storage.html, and I think will make a good HOWTO/Guide for the docs project For FC3, we might want to touch on gamin as well -- Colin Charles, byte(a)aeon.com.my http://www.bytebot.net/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

19 years, 9 months

3
2
0 / 0

Fedora Doc List used as Help Desk

by redwire＠therockmere.com

I agree that we need to clarify the actual usage of this mailing list. But, as was mentioned in one of the preceding posts: there aren't any Published DOCS for Fedora. And, we are the DOCS link mentioned on the Fedora Main Page. Maybe if we released some documentation for posting to the Fedora Website we could negate a number of these 'request for help' type postings. Just my opinion. Brad p.s. I've been locked out of the CVS to retreive the examples. Can someone repost the synatax for getting the docs from CVS. Also, if I wasn't just imagining that I could D'L from the CVS if you could confirm that I'd sleep better at night. I have a doc on YUM conversion from RH9 to FC 1 or 2, but I can't finish cleaning it up until I can check the examples. TIA...Brad

19 years, 9 months

3
2
0 / 0

Problems using a wireless mouse unfer FC2

by Pablo

I´ve got a wireless USB keyboard + optical mouse in a machine running Fedora Core 2. Both devices are working perfectly. I can use the keyboard without any problem but I´m having a little trouble with the mouse. The pointer (cursor) moves perfectly -so the mouse is working- but I can´t click or use the wheel. I don´t really care about the wheel too much but no button is working. This doesn´t happen when I use a PS/2 optical mouse. And, finally, under Windowshit XP (in the same machine) it works perfectly... so, is nos the BIOS setting. And of course I played for a while with kudzu and system-config-mouse. What can I do? Is there a driver for that? Thanks. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

19 years, 9 months

6
13
0 / 0

what is ready for fedora.redhat.com

by Karsten Wade

Can we put together a list of what exactly is ready to post or change in either of the Docs pages at fedora.redhat.com? There are two categories: 1. Actual Documentation - http://fedora.redhat.com/docs These would be new documents or changes to existing documents. If you have specific bugzilla reports, post them. Perhaps bug reports, one for each document ready to post? I'll start the list: ## Documents Ready For Post and Maintenance Fedora Core 2 SELinux FAQ (in CVS) Fedora Core 3text1 SELinux FAQ (soon to be in CVS) 2. Docs Project - http://fedora.redhat.com/projects/docs/ Specific changes we should file as bugzilla reports, then report the bugzilla number back to this thread. If it's something for the FDP Documentation Guide, it needs a bugzilla number, and should be included in this category. - Karsten -- Karsten Wade, RHCE, Tech Writer this .signature subject to random changes http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41

19 years, 9 months

2
1
0 / 0

Test message

by Dave Pawson

-- Regards DaveP. XSLT&Docbook FAQ http://www.dpawson.co.uk/xsl

19 years, 10 months

1
0
0 / 0

Fedora Project Mailing Lists reminder

by Elliot Lee

This is a reminder of the mailing lists for the Fedora Project, and the purpose of each list. You can view this information at http://fedora.redhat.com/participate/communicate/ When you're using these mailing lists, please take the time to choose the one that is most appropriate to your post. If you don't know the right mailing list to use for a question or discussion, please contact me. This will help you get the best possible answer for your question, and keep other list subscribers happy! Mailing Lists Mailing lists are email addresses which send email to all users subscribed to the mailing list. Sending an email to a mailing list reaches all users interested in discussing a specific topic and users available to help other users with the topic. The following mailing lists are available. To subscribe, send email to <listname>-request(a)redhat.com (replace <listname> with the desired mailing list name such as fedora-list) with the word subscribe in the subject. fedora-announce-list - Announcements of changes and events. To stay aware of news, subscribe to this list. fedora-list - For users of releases. If you want help with a problem installing or using , this is the list for you. fedora-test-list - For testers of test releases. If you would like to discuss experiences using TEST releases, this is the list for you. fedora-devel-list - For developers, developers, developers. If you are interested in helping create releases, this is the list for you. fedora-docs-list - For participants of the docs project fedora-desktop-list - For discussions about desktop issues such as user interfaces, artwork, and usability fedora-config-list - For discussions about the development of configuration tools fedora-legacy-announce - For announcements about the Fedora Legacy Project fedora-legacy-list - For discussions about the Fedora Legacy Project fedora-selinux-list - For discussions about the Fedora SELinux Project fedora-de-list - For discussions about Fedora in the German language fedora-es-list - For discussions about Fedora in the Spanish language fedora-ja-list - For discussions about Fedora in the Japanese language fedora-i18n-list - For discussions about the internationalization of Fedora Core fedora-trans-list - For discussions about translating the software and documentation associated with the Fedora Project German: fedora-trans-de French: fedora-trans-fr Spanish: fedora-trans-es Italian: fedora-trans-it Brazilian Portuguese: fedora-trans-pt_br Japanese: fedora-trans-ja Korean: fedora-trans-ko Simplified Chinese: fedora-trans-zh_cn Traditional Chinese: fedora-trans-zh_tw

19 years, 10 months

1
0
0 / 0

Problems with my Lucent winmodem under FC2 !!!!

by Pablo

Hello... I'm having troubles installing my lucent winmodem under Fedora Core 2. I downloadad the lasta driver available from www.linmodem.org, succesfully compiled (with no errors at all). The symlinks are correct and both modules are generated. The problem is that the system doesn´t recognize the modules' format. Even when I try to install them with insmod or load the modules with modprobe I get an error message: "Unrecognized module format". Of course, with KPPP I cannot dial. The message is that the modem is busy when I try to use the /dev/modem port. I tryed with two different chipsets models (both supported by the driver) in two different computers (one AMD Athlon 2600+ with 512Mb. RAM and another Athlon Thunderbird 900Mhz. with 128Mb. RAM). Can anybody help me with this? I can´t see where´s the problem. I tryed several times and the compilation process is always succesful but the problem is always the same. Thank U.

19 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs July 2004