Slashdot Mirror

drfickle writes: "Although there has not yet been a formal announcement, David Merrill has stepped down as the Linux Documentation Project Collection Editor & Review Coordinator and appointed Joy Yokley Goodreau as his replacement. Joy has been very active in the LDP community for well over a year and has represented the LDP at many Linux conferences. She is an employee of the IBM Linux Technology Center on the LDoc team."

Guylhem writes: "The former LDP license was the first license used for our documentation. While we are now recommending the GNU FDL and the OPL 1 without options A or B, many documents are still licensed under the LDPL. David Merril, our Collection Coordinator, noticed that the LDPL is "not free" according to the Debian Free Software Guidelines. We have to get in touch with the authors as soon as possible or 2/3 of the LDP document collection will be removed from the base Debian distribution because the code freeze is happening in 2 days. Maybe some of the LDP unreachable authors are reading slashdot and could take 1 minute to submit an updated document licensed under the FDL or OPL v1 -A -B ? Another solution is to find volunteers to rewrite from scratch the concerned documents."

Guylhem writes: "The former LDP license was the first license used for our documentation. While we are now recommending the GNU FDL and the OPL 1 without options A or B, many documents are still licensed under the LDPL. David Merril, our Collection Coordinator, noticed that the LDPL is "not free" according to the Debian Free Software Guidelines. We have to get in touch with the authors as soon as possible or 2/3 of the LDP document collection will be removed from the base Debian distribution because the code freeze is happening in 2 days. Maybe some of the LDP unreachable authors are reading slashdot and could take 1 minute to submit an updated document licensed under the FDL or OPL v1 -A -B ? Another solution is to find volunteers to rewrite from scratch the concerned documents."

Guylhem writes: "The former LDP license was the first license used for our documentation. While we are now recommending the GNU FDL and the OPL 1 without options A or B, many documents are still licensed under the LDPL. David Merril, our Collection Coordinator, noticed that the LDPL is "not free" according to the Debian Free Software Guidelines. We have to get in touch with the authors as soon as possible or 2/3 of the LDP document collection will be removed from the base Debian distribution because the code freeze is happening in 2 days. Maybe some of the LDP unreachable authors are reading slashdot and could take 1 minute to submit an updated document licensed under the FDL or OPL v1 -A -B ? Another solution is to find volunteers to rewrite from scratch the concerned documents."

Guylhem writes: "The former LDP license was the first license used for our documentation. While we are now recommending the GNU FDL and the OPL 1 without options A or B, many documents are still licensed under the LDPL. David Merril, our Collection Coordinator, noticed that the LDPL is "not free" according to the Debian Free Software Guidelines. We have to get in touch with the authors as soon as possible or 2/3 of the LDP document collection will be removed from the base Debian distribution because the code freeze is happening in 2 days. Maybe some of the LDP unreachable authors are reading slashdot and could take 1 minute to submit an updated document licensed under the FDL or OPL v1 -A -B ? Another solution is to find volunteers to rewrite from scratch the concerned documents."

slick_rick asks: "I'm looking for info on encrypted file systems under Linux to help my employers company move away from Microsoft centric solutions. However the latest HOWTO is two years old, the latest kernel patch dates back to April (and 2.4.3) and even the Sourceforge project has nearly zero documentation and appears to be very dead. Are slashdotters using encrypted file systems? If so, what are your experiences?" We last talked about this topic, just over a year ago, in this article.

Jobe_br asks: "I've recently come across a need for a way of connecting to a SCO Unix box with full SCO-ANSI emulation (so that I can send F1-F12 commands and ASCII line art appears as lines, not strange foreign letters). After checking out the Terminal-HOWTO at linuxdoc.org I came away with no clearer understanding of what I need to do. I can pretty much pick any 'ole terminal emulator for win32 and get what I need, but no matter what I do to fiddle with my xterms/eterms/vts I can't get things to go. Is this not facilitated under Linux?"

