On Lu, 21 iul 14, 23:52:17, Alex Mestiashvili wrote:
The selection of system used for a task depends a lot on the task.
I do not see anything silly in using testing in production.
Sure, but then it's not fair to complain that things are, well, still in
testing.
Kind regards,
Andrei
--
On Mon, Jul 21, 2014 at 11:19:54PM CEST, Andrei POPESCU
andreimpope...@gmail.com said:
On Lu, 21 iul 14, 21:54:48, Erwan David wrote:
Le 21/07/2014 21:33, Joe a écrit :
Let us hope so. Tonight's upgrade to sid requires the removal of
sysvinit-core...
libpam-systemd 204 depends
On Mon, 21 Jul 2014 22:54:42 -0400
The Wanderer wande...@fastmail.fm wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/21/2014 06:46 PM, Michael Biebl wrote:
Am 22.07.2014 00:21, schrieb Joe:
So I plugged in the drive, and suddenly it all burst into life.
Well, nearly
On Tue, 22 Jul 2014 00:46:19 +0200
Michael Biebl bi...@debian.org wrote:
Am 22.07.2014 00:21, schrieb Joe:
So I plugged in the drive, and suddenly it all burst into life.
Well, nearly all, no networking, which is a bit limiting for a
workstation...
This drive has its own fstab entries
On 2014-07-22 00:46 +0200, Michael Biebl wrote:
I assume this partition on the removable drive is not marked noauto or
nofail
Since systemd can't know which mount points are essential for your
system to come up properly, the default is to drop you into a rescue
shell if the devices do not
On 7/22/14, Erwan David er...@rail.eu.org wrote:
On Mon, Jul 21, 2014 at 11:19:54PM CEST, Andrei POPESCU
andreimpope...@gmail.com said:
On Lu, 21 iul 14, 21:54:48, Erwan David wrote:
Le 21/07/2014 21:33, Joe a écrit :
Let us hope so. Tonight's upgrade to sid requires the removal of
On Tue, Jul 22, 2014 at 10:12:37AM CEST, Zenaan Harkness z...@freedbms.net
said:
On 7/22/14, Erwan David er...@rail.eu.org wrote:
On Mon, Jul 21, 2014 at 11:19:54PM CEST, Andrei POPESCU
andreimpope...@gmail.com said:
On Lu, 21 iul 14, 21:54:48, Erwan David wrote:
Le 21/07/2014 21:33,
On Tue, Jul 22, 2014 at 5:11 PM, Sven Joachim svenj...@gmx.de wrote:
On 2014-07-22 00:46 +0200, Michael Biebl wrote:
I assume this partition on the removable drive is not marked noauto or
nofail
Since systemd can't know which mount points are essential for your
system to come up properly,
On Tue, Jul 22, 2014 at 4:48 PM, Joe j...@jretrading.com wrote:
On Mon, 21 Jul 2014 22:54:42 -0400
[...]
systemd[1]: /usr appears to be on its own filesytem and is not already
mounted. This is not a supported setup. Some things will probably break
(sometimes even silently) in mysterious ways.
On Mon, Jul 21, 2014 at 11:34 PM, Chris Bannister
cbannis...@slingshot.co.nz wrote:
On Mon, Jul 21, 2014 at 07:26:43AM +0200, Erwan David wrote:
I do not have the ressources to test : no time no machine which I can afford
to break.
And since today syste,md-shim is no more an option
On Tue, 22 Jul 2014 22:04:22 +0900
Joel Rees joel.r...@gmail.com wrote:
On Tue, Jul 22, 2014 at 4:48 PM, Joe j...@jretrading.com wrote:
On Mon, 21 Jul 2014 22:54:42 -0400
[...]
systemd[1]: /usr appears to be on its own filesytem and is not
already mounted. This is not a supported setup.
On 22/07/14 15:03, Joe wrote:
I've got it now. Apparently /usr has needed to be available at boot
time for a long time, but this seems to have completely passed me by,
and hasn't yet bitten me. I have always thought that 'usr' was short for
'user', and that /usr contains only applications and
On Mon, Jul 21, 2014 at 3:09 PM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Tom H wrote:
On Mon, Jul 21, 2014 at 11:49 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Damn right I don't use development or testing versions in production.
I'm
looking down the road a year and
On Tue, 22 Jul 2014 22:04:22 +0900
Joel Rees joel.r...@gmail.com wrote:
On Tue, Jul 22, 2014 at 4:48 PM, Joe j...@jretrading.com wrote:
On Mon, 21 Jul 2014 22:54:42 -0400
[...]
systemd[1]: /usr appears to be on its own filesytem and is not
already mounted. This is not a supported setup.
Jonathan Dowland wrote:
You can install systemd to try it out before committing to it as your
default init system. Just install 'systemd' but not 'systemd-sysv' and
pass init=/bin/systemd to Linux via your boot manager.
Hi all,
FWIW, I just tried this with my amd64 sid system.
Most things
On Monday 21 July 2014 05:42:09 debian-user-digest-requ...@lists.debian.org
wrote:
You can install systemd to try it out before committing to it as your
default init system. Just install 'systemd' but not 'systemd-sysv' and
pass init=/bin/systemd to Linux via your boot manager.
Erwan David wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland j...@debian.org
said:
On Sun, Jul 20, 2014 at 03:09:40PM +0200, Erwan David wrote:
Problem is where do we get the knowledge to repair mannually ? I do noit
see it in /usr/share/doc/systemd nor in the crossreference
On 2014-07-21, Erwan David er...@rail.eu.org wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland j...@debian.org
said:
(...)
This and more excellent documentation at
https://wiki.debian.org/systemd#Configuring_for_testing
I do not have the ressources to test : no time no
On Mon, Jul 21, 2014 at 02:26:44PM CEST, Liam O'Toole liam.p.oto...@gmail.com
said:
On 2014-07-21, Erwan David er...@rail.eu.org wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland j...@debian.org
said:
(...)
This and more excellent documentation at
Am Montag, 21. Juli 2014, 08:16:57 schrieb Miles Fidelman:
Erwan David wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland
j...@debian.org said:
On Sun, Jul 20, 2014 at 03:09:40PM +0200, Erwan David wrote:
Problem is where do we get the knowledge to repair mannually ? I do
On Mon, Jul 21, 2014 at 07:26:43AM +0200, Erwan David wrote:
BULLSHIT !! testing withoput doc does not replace knowledge. That's diy
computing, that's not serious. When I reasd this
Please moderate your behaviour on this list. Please see [1] and [2] to learn
what is acceptable and what is not
On Mon, Jul 21, 2014 at 08:16:57AM -0400, Miles Fidelman wrote:
That does capture things in a nutshell. Some of us actually run Debian in
production, server environments - and have enough issues keeping things up
for our users. As someone pointed out a little earlier:
No where, just go
On Mon, Jul 21, 2014 at 07:26:43AM +0200, Erwan David wrote:
I do not have the ressources to test : no time no machine which I can afford
to break.
And since today syste,md-shim is no more an option (aptitude wants to remove
it)
I do not want to test. I want to be surze it works. And
On Mon, Jul 21, 2014 at 04:34:16PM CEST, Chris Bannister
cbannis...@slingshot.co.nz said:
On Mon, Jul 21, 2014 at 07:26:43AM +0200, Erwan David wrote:
I do not have the ressources to test : no time no machine which I can
afford to break.
And since today syste,md-shim is no more an
On Tue, 22 Jul 2014 02:34:16 +1200
Chris Bannister cbannis...@slingshot.co.nz wrote:
On Mon, Jul 21, 2014 at 07:26:43AM +0200, Erwan David wrote:
I do not have the ressources to test : no time no machine which I
can afford to break.
And since today syste,md-shim is no more an option
Martin Steigerwald wrote:
Am Montag, 21. Juli 2014, 08:16:57 schrieb Miles Fidelman:
Erwan David wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland
j...@debian.org said:
On Sun, Jul 20, 2014 at 03:09:40PM +0200, Erwan David wrote:
Problem is where do we get the knowledge to
Chris Bannister wrote:
On Mon, Jul 21, 2014 at 08:16:57AM -0400, Miles Fidelman wrote:
That does capture things in a nutshell. Some of us actually run Debian in
production, server environments - and have enough issues keeping things up
for our users. As someone pointed out a little earlier:
On 2014-07-21, Erwan David er...@rail.eu.org wrote:
On Mon, Jul 21, 2014 at 02:26:44PM CEST, Liam O'Toole
liam.p.oto...@gmail.com said:
On 2014-07-21, Erwan David er...@rail.eu.org wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland
j...@debian.org said:
(...)
This and
Le 21/07/2014 17:59, Liam O'Toole a écrit :
On 2014-07-21, Erwan David er...@rail.eu.org wrote:
On Mon, Jul 21, 2014 at 02:26:44PM CEST, Liam O'Toole
liam.p.oto...@gmail.com said:
On 2014-07-21, Erwan David er...@rail.eu.org wrote:
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland
On Mon, Jul 21, 2014 at 11:49 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Damn right I don't use development or testing versions in production. I'm
looking down the road a year and planning what I will use in production when
my current system is ready for upgrade. It's looking less
Tom H wrote:
On Mon, Jul 21, 2014 at 11:49 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Damn right I don't use development or testing versions in production. I'm
looking down the road a year and planning what I will use in production when
my current system is ready for upgrade. It's
On Mon, 21 Jul 2014 13:00:01 -0400
Tom H tomh0...@gmail.com wrote:
On Mon, Jul 21, 2014 at 11:49 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Damn right I don't use development or testing versions in
production. I'm looking down the road a year and planning what I
will use in
Le 21/07/2014 21:33, Joe a écrit :
On Mon, 21 Jul 2014 13:00:01 -0400
Tom H tomh0...@gmail.com wrote:
On Mon, Jul 21, 2014 at 11:49 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Damn right I don't use development or testing versions in
production. I'm looking down the road a year
On Lu, 21 iul 14, 21:54:48, Erwan David wrote:
Le 21/07/2014 21:33, Joe a écrit :
Let us hope so. Tonight's upgrade to sid requires the removal of
sysvinit-core...
libpam-systemd 204 depends systemd-sysv|systemd-shim
libpam-systemd 208 depends systemd-sysv
Alternative disappeared
On 07/21/2014 04:34 PM, Chris Bannister wrote:
On Mon, Jul 21, 2014 at 07:26:43AM +0200, Erwan David wrote:
I do not have the ressources to test : no time no machine which I can afford to
break.
And since today syste,md-shim is no more an option (aptitude wants to remove it)
I do not want to
On Tue, 22 Jul 2014 00:19:54 +0300
Andrei POPESCU andreimpope...@gmail.com wrote:
On Lu, 21 iul 14, 21:54:48, Erwan David wrote:
Le 21/07/2014 21:33, Joe a écrit :
Let us hope so. Tonight's upgrade to sid requires the removal of
sysvinit-core...
libpam-systemd 204 depends
Am 22.07.2014 00:21, schrieb Joe:
So I plugged in the drive, and suddenly it all burst into life. Well,
nearly all, no networking, which is a bit limiting for a workstation...
This drive has its own fstab entries by UUID, as it often gets plugged
into this desktop. My assumption is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/21/2014 06:46 PM, Michael Biebl wrote:
Am 22.07.2014 00:21, schrieb Joe:
So I plugged in the drive, and suddenly it all burst into life.
Well, nearly all, no networking, which is a bit limiting for a
workstation...
This drive has its
How safe are these on new 64bit system (dist-upgraded to Sid)?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1448925.rEsNO80blQ@dovidhalevi
Am Sonntag, 20. Juli 2014, 11:00:15 schrieb David Baron:
How safe are these on new 64bit system (dist-upgraded to Sid)?
Which do you mean by these?
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/20/2014 05:17 AM, Martin Steigerwald wrote:
Am Sonntag, 20. Juli 2014, 11:00:15 schrieb David Baron:
How safe are these on new 64bit system (dist-upgraded to Sid)?
Which do you mean by these?
I'd imagine he means upgrades to systemd,
On Sun 20 Jul 2014 at 11:00:15 +0300, David Baron wrote:
How safe are these on new 64bit system (dist-upgraded to Sid)?
In principle nothing that you do with unstable is safe. But you have
chosen to test it. So go ahead and be prepared to analyse and report
bugs or fix issues.
--
To
The Wanderer writes:
There are reasons sid is also called unstable.
It's called Unstable because it changes frequently. The biggest problem
with Sid is dependency problems. Because a new version of any package
can be uploaded to Sid at any time without regard to dependencies one
can get stuck
Le 20/07/2014 14:17, The Wanderer a écrit :
On 07/20/2014 05:17 AM, Martin Steigerwald wrote:
Am Sonntag, 20. Juli 2014, 11:00:15 schrieb David Baron:
How safe are these on new 64bit system (dist-upgraded to Sid)?
Which do you mean by these?
I'd imagine he means upgrades to systemd,
On Du, 20 iul 14, 07:59:21, John Hasler wrote:
The Wanderer writes:
There are reasons sid is also called unstable.
It's called Unstable because it changes frequently. The biggest problem
with Sid is dependency problems. Because a new version of any package
can be uploaded to Sid at any
On Sun, 20 Jul 2014 08:17:05 -0400
The Wanderer wande...@fastmail.fm wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/20/2014 05:17 AM, Martin Steigerwald wrote:
Am Sonntag, 20. Juli 2014, 11:00:15 schrieb David Baron:
How safe are these on new 64bit system
20.07.2014, 14:23, Brian a...@cityscape.co.uk:
On Sun 20 Jul 2014 at 11:00:15 +0300, David Baron wrote:
How safe are these on new 64bit system (dist-upgraded to Sid)?
In principle nothing that you do with unstable is safe. But you have
chosen to test it. So go ahead and be prepared to
On Sun, Jul 20, 2014 at 03:09:40PM +0200, Erwan David wrote:
Problem is where do we get the knowledge to repair mannually ? I do noit
see it in /usr/share/doc/systemd nor in the crossreference man pages,
nor anywhere else.
You can install systemd to try it out before committing to it as your
On Sun, 20 Jul 2014 21:36:30 +0100
Jonathan Dowland j...@debian.org wrote:
You can install systemd to try it out before committing to it as your
default init system. Just install 'systemd' but not 'systemd-sysv' and
pass init=/bin/systemd to Linux via your boot manager.
This and more
On Sun, Jul 20, 2014 at 10:36:30PM CEST, Jonathan Dowland j...@debian.org
said:
On Sun, Jul 20, 2014 at 03:09:40PM +0200, Erwan David wrote:
Problem is where do we get the knowledge to repair mannually ? I do noit
see it in /usr/share/doc/systemd nor in the crossreference man pages,
nor
50 matches
Mail list logo
