On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale <garyd...@torfree.net> writes:
I haven't had any significant problems with systemd but then I waited
several months before upgrading my servers to jessie and before
upgrading my workstation to stretch. Maybe it's because of MS-DO but
I've learned to wait for the .1 release before upgrading. :)
I actually ran into my first problem in ages when I reinstalled a
computer here.
It was supposed to run DHCP, and get a static assignment from the DHCP
server based on MAC, but when I booted it it hung on trying to start
rpcbind because the network wasn't up yet.
Only when I replaced the DHCP with a static IP assignment in
/etc/network/interfaces did things work.
Funny thing was that Jessie did just fine, it was upgrading to Sid from
a clean network install that broke things.
And on the gripping hand: I used to have this issue with SysV init, and
it went away when switching to systemd, I don't know why it returned
yet.
I was so stressed out that I didn't feel like troubleshooting it
further, hence no bug report. If someone wants me to file one, I can
troubleshoot next weekend.
Mart
Upgrading to sid is asking for trouble. Sid isn't called unstable for
nothing. I prefer to stick with stable for servers and testing for my
workstation (and then only because I like to keep reasonably current -
if I was running an enterprise, I'd stay with stable for the desktop and
use the occasional backport if there was something I really needed).
--
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/55b5aa3c.1090...@torfree.net
