You are not logged in.

#1 2012-12-05 22:15:35

theking2
Member
From: Romanshorn Switzerland
Registered: 2009-03-04
Posts: 326

The legacy configuration options are no longer supported in rc.conf

Hi!

pacman reports "The legacy configuration options are no longer supported in rc.conf" what does this mean? I don't think I have any legacy configuration in my rc.conf but how can I be sure?


cheers


archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise  PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR

Offline

#2 2012-12-05 22:21:34

FlyingHappy
Member
From: Cincinnati, OH
Registered: 2011-04-18
Posts: 186

Re: The legacy configuration options are no longer supported in rc.conf

If you read the home page, the old init scripts are no longer supported, so you shouldn't even have an rc.conf anymore.  That is basically what it is saying, you should be using systemd now.

Offline

#3 2012-12-05 22:26:48

DSpider
Member
From: Romania
Registered: 2009-08-23
Posts: 2,273

Re: The legacy configuration options are no longer supported in rc.conf

DAEMONS line from rc.conf still works tho. For now. But the rest of the stuff was discarded when SysVinit was replaced by systemd back in October.

See this for the transition. Just be careful about:

...
Otherwise, a service file may not be available for systemd. In that case, you'll need to keep rc.conf to start the service during boot up.

Last edited by DSpider (2012-12-05 22:29:15)


"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

Offline

#4 2012-12-05 22:38:35

tomegun
Developer
From: France
Registered: 2010-05-28
Posts: 661

Re: The legacy configuration options are no longer supported in rc.conf

All our packages now have service files, so everyone should be able to migrate away from rc.conf. New users should never create/need it.

Offline

#5 2012-12-06 00:08:48

theking2
Member
From: Romanshorn Switzerland
Registered: 2009-03-04
Posts: 326

Re: The legacy configuration options are no longer supported in rc.conf

tomegun wrote:

All our packages now have service files, so everyone should be able to migrate away from rc.conf. New users should never create/need it.

Does "All our packages" also include the AUR packages? The one I specifically am worried about is the LogitechMediaServer AUR, and the miniDLA. Is there a way to find out if they will run with systemd and if not what to do?


archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise  PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR

Offline

#6 2012-12-06 00:22:32

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: The legacy configuration options are no longer supported in rc.conf

theking2 wrote:

Does "All our packages" also include the AUR packages? The one I specifically am worried about is the LogitechMediaServer AUR, and the miniDLA. Is there a way to find out if they will run with systemd and if not what to do?

Do these packages need any setting in the rc.conf file?

If not, and as long as the maintainers keep their packages up to date as Arch Devs do no officially support these packages if I remember correctly, I don't think you should worry about them working correctly.

Last edited by root (2012-12-06 00:23:12)


\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#7 2012-12-06 00:25:58

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,840
Website

Re: The legacy configuration options are no longer supported in rc.conf

theking2 wrote:
tomegun wrote:

All our packages now have service files, so everyone should be able to migrate away from rc.conf. New users should never create/need it.

Does "All our packages" also include the AUR packages?

No: they are not Arch packages.


theking2 wrote:

The one I specifically am worried about is the LogitechMediaServer AUR, and the miniDLA. Is there a way to find out if they will run with systemd and if not what to do?

You can just read the PKGBUILD rather than expecting others to do it for you...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#8 2012-12-06 01:17:44

theking2
Member
From: Romanshorn Switzerland
Registered: 2009-03-04
Posts: 326

Re: The legacy configuration options are no longer supported in rc.conf

jasonwryan wrote:
theking2 wrote:
tomegun wrote:

All our packages now have service files, so everyone should be able to migrate away from rc.conf. New users should never create/need it.

Does "All our packages" also include the AUR packages?

No: they are not Arch packages.


theking2 wrote:

The one I specifically am worried about is the LogitechMediaServer AUR, and the miniDLA. Is there a way to find out if they will run with systemd and if not what to do?

You can just read the PKGBUILD rather than expecting others to do it for you...

I can read fairly well, (with my reading glasses, admitted) what particularly do I have to (not) worry about?

p.s. I did write my own PKGBUILDs in the past that work passably well

Last edited by theking2 (2012-12-06 01:18:48)


archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise  PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR

Offline

#9 2012-12-06 01:21:08

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,840
Website

Re: The legacy configuration options are no longer supported in rc.conf

Sigh. If you read, for example the LMS, PKGBUILD you will see it installs a service file...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

Board footer

Powered by FluxBB