Steve,
This page was last modified in 2006 and it too talks about latest Debian
curl -I http://blog.edseek.com/~jasonb/articles/exim4_courier/exim4.html
HTTP/1.1 200 OK
Date: Mon, 23 Jun 2014 18:54:55 GMT
Server: Apache/2.2.16 (Debian)
Last-Modified: Fri, 19 May 2006 19:30:55 GMT
ETag:
btw It looks like exim4 first entered into Debian with Sarge (Debian
3.1, released 2005), here's a link with more info:
http://www.debian-administration.org/article/98/Upgrading_from_Woody_to_Sarge_Part_4_-_Apache2
Cheers
A.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On 28/06/2014 11:35 PM, Kent West wrote:
I had a computer once which exhibited this behavior. It's not
Debian-related; it's hardware related. I couldn't even get into the
BIOS, etc. i never found a solution. I gave up on the computer and gave
it to a friend who was happy running Windows. I've
On 3/08/2014 4:39 AM, Brian wrote:
On Sun 03 Aug 2014 at 01:29:57 +0800, Bret Busby wrote:
There is no substitute for Skype (either the software or the service)
whether it be open or closed source,
What about Google Hangouts? That might be a reasonable substitute
I haven't used Skype
On 3/08/2014 9:21 AM, Joel Rees wrote:
On 03/08/2014, Andrew McGlashan andrew.mcglas...@affinityvision.com.au
wrote:
What about Google Hangouts? That might be a reasonable substitute
Google? That is even more sinister than the NSA, isn't it? The NSA
doesn't drive around suburbia
On 3/08/2014 12:31 PM, David Christensen wrote:
On 08/02/2014 12:16 PM, Joel Rees wrote:
As I understand it, he's asking whether any of us on the users list has
anaylyzed the output of both /dev/random and /dev/urandom . Not just
whether any of us are having issues with blocking, but with the
On 3/08/2014 6:46 PM, Bret Busby wrote:
On 03/08/2014, Andrew McGlashan andrew.mcglas...@affinityvision.com.au
wrote:
On 3/08/2014 9:21 AM, Joel Rees wrote:
On 03/08/2014, Andrew McGlashan andrew.mcglas...@affinityvision.com.au
I do not have a smart phone - I have an Oldies Phone
On 3/08/2014 10:48 PM, B wrote:
On Sun, 03 Aug 2014 18:20:19 +1000
I do not agree with that because using only zeros makes
the result part predictable for the attacker: if he knows
what you wrote, he has a (very) large part of the
cryptanalysis done…
This is 1.0.1 of cryptanalysis: if
On 4/08/2014 1:16 AM, B wrote:
The question raise the underlying problems:
snip
* Should we pay for good crypto (and very good cryptanalysis)?
I think YES (stop yelling, think crowfunding;), because
good crypto skills are rare and thus expensive;
furthermore, we need stable
On 4/08/2014 4:19 AM, B wrote:
On Mon, 04 Aug 2014 03:45:48 +1000
Andrew McGlashan andrew.mcglas...@affinityvision.com.au wrote:
Yes, but the method of encryption used (aes-xts-plain64) does NOT
lend itself to this kind of analysis.
Not that we know of…
Yes.
XTS doesn't seem
On 4/08/2014 5:43 AM, David Christensen wrote:
On 08/03/2014 10:45 AM, Andrew McGlashan wrote:
On 3/08/2014 10:48 PM, B wrote:
On Sun, 03 Aug 2014 18:20:19 +1000
I do not agree with that because using only zeros makes
the result part predictable for the attacker:
Yes, but the method
Hi Bret,
On 3/08/2014 8:47 PM, Bret Busby wrote:
Actually we are subject to a bill of rights, see here:
http://www.clrg.info/2011/02/validity-of-bill-of-rights-1688/
That applies only to Victoria - I believe that, like motor vehicle
roadworthiness testing, human rights legislation applies to
On 25/07/2014 11:17 PM, Nelson Green wrote:
On Thu, Jul 24, 2014 at 10:52 AM, B lazyvi...@gmx.com wrote:
On Thu, 24 Jul 2014 10:36:47 -0500
Nelson Green nelsongree...@gmail.com wrote:
Good morning all,
Good afternoon alone,
PC. I would like to be able to share his desktop to me so
My own view is why systemd fix sysinit instead, where it is
broken or rather the packages [whatever they are] that don't work properly.
systemd gives faster boot times, so what! I prefer to boot less often
and run with what works until I /have/ to do a reboot, so it wouldn't
matter if it
On 4/08/2014 9:04 PM, Lisi Reisz wrote:
On Monday 04 August 2014 09:44:31 Andrew McGlashan wrote:
I wonder about Kirby myself. To me, it shouldn't be the court deciding
a matter of fact via *their* opinion. If the law says xa and the
opinion says xb ... then it is up to the parliament
On 4/08/2014 9:13 PM, Jeff Bauer wrote:
The problem with quotes on the Internet is that it is hard to verify
their authenticity. - Abraham Lincoln
Now THAT is truly funny!
Thanks
A.
signature.asc
Description: OpenPGP digital signature
On 4/08/2014 10:03 PM, Raffaele Morelli wrote:
I've seen tons of posts sent to this list about systemd... bla bla
bla... and did not understand what's the matter with it.
I wonder what are you all doing with your init scripts which doesn't
work with systemd. So what?
If it isn't broken,
On 4/08/2014 11:35 PM, Raffaele Morelli wrote:
2014-08-04 15:11 GMT+02:00 Andrew McGlashan
andrew.mcglas...@affinityvision.com.au
mailto:andrew.mcglas...@affinityvision.com.au:
On 4/08/2014 10:03 PM, Raffaele Morelli wrote:
I've seen tons of posts sent to this list about systemd
On 4/08/2014 11:32 PM, Tom H wrote:
On Mon, Aug 4, 2014 at 6:37 AM, Andrew McGlashan
andrew.mcglas...@affinityvision.com.au wrote:
My own view is why systemd fix sysinit instead, where it is
broken or rather the packages [whatever they are] that don't work properly.
Who should fix
On 5/08/2014 5:44 AM, Erwan David wrote:
Le 04/08/2014 21:34, Tom H a écrit :
Going back to fix sysinit instead (which is what I was replying to),
did anyone add cgroup support to sysvinit so someone could tell
Lennart f-u, sysvinit can kill double-forked children?
For me that should be
On 4/08/2014 7:51 PM, Joel Rees wrote:
On Mon, Aug 4, 2014 at 3:53 PM, Andrew McGlashan
andrew.mcglas...@affinityvision.com.au wrote:
[...]
If you do the /dev/zero against a volume, then no useful data will
remain on that volume ... you need to backup that file system first,
then restore
On 10/08/2014 10:06 AM, Mike McClain wrote:
Please describe your network topology. Where's the Win2k box ?
__
| Debian| LAN| Windows 2000 |
Inet|Linux
On 20/08/2014 12:22 AM, Ralph Katz wrote:
Steve Gibson reports, Secure browser connections can be intercepted
and decrypted... Worth a look:
https://www.grc.com/fingerprints.htm
Got a good fingerprint in my browser, it matches from the Gibson tool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm going to address a number of things here
First off, I used to use this script [1], with an entry in /etc/rc.local
to kick it off on boot. My goal was to start the RAID1 array only if 2
members could be found (minimum), I added a 3rd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/09/2014 4:00 AM, Andrew McGlashan wrote:
First off, I used to use this script [1], with an entry
in /etc/rc.local to kick it off on boot. My goal was to start
the RAID1 array only if 2 members could be found (minimum), I
added a 3rd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Do I want systemd ?
- definitely and absolutely NO.
Is there any point arguing here in debian-user ?
- definitely NOT.
My view is that systemd is a forgone conclusion and no-one whom has
decided that it should be will be convinced otherwise.
it much earlier and it didn't come
through?? Are posts being moderated, posts that are not in line with
CTTE views?
On 5/10/2014 7:44 AM, John Hasler wrote:
Andrew McGlashan writes:
My view is that the Rabbit of Caerbannog is a forgone conclusion and
no-one whom hasdecided that it should
On 9/10/2014 10:40 AM, Andrew McGlashan wrote:
Hi,
$ sed 's/s.st.md/the Rabbit of Caerbannog/'
Bingo!!!
Definitely moderated posts!
:(
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Definitely moderated posts:
https://lists.debian.org/debian-user/2014/10/msg00602.html
https://lists.debian.org/debian-user/2014/10/msg00603.html
:(
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 9/10/2014 7:01 AM, Brian wrote:
No problem, just don't killfile incoming messages. Problem
solved.
But if you *do*, then say you did it and say why. Otherwise,
don't killfile incoming message.
From less than 7 days ago:
On Tue, Oct 07, 2014 at 06:52:20PM +0100, Brian wrote:
If you're not careful, the newspapers will have you hating the
people who are being oppressed, and loving the people who are
doing the oppressing. --- Malcolm X
Ironic signature there...
Isn't that how the /filtered/ posts are supposed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 9/10/2014 10:47 AM, Andrew McGlashan wrote:
On 9/10/2014 10:40 AM, Andrew McGlashan wrote:
Hi,
$ sed 's/s.st.md/killer bunny/'
* it looks like the filtering has been adjusted *
re-sending
The more I read about the use
On 10/10/2014 8:44 AM, James Ensor wrote:
But, to get more to the point of my original question, there has been
so much discussion about systemd here, but as far as I can tell very
little of this discussion has been of practical use for a debian-user.
Are you crazy, people are having problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/10/2014 2:01 AM, James Ensor wrote:
The point of this thread was to demonstrate that you *do* still have a
choice. It's relatively simple to remove systemd from your Debian
installation if you choose to.
In the short term, sure, but in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/10/2014 4:01 AM, James Ensor wrote:
What I was trying to say here is that people seem to want to debate
the philosophy/quality/whatever about systemd, and have used this to
come to wrong conclusions about the practical aspect of using an
On 13/10/2014 2:34 AM, Martin Read wrote:
On 12/10/14 15:53, lee wrote:
And when they are filtered, does the sender get a message telling him
that their message hasn't been delivered?
The requirement in RFC 2821 (the successor to RFC 821 which you've
recently been referring to) section
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/10/2014 3:45 AM, The Wanderer wrote:
My understanding is that the only filtering which has been stated to be
being used is not keyword-based, but thread-based. That is, if the post
is in a thread which has been added to the filter list,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/10/2014 4:22 AM, Andrei POPESCU wrote:
On Lu, 13 oct 14, 02:50:18, Andrew McGlashan wrote:
There is an amazing level of resistance to care what us users and
sysadmins think of the changes dictated by the vote of the Tech CTTE
On 13/10/2014 5:48 AM, Brian wrote:
On Mon 13 Oct 2014 at 05:02:15 +1100, Andrew McGlashan wrote:
Not a single one of these people have a *genuine* problem with systemd
on Debian. The first port of call for genuine problems with systemd is
the mailing list at pkg-systemd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/10/2014 9:04 AM, lee wrote:
Bas Wijnen wij...@debian.org writes:
Considering that the users are Debians' priority, couldn't this
issue be a case in which significant concerns from/of the users
about an issue might initiate a GR?
No.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/10/2014 11:21 PM, Thorsten Glaser wrote:
On Mon, 13 Oct 2014, Miles Fidelman wrote:
Those who are most impacted are sys admins of servers, and upstream
developers
I’m both, and I joined Debian to try to make an impact…
- the two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 4:24 AM, Curt wrote:
On 2014-10-13, Miles Fidelman mfidel...@meetinghouse.net wrote:
I'm really curious to know how many others here have come to a similar
conclusion, and what folks are looking at (in my case, SmartOS is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 5:29 AM, Jeroen Dekkers wrote:
Sysvinit-core was introduced in jessie and systemd-sysv conflicts with
sysvinit-core. Systemd-sysv is also available in wheezy, but there are
24486 reports from the popcon version 1.61
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 5:47 AM, Andrei POPESCU wrote:
On Lu, 13 oct 14, 12:34:27, Miles Fidelman wrote:
Again.. when did the desktop become the priority for Debian. For years,
Debian (and Linux in general) has been most useful in the server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 5:56 AM, Miles Fidelman wrote:
Andrei POPESCU wrote:
On Lu, 13 oct 14, 12:34:27, Miles Fidelman wrote:
Again.. when did the desktop become the priority for Debian. For years,
Debian (and Linux in general) has been most useful in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 6:43 AM, Andrei POPESCU wrote:
On Lu, 13 oct 14, 19:45:03, Anders Wegge Keller wrote:
It seems that there's a lot of controversy about the
SysV-replacement that should not be named. Most, if not all of
the arguments for, as well as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 5:49 AM, Steve Litt wrote:
If I were going to give up free software and go proprietary, I'd go
Mac. Unfortunately, at this point I'm actually considering Mac as my
final backstop.
Last I checked, Mac hadn't patch Shellshock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 6:53 AM, Andrei POPESCU wrote:
On Ma, 14 oct 14, 06:21:24, Andrew McGlashan wrote:
A default desktop install of Jessie will bring in Gnome and as a
result will also bring in systemd
Small correction here, just to make it 100
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 7:18 AM, Andrei POPESCU wrote:
On Ma, 14 oct 14, 06:53:12, Andrew McGlashan wrote:
That list is basically irrelevant, no traffic at all, virtually.
That only happens because people insist on posting off-topic stuff
to -user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 8:32 AM, John Hasler wrote:
Andrei POPESCU writes:
Without an accurate count I'd say only about 1% (or less) of the
subscribers are actually participating in these discussion.
1% participation in any discussion on a list such as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 8:19 AM, Andrei POPESCU wrote:
In my opinion this is the very definition of vocal minority.
Vocal minority, looking after the interests of many more whom will be
yet to learn of the facts at some stage. but otherwise have no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 9:11 AM, Brian wrote:
On Tue 14 Oct 2014 at 06:34:17 +1100, Andrew McGlashan wrote:
Although I'm up with patching, but I most definitely don't want any
system that I am responsible to maintain to have systemd installed, it
is far
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 9:50 AM, Joey Hess wrote:
Sysvinit will continue to be supported on servers in Debian 8
(jessie) release of Debian. So you can continue to boot your
production servers with sysvinit.
Okay, for now, that is until more packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 3:14 PM, Miles Fidelman wrote:
Joey Hess wrote:
Well I guess I'd find it a lot cleaner to make the choice as part of
installation, rather than have systemd installed as a default and then
have to uninstall it. I hate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 8:09 PM, Andrei POPESCU wrote:
aptitude search '?depends(^systemd$)'
# aptitude search '?depends(^systemd$)'
Wednesday 15 October 14:54:30 EST 2014 -- search ?depends(^systemd$)
p libpam-systemd
- system and service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/10/2014 11:01 PM, Richard Owlett wrote:
I suspect any list with offtopic in its name will get ignored when
there is a large number of people want to say something about a specific
topic.
Absolutely, it helps hide problems under the rug, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/10/2014 6:02 PM, Andrei POPESCU wrote:
ConsoleKit, unmaintained.
But fixed, for kFreeBSD
A.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iF4EAREIAAYFAlQ+ZOQACgkQqBZry7fv4vtv5gEAqxefTmCV1PLqwNWgJOGeFwGD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/10/2014 3:22 AM, Slavko wrote:
But e.g. my dbus package doesn't depends on systemd at all:
LANG=en aptitude show dbus | grep Depends -A2
Depends: libaudit1 (= 1:2.2.1), libc6 (= 2.17), libcap-ng0, libdbus-1-3 (=
1.7.6),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/10/2014 6:49 AM, Jonathan Dowland wrote:
reported bugs will get less attention nowtoo). But the consolekit
deprecation happened a long time before the tech-ctte decision
about systemd. Some one/people could have picked it up long ago.
If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Thanks for the cc in this case, your message never made it to the
list, it was /probably/ silently dropped changing the subject
line to see if it helps *this* message to get through ;-)
for the list *benefit* ... said email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/10/2014 4:30 AM, goli...@riseup.net wrote:
The fact that an executable is linked against a systemd library doesn't
automatically mean you have to run systemd as PID1.
This is especially true for the sd-daemon and sd-journal libraries in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/10/2014 10:24 PM, Laurent Bigonville wrote:
Andrew McGlashan wrote:
That is 100% true, I couldn't give a rats if it is PID1 or not. It IS
systemd, that's more than enough for me to want it OUT -- it's a
cancer that is spreading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I have a server that was upgraded from squeeze-lts to wheezy.
Since the upgrade, any mail coming from hotmail servers can no longer be
delivered to the server.
I see lots of errors like these in the /var/log/exim4/mainlog
TLS error on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 8/11/2014 7:51 PM, Mart van de Wege wrote:
The fact that the Constitution is being used to ram a GR down the
developers' throats two weeks before Jessie freeze may have a teensy bit
to do wit that?
Maybe so, but that in itself is sad. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
SOLVED ...
Short story:
regenerate exim.crt and exim.key
Turns out that most servers out in the world were happy with the re-use
of the old exim.crt and exim.key files.
These servers had problems until I created new key and cert files:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 9/11/2014 2:03 AM, Mart van de Wege wrote:
Andrew McGlashan andrew.mcglas...@affinityvision.com.au writes:
On 8/11/2014 7:51 PM, Mart van de Wege wrote:
The fact that the Constitution is being used to ram a GR down the
developers' throats
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2/11/2014 8:24 PM, Virgo Pärna wrote:
Ok problem is solved. I did have invalid lines in file: like that
209.85.128/17 line. And exim stops processing file, if it meets invalid
host line. I guess, that it was just coincidence, that it
Forwarding a message as is from another mailing list ... very relevant
to Linux and the systemd dilemma.
begin forward...
http://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html
On Fri, 30.05.14 04:32, Michael Biebl (mbiebl at gmail.com) wrote:
2014-05-30 4:26 GMT+02:00
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/11/2014 6:01 PM, Matthias Urlichs wrote:
Andrew McGlashan:
Forwarding a message as is from another mailing list ... very relevant
to Linux and the systemd dilemma.
No, it is not.
Sorry, but requiring an up-to-date kernel (or any other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/11/2014 7:38 PM, Matt Ventura wrote:
On 11/9/2014 11:01 PM, Matthias Urlichs wrote:
Andrew McGlashan:
Forwarding a message as is from another mailing list ... very relevant
to Linux and the systemd dilemma.
No, it is not.
Sorry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/11/2014 9:55 PM, Martin Read wrote:
On 10/11/14 08:57, Andrew McGlashan wrote:
And for those choosing to go with systemd they'll need 20 updates of
Jessie just because the kernel is intrinsically linked to systemd and
needs an update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/11/2014 11:49 PM, fsmithred wrote:
It seems to be working, so far, but as mentioned, it may break at some
point with upgrades. Others can try the same thing and share their
experiences. If you're willing to accept libsystemd0, then I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/11/2014 5:46 AM, Hans wrote:
--
You could at least spell the perp's name correctly if you are
going to come to his defense. It's LENNART!
Sorry for that, I hope he will not blame me for that. However, I
intended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/11/2014 1:11 AM, songbird wrote:
the vote is in.
let us thank each one of them for their efforts to continue making
Debian what it is:
a fractious and wonderful expression of free source code, the
ability to distribute such in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/11/2014 4:01 AM, golinux wrote:
My beloved Debian, RIP. Very sad that the ride will be over when when
Squeeze and Wheezy (and possibly Jessie - jury is still out) get to EOL
. . .
golinux
(soon to be linuxrip)
1
I am greatly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/11/2014 5:45 AM, Brian wrote:
The vast majority on debian-user see this list as being for the support
of users who *use* Debian and not a talking shop about it. Encouragement
to pervert its purpose is little short of bad manners, no matter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/11/2014 11:14 AM, John Hasler wrote:
Renaud (Ron) OLGIATI writes:
But they are anathema to the We are systemd of Borg, resistance is
futile crowd.
And then there is the Systemd is the Borg! Kill! Kill! crowd who jump
into every mention
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/11/2014 7:53 PM, Scott Ferguson wrote:
How many people subscribe to this list?
How many people follow the various reposting of this list?
Sorry Scott, you have absolutely no idea what you are talking about.
The assumptions you are making
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/11/2014 3:38 AM, John Hasler wrote:
Andrew McGlashan writes:
I DO NOT WANT SYSTEMD ON ANY SYSTEM THAT I ADMINISTRATE ... is
that so hard to understand?
What's hard to understand is why I should give a damn.
Ditto on why I should give
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/11/2014 4:17 AM, Jerry Stuckle wrote:
On 11/23/2014 11:43 AM, John Hasler wrote:
Andrew McGlashan writes:
You will never see the full picture of the problem if you only listen to
what is allowed to be received via the debian-user list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/11/2014 11:07 AM, Scott Ferguson wrote:
And *what do we know about the original customisation* that was
made - which may have 'some' bearing on the badness of the
upgrade/update defaults??
Oh, I get it, you think Debian is perfect and that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/11/2014 3:50 PM, Scott Ferguson wrote:
It would be nice if I could have used the time replying to your
obstreperous and bilious attack helping people with Debian
problems.
Unfortunately *systemd is very much now a Debian problem* going
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/11/2014 8:42 PM, Rainer Dorsch wrote:
blackbox:/etc/bind# cat /etc/systemd/system/bind9-resume.service
So ... buggy systemd bites yet again; and *some* [too many] people still
don't understand why we don't want this on our Debian (or other)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 1/01/2015 5:10 AM, Andrei POPESCU wrote:
On Mi, 31 dec 14, 09:45:53, Jerry Stuckle wrote:
I've never said anyone should be obliged to maintain Debian the
way I want. I said the way they are going is not acceptable, so
my clients are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 7/02/2015 12:01 PM, Curtis Vaughan wrote:
That seems to work, but here's a problem. Each time it enters a new user
directory I have to re-enter the root password. I realize I can just set
it up so that I don't have to enter a password at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Okay, you've had two supporting replies, that is virtually none.
I would like to say a BIG NO THANKS ... Debian is much less than it
was for me. You couldn't even bring yourself to say systemd, what's
wrong with saying it?
Now, just wait
it (partially caused by my
ignorance of systemd), I decided to take the leap - if nothing
else, to be able to honestly criticize it and actually know what
I was talking about.
On 18/02/15 20:29, Andrew McGlashan wrote:
You couldn't even bring yourself to say systemd, what's wrong
with saying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/02/2015 2:52 PM, Jack Chuge wrote:
I know it means nothing to me until I want to install CGoban, a go
client been maintaining by kgs(www.gokgs.com). And I found my debian
pre-installed a java version of 1.6.0, seems odd for ever.
Keep in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/02/2015 2:26 AM, Lisi Reisz wrote:
On Wednesday 18 February 2015 10:32:59 Martin Read wrote:
On 18/02/15 07:29, Andrew McGlashan wrote:
What I want from a DPL (another thread), is a DPL that will
remove systemd (for starters), particularly
On 30/03/2015 9:25 PM, Lisi Reisz wrote:
Any useful suggestions for what I could try? In my book, chuck systemd would
not count as useful. Though it has crossed my mind. :-(
You wouldn't be the first... to chuck systemd ... it's bad new ;-)
A.
--
To UNSUBSCRIBE, email to
On 31/03/2015 3:18 AM, Andrew McGlashan wrote:
On 31/03/2015 1:00 AM, Renaud (Ron) OLGIATI wrote:
http://distrowatch.com/weekly.php?issue=20150330#community
It's too early for an April fools joke, no matter where you live.
Or is it serious ?
Lennart Linux lives on give us back Linus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/03/2015 1:00 AM, Renaud (Ron) OLGIATI wrote:
http://distrowatch.com/weekly.php?issue=20150330#community
It's too early for an April fools joke, no matter where you live.
Or is it serious ?
Lennart Linux lives on give us back Linus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 1/04/2015 2:07 AM, bjf...@gmail.com wrote:
Reading Wikipedia- it says systemd was chosen as default on Jessie aft
er discussion over these mailing lists...
Is this wrong?
It is wrong to a great extent.
Most negative discussion of system was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 8/06/2015 4:55 AM, Francis Gerund wrote:
Does anyone here have any inside information on what is happening (or
not happening) with the Devuan project?
It seems to be dead, or at least dying.
Not so quick.
systemd is a huge mistake for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/06/2015 11:49 PM, Ansgar Burchardt wrote:
Andrew McGlashan andrew.mcglas...@affinityvision.com.au writes:
If it quacks like a duck, it's a duck, plain and simple.
I absolutely agree with the post that systemd is a cancer
And I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/06/2015 1:43 AM, Martin Read wrote:
On 22/06/15 15:32, Gene Heskett wrote:
But from the tone of the messages, I think its clear that it
should have spent another 6 months on the back table in a lab
someplace, getting the kinks worked out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/06/2015 12:31 AM, to...@tuxteam.de wrote:
But please, please: don't pour hate on people writing free
software. This is not helping anyone (well, it is helping those not
wanting free software to succeed!).
Unfortunately it's not that simple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/06/2015 5:38 AM, Ansgar Burchardt wrote:
chris tknch...@gmail.com writes:
systemd is a cancer that you should completely eradicate
especially on a system like that
Please follow Debian's Code of Conduct[1] (or just basic manners)
on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/06/2015 4:02 AM, Dan wrote:
Thanks a lot for your answers. I can not use intel because the
provider of our company only proposes AMD or NVIDIA for the
workstations.
I do not need a very fancy graphic card, I need something that
works.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 6/07/2015 2:44 AM, Alef Farah wrote:
On 2015-06-28 19:00, Don Armstrong wrote:
Contentless maligning of systemd and/or other parts of Debian are
not on topic on Debian mailing lists, and certainly not on topic
on -user. Please stop.
On the
301 - 400 of 611 matches
Mail list logo
