- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: identifying boot loader
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2005 12:12 AM
07-06-2005 12:12 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2005 12:18 AM
07-06-2005 12:18 AM
Re: identifying boot loader
ls -l /etc/{lilo,grub}.conf
you'll only have one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2005 12:23 AM
07-06-2005 12:23 AM
Re: identifying boot loader
just a little risky method:
strings
eg: strings /dev/hda | less
the first few lines should have either GRUB or LILO on it.
Note: You have to run it as root user and the give the device name or partition name where bootloader is written.
Hope this helps,
Gopi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2005 03:22 AM
07-06-2005 03:22 AM
Re: identifying boot loader
What risky about the strings method (this is a producation server)
thx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2005 03:26 AM
07-06-2005 03:26 AM
Re: identifying boot loader
not much if you are doing it carefully. strings will just read the hard disk and pipe it to less.
as long as you are not trying to write to it, then it is safe. Before typing the reply to you, i tried it on my one and only desktop which has every data of mine and till now it is working fine.
Hope this helps,
Gopi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2005 03:32 AM
07-06-2005 03:32 AM
Solutionlilo -v
and
grub -v
One of them should be not found. If you
have both, it will take some more work
to determine which loader is being used.
If the MBR is used then the command
dd if=/dev/hda bs=512 count=1 | strings
The output will include either GRUB or LILO
if they are install in the master boot
record. If not use fdisk or cfdisk to
find the bootable partition and try the
above command replacing /dev/hda with
the bootable partion.