First I want to say, WOW! I'm SOOOOOO happy to finally find a Linux community that is geared towards newbies! I'm an IT Manager for a large company in the US, MCSE, A+ etc... but have never seriously sat down and learned linux. I've installed in numerous times, and played with it, but never enough to really do EVERYTHING that i need it to do. Last summer was the last time that i did anything serious. Well, now I'm installing Fedora C2 on a desktop. I'm looking forward to getting wine installed, and using some windows programs working under linux. If i am successful, then I plan on dual booting my Home PC with Fedora C2 as well.
Anyway, Anyweb, thanks a ton for this site, and for all the helpful items, reviews etc that you have put on your site, as well as all the members that have contributed. I plan on being as active as possible on this board.
okay its down to 8 teams and quiet a few of the favorits are already out (like spain, italy and germany [img]<___base_url___>/uploads/emoticons/default_rolleyes.gif[/img] ) so whats your bet, who will win this European Championship??
ill go with denmark, but then again im danish :):) but we do have a very stron team this year, and we have done it before (1992) B)
Posted by: z0ny - 2004-06-23, 05:17 PM - Forum: Tips and Tricks
- No Replies
Let's assume some friend of yours (or even you?) wants to run a system service (or anything else that requires root privileges) on your box and you allow him to do that. Unfortunately the service requires root privileges and you don't want to give him your root password. The solution is 'sudo'.
Step 1: Locate the service
Locate the executable of the service, if you use 'service <name> <on|off|...>' as root a good place to look is within '/etc/init.d/'.
Step 2: Allow the use of 'sudo'
You have to add the target user to the sudoers list in order to grant him the priviledge to use 'sudo'. That is done by executing 'visudo' (it is recommended to use that command instead of editing the file directly) as root. As we don't want the user to be prompted for a password we add the following to that file (information about the syntax and stuff can be gathered from 'man sudoers'):
Code:
<user> ALL=NOPASSWD: /etc/init.d/<name>
We repeat that for every "root-command" (= command that requires root privileges) the user needs access to. After saving the file the specified user is able to control the program by placing 'sudo' in front of the command, in example 'sudo /etc/init.d/<name>'. Kinda easy, isn't it? :)
SCSI-IDLE is a simple tool to let you spin down/spin up/spin down on idle- your annoying scsi-drive.
WARNING: Before you use this program, be aware of the risks. Have a google around.
Old disks in particular, and disks that have been running 24/7 for longer periods can be dangerous to park this way, according to some forum entries. Yet again other entries say that newer edition scsi disks that aren' bleeding edge will most likely behave in exactly the same way as their counterversion ide-drives. I'm taking the chance at least... my ears need a rest :)
Btw.. that rpm works fine in FedoraCore2
I think this might be bending the rules a bit, but that site looked a bit outdated and flimsy.. so in case it goes down I've included the rpm that worked under FC2 here as a .tgz file. Forum wouldn't allow tgz's or rpms to be uploaded, so I removed the ending. Just change it back to tgz, decompress and install!
scsi-idle is a package for controlling the motors in your SCSI disks. There are three programs, scsi-stop, scsi-start, and scsi-idle. The first two allow you to spin up and spin down you drives manually. You don't need a kernel patch to use these programs. The third program, scsi-idle, is a daemon which will spin down your discs after an idle timeout. You do need the kernel patch to allow this, since one of the things the kernel patch does is provide a way to get the idle time of a disk. The kernel patch also allows the kernel to spin up your drives automatically when they are accessed. This doesn't work perfectly, if you access the drive via a swap partition or by trying to mount a filesystem on it, bad things happen.
I updated the patch to work with the the 2.0.36 kernel and again to work with 2.2.10. I also wrote the scsi-start and scsi-stop programs. The 2.2.10 version also includes the patch for 2.0.36, and should work fine with a 2.0.x kernel.
Alright, many of you have probably dealt with this before, probably many times over.
For some reason, the commands to install themes throught the console in Mandrake 10 (KDE) don't work.
I need instructions, please, as in, instructions you would give to a 5 YEAR OLD, lol.
I mean, ultra-simple instructions. I'd really appreciate it. Seriously.
I have a KDE 3.2 theme file, downloaded from within WindowsXP, simpy because my modem isn't yet configured for Linux, but since I have dual-boot, I have access to my windows hard drive from within Mandrake 10.
It is a .tar file, but the extension reads .tar.tar. It seems I've been able to unpack it to a directory, by using the right-click menu on it, and I can see an "admin" folder and a "config" folder along with alot of .ini files that can be read by double clicking on them. Anyway, the folder in which these files and subfolders are is called "ballistik-0.5" Ballistik is the name of the theme. I put this folder in /tmp.
So, what next? I assume I have to go into the console. Could I get some step-by-step commands?
ok I had samba all setup in kde I could see my windows share using the lan browser in konqueror but I siwtched to gnome cuz I seem to like it better....and I can't figure out how to acs my windows network from gnome I've tried click my computer->network->windows network but then it just sits there with a nothing in the box? I am on fedora core2....oh also I can acs files on my linux box from windows...
