search for: colorl

Hello, I have several virtual machines, all with CentOS 6.x and one so called virtual server at a web hoster my virtual machines (VMware) were all installed manually using the .iso, some exist longer and therefore were originally a CentOS 6.3, some are newer and wer originally a CentOS 6.6; and this virtual server has been installed using a preconfigured image from the web hoster; on all

In dosdevices is the command ll (2 l's) in terminal window a valid command to see what devices are there.? I found this in LinuxForums. Now, Wine has simulated ports and drive letters in the ~/.wine/dosdevices directory. In there you will find symbolic links to the Linux paths of your physical devices. Go to that directory in a terminal window and type "ll" (two L's). You should

...ce left on device tar: ./etc/magic: Cannot write: No space left on device tar: ./etc/DIR_COLORS: Cannot write: No space left on device tar: ./etc/DIR_COLORS.256color: Cannot write: No space left on device tar: ./etc/DIR_COLORS.lightbgcolor: Cannot write: No space left on device tar: ./etc/profile.d/colorls.csh: Cannot write: No space left on device tar: ./etc/profile.d/colorls.sh: Cannot write: No space left on device tar: ./etc/skel/.bash_logout: Cannot write: No space left on device tar: ./etc/skel/.bash_profile: Cannot write: No space left on device tar: ./etc/skel/.bashrc: Cannot write: No space...

...ce left on device tar: ./etc/magic: Cannot write: No space left on device tar: ./etc/DIR_COLORS: Cannot write: No space left on device tar: ./etc/DIR_COLORS.256color: Cannot write: No space left on device tar: ./etc/DIR_COLORS.lightbgcolor: Cannot write: No space left on device tar: ./etc/profile.d/colorls.csh: Cannot write: No space left on device tar: ./etc/profile.d/colorls.sh: Cannot write: No space left on device tar: ./etc/skel/.bash_logout: Cannot write: No space left on device tar: ./etc/skel/.bash_profile: Cannot write: No space left on device tar: ./etc/skel/.bashrc: Cannot write: No space...

we started using an ocfs file system about 4 months ago as the shared archived redo destination for the 4-node rac instances (HP dl380, msa1000, RH AS 2.1) . last night we are seeing some weird behavior, and my guess is the inode directory in the file system is getting corrupted. I've always had a bad feeling about OCFS not being very robust at handling constant file creation and deletion

CentOS-6 When I login as root I see this prompt: [root at vhost04 ~]# When I login as a non-priviledged user I see this instead: sh-4.1$ .bashrc and .bash_profile have identical contents in /root and /home/user. What causes the difference? Why? How does one change the default so that all normal users get a [userid at hostname pwd]$ prompt? I have loked in/etc/profile.d and /etc/bashrc