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.
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
Enjoy.
Oh yeah, I've been checking that out already. Yeah man I'll be lurking around on forums just soaking it all in. Thanks for your help!
I don't know if you've read about it yet but if you want to up your command line game read about "bash piping and redirection" (web search finds decent results). Essentially you can feed commands into other commands which really opens up what you can do in a terminal and scripts.
Good to see you're having fun and finding your way alright.
I don't know if you've read about it yet but if you want to up your command line game read about "bash piping and redirection" (web search finds decent results). Essentially you can feed commands into other commands which really opens up what you can do in a terminal and scripts.
Good to see you're having fun and finding your way alright.
Yeah I've been checking out the piping commands for Linux. Thankfully since I work on CISCO routers and switches, I do a lot of that already. Of course, even though CISCO devices are "technically Linux" based, it's still vastly different compared to the real deal like this. Much appreciated!
Yeah I've been checking out the piping commands for Linux. Thankfully since I work on CISCO routers and switches, I do a lot of that already. Of course, even though CISCO devices are "technically Linux" based, it's still vastly different compared to the real deal like this. Much appreciated!
The beauty of Linux and the joy of Slackware is that you get your computer back.
One doesn't want to give up the ability and authority once you have it.
There are lots of different ways to tweak your Slackware.
Sometimes I build everything from scratch the hard hard way.
OpenBoard is one example of that, but generally I use a mix of installable
packages from AlienBob and Ponce, slackbuilds, and executable binaries.
Package tools I use most often are slpkg (gives great feedback),
and sbopkg/sqg (the up-to-date stuff for -current is a plus).
Slackware64-current has been my daily driver for several years
and I keep updated to the very latest version of -current and
KDE5. That works best for me. I have used Ubuntu quite a bit,
but I no longer have Ubuntu around anymore. (I don't want or need a nanny.)
I don't do any gaming at all. There is no time for it.
I run a multi-boot system with two partitions containing Slackware64-current and I use the secondary
partition of slackware to repair the main one sometimes in case I goof something up.
ReFind is my efi multiboot manager and its website is quite useful.
I also have Windows10 because I have some software that doesn't run on Linux.
The main two of those at present are some high end camera software
(yes I know about gphoto2, gstreamer and et cetera),
and some voice to text transcription software (serious lament).
I have no other reasons for Windows, period.
Occasionally I am forced to use Windows for some other reasons to run something
that doesnt work on Linux. CorelDRAW and some Adobe tools used to be among those.
I can read and write my windows partitions with Linux and can copy files out of
Linux partitions while in windows10.
LinuxQuestions is the place to come to for really great community support.
Holy crap.... is that what they mean by dependency hell? Bring it on!!
Oh, no no no!
I personally would not touch that build. I would simply download the *.txz file from AlienBob's repository, and install it with
Quote:
installpkg <package name>.txz
You could build it, if you really want, using the script. But be aware that it is a much larger build than even huge projects like Wine or the kernel.
If you want to learn how to build software, I strongly recommend starting with smaller projects. If you use torrents, Transmission is a great example. So are most game engine ports, if you have the game files lying around. The Quake series, the various Doom engines, etc.
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.
I was a lurker on these forums for years just soaking up information from people much more knowledgeable than me. Eventually I realized I was able to start helping people with problems and I started contributing back. I still soak up information from people much more knowledgeable than me, but I at least can help back as well
I was a lurker on these forums for years just soaking up information from people much more knowledgeable than me. Eventually I realized I was able to start helping people with problems and I started contributing back. I still soak up information from people much more knowledgeable than me, but I at least can help back as well
I think I need to do that today. Maybe I can find other people who have issues I do know how to fix. That's actually a great idea.
Oh OK that makes sense. What about when I go into su mode? I notice when I go into su mode my alias's and colors are gone as well. I'm assuming that's a different profile? I probably shouldn't worry about using su right now.
Make a file named " .bashrc " and put it in /root directory, don't forget the period in front of the name that means it is a hidden file. Put the script below into that file, that will give you color when you go to root.
It will also give you several single commands, put your user name in
alias d="cd/home/username/Downloads" for a single d to go to Downloads.
Code:
# enable color support of ls and add handy aliases when root
if [ "$TERM" != "dumb" ]; then
eval "`dircolors -b`"
alias d="cd /home/username/Downloads"
alias c='clear'
alias h='history'
alias ls='ls --color=auto'
alias dir='ls --color=auto --format=vertical'
alias vdir='ls --color=auto --format=long'
alias dssh='ssh 192.168.5.104'
alias home="tput setaf 1; ssh -X -p 675 -i ~/home.key root@192.168.5.100; tput setaf 0"
PS1="\h \w # "
export HISTSIZE=4000
export HISTCONTROL=ignoreboth:erasedups
#echo 'export HISTCONTROL=ignoreboth:erasedups' >> ~/.bashrc
fi
I'm using this one because I was trying to learn how to assign aliases. It seem to be accepted by bash (or shell?) so I felt a sense of brief accomplishment.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
But don't worry... bigger mistakes have been made here!
