I have tried to install amd 64 kernel but it says it cant find one.

I went right back to the beginning and followed through the instructions from the link. Got to the installing the kernel and it did load this time, did the check requested in the article and saw it was the correct kernel running installed the amd64 dpkg, apt etc as told then troubles started again could not get apt to run properly By now I thought this is a nonsense, over the years no end of crud has built up, and I have cocked something up. So decided to do what I should have done before, downloaded backups of data, db files. and conf files and did a complete reinstall of the OS. Which I might add was quicker in the end Have installed, loaded all the necessary software, set up the firewall again and am now in the process of reloading websites, databases and Bind9 files. The problems before were obviously where I had cocked something up and I could spend days hunting through. Now I have a nice clean installation, tons of rubbish deleted and I can manage the various bind zones and apache website files in a more orderly fashion. Sorry to have been a nuisance Keith On Mon, 22 Jul 2019 at 18:02, Andy Smith <andy(a)bitfolk.com> wrote:

Hi Keith, On Mon, Jul 22, 2019 at 09:14:25PM +0100, Keith Williams wrote: time, So I suspect what happened before was that you did not put the ":amd64" on the end of the "apt-get install linux-image-amd64:amd64" command. I did say that stopping at the point of installing a 64-bit kernel was the easy part and a perfectly valid place to stop, as after that it gets tricky. Impossible to comment further without a log of what you did, but yes you have to do some scary things that apt asks if you are sure about and it's very easy to completely break your system from here on in if you don't know what you are doing. Unless you are confident in what you're doing I don't recommend that anyone does this past switching the kernel. Probably nothing to do with your past configurations, more likely that apt doesn't really know how to achieve what you're asking and you have accidentally let it remove something essential. It could probably be rescued - when I do this process there are always periods of time where the system is broken because essential things have been removed, but I then put them back - forcibly by wgetting the .deb file and installing it with dpkg if necessary. So it may be that you've gone too far and really broken it, or that it's slightly broken and you don't know how to recover from it. *You* have done a reinstall now, but if anyone else gets in this position then they could post on here where they have got to and what's going wrong and we/I will try to help. Though in terms of good use of your time, it will be faster and safer to reinstall, assuming you have backups. It is certainly worth considering that provided you can put back all your data and settings, reinstalling is definitely going to be faster than fully crossgrading your system. You can run through a Debian or Ubuntu install in just a couple of minutes. It's always good to see what problems users are having and if there are ways to avoid them. Though knowing details of what exactly you did and what then happened would be good instead of, "it broke" or "it didn't work". :) In this case it seems like it is worth reiterating that no one should try to fully crossgrade their Debian/Ubuntu system unless they are very familiar with apt/dpkg and prepared to guide apt in what it's doing when it gives up and tries to remove most of the system. As it definitely will do when you go much beyond the kernel. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users

On Mon, Jul 22, 2019 at 10:09:06PM +0100, Keith Williams wrote: useful The "script" command is useful. When you run it, it spawns a new shell, while logging everything that happens in that shell to a file. The trouble with that is that I find I quite often don't realise that my scrollback buffer is important until after I've already started. Fortunately if you use a terminal multiplexer like GNU Screen or tmux and have it set to have a suitably large scrollback then it's easy to save that scrollback out to a file for sharing with people. So 1. Use a terminal multiplexer, and 2. Set its scrollback buffer to a decent size now. :) Easy to review and share what you typed, then. = Setting a large scrollback buffer == GNU Screen: $HOME/.screenrc defscrollback 10000 == tmux: $HOME/.tmux.conf set -g history-limit 10000 = Saving scrollback to a file == GNU Screen hardcopy -h <filename> This is typed in command mode which is usually entered by typing ctrl-a and then ':'. == tmux capture-pane -S -10000 save-buffer <filename> Again this is typed in command mode, two commands, and the default way to enter that mode in tmux is ctrl-b and then ':'. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users

apt -o Debug::pkgProblemResolver=1 -f install

My approach was to install lxc (Linux containers) onto the Gentoo install.

Then again, all that might just seem easy to me because I've been working with lxc for more years than I care to think about!