Now chromatic has stepped through another couple of books, in addition to the nine in the previous parts of this series on books for the Linux newbie-to-semi-newbie. Actually, the selections this time go on the assumption that you've taken a few weeks (or some very intense days) to absorb the information you need to accomplish some basic tasks, and they take on the challenge of going beyond the basics. Note: here are links to part one, part two, and part three of this series.

(See below) author (Various) pages - publisher (Various) rating (vary) reviewer chromatic ISBN (varies) summary Books to take you beyond newbiehood comfortably.

As this series comes to a close, we move up a notch on the complexity scale to install Linux as a network client. Where some previous books have discussed how to make your new OS play nicely with others, here are two dedicated to helping you replace an existing box or setup a new server from scratch.

The eleven books we've featured barely scratch the surface of the printed documentation available for new Linux users. For example, O'Reilly has two particularly good choices, Learning Debian GNU/Linux, available through their Open Books Project, and Running Linux, reviewed last year.

We've obviously overlooked other worthy titles. For the sake of completeness, what else may come in handy? Which books have you found most useful?

title Linux Administration: A Beginner's Guide publisher Osborne Included Stuff RedHat 6.1 CD-ROM (Publishers Edition) Intended Audience NT Administrators new to Linux. Scope Installation, introduction to Linux, networking setup, Internet and intranet applications. Technical Correctness Good. Writing style Easy to read and informative. Other

Though this book comes with a RedHat CD, nearly everything can apply to other distributions.

Here's a book aimed squarely at the ranks of NT administrators. Not only does it point out (fairly) the differences between NT and Linux, but it explains the Linux method in relation to the NT method. (For example, compare NT file sharing via Network Neighborhood and SMB to NFS shares.) From a practical standpoint, professional experience is almost necessary to understand the initial concepts -- but it's certainly understandable without too much prior knowledge.

Shah starts with some background, then steps lightly through a RedHat 6.1 Server installation. X, KDE, and GNOME get basic treatment, mostly related to configuration. Software installation comes next, in both RPM and tarball (.tar.gz file) formats.

