LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-25-2018, 03:20 PM   #1
vmolution
LQ Newbie
 
Registered: Oct 2018
Posts: 2

Rep: Reputation: Disabled
Experiencing Slackware Alternatively


I set up a vdi in VirtualBox, boot up using some linux live dvd.

Set up VirtualBox, enable EFI

Create GPT partition, 1st primary partition formatted as FAT32.

Copy EFI and kernels directories only.

My expectation would be

1. having a shell thats it.

But I got the following
Boot Failed. EFI DVD/CDROM
Welcome to GRUB!
_
 
Old 11-25-2018, 06:03 PM   #2
Qury
Member
 
Registered: Feb 2004
Location: Naas,IE
Distribution: Slackware
Posts: 212

Rep: Reputation: 184Reputation: 184
what is your question?
 
2 members found this post helpful.
Old 11-26-2018, 03:45 PM   #3
chemfire
Member
 
Registered: Sep 2012
Posts: 422

Rep: Reputation: Disabled
You can't just copy the EFI loader and the Kernel for a number of reasons.

First EFI needs to be registered using something like efibootmgr. Unless you specifically place the efi loader at the fall back location /bootx64.efi on the efi filesystem. So the EFI system probably has no idea what to load next as it is.

Second it takes more than the kernel to get a shell. The kernels is really process scheduling, filesystem handling, hardware abstraction, etc. Its not something use can really interact with as a user. You need a user space process to do that. On UNIX this is the shell.

To run the shell though it needs to live on a filesystem of itself. However you can't just park bash there. You will need a set of libraries and device nodes at a minimum. To that end it will have to be a separate filesystem from the EFI because it will need to be able to host devs and fat32 is not able to do this. You will also need to configure whatever bootloader you have chose to pass the kernel a command line argument for init.

Frankly all of this is rather complex; not beyond the ability to understand by any means; but its not like BIOS just loading the first 512 bytes of the disk which in turns reads MSDOS.SYS or similar of old. My advice is install Slackware using the installer! Boot of the installation media and follow the documentation. Once you have working booting system; than you can take time to learn and understand the boot process. It will all make more sense when you have something complete and correct to look at; rather than trying to assemble piecemeal
 
1 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Experiencing Slackware Installation Alternatively vmolution LinuxQuestions.org Member Intro 0 11-25-2018 03:09 PM
Force install in /usr/local, or, alternatively, how to use a usb-stick as extra space InNomineLibertas Linux - Software 4 03-10-2012 05:22 PM
How to switch among two threads alternatively ?? apanimesh061 Programming 4 09-18-2011 03:38 PM
Internet comes alternatively ntu929 Linux - Wireless Networking 2 03-20-2011 11:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:44 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration