On Fri, 2010-07-30 at 14:41 -0700, darrell pfeifer wrote:
>
>
> On Fri, Jul 30, 2010 at 14:05, Adam Williamson
> wrote:
> On Wed, 2010-07-28 at 21:56 -0700, darrell pfeifer wrote:
>
> > I also had the same problem with one core using 100% CPU, in
> my case
>
On Fri, Jul 30, 2010 at 14:05, Adam Williamson wrote:
> On Wed, 2010-07-28 at 21:56 -0700, darrell pfeifer wrote:
>
> > I also had the same problem with one core using 100% CPU, in my case
> > for Xorg.
>
> I've filed a bug on this -
> https://bugzilla.redhat.com/show_bug.cgi?id=619889.
> --
>
S
On Wed, 2010-07-28 at 21:56 -0700, darrell pfeifer wrote:
> I also had the same problem with one core using 100% CPU, in my case
> for Xorg.
I've filed a bug on this -
https://bugzilla.redhat.com/show_bug.cgi?id=619889.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adam
On Wed, Jul 28, 2010 at 21:20, wrote:
> I found a fix on bugzilla:
> rpm -e --nodeps systemd-units
> yum install systemd-units
> Which created the symlinks and default.service which seemed to be missing,
> and allowed the boot to finish, but I may have been to quick to use it. One
> CPU core is
o I'm temporarily back to upstart
till I get time to look at it further.
https://bugzilla.redhat.com/show_bug.cgi?id=618315
-Original Message-
From: darrell pfeifer
To: Development discussions related to Fedora
Sent: Wed, Jul 28, 2010 6:46 pm
Subject: Re: [HEADS-UP] systemd is now the de
On Wed, Jul 28, 2010 at 19:33, wrote:
> Add init=/sbin/upstart to the end of the kernel line and it will boot up
> using upstart. Last lines in my boot read failing to load default.service
> and then failing to start default.service.
>
> Check one of the recent previous messages.
ln -sf /lib/sy
Sent: Wed, Jul 28, 2010 5:59 pm
Subject: Re: [HEADS-UP] systemd is now the default init system in rawhide
I installed the latest systemd and added the appropriate symbolic link to
graphical startup.
My system hangs when almost complete at the plymouth throbber. In text mode it
gets to the end of
I installed the latest systemd and added the appropriate symbolic link to
graphical startup.
My system hangs when almost complete at the plymouth throbber. In text mode
it gets to the end of starting services and hangs. gdm never starts.
In /var/log/messages, these seem to be the suspicious lines
On Wed, 28 Jul 2010 13:55:23 -0700
darrell pfeifer wrote:
> On Sat, Jul 24, 2010 at 23:34, Kevin Fenzi wrote:
>
> > >>
> >
> > First it seems that my boot would fail. It was unable to find or
> > run a 'default.target' and would hang. Unfortunately it advises you
> > to check the logs, but sinc
On Sat, Jul 24, 2010 at 23:34, Kevin Fenzi wrote:
> >>
>
> First it seems that my boot would fail. It was unable to find or run a
> 'default.target' and would hang. Unfortunately it advises you to check
> the logs, but since syslog isn't up yet and you can't do anything to
> look at dmesg thats n
Hi
On Wed, Jul 28, 2010 at 6:26 AM, Lennart Poettering
wrote:
> On Sat, 24.07.10 00:14, Casey Dahlin (cdah...@redhat.com) wrote:
>
>>
>> On Fri, Jul 23, 2010 at 10:54:50PM -0500, Garrett Holmstrom wrote:
>> > On 7/23/2010 20:26, Lennart Poettering wrote:
>> > > - You can boot into either of them
On Sat, 24.07.10 00:14, Casey Dahlin (cdah...@redhat.com) wrote:
>
> On Fri, Jul 23, 2010 at 10:54:50PM -0500, Garrett Holmstrom wrote:
> > On 7/23/2010 20:26, Lennart Poettering wrote:
> > > - You can boot into either of them by setting the "init=" kernel cmdline
> > >option according to you
On Tue, 2010-07-27 at 11:34 -0400, Bill Nottingham wrote:
> Adam Williamson (awill...@redhat.com) said:
> > > The 'not separating the scripts into a separate subpackage' bit.
> >
> > Ah. I thought the point of separating them wasn't to allow for multiple
> > init systems, but because our current
On Tue, Jul 27, 2010 at 12:55:17AM -0700, Matt McCutchen wrote:
> The next sentence says, "/bin contains commands that may be used by both
> the system administrator and by users, but which are required when no
> other filesystems are mounted (e.g. in single user mode)." systemd
> qualifies on bot
Adam Williamson (awill...@redhat.com) said:
> > The 'not separating the scripts into a separate subpackage' bit.
>
> Ah. I thought the point of separating them wasn't to allow for multiple
> init systems, but because our current guidance was to use sysvinit
> scripts by default, not upstart scrip
On Tue, 2010-07-27 at 11:11 -0400, Bill Nottingham wrote:
> Adam Williamson (awill...@redhat.com) said:
> > > > seems like something that should be changed. readahead,
> > > > system-setup-keyboard and vpnc also have direct dependencies on upstart,
> > > > presumably because they (I think incorrec
Adam Williamson (awill...@redhat.com) said:
> > > seems like something that should be changed. readahead,
> > > system-setup-keyboard and vpnc also have direct dependencies on upstart,
> > > presumably because they (I think incorrectly) include upstart-style
> > > scripts in their main packages ra
On Tue, 2010-07-27 at 10:48 -0400, Bill Nottingham wrote:
> Adam Williamson (awill...@redhat.com) said:
> > %define with_upstart 1%{nil}
> > ...
> > if with_upstart
> > Requires: upstart >= 0.6.0
> > %else
> > Requires: SysVinit >= 2.85-38
> > %endif
> >
> > seems like something that should be ch
Adam Williamson (awill...@redhat.com) said:
> %define with_upstart 1%{nil}
> ...
> if with_upstart
> Requires: upstart >= 0.6.0
> %else
> Requires: SysVinit >= 2.85-38
> %endif
>
> seems like something that should be changed. readahead,
> system-setup-keyboard and vpnc also have direct dependenci
On 07/26/2010 10:33 PM, Adam Williamson wrote:
> On Mon, 2010-07-26 at 11:32 -0400, Peter Jones wrote:
>> On 07/25/2010 04:30 AM, Frank Murphy wrote:
>>> On 25/07/10 07:34, Kevin Fenzi wrote:
Greetings.
first it seems that systemd-sysvinit needs to add a:
Provides: sysvinit
2010/7/27 Matt McCutchen :
> On Tue, 2010-07-27 at 09:42 +0200, Rudolf Kastl wrote:
>> i do not understand how a daemon (like e.g. dbus-daemon) qualifies as
>> "/bin : Essential user command binaries (for use by all users)" (taken
>> from fhs 2.3). one could argue if a daemon qualifies as "command
On Tue, 2010-07-27 at 09:42 +0200, Rudolf Kastl wrote:
> i do not understand how a daemon (like e.g. dbus-daemon) qualifies as
> "/bin : Essential user command binaries (for use by all users)" (taken
> from fhs 2.3). one could argue if a daemon qualifies as "command".
> especially since it seems i
2010/7/27 Rudolf Kastl :
> 2010/7/27 Matt McCutchen :
>> On Mon, 2010-07-26 at 10:31 +0100, Bryn M. Reeves wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 07/24/2010 09:39 PM, Matt McCutchen wrote:
>>> > On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
>>> >> On Sat,
2010/7/27 Matt McCutchen :
> On Mon, 2010-07-26 at 10:31 +0100, Bryn M. Reeves wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 07/24/2010 09:39 PM, Matt McCutchen wrote:
>> > On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
>> >> On Sat, Jul 24, 2010 at 12:14:33AM -0400,
On Mon, 2010-07-26 at 10:31 +0100, Bryn M. Reeves wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/24/2010 09:39 PM, Matt McCutchen wrote:
> > On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
> >> On Sat, Jul 24, 2010 at 12:14:33AM -0400, Casey Dahlin wrote:
> Why is
2010/7/26 Bryn M. Reeves :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/24/2010 09:39 PM, Matt McCutchen wrote:
>> On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
>>> On Sat, Jul 24, 2010 at 12:14:33AM -0400, Casey Dahlin wrote:
> Why is the systemd executable in /bin in
On Mon, 2010-07-26 at 11:32 -0400, Peter Jones wrote:
> On 07/25/2010 04:30 AM, Frank Murphy wrote:
> > On 25/07/10 07:34, Kevin Fenzi wrote:
> >> Greetings.
> >>
> >> first it seems that systemd-sysvinit needs to add a:
> >>
> >> Provides: sysvinit-userspace
> >>
> >> To avoid the current conflict
On Mon, 2010-07-26 at 17:45 -0700, Adam Williamson wrote:
> It also doesn't seem that systemd is yet kicking in as the default for
> the live builds. Even though the installed systemd-units package is
> systemd-units-4-3.fc14.x86_64 , indicating a version new enough to be
> intended to be the defa
On Sat, 2010-07-24 at 03:26 +0200, Lennart Poettering wrote:
> Heya,
>
> I have just uploaded a new systemd and a new upstart package which make
> systemd the default init system for Rawhide. The scheme I followed makes
> sure that in case systemd actually breaks systems there is an easy path
> ba
On 07/25/2010 04:30 AM, Frank Murphy wrote:
> On 25/07/10 07:34, Kevin Fenzi wrote:
>> Greetings.
>>
>> first it seems that systemd-sysvinit needs to add a:
>>
>> Provides: sysvinit-userspace
>>
>> To avoid the current conflicts/upgrade problems:
>>
>> ---> Package upstart-sysvinit.x86_64 0:0.6.5-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2010 09:39 PM, Matt McCutchen wrote:
> On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
>> On Sat, Jul 24, 2010 at 12:14:33AM -0400, Casey Dahlin wrote:
Why is the systemd executable in /bin instead of /sbin?
>>> Without looking t
Lennart Poettering wrote:
> I have just uploaded a new systemd and a new upstart package which make
> systemd the default init system for Rawhide. The scheme I followed makes
> sure that in case systemd actually breaks systems there is an easy path
> back to upstart. And here's how it works:
[...
On 25/07/10 07:34, Kevin Fenzi wrote:
> Greetings.
>
> first it seems that systemd-sysvinit needs to add a:
>
> Provides: sysvinit-userspace
>
> To avoid the current conflicts/upgrade problems:
>
> ---> Package upstart-sysvinit.x86_64 0:0.6.5-7.fc14 set to be installed
> --> Processing Conflict:
On 25/07/10 09:16, Piscium wrote:
Please try and trim "replied to post(s)*
to relevant parts.
>
> What about sysd? It would save sysadmins typing 3 characters.
>
Still doesn't help with Google,
which I feel is just maybe it's newness?
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
On 25 July 2010 07:34, Kevin Fenzi wrote:
> Greetings.
>
> first it seems that systemd-sysvinit needs to add a:
>
> Provides: sysvinit-userspace
>
> To avoid the current conflicts/upgrade problems:
>
> ---> Package upstart-sysvinit.x86_64 0:0.6.5-7.fc14 set to be installed
> --> Processing Conflic
Greetings.
first it seems that systemd-sysvinit needs to add a:
Provides: sysvinit-userspace
To avoid the current conflicts/upgrade problems:
---> Package upstart-sysvinit.x86_64 0:0.6.5-7.fc14 set to be installed
--> Processing Conflict: upstart-sysvinit-0.6.5-7.fc14.x86_64 conflicts
syste
On Sat, Jul 24, 2010 at 01:39:20PM -0700, Matt McCutchen wrote:
> > > Without looking too closely I believe systemd eventually seeks to replace
> > > things like gnome-session daemon. It has session management in mind as
> > > well as system.
> > Still belongs in /sbin, unless it's meant to actuall
On 07/24/2010 04:39 PM, Matt McCutchen wrote:
> On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
>> On Sat, Jul 24, 2010 at 12:14:33AM -0400, Casey Dahlin wrote:
Why is the systemd executable in /bin instead of /sbin?
>>> Without looking too closely I believe systemd eventually seeks t
On Sat, 2010-07-24 at 16:36 -0400, Matthew Miller wrote:
> On Sat, Jul 24, 2010 at 12:14:33AM -0400, Casey Dahlin wrote:
> > > Why is the systemd executable in /bin instead of /sbin?
> > Without looking too closely I believe systemd eventually seeks to replace
> > things like gnome-session daemon.
On Sat, Jul 24, 2010 at 12:14:33AM -0400, Casey Dahlin wrote:
> > Why is the systemd executable in /bin instead of /sbin?
> Without looking too closely I believe systemd eventually seeks to replace
> things like gnome-session daemon. It has session management in mind as
> well as system.
Still bel
On Fri 23 July 2010 18:26:29 Lennart Poettering wrote:
[snip]
> - You can boot into either of them by setting the "init=" kernel cmdline
> option according to your wishes. If you pass "init=/bin/systemd" you
> will boot into systemd, if you pass "init=/sbin/upstart" you will boot
> into upstar
On Fri, Jul 23, 2010 at 10:54:50PM -0500, Garrett Holmstrom wrote:
> On 7/23/2010 20:26, Lennart Poettering wrote:
> > - You can boot into either of them by setting the "init=" kernel cmdline
> >option according to your wishes. If you pass "init=/bin/systemd" you
> >will boot into systemd,
On Fri, Jul 23, 2010 at 08:04:48PM -0700, darrell pfeifer wrote:
> On Fri, Jul 23, 2010 at 18:26, Lennart Poettering wrote:
>
> > Heya,
> >
> > I have just uploaded a new systemd and a new upstart package which make
> > systemd the default init system for Rawhide. The scheme I followed makes
> > s
On 7/23/2010 20:26, Lennart Poettering wrote:
> - You can boot into either of them by setting the "init=" kernel cmdline
>option according to your wishes. If you pass "init=/bin/systemd" you
>will boot into systemd, if you pass "init=/sbin/upstart" you will boot
>into upstart (note the
On Fri, Jul 23, 2010 at 18:26, Lennart Poettering wrote:
> Heya,
>
> I have just uploaded a new systemd and a new upstart package which make
> systemd the default init system for Rawhide. The scheme I followed makes
> sure that in case systemd actually breaks systems there is an easy path
> back t
Heya,
I have just uploaded a new systemd and a new upstart package which make
systemd the default init system for Rawhide. The scheme I followed makes
sure that in case systemd actually breaks systems there is an easy path
back to upstart. And here's how it works:
- "upstart" and "systemd" are no
46 matches
Mail list logo