Section two covers basic administration. Users come first, with command line and Linuxconf tools presented. A good chapter introduces the shell and basic commands for file manipulation, processes, and permissions. Next up is the boot process, detailing LILO and the rc scripts. Basic file system theory, tools, partitioning schemes, mounting, and quotas get their due. The core system services chapter covers important daemons like the parent process, the Internet super daemon, system logging, and the cron scheduler. Shah rounds out this section by discussing kernel building, patching, and installing, and includes a good chapter on individual system security. (While brief, it's good and useful, including plenty of links to sites with much more information).

Internet Services looks at DNS, ftp, web, SMTP, POP, and SSH services. While there's theory given, it's accompanied by practical examples of setting up the appropriate software. BIND (for DNS) and wu-ftpd (for FTP) get excellent treatment, while the sendmail section is pared down (compared to Shah's chapter in the previously reviewed Red Hat Linux 6 Unleashed) and the Apache chapter is slim. That's not a problem with sendmail, as there's plenty of information provided to use the m4 macros, but a serious Apache configuration would require additional research. The section ends with a chapter on QPopper (providing POP3 access to users) and another discussing security and cryptography as related to SSH. Versions one and two of the protocol are covered, with information on running both.

Part four details intranet services. Here's how to make your Linux server speak eloquently on a larger network. NFS server and client setup takes up one chapter, and NIS server and client setup the next. The author sagely includes suggestions for different network configurations. Samba has a similar treatment, though the configuration section concentrates mostly on the SWAT web-configuration tool. A short chapter on printing includes accessing remote printers via SMB shares, while a quick DHCP chapter packs in a lot of information. Rounding things out is a quick look at backups, concentrating on command line tools like dump and tar.

The final section, entitled "Advanced Linux Networking", covers NIC configuration and routing, as well as TCP/IP theory. It's short, but effective. Somewhat longer is the chapter on packet filtering, ipchains, and IP Masquerading. There's plenty of information to build an effective firewall, and pointers to additional resources won't leave you hanging. Shah concludes with an interesting tour of the /proc virtual file system. Two appendixes discuss, very briefly, popular Linux programming languages and popular programs for certain tasks -- mostly desktop software.

This book is likable and readable, while providing good information. While the treatment of some subjects is short, the author always provides references to more information. Administrators familiar with NT who are willing to see what the Linux fuss is all about will have no difficulty learning from this book.

title Linux Network Administrators Guide publisher O'Reilly & Associates Included Stuff Complete text online. Intended Audience New and moderately experienced administrators already somewhat familiar with Linux. Scope Network setup and configuration, some programs. Technical Correctness Complete. Writing style Readable, while aimed at the technically proficient. Other Wide scope of network types discussed.

The Linux Documentation Project has produced some excellent work. This book is no exception. O'Reilly has updated the dead tree version with a new edition while providing the complete text at the link above.

Topics included cover what you'd expect, along with some features you might not have considered. Early on, the authors put forth an example network connecting a small brewery to an affiliated small pub. Subsequent chapters build on this simple Ethernet setup serving as a commented example.

This book is strong on theory, while not skimping on actual usage information. Detailed data about IP routing and address resolution, for example, contributes to understanding the tools, though the knowledge isn't a requirement to setting up BIND or gated. As you might expect, what's covered is covered comprehensively -- protocols like TCP, UDP, ICMP, and UUCP, dedicated Ethernet hardware, parallel port networking, and serial port-driven communications.

The first few chapters cover theory and configuration. There's plenty of information to get a single Linux box on an existing network, but read on! DNS server and client setup comes next. SLIP and PPP get their own chapters, of course. The firewalling chapter explains both ipfwadm (from the 2.0 series of kernels) and ipchains (2.2 series), clearly explaining the slightly different approaches to reach the same goal, in a long and excellent discussion. IP Accounting comes next, with IP Masquerading close behind. The discussions take a similar approach.

Network services take up the next few chapters. First up is the Internet daemon (inetd) and tcpwrappers. Next comes the NIS chapter, with good information about configuration and security. NFS follows suit. Rather unique to this book is a chapter on Novell's IPX protocol and the NCP filesystem, packing in some history, lots of theory, and information on managing bindery objects, printing to remote printers, and routing IPX packets. Following that is a discussion of Taylor UUCP, both as a client and a server.

E-mail and Netnews discussions end the book. Each gets a chapter describing the service from a basic standpoint, then a technical approach. Next, there are two or three chapters describing popular packages providing that service. For e-mail, these cover sendmail and exim (quite well). For news, it features C news, nntpd, and INN. As you'd expect, these chapters are quite detailed and easy enough to follow. Appendixes include copyright information, cable configurations, diagrams of the example network, and a quick blurb about SAGE (the System Adminstrators Guild).

While other books cover a wide range of topics in a scattershot fashion, the coverage here is highly focused. There's a good balance of history, theory, and applicability, making this book a very good starting point or a refresher for someone looking to fill in some gaps.

Taking space to explain the fundamentals of a topic instead of diving right into configuration files is very helpful. Knowing the theory of mail transport is more likely to help you configure any MTA than just knowing what's in sendmail.cf. Be aware that this isn't a one-stop shopping spot for every service you'll want to configure on your network. Instead, it's an overview of networking issues; narrow in scope, and detailed.

See the earlier Slashdot review by Christopher Thompson, for more on this book.

You can purchase Linux Administration: A Beginner's Guide or the Linux Network Administrator's Guide at Fatbrain.

Leonel asks: "The company I work for is having some real trouble setting up network printers under Linux. There seems to be no way to directly set up a network-only printer (not a SAMBA printer) using Printtool, and it seems to have almost no vendor support. There are two NT servers now that we can't replace with Linux because of this problems. Specifically, I need support for a GCC EliteXL 1208, which is the most important. Also a HP Laserjet 6MP, to which we have found a temporary solution but some insight on that would help too. Any insights?" Network printing support is mentioned in the HOWTO however that section only discusses HP devices in any real detail. Could anyone lend a hand? Queue names for the GCC Elite, if available, would be ideal.

luge writes "In more than a few Lego articles posted here, I've seen the question asked "But can I use the Mindstorms under Linux?" Well, the new Lego + Linux mini-HOWTO provides the answer. There are (currently) 7 different software options in 7 different languages (including C, Perl, and Java) for the Linux-based Mindstorms owner."

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar, one of the folks over at the Linux Documentation Project has sent us an updated list of features/responses/additions that they've put into the project. Much of this work comes as a result of Slashdot suggestions; you can read more below and perhaps want to sign up to help out.

Thanks a lot to Slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.

While reading the comments, I took a paper and wrote down the different problems people had.

Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.

- web site design : FIXED

Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.

- provide direct access to important links : FIXED

We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.

- provide security bulletins & link to RFC archives

I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.

- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.

- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

- "tables don't scale to window size and resolution and 10 pt font size is hardcoded

Our Webmasters are working on these problems.

- How can I submit my work to the LDP? You can read the HOWTO-HOWTO

three possibilities depending on the format:

a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.

Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first

- You should check the documents : FIXED

We have since November! We would like to be able to have our peer review team proofread each submitted document.

However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

- XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).

- I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.

- license problem, GNU/Linux... FIXED

We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.

We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.

Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.

Guylhem Aznar writes " After some restructuring of the Linux Documentation Project (LDP) we feel ready to serve the Linux community from our new home. The LDP has collected and produced numerous documents such as guides, HOWTOs and mini-HOWTOs, FAQs pages, and more. " Continues in article body...

All in all the LDP endeavors to produce and provide a one-stop source of information relating to the various aspects of Linux. There is now also a search engine on the front page to help you quickly and efficiently locate the documents you need. If you have a question, chances are you will find what you need here.

These documents are produced for you, the end users. That means if there is anything in the documents you find unclear, ambiguous or incorrect you should not hesitate in contacting the author. While the workload of the authors in general may be high and cannot be expected to answer specific problems you may have on your machine, generally authors are only happy to receive feedback on the documents.

Likewise, if you feel you have something to contribute or you wish to try your hands as an LDP author you are welcome to contact the LDP coordinator with your inputs (see the HOWTO-HOWTO). Remember that new documents are produced all the time so it is important to contact the LDP before you start writing in order to eliminate the possibility of duplicate work.

Remember that you do not have to be on-line to read the HOWTOs, in many cases these documents are installed with your Linux distribution and can be found in /usr/doc/HOWTO/

synthetic writes "If you go to Fox's website Fox.com, with Netscape in Linux, you get a page saying you are not running a PC or a Mac..." Very disappointing to see such a major website disregard a whole OS...the odd part is that apparently this is over Flash plugins (which actually work). Read on for more.

Additional info by roblimo: Okay, in the spirit of fairness we tried to contact Fox and ask what was going on before we ran this. The media relations department had no idea what I was talking about, almost to the point of "You mean we have a Web site?" but since it involved the word "computer" they referred me to Fox's internal tech support desk, where a courteous rep named Brian told me, "That's the way the Javascript on the site was written. That's the breaks."

Since Brian was an internal tech support guy, he had no idea who was responsible for the company's external Web site. He promised to find out who was and to have them get back to me. No one has.

I'm assuming this "Can't see our Web site with Linux or Unix" thing is a corporate oversight, not some sort of evil conspiracy. Don't forget: Fox brings you The Simpsons, so "Doh!" has got to be a word heard commonly around their offices and studios.

Perhaps if a whole bunch of Slashdot readers call and e-mail Fox politely requesting changes to their Web site so that we Linux and Unix users can view it, someone at Fox will utter a big "Doh!" and a change will be made. Let's try it, anyway.

Please start by reading at least this section of the Linux Advocacy mini-HOWTO. Then call the following phone numbers and/or write to the following e-mail addresses. Politely.

1) Fox Network main phone = 310-369-1000
2) News Corp. (parent company) = 212-852-7017
3) e-mail publicity@foxinc.com 4) e-mail askfox@foxinc.com

