[SOLVED] Disabling autologin for the "vl" account.

[axelswe]

Hi.

I want to shut of the autologin for the vl-account and then remove it. I tried removing it without removing the loginscript and the boot process went bananas.
I figure i should change one of the files in the /rc.d/ folder. Which I for instance have done to make wicd autostart

[nightflier]

Which version of VL are you using?

[axelswe]

6.0 light live with xfce

[sledgehammer]

I am interested in this thread.  Perhaps it will give me a clue how, on start up, I can get VL 6.0 standard to automatically boot into the new kernel (2.6.27.29).

John

[nightflier]

Assuming you kept KDM as your login manager on Light. As root run command:

Code:

/sbin/vkdmconf

For booting different kernels, use vliloconf.

[budulay]

I am interested in this thread.  Perhaps it will give me a clue how, on start up, I can get VL 6.0 standard to automatically boot into the new kernel (2.6.27.29).

John

that one can be solved by changing the default parameter in your /etc/lilo.conf

[sledgehammer]

budulay,

This is how it looked:

# End LILO global section
# Partition 4: Linux
image = /boot/vmlinuz-2.6.27.29
    root = /dev/hda2
    label = 2.6.27.29
    append = " "
    read-only


# Partition 1: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hda2
    label = linux
    append = " "
    read-only
   
# Partition 2: Linux TUI mode
image = /boot/vmlinuz
    root = /dev/hda2
    label = linux-tui               
    append = "2  "
    read-only
   
# Partition 3: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hda2
    label = linux-gui
    append = "4  "
    read-only

I changed "Partition 4" to "Partition 1" and renumbered the other two, but it didn't change the login screen.

I must be doing something wrong. So I changed it back to original, as above, and did up this reply.

Any thoughts?

John

[nightflier]

Towards the beginning of lilo.conf, in the "Global" section, find the line that says:

Code:

default = linux

That is the label of default boot.
Change "linux" to "2.6.27.29", then run command "lilo".

[axelswe]

Assuming you kept KDM as your login manager on Light. As root run command:

Code:

/sbin/vkdmconf

Thanks a bunch

[sledgehammer]

Thanks nightflier!

However it still boots into linux, rather than 2.6.27.29.  I probably screwed it up somehow when I was fooling with it before writing the forum.

Here is my complete lilo.conf

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
default = 2.6.27.29
compact
prompt
timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
bitmap = /boot/bitmap/boot.bmp
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769


# End LILO global section
# Partition 4: Linux
image = /boot/vmlinuz-2.6.27.29
    root = /dev/hda2
    label = 2.6.27.29
    append = " "
    read-only


# Partition 1: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hda2
    label = linux
    append = " "
    read-only
   
# Partition 2: Linux TUI mode
image = /boot/vmlinuz
    root = /dev/hda2
    label = linux-tui               
    append = "2  "
    read-only
   
# Partition 3: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hda2
    label = linux-gui
    append = "4  "
    read-only

Any thoughts?

John

[nightflier]

Did you run command "lilo" after editing the file?

[sledgehammer]

Nope.

So, I ran lilo, rebooted, and it works (boots into 2.6.27.29 by default).

Thanks nightflier.

Now both the original and my piggyback aspect of this thread are solved.

John