Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: Xconfig problems
- To: tlug@example.com
- Subject: tlug: Xconfig problems
- From: ulrike@example.com
- Date: Thu, 18 May 2000 17:41:34 +0900
- Cc: ulrike@example.com
- Reply-To: tlug@example.com
- Sender: owner-tlug
Hello, I am having problems with configuring X windows on debian, and before i start further experiments I think I have to change /etc/inittab so that the machine does not try to start x and I have tried to understand the inittab manpage but am forced to give up. The machine starts with runlevel 2, which I thought is ok, but later tries to start x out of some reasons ... here is /etc/inittab, but is the neccessary information in some other file, maybe?: # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.8 1998/05/10 10:37:50 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 #-- isdnutils begin # Change the lines below for your local setup and uncomment them. # Use "init q" to reread inittab. # look at the vboxgetty / mgetty manpage for more information (mgetty isn't # standard!) # #I0:2345:respawn:/usr/sbin/vboxgetty -d /dev/ttyI0 #I1:2345:respawn:/sbin/mgetty -D -m '"" ATZ OK AT&Eyourmsnhere OK AT&B512 OK' -s 38400 ttyI1 #-- isdnutils end My last configuration attempt ended in black-white-grey blinking garbage and I did not know how to get back to a console, and the system always started this garbage after bootup ... I read somewhere that the runlevel can be defined during bootup, I thought 2 would be nice, but this is what is written in the inittab, isn't it? Before my next try: how should I edit what? Or how can I get back to a console after garbage on my screen? Thanks -------------------------------------------------------------------- Next Nomikai Meeting: June 16 (Fri), 19:00 Tengu TokyoEkiMae Next Technical Meeting: July 8 (Sat) 13:30 Topic: TBA -------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
Home | Main Index | Thread Index
- Prev by Date: tlug: canna user dictionaries
- Next by Date: tlug: Hosting a Domain
- Prev by thread: tlug: canna user dictionaries
- Next by thread: tlug: Hosting a Domain
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links