Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I'm running Slackware 12.2 on Xfce 4.4.3 with kernel 2.6.27.7 smp. I just finished fine tuning my desktop and installing the modules for my network interfaces. Anyhow, I have a BT3 cd which contains several lzm files. I did
lzm2dir pentest.lzm /
everything works perfectly. I can go into each directory in that /pentest directory. However, the windows_binaries folder cannot be accessed. When I try
cd /pentest/windows_binaries
it returns
bash: cd: windows_binaries: No such file or directory
This directory includes several .exe files. Do I need to enable ntfs support somehow? Maybe edit my /boot/config-huge-smp-2.6.27.7-smp and edit the CONFIG_NTFS_FS CONFIG_NTFS_RW lines? If so, how would I rebuild the kernel right after that?
Or do I need to somehow use ntfs-3g?
Also, when I'm in a terminal, how do I make it where if I execute ls, it shows different colors for the files and the directories? I'm currently using a .bashrc file. I've already defined all the colors in that file. What else do I need to do?
Do I put that ls --color=always in the .bashrc file? I tried it and now when I enter ls, nothing comes out. I have a black background in terminal so I'm thinking that something is wrong and that the output of ls is black. Here is my .bashrc file
[trist007@darkstar:~]$ cat .bashrc
# .bashrc
# User specific aliases and functions
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
Your .bashrc looks fine except you've commented out the alias line! Remove the '#' from the beginning of the line.
/pentest/windows_binaries is not a directory, it's a symbolic link - a pointer to another file, in this case /opt/windows_binaries/. Apparently /opt/windows_binaries/ doesn't exist, so the link is broken. I'm not sure why the link's there or why you thought there would be files inside it - what's a BT3 CD and what's an lzm file? Is it a bootable cd?
Ah, ok I got it. As for the ls --colors=always, yeah I had it uncommented and the output of ls was all black. Am I missing something on defining the colors?
Also another thing. I just got through installpkg laptop battery plugin for Xfce 4.4.3. Worked great. Then when I rebooted, the plugin had a null value, like the battery percentage and time was always at 0. Is there something I need to refresh?
I have no idea where did you take this from, but all this code does is to set a lot of variables which are never used in your bashrc by the way. So, we can assume that this code is useless as it is.
Code:
#alias ls= 'ls --color=auto'
Remove the space after =, and it might work then. Of course, remove the # as well, and open a new shell.
Also, you can use this command to see a list of defined aliases:
Code:
alias
If the ls line is not on that output and/or it's contents is incorrect then you have found your problem. Also, try ls --color=always on command line and see if it works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.