Re: The Simple Things in Life
On Tue, 2016-07-19 at 15:01 -0700, Markus Lankeit wrote: > Adding my $0.02... > > If you pick "samba file server" during install, libnss-winbind > libpam-winbind are not installed by default. It took me a long to > time to track down why in 16.04 I can "join" an AD domain just fine, > but domain users get "access denied" to samba file shares. Not sure > the logic behind not installing relevant packages... > To be fair, configuring Samba is non-trivial, and I often think joining a domain as a member rather than a domain controller is some incidental feature that's a prerequisite for being a domain controller. Samba doesn't seem to support being a domain member very well at all, to the point that searching on errors and asking Google how to get a Samba domain member to authenticate to a different domain controller (because you joined on a RWDC network and now need to authenticate against a RODC) brings up documentation on configuring Samba as a domain controller. I configure Samba all the time; I have no idea how it works, and when it breaks I'm lost. To put this into perspective, I know how *everything* works, and when it breaks I can project the entire configuration and behavior and identify something I probably should have seen before--something unfamiliar, which I haven't inspected, but which I was able to assembly by simply throwing the state together in my head and making myself aware that some problem exists somewhere. I have NO IDEA why my Linux servers can authenticate to Active Directory; I just know I did things to PAM and nsswitch.conf and repeatedly ran a dozen forms of net join until, despite consistently throwing errors and failing, the server magically started authenticating. More basically, Samba can be a Samba file server without joining an AD domain. > Also, the whole network device naming scheme is just a fiasco... > Before, I could have a simple template for all my systems... now > every system requires a unique template that takes me to the HW > level to figure out what it might be. And this is supposed to be > more intuitive and/or predictable than "eth0"? > > > > Thx. > > > > -ml > > > > > On 7/19/2016 2:48 PM, John Moser wrote: > > > > > > > > > > On Tue, 2016-07-19 at 14:29 -0700, Jason Benjamin wrote: > > > > > > > > > > > > > I've > > > been irritated by so many obvious shortcomings of Ubuntu this > > > version (16.04). So many of the most obvious fixes are easily > > > attributed to configuration files. I don't know if those who > > > purchase the operating system directly from Canonical versus a > > > download are having to deal with the same problems or are > > > getting a supe> > > rior/better operating system. > > > operating system. > > > Some of my main qualms that I am unable to deal with are the > > > theming. Even using alternative themes most of them won't > > > even look right as supposed. > > > > > > > > > The > > > HIBERNATION itself seems to work fine on other closely related > > > distros (Elementary OS I tested). but Ubuntu has problems > > > with it. AFAIK the GRUB_CMDLINE breaks this if anything, and > > > alternatives such as TuxOnIce don't work either. My guess is > > > that its Plymouth and there doesn't seem to be any clear > > > pointers to a solution. After desktop session saving was > > > deprecated (or removed because of transition from Gnome?), > > > this seems like a serious and necessary *implementation* of > > > desktop application saving. > > > > > > > > > I've > > > seen a lot of these blogs that suggest installing extra > > > programs and such after the installation. Here's mine: > > > > > > > > > > > > > > > > > > > > You just listed a bunch of odd things about hiding the boot > > process. > > > > > > > > > > > > > > I've been repeatedly distressed and confused by this hidden > > boot process. I've sat and waited at blank screens and splashes > > that give no feedback, wondering if the kernel is hanging at > > initializing a driver, trying to find network, or making > > decisions about a disk. There is no standard flow which can be > > disrupted with a new, non-error status message curtly explaining > > that something is happening and all is well; there is a standard > > flow in which the machine displays a blank, meaningless state > > for a fixed amount of time, and deviation in that time by any > > more than a few tenths of a second gives the immediate, > > gut-wrenching feeling that the system has hanged during boot and > > is terminally broken in some
Re: The Simple Things in Life
On 19.07.2016 [15:01:46 -0700], Markus Lankeit wrote: > Adding my $0.02... > > If you pick "samba file server" during install, libnss-winbind > libpam-winbind are not installed by default. It took me a long to time to > track down why in 16.04 I can "join" an AD domain just fine, but domain > users get "access denied" to samba file shares. Not sure the logic behind > not installing relevant packages... Thanks for bringing this up -- I think this is due to libpam-smbpass being removed/deprecated and being replaced with libpam-winbind. I will file a post-release FFe bug (unless you've already filed a bug?) to change the seed for xenial, we'll see what happens. I've already updated the 16.10 seeds to install libpam-winbind. Note that earlier Ubuntu releases did not require (I'm guessing?) libnss-winbind (libpam-winbind suggests it, but doesn't require it). In your environment, is it strictly necessary in order to join the AD domain? Thanks, Nish -- Nishanth Aravamudan Ubuntu Server Canonical Ltd -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: The Simple Things in Life
Adding my $0.02... If you pick "samba file server" during install, libnss-winbind libpam-winbind are not installed by default. It took me a long to time to track down why in 16.04 I can "join" an AD domain just fine, but domain users get "access denied" to samba file shares. Not sure the logic behind not installing relevant packages... Also, the whole network device naming scheme is just a fiasco... Before, I could have a simple template for all my systems... now every system requires a unique template that takes me to the HW level to figure out what it might be. And this is supposed to be more intuitive and/or predictable than "eth0"? Thx. -ml On 7/19/2016 2:48 PM, John Moser wrote: On Tue, 2016-07-19 at 14:29 -0700, Jason Benjamin wrote: I've been irritated by so many obvious shortcomings of Ubuntu this version (16.04). So many of the most obvious fixes are easily attributed to configuration files. I don't know if those who purchase the operating system directly from Canonical versus a download are having to deal with the same problems or are getting a *supe**rior*//better/ operating system. Some of my main qualms that I am unable to deal with are the theming. Even using alternative themes most of them won't even look right as supposed. The HIBERNATION itself seems to work fine on other closely related distros (Elementary OS I tested). but Ubuntu has problems with it. AFAIK the GRUB_CMDLINE breaks this if anything, and alternatives such as TuxOnIce don't work either. My guess is that its Plymouth and there doesn't seem to be any clear pointers to a solution. After desktop session saving was deprecated (or removed because of transition from Gnome?), this seems like a serious and necessary *implementation* of desktop application saving. I've seen a lot of these blogs that suggest installing extra programs and such after the installation. Here's mine: You just listed a bunch of odd things about hiding the boot process. I've been repeatedly distressed and confused by this hidden boot process. I've sat and waited at blank screens and splashes that give no feedback, wondering if the kernel is hanging at initializing a driver, trying to find network, or making decisions about a disk. There is no standard flow which can be disrupted with a new, non-error status message curtly explaining that something is happening and all is well; there is a standard flow in which the machine displays a blank, meaningless state for a fixed amount of time, and deviation in that time by any more than a few tenths of a second gives the immediate, gut-wrenching feeling that the system has hanged during boot and is terminally broken in some mysterious and completely-unknown manner. What Ubuntu needs most is a simple, non-buried toggle option to show the boot process--including displaying the bootloader, displaying the kernel load messages, and listing which services are loading and already-loaded during the graphical boot. Ubuntu's best current feature is the Recovery boot mode, aside from not having a setting to make this the standard boot mode sans the recovery prompt. "Blindside the user with a confusing and meaningless boot process and terror at a slight lag in boot time because the system may be broken" is not a good policy for boot times longer than 1 second. Even Android displays a count of system assemblies AOT cached during boots after update so as to convey to the user that something is indeed happening. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: The Simple Things in Life
John Moser schreef op 19-07-2016 23:48: What Ubuntu needs most is a simple, non-buried toggle option to show the boot process--including displaying the bootloader, displaying the kernel load messages, and listing which services are loading and already-loaded during the graphical boot. Ubuntu's best current feature is the Recovery boot mode, aside from not having a setting to make this the standard boot mode sans the recovery prompt. "Blindside the user with a confusing and meaningless boot process and terror at a slight lag in boot time because the system may be broken" is not a good policy for boot times longer than 1 second. It's really quite obvious isn't it. But you don't need to see everything. See currently it is either all or nothing and that is how many people seem to think. Either you see a splash screen with no information at all (save perhaps an encryption message or a leaked-through kernel command line bug or error during the boot process) or you see all of the systemd services starting and perhaps much more information as well. Why not divide the boot process in 5 or 6 stages and then show the user when each stage has been completed? SystemD already has stages (targets) but it was not really meant for humans. I mean how obvious is it that "one state" (such as the desktop being loaded) is not informative enough, while "1000 states" may be much too informative? When do people learn to find the middle road? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: The Simple Things in Life
On Tue, 2016-07-19 at 14:29 -0700, Jason Benjamin wrote: > I've been irritated by so many obvious shortcomings of Ubuntu this > version (16.04). So many of the most obvious fixes are easily > attributed to configuration files. I don't know if those who > purchase the operating system directly from Canonical versus a > download are having to deal with the same problems or are getting a > superior/better operating system. Some of my main qualms that I am > unable to deal with are the theming. Even using alternative themes > most of them won't even look right as supposed. > The HIBERNATION itself seems to work fine on other closely related > distros (Elementary OS I tested). but Ubuntu has problems with it. > AFAIK the GRUB_CMDLINE breaks this if anything, and alternatives > such as TuxOnIce don't work either. My guess is that its Plymouth > and there doesn't seem to be any clear pointers to a solution. After > desktop session saving was deprecated (or removed because of > transition from Gnome?), this seems like a serious and necessary > *implementation* of desktop application saving. > I've seen a lot of these blogs that suggest installing extra programs > and such after the installation. Here's mine: You just listed a bunch of odd things about hiding the boot process. I've been repeatedly distressed and confused by this hidden boot process. I've sat and waited at blank screens and splashes that give no feedback, wondering if the kernel is hanging at initializing a driver, trying to find network, or making decisions about a disk. There is no standard flow which can be disrupted with a new, non-error status message curtly explaining that something is happening and all is well; there is a standard flow in which the machine displays a blank, meaningless state for a fixed amount of time, and deviation in that time by any more than a few tenths of a second gives the immediate, gut-wrenching feeling that the system has hanged during boot and is terminally broken in some mysterious and completely-unknown manner. What Ubuntu needs most is a simple, non-buried toggle option to show the boot process--including displaying the bootloader, displaying the kernel load messages, and listing which services are loading and already-loaded during the graphical boot. Ubuntu's best current feature is the Recovery boot mode, aside from not having a setting to make this the standard boot mode sans the recovery prompt. "Blindside the user with a confusing and meaningless boot process and terror at a slight lag in boot time because the system may be broken" is not a good policy for boot times longer than 1 second. Even Android displays a count of system assemblies AOT cached during boots after update so as to convey to the user that something is indeed happening.-- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
The Simple Things in Life
I've been irritated by so many obvious shortcomings of Ubuntu this version (16.04). So many of the most obvious fixes are easily attributed to configuration files. I don't know if those who purchase the operating system directly from Canonical versus a download are having to deal with the same problems or are getting a superior/better operating system. Some of my main qualms that I am unable to deal with are the theming. Even using alternative themes most of them won't even look right as supposed. The HIBERNATION itself seems to work fine on other closely related distros (Elementary OS I tested). but Ubuntu has problems with it. AFAIK the GRUB_CMDLINE breaks this if anything, and alternatives such as TuxOnIce don't work either. My guess is that its Plymouth and there doesn't seem to be any clear pointers to a solution. After desktop session saving was deprecated (or removed because of transition from Gnome?), this seems like a serious and necessary *implementation* of desktop application saving. I've seen a lot of these blogs that suggest installing extra programs and such after the installation. Here's mine: Top real things to do after installing Ubuntu 16.04 LTS: Fix splash at boot up while root create file /etc/initramfs-tools/conf.d/splash and add the line: FRAMEBUFFER=y then run sudo update-initramfs -u [-k all] “-k all” refers to checking all graphics cards Alternative recourse if the previous splash fix doesn’t cover everything Comment out GRUB_HIDDEN_TIMEOUT and GRUB_HIDDEN_TIMEOUT_QUIET lines (both deprecated) uncomment GRUB_TIMEOUT (preferably set to 0) and add ‘GRUB_TIMEOUT_STYLE=hidden’ add boot option ‘fastboot’ to /etc/default/grub (to hide file system clean message at boot) add ‘GRUB_GFXPAYLOAD_LINUX=keep’ to same file run sudo update-grub Disable upstart entry in grub menu as root edit /etc/grub.d/10_linux and find line SUPPORTED_INITS and remove the option ‘upstart:/sbin/upstart’ run sudo update-grub Remove Guest account from login create new file /etc/lightdm/lightdm.conf and add following lines: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu allow-guest=false Fix event sounds for startup open startup applications and add “canberra-gtk-play -i desktop-login &” as root in /etc/lightdm/lightdm.conf add the line: “session-cleanup-script=/usr/share/gnome/shutdown/libcanberra-logout-sound.sh” Enable hibernate First make sure your swap partition is large enough the kernel that comes with Ubuntu is behind and has a bug that causes hibernate to crash when in practical situations go to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.8-wily download and install kernel headers and image remove any older kernel packages run sudo blkid and determine swap UUID ensure UUID is the same in /etc/initramfs-tools/conf.d/resume add the same line to /etc/default/grub at the end of GRUB_CMDLINE_LINUX_DEFAULT or to GRUB_CMDLINE_LINUX run sudo update-grub and sudo update-initramfs -u while root create /var/lib/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla and add following lines: [Re-enable hibernate by default in upower] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes [Re-enable hibernate by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.hibernate-multiple-sessions ResultActive=yes As root edit /usr/share/X11/xkb/symbols/inet and change XF86Hibernate key to and comment out XF86Suspend line run sudo dpkg-reconfigure xkb-data *optional: edit /etc/systemd/logind.conf find line “#HandleLidSwitch=suspend” and uncomment change suspend to hibernate Fix scaling to remove distortions use dconf or gsettings change /com/canonical/unity/interface/text-scale-factor to 0.95 change /org/gnome/desktop/interface/text-scaling-factor to 0.95 change /org/gnome/desktop/interface/document-font-name to Sans 12 change /org/gnome/desktop/interface/font-name to Ubuntu 12 *optional: install Unity Tweak sudo apt install unity-tweak-tool -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Enable SUPPORT_PROXY compile option for exim
Hello, it would be nice if I could use the proxy protocol with exim on ubuntu. The feature is not experimental anymore. Are there any plans to include it? I couldn't find any informations about this. Regards Kim -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
