What's new in the Buster release?
Buster (Debian 10) is not released yet. This page is barely scratching the surface, and anything in the current buster (testing) release is subject to change. See the official (but still in-progress) buster release notes and buster issues/warnings for additional information.
AppArmor enabled by default (so far...)
Wayland is the default session type for GNOME 3.
- Kernel new enough to support mounting SMBv3 encrypted shares
- Tool "find-dbgsym-packages" (in package debian-goodies)
The su command in buster is provided by the util-linux source package, instead of the shadow source package, and no longer alters the PATH variable by default. This means that after doing su, your PATH may not contain directories like /sbin, and many system administration commands will fail. There are several workarounds:
Use su - instead; this launches a login shell, which forces PATH to be changed, but also changes everything else including the working directory.
Use sudo instead. sudo still runs commands with an altered PATH variable.
To get a regular root shell with the correct PATH, you may use sudo -s.
To get a login shell as root (equivalent to su -), you may use sudo -i.
Put ALWAYS_SET_PATH yes in /etc/login.defs to get an approximation of the old behavior.
Put the system administration directories (/sbin, /usr/sbin, /usr/local/sbin) in your regular account's PATH (see EnvironmentVariables for help with this).
The default Wayland session for GNOME stops some packages like synaptic from working. Graphical system administration packages that need superuser privileges will generally be problematic until major rewrites occur. Workarounds include using GNOME on X11 instead of Wayland, or using non-graphical alternative tools.
The security settings for some components of systemd have been tightened. People using nis with systemd may encounter bug 878625 which breaks a variety of things related to login sessions. Workarounds include installing the nscd package, or reconfiguring systemd-logind.service to allow it to use the network.
If you use the nis client (ypbind), you must make sure that the YPBINDARGS= option in /etc/default/nis does not include -no-dbus. The upgrade will not modify this file, and if the -no-dbus option remains present, ypbind will fail to start, and you may not be able to login. See also: bugs 906436, 834298.
So, is anything in Buster new with respect to Stretch, aside from fixed bugs and security atrociousness? I suspect there's lots of changes between Stretch and Buster in the system's server daemons, but far less noticeable from the user interface point of view. I guess the devs may weigh in here sometime (presuming they care about this and care to notice this ), when they understand what upstream's been up to lately.
- Buster has a new linux kernel in it that appears to support Encrypted SMBv3 shares mounted via CIFS/SMB. This was verified by mounting a share from a Netapp on which Encrypted SMB3 was required. Buster was able to mount this fine owing to the newer kernel.
Thu., 29 Mar., 2018, drat & damnit! stellarium: Insufficient OpenGL version. Grr.
I've recently been told that my /etc/apt/sources.list in testing (buster) need only contain one line (possibly two; add a deb-src line if useful, and non-free on the end (of each) if you wish):
deb http://deb.debian.org/debian/ buster main contrib
Security fixes aren't really supported on testing (they're being tested there, silly ) and backports are not a testing sort of thing; testing gets new stuff, to test! Even meltdown didn't cause testing's security repositories to be used.
Wed., 10 Jan., apt upgrade hung at 99%. Logging into another xterm or CTRL-C in original xterm did little, so I frobbed it and followed up with dpkg --configure -a, and it worked, and all is running sweet since. Curious. !@#$ happens, Debian recovers, Shootzy scores!
Sat. 16 Dec., seen this? kernel: [18046.426631] perf: interrupt took too long (6127 > 6121), lowering kernel.perf_event_max_sample_rate to 32500 Well, apparently, it's nothing. I worried that it was sound on my box related; I was noticing slowness and thought this might be related and that I might help it be less confused. Nope, irrelevant to that situation; great! Testing, testing, 1, 2, 3.
Sun. 3 Dec., "apt upgrade" failed. In IRC (#debian-next on irc.oftc.net) I learned how to get it all fixed and happy again with "apt install gnustep-base-common", which was followed by a successful "apt update && apt upgrade". I don't know why (yet! ) apt was failing in the update instead of just handling it automatically, but it's all fixed up now. "... from the time i mentioned it here to cleanly updated and upgraded: 25 min. i wonder how long that would have taken in ms and apple land. tres cool." Looking back over it now, that was a really fun episode. I learned a lot, and did a lot of stuff I've been holding off for a while.
I thought Stretch the best Linux and Debian I've ever used. Now Buster inherits that. I love the ride. Have fun!