>
> 2) is still sourced from '/etc/X11/xinit/Xclients' for two envvars:
> - 'DESKTOP' - nickname for one from recognized sessions (GNOME, KDE, MATE
> or LXDE).
> - 'PREFERRED' - in case when 'DESKTOP' unset/unrecognized, this variable
> should be path for program starting graphical session (for
On Tue, 26 Jul 2022 10:09:39 +0100
Ankur Sinha wrote:
> Hi folks,
>
> While updating this quick-doc, I came across the last section where
> `/etc/sysconfig/desktop` is mentioned as a config file to change default
> desktop environment etc.
>
> https://docs.fedoraproject
Hi folks,
While updating this quick-doc, I came across the last section where
`/etc/sysconfig/desktop` is mentioned as a config file to change default
desktop environment etc.
https://docs.fedoraproject.org/en-US/quick-docs/switching-desktop-environments/
I haven't been able to find any
On Wed, Oct 17, 2018 at 09:28:41AM -0400, Ben Cotton wrote:
> == Upgrade/compatibility impact ==
> In [https://bugzilla.redhat.com/show_bug.cgi?id=1619270 BZ1619270] a
> python script that will convert a sysconfig/nfs config into nfs.conf
> config. There are a couple thoughts on how to use it.
On Sat, Oct 27, 2018 at 12:41:01PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Oct 17, 2018 at 09:28:41AM -0400, Ben Cotton wrote:
> > == Upgrade/compatibility impact ==
> > In [https://bugzilla.redhat.com/show_bug.cgi?id=1619270 BZ1619270] a
> > python script that will convert a
https://fedoraproject.org/wiki/Changes/nfs.conf
== Summary ==
Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure
NFS daemons.
== Owner ==
* Name: Steve Dickson
* Email: ste...@redhat.com
== Detailed Description ==
Since the beginning /etc/sysconfig/nfs has been used
https://fedorahosted.org/389/ticket/48950
https://fedorahosted.org/389/attachment/ticket/48950/0001-Ticket-48950-don-t-EXPORT-varaibles-from-etc-sysconf.patch
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/389-devel@lists.fedoraproject.org
Hi,
Today after round and round and since begging of Fedora with grub2. I
think this page https://fedoraproject.org/wiki/GRUB_2#Setting_default_e
ntry (on setting one default entry) is missing mention that we need
set UPDATEDEFAULT=no in /etc/sysconfig/kernel, for when is running
/sbin/new-kernel
commit 848975062c84ef81f2678ad2a77c2f3ece0e19c6
Author: Adam Williamson awill...@redhat.com
Date: Fri May 10 10:05:57 2013 -0700
init_network.patch: don't source /etc/sysconfig/network in initscript
amavisd-new-2.8.0-init_network.patch | 13 +
amavisd-new.spec
Summary of changes:
8489750... init_network.patch: don't source /etc/sysconfig/network in (*)
(*) This commit already existed in another branch; no separate mail sent
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel
2012/9/19 Antonio Trande anto.tra...@gmail.com
2012/9/19 Bill Nottingham nott...@redhat.com
Sérgio Basto (ser...@serjux.com) said:
Hi,
In my F17 system
rpm -qf /etc/sysconfig/modules/*
bluez-4.99-2.fc17.x86_64
qemu-system-x86-1.0.1-1.fc17.x86_64
on this
http://fedora-os.org
On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
As long as another issue: at every reboot I am compelled to restart
'fedora-loadmodules.service', otherwise the problem with vbox modules
arises again.
No , fedora-loadmodules.service run at startup by default .
--
Sérgio M. B.
--
2012/9/26 Sérgio Basto ser...@serjux.com
On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
As long as another issue: at every reboot I am compelled to restart
'fedora-loadmodules.service', otherwise the problem with vbox modules
arises again.
No , fedora-loadmodules.service run at
On Qua, 2012-09-26 at 19:23 +0200, Antonio Trande wrote:
2012/9/26 Sérgio Basto ser...@serjux.com
On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
As long as another issue: at every reboot I am compelled to
restart
'fedora-loadmodules.service',
2012/9/26 Sérgio Basto ser...@serjux.com
On Qua, 2012-09-26 at 19:23 +0200, Antonio Trande wrote:
2012/9/26 Sérgio Basto ser...@serjux.com
On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
As long as another issue: at every reboot I am compelled to
restart
2012/9/19 Bill Nottingham nott...@redhat.com
Sérgio Basto (ser...@serjux.com) said:
Hi,
In my F17 system
rpm -qf /etc/sysconfig/modules/*
bluez-4.99-2.fc17.x86_64
qemu-system-x86-1.0.1-1.fc17.x86_64
on this
http://fedora-os.org/2012/09/13/workaround-for-vbox-modules-loading
Sérgio Basto (ser...@serjux.com) said:
Hi,
In my F17 system
rpm -qf /etc/sysconfig/modules/*
bluez-4.99-2.fc17.x86_64
qemu-system-x86-1.0.1-1.fc17.x86_64
on this
http://fedora-os.org/2012/09/13/workaround-for-vbox-modules-loading/
Antonio Trande says that modules of vbox ( don't
On Wed, 2011-07-20 at 11:48 +0200, Adam Tkac wrote:
Any idea how to handle the VNCSERVERS argument in backward-compatible
way is welcomed, otherwise I will simply drop sysconfig support at all
in the service file and admin will have to create /etc/systemd/system/
service files with appropriate
On Wed, 20.07.11 11:48, Adam Tkac (at...@redhat.com) wrote:
Hello all,
I'm trying to package systemd service file for tigervnc server and to
find a solution how to make it backward-compatible with current format
of the /etc/sysconfig/vncservers.
Current /etc/sysconfig/vncservers has
Le Lun 18 juillet 2011 20:57, Lennart Poettering a écrit :
No. There is no need for a directory that replaces /etc/sysconfig. It's
borked. If a daemon has not configuration file but should have one, then
fix the daemon, don't fake a configuration file.
Well, really that's a bit rich comming
You know, I am not really developer, I just a user and my laptop starts only
Xorg, Apache, DNS proxy
(to filter web adv sites), Privoxy, Perl and something else.
Right now systemd can't boot my system up, it hangs everything. So I fixed up
upstart (mainly to be
able use selinux and update the
On 07/19/2011 10:23 AM, Lucas wrote:
Right now systemd can't boot my system up, it hangs everything.
You're hitting a kernel bug, don't blame systemd.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, 19.07.11 03:43, Miloslav Trmač (m...@volny.cz) wrote:
On Mon, Jul 18, 2011 at 11:34 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
On Mon, 18.07.11 23:26, Miloslav Trmač (m...@volny.cz) wrote:
I can't see a reason to discuss /etc/sysconfig as a single unit, nor
to argue
'last one wins' behavior among multiple DMs.
I suppose we could use alternatives for this, as much as I dislike it.
I meant creating that symlink was the replacement for
/etc/sysconfig/desktop, the end-user configuration.
Yes, this link will replace the config file.
As for what
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Hi,
2011/7/18 Neal Becker ndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I think
the right way it keeping minimal, standardized configuration in
/etc
On Mon, 18.07.11 20:54, Michał Piotrowski (mkkp...@gmail.com) wrote:
Hi,
2011/7/18 Neal Becker ndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I
On 07/18/2011 06:57 PM, Lennart Poettering wrote:
On Mon, 18.07.11 20:54, Michał Piotrowski (mkkp...@gmail.com) wrote:
Hi,
2011/7/18 Neal Beckerndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I
On Mon, 2011-07-18 at 20:57 +0200, Lennart Poettering wrote:
On Mon, 18.07.11 20:54, Michał Piotrowski (mkkp...@gmail.com) wrote:
Hi,
2011/7/18 Neal Becker ndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I think
the right way it keeping minimal, standardized configuration in
/etc/services.conf/ or something like that.
No. There is no need
and
in the sense of political will to make the necessary changes.)
The necessary political will to obsolete /etc/sysconfig may not exist
at this very moment but I think that the reasoning is sound enough
that anticipating, identifying and mitigating potential problems the
removal would cause seems
Simo Sorce s...@redhat.com writes:
On Mon, 2011-07-18 at 20:57 +0200, Lennart Poettering wrote:
http://0pointer.de/blog/projects/on-etc-sysinit.html
No. There is no need for a directory that replaces /etc/sysconfig. It's
borked. If a daemon has not configuration file but should have one
Software, and software that cannot be modified would not
qualify as that.
Lennart
SNIP
What about /etc/sysconfig/network and /etc/sysconfig/network-scripts/
... where would be a more appropriate location for those? Not saying
there isn't one, just wondering what the logical progression would
On Mon, 18.07.11 15:34, Tom Lane (t...@redhat.com) wrote:
Simo Sorce s...@redhat.com writes:
On Mon, 2011-07-18 at 20:57 +0200, Lennart Poettering wrote:
http://0pointer.de/blog/projects/on-etc-sysinit.html
No. There is no need for a directory that replaces /etc/sysconfig. It's
Lennart Poettering mzerq...@0pointer.de writes:
On Mon, 18.07.11 15:34, Tom Lane (t...@redhat.com) wrote:
Well, if they didn't need fixed before, they'll certainly need fixed
when you make them start keeping their configuration info someplace else
than /etc/sysconfig. This proposal sounds
that
is, since we need to remove it from the distro then. Fedora only
includess Free Software, and software that cannot be modified would not
qualify as that.
Lennart
SNIP
What about /etc/sysconfig/network and /etc/sysconfig/network-scripts/
... where would be a more appropriate location for those
info someplace else
than /etc/sysconfig. This proposal sounds more like wait, systemd has
not yet broken everything in sight, how can we solve that problem?
than like something that will actually improve matters for anyone.
What does systemd break in this regard?
There's a big difference
ship are
easier to fix than the US deficit (in both the technical sense and
in the sense of political will to make the necessary changes.)
The necessary political will to obsolete /etc/sysconfig may not exist
at this very moment but I think that the reasoning is sound enough
that anticipating
On Mon, Jul 18, 2011 at 02:46:30PM -0400, Neal Becker wrote:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
I'm sympathetic to Lennart's arguments, but really this should be
discussed and decided in the context of a real, open forum, drawing
Neal Becker ndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I think
the right way it keeping minimal, standardized configuration
Piotrowski (mkkp...@gmail.com) wrote:
Hi,
2011/7/18 Neal Becker ndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I think
On Mon, Jul 18, 2011 at 12:42 PM, mike cloaked mike.cloa...@gmail.com wrote:
I guess the process can be started - but by the time it is ready for
prime time then any daemons that need to work should have been tested
to work without the need for any /etc/sysconfig/... files - just by
the way
On Mon, 18.07.11 21:57, Richard W.M. Jones (rjo...@redhat.com) wrote:
On Mon, Jul 18, 2011 at 02:46:30PM -0400, Neal Becker wrote:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
I'm sympathetic to Lennart's arguments, but really
Hi,
On Mon, Jul 18, 2011 at 4:42 PM, mike cloaked mike.cloa...@gmail.com wrote:
what then out of interest is the replacement for a
/etc/sysconfig/desktop file that defines which login manager should be
the default (and which is not there by default)? Can KDM then be
started when X starts
On Mon, Jul 18, 2011 at 11:14 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
On Mon, 18.07.11 21:57, Richard W.M. Jones (rjo...@redhat.com) wrote:
On Mon, Jul 18, 2011 at 02:46:30PM -0400, Neal Becker wrote:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects
David Michael (fedora@gmail.com) said:
what then out of interest is the replacement for a
/etc/sysconfig/desktop file that defines which login manager should be
the default (and which is not there by default)? Can KDM then be
started when X starts and not GDM without the use
...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I think
the right way it keeping minimal, standardized configuration in
/etc
On Mon, 18.07.11 17:00, Simo Sorce (s...@redhat.com) wrote:
Generally speaking I like the idea of dropping /etc/sysconfig. I think
the right way it keeping minimal, standardized configuration in
/etc/services.conf/ or something like that.
No. There is no need
On Mon, 18.07.11 23:17, Miloslav Trmač (m...@volny.cz) wrote:
These interfaces introduced by systemd are actually discussed in quite
some detail on the systemd irc channel and mailing list. It's a very
open forum, you are welcome to join.
So Fedora is the right place to discuss removal
LSB?
/etc/sysconfig is not a file format standard.
/etc/sysconfig is not a place where configuration files of the same
format or purpose are stored.
/etc/sysconfig is not a place used to store configuration shared by
independent software packages.
/etc/sysconfig is not a software package.
I can't
Hi,
On Mon, Jul 18, 2011 at 5:16 PM, Bill Nottingham nott...@redhat.com wrote:
Right, but that then causes 'last one wins' behavior among multiple DMs.
I suppose we could use alternatives for this, as much as I dislike it.
I meant creating that symlink was the replacement for
/etc/sysconfig
to go to the hospital to be cured.
Pregnancy and /etc/sysconfig are perfectly natural and healthy. Pregnant
women and /etc/sysconfig both have perfectly valid use cases and do not
need to be fixed :)
Most pregnancies last ~40 weeks. If that takes much longer it needs to be fixed.
Kay
--
devel
it.
I meant creating that symlink was the replacement for
/etc/sysconfig/desktop, the end-user configuration.
Yes, this link will replace the config file.
As for what packages do about their DM service files, I would agree
with letting alternatives manage a default
/lib/systemd/system/display
people from all of the Linux distros (possibly BSD etc
too). Perhaps LSB?
/etc/sysconfig is not a file format standard.
/etc/sysconfig is not a place where configuration files of the same
format or purpose are stored.
/etc/sysconfig is not a place used to store configuration shared
someplace else
than /etc/sysconfig. This proposal sounds more like wait, systemd has
not yet broken everything in sight, how can we solve that problem?
than like something that will actually improve matters for anyone.
What does systemd break in this regard?
There's a big difference between
On Mon, 2011-07-18 at 23:14 +0200, Lennart Poettering wrote:
On Mon, 18.07.11 21:57, Richard W.M. Jones (rjo...@redhat.com) wrote:
On Mon, Jul 18, 2011 at 02:46:30PM -0400, Neal Becker wrote:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc
Hi,
On Mon, Jul 18, 2011 at 5:32 PM, Kay Sievers kay.siev...@vrfy.org wrote:
We should not let packages create config files in lib, lib is more for
static content from rpms, not really for configuration. For the same
reason, 'systemctl enable/disable' acts on /etc only.
I had imagined using
ndbeck...@gmail.com:
This article recommends ending /etc/sysconfig
http://0pointer.de/blog/projects/on-etc-sysinit.html
Generally speaking I like the idea of dropping /etc/sysconfig. I
think
the right way it keeping minimal, standardized configuration in
/etc
.
Lennert's review of what we have currently in /etc/sysconfig is
correct -- a horrid mess. A cleanup is needed. But we can't do away
with the ability to override the shipped configuration.
For example - I often use those overrides to point a daemon to a
different config file or dir, so as to make
59 matches
Mail list logo