Perhaps none of this will do any good, but it's worth a try. And if anyone else has useful contact info for Fox, please post it below. The more the merrier!

synthetic writes "If you go to Fox's website Fox.com, with Netscape in Linux, you get a page saying you are not running a PC or a Mac..." Very disappointing to see such a major website disregard a whole OS...the odd part is that apparently this is over Flash plugins (which actually work). Read on for more.

Additional info by roblimo: Okay, in the spirit of fairness we tried to contact Fox and ask what was going on before we ran this. The media relations department had no idea what I was talking about, almost to the point of "You mean we have a Web site?" but since it involved the word "computer" they referred me to Fox's internal tech support desk, where a courteous rep named Brian told me, "That's the way the Javascript on the site was written. That's the breaks."

Since Brian was an internal tech support guy, he had no idea who was responsible for the company's external Web site. He promised to find out who was and to have them get back to me. No one has.

I'm assuming this "Can't see our Web site with Linux or Unix" thing is a corporate oversight, not some sort of evil conspiracy. Don't forget: Fox brings you The Simpsons, so "Doh!" has got to be a word heard commonly around their offices and studios.

Perhaps if a whole bunch of Slashdot readers call and e-mail Fox politely requesting changes to their Web site so that we Linux and Unix users can view it, someone at Fox will utter a big "Doh!" and a change will be made. Let's try it, anyway.

