Trying (in vain, I might add) to install Slack alongside Ubuntu

nohopeforme · 11-01-2019, 06:22 PM

Quote:

Originally Posted by colorpurple21859

did you do what I suggested in an earlier post, boot into ubuntu open a terminal

Code:

sudo blkid | grep /dev/sdc3

edit the grub.cfg slackware menuenty and change to root=PARTUUID=the number from the blkid output on the linux line.

This is what my current entry looks like for the huge kernel:

Code:

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Slackware 14.2 (on /dev/sdc3)' --class slackware --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-c364ca81-25c0-42ed-9c46-88d61cb0870a' {
        insmod part_gpt
        insmod ext2
        set root='hd2,gpt3'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt3 --hint-efi=hd2,gpt3 --hint-baremetal=ahci2,gpt3  c364ca81-25c0-42ed-9c46-88d61cb0870a
        else
          search --no-floppy --fs-uuid --set=root c364ca81-25c0-42ed-9c46-88d61cb0870a
        fi
        linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3
}

So, you're saying I want to change "linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3" to "linux /boot/vmlinuz-huge-4.4.14 root=PARTUUID=whatever my PARTUUID #" is?

colorpurple21859 · 11-01-2019, 07:25 PM

yes the partuuid= that was given for /dev/sdc3 by the blkid code.

nohopeforme · 11-02-2019, 12:55 AM

Quote:

Originally Posted by colorpurple21859

yes the partuuid= that was given for /dev/sdc3 by the blkid code.

So much for that, lol. I did as directed and not only could I not boot into slack...but I hosed my ubuntu install as well. It's all good, though. I managed to reinstall ubuntu, so I'm essentially back to square one. Really appreciate you guys putting up with my idiotic noob self :-)

colorpurple21859 · 11-02-2019, 07:00 AM

Quote:

So much for that, lol. I did as directed and not only could I not boot into slack...but I hosed my ubuntu install as well

That don't make no sense, that shouldn't have done anything to ubuntu. What happened in detail when you rebooted to cause a reinstall of ubuntu? If you want to try it one more time, press e at the grub slack menu entry when you first boot and change it there, that will only be a temporary change.

BW-userx · 11-02-2019, 07:17 AM

You should have just installed Slackware and got on with it, turning your noob status to an actual, "Hey, I'm actually learning how to use Linux/GNU", and not relying on a windows like clone done with linux/GNU keeping one from from moving past the I just point and click for everything I do, if I cannot do that then I don't get anything done. .. .. ..

One learns how to survive by actually putting themselves into situations where they need to survive. (or taking classes on survival, then getting themselves on a tv show called Naked and Afraid, and that is a non related Linux/GNU analogy)

nohopeforme · 11-02-2019, 10:17 AM

Quote:

Originally Posted by BW-userx

You should have just installed Slackware and got on with it, turning your noob status to an actual, "Hey, I'm actually learning how to use Linux/GNU", and not relying on a windows like clone done with linux/GNU keeping one from from moving past the I just point and click for everything I do, if I cannot do that then I don't get anything done. .. .. ..

One learns how to survive by actually putting themselves into situations where they need to survive. (or taking classes on survival, then getting themselves on a tv show called Naked and Afraid, and that is a non related Linux/GNU analogy)

Ya know, I bounced that around a couple times. That said, if I go that route...I still never figured out how to make slack work along side ubuntu. As you can tell by most of my replies, I'm still rather green behind the ears. I try my best to start at the bottom and work my way up when I'm learning new things, as opposed to running before I can walk. Truth be told, I may still wipe ubuntu and go straight slack. I'm just not ready to give up on this venture quite yet. :-)

BW-userx · 11-02-2019, 11:09 AM

Quote:

Originally Posted by nohopeforme

Ya know, I bounced that around a couple times. That said, if I go that route...I still never figured out how to make slack work along side ubuntu. As you can tell by most of my replies, I'm still rather green behind the ears. I try my best to start at the bottom and work my way up when I'm learning new things, as opposed to running before I can walk. Truth be told, I may still wipe ubuntu and go straight slack. I'm just not ready to give up on this venture quite yet. :-)

install slack and learn how to make Ubuntututu work along side of Slack instead. same thing different approach.

better to use slack for a bit before jumping into the lake before you learn how to paddle the boat.

after you've used Linux for a while having learned how to customize, and figure out work around to get something to work the way you want it to. then I'd say go a little more complex.

I got Ubunutu and slack to work together without issue. so I do not really know what you're issue was not being there to see what you're doing to help you out in that fashion.

it is basic, install one then the other, with UEFI that is the catch. install slack UEFI.

