The same as all other "dotfiles" (personal configuration files), you home directory.
And this...
Ctho, I hope you're just trying to push buttons and don't actually think that.
The same as all other "dotfiles" (personal configuration files), you home directory.
And this...
Ctho, I hope you're just trying to push buttons and don't actually think that.
There is .profile and/or .bash_profile in your home directory, generally you should put your customizations in these, not the one in /etc.
cleverhandle
Diamond Member
- Dec 17, 2001
- 3,566
- 3
- 81
Yes, true in theory. But I'm going along with the Debian style of putting user customizations in .bashrc, since the default Debian files source that into .bash_profile. You would probably want this particular alias to apply to xterms and such as well. So .bashrc seems like the Debian way to do this for a single user, and /etc/profile would be a global change.
AFAIK, profile (including .bash_profile and .profile) are read when you log into a "login" shell (-bash, -sh, etc), and .bashrc is read when you open a non-login shell, or subshell (just /bin/bash or whatever). However you want to use that to customize how your shells work is up to you, the debian supplied .bashrc and .bash_profile are simply defaults, for people who don't care about changing them. If you _do_ want to change them, you can and should, they are yours, and will never be changed by debian, as they are simply copied upon user creation from /etc/skel. Either way, I still believe that you should not generally make any changes to /etc/profile for the sake of configuring your own environment, because the whole concept is that _your_ config files go in _your_ home directory, and it is a good one, because I can just tar up my home directory and burn it to cd, throw my hard drive in the river, get a new hard drive, install whatever different OS I want, restore my home directory, and I'm back in business with no change in configuration. Putting things in /etc just goes against that. You sure don't want to restore your entire /etc on a new installation (especially of a different OS), and the alternative is picking through, restoring files here and there that you customized in /etc. PITA! Home dirs 4 lyfe fewl!
Originally posted by: BingBongWongFooeyYou sure don't want to restore your entire /etc on a new installation (especially of a different OS), and the alternative is picking through, restoring files here and there that you customized in /etc. PITA! Home dirs 4 lyfe fewl!
That is an understatement. 3a.m. in the morning and my brain is pretty much completely fried. After installing debian I decided to copy my mandrake /etc over, so I could save myself some trouble. BAD MOVE! The next day I had to do a complete reinstall. Lesson learned here: never migrate to a new OS, when your so tired you can feel you're brain cells commiting mass suicide.
Well, OpenBSD is for super-insane security systems and firewalls. NetBSD is for running on your calculator, your toaster, your VCR, etc. FreeBSD is for the people I said above. I don't know of any other reason to run it (unless the GPL is too restricting for you).
For me personally, if an operating system is open source and free, I have no problems using it. Some people seem to hate Linux because they claim it's not "Free" - well, very slightly true; it's not free to the large corporations who might want to rip off parts of it to include in their big, bloated, expensive OSes.
Originally posted by: jliechty
For me personally, if an operating system is open source and free, I have no problems using it. Some people seem to hate Linux because they claim it's not "Free" - well, very slightly true; it's not free to the large corporations who might want to rip off parts of it to include in their big, bloated, expensive OSes.
True, but then again I'm sure there is some reason that FreeBSD continues existing, right?
EDIT: Uhhhh, misplaced comma.........
what I would do if I was doing what you are doing (which i do) is to install a different OS on each computer... Openbsd, Debian, Freebsd, SLackware,Redhat.. WHatever your cofortable doing... and put the one you feel comfortable tweaking the most on your main desktop (or computer kingdom monitoring superstation and uber hacker workplace as I like to tell my roomates ).. That way you get the best of all OS's. It's not like win98/w2k hell, were each OS is different and subtle incompatabilities are the norm, It's unix and most OS's work realy hard to gain easy compatabilities thru using OpenStandards.
You'll learn howto use "Unix" rather then how to just how to utilize the different platforms configuration tools.... The config apps are nice and work, some are better then others, but if you don't usderstand the underlying stuff they do for you they can be a liability...
Some stuff that can help is, a eligent program called "screen" it is a terminal manager that can manage multiple sessions in one window... For example if you ssh into a Openbsd box you just start screen. IF you are using pico or vi to edit a config file and you need to see some other settings because you forgot something, or you need to consult a man file you just hit crtl-a ctrl-c to open up a new terminal were you can view the man file, then you can hit ctrl-a a, to go back to the other terminal, now you can switch back and forth by using the ctrl-a a buttons with out having to use the mouse or close out any programs.... Plus if you get tired of working on it, you can just hit the x button and shut off the xterm and end the ssh session. If you want to go back you just log into the openbsd box with ssh and hit screen -R and will open you right back into your previous session right were you left off!
another thing... if you have a x windows app that you want to use on one computer... say you got Mozilla 1.3 on your slackware box and you want to use it on your Debian and Freebsd boxes, but you don't want upgrade or waste disk space by having muktiple copies, you can open up a X session.. Remember that X windows is a NETWORK protocol, normally you just use the "server" (the part with the output and input, the monitor,keyboard and you) on the same box as the "client" (the computer that does the work.) But the server and the client don't have to be on the same computer! They can be any computer that supports X windows. The easiest and most secure is to set up X so that it pipes thru ssh (openssh supports this by defualt) all you realy have to do is uncommit a couple entiries in a couple configuration files. Once you get it set up all you have to do is "ssh -X" into a remote "client" and the DISPLAY variables should be set up automaticly, so you can open Mozilla and it will run in your server with all the bookmarks and settings that were set up by the user you are using to run SSH and run it incoprporated in your current X session! Better than VNC!! I do that with my old 200mx laptop so I can use the power of my 1.3Ghz workstation PC over the network, also can work over the internet If you got a nice connection, but then security is a real concern!!! That's why I pipe it thru SSH....
eventually I am going to figure out how to use stuff to make a full fledged Unix domain, with a file server that'll house all the home folders of the users, so that my settings don't change from Unix box to Unix box and a application server so I can use my nice PC to run apps on all my pentium 1/2's and the 486 file server. Then I'll figure out how to set it all up to work with 2k domains and write scripts so that I can show howto intigrate unix and windows domains....
).. That way you get the best of all OS's. It's not like win98/w2k hell, were each OS is different and subtle incompatabilities are the norm, It's unix and most OS's work realy hard to gain easy compatabilities thru using OpenStandards. You'll learn howto use "Unix" rather then how to just how to utilize the different platforms configuration tools.... The config apps are nice and work, some are better then others, but if you don't usderstand the underlying stuff they do for you they can be a liability...
Some stuff that can help is, a eligent program called "screen" it is a terminal manager that can manage multiple sessions in one window... For example if you ssh into a Openbsd box you just start screen. IF you are using pico or vi to edit a config file and you need to see some other settings because you forgot something, or you need to consult a man file you just hit crtl-a ctrl-c to open up a new terminal were you can view the man file, then you can hit ctrl-a a, to go back to the other terminal, now you can switch back and forth by using the ctrl-a a buttons with out having to use the mouse or close out any programs.... Plus if you get tired of working on it, you can just hit the x button and shut off the xterm and end the ssh session. If you want to go back you just log into the openbsd box with ssh and hit screen -R and will open you right back into your previous session right were you left off!
another thing... if you have a x windows app that you want to use on one computer... say you got Mozilla 1.3 on your slackware box and you want to use it on your Debian and Freebsd boxes, but you don't want upgrade or waste disk space by having muktiple copies, you can open up a X session.. Remember that X windows is a NETWORK protocol, normally you just use the "server" (the part with the output and input, the monitor,keyboard and you) on the same box as the "client" (the computer that does the work.) But the server and the client don't have to be on the same computer! They can be any computer that supports X windows. The easiest and most secure is to set up X so that it pipes thru ssh (openssh supports this by defualt) all you realy have to do is uncommit a couple entiries in a couple configuration files. Once you get it set up all you have to do is "ssh -X" into a remote "client" and the DISPLAY variables should be set up automaticly, so you can open Mozilla and it will run in your server with all the bookmarks and settings that were set up by the user you are using to run SSH and run it incoprporated in your current X session! Better than VNC!! I do that with my old 200mx laptop so I can use the power of my 1.3Ghz workstation PC over the network, also can work over the internet If you got a nice connection, but then security is a real concern!!! That's why I pipe it thru SSH....
eventually I am going to figure out how to use stuff to make a full fledged Unix domain, with a file server that'll house all the home folders of the users, so that my settings don't change from Unix box to Unix box and a application server so I can use my nice PC to run apps on all my pentium 1/2's and the 486 file server. Then I'll figure out how to set it all up to work with 2k domains and write scripts so that I can show howto intigrate unix and windows domains....
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter