ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And could you tell me how to use the patch? I never used a .diff. Plus I do not have a running Slackware OS. The patch should be done by Arch.
After 3,752 posts in 11 years on this forum, it appears that you have not really touched the basics of working with a Linux computer. You have some learning to do, and you need to do that fast if your are going to use Arch instead of Slackware.
As others said before me: please ask the moderators to move this thread to the Arch Linux forum. It does not belong here.
But Slackware.com gives a .txz package, and using tar to extract the files I get a very complicated tree.
Quote:
Originally Posted by stf92
And could you tell me how to use the patch? I never used a .diff. Plus I do not have a running Slackware OS. The patch should be done by Arch.
As a general comment it is probably easier to figure out which files from the txz are needed and where to put them (the package is not that complicated) than to research how to apply patches and compile from source.
Another possibility is to get source code from the Crux repository. You will need two packages: lilo itself and bin86. A great advantage of piggybacking on Crux is that the Crux Pkgconfig files will give you suitable build configuration choices.
I have finally been able to run lilo from Arch. I have done an unsuccessful slackware current install but the needed packages are all there. Setup installed them. I just mounted the slackware partition in /mnt and ran /mnt/sbin/lilo -v -t successfully. What happens after booting and choosing the OS from the lilo prompt is another matter, which I'll treat in another thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.