Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Click Here to receive this Complete Guide absolutely free.
What are these commands? Is this a service? Is it a graphical program? Is this a user program or a system program?
If this is a user program, it is better to start it when you log in instead of when your computer boots.
If this is a user console program, then your .profile script is a good place to start it, but you may need to run it in the background so that the .profile script will finish. If this is a GUI program, placing a shortcut in an Autostart directory may be better. If you want it to start regardless of which desktop environment you use, then an X script such as .xsession.
Also, include a full path to the command in your scripts. A script started at boot and run as root will have a different environment then one started by a regular user.
it is an I/O module slotted in one of my PCI-Express slot. It doesnt load automatically with every boot. To load the module i have to type the commands in the command shell.
Where exactly is this "ixpio" directory?
If it's in your home directory, specify the full path of this directory, an example below using my /etc/rc.local file.
Code:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
cd /home/me/ixpio
./ixpio.inst
exit 0
You can also put them both in one command as such: cd /home/me/ixpio && ./ixpio.inst
Could you provide a link with more information on this device and the program? A README file would be great.
Does it work when you run it manually? The only way I can see this is if it is using the fuse system to load a userland driver.
A user program to load a kernel module just doesn't sound right. I can see running a script as root to install the kernel module in /lib/modules/$(uname -r)/ and then adding a file in /etc/modprobe.d/ with an install command, modprobing the device and running "depmod -a".
Perhaps this has been done previously and the ixpio.inst command does something else than load the module.
In that case, the problem could have been in the previous phase of installation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.