I know that in an xterminal I can redefine the default colour with something like
!!red
URxvt.color1: rgb:cc/00/00
URxvt.color9: rgb:ef/29/29
Is it possible to do something similar in the Linux (framebuffer) console?
Does anyone know how to make the file colours appear different for each file type in the shell like happens in ubuntu?
View 4 Replies View RelatedHow can I change the colour for each virtual console seperately?I.e. blue for console 1, green for console 2, etc. I'm using SuSE 11.4.It worked under SuSE 11.1 like a charm
View 9 Replies View RelatedI want to set the default colours for the vttys but can't seem to find where the defaults are kept, I can set up the vtty as I like via setterm in .bashrc etc but as soon as I do an ls or vim on return the colours are reset to white on black, been googling this but can't find an answer, any ideas?
View 2 Replies View RelatedI use putty to ssh to linux box. By default I get black screen background with white foreground.
To change colours, I go to change settings -> Window/colours and then I set background colours as white and foreground colours as black. This is more easy on my eyes. But I can't seem to be able to set this colour setting as default and each time I login, I have to set colours.
Could someone please suggest a solution?
A week ago I opened this thread viewtopic.php?f=17&t=61580 in "Board index ‹ Help ‹ Installation" and asked for a moderator to move this to here. Because it hasnt happened up to know, I am reopening the thread here. It would be reeeeally great if somebody could help me with my problem!
I own two computers, one netbook and one laptop. I want to boot my netbook as a diskless client via PXE.I set up a dhcp-, tftp and nfs-server on my laptop but when i boot my netbook, the follwoing messages are displayed:(to make it more clear, i uploaded the whole output and shortened the output below)
[Code]...
The resolution is OK in grub menu but after something is setting to higher value. How can i set it back to 640x480?
View 1 Replies View RelatedI would like to put an image in the background of my console (tty) like done by Gentoo or Suse : I found several tracks to follow, but I would like to have your advice on the best way to do that for Debian.
View 3 Replies View RelatedI'm trying Debian again just for fun after using Slackware for years. When I "su -" on Konsole in Debian I get this for my prompt:
Code:
darksaurian@darkswamp:~$ su -
Password:
darkswamp:~#
darkswamp is my hostname that I made up when I installed. On Slackware I'm used to it saying:
root@darkswamp
or something like that.
I'm starting Konsole the same way on both:
konsole -e $SHELL -l
I kind of wish it still said "root" just because I'm used to it.
I know there are many threads regarding this topic.I probably read most of them. At installation time I told Debian to use German keyboard layout (since I am from Germany). Now I want to switch it to American keyboard layout. In X this was no problem. But in the tty consoles I cant get it changed. It does not matter to me if it is system wide or user wide because I am the only user. (system wide would be a little bit more preferrable because it would affect the super user too, I think).I tried dpkg-reconfigure console-data
and selecting my desired layout. This changes the Layout to American until reboot
I've been scouring the internet for an answer to this problem. I am using Squeeze and have properly configured Grub2 to set my console screen resolution to 1024x768x32 (as per updating /etc/default/grub to contain 'GRUB_GFXMODE=1024x768x32' and updating /etc/grub.d/00_header to contain 'set gfxpayload=keep') and everything works wonderfully. My resolution is set as it should be. However upon installing Xorg (aptitude install xorg ratpoison), my console resolution gets changed to what appears to be 1280x1024.
I thought that this was due to xrandr, however when I issue:
# xrandr -s 1024x768
only the X resolution is changed. When I then CTRL-ALT-F1 back to the console, the resolution is still at 1280x1024 (I am aware that xrandr only affects X, but I assumed that because my console resolution was correct before installing X there might have been some correlation).
I would like for my console resolution to stay at 1024x768 as per Grub2's configuration and for X's resolution to be at 1280x1024.
PS I also noticed that prior to installing Xorg, my CPU boots up without any screen blanking (only for a second or so). However, after installing Xorg, during the boot process the screen does blank briefly. It is at that time that the resolution gets changed to the 1280x1024 setting.
I installed the base of Debian (only CD 1) without the desktop environment, so it is console only; also I am dual booting with Windows 7 x64 on this Dell Inspiron 1545 laptop... I have also successfully mounted my usb flash drive and CD drive; the one thing I am finding rather hectic is finding a way to connect to my wireless network with a "WPA2 Personal" Security and "TKIP/AES" Encryption with a Dell Wireless 1397 WLAN Mini-Card... I doubt that the drivers are actually installed, and Idk how to install them.Google searches on this yield confusing results, so I need help. So far, the most useful help I have found is the link posted here: http://en.community.dell.com/support-fo ... 29916.aspx but I have no idea on how to install that, if it is even what I need.
View 5 Replies View RelatedReinstalled Debian Squeeze (64bit/gnome) on my Notebook using Netinstall. Everything worked like always but in the setup instead of typing in a root password as asked to i just pressed enter (in the hope of not having to type in a pw in the console later, just having to press enter then)
When i needed rootpw to install some software (using SoftwareDownloader) the normal loginpw seemed to work, but not in the console.
ari@HP625:~$ su -
Password:
su: Authentication failure
[Code]....
I just installed Debian 6 and need to change the console keyboard layout (I am not running any sort of gui).I installed 'console-data' and ran:# dpkg-reconfigure console-dataThis assigns my Apple keyboard keys perfectly but it won't survive a reboot, which is really important for entering passwords
View 2 Replies View RelatedSince moving my debian server over to a Gigabyte H97N-WIFI motherboard the console dims on booting and generally stays dark. Strangely the screen the brightens up if I go to an emergency shell, but if the boot runs successfully I don't see the resulting login prompts. Also, during the boot process the messages to the console are too dark to see.
I've tried the i915.invert_brightness=1 fix mentioned here [URL].... but that seems to have no effect. I'm assuming that this has something to do with moving to intel graphics as my previous hardware had a radeon graphics card and didn't display this problem.
I'm always getting a blank console screen after booting a 2.6.32-trunk-amd64 kernel in squeeze. I still can read the line "Loading, please wait ..." in the display for a second - then it's completely black until X windows is starting. When I try switching from the X console to another virtual console (by pressing Ctrl-Alt-F1 e. g.), the complete system freezes. I have to hard reboot then.When I boot the previous 2.6.32-3-amd64 kernel instead, everything is fine as expected, though.There's a line "GRUB_GFXMODE=1024x768x16@60" in /etc/default/grub as well as a line "set gfxpayload=keep" in /etc/grub.d/00_header. So the problem might be framebuffer related in any way. Any ideas what could be tried?The system is a Latitude E6500 with a Mobile 4 Series Chipset Integrated Graphics Controller
View 2 Replies View RelatedThis only started after the recent updates which included a lot of sysv stuff in Squeeze. I'm not talking the Gnome or Xwindows consoles, I'm talking the full-on type you get when you do the CTL-ALT-F2 type of console. before those updates, I had no trouble. Now I can't get back into the gui by pressing CTL-ALT-F7 as usual. All i get is just a black screen. I do have the nvidia proprietary driver installed using DKMS, and I am running the latest (I think) liquorix kernel.
View 5 Replies View RelatedAfter install debian 8, I can't see system start and stop message from console ... How can I enable system message from console in debain 8?
debian 7 output
----------------------------------------------
root@demo:~# service apache2 restart
[ ok ] Restarting web server: apache2 ... waiting .
root@demo:~#
debian 8 output
-----------------------------------------------
root@demo:~# service apache2 restart
root@demo:~# <=============================== No message (start or stop)
After an update on squeeze about a week or two ago, my console font turned green. I'm not exactly sure of the timing, because I switch between lenny and squeeze, and some time passed between the update and the reboot in squeeze.
During the update, I was asked if I wanted to keep my altered /etc/grub.d/00_header or take the package maintainer's version. I took the PM's version, knowing I'd lose my edit (set gfxpayload=1024x768x16). When I add that line to the new 00_header, run update-grub and reboot, the console font is the size I want, but it's a dull green. Reminds me of my first computer. How do I get it back to white and keep the 1024x768 resolution?
Currently booting with grub-legacy and chainloading grub2. If I boot entirely with grub-legacy, and pass vga=791, the console font will be white. It doesn't matter which kernel I use. Currently, I'm running 2.6.32-3-686. Same behavior exists if I use 2.6.30-2-686. If I use 1024x768x8 I get a dull gray instead of dull green.
I have my X11 setup configured to rotate 90s counterclockwise for a portrait monitor. But when the system turns on, it's in the framebuffer console which is set to landscape mode. Is there a way to set it so that even the console is rotated in portrait mode? I'd like to do this automatically.
View 6 Replies View RelatedI have been using my system for couple of weeks, and normally update software when the icon is displayed on top bar (gnome). Last couple of days there were updates for X, and I am not sure whether that is the cause of my problem. Once bootup, I get the login screen. When enter the password the login screen keep coming back. there is no error about any password issue, or anything. It keeps prompt me to enter the password.
I could login back the following way.
1. ctrl + alt + F1 , and login with the same username/pwd as for X
2.change to root
3.pkill gdm3
4.exit from root to user privilege
5. startx
The system starts X correctly and no login screen is displayed. I could use the system as usual.
The only thing I did custom to my system was upgrading to the latest kernel (2.6.38) using the source. This was to get support for my hardware, but that was about a month ago. I do not see anything in /var/log (X, demesg etc).
I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
View 6 Replies View RelatedMy Squeeze installation has the horrific 80x25 line display, and I cannot stand it. I know it can do better, because the grub screen is very tiny. I ran dpkg-reconfigure console-setup, but the offerings there aren't much better. I don't know what happened to the good ol' days of grub when all you had to do was pass vga=791 to the kernel to get a decent console size... but it seems they are gone.
I don't really understand this new v2 grub... I don't know why it was necessary to change how it was configured, when it seemed to work so exquisitely. how I would accomplish the functional equivalent of passing vga=791 (1024x768@75hz) to the kernel in grub
On this moment i build an webenvironment with wordpress, apache2, debian 8. On this moment i try to impelement Varnish.
By default this application use the port 6081. I try to put apache on port 8080. This already works but i get varnish not running on port 80.
You can see below that varnish still listen to the default port 6081. How can i fix this?
Code: Select allroot@webI:/home/beheerder# netstat -lpt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:ssh *:* LISTEN 2917/sshd
tcp 0 0 *:6081 *:* LISTEN 3717/varnishd
tcp 0 0 localhost:6082 *:* LISTEN 3699/varnishd
[Code] ....
To test another port i have also try to start Varnish on port 85.
Code: Select allvim /etc/default/varnish
DAEMON_OPTS="-a :85
-T localhost:6082
-f /etc/varnish/default.vcl
-S /etc/varnish/secret
-s malloc,256m"
I have restart the apache and varnish services. I have also rebooted the server but varnish will not listen on port 80 (or other non default ports). On port 6081 the application works fine. But how can i fix this ?
Source Varnish port 80
I can use the application with the following command
Code: Select allvarnishd -f /etc/varnish/default.vcl -a 0.0.0.0:80.
But why is this not working with the normal config file. Varnish are than listen to port 80. With every server reboot i need than to run this command. So i would like to use the config file.
I run Debian Squeeze on my Lenovo ThinkPad W500. Today I tried to use the expresscard slot on the device and was disappointed to find that it didn't work. A bit of digging revealed that the pciehp module was not loaded (but is required for hot-plugging these kinds of devices).Can anyone explain to me why this is the case? All other hardware on my system has had the module auto-loaded on boot-up, but why not pciehp for my expresscard slot?
View 2 Replies View RelatedAnyone know what the 'ls' command means when it outputs the file name in red on black, with the permissions, owner, etc. all missing? The 'man' page was of no help. In the example below, from a DVD ROM, the third file was OK and I could read it. The first two could not be read, even as root.
?--------- ? ? ? ? /media/dvdrom/DVD_RTAV/VR_MANGR.BUP
?--------- ? ?? /media/dvdrom/DVD_RTAV/VR_MOVIE.VRO
-rwxrwxrwx 1 root root 132624 2007-09-20 02:18 VR_MANGR.IFO
I installed it from the packages list and the eye candy has been good.
However, in trying to fix an error showing up in syslog
Feb 1 17:37:38 host ntop[30764]: **ERROR** Buffer too short @ dataFormat.c:144 (increase to at least 56) [230982 years, 187 days 7:107374]
I started looking at the configuration files; well attempted. It asks for a login. It isn't any user or root, but apparently is admin, but IO don't ever remember setting it.
Various web search suggests it is done at compile(downloaded compiled) /installation, but I have no recollection of entering any.
There is a Redhat/Centos wrinkle ntop -set-admin-passwd=password; but that puts out a lot of lines, then hangs and has no effect.
Note, despite message(old version of ntop), it is up todate in packages.
I've been working on my servers, one of them is Ubuntu and the other one is Debian (Newest), and both seams to have a problem with charset configuration.
They wont register ISO-8859-1, insted it says no value when i look at it with phpinfo() function. It's importen that i feel this is working.
i have created a wordpress user with a symbolic link from his home (/home/wordpress) to /usr/share/wordpress but when wordpress ftps to wordpress home dir it does not follow the sym-link. is there a way to set default ftp dir for the wordpress user to /usr/share/wordpress rather than /home/wordpress?
View 6 Replies View Relatedif you try to browse the web from the machine, or log in through a nomachine (nxclient/nxserver) session, it claims there is no internet conenction. You have to run System|Administration|Network and select the stored "Location" for our wired connection. There does not seem to be an option to make this (one and only) "Location" the default. If the machine is up and incoming connections are possible (samba & apache), surely outgoing connections should be working without extra fiddling?
The issue with nxserver (nomachine) becoming unavailable on a re-booted unattended machine (unless someone logs in AT THE MACHINE and runs System|Administration|Network) is causing problems for remote access.