Re: [expert] Can't Break X Autostart
Ok, if any of you experts have been holding baack while I was working on this, please jump in now. I'm totally stumped. Lane's theory sound ok to me, but we've definately exceeded my level of expertise here. Lane Lester wrote: > > Brian T. Schellenberger said: > > I didn't mean rc.local; I meant /etc/rc.d/init.d > > That directory holds the following: > anacron* gpm* linuxconf-setup@ postfix* usb* > apmd*halt* lpd* postgresql* vmware* > atd* inet* mandrake_everytime* random* xfs* > autofs* innd* mandrake_firstime* routed* xntpd* > crond* keytable* mysql* single* > dhcpd* killall* netfs* smb* > fonttastic* kudzu* network* snmpd* > functions* ldap* numlock* syslog* > > I wonder if it could be the linuxconf-setup link. Just before the switch to > runlevel 5, there is some linuxconf stuff, including a line I don't remember > from the original install, "Dropin's commands" or something like that. I =did= > install a newer version of linuxconf. > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
RE: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > Also, w/r/t to your previous comment on the same topic, he pasted in a > big of his init script. He seems to start at runlevel 3 and then get > mysteriously switched to runlevel 5. > Nonetheless, pasting in his entire /etc/inittab and /etc/lilo.conf > files is probably good advice . . . I sent my lilo.conf, and my inittab is below my sig. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go... id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Things to run in every runlevel. # commented out by Lane # ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # Run gettys in standard runlevels 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mgetty ttyS1 # Run xdm in runlevel 5 # xdm is now a separate service #x:5:respawn:/etc/X11/prefdm -nodaemon #x:5:respawn:ps alwf > /root/ps-output
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > I didn't mean rc.local; I meant /etc/rc.d/init.d That directory holds the following: anacron* gpm* linuxconf-setup@ postfix* usb* apmd*halt* lpd* postgresql* vmware* atd* inet* mandrake_everytime* random* xfs* autofs* innd* mandrake_firstime* routed* xntpd* crond* keytable* mysql* single* dhcpd* killall* netfs* smb* fonttastic* kudzu* network* snmpd* functions* ldap* numlock* syslog* I wonder if it could be the linuxconf-setup link. Just before the switch to runlevel 5, there is some linuxconf stuff, including a line I don't remember from the original install, "Dropin's commands" or something like that. I =did= install a newer version of linuxconf. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
"Brian T. Schellenberger" wrote: > > Actually, we've *already* solved his problem in a practical sense. > He's got his system operating as he wants it. > > He's just indulging us in trying to solve the mystery of why it was > acting oddly in the first place, and a re-install won't accomplish > *that*! Exactly -- this is a significant learning opportunity. Poor Lane. -Stephen-
Re: [expert] Can't Break X Autostart
Drat! I didn't mean rc.local; I meant /etc/rc.d/init.d On Mon, 10 Apr 2000, you wrote: | Brian T. Schellenberger said: | > Yes, but what rc.5 has is irrelevent; the question is: "why are we | > using rc.5 in the *first* place? -- what's putting us into run-level 5?" | > | > Do you have an init in the rc.local at all?(Possibly linked in for | > run-level 3.) I suspect not, and that 'init' is some "special" magical | > string that will require a more expert expert than me to decipher, but | > I figured we could eliminate the obvious first. | | I don't see anything like that in rc.local (copied below sig). | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... | | #!/bin/sh | # | # This script will be executed *after* all the other init scripts. | # You can put your own initialization stuff in here if you don't | # want to do the full Sys V style init stuff. | | if [ -f /etc/mandrake-release ]; then | R=$(cat /etc/mandrake-release) | | arch=$(uname -m) | a="a" | case "_$arch" in | _a*) a="an";; | _i*) a="an";; | esac | | NUMPROC=`egrep -c "^cpu[0-9]+" /proc/stat` | if [ "$NUMPROC" -gt "1" ]; then | SMP="$NUMPROC-processor " | [ "$NUMPROC" = "2" ] && \ | SMP="Bi-processor " | if [ "$NUMPROC" = "8" -o "$NUMPROC" = "11" ]; then | a="an" | else | a="a" | fi | fi | | # This will overwrite /etc/issue at every boot. So, make any changes you | # want to make to /etc/issue here or you will lose them when you reboot. | | if [ -x /usr/bin/linux_logo ];then | /usr/bin/linux_logo -c -n -f > /etc/issue | echo "" >> /etc/issue | else | > /etc/issue | fi | echo "$R" >> /etc/issue | echo "Kernel $(uname -r) on $a $SMP$(uname -m) / \l" >> /etc/issue | | echo "Welcome to %h" > /etc/issue.net | echo "$R" >> /etc/issue.net | echo "Kernel $(uname -r) on $a $SMP$(uname -m)" >> /etc/issue.net | fi | #insmod ide-scsi | #modprobe ide-scsi | /usr/local/sbin/ledd 1>/dev/null 2>&1 & -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
RE: [expert] Can't Break X Autostart
Actually, we've *already* solved his problem in a practical sense. He's got his system operating as he wants it. He's just indulging us in trying to solve the mystery of why it was acting oddly in the first place, and a re-install won't accomplish *that*! Also, w/r/t to your previous comment on the same topic, he pasted in a big of his init script. He seems to start at runlevel 3 and then get mysteriously switched to runlevel 5. Nonetheless, pasting in his entire /etc/inittab and /etc/lilo.conf files is probably good advice . . . On Mon, 10 Apr 2000, you wrote: | Of course, this all begs the question... | | Why spends days debugging this when a simple reinstall (an hour) would most | likely fix it? | | That's one of the reasons I always design my systems so that I can reinstall | the OS without destroying any of my data. One of the powers of Linux. I'm | able to backup a few scripts, re-install the OS, and then restore those | scripts. Less that 2 hours later, my entire system is back up and running. | | Of course, there's probably a simple explanation as to *WHY* this is | happening, and it would be shorter to fix that... Once we know what's | happening. | | Russ -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > Yes, but what rc.5 has is irrelevent; the question is: "why are we > using rc.5 in the *first* place? -- what's putting us into run-level 5?" > > Do you have an init in the rc.local at all? (Possibly linked in for > run-level 3.) I suspect not, and that 'init' is some "special" magical > string that will require a more expert expert than me to decipher, but > I figured we could eliminate the obvious first. I don't see anything like that in rc.local (copied below sig). -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. if [ -f /etc/mandrake-release ]; then R=$(cat /etc/mandrake-release) arch=$(uname -m) a="a" case "_$arch" in _a*) a="an";; _i*) a="an";; esac NUMPROC=`egrep -c "^cpu[0-9]+" /proc/stat` if [ "$NUMPROC" -gt "1" ]; then SMP="$NUMPROC-processor " [ "$NUMPROC" = "2" ] && \ SMP="Bi-processor " if [ "$NUMPROC" = "8" -o "$NUMPROC" = "11" ]; then a="an" else a="a" fi fi # This will overwrite /etc/issue at every boot. So, make any changes you # want to make to /etc/issue here or you will lose them when you reboot. if [ -x /usr/bin/linux_logo ];then /usr/bin/linux_logo -c -n -f > /etc/issue echo "" >> /etc/issue else > /etc/issue fi echo "$R" >> /etc/issue echo "Kernel $(uname -r) on $a $SMP$(uname -m) / \l" >> /etc/issue echo "Welcome to %h" > /etc/issue.net echo "$R" >> /etc/issue.net echo "Kernel $(uname -r) on $a $SMP$(uname -m)" >> /etc/issue.net fi #insmod ide-scsi #modprobe ide-scsi /usr/local/sbin/ledd 1>/dev/null 2>&1 &
RE: [expert] Can't Break X Autostart
Russ Johnson said: > /etc/inittab is the file that controls how init works. You can override > inittab by specifying a parameter at the lilo prompt. So, that being the > case, let's see what's in the /etc/lilo.conf file. All of it. You got it! boot = /dev/hda timeout = 200 prompt vga = extended read-only other = /dev/hda3 label = win image = /boot/vmlinuz-2.2.14-15mdk label = mx vga = normal append = "mem=124M" # append = "hdc=ide-scsi mem=124M" root = /dev/hdb8 read-only image = /boot/vmlinuz-2.2.14-15mdk label = mc vga = normal append = "init 3" root = /dev/hdb8 read-only image = /mnt/mandrake2boot/vmlinuz label = m2 vga = normal append = "mem=124M" root = /dev/hda7 -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
RE: [expert] Can't Break X Autostart
Of course, this all begs the question... Why spends days debugging this when a simple reinstall (an hour) would most likely fix it? That's one of the reasons I always design my systems so that I can reinstall the OS without destroying any of my data. One of the powers of Linux. I'm able to backup a few scripts, re-install the OS, and then restore those scripts. Less that 2 hours later, my entire system is back up and running. Of course, there's probably a simple explanation as to *WHY* this is happening, and it would be shorter to fix that... Once we know what's happening. Russ
RE: [expert] Can't Break X Autostart
"Normally", the init level is set by the first non-comment line in /etc/inittab. Mine says: id:3:initdefault: and my system does properly boot to runlevel 3. /etc/inittab is the file that controls how init works. You can override inittab by specifying a parameter at the lilo prompt. So, that being the case, let's see what's in the /etc/lilo.conf file. All of it. Russ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brian T. Schellenberger Sent: Sunday, April 09, 2000 8:40 PM To: [EMAIL PROTECTED] Subject: Re: [expert] Can't Break X Autostart Yes, but what rc.5 has is irrelavent; the question is: "why are we using rc.5 in the *first* place? -- what's putting us into run-level 5?" Do you have an init in the rc.local at all? (Possibly linked in for run-level 3.) I suspect not, and that 'init' is some "special" magical string that will require a more expert expert than me to decipher, but I figured we could eliminate the obvious first.
Re: [expert] Can't Break X Autostart
Yes, but what rc.5 has is irrelavent; the question is: "why are we using rc.5 in the *first* place? -- what's putting us into run-level 5?" Do you have an init in the rc.local at all? (Possibly linked in for run-level 3.) I suspect not, and that 'init' is some "special" magical string that will require a more expert expert than me to decipher, but I figured we could eliminate the obvious first. On Sun, 09 Apr 2000, you wrote: | Brian T. Schellenberger said: | > | Apr 9 12:38:36 localhost mandrake_everytime: Building Window Manager | > Sessions | > | succeeded | > | Apr 9 12:38:40 localhost init: Switching to runlevel: 5 | > | > Well, this is where you're switching to run-level 5. You didn't want | > to do that. It's happening in "init". | > | > I don't have such a service on my machine, do you have a file called | > /etc/rc.d/init.d? Is this listed in your run-level 5 startup? | | I have a =directory= by that name, and it's full of all kinds of boot-time | programs. | And /etc/rc.d/rc.5 has symlinks to 15 of the programs in init.d. Here are the | links: | K08autofs@ K50snmpd@ S10network@ S50inet@ S90xfs@ | K35smb@ K55routed@S30syslog@ S60lpd@ S99linuxconf-setup@ | K40ldap@S05kudzu@ S40crond@S75keytable@ S99local@ | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
I just realized that this mail of mine might confuse people a bit.
Please notice that I had comments in the middle of the messages as well
as in the middle of the original message.
On Sun, 09 Apr 2000, you wrote:
| On Sun, 09 Apr 2000, you wrote:
| | Brian T. Schellenberger said:
| | > A possible way to find out is to do a
| | >
| | > ps alwf > /root/ps-output
| | >
| | > when you go to run-level 5; eg, put this:
| | >
| | > :5:respawn:ps alwf > /root/ps-output
| | >
| | > in your /etc/inittab. Then we can at least see what's going on when
| | > this happens.
| |
| | I added the second line to inittab:
| | #x:5:respawn:/etc/X11/prefdm -nodaemon
| | x:5:respawn:ps alwf > /root/ps-output
| |
| | I put the x at the beginning after the system complained about nothing being
| | there
| | I'm probably still not doing this right somehow, because I'm not getting
| | anything informative.
| | This one line is all it says:
| | F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTYTIME COMMAND
| |
|
| That's all that's in your /root/ps-output file?
|
| Odd.
|
|
| | At boot time, there's the message that the line is respawning too fast and will
| | be paused for 5 minutes.
| |
| | > Also, your /var/log/messages might show something about switching to
| | > run-level 5. Perhaps it will give a clue to who is doing it?
| |
| | I'll the lines from one boot below my sig.
| | --
| | Lane
| |
| | Lane Lester / Madison County, Georgia USA
| | Using Linux to get where I want to go...
| |
| | Apr 9 12:38:52 localhost syslogd 1.3-3: restart.
| | Apr 9 12:38:52 localhost syslog: syslogd startup succeeded
| | Apr 9 12:38:52 localhost kernel: klogd 1.3-3, log source = /proc/kmsg started.
| | Apr 9 12:38:52 localhost syslog: klogd startup succeeded
| | Apr 9 12:38:52 localhost kernel: Inspecting /boot/System.map-2.2.14-15mdk
| | Apr 9 12:38:52 localhost kernel: Loaded 6230 symbols from
| | /boot/System.map-2.2.14-15mdk.
| | Apr 9 12:38:52 localhost kernel: Symbols match kernel version 2.2.14.
| | Apr 9 12:38:52 localhost kernel: Loaded 151 symbols from 10 modules.
| | Apr 9 12:38:53 localhost crond: crond startup succeeded
| | Apr 9 12:38:27 localhost rc.sysinit: Mounting proc filesystem succeeded
| | Apr 9 12:38:27 localhost date: Sun Apr 9 12:38:26 EDT 2000
| | Apr 9 12:38:27 localhost rc.sysinit: Setting clock : Sun Apr 9 12:38:26 EDT
| | 2000 succeeded
| | Apr 9 12:38:27 localhost rc.sysinit: Loading default keymap succeeded
| | Apr 9 12:38:27 localhost rc.sysinit: Activating swap partitions succeeded
| | Apr 9 12:38:27 localhost rc.sysinit: Setting hostname localhost succeeded
| | Apr 9 12:38:27 localhost fsck: /dev/hdb8: clean, 94544/261120 files,
| | 422329/522104 blocks
| | Apr 9 12:38:27 localhost rc.sysinit: Checking root filesystem succeeded
| | Apr 9 12:38:27 localhost isapnp: Board 1 has Identity 9a 0b 43 20 32 9e 00 8c
| | 0e: CTL009e Serial No 188948530 [checksum 9a]
| | Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[0]{Audio }:
| | Ports 0x220 0x330 0x388; IRQ5 DMA1 DMA5 --- Enabled OK
| | Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[1]{Game}:
| | Port 0x200; --- Enabled OK
| | Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[2]{WaveTable }:
| | Ports 0x620 0xA20 0xE20; --- Enabled OK
| | Apr 9 12:38:27 localhost rc.sysinit: Setting up ISA PNP devices succeeded
| | Apr 9 12:38:27 localhost rc.sysinit: Remounting root filesystem in read-write
| | mode succeeded
| | Apr 9 12:38:27 localhost rc.sysinit: Loading sound module succeeded
| | Apr 9 12:38:34 localhost rc.sysinit: Loading midi module succeeded
| | Apr 9 12:38:34 localhost rc.sysinit: Checking filesystems succeeded
| | Apr 9 12:38:35 localhost rc.sysinit: Mounting local filesystems succeeded
| | Apr 9 12:38:35 localhost rc.sysinit: Turning on user and group quotas for
| | local filesystems succeeded
| | Apr 9 12:38:35 localhost rc.sysinit: Enabling swap space succeeded
| | Apr 9 12:38:36 localhost mandrake_everytime: Building Window Manager Sessions
| | succeeded
| | Apr 9 12:38:40 localhost init: Switching to runlevel: 5
|
| Well, this is where you're switching to run-level 5. You didn't want
| to do that. It's happening in "init".
|
| I don't have such a service on my machine, do you have a file called
| /etc/rc.d/init.d? Is this listed in your run-level 5 startup?
|
| Does anybody else know if there's some other place where an "init"
| would be started?
|
|
| | Apr 9 12:38:50 localhost kudzu: succeeded
| | Apr 9 12:38:51 localhost network: Bringing up interface lo succeeded
| | Apr 9 12:38:53 localhost inet: inetd startup succeeded
| | Apr 9 12:38:53 localhost lpd: lpd startup succeeded
| | Apr 9 12:38:53 localhost loadkeys: Loading
| | /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
| | Apr 9 12:38:53 localhost keytable: Loading keymap: us succeeded
| | Apr 9 12:38:53 localhost loadkey
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > | Apr 9 12:38:36 localhost mandrake_everytime: Building Window Manager > Sessions > | succeeded > | Apr 9 12:38:40 localhost init: Switching to runlevel: 5 > > Well, this is where you're switching to run-level 5. You didn't want > to do that. It's happening in "init". > > I don't have such a service on my machine, do you have a file called > /etc/rc.d/init.d? Is this listed in your run-level 5 startup? I have a =directory= by that name, and it's full of all kinds of boot-time programs. And /etc/rc.d/rc.5 has symlinks to 15 of the programs in init.d. Here are the links: K08autofs@ K50snmpd@ S10network@ S50inet@ S90xfs@ K35smb@ K55routed@ S30syslog@ S60lpd@ S99linuxconf-setup@ K40ldap@S05kudzu@ S40crond@S75keytable@ S99local@ -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
On Sun, 09 Apr 2000, you wrote:
| Brian T. Schellenberger said:
| > A possible way to find out is to do a
| >
| > ps alwf > /root/ps-output
| >
| > when you go to run-level 5; eg, put this:
| >
| > :5:respawn:ps alwf > /root/ps-output
| >
| > in your /etc/inittab. Then we can at least see what's going on when
| > this happens.
|
| I added the second line to inittab:
| #x:5:respawn:/etc/X11/prefdm -nodaemon
| x:5:respawn:ps alwf > /root/ps-output
|
| I put the x at the beginning after the system complained about nothing being
| there.
| I'm probably still not doing this right somehow, because I'm not getting
| anything informative.
| This one line is all it says:
| F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTYTIME COMMAND
|
That's all that's in your /root/ps-output file?
Odd.
| At boot time, there's the message that the line is respawning too fast and will
| be paused for 5 minutes.
|
| > Also, your /var/log/messages might show something about switching to
| > run-level 5. Perhaps it will give a clue to who is doing it?
|
| I'll the lines from one boot below my sig.
| --
| Lane
|
| Lane Lester / Madison County, Georgia USA
| Using Linux to get where I want to go...
|
| Apr 9 12:38:52 localhost syslogd 1.3-3: restart.
| Apr 9 12:38:52 localhost syslog: syslogd startup succeeded
| Apr 9 12:38:52 localhost kernel: klogd 1.3-3, log source = /proc/kmsg started.
| Apr 9 12:38:52 localhost syslog: klogd startup succeeded
| Apr 9 12:38:52 localhost kernel: Inspecting /boot/System.map-2.2.14-15mdk
| Apr 9 12:38:52 localhost kernel: Loaded 6230 symbols from
| /boot/System.map-2.2.14-15mdk.
| Apr 9 12:38:52 localhost kernel: Symbols match kernel version 2.2.14.
| Apr 9 12:38:52 localhost kernel: Loaded 151 symbols from 10 modules.
| Apr 9 12:38:53 localhost crond: crond startup succeeded
| Apr 9 12:38:27 localhost rc.sysinit: Mounting proc filesystem succeeded
| Apr 9 12:38:27 localhost date: Sun Apr 9 12:38:26 EDT 2000
| Apr 9 12:38:27 localhost rc.sysinit: Setting clock : Sun Apr 9 12:38:26 EDT
| 2000 succeeded
| Apr 9 12:38:27 localhost rc.sysinit: Loading default keymap succeeded
| Apr 9 12:38:27 localhost rc.sysinit: Activating swap partitions succeeded
| Apr 9 12:38:27 localhost rc.sysinit: Setting hostname localhost succeeded
| Apr 9 12:38:27 localhost fsck: /dev/hdb8: clean, 94544/261120 files,
| 422329/522104 blocks
| Apr 9 12:38:27 localhost rc.sysinit: Checking root filesystem succeeded
| Apr 9 12:38:27 localhost isapnp: Board 1 has Identity 9a 0b 43 20 32 9e 00 8c
| 0e: CTL009e Serial No 188948530 [checksum 9a]
| Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[0]{Audio }:
| Ports 0x220 0x330 0x388; IRQ5 DMA1 DMA5 --- Enabled OK
| Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[1]{Game }:
| Port 0x200; --- Enabled OK
| Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[2]{WaveTable }:
| Ports 0x620 0xA20 0xE20; --- Enabled OK
| Apr 9 12:38:27 localhost rc.sysinit: Setting up ISA PNP devices succeeded
| Apr 9 12:38:27 localhost rc.sysinit: Remounting root filesystem in read-write
| mode succeeded
| Apr 9 12:38:27 localhost rc.sysinit: Loading sound module succeeded
| Apr 9 12:38:34 localhost rc.sysinit: Loading midi module succeeded
| Apr 9 12:38:34 localhost rc.sysinit: Checking filesystems succeeded
| Apr 9 12:38:35 localhost rc.sysinit: Mounting local filesystems succeeded
| Apr 9 12:38:35 localhost rc.sysinit: Turning on user and group quotas for
| local filesystems succeeded
| Apr 9 12:38:35 localhost rc.sysinit: Enabling swap space succeeded
| Apr 9 12:38:36 localhost mandrake_everytime: Building Window Manager Sessions
| succeeded
| Apr 9 12:38:40 localhost init: Switching to runlevel: 5
Well, this is where you're switching to run-level 5. You didn't want
to do that. It's happening in "init".
I don't have such a service on my machine, do you have a file called
/etc/rc.d/init.d? Is this listed in your run-level 5 startup?
Does anybody else know if there's some other place where an "init"
would be started?
| Apr 9 12:38:50 localhost kudzu: succeeded
| Apr 9 12:38:51 localhost network: Bringing up interface lo succeeded
| Apr 9 12:38:53 localhost inet: inetd startup succeeded
| Apr 9 12:38:53 localhost lpd: lpd startup succeeded
| Apr 9 12:38:53 localhost loadkeys: Loading
| /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
| Apr 9 12:38:53 localhost keytable: Loading keymap: us succeeded
| Apr 9 12:38:53 localhost loadkeys: Loading
| /usr/lib/kbd/keymaps/compose/compose.latin.gz
| Apr 9 12:38:54 localhost keytable: Loading compose keys: compose.latin
| succeeded
| Apr 9 12:38:54 localhost keytable: succeeded
| Apr 9 12:38:54 localhost keytable: Loading system font: succeeded
| Apr 9 12:38:54 localhost PAM_pwdb[379]: (su) session opened for user xfs by
| (uid=0)
| Apr 9 12:38:54 localhost PAM_pwdb[379]: (su) session closed for user xfs
|
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said:
> A possible way to find out is to do a
>
> ps alwf > /root/ps-output
>
> when you go to run-level 5; eg, put this:
>
> :5:respawn:ps alwf > /root/ps-output
>
> in your /etc/inittab. Then we can at least see what's going on when
> this happens.
I added the second line to inittab:
#x:5:respawn:/etc/X11/prefdm -nodaemon
x:5:respawn:ps alwf > /root/ps-output
I put the x at the beginning after the system complained about nothing being
there.
I'm probably still not doing this right somehow, because I'm not getting
anything informative.
This one line is all it says:
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTYTIME COMMAND
At boot time, there's the message that the line is respawning too fast and will
be paused for 5 minutes.
> Also, your /var/log/messages might show something about switching to
> run-level 5. Perhaps it will give a clue to who is doing it?
I'll the lines from one boot below my sig.
--
Lane
Lane Lester / Madison County, Georgia USA
Using Linux to get where I want to go...
Apr 9 12:38:52 localhost syslogd 1.3-3: restart.
Apr 9 12:38:52 localhost syslog: syslogd startup succeeded
Apr 9 12:38:52 localhost kernel: klogd 1.3-3, log source = /proc/kmsg started.
Apr 9 12:38:52 localhost syslog: klogd startup succeeded
Apr 9 12:38:52 localhost kernel: Inspecting /boot/System.map-2.2.14-15mdk
Apr 9 12:38:52 localhost kernel: Loaded 6230 symbols from
/boot/System.map-2.2.14-15mdk.
Apr 9 12:38:52 localhost kernel: Symbols match kernel version 2.2.14.
Apr 9 12:38:52 localhost kernel: Loaded 151 symbols from 10 modules.
Apr 9 12:38:53 localhost crond: crond startup succeeded
Apr 9 12:38:27 localhost rc.sysinit: Mounting proc filesystem succeeded
Apr 9 12:38:27 localhost date: Sun Apr 9 12:38:26 EDT 2000
Apr 9 12:38:27 localhost rc.sysinit: Setting clock : Sun Apr 9 12:38:26 EDT
2000 succeeded
Apr 9 12:38:27 localhost rc.sysinit: Loading default keymap succeeded
Apr 9 12:38:27 localhost rc.sysinit: Activating swap partitions succeeded
Apr 9 12:38:27 localhost rc.sysinit: Setting hostname localhost succeeded
Apr 9 12:38:27 localhost fsck: /dev/hdb8: clean, 94544/261120 files,
422329/522104 blocks
Apr 9 12:38:27 localhost rc.sysinit: Checking root filesystem succeeded
Apr 9 12:38:27 localhost isapnp: Board 1 has Identity 9a 0b 43 20 32 9e 00 8c
0e: CTL009e Serial No 188948530 [checksum 9a]
Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[0]{Audio }:
Ports 0x220 0x330 0x388; IRQ5 DMA1 DMA5 --- Enabled OK
Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[1]{Game}:
Port 0x200; --- Enabled OK
Apr 9 12:38:27 localhost isapnp: CTL009e/188948530[2]{WaveTable }:
Ports 0x620 0xA20 0xE20; --- Enabled OK
Apr 9 12:38:27 localhost rc.sysinit: Setting up ISA PNP devices succeeded
Apr 9 12:38:27 localhost rc.sysinit: Remounting root filesystem in read-write
mode succeeded
Apr 9 12:38:27 localhost rc.sysinit: Loading sound module succeeded
Apr 9 12:38:34 localhost rc.sysinit: Loading midi module succeeded
Apr 9 12:38:34 localhost rc.sysinit: Checking filesystems succeeded
Apr 9 12:38:35 localhost rc.sysinit: Mounting local filesystems succeeded
Apr 9 12:38:35 localhost rc.sysinit: Turning on user and group quotas for
local filesystems succeeded
Apr 9 12:38:35 localhost rc.sysinit: Enabling swap space succeeded
Apr 9 12:38:36 localhost mandrake_everytime: Building Window Manager Sessions
succeeded
Apr 9 12:38:40 localhost init: Switching to runlevel: 5
Apr 9 12:38:50 localhost kudzu: succeeded
Apr 9 12:38:51 localhost network: Bringing up interface lo succeeded
Apr 9 12:38:53 localhost inet: inetd startup succeeded
Apr 9 12:38:53 localhost lpd: lpd startup succeeded
Apr 9 12:38:53 localhost loadkeys: Loading
/usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Apr 9 12:38:53 localhost keytable: Loading keymap: us succeeded
Apr 9 12:38:53 localhost loadkeys: Loading
/usr/lib/kbd/keymaps/compose/compose.latin.gz
Apr 9 12:38:54 localhost keytable: Loading compose keys: compose.latin
succeeded
Apr 9 12:38:54 localhost keytable: succeeded
Apr 9 12:38:54 localhost keytable: Loading system font: succeeded
Apr 9 12:38:54 localhost PAM_pwdb[379]: (su) session opened for user xfs by
(uid=0)
Apr 9 12:38:54 localhost PAM_pwdb[379]: (su) session closed for user xfs
Apr 9 12:38:54 localhost xfs: xfs startup succeeded
Apr 9 12:38:55 localhost linuxconf-setup: Linuxconf final setup
Apr 9 12:38:55 localhost rc: Starting linuxconf-setup succeeded
Apr 9 12:39:08 localhost PAM_pwdb[400]: (login) session opened for user root
by LOGIN(uid=0)
Re: [expert] Can't Break X Autostart
Ok, that verifies that removing that last line of /etc/inittab was a kludge fix, and we still haven't figured out the *real* question; namely, *why* are you at run-level 5 when you are asking for run-level 3? Somebody must be throwing you into run-level 5, but who? Why? What did you do to deserve this? A possible way to find out is to do a ps alwf > /root/ps-output when you go to run-level 5; eg, put this: :5:respawn:ps alwf > /root/ps-output in your /etc/inittab. Then we can at least see what's going on when this happens. Also, your /var/log/messages might show something about switching to run-level 5. Perhaps it will give a clue to who is doing it? On Sat, 08 Apr 2000, you wrote: | Brian T. Schellenberger said: | > Well, it's not X, really, that's broken, it's the run levels. | | > To verify that this is what we've really done, could you indulge us all | > and just issue the "runlevel" command (no arguments) and let us all | > know what it says? | | Hey, I'm willing to indulge you guys quite a bit for helping me out. | Here is what "runlevel" says when X is running: # 5 | And here's what it says with just the console after I exit X completely: #5 | | So I guess you're right about the run levels being broken. | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > Well, it's not X, really, that's broken, it's the run levels. > To verify that this is what we've really done, could you indulge us all > and just issue the "runlevel" command (no arguments) and let us all > know what it says? Hey, I'm willing to indulge you guys quite a bit for helping me out. Here is what "runlevel" says when X is running: # 5 And here's what it says with just the console after I exit X completely: #5 So I guess you're right about the run levels being broken. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
On Fri, 07 Apr 2000, you wrote: | Civileme said: | > Deleting the line changes the X behavior--basically breaking it. | | Evidently not irreparably, since startx starts X. Well, it's not X, really, that's broken, it's the run levels. Most likely you really *are* at run-level 5 (which should mean "X") but we've just fixed it up so that X doesn't auto-start at run-level 5. Strictly speaking, this is "wrong", though for a single-user system you might not care. To verify that this is what we've really done, could you indulge us all and just issue the "runlevel" command (no arguments) and let us all know what it says? | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
I don't know if someone has suggested this, if so, please skip it. Can you dump the relevant lines for the startup of your system from /var/log/messages? Usually these lines show (in order) what processes get started when you boot your machine. We may be able to find some useful info from the lines before and after the telinit 5 line. Make sure you reproduce the case to show the telinit 5 line. Chunnuan Lane Lester wrote: > Civileme said: > > Deleting the line changes the X behavior--basically breaking it. > > Evidently not irreparably, since startx starts X. > > > I finally reproduced the problem. > > > > High security > > > > user login > > > > su'ed in a Konsole > > > > Set /etc/inittab line to > > > > id:3:initdefault: > > > > logged out and rebooted--finding myself in X > > > > cat /var/run/runlevel.dir > > > > /etc/rc.d/rc5.d > > > > kudzu looks at /etc/inittab and boots to RL5 if it sees 5 > > > > linuxconf is called by a symlink called /sbin/askrunlevel and looks in > > /var/run/runlevel.dir > > > > Apparently su-ing in High security level enables the permission to edit > > a file but not to make linuxconf do its thing. > > > > So they are out of sync and runlevel 5 is a logical OR of their > > individual directives. > > > > It appears the remedy is to use linuxconf to set your runlevel--under > > Misc Servives on the opening screen. > > Wow, what a combination of factors to duplicate the problem. I did my original > install with medium security and automatic X start. I haven't changed the > security. During my attempts to stop X autostart, I have been logging on as > root... but of course, X was starting before the system knew that. > > I had either used linuxconf to switch to 3 or when I ran linuxconf it was > already set to 3... and X was still autostarting. > > My impression is that the auto X continued whether or not kudzu was executed. I > turned kudzu off because it slows the boot, and I know I don't have any new > hardware. I have it on right now, because I was recently trying to get my IDE > cd-writer to work (another long story). > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Civileme said: > Deleting the line changes the X behavior--basically breaking it. Evidently not irreparably, since startx starts X. > I finally reproduced the problem. > > High security > > user login > > su'ed in a Konsole > > Set /etc/inittab line to > > id:3:initdefault: > > logged out and rebooted--finding myself in X > > cat /var/run/runlevel.dir > > /etc/rc.d/rc5.d > > kudzu looks at /etc/inittab and boots to RL5 if it sees 5 > > linuxconf is called by a symlink called /sbin/askrunlevel and looks in > /var/run/runlevel.dir > > Apparently su-ing in High security level enables the permission to edit > a file but not to make linuxconf do its thing. > > So they are out of sync and runlevel 5 is a logical OR of their > individual directives. > > It appears the remedy is to use linuxconf to set your runlevel--under > Misc Servives on the opening screen. Wow, what a combination of factors to duplicate the problem. I did my original install with medium security and automatic X start. I haven't changed the security. During my attempts to stop X autostart, I have been logging on as root... but of course, X was starting before the system knew that. I had either used linuxconf to switch to 3 or when I ran linuxconf it was already set to 3... and X was still autostarting. My impression is that the auto X continued whether or not kudzu was executed. I turned kudzu off because it slows the boot, and I know I don't have any new hardware. I have it on right now, because I was recently trying to get my IDE cd-writer to work (another long story). -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
RE: [expert] Can't Break X Autostart
That means something else is broken. By commenting out that line, you effectively broke your system. Yes, it's now doing what you want, but in the wrong manner. There's probably other things going on that you don't need, or things that you want that aren't running. Russ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester Sent: Thursday, April 06, 2000 5:58 PM To: [EMAIL PROTECTED] Subject: RE: [expert] Can't Break X Autostart Russ Johnson said: > Read up on how init reads that file. The answer will become clear. > > I suspect you could put that line back (and make no other changes to your > system) and it wouldn't run X on startup... As long as it's truly starting > in runlevel 3. This is controlled by the first line in inittab. Perhaps you haven't been following the whole thread. I've had: id:3:initdefault: for a long time without effect. It was not until I commented out: x:5:respawn:/etc/X11/prefdm -nodaemon that I finally was able boot without X automatically starting. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Yes, the last line in /etc/inittab could stay in and not cause a problem. What he had was the standard last line that is altered only if you want to have kde startup for a graphical login. Its presence is not the problem, definitely. I have had that last line in about 6 different linux installs and never seen it cause a problem Tom Russ Johnson wrote: > > Read up on how init reads that file. The answer will become clear. > > I suspect you could put that line back (and make no other changes to your > system) and it wouldn't run X on startup... As long as it's truly starting > in runlevel 3. This is controlled by the first line in inittab. > > If it does, you have much bigger problems than just X starting at bootup. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Brian T. > Schellenberger > Sent: Thursday, April 06, 2000 1:09 PM > To: [EMAIL PROTECTED] > Subject: RE: [expert] Can't Break X Autostart > > If that's the case, then why does deleting that line solve the problem? > > On Thu, 06 Apr 2000, you wrote: > | For what it's worth, you'll need the line in inittab for X to start in > | runlevel 5. If you start in runlevel 3, that line is never run, so it's > not > | part of the problem. > | > | Russ > | > | -Original Message- > | From: [EMAIL PROTECTED] > | [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester > | Sent: Thursday, April 06, 2000 4:03 AM > | To: [EMAIL PROTECTED] > | Subject: Re: [expert] Can't Break X Autostart > | > | > | Brian T. Schellenberger said: > | > I believe that the reason you get a totally blank screen when you just > | > do a startx is because you have an empty .xinitrc. > | > > | > Since you have a .xinitrc the system one dosn't run 'cause it thinks > | > you want to replace it with your own, but yours doesn't do anything. > | > > | > Thus a plain gray screen. > | > > | > Try deleting it and then do a startx. > | > | Many, many thanks to you and Civileme and others for sticking with this > | investigation. It looks like the above finally did the trick. Deleting > | (well, actually renaming) the .xinitrc and taking out > | "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab > | allowed the boot to stop at the console screen and for "startx" to > | operate without crashing back to the console. > | > | Interestingly, now that I've done a startx, the window manager that is > | running is KDE, not my preferred and previous IceWM. I think I can find > | where that is going on and make the change. > | -- > | Lane > | > | Lane Lester / Madison County, Georgia USA > | Using Linux to get where I want to go... > -- > "Brian, the man from babbleon-on" [EMAIL PROTECTED] > Brian T. Schellenberger http://www.babbleon.org > Support http://www.eff.org. Support decss defendents. > Support http://www.programming-freedom.org. Boycott amazon.com.
RE: [expert] Can't Break X Autostart
Well, there's theory, and then there's practice. In practice, it solved his problem. But I do see what you're saying now . . . what he's done, really, presumably, is that he's still in runlevel 5 but now runlevel 5 doesn't really do what it ought. So this solves his problem but it's not the right solution. Well, I'm a pretty emperical guy myself, so good enough for me, but there's still a mystery to be solved. Have at it! On Thu, 06 Apr 2000, you wrote: | Read up on how init reads that file. The answer will become clear. | | I suspect you could put that line back (and make no other changes to your | system) and it wouldn't run X on startup... As long as it's truly starting | in runlevel 3. This is controlled by the first line in inittab. | | If it does, you have much bigger problems than just X starting at bootup. | | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Brian T. | Schellenberger | Sent: Thursday, April 06, 2000 1:09 PM | To: [EMAIL PROTECTED] | Subject: RE: [expert] Can't Break X Autostart | | | | If that's the case, then why does deleting that line solve the problem? | | On Thu, 06 Apr 2000, you wrote: | | For what it's worth, you'll need the line in inittab for X to start in | | runlevel 5. If you start in runlevel 3, that line is never run, so it's | not | | part of the problem. | | | | Russ | | | | -Original Message- | | From: [EMAIL PROTECTED] | | [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester | | Sent: Thursday, April 06, 2000 4:03 AM | | To: [EMAIL PROTECTED] | | Subject: Re: [expert] Can't Break X Autostart | | | | | | Brian T. Schellenberger said: | | > I believe that the reason you get a totally blank screen when you just | | > do a startx is because you have an empty .xinitrc. | | > | | > Since you have a .xinitrc the system one dosn't run 'cause it thinks | | > you want to replace it with your own, but yours doesn't do anything. | | > | | > Thus a plain gray screen. | | > | | > Try deleting it and then do a startx. | | | | Many, many thanks to you and Civileme and others for sticking with this | | investigation. It looks like the above finally did the trick. Deleting | | (well, actually renaming) the .xinitrc and taking out | | "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab | | allowed the boot to stop at the console screen and for "startx" to | | operate without crashing back to the console. | | | | Interestingly, now that I've done a startx, the window manager that is | | running is KDE, not my preferred and previous IceWM. I think I can find | | where that is going on and make the change. | | -- | | Lane | | | | Lane Lester / Madison County, Georgia USA | | Using Linux to get where I want to go... | -- | "Brian, the man from babbleon-on" [EMAIL PROTECTED] | Brian T. Schellenberger http://www.babbleon.org | Support http://www.eff.org. Support decss defendents. | Support http://www.programming-freedom.org. Boycott amazon.com. -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
RE: [expert] Can't Break X Autostart
Russ Johnson said: > Read up on how init reads that file. The answer will become clear. > > I suspect you could put that line back (and make no other changes to your > system) and it wouldn't run X on startup... As long as it's truly starting > in runlevel 3. This is controlled by the first line in inittab. Perhaps you haven't been following the whole thread. I've had: id:3:initdefault: for a long time without effect. It was not until I commented out: x:5:respawn:/etc/X11/prefdm -nodaemon that I finally was able boot without X automatically starting. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger wrote: > > If that's the case, then why does deleting that line solve the problem? > > On Thu, 06 Apr 2000, you wrote: > | For what it's worth, you'll need the line in inittab for X to start in > | runlevel 5. If you start in runlevel 3, that line is never run, so it's not > | part of the problem. > | > | Russ > | > | -Original Message- > | From: [EMAIL PROTECTED] > | [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester > | Sent: Thursday, April 06, 2000 4:03 AM > | To: [EMAIL PROTECTED] > | Subject: Re: [expert] Can't Break X Autostart > | > | > | Brian T. Schellenberger said: > | > I believe that the reason you get a totally blank screen when you just > | > do a startx is because you have an empty .xinitrc. > | > > | > Since you have a .xinitrc the system one dosn't run 'cause it thinks > | > you want to replace it with your own, but yours doesn't do anything. > | > > | > Thus a plain gray screen. > | > > | > Try deleting it and then do a startx. > | > | Many, many thanks to you and Civileme and others for sticking with this > | investigation. It looks like the above finally did the trick. Deleting > | (well, actually renaming) the .xinitrc and taking out > | "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab > | allowed the boot to stop at the console screen and for "startx" to > | operate without crashing back to the console. > | > | Interestingly, now that I've done a startx, the window manager that is > | running is KDE, not my preferred and previous IceWM. I think I can find > | where that is going on and make the change. > | -- > | Lane > | > | Lane Lester / Madison County, Georgia USA > | Using Linux to get where I want to go... > -- > "Brian, the man from babbleon-on" [EMAIL PROTECTED] > Brian T. Schellenberger http://www.babbleon.org > Support http://www.eff.org. Support decss defendents. > Support http://www.programming-freedom.org. Boycott amazon.com. > > > Deleting the line changes the X behavior--basically breaking it. I finally reproduced the problem. High security user login su'ed in a Konsole Set /etc/inittab line to id:3:initdefault: logged out and rebooted--finding myself in X cat /var/run/runlevel.dir /etc/rc.d/rc5.d kudzu looks at /etc/inittab and boots to RL5 if it sees 5 linuxconf is called by a symlink called /sbin/askrunlevel and looks in /var/run/runlevel.dir Apparently su-ing in High security level enables the permission to edit a file but not to make linuxconf do its thing. So they are out of sync and runlevel 5 is a logical OR of their individual directives. It appears the remedy is to use linuxconf to set your runlevel--under Misc Servives on the opening screen. Civileme
Re: [expert] Can't Break X Autostart
"Brian T. Schellenberger" wrote: > If that's the case, then why does deleting that line solve the problem? Removing .xinitrc was what solved the problem, AFAIK. -Stephen-
RE: [expert] Can't Break X Autostart
Read up on how init reads that file. The answer will become clear. I suspect you could put that line back (and make no other changes to your system) and it wouldn't run X on startup... As long as it's truly starting in runlevel 3. This is controlled by the first line in inittab. If it does, you have much bigger problems than just X starting at bootup. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brian T. Schellenberger Sent: Thursday, April 06, 2000 1:09 PM To: [EMAIL PROTECTED] Subject: RE: [expert] Can't Break X Autostart If that's the case, then why does deleting that line solve the problem? On Thu, 06 Apr 2000, you wrote: | For what it's worth, you'll need the line in inittab for X to start in | runlevel 5. If you start in runlevel 3, that line is never run, so it's not | part of the problem. | | Russ | | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester | Sent: Thursday, April 06, 2000 4:03 AM | To: [EMAIL PROTECTED] | Subject: Re: [expert] Can't Break X Autostart | | | Brian T. Schellenberger said: | > I believe that the reason you get a totally blank screen when you just | > do a startx is because you have an empty .xinitrc. | > | > Since you have a .xinitrc the system one dosn't run 'cause it thinks | > you want to replace it with your own, but yours doesn't do anything. | > | > Thus a plain gray screen. | > | > Try deleting it and then do a startx. | | Many, many thanks to you and Civileme and others for sticking with this | investigation. It looks like the above finally did the trick. Deleting | (well, actually renaming) the .xinitrc and taking out | "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab | allowed the boot to stop at the console screen and for "startx" to | operate without crashing back to the console. | | Interestingly, now that I've done a startx, the window manager that is | running is KDE, not my preferred and previous IceWM. I think I can find | where that is going on and make the change. | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
RE: [expert] Can't Break X Autostart
If that's the case, then why does deleting that line solve the problem? On Thu, 06 Apr 2000, you wrote: | For what it's worth, you'll need the line in inittab for X to start in | runlevel 5. If you start in runlevel 3, that line is never run, so it's not | part of the problem. | | Russ | | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester | Sent: Thursday, April 06, 2000 4:03 AM | To: [EMAIL PROTECTED] | Subject: Re: [expert] Can't Break X Autostart | | | Brian T. Schellenberger said: | > I believe that the reason you get a totally blank screen when you just | > do a startx is because you have an empty .xinitrc. | > | > Since you have a .xinitrc the system one dosn't run 'cause it thinks | > you want to replace it with your own, but yours doesn't do anything. | > | > Thus a plain gray screen. | > | > Try deleting it and then do a startx. | | Many, many thanks to you and Civileme and others for sticking with this | investigation. It looks like the above finally did the trick. Deleting | (well, actually renaming) the .xinitrc and taking out | "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab | allowed the boot to stop at the console screen and for "startx" to | operate without crashing back to the console. | | Interestingly, now that I've done a startx, the window manager that is | running is KDE, not my preferred and previous IceWM. I think I can find | where that is going on and make the change. | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
On Wed, 05 Apr 2000, you wrote: > > Well, I'm running 7.0.2, so I don't know if there are any updates. I guess I > could install the initscripts and wipe out any customizing I've done, if you > think it's a good idea. Unless the name of the file is initscripts.rpm, I might > need some help identifying it. > Hmm...I coulda sworn there was another person with similar problems running 6.1. :-) In any event, you will find it quite easily. It'll be "initsricpts-some_version-number.rpm" Should be REALLY easy to find. And, yes, it wouldn't hurt to backup your initscripts, etc. John
RE: [expert] Can't Break X Autostart
For what it's worth, you'll need the line in inittab for X to start in runlevel 5. If you start in runlevel 3, that line is never run, so it's not part of the problem. Russ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester Sent: Thursday, April 06, 2000 4:03 AM To: [EMAIL PROTECTED] Subject: Re: [expert] Can't Break X Autostart Brian T. Schellenberger said: > I believe that the reason you get a totally blank screen when you just > do a startx is because you have an empty .xinitrc. > > Since you have a .xinitrc the system one dosn't run 'cause it thinks > you want to replace it with your own, but yours doesn't do anything. > > Thus a plain gray screen. > > Try deleting it and then do a startx. Many, many thanks to you and Civileme and others for sticking with this investigation. It looks like the above finally did the trick. Deleting (well, actually renaming) the .xinitrc and taking out "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab allowed the boot to stop at the console screen and for "startx" to operate without crashing back to the console. Interestingly, now that I've done a startx, the window manager that is running is KDE, not my preferred and previous IceWM. I think I can find where that is going on and make the change. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > I believe that the reason you get a totally blank screen when you just > do a startx is because you have an empty .xinitrc. > > Since you have a .xinitrc the system one dosn't run 'cause it thinks > you want to replace it with your own, but yours doesn't do anything. > > Thus a plain gray screen. > > Try deleting it and then do a startx. Many, many thanks to you and Civileme and others for sticking with this investigation. It looks like the above finally did the trick. Deleting (well, actually renaming) the .xinitrc and taking out "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab allowed the boot to stop at the console screen and for "startx" to operate without crashing back to the console. Interestingly, now that I've done a startx, the window manager that is running is KDE, not my preferred and previous IceWM. I think I can find where that is going on and make the change. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > > /sbin/askrunlevel That is a SYMLINK to /bin/linuxconf * WHat is the output of cat /var/run/runlevel.dir Civileme
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > > Civileme said: > > Well open /etc/rc.d/init.d/kudzu with kedit and search for > > telinit > > > > the line should look like > > > > grep -q "^id:5:initdefault:" /etc/inittab && telinit 5 > > If it doesn't, our problem may end there > > Yep, that's what it says. > > > Now the ~/.compupic/def.phd shows up in both directories so it is > > something you are using, but what? I do not recall this one from > > my experience. Could it be some resource file that runs? > > It's a graphics viewer that I use infrequently. It looks like a binary file > that starts with "Photodex File Mirror 1.00_" > > > dynamically into an environment variable. See if you can dump > > your environment with > > > > printenv > > If a variable is set to telinit or "telinit 5", then we need to > > rgrep for it to find out where the setting is coming from. > > It's posted below my sig and looks innocent. > > > Also, look at /etc/fstab and see if there are mounts after /proc > > in the table order. If so, do the rgrep on each of those mounts > > (/mnt/* excluded of course). > > There is only: > none /proc proc defaults 0 0 > none /dev/pts devpts mode=0620 0 0 > > and > rgrep -i -l -r telinit /dev/pts > didn't turn up anything. > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... > > PWD=/root > COLORFGBG=15;default;0 > WINDOWID=41943042 > HOSTNAME=localhost > HISTFILESIZE=1000 > LESSKEY=/etc/.less > LANGUAGE=en > PS1=[\u@\h \W]\$ > ENV=/root/.bashrc > KDEDIR=/usr > LESS=-MM > USER=root > MACHTYPE=i586-mandrake-linux-gnu > LC_ALL=en > MAIL=/var/spool/mail/root > INPUTRC=/etc/inputrc > LINGUAS=en_US:en > LANG=en > COLORTERM=rxvt-xpm > DISPLAY=unix:0.0 > LOGNAME=root > SHLVL=1 > SHELL=/bin/bash > USERNAME=root > HOSTTYPE=i586 > OSTYPE=linux-gnu > HISTSIZE=1000 > HOME=/root > TERM=rxvt > SECURE_LEVEL=3 > _=/usr/bin/printenv > LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33; > 01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:* > .btm=01;32:*.bat=01;32:*.tar=01;31:*.tgz=01;31:*.tbz2=01;31:*.arc=01;31:*.arj=0 > 1;31:*.taz=01;31:*.lzh=01;31:*.lha=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=0 > 1;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.jpg=01;35:*.jpeg=01;35:*.g > if=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:*.tiff=01; > 35: > PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/root/myscript > s NOTHING there Let's take a wild stab do you have a file called /etc/inittab~? If so, move or delete it. Then restore that line at the bottom of inittab. There is just a slight possibility that the backup inittab is being read; I observed another changed initscript /etc/rc.d/init.d/S00halt was also not taking the right effect because the backup was being used by the system. SO try that. There is little else left to try--your telinit has to be coming from kudzu or from one of the directories that might not have been checked rgrep -i -l -r telinit /tmp rgrep -i -l -r telinit /usr rgrep -i -l -r telinit /var IF nothing else comes up, then this is not possible. Computers behave in predictable programmable fashion. We just need to know enough of the system to bring the apparent magic into reality Civileme -- Anyone remember TurboDOS? How about Formula/Formula II or Final Word?
Re: [expert] Can't Break X Autostart
Let's not do that yet! I believe that the reason you get a totally blank screen when you just do a startx is because you have an empty .xinitrc. Since you have a .xinitrc the system one dosn't run 'cause it thinks you want to replace it with your own, but yours doesn't do anything. Thus a plain gray screen. Try deleting it and then do a startx. On Wed, 05 Apr 2000, you wrote: | John Aldrich said: | > So...to the original querant: Go download the initscripts | > update from the Mandrake 6.1 updates and do an "rpm -Uvh" | > on it and see if that helps! | > John | | Well, I'm running 7.0.2, so I don't know if there are any updates. I guess I | could install the initscripts and wipe out any customizing I've done, if you | think it's a good idea. Unless the name of the file is initscripts.rpm, I might | need some help identifying it. | | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
Stephen F. Bosch said:
> Can you show me rc.local and rc.sysinit?
OK, here's rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
if [ -f /etc/mandrake-release ]; then
R=$(cat /etc/mandrake-release)
arch=$(uname -m)
a="a"
case "_$arch" in
_a*) a="an";;
_i*) a="an";;
esac
NUMPROC=`egrep -c "^cpu[0-9]+" /proc/stat`
if [ "$NUMPROC" -gt "1" ]; then
SMP="$NUMPROC-processor "
[ "$NUMPROC" = "2" ] && \
SMP="Bi-processor "
if [ "$NUMPROC" = "8" -o "$NUMPROC" = "11" ]; then
a="an"
else
a="a"
fi
fi
# This will overwrite /etc/issue at every boot. So, make any changes you
# want to make to /etc/issue here or you will lose them when you reboot.
if [ -x /usr/bin/linux_logo ];then
/usr/bin/linux_logo -c -n -f > /etc/issue
echo "" >> /etc/issue
else
> /etc/issue
fi
echo "$R" >> /etc/issue
echo "Kernel $(uname -r) on $a $SMP$(uname -m) / \l" >> /etc/issue
echo "Welcome to %h" > /etc/issue.net
echo "$R" >> /etc/issue.net
echo "Kernel $(uname -r) on $a $SMP$(uname -m)" >> /etc/issue.net
fi
modprobe ide-scsi
/usr/local/sbin/ledd 1>/dev/null 2>&1 &
(the last line is for the "ledcontrol" daemon that lets me use the Scroll Lock
LED as an incoming fax notifier)
Since rc.sysinit is so large, I've pasted it below my sig. The only line that
looked interesting to my uninformed gaze was the last one:
/sbin/askrunlevel
--
Lane
Lane Lester / Madison County, Georgia USA
Using Linux to get where I want to go...
#!/bin/sh
#
# /etc/rc.d/rc.sysinit - run once at boot time
#
# Taken in part from Miquel van Smoorenburg's bcheckrc.
#
# Rerun ourselves through initlog
if [ -z "$IN_INITLOG" ]; then
[ -f /sbin/initlog ] && exec /sbin/initlog $INITLOG_ARGS -r
/etc/rc.d/rc.sysinit
fi
# Set the path
PATH=/bin:/sbin:/usr/bin:/usr/sbin
export PATH
# Read in config data.
if [ -f /etc/sysconfig/network ]; then
. /etc/sysconfig/network
else
NETWORKING=no
HOSTNAME=localhost
fi
# Source functions
. /etc/rc.d/init.d/functions
# Print a banner. ;)
echo -en "\t\t\tWelcome to Linux "
[ "$BOOTUP" != "serial" ] && echo -en "\\033[1;36m"
echo -e "Mandrake"
[ "$BOOTUP" != "serial" ] && echo -en "\\033[0;39m"
if [ "$PROMPT" != "no" ]; then
echo -en "\t\tPress 'I' to enter interactive startup."
echo
sleep 3
fi
# Fix console loglevel
/bin/dmesg -n $LOGLEVEL
# Mount /proc (done here so volume labels can work with fsck)
action "Mounting proc filesystem" mount -n -t proc /proc /proc
# Turn off sysrq
if [ -f /proc/sys/kernel/sysrq -a "$MAGIC_SYSRQ" = "no" ]; then
echo "0" > /proc/sys/kernel/sysrq
action "Turning off Magic SysRq key" /bin/true
fi
# Turn off Stop-A
if [ -f /proc/sys/kernel/stop-a -a "$STOP_A" = "no" ]; then
echo "0" > /proc/sys/kernel/stop-a
action "Turning off Stop-A/Break-A" /bin/true
fi
# Set the system clock.
ARC=0
SRM=0
UTC=0
if [ -f /etc/sysconfig/clock ]; then
. /etc/sysconfig/clock
# convert old style clock config to new values
if [ "${CLOCKMODE}" = "GMT" ]; then
UTC=true
elif [ "${CLOCKMODE}" = "ARC" ]; then
ARC=true
fi
fi
if grep "system serial" /proc/cpuinfo | grep -q MILO ; then
ARC=true
fi
CLOCKDEF=""
CLOCKFLAGS="--hctosys"
case "$UTC" in
yes|true)
CLOCKFLAGS="$CLOCKFLAGS -u";
CLOCKDEF="$CLOCKDEF (utc)";
;;
esac
case "$ARC" in
yes|true)
CLOCKFLAGS="$CLOCKFLAGS -A";
CLOCKDEF="$CLOCKDEF (arc)";
;;
esac
case "$SRM" in
yes|true)
CLOCKFLAGS="$CLOCKFLAGS -S";
CLOCKDEF="$CLOCKDEF (srm)";
;;
esac
/sbin/hwclock $CLOCKFLAGS
action "Setting clock $CLOCKDEF: `date`" date
# Load keymap
KEYMAP=
if [ -f /etc/sysconfig/console/default.kmap ]; then
KEYMAP=/etc/sysconfig/console/default.kmap
# Since this takes in/output from stdin/out, we can't use initlog
loadkeys $KEYMAP < /dev/tty0 > /dev/tty0 2>/dev/null && \
success "Loading default keymap" || failure "Loading default keymap"
echo
else
if [ -x etc/rc.d/init.d/keytable -a -d /usr/lib/kbd/keymaps ]; then
/etc/rc.d/init.d/keytable start
else
DELAYED_KEYMAP=y
fi
fi
# Load system font
if [ -x /sbin/setsysfont ]; then
[ -f /etc/sysconfig/i18n ] && . /etc/sysconfig/i18n
if [ -f /etc/sysconfig/console/$SYSFONT.psf.gz -o -f
/usr/lib/kbd/consolefonts/$SYSFONT.psf.gz ]; then
action "Setting default font" /sbin/setsysfont
fi
fi
# Start up swapping.
action "Activating swap partitions" swapon -a
# Set the hostname.
action "Setting hostname ${HOSTNAME}" hostname ${HOSTNAME}
# Set the NIS domain name
if [ -n "$NISDOMAIN" ]; then
action "Setting NIS domain name $NISDOMAIN" domainname $NISDOMAIN
else
domainname ""
fi
if [ -f /fsckoptions ]; t
Re: [expert] Can't Break X Autostart
Stephen F. Bosch said: > John Aldrich wrote: > > > Hmm...based on everything you've shown so far, it appears > > that SOMEWHERE in one of your startup scripts, you're > > calling "startx" or something Dunno how do you feel > > about a reinstall? > > John > > Whoa -- that's a Micro$oft solution. > > Nope -- we need to find out what the problem is, or he'll go and > reinstall and then something ELSE won't work (and his original problem > may still exist). Whew! -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
John Aldrich said: > So...to the original querant: Go download the initscripts > update from the Mandrake 6.1 updates and do an "rpm -Uvh" > on it and see if that helps! > John Well, I'm running 7.0.2, so I don't know if there are any updates. I guess I could install the initscripts and wipe out any customizing I've done, if you think it's a good idea. Unless the name of the file is initscripts.rpm, I might need some help identifying it. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Brian T. Schellenberger said: > Crashes or locks up? > > the gray screen goes away? Yes, X exits completely back to the console screen, which then works fine. I can startx again with the same effect: go to the gray and then exit. > Do you have a .xinitrc? What does it contain, if so? Well, I have one, but it seems to be "empty." #!/bin/sh #xscreensaver & #exec icewm The above was part of an earlier experiment with something else. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Civileme said: > Well open /etc/rc.d/init.d/kudzu with kedit and search for > telinit > > the line should look like > > grep -q "^id:5:initdefault:" /etc/inittab && telinit 5 > If it doesn't, our problem may end there Yep, that's what it says. > Now the ~/.compupic/def.phd shows up in both directories so it is > something you are using, but what? I do not recall this one from > my experience. Could it be some resource file that runs? It's a graphics viewer that I use infrequently. It looks like a binary file that starts with "Photodex File Mirror 1.00_" > dynamically into an environment variable. See if you can dump > your environment with > > printenv > If a variable is set to telinit or "telinit 5", then we need to > rgrep for it to find out where the setting is coming from. It's posted below my sig and looks innocent. > Also, look at /etc/fstab and see if there are mounts after /proc > in the table order. If so, do the rgrep on each of those mounts > (/mnt/* excluded of course). There is only: none /proc proc defaults 0 0 none /dev/pts devpts mode=0620 0 0 and rgrep -i -l -r telinit /dev/pts didn't turn up anything. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go... PWD=/root COLORFGBG=15;default;0 WINDOWID=41943042 HOSTNAME=localhost HISTFILESIZE=1000 LESSKEY=/etc/.less LANGUAGE=en PS1=[\u@\h \W]\$ ENV=/root/.bashrc KDEDIR=/usr LESS=-MM USER=root MACHTYPE=i586-mandrake-linux-gnu LC_ALL=en MAIL=/var/spool/mail/root INPUTRC=/etc/inputrc LINGUAS=en_US:en LANG=en COLORTERM=rxvt-xpm DISPLAY=unix:0.0 LOGNAME=root SHLVL=1 SHELL=/bin/bash USERNAME=root HOSTTYPE=i586 OSTYPE=linux-gnu HISTSIZE=1000 HOME=/root TERM=rxvt SECURE_LEVEL=3 _=/usr/bin/printenv LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33; 01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:* .btm=01;32:*.bat=01;32:*.tar=01;31:*.tgz=01;31:*.tbz2=01;31:*.arc=01;31:*.arj=0 1;31:*.taz=01;31:*.lzh=01;31:*.lha=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=0 1;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.jpg=01;35:*.jpeg=01;35:*.g if=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:*.tiff=01; 35: PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/root/myscript s
Re: [expert] Can't Break X Autostart
On Wed, 05 Apr 2000, you wrote: > John Aldrich wrote: > > > Hmm...based on everything you've shown so far, it appears > > that SOMEWHERE in one of your startup scripts, you're > > calling "startx" or something Dunno how do you feel > > about a reinstall? > > John > > Whoa -- that's a Micro$oft solution. > > Nope -- we need to find out what the problem is, or he'll go and > reinstall and then something ELSE won't work (and his original problem > may still exist). > Well...maybe just reinstall initscripts??? IIRC, that WAS something that needed doing in Mandrake 6.1 Haven't upgraded to 6.1 yet myself (mostly happy with 6.0 ) but I have been reading this list for some time now... So...to the original querant: Go download the initscripts update from the Mandrake 6.1 updates and do an "rpm -Uvh" on it and see if that helps! John
Re: [expert] Can't Break X Autostart
John Aldrich wrote: > Hmm...based on everything you've shown so far, it appears > that SOMEWHERE in one of your startup scripts, you're > calling "startx" or something Dunno how do you feel > about a reinstall? > John Whoa -- that's a Micro$oft solution. Nope -- we need to find out what the problem is, or he'll go and reinstall and then something ELSE won't work (and his original problem may still exist). -Stephen-
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > Stephen F. Bosch said: > >> OK, I tried "mx init 3" with the same result. At one point in the boot it > says: > >> INIT: Switching to runlevel 5 in 2 seconds > >> sbin/telinit 5 > > >I swear... it looks like you have weird stuff in your inittab. > >Why don't you post it? Can you show me rc.local and rc.sysinit? "This is DAMN peculiar." -Captain Kirk, Star Trek II -Stephen-
Re: [expert] Can't Break X Autostart
Hmm...based on everything you've shown so far, it appears that SOMEWHERE in one of your startup scripts, you're calling "startx" or something Dunno how do you feel about a reinstall? John
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > > Civileme said: > > POST the output of this and, if you show any files besides > /etc/rc.d/init.d/kudzu > > in the output, please attach them . If kudzu is the only file, then attach > it. > > If you have something in /etc/pcmcia/serial, make sure you send that. > > You will need to run the command in superuser mode > > # rgrep -i -l -r telinit /etc > > [root@localhost /root]# rgrep -i -l -r telinit /etc > /etc/rc.d/init.d/kudzu > > > There is a chance that it is in another directory besides /etc, but > > # rgrep -i -l -r telinit / > > [root@localhost /root]# rgrep -i -l -r telinit / > /etc/rc.d/init.d/kudzu > /home/llester/.compupic/def.phd > /var/lib/rpm/packages.rpm > /var/lib/rpm/fileindex.rpm > /var/lib/slocate/slocate.db > /var/log/netconf.log > /var/log/netconf.log.1 > /root/.cscmail/7/9/597.msg > /root/.cscmail/3/0/603.msg > /root/.compupic/def.phd > /root/.cscmail-save/.cscmail/7/9/597.msg > /proc/kcore > > > We are NOT lookiing for files of the nature > > /home///*, > >nor /var/lib/*.rpm, nor /var/lib/*.db if you elect to > > do this more thorough search. > > That looks like all I got. > > > Also post the output of > > $ grep "^id:" /etc/inittab > > [root@localhost /root]# grep "^id:" /etc/inittab > id:3:initdefault: > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... Hmmm, Well open /etc/rc.d/init.d/kudzu with kedit and search for telinit the line should look like grep -q "^id:5:initdefault:" /etc/inittab && telinit 5 If it doesn't, our problem may end there Now the ~/.compupic/def.phd shows up in both directories so it is something you are using, but what? I do not recall this one from my experience. Could it be some resource file that runs? Something is calling telinit during the boot or after login? Which is it? And considering how definitely linux frowns on self-modifying code(at the machine level), the text for the telinit call almost has to be set statically into a file or dynamically into an environment variable. See if you can dump your environment with printenv If a variable is set to telinit or "telinit 5", then we need to rgrep for it to find out where the setting is coming from. Civileme Also, look at /etc/fstab and see if there are mounts after /proc in the table order. If so, do the rgrep on each of those mounts (/mnt/* excluded of course). Civileme
Re: [expert] Can't Break X Autostart
Crashes or locks up? the gray screen goes away? In any case, getting rid of that last line was the right thing to do (if you don't want to boot into X); now it's just a matter of figuring out why startx is so short. Do you have a .xinitrc? What does it contain, if so? On Tue, 04 Apr 2000, you wrote: | Stephen F. Bosch said: | >> OK, I tried "mx init 3" with the same result. At one point in the boot it | says: | >> INIT: Switching to runlevel 5 in 2 seconds | >> sbin/telinit 5 | | >I swear... it looks like you have weird stuff in your inittab. | >Why don't you post it? | | OK, it's below my sig. I might mention that, as an experiment, I commented out | the last line. Mandrake then boots just to the console (that's good), but when | I run startx, X gets as far as the gray screen with the X cursor, and then it | crashes. None of the text on the console screen looks like errors, and the last | line is like "Waiting for X server to shut down." | | I might add that, even with the last line commented out, during the boot | process I still see the line, "INIT: Switching to runlevel 5." | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... | | # inittab This file describes how the INIT process should set up | # the system in a certain run-level. | | # Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]> | # Modified for RHS Linux by Marc Ewing and Donnie Barnes | | | # Default runlevel. The runlevels used by RHS are: | # 0 - halt (Do NOT set initdefault to this) | # 1 - Single user mode | # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) | # 3 - Full multiuser mode | # 4 - unused | # 5 - X11 | # 6 - reboot (Do NOT set initdefault to this) | | id:3:initdefault: | | # System initialization. | si::sysinit:/etc/rc.d/rc.sysinit | | l0:0:wait:/etc/rc.d/rc 0 | l1:1:wait:/etc/rc.d/rc 1 | l2:2:wait:/etc/rc.d/rc 2 | l3:3:wait:/etc/rc.d/rc 3 | l4:4:wait:/etc/rc.d/rc 4 | l5:5:wait:/etc/rc.d/rc 5 | l6:6:wait:/etc/rc.d/rc 6 | | # Things to run in every runlevel. | # commented out by Lane | # ud::once:/sbin/update | | # Trap CTRL-ALT-DELETE | ca::ctrlaltdel:/sbin/shutdown -t3 -r now | | # When our UPS tells us power has failed, assume we have a few minutes | # of power left. Schedule a shutdown for 2 minutes from now. | # This does, of course, assume you have powerd installed and your | # UPS connected and working correctly. | pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" | | # If power was restored before the shutdown kicked in, cancel it. | pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" | | | # Run gettys in standard runlevels | 1:2345:respawn:/sbin/mingetty tty1 | 2:2345:respawn:/sbin/mingetty tty2 | 3:2345:respawn:/sbin/mingetty tty3 | 4:2345:respawn:/sbin/mingetty tty4 | 5:2345:respawn:/sbin/mingetty tty5 | # 6:2345:respawn:/sbin/mingetty tty6 | 6:2345:respawn:/sbin/mgetty ttyS1 | | # Run xdm in runlevel 5 | # xdm is now a separate service | x:5:respawn:/etc/X11/prefdm -nodaemon -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
Civileme said: > POST the output of this and, if you show any files besides /etc/rc.d/init.d/kudzu > in the output, please attach them . If kudzu is the only file, then attach it. > If you have something in /etc/pcmcia/serial, make sure you send that. > You will need to run the command in superuser mode > # rgrep -i -l -r telinit /etc [root@localhost /root]# rgrep -i -l -r telinit /etc /etc/rc.d/init.d/kudzu > There is a chance that it is in another directory besides /etc, but > # rgrep -i -l -r telinit / [root@localhost /root]# rgrep -i -l -r telinit / /etc/rc.d/init.d/kudzu /home/llester/.compupic/def.phd /var/lib/rpm/packages.rpm /var/lib/rpm/fileindex.rpm /var/lib/slocate/slocate.db /var/log/netconf.log /var/log/netconf.log.1 /root/.cscmail/7/9/597.msg /root/.cscmail/3/0/603.msg /root/.compupic/def.phd /root/.cscmail-save/.cscmail/7/9/597.msg /proc/kcore > We are NOT lookiing for files of the nature > /home///*, >nor /var/lib/*.rpm, nor /var/lib/*.db if you elect to > do this more thorough search. That looks like all I got. > Also post the output of > $ grep "^id:" /etc/inittab [root@localhost /root]# grep "^id:" /etc/inittab id:3:initdefault: -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Stephen F. Bosch said: >> OK, I tried "mx init 3" with the same result. At one point in the boot it says: >> INIT: Switching to runlevel 5 in 2 seconds >> sbin/telinit 5 >I swear... it looks like you have weird stuff in your inittab. >Why don't you post it? OK, it's below my sig. I might mention that, as an experiment, I commented out the last line. Mandrake then boots just to the console (that's good), but when I run startx, X gets as far as the gray screen with the X cursor, and then it crashes. None of the text on the console screen looks like errors, and the last line is like "Waiting for X server to shut down." I might add that, even with the last line commented out, during the boot process I still see the line, "INIT: Switching to runlevel 5." -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go... # inittab This file describes how the INIT process should set up # the system in a certain run-level. # Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]> # Modified for RHS Linux by Marc Ewing and Donnie Barnes # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Things to run in every runlevel. # commented out by Lane # ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run gettys in standard runlevels 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 # 6:2345:respawn:/sbin/mingetty tty6 6:2345:respawn:/sbin/mgetty ttyS1 # Run xdm in runlevel 5 # xdm is now a separate service x:5:respawn:/etc/X11/prefdm -nodaemon
Re: [expert] Can't Break X Autostart
Sheldon Lee Wen wrote: > "Stephen F. Bosch" wrote: > [snip] > > > If you don't use "init", lilo doesn't know what to do with the parameter. > > Yes it does. I use "linux 3" at the lilo prompt all the time. No > problems. Well, mine doesn't =) -Stephen-
Re: [expert] Can't Break X Autostart
On Tue, 04 Apr 2000, you wrote: > John Aldrich wrote: > > > On Tue, 04 Apr 2000, you wrote: > > > It won't. You need "mx init 3". > > > Without the init, you just gave lilo a random number, which it cheerfully > > > ignored. > > > > > If that's so, why does "linux 1" work? > > Did he say it did? > Nope, but it works here... :-) John
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > Stephen F. Bosch said: > > > Entering "mx 3" does not prevent X from autostarting. Here is the > lilo.conf > > > stanza: > > > image = /boot/vmlinuz-2.2.14-15mdk > > > label = mx > > > vga = normal > > > append = "mem=124M" > > > root = /dev/hdb8 > > > read-only > > > > Again -- have you tried "mx init 3"? Init doesn't know you're talking to it > > unless you say "init". > > OK, I tried "mx init 3" with the same result. At one point in the boot it says: > INIT: Switching to runlevel 5 in 2 seconds > sbin/telinit 5 > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... Lane, POST the output of this and, if you show any files besides /etc/rc.d/init.d/kudzu in the output, please attach them . If kudzu is the only file, then attach it. If you have something in /etc/pcmcia/serial, make sure you send that. You will need to run the command in superuser mode # rgrep -i -l -r telinit /etc There is a chance that it is in another directory besides /etc, but # rgrep -i -l -r telinit / WILL hang on /proc after showing /proc/kcore and will need to be terminated with ctrl-C We are NOT lookiing for files of the nature /home///*, nor /var/lib/*.rpm, nor /var/lib/*.db if you elect to do this more thorough search. Also post the output of $ grep "^id:" /etc/inittab The # and the $ means the system prompt This is too strange for words I thought someone else would handle it, but this one is very different. Not reproducible here. Civileme
Re: [expert] Can't Break X Autostart
I thought that this problem had been solved long ago. The original poster (you?) discovered that the end of hir rc.local had something that switched the runlevel to 5. Just delete those lines. (Runlevel 5 is xdm/kdm; runlevel 3 is normal multi-user text mode.) On Tue, 04 Apr 2000, you wrote: | Stephen F. Bosch said: | > > Entering "mx 3" does not prevent X from autostarting. Here is the | lilo.conf | > > stanza: | > > image = /boot/vmlinuz-2.2.14-15mdk | > > label = mx | > > vga = normal | > > append = "mem=124M" | > > root = /dev/hdb8 | > > read-only | > | > Again -- have you tried "mx init 3"? Init doesn't know you're talking to it | > unless you say "init". | | OK, I tried "mx init 3" with the same result. At one point in the boot it says: | INIT: Switching to runlevel 5 in 2 seconds | sbin/telinit 5 | -- | Lane | | Lane Lester / Madison County, Georgia USA | Using Linux to get where I want to go... -- "Brian, the man from babbleon-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
Re: [expert] Can't Break X Autostart
John Aldrich wrote: > On Tue, 04 Apr 2000, you wrote: > > It won't. You need "mx init 3". > > Without the init, you just gave lilo a random number, which it cheerfully > > ignored. > > > If that's so, why does "linux 1" work? Did he say it did? -Stephen-
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > > Again -- have you tried "mx init 3"? Init doesn't know you're talking to it > > unless you say "init". > > OK, I tried "mx init 3" with the same result. At one point in the boot it says: > INIT: Switching to runlevel 5 in 2 seconds > sbin/telinit 5 I swear... it looks like you have weird stuff in your inittab. Why don't you post it? -Stephen-
Re: [expert] Can't Break X Autostart
"Stephen F. Bosch" wrote: [snip] > If you don't use "init", lilo doesn't know what to do with the parameter. Yes it does. I use "linux 3" at the lilo prompt all the time. No problems. -- == "Definitions involving chicken heads no longer apply." -Jon katz ==
Re: [expert] Can't Break X Autostart
On Tue, 04 Apr 2000, you wrote: > It won't. You need "mx init 3". > Without the init, you just gave lilo a random number, which it cheerfully > ignored. > If that's so, why does "linux 1" work? John
Re: [expert] Can't Break X Autostart
At 07:45 04/04/00 EDT, you wrote: >Stephen F. Bosch said: >> > Entering "mx 3" does not prevent X from autostarting. Here is the >lilo.conf >> > stanza: >> > image = /boot/vmlinuz-2.2.14-15mdk >> > label = mx >> > vga = normal >> > append = "mem=124M" >> > root = /dev/hdb8 >> > read-only >> >> Again -- have you tried "mx init 3"? Init doesn't know you're talking to it >> unless you say "init". > >OK, I tried "mx init 3" with the same result. At one point in the boot it says: >INIT: Switching to runlevel 5 in 2 seconds >sbin/telinit 5 >-- How about "mx init s" or "mx init single"?? ttfn nick@nexnix >
Re: [expert] Can't Break X Autostart
Stephen F. Bosch said: > > Entering "mx 3" does not prevent X from autostarting. Here is the lilo.conf > > stanza: > > image = /boot/vmlinuz-2.2.14-15mdk > > label = mx > > vga = normal > > append = "mem=124M" > > root = /dev/hdb8 > > read-only > > Again -- have you tried "mx init 3"? Init doesn't know you're talking to it > unless you say "init". OK, I tried "mx init 3" with the same result. At one point in the boot it says: INIT: Switching to runlevel 5 in 2 seconds sbin/telinit 5 -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
It won't. You need "mx init 3". Without the init, you just gave lilo a random number, which it cheerfully ignored. --- Lane Lester <[EMAIL PROTECTED]> wrote: > Entering "mx 3" does not prevent X from autostarting. Here is the lilo.conf > stanza: > image = /boot/vmlinuz-2.2.14-15mdk > label = mx > vga = normal > append = "mem=124M" > root = /dev/hdb8 > read-only > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... > > = Mage Grimau, Strange Unwashed & Somewhat Slightly Dazed VoiceMail/Fax: 1-651-328-1145 __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > Stephen F. Bosch said: > > linux 3 doesn't work for me... > > > > i type: > > > > linux init 3 > > > > (try that =) ) > > No, it doesn't work for me. The key part of this is the "init 3" part -- it should come after whatever profile name you've configured lilo to use for Linux. If you don't use "init", lilo doesn't know what to do with the parameter. At least see if you can get into console mode this way first. -Stephen-
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > Entering "mx 3" does not prevent X from autostarting. Here is the lilo.conf > stanza: > image = /boot/vmlinuz-2.2.14-15mdk > label = mx > vga = normal > append = "mem=124M" > root = /dev/hdb8 > read-only Again -- have you tried "mx init 3"? Init doesn't know you're talking to it unless you say "init". -Stephen-
Re: [expert] Can't Break X Autostart
Mike & Tracy Holt said: > I haven't been following this thread, so excuse my ignorance. Did you say > that X works o.k.? If so, go to the Drakconf icon on your kde desktop and > then select the 'X configurator' button. That will allow you to adjust your > settings and whether you want to boot directly into X or go straight to the > command line. The X Configuration button just provides resolution choices for me. If I click the Linuxconf button, then it presents "Init default runlevel" options. However, I've had that set to 3 for some time, and X still autostarts. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Stephen F. Bosch said: > linux 3 doesn't work for me... > > i type: > > linux init 3 > > (try that =) ) No, it doesn't work for me. What does your linux.conf look like? I have customized mine for shorter entries: win, mx, mc, and m2. The idea is that win starts Win98, mx starts Mandrake in X, mc starts Mandrake console (this doesn't work yet), and m2 starts a completely separate Mandrake install. Here is mine: boot = /dev/hda timeout = 200 prompt vga = extended read-only other = /dev/hda3 label = win image = /boot/vmlinuz-2.2.14-15mdk label = mx vga = normal append = "mem=124M" root = /dev/hdb8 read-only image = /boot/vmlinuz-2.2.14-15mdk label = mc vga = normal append = "3" root = /dev/hdb8 read-only image = /mnt/mandrake2boot/vmlinuz label = m2 vga = normal append = "mem=124M" root = /dev/hda7 Something somewhere in my system is overriding the usual controls of whether Linux boots just to the console or autostarts X. No one knows just what that is. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Entering "mx 3" does not prevent X from autostarting. Here is the lilo.conf stanza: image = /boot/vmlinuz-2.2.14-15mdk label = mx vga = normal append = "mem=124M" root = /dev/hdb8 read-only -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Lane Lester wrote: > jpilrose said: > > > > > Another solution is to just type linux 3 at the boot prompt then you > are sure > > you will only go to level 3. > linux 3 doesn't work for me... i type: linux init 3 (try that =) ) -Stephen-
Re: [expert] Can't Break X Autostart
I haven't been following this thread, so excuse my ignorance. Did you say that X works o.k.? If so, go to the Drakconf icon on your kde desktop and then select the 'X configurator' button. That will allow you to adjust your settings and whether you want to boot directly into X or go straight to the command line. Just a little more info... Michael Holt [EMAIL PROTECTED] - Original Message - From: "Lane Lester" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, April 02, 2000 3:13 PM Subject: Re: [expert] Can't Break X Autostart > Stephen Bosch said: > > > What could be overriding the inittab line? > > > > Have you got 'startx' in any of your startup scripts? > > Sure don't. Taking the other guy's question as a clue, I commented out the last > line of inittab: > x:5:respawn:/etc/X11/prefdm -nodaemon > > After I rebooted, sure enough, I stayed in the console. However, when I > executed startx, X started to the gray screen and then crashed back to the > console! > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... >
Re: [expert] Can't Break X Autostart
Adding the '3' in there is what does the trick Michael Holt [EMAIL PROTECTED] - Original Message - From: "Lane Lester" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 03, 2000 4:01 AM Subject: Re: [expert] Can't Break X Autostart > jpilrose said: > > > > > Another solution is to just type linux 3 at the boot prompt then you > are sure > > you will only go to level 3. > > I =think= that works only for folks who haven't customized their lilo.conf. For > example, I type mx (Mandrake X) or mc (Mandrake Console... which doesn't work) > or win (Win98). > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go... >
Re: [expert] Can't Break X Autostart
jpilrose said: > > Another solution is to just type linux 3 at the boot prompt then you are sure > you will only go to level 3. I =think= that works only for folks who haven't customized their lilo.conf. For example, I type mx (Mandrake X) or mc (Mandrake Console... which doesn't work) or win (Win98). -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Tom Berkley said: > Yeah, that's ok. Don't know what to suggest now. Good luck. Thanks for trying, Tom. Isn't it interesting that this is a mystery? Sometimes I think it would be better if Linux were more standardized this way. For example, I had people tell me to use .xsession to start programs with X, but it seems that Mandrake ignores that one and only responds to .xinitrc. -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
At 18:13 02/04/00 EDT, you wrote: >Stephen Bosch said: >> > What could be overriding the inittab line? >> >> Have you got 'startx' in any of your startup scripts? > >Sure don't. Taking the other guy's question as a clue, I commented out the last >line of inittab: >x:5:respawn:/etc/X11/prefdm -nodaemon > >After I rebooted, sure enough, I stayed in the console. However, when I >executed startx, X started to the gray screen and then crashed back to the >console! Looks like you Xwindows is not set up right - try running your Xconfigurator from the command line. hih nick@nexnix >-- >Lane > >Lane Lester / Madison County, Georgia USA >Using Linux to get where I want to go... > > >
Re: [expert] Can't Break X Autostart
Stephen Bosch said: > > What could be overriding the inittab line? > > Have you got 'startx' in any of your startup scripts? Sure don't. Taking the other guy's question as a clue, I commented out the last line of inittab: x:5:respawn:/etc/X11/prefdm -nodaemon After I rebooted, sure enough, I stayed in the console. However, when I executed startx, X started to the gray screen and then crashed back to the console! -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Yeah, that's ok. Don't know what to suggest now. Good luck. Tom Lane Lester wrote: > > Tom Berkley said: > > > What are the last two lines in your /etc/inittab? > > # Run xdm in runlevel 5 > # xdm is now a separate service > x:5:respawn:/etc/X11/prefdm -nodaemon > > Is that it? > > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
Another solution is to just type linux 3 at the boot prompt then you are sure you will only go to level 3. Jim > > > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > > On 4/2/00, 8:36:07 AM, Lane Lester <[EMAIL PROTECTED]> wrote > regarding [expert] Can't Break X Autostart: > > > > When I installed Mandrake 7, I chose the X autostart option. Now I'd > like to > > stop that and have a console logon. I changed the inittab line to: > > id:3:initdefault: > > but X still autostarts. I'm wondering if it has something to do with > my > > installation of a newer version of LinuxConf. When I run LinuxConf > from within > > DrakConf, it says that the Default runlevel is 3... but X still > autostarts. > > > During the boot, I see the words, "Dropin's boot time commands," and > I'm > > wondering if that has something to do with the problem. I don't know > what the > > words refer to. > > > What could be overriding the inittab line? > > Have you got 'startx' in any of your startup scripts? > > -Stephen- > > > > -- Jim Pilrose Sysadmin Future Sight
Re: [expert] Can't Break X Autostart
Tom Berkley said: > What are the last two lines in your /etc/inittab? # Run xdm in runlevel 5 # xdm is now a separate service x:5:respawn:/etc/X11/prefdm -nodaemon Is that it? -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
Re: [expert] Can't Break X Autostart
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 4/2/00, 8:36:07 AM, Lane Lester <[EMAIL PROTECTED]> wrote regarding [expert] Can't Break X Autostart: > When I installed Mandrake 7, I chose the X autostart option. Now I'd like to > stop that and have a console logon. I changed the inittab line to: > id:3:initdefault: > but X still autostarts. I'm wondering if it has something to do with my > installation of a newer version of LinuxConf. When I run LinuxConf from within > DrakConf, it says that the Default runlevel is 3... but X still autostarts. > During the boot, I see the words, "Dropin's boot time commands," and I'm > wondering if that has something to do with the problem. I don't know what the > words refer to. > What could be overriding the inittab line? Have you got 'startx' in any of your startup scripts? -Stephen-
Re: [expert] Can't Break X Autostart
What are the last two lines in your /etc/inittab? Tom Lane Lester wrote: > > When I installed Mandrake 7, I chose the X autostart option. Now I'd like to > stop that and have a console logon. I changed the inittab line to: > id:3:initdefault: > but X still autostarts. I'm wondering if it has something to do with my > installation of a newer version of LinuxConf. When I run LinuxConf from within > DrakConf, it says that the Default runlevel is 3... but X still autostarts. > > During the boot, I see the words, "Dropin's boot time commands," and I'm > wondering if that has something to do with the problem. I don't know what the > words refer to. > > What could be overriding the inittab line? > -- > Lane > > Lane Lester / Madison County, Georgia USA > Using Linux to get where I want to go...
[expert] Can't Break X Autostart
When I installed Mandrake 7, I chose the X autostart option. Now I'd like to stop that and have a console logon. I changed the inittab line to: id:3:initdefault: but X still autostarts. I'm wondering if it has something to do with my installation of a newer version of LinuxConf. When I run LinuxConf from within DrakConf, it says that the Default runlevel is 3... but X still autostarts. During the boot, I see the words, "Dropin's boot time commands," and I'm wondering if that has something to do with the problem. I don't know what the words refer to. What could be overriding the inittab line? -- Lane Lane Lester / Madison County, Georgia USA Using Linux to get where I want to go...
