Thank you all who made Debian 9 possible. It has been stellar in performance since install. I could not be happier with this distro. Thanks again to you all.
Bill
NFT5 wrote:A truly great distro. Is it?
Would have changed the UUID of Swap, had I not prevented it. Another fail that would have meant more manual setting up and newbies would be wondering about ridiculous load times.
systemd-analyze
Startup finished in 3.511s (kernel) + 10.448s (userspace) = 13.960s
Lysander wrote:It's perfectly understandable that you have had issues with Stretch but it would be nice if we kept this thread positive. This isn't really the place for a diatribe on the problems with Debian 9 and why you don't like it, neither is it the right place to encourage a back-and-forth debate on its demerits.
None1975 wrote:Maybe you do something very wrong, or should stay in Ubuntu land....
chris@BOSSDESK:~$ systemd-analyze
Startup finished in 1.898s (kernel) + 2.211s (userspace) = 4.110s
NFT5 wrote:Even Ubuntu 16.04 did a better job of installing and configuring and, like MX-16, is far better aimed at the desktop user, provided you can get past their insistence on sudo for everything which is nearly as bad as MX-16's need to become root to even scratch your nose.
NFT5 wrote:
Why? I was under the impression that this was a forum where open discussion was not discouraged and that aspects of this distribution that we use could be talked about in a sensible way. What better place to bring a point of balance than a thread which, if allowed to continue in such a way as you seem to propose would have us seen as no more than ostriches, burying our heads in the sand to avoid seeing or hearing facts that we don't want to acknowledge.
Would it not seem equally ridiculous if we were to have a separate thread where the shortcomings of Stretch were allowed, but any positive comments not?
NFT5 wrote:Fact: If you have a machine with an existing swap partition and take the default Debian (or most other Linux distros) installation, it will format that partition and a new UUID will be allocated. When this happens and you start one of the other distros it will go looking for the old swap UUID and continue to look for it for some 90 seconds, after which it will give up. The solution is to correct the UUID in /etc/fstab, following which the problem will not recur.
# swap was on /dev/sda3 during installation
UUID=1ed583c1-e6a3-43e5-997e-f6c83c1b1c78 none swap sw 0 0
# swap was on /dev/sda3 during installation
/dev/sda3 none swap sw 0 0
Users browsing this forum: No registered users and 13 guests