Re: any plymouth ...
Quoting Thomas Prost (t...@prosts.info): Maybe the aubergine at boot stays black (it's an old laptop I test it on, where this difference is hardly seen), but what I hoped for is not a twenty seconds empty screen but displaying messages right from leaving the BIOS screen :-( I would very much like to go back to the old way of booting too, especially for Ubuntu Server installs. However, i was told there is no way Ubuntu is going back to 'the old boot style' because of changes in the entire boot sequence: upstart introduces parallel bootstrapping of services which would result in incomprehensible output on your console if those services being started could log to the console at all because of the way upstart works. My attempts at getting rid of plymouth and the explanation of involved Ubuntu devs should be archived in the ubuntu-server@ mailinglist archives. IMO all these changes are really useful on desktop installs, parallel booting makes it fast, the splashscreen doesn't scare off people with all these strange numbers and words scrolling on the screen, however, as a sysadmin, with servers, it all Just Has No Use and frustrates debugging (boot)issues. Problem is, 'Ubuntu Server' is just a different selection of packages with a shared base set. Not a completely different 'distribution', so it shares all these eyecandy patches with the Desktop installs. HTH, -Sndr. -- | The cigarette does all the smoking. You are just the sucker. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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
Precise, php5-gd, auxv filedescriptors
Hello, I've submitted bug https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1177684 which shows 'auxv' filehandles left openend and cluttering the system. I've been able to reproduce this on any Precise system, yet no-one seems to really notice of think of this as a problem. Does anyone else see the described problem on their Precise webservers running Apache, mod_php and php5-gd? -Sndr. -- | Women like silent men, they think they're listening. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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: Problem with Quantal and a KVM
Quoting Jordon Bedwell (jor...@envygeeks.com): I agree, just did not want to say it. I get the feeling there are a lot of people working on Linux these days who have never set foot into a data centre. Your statement is full of fail and horseshit. Not to start a war at this beautiful start of 2013, but your reply isn't really constructive either, Jordon. Do you see any added value to a 'splash screen' hiding *everything* that is happening on *SERVER* installs? And framebuffered consoles. I can see *some* value of having larger terminals than the default 80x24. But the way it is now, it does not work on every system. Launchpad is full of bugs against the kernel because the display is blank on a device until X kicks in... On my laptop running Precise, this too is the case. It's nice for my mom. She also runs Ubuntu *DESKTOP* and is now no longer scared by all the text scrolling over the screen when she boots her computer. For experienced Linux admins it is a right PAIN in the ASS to not be able to see what's going on. Ubuntu 'server' has never had a real focus on the 'server' part. All the 'server' part does is leave out a certain set of packages, maybe include a few others. Other than that it's just the same codebase/packages as the Destkop flavour, and over the years the focus on the 'desktop' behaviour has become very very big with all the splashscreens and vital information hiding. Just my 25 cents. -Sndr. -- | If peanut butter cookies are made from peanut butter, | then what are Girl Scout cookies made out of? | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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: Problem with Quantal and a KVM
Quoting Jordon Bedwell (jor...@envygeeks.com): Do you see any added value to a 'splash screen' hiding *everything* that is happening on *SERVER* installs? Disable it? It takes but one obvious edit inside of /etc/default/grub. Pro tip: - quiet splash + nosplash Pro tip: update-grub Thanks. I am aware of your 'pro-tips'. If you had actually read the thread before hitting reply you would have seen my hints to Dale about the various nosplash, noplymouth, vga=xx and verboseness parameters. (Which, adressing your follow-up mail, work for installers and installed systems alike. For me, this is about installed Ubuntu systems. Not installers.) The 'nosplash' param indeed disables the splashscreen, just like hitting ESC would. Still, compared to booting Ubuntu pre-plymouth, there's not really much usefull information shown on the console about what is actually going on. There have been situations when there were no messages being logged to the screen and the system would not continue booting either. This is why i normally use 'init=/sbin/init -v' and INIT_VERBOSE=yes, but it still is rather messy due to the parallel starting of services. And framebuffered consoles. I can see *some* value of having larger terminals than the default 80x24. And this is more constructive than my comments? Jump in and help fix them bugs. Complaining is not any more constructive than what I did, I should indeed put effort in getting framebuffers working out-of-the-box on all my systems. You are totally correct in that aspect. But this is not my main pet peeve. As said, i can make framebuffers work by specifying a specific vga=xxx parameter that does work. My question boils down to why server installs need all this doohickey. In my opinion it shouldn't be this hard to get back to what is actually going on during boot of a server install. I'm totally pro these gadgets in desktop installs, really, but this makes Ubuntu feel 'Windows™®©-y', if i may use that word. Stuff happens behind 'the screen' and it makes debugging bootproblems unnecessarily hard for sysadmins running Ubuntu on serverhardware in colocating environments. -Sndr. -- | 1 1 was a racehorse, 2 2 was 1 2, 1 1 1 1 race 1 day, 2 2 1 1 2 | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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: Problem with Quantal and a KVM
Quoting Dale Amon (a...@vnl.com): Anyone know of a work around? A change in initrd? A change in /etc/default/grub? Warning: kinda ranty: This sounds like one of my major annoyances with Ubuntu (server): the framebuffered consoles splashscreens that are TERRIBLY incompatible with virtual monitors other than a physical connected VESA-VGA capable video display. Be it DRAC, ILOM, iRMC, KVM-switches alike, they all struggle with the framebuffered videomodes. Up until precise(?) it was possible to blacklist the framebuffered videomodule (fbcon, vga16) but these are now compiled in the kernel en therefore no longer blacklistable. :( What seemed to help for me was to force a specific videmode you *know* your monitor/application supports with the 'vga=xxx' kernelparameter (or gfxpayload GRUB option). However, things have been changing wildly the last couple of releases, none of my hacks to keep it working Try editing /etc/default/grub: * Comment out every line starting with 'GRUB_HIDDEN' This enables you to actually SEE the grub bootloader, without having to guess what key-combo is today's way to break in to the menu of GRUB. (It used to be ESC, then became one of the alt, ctrl or shift keys, today you might have to hold Escape-Meta-Alt-Control-Shift while double clicking your middle mouse button... who knows!) * Increase GRUB_TIMEOUT to 30 seconds This gives your monitor time to tune in and show you the GRUB menu AND allows you more time to change options / break the default process. * Change/Replace GRUB_CMDLINE_LINUX_DEFAULT with: vga=792 noplymouth nosplash verbose init_verbose=yes INIT=/sbin/init -v This line i composed in a fit of rage when i had a system not booting and not showing me ANYTHING usefull. It changes videomode, disables plymouth (as far as possible) switches off splashscreens, etc... * *UN*comment GRUB_TERMINAL=console Even GRUB has been switched to framebuffered video by default. :( HTH. -Sander. -- | The problem with dancing naked: not everything stalls when the music stops. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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: Munin-node's 'apt_all' cronjob.
Quoting Daniel Hahler (ubuntu+li...@thequod.de): I agree with this, however maybe it would be possible to make the cron run (more) silent, e.g. by only logging to /var/log/cron, but not syslog?! IMO the problem here is munin-node's cron entry, not cron itself. I like cron and the way it logs stuf. Your idea would require something like syslog-ng as default syslog daemon with filters in place to move messages to separate logs which is way more impacting to Ubuntu than changing the munin-node apt_all plugin. -Sndr. -- | The problem with dancing naked: not everything stalls when the music stops. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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
Munin-node's 'apt_all' cronjob.
Hi, I am somewhat annoyed by the cronjob for Munin's apt_all plugin. This cronjob is enabled by default even if one does not activate the apt_all plugin and it spams my syslog which is completely unnescessary, imo. Even though it is only 288 lines a day; with my server i have to 'grep -v' the crap to get a clear view of what happened in my logs. Yes i know i can disable it, but it seems to me such functionality should not be enabled by default at all. Any chance on making the default commented out in cron.d/munin-cron? The apt_all plugin could just error out if the cron isn't enabled or something similar, alerting the few users interrested in a graph of their packages to manually switch on the cronjob. Before i'm filing a wishlist bug, any comments? With regards, -Sander. -- | Bakers trade bread recipes on a knead to know basis. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- 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
