little confused by directory structure

[Easileigh]

i just installed it on a spare box and i dont really know what to do with it :|

on a seperate note: is it possible to dual boot it with win2k? i read somewhere it aint

[trip]

Directory structure:

As you know in Windows, all most all programs you install have their own directory. Under Linux, a lot of programs (just about all admin and pre-installed system tools) are split into different directorys that hold files of the same type.

/ : Root directory. the 'root' of your filesystem.
/bin : This directory holds binarys, or programs.
/sbin : This directory holds system admin binarys, anything normal users wont need, and shouldent use.
/etc : this directory holds configuration files, like lilo.conf for lilo, your bootloader, and fstab, a tab of the filesystems used on ur system.
/usr : This holds mad poo. user installed programs go in here
/usr/bin : This directory actually.
/usr/sbin : guess
/var : holds logs, and stuff like that
/boot : different on some systems, but if u have this one then your kernel images are normally kept here

hmmm... ive probably missed some, im in windows atm.

[Godin]

theres also

/home : user home directorys are kept under here
/root : This is the root users home directory

[trip]

apparently Win2k dosent mind. (http://www.linuxnewbie.org/cgi-bin/ubbcgi/ultimatebb.cgi?ubb=get_topic&f=1&t=011295)

[aef]

A not-too-bad guide to this is at:

http://www.firstlinux.com/articles/cards/lds.shtml

(Though your init scripts will probably be in /etc/init.d, not /sbin/init.d.)

Should be no problem dual-booting Win2k and Linux, but I haven't tried it.

AEF

[Skunk]

The other directory you might spot is /proc

This is a very interesting directory. It doesn't actually contain any files (in fact it isn't even a location on your hard drive) - instead it holds a load of "virtual" files which represent the current state of your PC. Every time a program (or processs) is started it gets a sub-directory within /proc with the same name as it's process ID (the number that identifies the process). Virtual files within the process sub directory represent different things about the program, uch as the command line used to start it, it's environment variables etc.

Other interesting virtual files within /proc include a file that tells you the spec of your PC, and one telling you the status of your hard drive free space (I think). It's a very interesting feature of linux. The best way to explore it is just to get in there as a non privelidged user (i.e not root) and use 'less' to read the different files.

[Ironheart]

Blimey, looking at files that don't really exist?

I think we're verging on quantum mechanics territory :)

[Gwil Da Skank Of TA]

Heh, a fun if dangerous game is type kill and randomly typing a number to see if it kills a process.*

*Highly not recommended!

:E

[aef]

Originally posted by Gwil Da Skank Of TA
Heh, a fun if dangerous game is type kill and randomly typing a number to see if it kills a process.*


You want: http://www.cs.unm.edu/~dlchao/flake/doom/

AEF

[Gwil Da Skank Of TA]

hhahaha nice one aef that is funny :)

:D