SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Correct. Root's files would be located in root's home directory (which is /root/, whereas all other users reside under /home/$USER/). So if you want root to have the same things, you can either copy your ~/.bash_profile to root's home directory, or you can make the changes systemwide by editing /etc/profile directly (or adding your own file under /etc/profile.d/, just make sure it ends in .sh or it won't be added).
Also, when running plain su, you don't get a login shell. This works for a lot of things, but sometimes you need all the scripts in /etc/profile.d/ to be run (especially when compiling). To run su with a login instance, you would run:
Code:
su -
Wow that command does exactly what I needed. OK so do you think it would be wise to learn bash pretty deep? I feel like I can't move forward unless I really understand how the interpreter works. I'm sure it isn't necessary, but I'm the type of user that has to know those things because that little command saves a TON of headache. I mean I was trying to look for config files and edit stuff. That "su -" literally is laughing at me right now lol. Is that command using a variable or an environment variable?
I'm actually using this command below coupled with "man" right now just to learn where executable programs are and what they do (provided they look of interest of course):
Code:
echo $PATH
Then after seeing the directories and locations, I will venture in (not su, lol) and ls the directories and check things out.
There are so many things you can learn about bash and the commands that are run. It is basically a language that can be used for scripting (have a look at the build script that Alien Bob made to build VLC). I've been using Linux for over 15 years and I still consider myself a novice in the command line. If you learn it and don't use it, you tend to forget it, so I'd just focus on learning the basics and then using man pages or websites to teach you additional things as you need them.
The - in the su command is a shortcut for -l or --login (see man su for more details). It forces using a login shell for the user. While su is commonly used to switch to the root user (since it is default), you can actually use su to switch to any other user.
(have a look at the build script that Alien Bob made to build VLC)
Just looked at that script. Wow... wow...
I really don't think VLC is worth all that when the MPlayer variants can do everything it can with much better performance. But I suppose it is a key piece of software for new converts.
Quote:
The - in the su command is a shortcut for -l or --login (see man su for more details). It forces using a login shell for the user.
Yeah I haven't gotten into installing stuff yet on here. I think for now color coding my terminal and navigating the OS is going to be solid baby steps for tonight. I'll be slacking on the forums late into the night. I need to actually scour our forums for any similar stuff I may run into. I don't want be wasting anyone's time if stuff has already been asked. Everyone has been super quick on response, so I really appreciate everyone's in the community.
Holy crap did Alien Bob write that entire script? I love VLC, it's so much more than a video player. I record my desktop and and even have links for free IP TV across the world (over 8000 channels). Most channels are crap, but I'm sure there is some gems in there. Plus all the custom codecs and goodness that comes with it.
OK so do you think it would be wise to learn bash pretty deep? I feel like I can't move forward unless I really understand how the interpreter works.
It can't hurt to learn. The Linux/GNU toolchain is very powerful. There are concepts which will help if you want to learn programming. eg: Learning how to direct output to obtain the result you want.
Quote:
Originally Posted by ul7
Then after seeing the directories and locations, I will venture in (not su, lol) and ls the directories and check things out.
If you're more of a visual person, check out Midnight Commander:$ mc
It's a text-based file browser that makes it easy to navigate the filesystem.
It can't hurt to learn. The Linux/GNU toolchain is very powerful. There are concepts which will help if you want to learn programming. eg: Learning how to direct output to obtain the result you want.
If you're more of a visual person, check out Midnight Commander:$ mc
It's a text-based file browser that makes it easy to navigate the filesystem.
Yeah I'll put that in my notes, I'm really trying to stay in the CLI if I can. But yeah, sometime when learning new stuff (especially a new OS) sometimes getting those concepts down is more important. I'll check it out for sure.
It is basically a language that can be used for scripting (have a look at the build script that Alien Bob made to build VLC).
Yeah, it's a big one, but this note in it explains why:
Quote:
Originally Posted by vlc.SlackBuild
# NOTE: this SlackBuild is a monster - it tries to wrap all dependencies to
# vlc into the resulting package by building these deps as static libraries
# and then in the final stage linking vlc against all the static libraries.
# The resulting package has all the vlc functionality and does not depend on
# any software that is not present in a standard full install of Slackware.
Back in the days before kids (i.e. when I had spare time on weekends), I built a similar chain of dependencies by hand to try and get Transcode working... I gave up in the end.
Quote:
Originally Posted by Fat_Elvis
I really don't think VLC is worth all that when the MPlayer variants can do everything it can with much better performance.
Not by default, it can't. For your statement to be true, you would have to build that same list of dependencies and re-compile MPlayer against it.
The end result of Eric's vlc script is a portable binary package which could last you for years across several different Slackware versions.
You don't need to download it. It's already installed by default...
Just type 'mc' to run it. (Hence the prompt at the end of my suggestion: $ mc).
. . . .. . .LOL omfg I'm crying with laughter right now. Dude I'm hopeless as [removed]. That should give you a laugh to remember me by...lmfao. Microsoft what have you done to me!!!
Nah man. It gets old real quick... which is why scripts like Eric's vlc.SlackBuild are lauded around here.
I wonder if there is anything for noobs like me to show involvement in the community? Obviously as I stand right now, probably don't touch anything and stay far far far away from code (lmfao). But yea, I'd be down to get involved once I can function like a normal human. lol..... I can at least donate when I can and stuff like that for now.
That should give you a laugh to remember me by...lmfao.
It did. But don't worry... bigger mistakes have been made here!
Have you 'discovered' the /usr/doc directory yet? In there, you will find a ton of documentation relating to the software installed on your machine. I can recommend that you look in the /usr/doc/Linux-HOWTOs for the basics. Some of the content is quite old, but much of it is still relevant. Eg: You can find out what to do with that source code for 'mc': /usr/doc/Linux-HOWTOs/Software-Building-HOWTO
Another one which helped me a lot back in the day was the DOS-Win-to-Linux-HOWTO... but it is a 20 year old document now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
in the community.
I love VLC, it's so much more than a video player. I record my desktop and and even have links for free IP TV across the world (over 8000 channels). Most channels are crap, but I'm sure there is some gems in there. Plus all the custom codecs and goodness that comes with it.
