the Arch Linux thread

ico

Super Moderator
Staff member
What is the difference between the inittab method and the daemon method?
well, inittab is how it should be.

Because if you use the rc.conf daemon method and your display manager always hangs because of some trouble, you'll have to boot into run-level 1 via grub, remove gdm daemon, and then reboot to fix things up. You're firing something up when it shouldn't get fired. I prefer booting into run-level 3 via bootloader to fix problems; kdm/gdm as a 'daemon' hanging in the beginning won't let me to.

Or (All iz well scenario) in simple words if you fire them as daemons, you can't prevent graphical login i.e. can't go to run-level 3 via bootloader.

Like I said, inittab is how it should be. This is a weird answer. But still inittab is how it should be. imo, starting your display manager as "daemon" is a "hack"... I hope you got what I meant.
 

krishnandu.sarkar

Simply a DIGITian
Staff member
That's right. I completely agree with ico's idea. I'm also using inittab. What ico said, is also described in that Beginners Guide.
 

doomgiver

Warframe
well, inittab is how it should be.

Because if you use the rc.conf daemon method and your display manager always hangs because of some trouble, you'll have to boot into run-level 1 via grub, remove gdm daemon, and then reboot to fix things up. You're firing something up when it shouldn't get fired. I prefer booting into run-level 3 via bootloader to fix problems; kdm/gdm as a 'daemon' hanging in the beginning won't let me to.

Or (All iz well scenario) in simple words if you fire them as daemons, you can't prevent graphical login i.e. can't go to run-level 3 via bootloader.

Like I said, inittab is how it should be. This is a weird answer. But still inittab is how it should be. imo, starting your display manager as "daemon" is a "hack"... I hope you got what I meant.
so this is why my DE's were not working :(
i had to manually kickstart them all the time
 

Desmond

Destroy Erase Improve
Staff member
Admin
I am getting a weird problem now, no idea what's wrong. But the root device is not being detected. Please help.

*i.imgur.com/wFtU4.png
 
Last edited:

hellknight

BSD init pwns System V
Hmm.. that seem to be some disk identification problem. As you're running to OS inside the VM, did you changed the name of the disk or move it outside the directory it was previously on?
 

njathan

Right off the assembly line
I am getting a weird problem now, no idea what's wrong. But the root device is not being detected. Please help.

*i.imgur.com/wFtU4.png

Chroot into the root partition using a live CD/DVD and rebuild/install initramfs image.

Refer:
*wiki.archlinux.org/index.php/Change_Root
*wiki.archlinux.org/index.php/Mkinitcpio#Image_creation_and_activation

Chrooting has a series of steps.. try to follow them.
To rebuild the image, use
Code:
mkinitcpio -p linux
This assumes you are using stock kernel. If that does not work for mkinitcpio, refer the complete wiki above.

Hmm.. that seem to be some disk identification problem. As you're running to OS inside the VM, did you changed the name of the disk or move it outside the directory it was previously on?

This usually happens when you force a upgrade using the pacman switch.
 

Desmond

Destroy Erase Improve
Staff member
Admin
Yes, it happened after I did a "pacman -Syu".

Will try these out and let you know what happens.
 

ico

Super Moderator
Staff member
Code:
alsactl -f /var/lib/alsa/asound.state store
Just posting it here for future reference. Sometimes a weird message comes up on boot. "Alsa generic initilize" something.
 

Anish

Spectre
Hi,
I tried to install arch on my laptop [core-local]
Here is how i partitioned the hardisk - I already had windows7 and suse in dual boot. Now I killed the suse and accommodated the space for arch. I need win7 + arch now.

sda1 - Primary - NTFS - windows (Sys reserved)
sda2 - Primary - NTFS - windows (c)
sda3 - Primary - NTFS - windows (other files)
sda4 - Logical - linux - /boot * [ flagged as bootable]
sda5 - Logical - linux - /linux swap
sda6 - Logical - linux - /root
sda7 - Logical - linux - /var
sda8 - Logical - linux - /home

Now, after setting up the hdd like the above, when i give "Write partition table" I get a message stating:

"No primary partitions are marked bootable. DOS MBR cannot boot this"

kindly help.
 

Anish

Spectre
The problem here is as your error says. /boot has to be in primary.

Yeah.. but linux stays in logical partitions afaik. why do i get this error and it does not proceed further. My data is locked in windows partition, I have no backup.
 

Liverpool_fan

Sami Hyypiä, LFC legend
Why do you need a separate /boot anyway. And you've flagged a logical drive with the boot flag. Change it to a primary partition, preferably your windows boot partition or "C:" partition.
And what's the point of the windows boot partition (the system reserved one. One should simply pre-plan the partition layout so that the WIndows installer does not create that useless partition) and the third NTFS partition? It need not be primary for any reason.
 

Anish

Spectre
Why do you need a separate /boot anyway. And you've flagged a logical drive with the boot flag. Change it to a primary partition, preferably your windows boot partition or "C:" partition.
And what's the point of the windows boot partition (the system reserved one. One should simply pre-plan the partition layout so that the WIndows installer does not create that useless partition) and the third NTFS partition? It need not be primary for any reason.

Dude, thanks for your reply.
Those partitions are created by default when I installed windows at that time I was a noob :wink:
Now, if I change the boot flag to windows partition, will it not damage the partition? i want all the three windows partition intact.
 
Top Bottom