Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #172028
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: How to get Jessie to run at boot time |
| Date | 2016-09-11 06:40 +0200 |
| Message-ID | <sg4IF-1s3-9@gated-at.bofh.it> (permalink) |
| References | <sfYjU-5uc-11@gated-at.bofh.it> |
| Organization | less than infinite |
Alan McConnell composed on 2016-09-10 17:45 (UTC-0400): > Good grief. I just wrote that I am now logged in to a working jessie. > So I can run any kind of apt-get, aptitude, etc. > So I repeat: apt-cache search grub gives me lots of grub files to install. > Do I want to install a different grub? Possibly, though not likely. What does 'dpkg -l | grep grub' show now? > I remember that previously I had lots > of files in /boot/grub/ . Now I have just a few, which I gave to you and the > List in my previous post. You had more files when you were using Grub. Now you surely have Grub2, which scatters files across more locations instead of keeping most in /boot/grub. > Again: are there people with a working dual boot system? I have no "dual boot" systems, but I do have *dozens* of multiboot systems representing hundreds of installations of various distros that include Wheezy, Jessie and Stretch. Grub is installed to the MBR of none of them, regardless whether or not Windows or DOS are among their installations. > I'd like a response > from one of them(if they exist here) letting me know how it works, Several different ways work here. This machine: 1-Generic code is installed to MBRs 2-/dev/sda1 and /dev/sdb1 are marked active/bootable in MBR table 3-Grub actually used for booting is installed to /dev/sda1 and /dev/sdb1 4-After installation or kernel update, I copy kernel and initrd to /dev/sd#1 5-Grub loads kernel/initrd from /dev/sd#1 6-/dev/sd#1/boot/grub are maintained entirely by myself 7-/ partitions are on /dev/md1, /dev/md2, /dev/md3 & /dev/md4 (md4 running) The method is fundamentally equivalent to how DOS, OS/2 and Windows boot: standard MBR code finds the active/bootable partition, then loads and transfers control to the boot code found there. A very different, and simpler, example can be found on: http://fm.no-ip.com/PC/install-doz-after.html > and also: > what is the content of their /boot/grub/ directory. From the one from which I write this (but note it's not the location from which machine normally "boots", only the one the distro installation installs and maintains): # ll /boot/grub total 532 drwxr-xr-x 2 root root 4096 Aug 2 02:58 . drwxr-xr-x 4 root root 4096 Aug 2 02:57 .. -rw------- 1 root root 10 Oct 3 2011 default -rw------- 1 root root 108 Jan 31 2015 device.map -rw------- 1 root root 30 Oct 3 2011 device.map-ab -rw------- 1 root root 108 Jan 31 2015 device.map-both -rw------- 1 root root 29 Oct 3 2011 device.map.old -rw-r--r-- 1 root root 13280 Sep 11 2015 e2fs_stage1_5 -rw-r--r-- 1 root root 11213 Sep 11 2015 fat_stage1_5 -rw-r--r-- 1 root root 9920 Sep 11 2015 ffs_stage1_5 -rw-r--r-- 1 root root 9984 Sep 11 2015 iso9660_stage1_5 -rw-r--r-- 1 root root 11968 Sep 11 2015 jfs_stage1_5 -rw------- 1 root root 681 Feb 7 2016 menu.lst -rw------- 1 root root 681 Feb 7 2016 menu.lst.0 -rw------- 1 root root 1360 Feb 7 2016 menu.lst.02 -rw------- 1 root root 1614 Feb 7 2016 menu.lst.03 -rw------- 1 root root 1620 May 30 21:39 menu.lst.04 -rw------- 1 root root 1620 Jul 2 01:51 menu.lst.05 -rw------- 1 root root 1620 Aug 2 02:54 menu.lst.06 -rw------- 1 root root 1363 Aug 2 02:54 menu.lst.old -rw-r--r-- 1 root root 10048 Sep 11 2015 minix_stage1_5 -rw-r--r-- 1 root root 13696 Sep 11 2015 reiserfs_stage1_5 -rw-r--r-- 1 root root 512 Sep 11 2015 stage1 -rw-r--r-- 1 root root 137520 Dec 26 2015 stage2 -rw-r--r-- 1 root root 10324 Sep 11 2015 ufs2_stage1_5 -rw-r--r-- 1 root root 9472 Sep 11 2015 vstafs_stage1_5 -rw-r--r-- 1 root root 13446 Sep 11 2015 xfs_stage1_5 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
icedove: failed to connect server XXX@gmail.com mudongliang <mudongliangabcd@hotmail.com> - 2016-09-09 17:10 +0200
How to get Jessie to run at boot time Alan McConnell <alan@his.com> - 2016-09-09 20:00 +0200
Re: How to get Jessie to run at boot time Felix Miata <mrmazda@earthlink.net> - 2016-09-09 20:10 +0200
Re: How to get Jessie to run at boot time "Andrew M.A. Cater" <amacater@galactic.demon.co.uk> - 2016-09-09 20:50 +0200
Re: How to get Jessie to run at boot time Alan McConnell <alan@his.com> - 2016-09-10 17:50 +0200
Re: How to get Jessie to run at boot time Brian <ad44@cityscape.co.uk> - 2016-09-10 18:40 +0200
Re: How to get Jessie to run at boot time Alan McConnell <alan@his.com> - 2016-09-10 23:50 +0200
Re: How to get Jessie to run at boot time "Andrew M.A. Cater" <amacater@galactic.demon.co.uk> - 2016-09-11 00:50 +0200
Re: How to get Jessie to run at boot time Felix Miata <mrmazda@earthlink.net> - 2016-09-11 06:40 +0200
Re: How to get Jessie to run at boot time -- Problem solved Alan McConnell <alan@his.com> - 2016-09-11 17:20 +0200
Re: How to get Jessie to run at boot time -- Problem solved Brian <ad44@cityscape.co.uk> - 2016-09-11 20:40 +0200
Re: How to get Jessie to run at boot time -- Problem solved Alan McConnell <alan@his.com> - 2016-09-11 21:20 +0200
Re: How to get Jessie to run at boot time -- Problem solved Brian <ad44@cityscape.co.uk> - 2016-09-11 22:00 +0200
Re: How to get Jessie to run at boot time -- Problem solved Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-12 13:20 +0200
Re: icedove: failed to connect server XXX@gmail.com Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-13 09:30 +0200
Re: icedove: failed to connect server XXX@gmail.com Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-13 10:00 +0200
side-track of thread to the subject of mailservers was: Re: icedove: failed to connect server XXX@gmail.com Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-13 11:20 +0200
Re: icedove: failed to connect server XXX@gmail.com Richard Owlett <rowlett@cloud85.net> - 2016-09-13 19:50 +0200
csiph-web