Please start by reading at least this section of the Linux Advocacy mini-HOWTO. Then call the following phone numbers and/or write to the following e-mail addresses. Politely.

1) Fox Network main phone = 310-369-1000
2) News Corp. (parent company) = 212-852-7017
3) e-mail publicity@foxinc.com 4) e-mail askfox@foxinc.com

Perhaps none of this will do any good, but it's worth a try. And if anyone else has useful contact info for Fox, please post it below. The more the merrier!

Quite a number of people have been writing to us about Dave Whitinger's column that ran on LinuxToday and was sent over here as well. Dave's contention is the browser compatibility is a crucial battle for the success of Linux - and things don't look so good. Click below to read the column, and contribute your thoughts.

By Dave Whitinger, dave@wmkt.com (Temporary E-Mail account)

Linux is quickly becoming the operating system of the future, thanks in part to the advanced type of development that we refer to as Free Software, or Open Source, as well as the rock-solid features that are present in Linux. It is the ultimate server platform.

Linux is also enjoying success as a desktop workstation. My wife, Trish, makes the perfect example of the typical desktop user.

When we became married in August of 1996, she was a complete computer illiterate, having never even used a Windows or Unix machine. I presented her with a choice:

1. I will give her a Windows computer, but will offer nothing in the way of technical support or training assistance.
2. I will give her a Linux box, and will give her complete technical support and training assistance.

A New Hope

Not knowing the difference anyway, she chose the latter, and found herself extremely happy with a rock-solid desktop.

She enjoys her Red Hat Linux 6.1 workstation. Coupled with the K Desktop Environment and various applications that I have installed for her, she's ready to go. She has her TkRat E-Mail program, Netscape Navigator, notepad text editor, licq, games, the Gimp, and a variety of other nice applications, all accessed via a friendly interface.

Finding friends in mailing lists and on-line web-based chat groups, she was happy as a clam. She would fire up her Netscape Navigator and hit any web site she wanted, and was constantly bragging to her friends about this great computer operating system that she had the privilege of using.

The Empire Strikes Back

...Until the day that Netscape Navigator, her web browser, her window to the outside world, the major purpose for using the computer, simply disappeared from her desktop while she was browsing.

Trish turned to me, confusion spread across her face, and opined, "Dave, my Netscape has simply vanished from my screen. Perhaps you have telneted in and did a kill -9 on it?"

Dave responds, "Absolutely not! Why would I do that? Let's examine the problem more closely, that the answer to this perplexing issue will reveal itself."

Upon further investigation, it turns out that Netscape apparantly did not "like" the Java code that was being incorporated into one of the websites that Trish frequents. My solution: Turn off Java.

A very important and critical issue is realized here. At this point, Trish's computer is not as powerful as all of her friends' Windows computers. If they can access certain Java-enabled pages that she cannot, she is being left out, all because she chose to use Linux.

Fade to 2 or 3 weeks later.

Trish: "Dave, this website is telling me that I cannot use their services."

