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.
I've been back slipping in between the Slackware and windows and then Slackware again. Now my computer pretty much caught on fire (very long tragic story). So I bought a brand new mini notebook. To hold me over until I can rebuild a decent computer. Put Slackware on it. The issue are now is that I got put into a lab (where I work) of basically all Linux box's. Everyone has a distro they wanted to use in the Lab. So I said toss in slackware in the lab for me. The next day I went in the lab it was added to the boot of all the computers. The problem is I don't feel like I don't know alot of functional commands to properly navigate through command line. To at least be pretty functional in linux. To even be useful with my other colleagues. I feel like I never truly used the distro at the level I should have from the time I started trying to use it.
Also a side questions what's the major differences between Slackware live cd's LiveSlax and Slackware installs? I keep a liveslax cd around me. For my practice I suppose.
Last edited by IwannaSlack; 11-06-2009 at 11:45 AM.
I've been back slipping in between the Slackware and windows and then Slackware again. Now my computer pretty much caught on fire (very long tragic story). So I bought a brand new mini notebook. To hold me over until I can rebuild a decent computer. Put Slackware on it. The issue are now is that I got put into a lab (where I work) of basically all Linux box's. Everyone has a distro they wanted to use in the Lab. So I said toss in slackware in the lab for me. The next day I went in the lab it was added to the boot of all the computers. The problem is I don't feel like I don't know alot of functional commands to properly navigate through command line. To at least be pretty functional in linux. To even be useful with my other colleagues. I feel like I never truly used the distro at the level I should have from the time I started trying to use it.
What is it you need to do in the lab? (What kind of lab is it?) Can you use a desktop environment (KDE)? Are you looking to edit text files? Do you need to copy or move files around? Do you need to know the basic file/directory structure? Do you need to visit web sites?
I get what you mean about "functional commands to properly navigate through command line." Command line usage is no longer essential for most computing tasks, but it can be exceptionally powerful and efficient when you get to know them.
Xfce would also be a very good option. Pretty good GUI and also quite low on resource-use compared to other behemoths. Also, it comes bundled with the latest Slack, so no need to install external libs to make it work. As LJS says, the Slackbook is a great place to get started.
I was trying to quote everyone but that was not exactly working out so instead I am going to try to answer all the questions in this post. I mean I know some commands that I can think of off the top of my head. I know the startx(first command I learned I forgot to install KDE one time). ifconfig, poweroff,reboot,alsamixer,adduser,fstab somethings I know off the top of the head. Some what I would like to know is navigating through folders via command line. Using wifi in multiple mode
s like promiscuous mode. Or capture mode I have heard them used interchangeably. One they use often is netmap, tcpdump or something like that. been using Slack on and off since 7 and I am familiar with KDE this new XFce is all new to me.
Also they telnet into they telnet into the other box's all the time. I feel behind.
Last edited by IwannaSlack; 11-06-2009 at 03:49 PM.
The only way to learn something on the 'cli' is to attempt to perform the task(s) that you wish to gain experience from.
You can read all the cookbooks, recipe or reference docs but until you get the hands on then learning will not be benefited. Experiment, read then experiment some more.
To navigate to a folder is easy,, just cd [change directory]
cd /usr for instance.
To navigate to a folder within a folder or a folder within a folder within a folder is more tricky because you need to know where the folder is to begin with:
mc - for file operations
nano - text editor
mocp - console audio player
Bash 'tab' completion is useful, same for 'history' (or 'history | grep SEARCHWORD') command history.
'ls' or 'dir' shows directory contents.
'top' shows running processes, 'htop' achieves the same with friendlier interface.
'mkdir'
'rm'
'cp'
'ln'
'ssh' lets you to log in to a remote machine.
'sshfs' can mount remote machine filesystem to a local folder.
'man' displays manual pages.
I'm not cli literate, these are just few helpful utilities i mostly use.
Sometimes the apropos command helps find the command you are looking for. It can produce more than you need so you may like to filter the results, for example
Code:
apropos directory | grep -E '(\(1\))|(\(8\))'
Many man pages have a "SEE ALSO" section that lists related commands.
Can someone tell me how to connect to remote wireless networks via command line. Also some other questions I want to open up a box to connect via telnet. how can i get aircrack to work with slackware. they're is also a command to see all currently connected people.
Also this thread is actually helping me thanks everyone who contributed.
Last edited by IwannaSlack; 11-10-2009 at 11:58 AM.
Can someone tell me how to connect to remote wireless networks via command line. Also some other questions I want to open up a box to connect via telnet. how can i get aircrack to work with slackware. they're is also a command to see all currently connected people.
Also this thread is actually helping me thanks everyone who contributed.
I use the below;
Code:
sample 'wlan.sh';
#!/bin/bash
#
#10-26-09 13:30 gws
#setup the bcm4312 wlan0 device
#
/sbin/ifconfig wlan0 192.168.1.18
/sbin/route add default gw 192.168.1.1
/sbin/iwconfig wlan0 essid "your_ap" <<- your wireless
/sbin/iwconfig wlan0 key your_key <<- your_key
/sbin/iwconfig wlan0 ap 00:00:00:00:00:00 <<- your ap
Posts containing information about cracking, piracy, warez, fraud or any topic that could be damaging to either LinuxQuestions.org or any third party will be immediately removed.
I never considered it a violation of rules when they are all under my control in a supervised network. Also I was only considering alternatives to Remote desktop. However I would still like to thank everyone that helped contribute. This topic was mainly to extend my knowledge. A useful command I have found is netstats.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.