Re: Problem with Quantal and a KVM
On Thu, Jan 03, 2013 at 04:14:44PM -0800, Mark - Syminet wrote: On Jan 3, 2013, at 3:35 PM, Dale Amon a...@vnl.com wrote: […] I had tried the GFX line earlier but had not joy... but I have fiddled many things since then, so perhaps I will try it again. Most people probably want to add this line as well: GRUB_RECORDFAIL_TIMEOUT=5 …in order to workaround bug #872244: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/872244 Thanks I will add it. I am hoping I can get this working in the next 12 hours so I can leave simpler instructions for the tech I have asked to be my remote button monkey. Otherwise your machine might randomly hang on reboots (which as we all know, will probably happen 30 seconds after your plane takes off on a 14 hour flight). Been there... -- 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
auto generated menu.lst file contents
Hi, I have customized Ubuntu distribution, along with several customization i have also changed distribution name, it works well. Currently I use this cutomized distro rootfs with Linux kernel but whenever i do update-grub, the auto-generated menu.lst file do have original distro name, My question is grub read which file to determine distro name, as i want to customize it completely. Sample snippet from auto-generated menu.lst file title Ubuntu, kernel 2.6.17-10-generic root (hd0,4) kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash initrd /boot/initrd.img-2.6.17-10-generic Look at title, it contains original distro name, it shows i missed some file in orignal distro and grub still can determine original distro name and show it in tile. So kindly guide how grub determine distro name... -- Kind Regards, Saqlain Abbas. -- 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: auto generated menu.lst file contents
On Fri, Jan 04, 2013 at 02:10:55PM +0500, Saqlain Abbas wrote: I have customized Ubuntu distribution, along with several customization i have also changed distribution name, it works well. Currently I use this cutomized distro rootfs with Linux kernel but whenever i do update-grub, the auto-generated menu.lst file do have original distro name, My question is grub read which file to determine distro name, as i want to customize it completely. The very old version of update-grub you're using hardcodes it, so you'd have to edit the update-grub script directly to fix this. More recent versions (anything from Ubuntu 7.10 onwards) pick up the title from lsb_release. Sample snippet from auto-generated menu.lst file title Ubuntu, kernel 2.6.17-10-generic root (hd0,4) kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash initrd /boot/initrd.img-2.6.17-10-generic You are using a dangerously old version of Ubuntu; that looks like Ubuntu 6.10, which has been out of security support for nearly five years and by now is very likely to be full of vulnerabilities. Even the version of Ubuntu that fixed the bug of not using lsb_release here has itself been out of security support for nearly four years! You should upgrade to something very much newer at the earliest opportunity. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- 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: ubuntu core - kernel installation question
On Wed, Jan 02, 2013 at 03:47:57PM +, Tim Verstraete wrote: I am evaluating ubuntu core 12.10 (this version because of touch screen support) and I am following https://wiki.ubuntu.com/Core/InstallationExample and up until the installation of the kernel everything is working (if I reuse a kernel installation from previous builds (my own builds) everything is fine) BUT when I want to install a .deb with the kernel selected from the packages list I get: root@ubuntu:/tmp# dpkg -i --force-all linux-image-3.5.0-21-generic_3.5.0-21.32_amd64.deb Never use --force-all. It is very dangerous and is entirely capable of accidentally trashing large swathes of your filesystem when a less cavalier set of options would have produced a sensible error messages. All the reasonable things you might want to force have much safer alternatives. [...] grep: /proc/cpuinfo: No such file or directory [...] This is normal since we have no proc/cpuinfo ... how can I overrule this check on cpuinfo? Is there any reason not to bind-mount /proc into your chroot? We don't support running very much without /proc in place, and certainly not installing packages in general. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- 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: auto generated menu.lst file contents
Thanks Colin for suggestions! I have now used used Ubuntu 12.04 (I can see 12.10 also available but did not give it a try) from https://wiki.ubuntu.com/Core I have modified rootfs as per my requirements (incorporated my all scripts and customization into into it, and is perfectly fine), I have modified /etc/lsb-release, but unfortunately still menu.lst generated through update-grub, contain title as ubuntu. I suppose with this version update-grub should pick name from lsb-release as you mentioned, or i am missing something else also? Or you would suggest me to use 12.10, i want to avoid modifying update-grub, the reason you mentioned it will pick from lsb-release, is there some other files which i need to modify also? I have modified /etc/lsb-release, /etc/os-release, /etc/issue, /var/run/motd etc Thanks, Saqlain. On Fri, Jan 4, 2013 at 6:11 PM, Colin Watson cjwat...@ubuntu.com wrote: On Fri, Jan 04, 2013 at 02:10:55PM +0500, Saqlain Abbas wrote: I have customized Ubuntu distribution, along with several customization i have also changed distribution name, it works well. Currently I use this cutomized distro rootfs with Linux kernel but whenever i do update-grub, the auto-generated menu.lst file do have original distro name, My question is grub read which file to determine distro name, as i want to customize it completely. The very old version of update-grub you're using hardcodes it, so you'd have to edit the update-grub script directly to fix this. More recent versions (anything from Ubuntu 7.10 onwards) pick up the title from lsb_release. Sample snippet from auto-generated menu.lst file title Ubuntu, kernel 2.6.17-10-generic root (hd0,4) kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash initrd /boot/initrd.img-2.6.17-10-generic You are using a dangerously old version of Ubuntu; that looks like Ubuntu 6.10, which has been out of security support for nearly five years and by now is very likely to be full of vulnerabilities. Even the version of Ubuntu that fixed the bug of not using lsb_release here has itself been out of security support for nearly four years! You should upgrade to something very much newer at the earliest opportunity. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- 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 -- 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: auto generated menu.lst file contents
Hello Saqlain, you know the saying: give a man a fish, he will eat for a day. Teach a man to fish The best thing of open source is that, well, you have the source. Inside the apt repository files, you can uncomment the source repositories, and, after an apt-get update, instead of downloading the binary, you can download the source. Out of my memory, I suggest you download grub's source, find the source file(s) of the update-grub, and start by looking at simple functions that open files, such as fopen(), or for some strings (as some of these file names might be hardcoded), or just stroll around the code. You would be amazed at how much one is able to learn just by looking at some never-seen-before code (or horrified, depending on the case) - but in any case, you will learn WHILE having a mental challenge. I sincerely hope this helps. 2013/1/4 Saqlain Abbas saqlain.abba...@gmail.com Thanks Colin for suggestions! I have now used used Ubuntu 12.04 (I can see 12.10 also available but did not give it a try) from https://wiki.ubuntu.com/Core I have modified rootfs as per my requirements (incorporated my all scripts and customization into into it, and is perfectly fine), I have modified /etc/lsb-release, but unfortunately still menu.lst generated through update-grub, contain title as ubuntu. I suppose with this version update-grub should pick name from lsb-release as you mentioned, or i am missing something else also? Or you would suggest me to use 12.10, i want to avoid modifying update-grub, the reason you mentioned it will pick from lsb-release, is there some other files which i need to modify also? I have modified /etc/lsb-release, /etc/os-release, /etc/issue, /var/run/motd etc Thanks, Saqlain. On Fri, Jan 4, 2013 at 6:11 PM, Colin Watson cjwat...@ubuntu.com wrote: On Fri, Jan 04, 2013 at 02:10:55PM +0500, Saqlain Abbas wrote: I have customized Ubuntu distribution, along with several customization i have also changed distribution name, it works well. Currently I use this cutomized distro rootfs with Linux kernel but whenever i do update-grub, the auto-generated menu.lst file do have original distro name, My question is grub read which file to determine distro name, as i want to customize it completely. The very old version of update-grub you're using hardcodes it, so you'd have to edit the update-grub script directly to fix this. More recent versions (anything from Ubuntu 7.10 onwards) pick up the title from lsb_release. Sample snippet from auto-generated menu.lst file title Ubuntu, kernel 2.6.17-10-generic root (hd0,4) kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash initrd /boot/initrd.img-2.6.17-10-generic You are using a dangerously old version of Ubuntu; that looks like Ubuntu 6.10, which has been out of security support for nearly five years and by now is very likely to be full of vulnerabilities. Even the version of Ubuntu that fixed the bug of not using lsb_release here has itself been out of security support for nearly four years! You should upgrade to something very much newer at the earliest opportunity. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- 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 -- 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 -- [] Alexandre Strube su...@ubuntu.com -- 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: auto generated menu.lst file contents
Alexander! what you said perfectly make sense, i am going to do same right now :-), i am newbie and my purpose of doing all this is to understand and i agree with you, may be better way is to look at source... On Fri, Jan 4, 2013 at 10:36 PM, Alexandre Strube su...@ubuntu.com wrote: Hello Saqlain, you know the saying: give a man a fish, he will eat for a day. Teach a man to fish The best thing of open source is that, well, you have the source. Inside the apt repository files, you can uncomment the source repositories, and, after an apt-get update, instead of downloading the binary, you can download the source. Out of my memory, I suggest you download grub's source, find the source file(s) of the update-grub, and start by looking at simple functions that open files, such as fopen(), or for some strings (as some of these file names might be hardcoded), or just stroll around the code. You would be amazed at how much one is able to learn just by looking at some never-seen-before code (or horrified, depending on the case) - but in any case, you will learn WHILE having a mental challenge. I sincerely hope this helps. 2013/1/4 Saqlain Abbas saqlain.abba...@gmail.com Thanks Colin for suggestions! I have now used used Ubuntu 12.04 (I can see 12.10 also available but did not give it a try) from https://wiki.ubuntu.com/Core I have modified rootfs as per my requirements (incorporated my all scripts and customization into into it, and is perfectly fine), I have modified /etc/lsb-release, but unfortunately still menu.lst generated through update-grub, contain title as ubuntu. I suppose with this version update-grub should pick name from lsb-release as you mentioned, or i am missing something else also? Or you would suggest me to use 12.10, i want to avoid modifying update-grub, the reason you mentioned it will pick from lsb-release, is there some other files which i need to modify also? I have modified /etc/lsb-release, /etc/os-release, /etc/issue, /var/run/motd etc Thanks, Saqlain. On Fri, Jan 4, 2013 at 6:11 PM, Colin Watson cjwat...@ubuntu.com wrote: On Fri, Jan 04, 2013 at 02:10:55PM +0500, Saqlain Abbas wrote: I have customized Ubuntu distribution, along with several customization i have also changed distribution name, it works well. Currently I use this cutomized distro rootfs with Linux kernel but whenever i do update-grub, the auto-generated menu.lst file do have original distro name, My question is grub read which file to determine distro name, as i want to customize it completely. The very old version of update-grub you're using hardcodes it, so you'd have to edit the update-grub script directly to fix this. More recent versions (anything from Ubuntu 7.10 onwards) pick up the title from lsb_release. Sample snippet from auto-generated menu.lst file title Ubuntu, kernel 2.6.17-10-generic root (hd0,4) kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash initrd /boot/initrd.img-2.6.17-10-generic You are using a dangerously old version of Ubuntu; that looks like Ubuntu 6.10, which has been out of security support for nearly five years and by now is very likely to be full of vulnerabilities. Even the version of Ubuntu that fixed the bug of not using lsb_release here has itself been out of security support for nearly four years! You should upgrade to something very much newer at the earliest opportunity. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- 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 -- 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 -- [] Alexandre Strube su...@ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- 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 -- Kind Regards, Saqlain Abbas. -- 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
On Fri, Jan 04, 2013 at 08:51:32AM +, Dale Amon wrote: Most people probably want to add this line as well: GRUB_RECORDFAIL_TIMEOUT=5 I did so. I finally got it to work with 'nomodeset' in conjunction with some of the others. Now if I can get my libvirt networking functioning on the new server in the next 12 hours before I go to the airport, I am golden. -- 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
On Thu, Jan 3, 2013 at 3:49 PM, Sander Smeenk ssme...@freshdot.net wrote: Quoting Jordon Bedwell (jor...@envygeeks.com): 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. I've just done a manual install of 12.10 to see what a plain, default install leads to. There's no splash or quiet on either the GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX lines and plymouth is set to its text theme. You might need some tweaks for some of your boxes either to kill the framebuffer or set it to the correct resolution or to make the boot more verbose but these settings both look like sane defaults. root@localhost:~# cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=2 GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT= GRUB_CMDLINE_LINUX= # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM=0x01234567,0xfefefefe,0x89abcdef,0xefefefef # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass root=UUID=xxx parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries GRUB_DISABLE_RECOVERY=true # Uncomment to get a beep at grub start #GRUB_INIT_TUNE=480 440 1 root@localhost:~# root@localhost:~# root@localhost:~# ls -l /etc/alternatives/*plymouth* lrwxrwxrwx 1 root root 53 Jan 4 20:29 /etc/alternatives/text.plymouth - /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth root@localhost:~# Furthermore: You had said in an earlier post that you used vga=792 noplymouth nosplash verbose init_verbose=yes INIT=/sbin/init -v You might want to set GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX rather than vga= because when you use vga= grub displays a message that it's deprecated (IIRC) and since kernel documentation (in kernel-parameters.txt) says that it's a boot-loader parameter, the grub developers might disable it at *some* point. Having both noplymouth and nosplash is overkill since they have the same effect. verbose doesn't do anything. You must mean --verbose, which is the same as -v, init=/sbin/init --verbose, and init=/sbin/init -v. It's not init_verbose=yes but INIT_VERBOSE=yes because of console output; env INIT_VERBOSE in /etc/init/rc.conf and /etc/init/rc-sysinit.conf. -- 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
On Thu, Jan 3, 2013 at 6:35 PM, Dale Amon a...@vnl.com wrote: On Thu, Jan 03, 2013 at 06:18:21PM -0500, Tom H wrote: On Wed, Jan 2, 2013 at 6:39 AM, Dale Amon a...@vnl.com wrote: # DMA20121218. This is new, suggested to me by Tom H on the ubuntudev list #GRUB_GFXPAYLOAD_LINUX=text If you don't set it text, the value of GRUB_GFXPAYLOAD_LINUX is that of GRUB_GFXMODE, which is auto by default. # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why don't you uncomment this line? The value of GRUB_TERMINAL is gfxterm by default. Note that I have it set to serial console up above in the file. I noticed serial console and then forgot about it when I saw two GRUB_CMDLINE_LINUX_DEFAULT lines... -- 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
