[SOLVED] latest slackpkg upgrade-all bricks system on slackware64-current
SlackwareThis Forum is for the discussion of Slackware 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.
I just need some simple instructions to make the initrd from the boot stick. I've done it before on occasion as an exercise.
I'm using -current to keep up-to-date so I can keep gimp-2.9.x current. If I remain with stock slackware, I don't have the libraries that I need to run gimp from git, and gimp-2.8 is so far behind 2.9.x that is' not worth talking about.
OK, maybe you guys have given me enough info to work this out, so thanks!
I'll report back later (things to do right now) with happiness or more tears.
I see what do do with chroot.
John.
At the end of day, I believe that the -current is not for you.
IF you have even trouble to debug a failed boot, bad things could happen for you while using -current.
For example, for a considerable time, the -current kernels randomly crashed by fault of some mysterious misfeature.
Long story short, the slackware-current is not the rolling release version, but the very development tree of Slackware, and it may or may not work at random times.
Hence, its usage is supposed to be targeted to advanced users who willingly assume the role of beta-testers and knows really well how Slackware works, then able alone to bring back their installations, if something bad happens.
I strongly suggest you to go back to Slackware 14.2 and to find somehow how you can build your desired GIMP in a custom way.
Last edited by Darth Vader; 01-03-2018 at 09:54 AM.
Boot an installation media (or live as said Darth), login as root, don't run setup, mount your (installed) root partition as /mnt, bind mount /dev /proc and /sys as /mnt/dev, /mnt/proc and /mnt/sys, chroot /mnt and make the intrd, install it and run lilo.
What do you mean: bind mount /dev /proc and /sys as /mnt/dev, /mnt/proc and /mnt/sys An example would be helpful.
I'll wait for the fix from slackware, or maybe someone can actually help me out.
While you are logged as root into your live system, mount your Linux partitions; let's suppose that your Linux lives in /dev/sda2
Code:
mkdir /mnt/sda2
mount /dev/sda2 /mnt/sda2
mount --bind /dev /mnt/sda2/dev
mount --bind /proc /mnt/sda2/proc
mount --bind /sys /mnt/sda2/sys
chroot /mnt/sda2 su -l
# there you are root into your installed Linux, time to fix your boot.
IF your installed Linux is composed of multiple filesystems, you should mount all of them accordingly.
Last edited by Darth Vader; 01-03-2018 at 10:01 AM.
I just tried doing an clean install from the latest -current64 iso and noticed a couple of issues. First, it never gave me an option to select the filesystem for the root (/) partition. Second, it can't detect the cdrom/dvd iso. Probably related the same kernel issue?
I just tried doing an clean install from the latest -current64 iso and noticed a couple of issues. First, it never gave me an option to select the filesystem for the root (/) partition. Second, it can't detect the cdrom/dvd iso. Probably related the same kernel issue?
I do not think so. Probably our BDFL messed something in the scripts from installer.
Great info here, but keep in mind that un UEFI eras most people do not run lilo. I use GRUB.
You are only a victim of your own laziness.
You are supposed to switch to the generic kernel and initrd after the first boot of your operating system. The huge one is/was only a workaround for the first boot, nothing more.
Quote:
Originally Posted by README.initrd
1. What is an initrd?
Initrd stands for "initial ramdisk". An initial ramdisk is a very small
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
and before the main root filesystem is mounted.
2. Why do I need an initrd?
The usual reason to use an initrd is because you need to load kernel
modules before mounting the root partition. Usually these modules are
required to support the filesystem used by the root partition (ext3, ext4,
btrfs, xfs), or perhaps the controller that the hard drive is attached
to (SCSI, RAID, etc). Essentially, there are so many different options
available in modern Linux kernels that it isn't practical to try to ship
many different kernels to try to cover everyone's needs. It's a lot more
flexible to ship a generic kernel and a set of kernel modules for it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.