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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Hi group.
Well, I took the leap, and installed, and theN compiled kernel 2.6.10 from the Slack 10.1 disk set. So far so gOod, but I suspect there is a lot to learn that is new. I do want to exploit Direct I/O. Anyway, am pleased to be state of the art, and want to thank the many participants in this Forum.
I have one question. Previously, In the directory /PROC/BUS/USB there used to be some entries (just as there are in /PROC/BUS/PCI, which is kind of what is printed with "lspci" command). The sister "lsusb" command displays nothing for me, perhaps because that directory is empty. Unless this is a new feature (which I doubt) I suspect I missed something along the lines of configuring USB or PROC virtual filesystem in my make menuconfig. Is that up the right track? If so, can someone pls tell me the name of the parameter I missed? I just can't find it, looking through my .config in /USR/SRC/LINUX (It's also 3:30am, and the eyes are weak...)
Thanks
wombat53

Guillermo - the parms seem ok on my .config file..USB support, and the PROC pseudo file system
Are you on 2.6? Do you have lsusb and /proc/bus/usb working correctly?
There are ceratinly changes...a new "input" directory, and a new /proc/sys/...directory...
George

Guillermo
This is what I did. First, the correct parms were set (so I believe): CONFIG_USB=yes and CONFIG_PROC_FS=yes.
Out of desperation, what I did was to convert several USB parms from modules , to kernel.
These were:
CONFIG_USB_UHCI_HCD
CONFIG_USB_PRINTER (I have USB cable to printer, not parallel), and finally,
CONFIG_USB_HID (I have a Logitech Kbd with USB only connector)

So, basically I replaced module suppot with kernel support, and got back the /PROC/BUS/USB support (as well as lsusb). I do not know if this is the way it is supposed to work, but that is what I found.

I guess this raises the question, what can be a module and what cannot (apart from the obvious, like ext2 support, etc.)
wombat53