Dave: "What's the URL?"

Examining the website, it turns out that it is using some special kind of plugin that is only available for Windows or Macintosh platforms. I explained to Trish that she simply will not be able to access the services on this website, until they decide to make this plugin available for Linux. A short and polite note to the webmaster later, there was nothing we could do, and the issue was closed, and Trish's computer became even less valuable to her.

Fade to 2 or 3 more weeks later.

Trish: "Dave, this website is telling me that I am using an unsupported web browser, and cannot view the pages within."

Dave: "Okay, this is starting to make me angry. The web was initially created as a completely open environment where multimedia can be viewed, regardless of your platform. It's a platform independant medium, yet here are people making platform dependant websites."

Trish: "That's great that you feel that way, but I just want to access this coupon website! All my friends say they are getting great deals, and I'm missing out! Oh, and now my netscape just froze again! Argh, (killall -9 netscape ; rm ~/.netscape/lock) again. I want a Windows computer like all my friends have."

I hung my head in shame, realizing that if she is going to be able to take full advantage of the web, she will need a Windows computer. Trish, who has used nothing but Linux for over 3 years, and is completely happy with her computer, now feels the need to switch to Windows so that she can get the same web-browsing features as her friends.

Does this sound like a big deal to you, gentle reader? If it does, than I have accomplished my mission. If it does not, read on:

In 1994, I hated Netscape Communications, Inc. The way they were embracing and extending the HTML standards was starting to become very disturbing for me. The more websites that I found that said that it uses Netscape Extensions, the more angry I became.

Then Netscape released Navigator for Linux, and everybody loved them again. They were our saviour, completing the picture of a perfect desktop for Linux users. We were all Linux users, browsing any site we wished, enjoying the satisfaction of having a great web browser for our desktop.

Then Microsoft created Internet Explorer. Then Microsoft won the "Browser War". Then webmasters began using some of the "advanced" features of Internet Explorer, shutting out Netscape users.

Problem yet? Still not convinced? Okay, let's fast forward 1 year:

Microsoft owns 99% of the web browser market share, and they control the HTTP protocol. They start adding a huge variety of features to their "Internet Information Server", their competitor to Apache, to offer advanced features to Internet Explorer clients. At this point, sites being served by Apache become useless. Then Linux becomes obsolete as a web server platform. Then Microsoft wins the war, and we're right back to square one, and proprietary technology wins again.

Return of the Jedi

On April 1st, 1998, Netscape Communications, Inc. made one final redeeming move. They released the source code to Netscape Navigator, freeing it to the Free Software community to do with as they chose.

1 and a half years later, this browser is still nowhere near completion. There is a band of rebels working feverishly on the code, trying to bring it to a usable state as quickly as possible. Plagued with problems and set-backs, Mozilla continues forward, currently at "Milestone 10". Will we see a completely usable web browser for Linux in time to save us from seeing a new monopoly for Microsoft be created?

Attention: This is the battle that could cost us the war. If we come together and push all of our might toward a Free Web Browser for Linux, we have a good chance of winning this battle. If we fail, we will lose the war. This is the issue that Microsoft wants us to overlook.

I am making a personal committment to get involved with the Mozilla project. It is the project with the most potential to become this Free Web Browser that we so desperately need. Netscape is NOT going to save us this time. Netscape has failed us, and it's time to take matters into our own hands.

If we fail, we will lose the war.

Add that to your .signature:

If we fail, we will lose the war.

And repeat it every morning to yourself:

If we fail, we will lose the war.

When you are looking over Mozilla, finding items that could use your contribution, remember:

If we fail, we will lose the war.

The truth of the matter, friends and esteemed members of the community:

If we fail, we will lose the war.

Tuesd@y asks: "I have been trying to find a way to get Linux to support my sound card, a Voyetra Turtle Beach Montego II Quadzilla, for quit some time. Is there any one out there who can offer some advice or even better a solution?" It's not listed in the Sound-HOWTO and appears to be a fairly new card. My guess is that support may be unavailable for this card at this time, and if this is true, are there any folks looking in to it?