Did you try to boot it? You have not upgraded the kernel so you don't need a new initrd. (It didn't work because you tried to make an initrd for the running kernel, not the kernel to be booted from the disk.)
|
1 Attachment(s)
Yes, I tried...
...the good news is that there is no more kernel panic :) ...the bad is a possible library conflict (?) (please see the attached picture) EDIT: it seems that I can login to my system (no X11). Some basic commands work...so I was thinking about updating everything again with the right mirror. But: Code:
# iwconfig |
Quote:
Think about what you are doing. |
Quote:
Code:
linux /boot/vmlinuz root=UUID=f52adeea-a45c-4dc5-b599-aecadc1709b5 ro Code:
linux /boot/vmlinuz disregard this drive block ID -->>root=UUID=f52adeea-a45c-4dc5-b599-aecadc1709b5 ro <<-- you will use your own. if you isntall lilo at boot time and never edit it you should be fine. !!! but you have grub LIKE ME. edit the grub to vmlinuz only do not worry about intrd.img . just do it. then after your done learn grub. then run as root grub-mkconfig -o /boot/grub/grub.cfg reboot and be happy. learn grub or learn lilo learn both. I prefer grub for multi systems and lilo for single system |
You could try to upgrade it to the latest -current. Without working network, you could use your Microsoft OS to download and burn http://bear.alienbase.nl/mirrors/sla...nstall-dvd.iso.
Then you could point slackpkg to the files on the DVD. See examples in the beginning of /etc/slackpkg/mirrors. |
The OP didn't install a new kernel and didn't really run either lilo or grub (tried but they didn't execute) and didn't make a new initrd either. And the system boots as well as ever before using the old kernel. The problem was that kernel could not exec init because /sbin/init was linked against a glibc which was not there.
The remaining problem now is probably due to the fact that the latest -current glibc.so is newer than the previous working glibc, and some executable binaries and/or libraries have problems with that. Upgrading to the latest current should help, but everyone knows that current is work with your own risk... |
@Petri, great! I am downloading the currentDVD right now.
Dealing with the grub / lilo issue, it's just that in the past I have never had any kind of problem in switching between them. I have lilo now, but since the system booted correctly I think we can move to the next step (as suggested). I will keep you update, thanks for the support. EDIT: Meanwhile, could I ask for a small clarification, please? By installing the official 14.2, one must choose the 14.2 repository. Otherwise, the right choice is (generally) the -current fork, like in the MateLIVE edition. Did I understand correctly? :) |
Quote:
"It is a version of Slackware (14.2 and newer) that can be booted and run directly from a DVD or a USB stick. It is distributed as an ISO image and meant to be a showcase of what Slackware is about. You get the default install, no customizations, but with all the power. You do not have to install Slackware to your harddisk first to experience it first-hand." I would understand it as a demo of what Slackware is so that you could install the real thing later on the hard drive. If that is correct, I wouldn't try to update MateLIVE using any repository as there is no MateLIVE repository. Instead, I would install the real Slackware to start with. Maybe Eric will give a better answer, himself. |
Quote:
|
Quote:
Good luck with that? By the way, I'm not using Slack, but I would like to get your explanation anyway, since I'm interested in it. |
Quote:
Otherwise, the only one that you know who has a system exactly like yours is yourself. Some things you'll catch from the upgrade comments, some you won't. The automated tools in Slackware generally won't leave the old kernel around unless you take steps for that to happen. Most of the time, you can get away with it. |
Quote:
I don't use a package manager but I do keep my local mirror up-to-date via Alien Bob's rsync-current.sh I wrote the script below my sig back when I ran Slackware 10.0, before I knew about any Package Managers for Slackware. It is set up for MY local Slackware rsync mirror ( see # edit me Comments near the top of .find-missing-packages ) for MY Slackware 14.2 + Multilib System. Example: Today's output for `./.find-missing-packages` is: Code:
ap/soma-2.10.4-noarch-1.txz As for the other 'missing packages' ... I know why each of these packages are not installed and I suppose I could modify .find-missing-packages with a blacklist But it is 'comforting' to see the familiar list ( soma, oxygen-gtk2, sendmail-* ) which tells me that the script is working properly. And my Blacklist is 'downstream' in my complementary update -and-or- install scripts. Anyhow, this has been working for me since Slackware 10.0 ... YMMV ... -- kjh This is .find-missing-packages It 'lives' in my update-log directory and it begins with a '.' so that I can safely `rm *` or `mv *` and not lose my scripts. Code:
#!/bin/sh |
2 Attachment(s)
First of all, thanks for all the various information. I am reading them step by step, but currently still facing a local problem.
I downloaded the current slackware iso, extracted and copied the content into '/mnt/current'. So, '/mnt/current' contains now the folders like "extra", "isolinux", etc..., (and, in particular, ChangeLog.txt). I edited '/etc/slackpkg/mirror' in order to have only one line uncommented, specifically: Code:
file://mnt/current/ Code:
slackpkg update I do not understand why it is still trying to connect to an online mirror, while the only line that I specified referred to my local folder. |
Wario --
The errors in your screenshot seem to refer to slackpkgplus ... Did you check the slackpkgplus README ? Specifically, did you configure /etc/slackpkg/slackpkgplus.conf for your system ? Disclaimer: I don't use slackpkg or slackpkgplus ... so HTH ... -- kjh |
1 Attachment(s)
Thanks so much for the README link!
I was unaware about "slackpkgplus" - here enabled by default since I installed the slackwareMATE edition. After having temporarily disabled it, the system upgrade from local directories is starting... At this moment I have to decide how to manage some packages conflict...but I think it would be wiser to share this step with you. Please, see again the attached picture :) What exactly does this message mean, and which action do you suggest to perform? Thanks again for your precious support. |
All times are GMT -5. The time now is 04:42 AM. |