Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #180054
| From | Dejan Jocic <jodejka@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: System broken after yesterday's upgrade |
| Date | 2017-04-13 11:20 +0200 |
| Message-ID | <tvJ50-Rx-3@gated-at.bofh.it> (permalink) |
| References | <tqhCp-4pL-11@gated-at.bofh.it> <tvH3c-7S2-21@gated-at.bofh.it> <tvHPz-8gn-5@gated-at.bofh.it> <tvIsi-kh-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 13-04-17, solitone wrote:
> On Thursday, 13 April 2017 09:53:05 CEST Dejan Jocic wrote:
> > If you have old kernel, you do not have to choose it in the GRUB menu during
> > boot, you can set up your GRUB to boot from it automatically.
>
> I have a submenu entry in my grub.cfg:
>
> solitone@alan:~$ grep --color menu /boot/grub/grub.cfg
> [...]
> menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --
> class os $menuentry_id_option 'gnulinux-simple-7f537d3b-e578-4cd3-8583-
> f3a2281f7d01' {
> submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option
> 'gnulinux-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-2-amd64' --class debian
> --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-4.9.0-2-amd64-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-2-amd64 (systemd)' --
> class debian --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-4.9.0-2-amd64-init-systemd-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-2-amd64 (recovery mode)'
> --class debian --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-4.9.0-2-amd64-recovery-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-1-amd64' --class debian
> --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-4.9.0-1-amd64-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-1-amd64 (systemd)' --
> class debian --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-4.9.0-1-amd64-init-systemd-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-1-amd64 (recovery mode)'
> --class debian --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-4.9.0-1-amd64-recovery-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
>
> To automatically load 'Debian GNU/Linux, with Linux 4.9.0-1-amd64' I need to
> set :
> GRUB_DEFAULT="1>3"
> in /etc/default/grub?
>
> Cheers,
> Davide
>
You can set it with numbers, but you can set it also with quotes, like
for example:
GRUB_DEFAULT='gnulinux-4.9.0-1-amd64-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01'
Which should be kind of more secure way if you do not to want to
miss what you exactly want with numbers.
Anyway, however that you do it, after that you will need to run
# update-grub.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Random usb failure at bootup solitone <solitone@mail.com> - 2017-03-29 11:00 +0200
System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-12 16:00 +0200
Re: System broken after yesterday's upgrade Jochen Spieker <ml@well-adjusted.de> - 2017-04-12 20:00 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-12 22:20 +0200
Re: System broken after yesterday's upgrade Mart van de Wege <mvdwege@gmail.com> - 2017-04-12 22:50 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-13 08:50 +0200
Re: System broken after yesterday's upgrade Jochen Spieker <ml@well-adjusted.de> - 2017-04-12 23:10 +0200
Re: System broken after yesterday's upgrade Michael Lange <klappnase@freenet.de> - 2017-04-13 00:40 +0200
Re: System broken after yesterday's upgrade Dejan Jocic <jodejka@gmail.com> - 2017-04-13 01:30 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-13 09:10 +0200
Re: System broken after yesterday's upgrade Dejan Jocic <jodejka@gmail.com> - 2017-04-13 10:00 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-13 10:40 +0200
Re: System broken after yesterday's upgrade Dejan Jocic <jodejka@gmail.com> - 2017-04-13 11:20 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-13 11:10 +0200
Re: System broken after yesterday's upgrade Michael Lange <klappnase@freenet.de> - 2017-04-13 11:30 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-13 12:50 +0200
Re: [SOLVED] System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-15 07:30 +0200
Re: System broken after yesterday's upgrade solitone <solitone@mail.com> - 2017-04-13 14:00 +0200
csiph-web