I think that a beginner's section would be critical to the success of the book. Considering that the vast majority of newcomers to Linux will have only Windows experience, making the transition from Windows to Linux as easy and painless as possible, and providing them with a roadmap to guide their way, would be essential. Considering that for roughly the past 10 years virtually all OS functions in Windows are performed by the mouse (eg, copying/moving a file is done via dragging/dropping, software installation is done via double-clicking, hardware configuration is done via an annoying "wizard", etc) the assumption that everybody will "already know the basic CLI commands" is not realistic. (Heck, unless a person has been using Windows since the late 80's or early 90's, the idea of a "command line" or a "terminal session" are likely to be a totally unfamiliar and alien concepts)

While I agree that a discussion of the CLI should not be the main emphasis of the book, I would recommend at least one chapter on it, which would contain the commands themselves; the usage of the most commonly used flags applicable to that command; and a discussion on how to interpret the results of the command. Personally, I thought OSourceDiplomat's suggestions were excellent, although I do agree that a troubleshooting section would be particularly useful -- just look at how many threads there are on installing and configuring audio and video cards, getting Internet access up and running, etc.

As a general comment, where I think most technical books fall down is if they try to be all things to all people, and try to cover all possible topics in order to be considered a "complete reference". The usual result is that they do a fair to adequate job in most areas, but an outstanding job in none, and the poor reader is stuck with trying to plow through a 1500 page monster that costs as much as 2 or 3 month's worth of broadband access. Perhaps it would be worthwhile to make things more modular, and split the subject matter into separate volumes. I also like the idea of a book for the intermediate-level Linux user, but I would also point out that you can't have intermediate-level users unless you also previously had a lot of beginner-level users. Most people I know will stick with a proven winner, and if an LQ book for beginners is well received, when those users want to move on to a more advanced level, their very first choice is likely to be something from LQ.

This book is a great idea, and if I can assist, count me in. -- J.W.

I agree that you won't be successful with a book aimed at experts. They have the desire to learn for themselves, and the resources for the current fixes. But on the other hand, I am tired of reading about installation and GNOME/KDE chapters.

It was suggested, and I think a great idea, to have something with members success stories. Cool things that people did, especially ones that they never would have done with windows. And of course, corresponding howtos so that other can do something similar. I also think that it would be a good idea to put in it answers to the most common posts, of which video cards comes to mind.

I think that this is a really neat idea! In my humble opinion, I think it ought to focus on the newbie market and on the info that's common across distros (basic GUI and command line skills, compiling programs, etc.). Of course in some cases such as package management it's necessary to get a bit more specific. And then after that a sort of advanced "tips & tricks" section with info about scripting, system administration, maybe software development, compiling the kernel, and other advanced usage.

I've subscribed to the mailing list and look forward to seeing what this project produces.

btmiller; like your style concise. jeremy add strong advice to newbies with regards to system administration not to forget root user password. I did then consequences set in. of course reading instructions with avoiding attention to fact it was meant for mulitple users not single user. writing down password within multiple users is security hole. not so single users at home .

I think that a beginers section in the book is absolutely necessary, however I don't think that it should be the focal point. I think that maybe the book's layout can be done similiar to the forum, with units such as software, hardware, security, networking, portable and distros (and their respective sub-units). It's at least something to think about.

I think that the book should try to touch on some subjects that aren't as well documented in books that have already been released, such as getting your digital camera and other mass-storage devices working, getting printers working, producing dvds, doing tv capture, and other things of this nature. Also, you can touch on setting up the major servers like apache, samba, ftp, ssh, sendmail, bind, and all the others. It really all depends on what the intended market is. A book about desktop linux will be different than one about server administartion. I think that maybe a mix of both would be the best way to stand out of the pack.

Also, I think an appendix with the HCL would be a good idea, as we have a pretty good one here in my opinion.

i'm not sure if i could give you any linux help or content help for this book, but i could certainly help on setup.

