LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
sound, video, openGL, divX (if possible)
DVD playing(with all codecs)
cd burning...
and all of this on a number of distros:
Slackware, Fedora, SuSE, Mandrake ..
especially Slackware ; )
and for BOTH the 2.4 and 2.6 series kernels.
Also Id really like to see a 'play it safe' kernel compilation guide.
One where you include everything possible, whilst still not causing any conflicts - ambitious if not impossible I know.
Some nice 3D coloured figures in the book to enforce the lesson, of course.
most books spend 3 or 4 chapters on working at the console.... this is a bit of a turn off for people who are used to Windows.
would like to see hardware installation issues as one of the early chapters... eg scanners webcams etc as these are not addressed automatically in the system install process, at least not in Fedora or LBA.
another issue is installing new software in tar gz formats, and the associated issue of where the software sits after it is installed, how to make icons and program links in desktop panels and menus.
perhaps really there should be two books, one for people new to PC's and one for people who are used to Windows and who want to replicate quickly the functionality they are used to.
Hi... I'm new here (in linux too) ..so I think it's my opportunity to be helpful:
what I don't like of linux books: it's always the same: filesystem; some common commands; etc...
what I *do* like of them: that info is always useful
what I expect in a linux book: a big chapter related to compatibility stuff 4ex: winmodems vs. fullmodems, etc.. remember: a lot of people came from the 'win-word' (like me), so this book should introuce a kind of 'different concept' of computer system without scaring them..
I like to think there's 2 kinds of *nix potential users: the first group are those who are system students or just computer addicts and are looking for something pretty much different from win.. not to replace it , but just to investigate and try different thinks.
The second are those people who are thinking of REPLACING win with *nix..
that people doesn't have time to investigate new things... they just want to have it quickly and working... -like office workers, graphic designers,etc...
Maybe you can play with that...
wish you a lot of luck with this book!
ciao
I think a book is a excelent idea. I would have to say OSourceDiplomat has touched on some the major points that should be included in this book. Other usefull information will be things to consider for a mixed environment (Linux and Windows). Good examples and tutorials of each topic will definatly be helpful. A appendix section for users news to linux could be a good idea. The appendix will give some advise on how they can become better users and ways to get involved in the linux community.
There are a large number of transitional users, pre-transitional users, who can install something like MDK 9/10 with the GUI, with a small effort they can configure it to start in X, without a password, and automatically connect to the WIN LAN, and the NET at startup.
All things you should not do, that win does automatically, to these people this is normal. They have their mouse, their keyboard for minimal typing and they are off.
But this is not Windows, they can click about, bounce off of a lot of things and do basic stuff. They are not computer noobs as such.
Get them to install a Non-o/s disk supplied package Rpm Ect, has instruction cd to ?????????
These people do not know how to open, or use a shell, many of them will not know what a shell is, R.T.F.M.
Is not the answer, if you really want to convert the convertible in droves.
They need that extra little bit at the beginning, that says do a,d,c with your mouse or d,e,f. This will open your shell (see t,a,k, in man g) at the flashing cursor type xyz/cde/ press enter (This will happen) then do ECT, ECT,
The references for these commands are k/a/w/and v in The Man pages. It will not take them long,
Ping a common exercise in windows or any other, heaps of bad instructions on How To. This one has the extra couple of lines.
Next, open the command prompt (Click Start/then run/) and type “ping” followed by any one of the IP addresses from your list, and press enter (Don’t type the quote marks). For instance, from the example table, if I wanted to ping the office computer I would type, “ping 192.168.0.2” and press enter.
A couple of books and a few reworked FAQ/RRA. With that little extra will go a long way.
ing1; that is to the point! speak the same language, just hope the conversion of non linux users is to help them become efficient with linux by
means of as you (well said) wrote that newusers read all available material
before committing any action of attempting to make linux work. As you stated windows makes user so dependant, dos almost forgotten. Thank you for those sage words!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.