usb stick with a GPT partition table on it then, burn ISO to it then boot it in uefi mode, then take it from there. it might help you learn how slack needs to be done then taking that bit of knowledge to the next step with Ubuntututu.

which I am sure is easier to install UEFI. Knowing how both need to be to get them to work separately, then just put that info together to get them both to work together like you wanted to in the first place.

colorpurple21859 · 11-02-2019, 03:03 PM

Maybe slackware-current will work better on your hardware.
https://docs.slackware.com/slackware:liveslak
https://slackware.nl/slackware-live/latest/

nohopeforme · 11-20-2019, 02:57 PM

Well, folks...I ain't dead, lol. I never had any luck with getting slack installed with ubuntu. However, I did manage to get slack installed on it's own drive. I found a gentleman on youtube, by the name of Mike Murphy (https://www.youtube.com/user/mikemurphycs), that has a rather impressive step by step playlist for installing slack with efi and grub. I dunno, it might be overkill for everyone here, but for my noob self, it was right down my alley. I just want to let y'all know I haven't given up and I *do* appreciate everyone who took the time to try and show me their expertise :-)

samtsco · 06-12-2020, 11:59 PM

Thanks for this thread. I need to install dual slack/arch on EFI. And I'm a newpie. This will help.

Ultimately, I want to write my build script so I can do FEA on slack but meanwhile I need to save time by using Arch and its ready-to-go Calculix package.

I currently run slackware current on an EFI machine. It doesn't quite work right, and I have to boot with a usb stick, because (I'm pretty sure) I installed per instructions for BIOS. Am poised to reformat and reinstall.

Come to think of it......I could install Ubuntu and use calculix on it....instead of Arch...wonder how much time that would save/cost??

Not an option: Windows. My dual-booting with Windows days are through. Hooray!

Thank You Everyone!

quickbreakfast · 06-13-2020, 11:39 PM

I'd like to suggest a new thread for a new problem.

Quote:

Originally Posted by samtsco

Thanks for this thread. I need to install dual slack/arch on EFI. And I'm a newpie. This will help.

I currently run slackware current on an EFI machine. It doesn't quite work right, and I have to boot with a usb stick, because (I'm pretty sure) I installed per instructions for BIOS. Am poised to reformat and reinstall.

Before you re install, when your electronic marvel boots into Slackware, use Gparted to have a look where your boot flag lies.

If the boot flag ain't attached the root partition, then move the boot flag until it is.

samtsco · 06-16-2020, 03:18 PM

I already have a thread regarding my incorrect install I have run till today. It is in Slackware - Installation, titled, " Newbie Request, but Think I want it from Slackware People"

Per your tip, I opened gparted which had an empty flags column. I saw how to boot flag the appropriate partition but did not execute because I am about to proceed with the new GPT table, and saw no value in making changes to an install that must be redone. The reason why is all in the other thread, but basically, I have no efi partition on my efi machine.

We shall see whether I still have no boot flag after I partition, format and install correctly. And I will make a note of this on that other thread. Many thanks.

Oh, and to make it clear to any readers just skimming over this, my incorrect installation issues, including this one of having no boot flag, is not related to the topic of dual-boot installations. I have yet made no move toward setting up a dual-boot system.

samtsco · 06-19-2020, 05:05 PM

I have given up the dual-boot objective.

Despite a very explicit and detailed step-by-step guide, I failed to get Arch to run. Didn't like some fundamental things about Arch anyway. Seems to me it is a nice idea but it tries to make things too easy and as a result breaks down - much like the fed gov. I don't like software (or anything else) that tries to do too many things FOR you; that is why I abandoned Windows. To me, computers are to do the repetitive for me, and all other control should be mine. And if I want to get fancy with my file management, let me write my own script. Plus, that whole systemd thing. I don't know much about it but to me it smells like a Windows-esque deal, and I'm glad for slack and it's slowness to get away from Unix-esque philosophy.

Arch tried a different approach than Slackware to deal with the rock in the field, dependencies, but in reality, the rock sits there the same. It cannot be simplified away. So in a sense, Arch is simple and lightweight, but ultimately, not any simpler or less heavy than a full slack install.

I could just install Mint and get my FEA done but I think I will instead get started on learning how to write a build script, and MAYBE get a little fea done meanwhile on a windows box instead of bothering further with more than one linux distro.

Just use two machines if you need to use Windows but want to learn Slack, is my new thing. And I don't need any linux beside Slack, I don't think. So I have no need for dual-booting. I dual-booted Windows and a distro (forget the name) based on Debian years ago. It's great to see things progress to where I can get along with a straight linux environment.