On Thu, Jul 15, 2010 at 03:30:41AM +0200, Lennart Poettering wrote:
> I have uploaded preliminary versions of the unit files I put together
> for the various services of our default install. I think they give an
> indication how simple these files actually are:
>
> http://0pointer.de/public/syste
On Wed, Jul 14, 2010 at 11:42 PM, Kevin Fenzi wrote:
> On Wed, 14 Jul 2010 23:30:44 +0200
> Lennart Poettering wrote:
>
>> Well, if this is all this is about then I wonder why this is there
>> anyway? If no gdm is installed, then runlevel 5 and 3 should be
>> identical anyway, so what's the point
On Wed, 2010-07-14 at 23:19 +0200, Lennart Poettering wrote:
> On Wed, 14.07.10 17:01, James Antill (ja...@fedoraproject.org) wrote:
> > But your runlevel is not a service configuration, so I see no reason
> > why you couldn't say "if there is an 'id:blah:' line in inittab that's
> > authoritative
Is there an expert related to GtkIconTheme, who could tell whether
http://bugzilla.redhat.com/614633
is a bug in the application and not in GtkIconTheme? More comments on
the symptoms:
http://bugzilla.redhat.com/530920#c3
http://bugzilla.redhat.com/530920#c8
In particular, icon references
On Wed, 14 Jul 2010 20:42:57 -0400
Orcan Ogetbil wrote:
> I have got news. The other day, my ACL request (that I made last
> year!) for F-10 was approved by ixs. 1 minute later, it was set back
> to Awaiting Review.
>
> Anyone have any idea of what's going on?
Not sure. Ixs was active the othe
On Thu, 2010-07-15 at 02:37 +0200, Lennart Poettering wrote:
> It's actually right the first paragraph after the list of options. Not
> sure how I can make this any more obvious to find.
>
> http://0pointer.de/public/systemd-man/systemd.html
No-one reads man pages any more, it's all about the wi
When: Friday, 2010-07-16 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Friday is the
FIRST blocker bug review meeting for the Fedora 14 Alpha.
Here are the current bugs listed as blocking the Alpha release. We'll be
Lennart Poettering (mzerq...@0pointer.de) said:
> I have uploaded preliminary versions of the unit files I put together
> for the various services of our default install. I think they give an
> indication how simple these files actually are:
>
> http://0pointer.de/public/systemd-units/
>
> Pleas
Stepping back, this is the situation I started with that led me to these
observations:
Incoming knowledge:
- Upstart and init experience
- A reading of the initial 'why I did systemd, and what it intends to
support' document
Testing methodology:
- Install it
- Boot it
- Poke around
Is this the
heya,
I have uploaded preliminary versions of the unit files I put together
for the various services of our default install. I think they give an
indication how simple these files actually are:
http://0pointer.de/public/systemd-units/
Please have a look and if you have any questions just ask!
E
On Wed, 14.07.10 20:19, Lennart Poettering (mzerq...@0pointer.de) wrote:
> Hmm, if you would be willing to do that, then it would be great to find
> somebody who fixed the .specs and makes a list of packages whose selinux
> policy needs fixing. Anyone? Rahul you should vague interest on IRC?
One
On Mon, Jul 5, 2010 at 7:05 PM, Orcan Ogetbil wrote:
> On Mon, Jul 5, 2010 at 6:17 PM, Michel Alexandre Salim wrote:
>> Hi all,
>>
>> I'm initiating a fast track procedure for libsndfile -- a security bug
>> has been reported for over a year, and there has been no response from
>> maintainer
>
> We
On Wed, 14.07.10 19:42, Matthias Clasen (mcla...@redhat.com) wrote:
>
> On Thu, 2010-07-15 at 01:29 +0200, Lennart Poettering wrote:
>
> [long comparsion elided...]
>
> > Or to explain this with a table, showing you what verbs most people
> > would probably use for four kinds (of the ten) of ob
On Wed, 14.07.10 15:55, Cleaver, Japheth (jclea...@soe.sony.com) wrote:
> 2) How will systemd handle telinit/runlevel cases with the existing
> runlevel? Is there a way to verify (from a logical init/subsys
> perspective only) that what should be running in your runlevel is?
Not sure I fully grok
On Thu, 2010-07-15 at 01:29 +0200, Lennart Poettering wrote:
[long comparsion elided...]
> Or to explain this with a table, showing you what verbs most people
> would probably use for four kinds (of the ten) of objects that are
> managed by systemd:
>
> Services: Started | Stopped
> Socke
Author: spot
Update of /cvs/pkgs/rpms/perl-Inline-Files/devel
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv30200/devel
Modified Files:
.cvsignore perl-Inline-Files.spec sources
Log Message:
0.63
Index: .cvsignore
===
Author: spot
Update of /cvs/pkgs/rpms/perl-Inline-Files/EL-6
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv30200/EL-6
Modified Files:
perl-Inline-Files.spec sources
Log Message:
0.63
Index: perl-Inline-Files.spec
A file has been added to the lookaside cache for perl-Inline-Files:
460ed656cb55cba677ae774319958fc2 Inline-Files-0.63.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mai
On Wed, 14.07.10 18:00, Bill Nottingham (nott...@redhat.com) wrote:
>
> Lennart Poettering (mzerq...@0pointer.de) said:
> > So, here's my call for help, in order to make this all a big success:
>
> So, I've actually played with this now, instead of just asking questions
> and operating on knowl
Could someone with enough karma rebuild krb5-auth-dialog 0.16 for F-13
(this is in relation to bug #597669). The 0.15 is leaking memory like
there is no tomorrow and I'm not getting much traction from the assignee
of the bug...
TIA,
--
Bojan
--
devel mailing list
devel@lists.fedoraproject.org
h
I just updated libdap to 3.10.2 in rawhide. Apparently this versioin dropped
a bunch of stuff but didn't bump the soversion. Bug is here:
https://bugzilla.redhat.com/show_bug.cgi?id=614657
I've pinged the libdap folks to see what's up.
--
Orion Poplawski
Technical Manager
> -Original Message-
> From: devel-boun...@lists.fedoraproject.org On Behalf
> Of Lennart Poettering
> Sent: Wednesday, July 14, 2010 8:43 AM
> To: devel@lists.fedoraproject.org
> Subject: Re: [HEADS-UP] systemd for F14 - the next steps
>
>
> 2) You parse some configuration files or simil
On Thu, 15.07.10 00:51, Kalev Lember (ka...@smartlink.ee) wrote:
> On 07/14/2010 09:13 PM, Lennart Poettering wrote:
> > /etc/systemd/system/default.target → /lib/systemd/system/graphical.target
> >
> > to boot into the graphical stuff by default. This is the default as we
> > package it.
>
> Let
Lennart Poettering (mzerq...@0pointer.de) said:
> So, here's my call for help, in order to make this all a big success:
So, I've actually played with this now, instead of just asking questions
and operating on knowledge from the initial announcement.
I must admit... at first glance, I'm not the
On Wed, 14.07.10 15:42, Kevin Fenzi (ke...@scrye.com) wrote:
> On Wed, 14 Jul 2010 23:30:44 +0200
> Lennart Poettering wrote:
>
> > Well, if this is all this is about then I wonder why this is there
> > anyway? If no gdm is installed, then runlevel 5 and 3 should be
> > identical anyway, so what
On 07/14/2010 09:13 PM, Lennart Poettering wrote:
> /etc/systemd/system/default.target → /lib/systemd/system/graphical.target
>
> to boot into the graphical stuff by default. This is the default as we
> package it.
Lets say the admin (or Anaconda) has modified the default.target
symlink. What hap
On Wed, 2010-07-14 at 15:42 -0600, Kevin Fenzi wrote:
> Perhaps someone could put together a wiki page for lazy sysadmins with
> a Q&A? ie, I used to do this in upstart/sysvinit, how do I do it with
> systemd?
Jóhann Guðmundsson (viking_ice) has been working on something along
these lines:
http
On Wed, 14 Jul 2010 23:30:44 +0200
Lennart Poettering wrote:
> Well, if this is all this is about then I wonder why this is there
> anyway? If no gdm is installed, then runlevel 5 and 3 should be
> identical anyway, so what's the point of fixing the default runlevel
> there?
Because you may have
Dear maintainers of twisted-dependent packages,
a while ago I asked for an update of twisted to 10.0.0. I got in contact
with the maintainer, and the problem is the huge dependency list. Thomas
(the maintainer) prefers to make sure that everything works before the
update is pushed, instead of t
On Wed, 14.07.10 17:23, Chris Lumens (clum...@redhat.com) wrote:
>
> > Hmm, I wasn't aware that Anaconda even asks a question about the
> > runlevel. Given that I am too lazy to try this out now, what exactly is
> > this question? i.e. does it ask "Are you installing a server or a
> > deskop?" or
On Wed, 14.07.10 14:22, Adam Williamson (awill...@redhat.com) wrote:
>
> On Wed, 2010-07-14 at 23:08 +0200, Lennart Poettering wrote:
>
> > > Did you see the post a while back from someone who tried systemd and
> > > found it wouldn't boot their system? Just curious. I will try this
> > > myself
On Wed, 2010-07-14 at 23:08 +0200, Lennart Poettering wrote:
> > Did you see the post a while back from someone who tried systemd and
> > found it wouldn't boot their system? Just curious. I will try this
> > myself later today.
>
> I think I have responded to all mails and bugzilla bugs. Or have
On Wed, 14.07.10 16:36, Horst H. von Brand (vonbr...@inf.utfsm.cl) wrote:
>
> Lennart Poettering wrote:
> > as many of you probably know systemd got accepted as feature for F-14 by
> > FESCO a few weeks back.
>
> Perhaps I'm being unusually dense, but...
>
> How do I go ahead and switch over t
> Hmm, I wasn't aware that Anaconda even asks a question about the
> runlevel. Given that I am too lazy to try this out now, what exactly is
> this question? i.e. does it ask "Are you installing a server or a
> deskop?" or what does it ask?
The default runlevel is inferred based upon packages inst
On Wed, 14.07.10 17:01, James Antill (ja...@fedoraproject.org) wrote:
>
> On Wed, 2010-07-14 at 22:38 +0200, Lennart Poettering wrote:
> > On Wed, 14.07.10 16:03, James Antill (ja...@fedoraproject.org) wrote:
> >
> > > > > Or you could just parse inittab and notice when runlevel 3 was
> > > > >
On Wed, 14.07.10 17:00, Jeff Garzik (jgar...@pobox.com) wrote:
> > I would have prefered if you would have taken up this fight with the
> > Upstart people when it was added to Fedora. We are just finishing the
> > work Upstart began in this area, and I am not really willing to fight
> > now a batt
On Wed, 14.07.10 16:34, Bill Nottingham (nott...@redhat.com) wrote:
>
> Lennart Poettering (mzerq...@0pointer.de) said:
> > > The issue is that this is a behavior change (from both sysvinit and
> > > upstart)
> > > that will need code to be handled properly in other packages. Anaconda,
> > > at
On Wed, 14.07.10 13:30, Adam Williamson (awill...@redhat.com) wrote:
>
> On Wed, 2010-07-14 at 22:26 +0200, Lennart Poettering wrote:
> > On Wed, 14.07.10 13:16, Adam Williamson (awill...@redhat.com) wrote:
> >
> > >
> > > On Wed, 2010-07-14 at 22:09 +0200, Lennart Poettering wrote:
> > >
> >
On Wed, Jul 14, 2010 at 2:13 PM, Lennart Poettering
wrote:
> On Wed, 14.07.10 14:07, Jeffrey Ollie (j...@ocjtech.us) wrote:
>
>>
>> I've been trying to test systemd on my dev box but without success so
>> far. My system boots up and I get the usual GDM login screen and VTs
>> but I can't login.
On Wed, 2010-07-14 at 22:38 +0200, Lennart Poettering wrote:
> On Wed, 14.07.10 16:03, James Antill (ja...@fedoraproject.org) wrote:
>
> > > > Or you could just parse inittab and notice when runlevel 3 was listed.
> > > > Keeps everything nice and compatible, including existing manuals and
> > >
On 07/14/2010 03:33 PM, Lennart Poettering wrote:
> On Wed, 14.07.10 15:18, Jeff Garzik (jgar...@pobox.com) wrote:
>
>>
>> On 07/14/2010 03:08 PM, Lennart Poettering wrote:
>>> I'd also argue that simply changing a symlink in /etc/systemd/system is
>>> a lot easier to understand and discoverable th
On Wed, 14.07.10 16:25, Horst H. von Brand (vonbr...@inf.utfsm.cl) wrote:
>
> Lennart Poettering wrote:
> > Heya,
> >
> > as many of you probably know systemd got accepted as feature for F-14 by
> > FESCO a few weeks back.
>
> Congratulations.
>
> Just a question: Why isn't it /sbin/systemd,
On Wed, 14.07.10 16:03, James Antill (ja...@fedoraproject.org) wrote:
> > > Or you could just parse inittab and notice when runlevel 3 was listed.
> > > Keeps everything nice and compatible, including existing manuals and
> > > books, and sysadmin knowledge.
> >
> > Is this really such a biggie
Lennart Poettering wrote:
> as many of you probably know systemd got accepted as feature for F-14 by
> FESCO a few weeks back.
Perhaps I'm being unusually dense, but...
How do I go ahead and switch over to check this out? Spell it out for a
somewhat moronic rawhide user...
How do I get back if t
Lennart Poettering (mzerq...@0pointer.de) said:
> > The issue is that this is a behavior change (from both sysvinit and upstart)
> > that will need code to be handled properly in other packages. Anaconda,
> > at least, will need to be patched to set the default bootup target
> > differently depend
On Wed, 2010-07-14 at 22:26 +0200, Lennart Poettering wrote:
> On Wed, 14.07.10 13:16, Adam Williamson (awill...@redhat.com) wrote:
>
> >
> > On Wed, 2010-07-14 at 22:09 +0200, Lennart Poettering wrote:
> >
> > > > 6. plymouth interactions
> > >
> > > There's https://bugzilla.redhat.com/show_bu
On Wed, 14.07.10 13:16, Adam Williamson (awill...@redhat.com) wrote:
>
> On Wed, 2010-07-14 at 22:09 +0200, Lennart Poettering wrote:
>
> > > 6. plymouth interactions
> >
> > There's https://bugzilla.redhat.com/show_bug.cgi?id=614245 which
> > currently is an issue when using plymouth in conjun
Lennart Poettering wrote:
> Heya,
>
> as many of you probably know systemd got accepted as feature for F-14 by
> FESCO a few weeks back.
Congratulations.
Just a question: Why isn't it /sbin/systemd, /sbin/systemctl,
/sbin/systemd-notify, /usr/sbin/systemd-cgls? This definitely isn't
"normal-use
On Wed, 14.07.10 14:28, Bill Nottingham (nott...@redhat.com) wrote:
> > And the admin could even define additional targets, to achieve different
> > system profiles he can boot into or switch forth and back to and from,
> > and give it arbitrary names, and even pull in any of the targets we ship
>
On Wed, 2010-07-14 at 22:09 +0200, Lennart Poettering wrote:
> > 6. plymouth interactions
>
> There's https://bugzilla.redhat.com/show_bug.cgi?id=614245 which
> currently is an issue when using plymouth in conjunction with
> systemd. Ray promised to look into this every day now ;-)
Plymouth is t
On Wed, 14.07.10 14:32, Bill Nottingham (nott...@redhat.com) wrote:
> 1. normal gettys
> 2. single-user mode
> 3. ctrl-alt-delete
> 4. prefdm starting
These four things should be covered for alraedy.
> 5. automatically starting gettys on serial consoles
This is currently not dealt with, I have
On Wed, 2010-07-14 at 21:08 +0200, Lennart Poettering wrote:
> On Wed, 14.07.10 14:24, Jeff Garzik (jgar...@pobox.com) wrote:
>
> > > /etc/systemd/system. You could do this:
> > >
> > > /etc/systemd/system/default.target → /lib/systemd/system/multi-user.target
> > >
> > > to avoid the graphical UI
On Wed, Jul 14, 2010 at 9:47 PM, Lennart Poettering
wrote:
> On Wed, 14.07.10 12:34, Adam Williamson (awill...@redhat.com) wrote:
>
>> > Ok. You got me on this one. Systemd does actually not parse the
>> > inittab. That cruft looked a bit too ugly and clumsy and old for us to
>> > support.
>>
>> V
On Wed, 14.07.10 12:34, Adam Williamson (awill...@redhat.com) wrote:
> > Ok. You got me on this one. Systemd does actually not parse the
> > inittab. That cruft looked a bit too ugly and clumsy and old for us to
> > support.
>
> Vaguely a propos - does systemd execute /etc/rc.local ?
Yes, there
On Wed, 14.07.10 15:23, Daniel J Walsh (dwa...@redhat.com) wrote:
> > And stuff like this. And of course this is just cleaner this way, since
> > the files in /var/run and /var/lock are runtime objects that are used
> > for synchronization and establishment of communication channels
> > only. They
On Wed, 14.07.10 15:26, Bill Nottingham (nott...@redhat.com) wrote:
>
> Lennart Poettering (mzerq...@0pointer.de) said:
> > > Would alternatives work here ?
> >
> > Yes, the alternatives system would probably work. However, I think there
> > are things where it is a good idea to use and where i
Adam Williamson (awill...@redhat.com) said:
> > > Does it pull this from inittab if there's no other configuration for
> > > this?
> >
> > Ok. You got me on this one. Systemd does actually not parse the
> > inittab. That cruft looked a bit too ugly and clumsy and old for us to
> > support.
>
> V
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=427049
Andreas Thienemann changed:
What|Removed |Added
On Wed, 2010-07-14 at 20:13 +0200, Lennart Poettering wrote:
> On Wed, 14.07.10 13:44, Bill Nottingham (nott...@redhat.com) wrote:
>
> >
> > Lennart Poettering (mzerq...@0pointer.de) said:
> > > There's also the systemd.unit= kernel command line option which you may
> > > use to boot into differen
On Wed, 14.07.10 15:18, Jeff Garzik (jgar...@pobox.com) wrote:
>
> On 07/14/2010 03:08 PM, Lennart Poettering wrote:
> > I'd also argue that simply changing a symlink in /etc/systemd/system is
> > a lot easier to understand and discoverable than having to edit old and
> > crufty /etc/inittab whic
Lennart Poettering (mzerq...@0pointer.de) said:
> > Would alternatives work here ?
>
> Yes, the alternatives system would probably work. However, I think there
> are things where it is a good idea to use and where it isn't. And I
> think this case is one of the latter. If we go down the switchab
On 07/14/2010 03:20 PM, Lennart Poettering wrote:
> On Wed, 14.07.10 14:24, Daniel J Walsh (dwa...@redhat.com) wrote:
>
myapp_t creating a directory in var_run_t will be labeled
myapp_var_run_t. I would just need to go through all the policy that
uses var_run_t directories and make
On Wed, 14.07.10 14:24, Daniel J Walsh (dwa...@redhat.com) wrote:
> >> myapp_t creating a directory in var_run_t will be labeled
> >> myapp_var_run_t. I would just need to go through all the policy that
> >> uses var_run_t directories and make sure it has this rule.
> >
> > Hmm, if you would be
On 07/14/2010 03:08 PM, Lennart Poettering wrote:
> I'd also argue that simply changing a symlink in /etc/systemd/system is
> a lot easier to understand and discoverable than having to edit old and
> crufty /etc/inittab which to fully understand you really must have a
> historical Unix background f
On Wed, 14.07.10 14:59, Matthias Clasen (mcla...@redhat.com) wrote:
>
> On Wed, 2010-07-14 at 20:48 +0200, Lennart Poettering wrote:
> > On Wed, 14.07.10 13:45, Matthias Clasen (mcla...@redhat.com) wrote:
> >
> > > > To achieve what you want to do upstart would need to support something
> > > >
On Wed, 14.07.10 14:07, Jeffrey Ollie (j...@ocjtech.us) wrote:
>
> I've been trying to test systemd on my dev box but without success so
> far. My system boots up and I get the usual GDM login screen and VTs
> but I can't login. SSH fails as well. SSH gives me "Unable to get
> valid context fo
On Wed, 14.07.10 20:25, drago01 (drag...@gmail.com) wrote:
> >> Or you could do this:
> >>
> >> /etc/systemd/system/default.target → /lib/systemd/system/graphical.target
> >>
> >> to boot into the graphical stuff by default. This is the default as we
> >> package it.
> >
> > Or you could just pars
On Wed, 14.07.10 14:24, Jeff Garzik (jgar...@pobox.com) wrote:
> > /etc/systemd/system. You could do this:
> >
> > /etc/systemd/system/default.target → /lib/systemd/system/multi-user.target
> >
> > to avoid the graphical UI, and boot into the text console only
> > (i.e. much like the old runlevel
I've been trying to test systemd on my dev box but without success so
far. My system boots up and I get the usual GDM login screen and VTs
but I can't login. SSH fails as well. SSH gives me "Unable to get
valid context for jcollie" shows me the last login date and closes the
connection. I think
On 07/14/2010 02:54 PM, Lennart Poettering wrote:
> On Wed, 14.07.10 13:31, Chris Adams (cmad...@hiwaay.net) wrote:
>
>>
>> Once upon a time, Lennart Poettering said:
>>> Yes this would work, though in a different syntax:
>>>
>>> ExecStartPre=-/bin/mkdir -p /var/run/foo ; -/sbin/restorecon /var
On Wed, 2010-07-14 at 20:48 +0200, Lennart Poettering wrote:
> On Wed, 14.07.10 13:45, Matthias Clasen (mcla...@redhat.com) wrote:
>
> > > To achieve what you want to do upstart would need to support something
> > > similar: make it possible to install it without insisting on the
> > > /sbin/init
On Wed, 14.07.10 13:31, Chris Adams (cmad...@hiwaay.net) wrote:
>
> Once upon a time, Lennart Poettering said:
> > Yes this would work, though in a different syntax:
> >
> > ExecStartPre=-/bin/mkdir -p /var/run/foo ; -/sbin/restorecon /var/run/foo
> >
> > (The initial - btw means that the ex
On Wed, 14.07.10 13:45, Matthias Clasen (mcla...@redhat.com) wrote:
> > To achieve what you want to do upstart would need to support something
> > similar: make it possible to install it without insisting on the
> > /sbin/init file name and related ones, and then add in those names via
> > symlink
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now that people are testing it, the tickets are rolling in for various
issues. While I could fix them all, there is an opportunity for folks
to help out here and pick off some of the bugs.
https://fedorahosted.org/fedora-packager/query?status=new&sta
Once upon a time, Lennart Poettering said:
> Yes this would work, though in a different syntax:
>
> ExecStartPre=-/bin/mkdir -p /var/run/foo ; -/sbin/restorecon /var/run/foo
>
> (The initial - btw means that the exit code of the command is ignored)
Why would you ignore the exit code? If you
Lennart Poettering (mzerq...@0pointer.de) said:
> Well, I am not sure what you mean by 95% coverage case. Minus bugs we
> should have 99.9% compatibility with SysV init right now. And those bugs
> we don't find if people don't use things. Feature-wise systemd is
> definitely "complete", bug-wise n
Lennart Poettering (mzerq...@0pointer.de) said:
> > Does it pull this from inittab if there's no other configuration for
> > this?
>
> Ok. You got me on this one. Systemd does actually not parse the
> inittab. That cruft looked a bit too ugly and clumsy and old for us to
> support.
>
> However,
On Wed, Jul 14, 2010 at 8:24 PM, Jeff Garzik wrote:
> On 07/14/2010 02:13 PM, Lennart Poettering wrote:
>> On Wed, 14.07.10 13:44, Bill Nottingham (nott...@redhat.com) wrote:
>>
>>>
>>> Lennart Poettering (mzerq...@0pointer.de) said:
There's also the systemd.unit= kernel command line option w
On 07/14/2010 02:13 PM, Lennart Poettering wrote:
> On Wed, 14.07.10 13:44, Bill Nottingham (nott...@redhat.com) wrote:
>
>>
>> Lennart Poettering (mzerq...@0pointer.de) said:
>>> There's also the systemd.unit= kernel command line option which you may
>>> use to boot into different targets. See the
On 07/14/2010 02:19 PM, Lennart Poettering wrote:
> On Wed, 14.07.10 13:47, Daniel J Walsh (dwa...@redhat.com) wrote:
>
>>> Hardcoding foo_t is bad if they ever switch policy (MLS, etc.). But
>>> it is an option.
>>>
>>> Bill
>> Not sure this works, but this would be preferable.
>> ExecStartPre=-"
On Wed, 14.07.10 13:47, Daniel J Walsh (dwa...@redhat.com) wrote:
> > Hardcoding foo_t is bad if they ever switch policy (MLS, etc.). But
> > it is an option.
> >
> > Bill
> Not sure this works, but this would be preferable.
> ExecStartPre=-"/bin/mkdir -p /var/run/foo; restorecon /var/run/foo"
Y
On Wed, 14.07.10 13:44, Bill Nottingham (nott...@redhat.com) wrote:
>
> Lennart Poettering (mzerq...@0pointer.de) said:
> > There's also the systemd.unit= kernel command line option which you may
> > use to boot into different targets. See the feature page for details.
>
> Does it pull this from i
On 07/14/2010 01:01 PM, Bill Nottingham wrote:
> Lennart Poettering (mzerq...@0pointer.de) said:
>> Well, I don't think we want to support both. I believe F14 should be
>> systemd and only systemd, but we want the option to revert to upstart
>> should that not work out.
>>
>> I am very much intere
On Wed, 2010-07-14 at 19:32 +0200, Lennart Poettering wrote:
>
> Well, that doesn't really work, since upstart and systemd would fight
> for the /sbin/init name. If we want the system to boot into systemd by
> default /sbin/init must be linekd to /bin/systemd.
>
> systemd provides compatibility
Lennart Poettering (mzerq...@0pointer.de) said:
> There's also the systemd.unit= kernel command line option which you may
> use to boot into different targets. See the feature page for details.
Does it pull this from inittab if there's no other configuration for
this?
Bill
--
devel mailing list
On Wed, 14.07.10 12:32, James Antill (ja...@fedoraproject.org) wrote:
>
> On Wed, 2010-07-14 at 10:58 -0400, Bill Nottingham wrote:
> > Lennart Poettering (mzerq...@0pointer.de) said:
> > > Since the acceptance by FESCO it has been added to Rawhide together with
> > > patched or updated versions
On Wed, 14.07.10 10:16, John Reiser (jrei...@bitwagon.com) wrote:
>
> > What I don't want is that
> > machines suddenly stop booting with no recourse other than init=/bin/bash
> > and manual recovery. There are some side cases that would be nice to either
> > have working, or documenting that th
On Wed, 14.07.10 19:07, drago01 (drag...@gmail.com) wrote:
>
> On Wed, Jul 14, 2010 at 7:01 PM, Bill Nottingham wrote:
> > Lennart Poettering (mzerq...@0pointer.de) said:
> >> Well, I don't think we want to support both. I believe F14 should be
> >> systemd and only systemd, but we want the opti
Once upon a time, James Antill said:
> ...but I think "install" does the right thing, so if we know /usr exists
> it could be:
>
> ExecStartPre=-/usr/bin/install /var/run/foo
I don't think install sets context by default, but in any case, you'd
need a -d in there to create a directory.
--
Chris
B1;2401;0cOn Wed, 14.07.10 13:01, Bill Nottingham (nott...@redhat.com) wrote:
>
> Lennart Poettering (mzerq...@0pointer.de) said:
> > Well, I don't think we want to support both. I believe F14 should be
> > systemd and only systemd, but we want the option to revert to upstart
> > should that not
On Wed, 2010-07-14 at 13:01 -0400, Bill Nottingham wrote:
> Lennart Poettering (mzerq...@0pointer.de) said:
> > Well, I don't think we want to support both. I believe F14 should be
> > systemd and only systemd, but we want the option to revert to upstart
> > should that not work out.
> >
> > I am
> What I don't want is that
> machines suddenly stop booting with no recourse other than init=/bin/bash
> and manual recovery. There are some side cases that would be nice to either
> have working, or documenting that they're not done yet (serial consoles,
> assorted other things.)
Right this mom
Orion Poplawski wrote:
> I'm moving this to fedora-devel to get more comment.
For context, here's the full text of the original proposal sent to kde list
a little while back,
--
Date: Tue, 29 Jun 2010 00:27:05 +0300
From: Kalev Lember
To: k...@lists.fedoraproject.or
Greetings,
I hope everyone is well. This e-mail is intended to inform you about
the upcoming
bugzilla changes happening around July 27, 2010 (Rawhide bug rebase)
and what you
need to do, if anything.
We will be automatically changing the version for most rawhide bugs to
Fedora 14.
This will resu
On Wed, 14.07.10 11:53, Colin Walters (walt...@verbum.org) wrote:
>
> On Wed, Jul 14, 2010 at 11:43 AM, Lennart Poettering
> wrote:
> >
> > time which is enabled via "systemd-install" because the admin wanted so,
>
> Does it make sense to export iscsid for administrator control? I mean
> - won
On 07/14/2010 10:06 AM, Rex Dieter wrote:
> On 07/14/2010 10:58 AM, Orion Poplawski wrote:
>> On 06/28/2010 03:27 PM, Kalev Lember wrote:
>
>>> Perhaps it'd be better to completely remove -DBUILD_SHARED_LIBS:BOOL=ON
>>> from the default %cmake macro? I would imagine that most (all?)
>>> libraries w
On Wed, Jul 14, 2010 at 7:01 PM, Bill Nottingham wrote:
> Lennart Poettering (mzerq...@0pointer.de) said:
>> Well, I don't think we want to support both. I believe F14 should be
>> systemd and only systemd, but we want the option to revert to upstart
>> should that not work out.
>>
>> I am very mu
Lennart Poettering (mzerq...@0pointer.de) said:
> Well, I don't think we want to support both. I believe F14 should be
> systemd and only systemd, but we want the option to revert to upstart
> should that not work out.
>
> I am very much interested to get upgraded systems to use systemd as
> well
On Wed, 14.07.10 11:04, Daniel J Walsh (dwa...@redhat.com) wrote:
> > I suspect the biggest issue here is confined daemons, as they may
> > not have permissions to create their own directories in /var/run or
> > /var/lock once they've been started. Unfortunately, it's the sort of
> > flag day that
On Wed, 14.07.10 10:58, Bill Nottingham (nott...@redhat.com) wrote:
>
> Lennart Poettering (mzerq...@0pointer.de) said:
> > Since the acceptance by FESCO it has been added to Rawhide together with
> > patched or updated versions of a few related packages. However, what has
> > not been done so f
1 - 100 of 117 matches
Mail list logo
