aking Fedora being able to function completely without the
>> > 'initscripts' package (hopefully) some day in the future. I have done some
>> > cleanup in initscripts recently, and I would like to ask maintainers of
>> > packages listed below to check if their package(s) sti
On Wed, Jul 4, 2018 at 8:16 AM Peter Robinson wrote:
>
> On Tue, Jun 19, 2018 at 3:56 PM, David Kaspar [Dee'Kej]
> wrote:
> > Hello people,
> >
> > I'm working on making Fedora being able to function completely without the
> > 'initscripts' pa
On Tue, Jun 19, 2018 at 3:56 PM, David Kaspar [Dee'Kej]
wrote:
> Hello people,
>
> I'm working on making Fedora being able to function completely without the
> 'initscripts' package (hopefully) some day in the future. I have done some
> cleanup in initscript
Hello people,
I'm working on making Fedora being able to function completely without the
'initscripts' package (hopefully) some day in the future. I have done some
cleanup in initscripts recently, and I would like to ask maintainers of
packages listed below to check if their p
On Tue, Feb 3, 2015 at 7:13 AM, Björn Persson wrote:
> Nico Kadel-Garcia wrote:
>> On Mon, Feb 2, 2015 at 12:19 AM, Björn Persson wrote:
>>
>> > What's the recommended way for a user to find out which of the three
>> > GUIs it is that pops up when one clicks on a menu entry, when the
>> > window
On Wed, 2015-01-28 at 00:38 -0500, Nico Kadel-Garcia wrote:
> Whether it has the options, and I didn't see them when using it
> yesterday, it is Not Your Friend(tm). The GUI's do not provide
> enough fine resolution, they display nothing of what the actual
> config files touched are or what th
On Mon, 2015-02-02 at 11:16 +0100, Dan Williams wrote:
> Assuming the current versions of the various DEs, then in GNOME, the
> thing you're looking at is the GNOME tools. If you're in KDE, then
> it's the KDE tools. If you're in XFCE/LXDE, then it's likely nm-
> connection-editor. So I guess
On 03.02.2015 14:16, Lukáš Nykrýn wrote:
> poma píše v Čt 22. 01. 2015 v 18:44 +0100:
>> Lukáš 'Allo 'Allo
>>
>> I see that some people are trying to "modernize" Fedora.
>> But what about RHEL relictum - initscripts, particularly now that we h
poma píše v Čt 22. 01. 2015 v 18:44 +0100:
> Lukáš 'Allo 'Allo
>
> I see that some people are trying to "modernize" Fedora.
> But what about RHEL relictum - initscripts, particularly now that we have
> NetworkManager/ModemManager and systemd-networkd,
- Original Message -
> On Mon, Feb 2, 2015 at 12:19 AM, Björn Persson wrote:
>
> > What's the recommended way for a user to find out which of the three
> > GUIs it is that pops up when one clicks on a menu entry, when the
> > window title is something generic like "network configuration
Nico Kadel-Garcia wrote:
> On Mon, Feb 2, 2015 at 12:19 AM, Björn Persson wrote:
>
> > What's the recommended way for a user to find out which of the three
> > GUIs it is that pops up when one clicks on a menu entry, when the
> > window title is something generic like "network configuration" and
On Mon, Feb 2, 2015 at 12:19 AM, Björn Persson wrote:
> What's the recommended way for a user to find out which of the three
> GUIs it is that pops up when one clicks on a menu entry, when the
> window title is something generic like "network configuration" and
> there is no about dialog? Run "ps
On Mon, 2015-02-02 at 06:19 +0100, Björn Persson wrote:
> Dan Williams wrote:
> >I'd also point out that there are three different NetworkManager GUIs,
> >and one TUI:
> >
> >1) GNOME Shell network settings - not really targeted for server
> >environments, has a smaller set of options that are suit
Dan Williams wrote:
>I'd also point out that there are three different NetworkManager GUIs,
>and one TUI:
>
>1) GNOME Shell network settings - not really targeted for server
>environments, has a smaller set of options that are suitable for
>desktop/workstation use-cases
>
>2) nm-connection-editor -
On Tue, 2015-01-27 at 22:20 -0500, Scott Schmit wrote:
> On Tue, Jan 27, 2015 at 02:18:31PM -0600, Dan Williams wrote:
> > NetworkManager is not intended only for mobile devices or notebooks,
> > because that's a small part of the networking story. Plus, more than
> > just notebooks have needs for
> and the main point is: there is no need to replace network.service on
> *any* static configured machine
(As a short-time initscripts comaintainer way-back-when:) There may not be a
need for anything smarter than init.d/network for machines with _trivial_
static configuration
On Tue, Jan 27, 2015 at 10:20 PM, Scott Schmit wrote:
> On Tue, Jan 27, 2015 at 02:18:31PM -0600, Dan Williams wrote:
>> NetworkManager is not intended only for mobile devices or notebooks,
>> because that's a small part of the networking story. Plus, more than
>> just notebooks have needs for th
On Tue, Jan 27, 2015 at 02:18:31PM -0600, Dan Williams wrote:
> NetworkManager is not intended only for mobile devices or notebooks,
> because that's a small part of the networking story. Plus, more than
> just notebooks have needs for the things that NetworkManager brings to
> the table.
>
> If
Am 28.01.2015 um 01:23 schrieb Jóhann B. Guðmundsson:
On 01/27/2015 08:18 PM, Dan Williams wrote:
We hope that NM can be installed on most systems, and will be there when
required and useful, but will get out of the way when not required.
Well I can confirm that NM pretty much does exactly th
On 01/27/2015 08:18 PM, Dan Williams wrote:
We hope that NM can be installed on most systems, and will be there when
required and useful, but will get out of the way when not required.
Well I can confirm that NM pretty much does exactly that seeing as I
have been running networkd for couple o
Am 27.01.2015 um 21:18 schrieb Dan Williams:
On Tue, 2015-01-27 at 20:56 +0100, Reindl Harald wrote:
there is a usecase for NM, surely, but not for me and not for a lot of
other people working professional in serious setups and tend to
configure personal workstations left and right as much as
On Tue, 2015-01-27 at 14:50 -0500, Nico Kadel-Garcia wrote:
>
> I have to admit that I remain pretty unhappy with NetworkManager.
> It's a complex GUI on top of the underlying actual iinit scrupts, it
Um. No it isn't. I think you have fundamentally misunderstood what
NetworkManager is. You see
On Tue, 2015-01-27 at 14:50 -0500, Nico Kadel-Garcia wrote:
> On Sun, Jan 25, 2015 at 12:40 PM, Adam Williamson
> wrote:
> > On Sun, 2015-01-25 at 08:49 -0500, Nico Kadel-Garcia wrote:
> >
> >> * KVM bridge configuration
> >
> > Works fine in F21+, I'm using NM on both my main desktop/test box and
On Tue, 2015-01-27 at 20:56 +0100, Reindl Harald wrote:
>
> Am 27.01.2015 um 20:50 schrieb Nico Kadel-Garcia:
> > On Sun, Jan 25, 2015 at 12:40 PM, Adam Williamson
> > wrote:
> >> On Sun, 2015-01-25 at 08:49 -0500, Nico Kadel-Garcia wrote:
> >>
> >>> * KVM bridge configuration
> >>
> >> Works fin
On Tue, 2015-01-27 at 14:50 -0500, Nico Kadel-Garcia wrote:
> On Sun, Jan 25, 2015 at 12:40 PM, Adam Williamson
> wrote:
> > On Sun, 2015-01-25 at 08:49 -0500, Nico Kadel-Garcia wrote:
> >
> >> * KVM bridge configuration
> >
> > Works fine in F21+, I'm using NM on both my main desktop/test box and
Am 27.01.2015 um 20:50 schrieb Nico Kadel-Garcia:
On Sun, Jan 25, 2015 at 12:40 PM, Adam Williamson
wrote:
On Sun, 2015-01-25 at 08:49 -0500, Nico Kadel-Garcia wrote:
* KVM bridge configuration
Works fine in F21+, I'm using NM on both my main desktop/test box and
my server VM host.
Test
On Sun, Jan 25, 2015 at 12:40 PM, Adam Williamson
wrote:
> On Sun, 2015-01-25 at 08:49 -0500, Nico Kadel-Garcia wrote:
>
>> * KVM bridge configuration
>
> Works fine in F21+, I'm using NM on both my main desktop/test box and
> my server VM host.
Testing now on a VM, with the Fedora 21 Workstation
Allo 'Allo
>>>>
>>>> I see that some people are trying to "modernize" Fedora.
>>>> But what about RHEL relictum - initscripts, particularly now that we have
>>>> NetworkManager/ModemManager and systemd-networkd,
>>>> when wil
o "modernize" Fedora.
> >> But what about RHEL relictum - initscripts, particularly now that we have
> >> NetworkManager/ModemManager and systemd-networkd,
> >> when will this package "fall off"?
> > We're slowly working on removing things
On Sun, 2015-01-25 at 08:49 -0500, Nico Kadel-Garcia wrote:
> * KVM bridge configuration
Works fine in F21+, I'm using NM on both my main desktop/test box and
my server VM host.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Am 25.01.2015 um 17:09 schrieb poma:
On 25.01.2015 17:02, Joonas Sarajärvi wrote:
also bridge configuration should be possible, but I have not really
tried it with NM.
In NetworkManager it is already settled in F20, and furthermore works in
NetworkD.
Will they still appear someone "who has
On 23.01.2015 16:02, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jan 22, 2015 at 06:44:08PM +0100, poma wrote:
>>
>> Lukáš 'Allo 'Allo
>>
>> I see that some people are trying to "modernize" Fedora.
>> But what about RHEL relictum - initscri
On 25.01.2015 17:02, Joonas Sarajärvi wrote:
> also bridge configuration should be possible, but I have not really
> tried it with NM.
In NetworkManager it is already settled in F20, and furthermore works in
NetworkD.
Will they still appear someone "who has not tried it yet"? :)
--
devel m
2015-01-25 15:49 GMT+02:00 Nico Kadel-Garcia :
>
> And especially because there are at least 3 things that NetworkManager
> does badly, if at all:These are:
>
> * pair bonding
> * KVM bridge configuration
> * VLAN tagging
>
> It tidn't handle them *at all* the last time I ran Fedora on a server,
>
On Fri, Jan 23, 2015 at 11:10 PM, Reindl Harald wrote:
>
>
> Am 23.01.2015 um 19:26 schrieb Dan Winship:
>>
>> On 01/23/2015 10:53 AM, Reindl Harald wrote:
>>>
>>> on servers and static machines you don't need any dynamic network
>>> configuration
>>
>>
>> which is why NM in F22 will have a "confi
Am 23.01.2015 um 19:26 schrieb Dan Winship:
On 01/23/2015 10:53 AM, Reindl Harald wrote:
on servers and static machines you don't need any dynamic network
configuration
which is why NM in F22 will have a "configure-and-quit" mode for such
machines
which is still no valid reason to reconfig
On 01/23/2015 10:53 AM, Reindl Harald wrote:
> on servers and static machines you don't need any dynamic network
> configuration
which is why NM in F22 will have a "configure-and-quit" mode for such
machines
-- Dan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.
Am 22.01.2015 um 18:44 schrieb poma:
Lukáš 'Allo 'Allo
I see that some people are trying to "modernize" Fedora.
But what about RHEL relictum - initscripts, particularly now that we have
NetworkManager/ModemManager and systemd-networkd,
when will this package "fal
On Thu, Jan 22, 2015 at 06:44:08PM +0100, poma wrote:
>
> Lukáš 'Allo 'Allo
>
> I see that some people are trying to "modernize" Fedora.
> But what about RHEL relictum - initscripts, particularly now that we have
> NetworkManager/ModemManager and syste
Lukáš 'Allo 'Allo
I see that some people are trying to "modernize" Fedora.
But what about RHEL relictum - initscripts, particularly now that we have
NetworkManager/ModemManager and systemd-networkd,
when will this package "fall off"?
poma
--
devel mailing list
On Thu, Apr 24, 2014 at 04:38:07PM +0200, Lukáš Nykrýn wrote:
> Network initscript. This will be probably the most controversial part.
> In fedora 21 we will have three different tools for networking
> (initscripts, NetworkManager and systemd-networkd) and all of them
> will be
ctl.conf
> > >
> > >Can we have a joint initscripts + systemd release in a few days to
> > >change ownership of those files?
> >
> > Sounds great. I will removed that from "upstream" and let you know.
>
> Historically, configuration like these (asid
Michael Scherer (m...@zarb.org) said:
> > For LSB, there is an explicit promise that if a vendor does what is
> > specified, the package will be possible to install and will run
> > correctly. We do, of course, have the option to repudiate LSB and
> > explicitly say we don't care for future relea
Lukáš Nykrýn (lnyk...@redhat.com) said:
> >Also the sysctl stuff should be consumed by systemd:
> >/usr/lib/sysctl.d/00-system.conf
> >/etc/sysctl.conf
> >/etc/sysctl.d/99-sysctl.conf
> >
> >Can we have a joint initscripts + systemd release in a few days t
2014-04-26 11:24 GMT+02:00 Michael Scherer :
> Le vendredi 25 avril 2014 à 19:30 +0200, Miloslav Trmač a écrit :
> > For LSB, there is an explicit promise that if a vendor does what is
> > specified, the package will be possible to install and will run
> > correctly. We do, of course, have the op
Am 26.04.2014 11:24, schrieb Michael Scherer:
> Le vendredi 25 avril 2014 à 19:30 +0200, Miloslav Trmač a écrit :
>> And it's not only commercial software; private projects that make no
>> sense to publish (such as a company's web site) are equally affected
>> such changes. Simply spoken, if we ca
Le vendredi 25 avril 2014 à 19:30 +0200, Miloslav Trmač a écrit :
>
> For LSB, there is an explicit promise that if a vendor does what is
> specified, the package will be possible to install and will run
> correctly. We do, of course, have the option to repudiate LSB and
> explicitly say we don'
Am 26.04.2014 02:01, schrieb Jóhann B. Guðmundsson:
> On 04/25/2014 10:53 PM, Miloslav Trmač wrote:
>> I don't think our foundations ever implied that we need or want to be a
>> closed ecosystem restricted to only the
>> repository we produce. The just don't address this.
>
> You must understan
On 04/25/2014 10:53 PM, Miloslav Trmač wrote:
I don't think our foundations ever implied that we need or want to be
a closed ecosystem restricted to only the repository we produce. The
just don't address this.
You must understand we cannot keep back process in the distribution, be
it cl
2014-04-26 0:37 GMT+02:00 "Jóhann B. Guðmundsson" :
> On 04/25/2014 05:30 PM, Miloslav Trmač wrote:
>
>> That's certainly an option but it's not the only one; see the recent
>> "Functional" threads for example.
>>
>
> Sorry I did not want to get involved in yet another attack on our
> foundation,
On 04/25/2014 05:30 PM, Miloslav Trmač wrote:
That's certainly an option but it's not the only one; see the recent
"Functional" threads for example.
Sorry I did not want to get involved in yet another attack on our
foundation,
Last time I checked Fedora was not LSB certified nor compliant s
Am 25.04.2014 19:30, schrieb Miloslav Trmač:
> 2014-04-25 12:40 GMT+02:00 "Jóhann B. Guðmundsson":
> Which is what we care about we cannot hold back progress in the
> distribution based on someone, someplace,
> somewhere might be using legacy cruff.
>
> It's better for everybody they
2014-04-25 12:40 GMT+02:00 "Jóhann B. Guðmundsson" :
> On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
>
>>
>> Only those that are maintained directly inside Fedora.
>>
>
> Which is what we care about we cannot hold back progress in the
> distribution based on someone, someplace, somewhere might be
On Fri, Apr 25, 2014 at 01:30:00PM +0200, Lukáš Nykrýn wrote:
> Dne 25.4.2014 13:24, Reindl Harald napsal(a):
> >
> >
> >Am 25.04.2014 13:12, schrieb Lukáš Nykrýn:
> >>Dne 25.4.2014 12:50, Reindl Harald napsal(a):
> >>>Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
> On 04/24/2014 04:30 PM
Dne 25.4.2014 13:24, Reindl Harald napsal(a):
Am 25.04.2014 13:12, schrieb Lukáš Nykrýn:
Dne 25.4.2014 12:50, Reindl Harald napsal(a):
Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
Only those that are maintained directly inside Fedora.
Am 25.04.2014 13:12, schrieb Lukáš Nykrýn:
> Dne 25.4.2014 12:50, Reindl Harald napsal(a):
>> Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
>>> On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
Only those that are maintained directly inside Fedora.
>>>
>>> Which is what we care about
Dne 25.4.2014 12:50, Reindl Harald napsal(a):
Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
Only those that are maintained directly inside Fedora.
Which is what we care about we cannot hold back progress in the
distribution based on someo
Am 25.04.2014 12:58, schrieb Jóhann B. Guðmundsson:
> On 04/25/2014 10:50 AM, Reindl Harald wrote:
>>
>> Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
>>> On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
Only those that are maintained directly inside Fedora.
>>> Which is what we care about
Dne 25.4.2014 02:19, Zbigniew Jędrzejewski-Szmek napsal(a):
On Thu, Apr 24, 2014 at 04:38:07PM +0200, Lukáš Nykrýn wrote:
Hi,
for the F22 I am planning some bigger changes regarding initscripts
and I would like to ask for comments.
Initscripts package was in the past a crucial part of the
On 04/25/2014 10:50 AM, Reindl Harald wrote:
Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
Only those that are maintained directly inside Fedora.
Which is what we care about we cannot hold back progress in the
distribution based on someone,
Am 25.04.2014 12:40, schrieb Jóhann B. Guðmundsson:
> On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
>>
>> Only those that are maintained directly inside Fedora.
>
> Which is what we care about we cannot hold back progress in the
> distribution based on someone, someplace, somewhere might be usi
On 04/24/2014 04:30 PM, Miloslav Trmač wrote:
Only those that are maintained directly inside Fedora.
Which is what we care about we cannot hold back progress in the
distribution based on someone, someplace, somewhere might be using
legacy cruff.
It's better for everybody they themselves i
On 04/25/2014 12:19 AM, Zbigniew Jędrzejewski-Szmek wrote:
I too think that this split is a lot of work for small gain. Working
out the full dependencies set of what needs what is going to take a
while, but I think it would be better to simply shrink the package to
nothing in small steps.
I al
On Thu, Apr 24, 2014 at 04:38:07PM +0200, Lukáš Nykrýn wrote:
> Hi,
> for the F22 I am planning some bigger changes regarding initscripts
> and I would like to ask for comments.
>
> Initscripts package was in the past a crucial part of the system.
> They basicaly set up whole
2014-04-24 18:13 GMT+02:00 Casey Dahlin :
> On Thu, Apr 24, 2014 at 05:55:29PM +0200, Miloslav Trmač wrote:
> > Hello,
> > 2014-04-24 16:38 GMT+02:00 Lukáš Nykrýn :
> >
> > > We must keep initscripts support, but I can imagine a setup where every
> > > se
On Thu, Apr 24, 2014 at 05:55:29PM +0200, Miloslav Trmač wrote:
> Hello,
> 2014-04-24 16:38 GMT+02:00 Lukáš Nykrýn :
>
> > We must keep initscripts support, but I can imagine a setup where every
> > service uses a systemd unit, so this part does not have to be installed by
&
Hello,
2014-04-24 16:38 GMT+02:00 Lukáš Nykrýn :
> We must keep initscripts support, but I can imagine a setup where every
> service uses a systemd unit, so this part does not have to be installed by
> default, but could be pulled in as a dependency.
>
Are you sure? If you take an
Hi,
for the F22 I am planning some bigger changes regarding initscripts and
I would like to ask for comments.
Initscripts package was in the past a crucial part of the system. They
basicaly set up whole system during the boot. Currently initscripts
package contains "support" for i
Upstart has been orphaned in rawhide since 2012-04-26.
I would like to drop support for it from the initscripts package proper, but
if someone is willing to maintain upstart, I'd be glad to give you the boot
infrastrucutre bits therein in whatever form you'd like to maintain along
wi
Lennart Poettering (mzerq...@0pointer.de) said:
> > Fixed in git, thanks for the report.
>
> BTW: A nice way to make activation of services conditional based on
> existance of a file is the relatively new ConditionPathExists= setting
> in [Unit]. If the file listed there doesn't exist, then the u
On Fri, 22.10.10 13:21, Bill Nottingham (nott...@redhat.com) wrote:
>
> Yanko Kaneti (yan...@declera.com) said:
> > Which seems to be caused by a "missing" /etc/crypttab
> > I've never had this file apparently.
> > # touch /etc/crypttab
> > and the systems seem to boot as exected
>
> Fixed in g
On 10/21/2010 04:43 PM, Bill Nottingham wrote:
> I've set up a repo on r.fp.org:
>http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>
> This repo includes updated initscripts and associated packages
> that test the conversion of various boot-time actions t
Yanko Kaneti (yan...@declera.com) said:
> Which seems to be caused by a "missing" /etc/crypttab
> I've never had this file apparently.
> # touch /etc/crypttab
> and the systems seem to boot as exected
Fixed in git, thanks for the report.
Bill
--
devel mailing list
devel@lists.fedoraproject.org
rg:
>>> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>>>
>>> This repo includes updated initscripts and associated packages
>>> that test the conversion of various boot-time actions to systemd
>>> services. (Essentially, rc.sysinit is dea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/21/2010 12:47 PM, Michał Piotrowski wrote:
> Hi,
>
> 2010/10/21 Bill Nottingham :
>> I've set up a repo on r.fp.org:
>> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>>
>> This
On Fri, 2010-10-22 at 09:03 +0300, Yanko Kaneti wrote:
..
> which seems to be caused by
> fedora-init-crypto-1.service - Initialize encrypted storage
> Loaded: loaded (/lib/systemd/system/fedora-init-crypto-1.service)
> Active: failed since [Fri, 22 Oct 2010 08:57:39 +0300; 1min 24s
> > http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
> > >
> > > Didn't automount anything from fstab other than /, not even /home. Even
> > > when I logged in on the console with a user that has a home directory
> > > there. Manuall
Bill Nottingham (nott...@redhat.com) said:
> Yanko Kaneti (yan...@declera.com) said:
> > On Thu, 2010-10-21 at 10:43 -0400, Bill Nottingham wrote:
> > > I've set up a repo on r.fp.org:
> > > http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
&g
Yanko Kaneti (yan...@declera.com) said:
> On Thu, 2010-10-21 at 10:43 -0400, Bill Nottingham wrote:
> > I've set up a repo on r.fp.org:
> > http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>
> Didn't automount anything from fstab other than /
W dniu 21 października 2010 20:50 użytkownik Michał Piotrowski
napisał:
> 2010/10/21 Bill Nottingham :
>> I've set up a repo on r.fp.org:
>> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>>
>> This repo includes updated initscripts and asso
2010/10/21 Bill Nottingham :
> I've set up a repo on r.fp.org:
> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>
> This repo includes updated initscripts and associated packages
> that test the conversion of various boot-time actions to systemd
>
On Thu, Oct 21, 2010 at 9:43 AM, Bill Nottingham wrote:
>
> This repo includes updated initscripts and associated packages
> that test the conversion of various boot-time actions to systemd
> services. (Essentially, rc.sysinit is dead.) Before putting this
> in rawhide, we want to
2010/10/21 drago01 :
>
> Any SELINUX avcs?
indeed there is an AVC (I forgot about SELinux :) - I do not use it
and I forgot to turn it off after installation)
type=AVC msg=audit(1287683664.377:70): avc: denied { getattr } for
pid=1679 comm="dhclient" path="/etc/pki/tls/openssl.cnf" dev=sda2
ino
2010/10/21 Michał Piotrowski :
> Hi,
>
> 2010/10/21 Bill Nottingham :
>> I've set up a repo on r.fp.org:
>> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>>
>> This repo includes updated initscripts and associated packages
>> t
Hi,
2010/10/21 Bill Nottingham :
> I've set up a repo on r.fp.org:
> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
>
> This repo includes updated initscripts and associated packages
> that test the conversion of various boot-time actions to systemd
>
On Thu, 2010-10-21 at 10:43 -0400, Bill Nottingham wrote:
> I've set up a repo on r.fp.org:
> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
Didn't automount anything from fstab other than /, not even /home. Even
when I logged in on the console with a user
On Thu, Oct 21, 2010 at 10:43:33AM -0400, Bill Nottingham wrote:
> I've set up a repo on r.fp.org:
> http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
I'll try it this afternoon.
--
Matthew Miller
Senior Systems Architect -- Instructional & Research Comput
I've set up a repo on r.fp.org:
http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
This repo includes updated initscripts and associated packages
that test the conversion of various boot-time actions to systemd
services. (Essentially, rc.sysinit is dead.) Before putting th
On Wed, 9 Jun 2010, Michel Alexandre Salim wrote:
>> $ rpm -q NetworkManager initscripts
>> NetworkManager-0.8.0-0.4.git20100211.fc13.x86_64
>> initscripts-9.11-1.fc13.x86_64
>>
>> $ sudo yum --disablerepo=updates update initscripts NetworkManager
run:
sudo
r F13 from a few days after initscripts was build that, for
>>> some reason, was never pushed as an update:
>>>
>>> http://koji.fedoraproject.org/koji/buildinfo?buildID=172856
>>>
>>> Are these two updates supposed to go together? I downloaded all
On Tue, 2010-06-08 at 00:42 +0200, Michel Alexandre Salim wrote:
> On Tue, Jun 8, 2010 at 12:31 AM, Michel Alexandre Salim
> wrote:
> > Here are the x86_64 package versions:
> >
> > $ rpm -q NetworkManager initscripts
> > NetworkManager-0.8.0-0.4.git20100211.fc13
On Mon, Jun 7, 2010 at 5:31 PM, Bill Nottingham wrote:
> Michel Alexandre Salim (michael.silva...@gmail.com) said:
>> The update conflicts with NetworkManager; there is a NetworkManager
>> build for F13 from a few days after initscripts was build that, for
>> some reason, w
On Tue, Jun 8, 2010 at 12:31 AM, Michel Alexandre Salim
wrote:
> Here are the x86_64 package versions:
>
> $ rpm -q NetworkManager initscripts
> NetworkManager-0.8.0-0.4.git20100211.fc13.x86_64
> initscripts-9.11-1.fc13.x86_64
>
> and on the netbook:
>
> $ rpm -q
Michel Alexandre Salim (michael.silva...@gmail.com) said:
> The update conflicts with NetworkManager; there is a NetworkManager
> build for F13 from a few days after initscripts was build that, for
> some reason, was never pushed as an update:
>
> http://koji.fedoraproject.org
Le mercredi 02 juin 2010 à 18:37 +0200, Lennart Poettering a écrit :
> Handling this with systemd is very easy: you can just drop in a file in
> /etc/init.d/foo *AND* /etc/systemd/system/foo.service from the same
> package. And then, if something that is not systemd is booted it will
> only see t
The update conflicts with NetworkManager; there is a NetworkManager
build for F13 from a few days after initscripts was build that, for
some reason, was never pushed as an update:
http://koji.fedoraproject.org/koji/buildinfo?buildID=172856
Are these two updates supposed to go together? I
On Fri, Jun 04, 2010 at 06:52:51PM +0200, Kevin Kofler wrote:
> Patrice Dumas wrote:
> > I think that this would be a huge mistake. Enrico is a very talented
> > packagers he generally is ahead of his time. I was myself sometimes
> > annoyed by the peculiarities of his packages, but he always compl
Patrice Dumas wrote:
> I think that this would be a huge mistake. Enrico is a very talented
> packagers he generally is ahead of his time. I was myself sometimes
> annoyed by the peculiarities of his packages, but he always comply to
> guidelines.
No he doesn't. For example, SVN revision tags in V
On Wed, Jun 02, 2010 at 09:13:02PM +0800, Chen Lei wrote:
> Fedora have upstart as the /sbin/init daemon for a long time, but we
> still use the old 'SysVinit' scripts from /etc/rc.d/init.d and fedora
> packaging guideline have nothing about upstart.
>
> Is it right for the maintainer to provide
On Fri, Jun 04, 2010 at 04:43:58AM +0200, Kevin Kofler wrote:
> Chen Lei wrote:
> > I found the maintainer violates fedora package/naming guideline many
> > times, we need a people to persuade him to obey those guideline.
>
> IMHO we need to unsponsor him and orphan his packages. There are way too
1 - 100 of 128 matches
Mail list logo
