Erwan David wrote:
>
> systemd is NOT an init system. It is a global system pretending to
> replace init, session management,dns, ntp, and more and more other
> components with incomplete solutions thought only for the laptops of its
> developers (see the "we won't support hard disks, we all use
On Tue, 10 Jan 2017 14:29:17 -0600
David Wright wrote:
>
> I can see that a post-mortem of what went wrong is useful, but I can't
> understand why you say that systemd made the "wrong" assumption.
> If you specify something wrongly, you can't really expect it to do
> what you want it to do, or
Le 01/10/2017 à 21:49, David Wright a écrit :
> On Tue 10 Jan 2017 at 20:54:50 (+0100), Steffen Dettmer wrote:
>> On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote:
> I'd rather keep it as simple as possible
you can still use sysvinit as init
>>
>> I read that trying to use sysvin
On Tue, 10 Jan 2017 08:57:36 -0500 rhkra...@gmail.com sent:
> > > This is called evolution.
> >
> > There are dissenting views, and y'all know that.
>
> Just to get my $0.02 in, evolution makes many mistakes. In fact, it
> is a process of (accidental) trial and error. ;-)
After co
On Tue 10 Jan 2017 at 20:54:50 (+0100), Steffen Dettmer wrote:
> On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote:
> >>> I'd rather keep it as simple as possible
> >>
> >> you can still use sysvinit as init
>
> I read that trying to use sysvinit causes trouble and several things
> depend on s
On Tue 10 Jan 2017 at 20:08:10 (+0100), Steffen Dettmer wrote:
> On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote:
> >> What happened before:
> >> I had issue with a Debian server SATA bus [1]. I noticed because
> >> apt-get upgrade hung, because initramfs updater calls "sync" which
> >> hang because of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 10, 2017 at 08:54:50PM +0100, Steffen Dettmer wrote:
> On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote:
> >>> I'd rather keep it as simple as possible
> >>
> >> you can still use sysvinit as init
>
> I read that trying to use sysvini
On Tue, 10 Jan 2017 20:54:50 +0100
Steffen Dettmer wrote:
> On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl
> wrote:
> >>
> >> you can still use sysvinit as init
>
> I read that trying to use sysvinit causes trouble and several things
> depend on systemd at the moment.
>
Various things requi
On Tue, 10 Jan 2017 20:08:10 +0100
Steffen Dettmer wrote:
> On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote:
> >> What happened before:
> >> I had issue with a Debian server SATA bus [1]. I noticed because
> >> apt-get upgrade hung, because initramfs updater calls "sync" which
> >> hang because of [1]
Am 10.01.2017 um 20:08 schrieb Steffen Dettmer:
> On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote:
>>> What happened before:
>>> I had issue with a Debian server SATA bus [1]. I noticed because
>>> apt-get upgrade hung, because initramfs updater calls "sync" which
>>> hang because of [1]. All operations
On Tue, Jan 10, 2017 at 12:51 PM, Dominique Dumont wrote:
> On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote:
>> I'm looking at Jessie (Debian 8) man fsck. I found no refernce
>> to systemd. I think this is some compatiblity feature of systemd.
>
> See systemd.mount(5) and systemd.swa
On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote:
>>> I'd rather keep it as simple as possible
>>
>> you can still use sysvinit as init
I read that trying to use sysvinit causes trouble and several things
depend on systemd at the moment.
> The shell scripts used by sysvinit are not simpler.
On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote:
>> What happened before:
>> I had issue with a Debian server SATA bus [1]. I noticed because
>> apt-get upgrade hung, because initramfs updater calls "sync" which
>> hang because of [1]. All operations accessing a certain (backup) disk
>> blocked. Shutdow
rhkra...@gmail.com wrote:
> On Tuesday, January 10, 2017 03:39:06 AM to...@tuxteam.de wrote:
>> On Tue, Jan 10, 2017 at 09:14:48AM +0100, deloptes wrote:
>> > Michael Biebl wrote:
>> > > Am 10.01.2017 um 00:43 schrieb deloptes:
>> > >> Steffen Dettmer wrote:
>> > >>> I'd rather keep it as simple a
On Tue 10 Jan 2017 at 12:51:09 (+0100), Dominique Dumont wrote:
> On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote:
> > I'm looking at Jessie (Debian 8) man fsck. I found no refernce
> > to systemd. I think this is some compatiblity feature of systemd.
>
> See systemd.mount(5) and sys
On Tuesday, January 10, 2017 03:39:06 AM to...@tuxteam.de wrote:
> On Tue, Jan 10, 2017 at 09:14:48AM +0100, deloptes wrote:
> > Michael Biebl wrote:
> > > Am 10.01.2017 um 00:43 schrieb deloptes:
> > >> Steffen Dettmer wrote:
> > >>> I'd rather keep it as simple as possible
> > >>
> > >> you can
On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote:
> I'm looking at Jessie (Debian 8) man fsck. I found no refernce
> to systemd. I think this is some compatiblity feature of systemd.
See systemd.mount(5) and systemd.swap(5)
Compatiblity is done by systemd-fstab-generator
HTH
--
On Mon, Jan 09, 2017 at 10:49:02PM +0100, Steffen Dettmer wrote:
> Because man page says so? Because fsck's job is to check fs?
> Don't know what systemd interferes at all.
See systemd-fsck(8).
--
Jonathan Dowland
Please do not CC me, I am subscribed to the list.
signature.asc
Description: Dig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 10, 2017 at 09:14:48AM +0100, deloptes wrote:
> Michael Biebl wrote:
>
> > Am 10.01.2017 um 00:43 schrieb deloptes:
> >> Steffen Dettmer wrote:
> >>
> >>> I'd rather keep it as simple as possible
> >>
> >> you can still use sysvinit as i
Michael Biebl wrote:
> Am 10.01.2017 um 00:43 schrieb deloptes:
>> Steffen Dettmer wrote:
>>
>>> I'd rather keep it as simple as possible
>>
>> you can still use sysvinit as init
>
> The shell scripts used by sysvinit are not simpler. More familiar maybe,
> but not simpler.
>
>
This is calle
Am 10.01.2017 um 00:43 schrieb deloptes:
> Steffen Dettmer wrote:
>
>> I'd rather keep it as simple as possible
>
> you can still use sysvinit as init
The shell scripts used by sysvinit are not simpler. More familiar maybe,
but not simpler.
--
Why is it that all of the instruments seeking int
Steffen Dettmer wrote:
> I'd rather keep it as simple as possible
you can still use sysvinit as init
or follow without-systemd.org
regards
Hi,
thank you for your quick reply.
On Mon, Jan 9, 2017 at 1:38 AM, David Wright wrote:
> On Sun 08 Jan 2017 at 15:56:36 (+0100), Steffen Dettmer wrote:
>> apparently is ignored and "1" is assumed instead, BUT systemd does not
>> call fsck! fsck parsed the line as intended (pass=0 -> no check),
On Sun 08 Jan 2017 at 15:56:36 (+0100), Steffen Dettmer wrote:
> Hi,
>
> main problem was the disk indeed! Apparently there was a typo in
> fstab, probably leading to a parse error (which isn't shown
> unfortunately) then the value "0" in the "pass" row for fsck
> apparently is ignored and "1" is
On Sun, 8 Jan 2017 14:28:09 +0100
Steffen Dettmer wrote:
> Hi,
>
> What happened before:
> I had issue with a Debian server SATA bus [1]. I noticed because
> apt-get upgrade hung, because initramfs updater calls "sync" which
> hang because of [1]. All operations accessing a certain (backup) disk
On Sun, 8 Jan 2017 14:28:09 +0100
Steffen Dettmer wrote:
> Hi,
>
> What happened before:
> I had issue with a Debian server SATA bus [1]. I noticed because
> apt-get upgrade hung, because initramfs updater calls "sync" which
> hang because of [1]. All operations accessing a certain (backup) disk
Hi,
main problem was the disk indeed! Apparently there was a typo in
fstab, probably leading to a parse error (which isn't shown
unfortunately) then the value "0" in the "pass" row for fsck
apparently is ignored and "1" is assumed instead, BUT systemd does not
call fsck! fsck parsed the line as in
Hi,
I think I found some more information.
In short:
"Failed at step exec spawning /bin/plymouth: no such file or directory"
but I have no clue why it is suddenly missing or suddenly required.
I found postings in the internet that simply installing plymouth seems
not to solve this issue.
What ca
Hi,
What happened before:
I had issue with a Debian server SATA bus [1]. I noticed because
apt-get upgrade hung, because initramfs updater calls "sync" which
hang because of [1]. All operations accessing a certain (backup) disk
blocked. Shutdown over network. It was reported server power LED still
29 matches
Mail list logo