i work for a printing company, setting up books, and i have a very good idea of how to get all this done (i've been working as such for about a year now). if you need any help in these respects, just contact me via my email and we'll talk.

contrary to what alot of people think, setup is one of the more important parts to any book-i mean if you can't read it, then it's not a very good book, right?

there's alot more to go into it than that, but either way i would still be more than willing to help you get it setup.

btw, have you decided as to whether you are going to be printing it offset or digital? if not i think your decision wuld have to rely heavily on how many people you believe would be purchasing this book. the company i work for is a digital printing company, and i think the most books we get done by any one publisher at a time (per book) is about 2000 copies. anything beyond that i would recomend going offset. (reason being offset would be more cost effective for anything beyond 2000 copies). although, i suspect you have already been looking into all this, and have already thought of pricing various printing companies out as it is.

also, i do have some experience in designing covers as well. are the initial first books going to be hardcover, or are you going to come out with soft cover books first? this will also cause a difference in pricing.

alright, i've probably taken up enough of your time. if you would like to talk more, just give me an email, as i said, i'm more than willing to help.

--
Terry L. Trent, Jr.

Considering how much information you could justify putting in a book like this, I recommend making it a set of books broken into categories so that it wasn't too big - like a LQ reference library. No one really likes a book that's 1500 pages and four inches thick anyway. One thing I highly recommend putting in that 'set' of books is a great compilation of the linux commands - like a pocket reference but better than any other...if there is such a thing!
I really think this idea would simplify things so much and make it a much more attractive buy. Pull out the book on desktop environments one day ('cause some people want to learn all about KDE and Gnome and the rest of 'em), iptables and security the next, and maybe the guide to kernel compilation the next. No need to drag around one huge book. Costs more to put together but worth the extra money to buy!
Just my two cents.

That's good news(the book) but i do not agree with people who says that it shouldn't be a newbie thing.
IMOHO -it should be easier and friendlier to use,with more refferences from the sites where one can get further help.
It should also contain alot of troubleshooting and solutions.
Please let us know when it's in the market as soon as possible.
Keep up the good work

As has been discussed on the mailing list, the thing about command line tinkering is - it's much more bound to be broadly Linux-oriented as opposed to distro-oriented, if one starts making UI setup instructions. Breaking it up into several projects makes the project increase exponentially in size... perhaps there should be the real live print - in-the-hand - coffee-stain-sucking copy - and make the rest, the minor/peripheral parts available for printable download for those who bought the book or contributed to the site? The costs & the work would be much lower, and the benefits mutual.

osourcediplomat; enjoy ur style & finesse. binding all that material into book form quite an undertaking. needs great fortitude and perseverance.
Jeremy certainly needs to be accoladed and commended. thank you Jeremy!

And a page or two in the section on how to use these commands for the information you need to have to ask a good question when you need help. Plus maybe a little blurb stressing the idea of using the output of an error to search the web before you ask the question which is sadly lacking in a few posts ...

I'd like to see a project oriented book.... like... "LAMP guide" or "Setting up an FTP server"

Jeremy; about books i`ve read that were not informative enough. author,s
& writers ; presumed readers (or stated) familiar /knowledgeable with linux
commands ,syntax without detail explanation on howto. left me feeling not
to even try linux. but persevered read other books with better information
and here I am. communicating with all users (gurus n newbies like me) .
what a difference that made. I commend you Jeremy with your great effort!
THANK YOU!

Great idea. I hope it's as successful as this website.

I think it should not be a complete noob book; however, it also should have some stuff to help the new comer to understand Linux. One thing in particular I have not been able to do is to compile my kernal from scratch (maybe I'm just new, but it sounds hard nonetheless). Like if you need to upgrade the kernal, but you don’t want to reinstall your OS. Or when you need to install certain drivers into the kernal, and you need to recompile the whole thing.

Writing an innovative book on Linux (that isn't a screen dump of possible command lines) is already a large task. I’m sure the more experienced LQ users could proof read sections of it for you. Unfortunately, I don’t think I fit into that category.

Good luck,
ian

Dear Jeremy,
Linux is a mission and LQ is one way to complete it. I am sure your book will add to it. Reading your own words, I anticipate that the book will be self-contained. Of course, we would like much more in the book. Let me break one news (Perhaps by now it would have reach the giants of Linux like you) that LIC, Life Insurance Corporation of India (until now the only life insurance company in India) is now switching to Linux. LIC is one of the biggest enterprise of Indian Government. I hope now Universities will have to produce LINUX GURUs.
Working with the Mathematics Department of one of the top Universities in Gujarat (India), I look forward to see your book directly adaptable in the syllabi of our computer oriented courses.

Love and all the best

Dinesh Karia