Operating Systems > Linux and UNIX

a few niggly little linux questions

<< < (2/2)

beltorak0:
1. stop using /home.  try /opt/cdimg.  then make a symlink.  I think M/9 is assuming that those perms are a mistake; as for what is doing it, i dunno.  I remember trying to do the same, and even though slackware never re-perm'd it, i couldn't access them.  I use /usr/local/music, but that's just my preference.

2.  edit "/etc/inittab".  look for the following line:
"id:5:initdefault:".  change that 5 to a 3.

3.  try this: for each wm and OS, make a .$wm.$OS directory to store your preferences.  Then, in ".profile", have it check to see what OS you are running, and create the neccessary symlinks for each "$.wm".

4.  (note: slackware specific) in /etc/inittab, the should be a line that looks like:
x1:4:wait:/etc/rc.d/rc.4
(your numbers will be "5" of course.)  That is the script that is executed when running that runlevel.  you can edit it, but if it is set up to check if the xdm's cousins are executable before executing them, then you can just turn off the executable bit in the xmd-cousin you don't want to use.  ie: my script fragment looks like this:

--- Code: ---
--- End code ---
so all i would have to do is "chmod a-x /usr/X11R6/bin/kdm" and gdm would become the default $xdm.  If i felt like punishing myself i could also "chmod a-x $samepath/gdm" and give xdm-proper a whirl.

3b.  again, solve it with symlinks.  The window manager start up routines are actually sh-scripts in the directory "/etc/X11/xinit", and are named "xinitrc.$wm".  "ln -s /path/xinitrc.$wm-of-yer-choice ~/.xinitrc" and startx will use that script upon loading X.  I have a script that lets me choose (but it prolly wouldn't work under runlevel 4 or 5, or whatever).  It's at the end of this post, so if you want to grab it, feel free.  You can always rename starx something else and name the script startx, but i just call it "x".

4.  
--- Code: ---
--- End code ---

under slackware: root (the partition of the root fs) is specified as /dev/hda5 ( (hd0,4) in bsd-speak i think).  My kernel resides on partition /dev/hda2 (which gets mounted under /boot).  The only things that are essential are the title and kernel lines.  and the root line if the kernel doesn't know it is on a different partition.  anything else is just options to the kernel.

now for the setup:

--- Code: ---
--- End code ---
you should see something like "found stage1 file... found stage2 file... setup complete".  if not try typing "help" into the grub prompt for information about how to get grub to search thru the partitions for it's own files.  i don't remember the command off hand.  also note: if you do not have the picture patch for grub installed, you will not get the splash screen to work.  i have not done it yet, so my slack.xpm is limp and worthless    ;)   .  I think that the grub that comes with M/9 has it applied.

last).  as for networking, i whish i could get experience.  i have a spare computer without a hard drive, and i haven't found the time to learn how to set it up as a thin client even.     :(   (.  we could collaberate and set up a VPN, but that might be even more work.... let me know.  I have a few friends interested....

I hope this helps...


--- Code: ---
--- End code ---

[ January 29, 2003: Message edited by: beltorak ]

[ January 29, 2003: Message edited by: beltorak ]

Calum:
beltorak, thank you very much for that!
i will begin assimilating that information right away! this machine already has red hat, mandrake and freeDOS on it, so i can use the red hat grub (in a lot of ways i do prefer red hat to mdk when it's running right) which i know does have that xpm patch because it shows me a little picture of a penguin at boot time.

As for me getting involved in a VPN, i would love to but i really think that since i know nothing about networking and since i have very little time right now that i will have to bow out for now. Remember me in future though...

and again, thanks.

beltorak0:
yeah; none of my friends have any time to set up a VPN -- me included.  If i ever get serious about it I'll let ya know...

glad to be of service...

also, i just found out today, that if you already have grub set up on the system, you do not need to go thru the setup again.  Grub reads the "menu.lst" file right off the hard drive at each boot, so if you make a change in there for a working grub, it will take effect on the next boot.  very cool indeed.

well, take care!

5amYan:
3. You can manually change the runlevel at command line as root by;
#/sbin/init n
where = an integer 0-9
0=halt
1=single user
2=??
3=??(some linux use this for multi user/network runlevel)
4=??
5=Usually multi user or network or in the case where those are in three this may be for x
6=reboot
7-9=unused in linux
Note: runlevels I think are from System V UNIX.  FreeBSD doesn't use runlevels. There is single and multiuser modes and that's it.  Nice and simple.

4. sudo >>>or better yet assign a group privs to exec what you want and add users you want to that group.

5.  As a note FBSD can be called in grub nearly the same way as windows.
 rootnoverify (hdx,xa) ## the a would specify whoch slice of the partition the BSD kernel is on.
 chainloader +1

6. I guess you could get vmware and run mutiple OS simultaneously.  Or maybe setup a faux network with honeyd for firewall implementation testing.  You can also connect via serial parallel or USB ports depending on what's available

[ February 17, 2003: Message edited by: 5amYan ]

Calum:
thanks! top answers!

Navigation

[0] Message Index

[*] Previous page