On 14/07/14 01:23, Tom Horsley wrote:
On Sun, 13 Jul 2014 19:18:35 +0200
Timothy Murphy wrote:
I'm afraid it does not reassure me at all when Dan Williams says
he will be granting every wish you dream of.
Yea, and my wish and dream is that NetworkManager goes away,
and network simply gets
On Sun, Jul 13, 2014 at 8:50 PM, Sam Varshavchik mr...@courier-mta.com wrote:
Rahul Sundaram writes:
This is one of the things that NM addresses with plugins so you can pick
and choose which features you want out of it. Also by integrating with
existing tools, you don't have to go all or
On 14.07.2014 02:49, Kevin Fenzi wrote:
On Sun, 13 Jul 2014 20:37:40 -0400
Sam Varshavchik mr...@courier-mta.com wrote:
poma writes:
Besides why would anyone spend valuable time on outdated network
scripts on top of something called
poma writes:
Besides it's not the package per se,
$ rpm -q --whatprovides /usr/lib/systemd/systemd-networkd
systemd-215-4.git3864c28.20140711.fc21.x86_64
Even though it is not offered as part of the official Fedora stable repo, it
is still very possible.
I successfully tested it, not only
On 07/12/2014 11:38 PM, Joe Zeff wrote:
On 07/12/2014 02:10 PM, Bill Oliver wrote:
Yeah, I know. Thanks for that useful suggestion.
Any time. And, I wasn't even intending to be sarcastic. I wanted to
point out that, unlike Windows, if you don't like the way Linux works,
you're free in
On 07/12/2014 10:59 PM, Anders Wegge Keller wrote:
Sam Varshavchik mr...@courier-mta.com writes:
I think that systemd should not be fixed. I think it should be
dumped, and replaced. It's fundamentally broken, even without this
latest fallout. So, why would I want to report systemd bugs, and
Actually, I take this opportunity to thanks all systemd associates for their
great effort, commitment and understanding.
Godspeed.
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
poma pomidorabelis...@gmail.com writes:
Besides why would anyone spend valuable time on outdated network
scripts on top of something called
http://man7.org/linux/man-pages/man8/systemd-networkd.8.html
IMO, if you cannot think of applications, where systemd is
inappropriate, you do not have
On Sun, 13 Jul 2014 10:39:00 +0200
poma wrote:
Besides why would anyone spend valuable time on outdated network scripts
Probably because NetworkManager still has about 10 years to go
before it manages to replicate all the functionality of
network, and then another 10 years before users figure
On Sat, Jul 12, 2014 at 12:08 PM, Sam Varshavchik mr...@courier-mta.com wrote:
Tom Horsley writes:
On Sat, 12 Jul 2014 10:00:45 -0400
Sam Varshavchik wrote:
Now, here's my hack, which is basically a clone of that NetworkManager
subpackage:
You're willing to invest a lot more time in
On Sat, 2014-07-12 at 11:36 -0400, Tom Horsley wrote:
On Sat, 12 Jul 2014 10:00:45 -0400
Sam Varshavchik wrote:
Now, here's my hack, which is basically a clone of that NetworkManager
subpackage:
You're willing to invest a lot more time in systemd than
I am :-). I just put a batch of
as I know, systemd will start the *.service first! and then the sysvinit
scripts.
I think that can cause the problem. Maybe if you create a foo.service
which point to your sysvinit script and
set the right order in dependency list.
maybe, I'm just guessing.
On Sun, 2014-07-13 at 10:57
H
On Sun, Jul 13, 2014 at 8:53 AM, Tom Horsley wrote:
Probably because NetworkManager still has about 10 years to go
before it manages to replicate all the functionality of
network, and then another 10 years before users figure out
how to use it...
You haven't looked at the latest
Rahul Sundaram wrote:
You haven't looked at the latest release yet I guess
http://blogs.gnome.org/dcbw/2014/06/20/well-build-a-dream-house-of-net/
I'm afraid it does not reassure me at all when Dan Williams says
he will be granting every wish you dream of.
One of the problems with NM, in my
On Sun, 13 Jul 2014 19:18:35 +0200
Timothy Murphy wrote:
I'm afraid it does not reassure me at all when Dan Williams says
he will be granting every wish you dream of.
Yea, and my wish and dream is that NetworkManager goes away,
and network simply gets better support for wi-fi, which should
Hi
On Sun, Jul 13, 2014 at 1:18 PM, Timothy Murphy wrote:
One of the problems with NM, in my view, is that it tries to do too much.
This is one of the things that NM addresses with plugins so you can pick
and choose which features you want out of it. Also by integrating with
existing
On Sat, Jul 12, 2014 at 3:16 PM, Sam Varshavchik mr...@courier-mta.com wrote:
Tom H writes:
NetworkManager-wait-online.service has:
begin
After=NetworkManager.service
Wants=network.target
Before=network.target network-online.target
/end
Perhaps you should replicate that in
poma writes:
Besides why would anyone spend valuable time on outdated network scripts on
top of something called
http://man7.org/linux/man-pages/man8/systemd-networkd.8.html
yum is unable to find this package. As such, even if it's the greatest thing
since sliced bread, it means nothing
Tom H writes:
On Sat, Jul 12, 2014 at 12:08 PM, Sam Varshavchik mr...@courier-mta.com
wrote:
Tom Horsley writes:
On Sat, 12 Jul 2014 10:00:45 -0400
Sam Varshavchik wrote:
Now, here's my hack, which is basically a clone of that NetworkManager
subpackage:
You're willing to invest a lot
Rahul Sundaram writes:
On Sun, Jul 13, 2014 at 1:18 PM, Timothy Murphy wrote:
One of the problems with NM, in my view, is that it tries to do too much.
This is one of the things that NM addresses with plugins so you can pick and
choose which features you want out of it. Also by
On Sun, 13 Jul 2014 20:37:40 -0400
Sam Varshavchik mr...@courier-mta.com wrote:
poma writes:
Besides why would anyone spend valuable time on outdated network
scripts on top of something called
http://man7.org/linux/man-pages/man8/systemd-networkd.8.html
yum is unable to find this
It appears that the entire Linux world hates your guts so perhaps you
might consider buying a Mac and using Mac OS X?
At the very least might I suggest the you STFU? Since you appear to
not be smart enough to deal with this.
Gee. Are there no moderators here?
On Sun, Jul 13, 2014 at 8:50 PM,
On Sun, 13 Jul 2014 21:01:35 -0400
David Boles thetinsm...@gmail.com wrote:
It appears that the entire Linux world hates your guts so perhaps you
might consider buying a Mac and using Mac OS X?
At the very least might I suggest the you STFU? Since you appear to
not be smart enough to deal
07/13/2014 06:01 PM, David Boles wrote:
It appears that the entire Linux world hates your guts so perhaps you
might consider buying a Mac and using Mac OS X?
At the very least might I suggest the you STFU? Since you appear to
not be smart enough to deal with this.
Gee. Are there no moderators
So then tell me where the heck have you have been for the past several
weeks? All the time this user has been whining and crying over this 3
or so year old change that he can not comprehend.?
On Sun, Jul 13, 2014 at 9:06 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sun, 13 Jul 2014 21:01:35 -0400
On Sun, 13 Jul 2014 21:38:33 -0400
David Boles thetinsm...@gmail.com wrote:
So then tell me where the heck have you have been for the past several
weeks? All the time this user has been whining and crying over this 3
or so year old change that he can not comprehend.?
I was not a moderator for
David Boles writes:
It appears that the entire Linux world hates your guts so perhaps you
might consider buying a Mac and using Mac OS X?
At the very least might I suggest the you STFU? Since you appear to
not be smart enough to deal with this.
Gee. Are there no moderators here?
Mr. Boles,
Now that I have your attention, the background is as follows. This is a
server with only statically configured network interfaces. NetworkManager is
not installed. All network interfaces are statically configured via
/etc/sysconfig/network-scripts.
The server is regularly updated to
On Sat, 12 Jul 2014 10:00:45 -0400
Sam Varshavchik wrote:
Now, here's my hack, which is basically a clone of that NetworkManager
subpackage:
You're willing to invest a lot more time in systemd than
I am :-). I just put a batch of systemctl restart commands in
the rc.local file with different
On Jul 12 10:00, Sam Varshavchik wrote:
Now that I have your attention, the background is as follows. This is a
server with only statically configured network interfaces. NetworkManager is
not installed. All network interfaces are statically configured via
/etc/sysconfig/network-scripts.
Corinna Vinschen writes:
On Jul 12 10:00, Sam Varshavchik wrote:
Now that I have your attention, the background is as follows. This is a
server with only statically configured network interfaces. NetworkManager
is
not installed. All network interfaces are statically configured via
Tom Horsley writes:
On Sat, 12 Jul 2014 10:00:45 -0400
Sam Varshavchik wrote:
Now, here's my hack, which is basically a clone of that NetworkManager
subpackage:
You're willing to invest a lot more time in systemd than
I am :-). I just put a batch of systemctl restart commands in
the
So, I would encourage you to ask the systemd list:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
for a probably more detailed answer than you might get here.
Or... file a bug if you think you have found one.
Kevin Fenzi writes:
So, I would encourage you to ask the systemd list:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
for a probably more detailed answer than you might get here.
There's a very specific reason why I don't wish to do that.
Or... file a bug if you think you have
On Sat, Jul 12, 2014 at 10:00 AM, Sam Varshavchik mr...@courier-mta.com wrote:
Now that I have your attention, the background is as follows. This is a
server with only statically configured network interfaces. NetworkManager is
not installed. All network interfaces are statically configured
On Jul 12 12:01, Sam Varshavchik wrote:
Corinna Vinschen writes:
[something]
This is certainly a valid workaround for the bug.
But this wasn't my point. I am looking for validation, based on the data I
posted, that systemd's dependency resolution is broken.
[...]
Hmm, ok. Let's try.
On 07/12/14 09:43, Kevin Fenzi wrote:
So, I would encourage you to ask the systemd list:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
for a probably more detailed answer than you might get here.
Or... file a bug if you think you have found one.
On Sat, 12 Jul 2014, Edward M wrote:
On 07/12/14 09:43, Kevin Fenzi wrote:
So, I would encourage you to ask the systemd list:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
for a probably more detailed answer than you might get here.
Or... file a bug if you think you have
On Sat, 12 Jul 2014 13:05:59 -0400
Sam Varshavchik mr...@courier-mta.com wrote:
Kevin Fenzi writes:
So, I would encourage you to ask the systemd list:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
for a probably more detailed answer than you might get here.
There's a
On Sat, 12 Jul 2014 18:43:34 + (UTC)
Bill Oliver ven...@billoblog.com wrote:
On Sat, 12 Jul 2014, Edward M wrote:
On 07/12/14 09:43, Kevin Fenzi wrote:
So, I would encourage you to ask the systemd list:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
for a probably
Tom H writes:
NetworkManager-wait-online.service has:
begin
After=NetworkManager.service
Wants=network.target
Before=network.target network-online.target
/end
Perhaps you should replicate that in wait-for-network.service for it
to behave as you intend it.
I assume that you can replicate
Kevin Fenzi ke...@scrye.com writes:
What would you suggest people do when they find a bug? Reporting it
to the people who can fix it is very much more likely to get it
fixed or worked around than complaining about it in a place where no
one will fix it.
Seeing the recent reactions in this
On 12.07.2014, Bill Oliver wrote:
But then, I guess Gentoo is the only distro left
that hasn't adopted systemd, or will be doing so shortly.
You could run Arch with openrc..
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
On 07/12/2014 12:52 PM, Anders Wegge Keller wrote:
I'm affected by a systemd bug, that I have no intention of
reporting. My workaround takes me far less time, than getting through
the endless layers of fanboys would.
You don't care, then, that if you're affected by this bug others are and
On 12 Jul 2014 21:52:22 +0200
Anders Wegge Keller we...@wegge.dk wrote:
Kevin Fenzi ke...@scrye.com writes:
What would you suggest people do when they find a bug? Reporting it
to the people who can fix it is very much more likely to get it
fixed or worked around than complaining about
Joe Zeff j...@zeff.us writes:
On 07/12/2014 12:52 PM, Anders Wegge Keller wrote:
I'm affected by a systemd bug, that I have no intention of
reporting. My workaround takes me far less time, than getting through
the endless layers of fanboys would.
You don't care, then, that if you're
On 07/12/2014 01:20 PM, Anders Wegge Keller wrote:
Why bother? When trying to diagnose the problem, I found several
well-documented bug reports with the soame contet. Some were almost
old enough to get rid of their diapers. They haven't been resolved, so
why should I spend time on another
Kevin Fenzi ke...@scrye.com writes:
On 12 Jul 2014 21:52:22 +0200
Anders Wegge Keller we...@wegge.dk wrote:
Kevin Fenzi ke...@scrye.com writes:
What would you suggest people do when they find a bug? Reporting it
to the people who can fix it is very much more likely to get it
On 12 Jul 2014 22:24:13 +0200
Anders Wegge Keller we...@wegge.dk wrote:
I'm not following your logic here.
Given 2 ways of reacting to a bug:
A) complain about it on a users mailing list that few developers
follow.
B) report a bug on it that developers will see and be able to
Joe Zeff j...@zeff.us writes:
On 07/12/2014 01:20 PM, Anders Wegge Keller wrote:
Why bother? When trying to diagnose the problem, I found several
well-documented bug reports with the soame contet. Some were almost
old enough to get rid of their diapers. They haven't been resolved, so
Kevin Fenzi writes:
On 12 Jul 2014 22:24:13 +0200
Anders Wegge Keller we...@wegge.dk wrote:
I'm not following your logic here.
Given 2 ways of reacting to a bug:
A) complain about it on a users mailing list that few developers
follow.
B) report a bug on it that developers will see
On 07/12/2014 11:43 AM, Bill Oliver wrote:
I really am starting to see this as an example of the Microsoft-ish
philosophy of tell the users where they must go and let them catch up
as they can. It works when the users don't have any other choice. But
then, I guess Gentoo is the only distro
On 07/12/2014 01:34 PM, Anders Wegge Keller wrote:
In this case, the wheel will get a pail of water, when the squeek
starts smoldering. So - even if I jinx my effort by stating the
intention - my best option is angst-inducing vague posts on a
non-technical mailing list.
I may well be wrong,
On 12.07.2014, Anders Wegge Keller wrote:
C) Report a bug and be ignored, told to fsck off to someplace else,
and be ridiculed to boot.
I fully understand your reaction.
I reported a (quite different) bug with systemd and got zero
response. After some (longer) time, I finally got a
Sam Varshavchik mr...@courier-mta.com writes:
I think that systemd should not be fixed. I think it should be
dumped, and replaced. It's fundamentally broken, even without this
latest fallout. So, why would I want to report systemd bugs, and
help improve it? I can't think of any reason why I'd
On Sat, 12 Jul 2014 13:45:56 -0700
Joe Zeff wrote:
put in
what you think an old-school linux should have and call it Steampunk
Linux to grab a bit of glamour
No, call it potskedeerf linux, and make the guiding principle
be that nothing advocated by freedesktop is included in the
distro :-).
Joe Zeff j...@zeff.us writes:
On 07/12/2014 01:34 PM, Anders Wegge Keller wrote:
In this case, the wheel will get a pail of water, when the squeek
starts smoldering. So - even if I jinx my effort by stating the
intention - my best option is angst-inducing vague posts on a
non-technical
On 12 Jul 2014 22:59:31 +0200
Anders Wegge Keller we...@wegge.dk wrote:
Sam Varshavchik mr...@courier-mta.com writes:
I think that systemd should not be fixed. I think it should be
dumped, and replaced. It's fundamentally broken, even without this
latest fallout. So, why would I want to
On Sat, 12 Jul 2014, Joe Zeff wrote:
On 07/12/2014 11:43 AM, Bill Oliver wrote:
I really am starting to see this as an example of the Microsoft-ish
philosophy of tell the users where they must go and let them catch up
as they can. It works when the users don't have any other choice. But
On 07/12/2014 02:10 PM, Bill Oliver wrote:
Yeah, I know. Thanks for that useful suggestion.
Any time. And, I wasn't even intending to be sarcastic. I wanted to
point out that, unlike Windows, if you don't like the way Linux works,
you're free in every sense of the word to Do Something
Hi Sam,
I don't know anything about Systemd, nor have I read the rest of
the responses to this, but just looking at the logical interpretation of
your named-chroot.service statements it seems to me that you are
requesting that named-chroot.service be started after network.target but
Stephen Morris writes:
Hi Sam,
I don't know anything about Systemd, nor have I read the rest of the
responses to this, but just looking at the logical interpretation of your
named-chroot.service statements it seems to me that you are requesting that
Well, technically it's not my
62 matches
Mail list logo
