similar to: /etc/inittab

Here is my output: Console: colour dummy device 80x25 console [tty0] console [hvc0] installing Xen timer for CPU 0 Detected 1806.840 MHz processor Calibrating delay loop (skipped), value calculated using timer frequency.. 3613.68 BogoMIPS (lpj=7227360) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line) Apic siabled by BIOS Grant table initialized NET: Registering protocol

I did installation of CentOS5.5 in text mode and made changes at the following places in the file /etc/X11/xorg.conf : section "device" identifier : "vesa" driver:"vesa" section "screen" device:"vesa" Also in the file /etc/inittab I changed id:3:initdefault to id:5:initdefault so that I can boot linux in graphical mode. I had to make the changes

Help! I hosed my system and did a restore from a backup but when I boot, I get an error no inittab file found. Where can I get a 5.2, 'stock' inittab file not in a rpm so I can use a rescue disk to create this file? Or if possible, could someone please post their's for me? TIA

>On Thu, 2006-06-29 at 20:48 -0700, Chris Fox wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Rodrigo Barbosa wrote: >> >> > you might want to try agetty: >> > >> > T0:23:respawn:/sbin/agetty 9600 ttyS0 vt100 >> > >> > Not sure if it will work, but seems likely. >> > >> I've always

We have several suse 10.3 guests running in paravirtualization, however all the guests boot with the following messages: Loading keymap Couldnt open /dev/tty1 Loading /usr/share/kbd/keymaps/i386/qwerty/us.map.gz failed Loading compose table latin1.add failed Start Unicode mode Couldnt open /dev/tty1 Couldnt open /dev/tty2 Couldnt open /dev/tty3 Couldnt open /dev/tty4 Couldnt open

Hi, We are having a strange issue. If we run asterisk from /etc/inittab and then connect using asterisk -r, we don't see any logs coming in CLI. However logs are properly reported to /var/log/asterisk/messages and system is working fine. Now, if we run from command line (asterisk -f) and then usie asterisk -r, we properly see logs in CLI. This is bit strange and not able to solve this

Amazon (or perhaps Amazon's configuration of Xen) forces a machine to come up at run level 4, regardless of what's in /etc/inittab. I've looked through /etc/rc.sysinit and /etc/rc.d/rc, to determine which (if any script) looks at /proc/cmdline and forces a particular run level, but to no avail. It seems that /sbin/init does the forcing. Can anyone confirm that /sbin/init reads

Hello fellow CentOS sysadmins, I run a small multiplayer card game with around 500 users at peak times. The client is in Flash and the server is in Perl. The Perl server binds to port 8080, i.e. only 1 instance of it can be started (important detail). The Perl server poll()s TCP-sockets and forks only once - at the startup by calling this method: sub daemonize { die "Can not

Hello, sorry, for 1 more question on CentOS 5 -> CentOS 6 migration. On my old CentOS 5.7 machine I have the following line: pref:3:respawn:/bin/su -c '/usr/local/pref/pref.pl >/tmp/pref-`date +%a`.txt 2>&1' afarber and this has served me well, I don't want to install anything else like daemontools etc. - to keep my web-server easily reinstallable (or movable to

folks, Im trying to boot to runlevel 4 explicitly, using this stanza: ie with a single 4 at end of APPEND line. LABEL 2.6.11-r10c2-soekris-v1 MENU LABEL ^j. runlevel 4 2.6.11-r10c2-soekris-v1 # 4 MENU DEFAULT KERNEL vmlinuz-2.6.11-r10c2-soekris-v1 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo

I decided to upgrade from openSuse 10.2 to openSuse 10.3. I installed xen things, but when I boot using xen option the system is blocked. It appears the green window, with little suse logo in the middle, and mouse cursor, but the system crashes. My computer is a Pentium 4 1,5 GHz, 512 MB of RAM. I attached "diff boot.msg boot.omsg" (as diff opensuse-normal-kernel opensuse-xen-kernel)

Hi All, How does one best turn of X-Windows? I dont need it, ssh works just fine for me. I seem to recall it was complicated and since I know enough to do my stuf and not well versed yet in fixing things I break, I dont want to blow this up. Best, -ML

The following patch allows OpenSSH 2.2.0-p1 to be started (and managed) from /etc/inittab (by "init") on systems which support that. This is useful when you *really* want SSHD to always run since it will be automatically restarted by "init" if it dies (and if "init" dies the the systems dies :-). I use a line (in /etc/inittab) like this on Solaris systems:

Hi *, as this is my first post I want to say hello to everybody. Well, and unfortunatly I''ve already got a question for you: I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and it''s para-virtualised (just to provide the information ;) ). After the installation and mount the image containing the guest to copy the necessary modules for the xen-kernel,

One of these days, RedHat might actually run me off!!!! AAAARGH!!!! Can anyone tell me how to get CentOS 4 to simply boot to the console in text mode? If I wanted a stinkin' GUI I would have installed winders! Now, my KVM and 25 foot cord is just too long to send a GUI signal across the room and I'm missing 50% of the screen.. striped vertically.. at about 1/8th inch spacing. Not

We run a CentOS-5 based hylafax server with external serial modems. We are transitioning to an Asterisk system using IAXmodem running on CentOS-6. On the CentOS-5 system to start the fax modems we added these lines to inittab: # Add fax lines and always ALWAYS run "telinit q" after making a change. fax1:2345:respawn:/usr/sbin/faxgetty ttyS0 fax2:2345:respawn:/usr/sbin/faxgetty ttyS1

good tips ill try that out thanks ps is there a recommended runlevel or 2345 is ok? -----Original Message----- From: Lee Howard [mailto:faxguy@howardsilvan.com] Sent: Monday, January 09, 2006 1:59 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] OT: IAXModem in inittab causes modem to be unres ponsive, running from console it's OK Colin Anderson

Hi fellows, Pretty new to CentOS. I was trying to find a way to boot CentOS into command prompt instead of GUI (or without loading any services). Tried using 'Crl+Alt+F1' at the boot process, but, that holds the screen at mounting and doing fstab and doesn't proceed further. Is there anyother way to boot CentOS into command prompt without using Rescue option from the installation CD?

I installed xen 3.3.0 on a etch box from sources. I just modified the standard kernel cause of some hardware drivers. I installed xen-tools from backports (3.9-3~bpo40+1). To create a domU ist not the problem. I can connect via ssh and everything works fine. But when i start a domU with "xm create host.example.tld.cfg -c" to login to console from domU it hangs after the message

I have a server with all the x-windows stuff installed. But it's giving me a text based login prompt on the console. I can log onto the console, and run gnome-session and GNOME comes up fine. How do I turn it on so that I get a X-Window GUI login prompt? === Al