MEPISThis forum is for the discussion of MEPIS 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 know this is going all over your head like a sonic boom. We customized our distro to exclude systemd and have some neato bold one of a kind scripts that do stuff no other distro does.
From installing flash to making our own kind of persistent pen drives.
I know this is going all over your head like a sonic boom. We customized our distro to exclude systemd and have some neato bold one of a kind scripts that do stuff no other distro does.
From installing flash to making our own kind of persistent pen drives.
Might be a wee bit complicated. But you can catch on eventually. I did. And I aint the sharpest pencil in the cup holder.
No, no, I get it all, honest. LOL Acutally I think the file I used has a bug because when I tried to clone it in mkusb it said
Code:
Libparted Bug Found!
(I like the exclamation point--as if I don't have enough stress in my life.) And the clone didn't go through yada yada yada.
I don't know what I was supposed to do with all your stuff. I only get a chance to enter info into the terminal when I'm pretty far into the installation.
Tested anitx gui install using version 15 full. Worked fine.
Tested cli-installer, and it messed up the partitioning.
I manually partitioned it, rebooted, restarted using cli-installer, and it appeared to get much more done. I am taking slight actions to prevent any screen saver involvement. Got to Grub install (finally) and that took longer than expected. After that I was able to log out (shutdown), remove the CD mount, boot it up and it worked fine.
There is something wrong with the partitioning. Perhaps not always, but there is the trick: manually partition your disk (perhaps using some other install) without actually doing the antix install. Then you can do the antix install using cli-installer onto the prepared disk and it works fine.
Tested anitx gui install using version 15 full. Worked fine.
Tested cli-installer, and it messed up the partitioning.
I manually partitioned it, rebooted, restarted using cli-installer, and it appeared to get much more done. I am taking slight actions to prevent any screen saver involvement. Got to Grub install (finally) and that took longer than expected. After that I was able to log out (shutdown), remove the CD mount, boot it up and it worked fine.
There is something wrong with the partitioning. Perhaps not always, but there is the trick: manually partition your disk (perhaps using some other install) without actually doing the antix install. Then you can do the antix install using cli-installer onto the prepared disk and it works fine.
Thanks wpeckham. That was great of you to test it like that. But still being quite the noob (but getting better) your advice is still a bit of a tall order. (Like I don't yet know how to manually partition the drive.)
But before I do anything, I tested the file I used for its integrity and it didn't pass.
Do you think that could've been a part of the problem? But of course you encountered the partitoning problem and so even if the lack of integrity is a problem it's not the only one.
Also I thought the antiX instructions were lacking. Yes, I missed a step, but even after that, there were all kinds of questions that were nowhere in the instructions.
Oh well. To be continued. Thanks so much for all the help.
P.S. And I'd still like to see this but I'm going to put it on the semi-back burner for now.
There are online pages and documents to answer questions, what you had was just an install cheat-sheet list of steps to install. Such lists are generally well tested (though not, obviously, on your hardware) and complete but sparce: a concise and minimal list of the required steps.
There are more complete install documents that cover every step in some detail, options, and advice. Few people have the patience to read them completely, thus the 'short form' you were using is quite popular.
I want to re-try the command line install and test different options. If it had failed for the developers, it would have been fixed before we ran into the problem. I have to believe that it is an easy issue to bypass.
First, you need a good download that is complete and intact. Installing a broken download just gives you a broken install, and at best results in a broken system.
I do wish we were close enough that I could pop over and show you a successful install. Alas, too many miles between and not enough time.
I have several USB keys loaded with ez2boot and various linux distributions, including antix15-full now. There would be a dozen options for (pretty automated) drive partitioning on the set.
There are online pages and documents to answer questions, what you had was just an install cheat-sheet list of steps to install. Such lists are generally well tested (though not, obviously, on your hardware) and complete but sparce: a concise and minimal list of the required steps.
There are more complete install documents that cover every step in some detail, options, and advice. Few people have the patience to read them completely, thus the 'short form' you were using is quite popular.
I want to re-try the command line install and test different options. If it had failed for the developers, it would have been fixed before we ran into the problem. I have to believe that it is an easy issue to bypass.
First, you need a good download that is complete and intact. Installing a broken download just gives you a broken install, and at best results in a broken system.
I do wish we were close enough that I could pop over and show you a successful install. Alas, too many miles between and not enough time.
I have several USB keys loaded with ez2boot and various linux distributions, including antix15-full now. There would be a dozen options for (pretty automated) drive partitioning on the set.
Thanks wpeckham. Thanks for explanation about the cheat sheet. Those complete install things are probably like those TOS on software downloads--yeah, I've got an hour to read this (and there will be five more on the other things you need to download).
I will make sure I've got a file that passes the integrity test next time.
I did what anticapitalista suggested and left the CD in (even when it told me to take it out!) and it booted up like it was going to install. I didn't have to go through all the preliminary set-up. It took me right to 'login.' (see screenshot) Then after I logged in, it ejected the disk, but when I removed the disc closed the tray and hit enter it did nothing. (see the screenshot)
So we'll see what happens next. I really appreciate all your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
