On Lu, 19 nov 12, 12:27:22, Tom H wrote:
>
> Yes, wheezy's udev thankfully pre-merge. Given that there are a few
> distributions that want and will want to have a standalone udev for
> the lifetime of jessie, some agreement can be reached about compiling
> it easily that way for the foreseeable fu
On 11/20/12, Zenaan Harkness wrote:
> On 11/20/12, Michael Biebl wrote:
>> You mentioned, that you use some sort of encryption.
>> Posting more details (fstab, cryptab, etc) might help.
>> I suspect your problem is related to that.
...
> fstab:
> # / was on /dev/sda5 during installation # about 8
On Mon, 19 Nov 2012 12:08:37 -0500
Tom H wrote:
> So what was the point?!
Systemd is superb! I've nothing to add. It's completely useless to
discuss it again and again.
Regards,
Ralf
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
On Mon, Nov 19, 2012 at 10:07 AM, Zenaan Harkness wrote:
>
> WFT?!!?! No syslog file.
>
> BIG apologies, I have been deceived by the systemd - I assumed it
> would log _something_ to syslog. No. Everything I was seeing (and
> reporting on thus far) was init. systemd "hangs" before it logs
> anythi
On Mon, Nov 19, 2012 at 9:05 AM, "Morel Bérenger"
wrote:
> Le Lun 19 novembre 2012 14:38, Ralf Mardorf a écrit :
>>
>> Don't worry I'm tired to explain it again and again. Everybody should
>> switch to systemd, it's superb to have everything startup needs in one big
>> binary beta blob, much more
On Mon, Nov 19, 2012 at 8:38 AM, Ralf Mardorf
wrote:
> On Mon, 2012-11-19 at 07:44 -0500, Tom H wrote:
>>
>> Nothing but innacuracy and FUD, as usual.
>>
>> As I've pointed out in another thread/post [1], you're confusing
>> consolekit and policykit.
>
> I'm not. Didn't you read the links?
>
>> P
On 11/20/12, Michael Biebl wrote:
> As for getting a more verbose debug log, there is plenty of
> documentation which is easily found by google.
> Try
> http://fedoraproject.org/wiki/How_to_debug_Systemd_problems
> or
> http://www.freedesktop.org/wiki/Software/systemd/Debugging
Yes, I'll do some
On 19.11.2012 16:07, Zenaan Harkness wrote:
> On 11/19/12, Tom H wrote:
>> On Sun, Nov 18, 2012 at 11:07 PM, Zenaan Harkness wrote:
>>>
>>> First, systemd worked.
>>> Now it hangs on bootup, with the following messages:
> ...
>>> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
On 11/19/12, Jon Dowland wrote:
> On Mon, Nov 19, 2012 at 10:54:57AM +0100, Ralf Mardorf wrote:
>> Could you please answer this question of the OP:
>> On Mon, 2012-11-19 at 19:42 +1100, Zenaan Harkness wrote:
>> > Can anyone here say they've achieved any sort of systemd joy, or am I
>> > just aski
On 11/19/12, Tom H wrote:
> On Sun, Nov 18, 2012 at 11:07 PM, Zenaan Harkness wrote:
>>
>> First, systemd worked.
>> Now it hangs on bootup, with the following messages:
...
>> Nov 19 14:31:12 localhost named[2353]: error (network unreachable)
>> resolving 'B.ROOT-SERVERS.NET//IN': 192.33.4.1
Hi - please trim your quotes.
On Mon, Nov 19, 2012 at 03:05:55PM +0100, "Morel Bérenger" wrote:
> If I am not wrong, there IS such a warning if you do the switch. At least,
> if you remove the package sysvinit (or whatever name) with aptitude, it
> will ask you to write an entire sentance which ex
On Mon, Nov 19, 2012 at 07:44:39AM -0500, Tom H wrote:
> The problem is that it's no longer possible for recent versions of
> udev to compile it without compiling systemd too.
The truth is a bit more complicated. You can build just udev from the
systemd sources: "make udevd" rather than the defau
Le Lun 19 novembre 2012 14:38, Ralf Mardorf a écrit :
> On Mon, 2012-11-19 at 07:44 -0500, Tom H wrote:
>
>> Nothing but innacuracy and FUD, as usual.
>>
>>
>> As I've pointed out in another thread/post [1], you're confusing
>> consolekit and policykit.
>
> I'm not. Didn't you read the links?
>
>
>
On Mon, 2012-11-19 at 07:44 -0500, Tom H wrote:
> Nothing but innacuracy and FUD, as usual.
>
> As I've pointed out in another thread/post [1], you're confusing
> consolekit and policykit.
I'm not. Didn't you read the links?
> Policykit is a standalone
> application/package. Consolekit on the o
On Mon, Nov 19, 2012 at 3:07 AM, Ralf Mardorf
wrote:
> On Mon, 2012-11-19 at 15:07 +1100, Zenaan Harkness wrote:
>> Is this the best place for systemd assistance?
>
> The best place to get assistance are the insane people who try to force
> this into every Linux distribution, with LP leading the
On Sun, Nov 18, 2012 at 11:07 PM, Zenaan Harkness wrote:
>
> First, systemd worked.
> Now it hangs on bootup, with the following messages:
> Loading, please wait...
> systemd-fsck[249]: /dev/sda5: clean, ...
> plus one similar fsck msg.
>
> After a minute or two it asks me for root pwd or to Ctrl-
On Mon, Nov 19, 2012 at 10:54:57AM +0100, Ralf Mardorf wrote:
> why not warn people to use something that's known for issues only?
It isn't known for issues only. There's a lot of heat and noise about
problems with systemd, that is true, but a substantial amount of that
heat and noise is posts lik
On 11/19/12, Jon Dowland wrote:
> On Mon, Nov 19, 2012 at 03:07:54PM +1100, Zenaan Harkness wrote:
>> Is this the best place for systemd assistance?
>
> For systemd-in-Debian, most likely, yes.
>
>> First, systemd worked.
>> Now it hangs on bootup, with the following messages:
>
> What has changed
On Mon, 2012-11-19 at 09:27 +, Jon Dowland wrote:
> On Mon, Nov 19, 2012 at 09:07:17AM +0100, Ralf Mardorf wrote:
> > On Mon, 2012-11-19 at 15:07 +1100, Zenaan Harkness wrote:
> > > Is this the best place for systemd assistance?
> >
> > The best place to get assistance are the insane people wh
On Mon, Nov 19, 2012 at 03:07:54PM +1100, Zenaan Harkness wrote:
> Is this the best place for systemd assistance?
For systemd-in-Debian, most likely, yes.
> First, systemd worked.
> Now it hangs on bootup, with the following messages:
What has changed? Have you upgraded systemd or other packages
On Mon, Nov 19, 2012 at 09:07:17AM +0100, Ralf Mardorf wrote:
> On Mon, 2012-11-19 at 15:07 +1100, Zenaan Harkness wrote:
> > Is this the best place for systemd assistance?
>
> The best place to get assistance are the insane people who try to force
> this into every Linux distribution, with LP lea
On Mon, 2012-11-19 at 09:03 +0200, ed mente wrote:
> Have you tried booting from another device and fsck on your root and
> boot partitions?
No, no, I suspect the issue has something to do with read only or not
read only at startup. However, search the web. I don't remember exactly
this issue, but
On 11/19/12, Ralf Mardorf wrote:
> On Mon, 2012-11-19 at 15:07 +1100, Zenaan Harkness wrote:
>> Is this the best place for systemd assistance?
>
> The best place to get assistance are the insane people who try to force
> this into every Linux distribution, with LP leading the way.
So perhaps post
On Mon, 2012-11-19 at 15:07 +1100, Zenaan Harkness wrote:
> Is this the best place for systemd assistance?
The best place to get assistance are the insane people who try to force
this into every Linux distribution, with LP leading the way.
> First, systemd worked.
> Now it hangs on bootup
That's
I shall try that tonight, thanks, but didn't think it necessary since it says,
each time I try to boot, fsck appears result in "clean" (see above).
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arch
Have you tried booting from another device and fsck on your root and
boot partitions?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y5hy2hwh@noname.com
Is this the best place for systemd assistance?
First, systemd worked.
Now it hangs on bootup, with the following messages:
Loading, please wait...
systemd-fsck[249]: /dev/sda5: clean, ...
plus one similar fsck msg.
After a minute or two it asks me for root pwd or to Ctrl-D for normal
bootup. I ca
27 matches
Mail list logo
