Haines Brown <haines@???> writes:
> I have been running Debian Sid on a laptop with a purged systemd for
> quite a few months. Maybe when I now ran # aptitude update or
> safe-upgrade for the first time after several months since the Sid
> installation systemd-udevd seems to have switched my wireless interface
> from wlan0 to wlp3s0.

This comes from another attempt at using udev device renaming facilities
in order to work around udev device re-ordering with a couple of "be
nice to Dell" gimmicks thrown in (the guy who originally implemented
'encode bus layout in network device name' for Fedora had a @dell.com
e-mail address). Since that's a totally braindead idea only a hardware
clown could ever come up with[*], the best course of action would seem
to be to disable this. Reportedly, the boot parameter

net.ifnames=0

does that.

[*] The kernel is supposed to provide an abstract programming interface
    for the available hardware such that it's easily possible to write
    software which is at least portable to different computers running
    the same OS. But unfortunately, the days of FORTRAN being considered
    the abstract programming interface of IBM 704 mainframes and IBM 704
    mainframes only haven't ended everywhere and the systemd guys aren't
    the only people who are generally pissed of by every bit of
    technical progress which happened since ca 1965[**].

[**] Weren't it for the current popularity of ARM, someone would likely
     have considered to implement the whole piece of Brobdingnagian
     precision mechanic in "hand-optimized x86 machine code" instead of
     C ...

[...]

> Then I found that while root can run starx with no problem, when user
> does it the desktop comes up frozen along with mouse and keyboard
> input.

Debian has chosen to disable setuid-execution of the X server to make
the system more secure against unwarranted intrusions of the person who
wrongly believes to own it. Reportedly, the xserver-org-legacy package
can be installed to fix this.