Topic: Virtual Machine Version

I tried to install NetSecL OS 4.0 in a virtual machine with Yaste live install. By the time it started to erase partition and proceeded after a confirmation to format the disk and then install the OS it had already produced an error dialog; with each of the steps that I note there was another error failure to complete those steps and I confirmed that I wanted to try to continue despite the errors. I'm new to this virtual machine thing, am I not supposed to actually install it and instead, just suspend and resume whenever I want to deal with it? Wouldn't this mean that virtual machine useage does not allow one to install non-prepackaged software or updates to existing packages? Otherwise, what exactly are the steps to install the OS on a virtual machine after I get it booted into the LiveVM?

Last edited by tau (2012-08-30 03:18:53)

Re: Virtual Machine Version

LiveVM? OK, I think I understood you. In your previous post you said that you already use the virtual machine, you downloaded the ready one from opensuse - and yes you are not supposed to install anything smile. Just use it, suspend it and then run it again whenever you want - it is like a PC but a virtual one smile. You can install packages and uninstall as you wish there is Software management in Yast.

Re: Virtual Machine Version

Last edited by tau (2012-08-31 22:41:36)

Re: Virtual Machine Version

Re: Virtual Machine Version

Last edited by tau (2012-09-02 00:07:54)

Re: Virtual Machine Version

Ok, great so it boots and you are able to see it.  Strange you get those - I don't get those errors, but try as root after that you go into graphical mode with startx.
>  Failed to write pack file. - Hmmmmmmm, doesn't sound right ...
Well if you want to install trough USB I think it would be best to use the LiveDVD you now know what option is needed to boot and it directly boots graphical. I can also build the Secure OS as a LiveDVD if you like?

Re: Virtual Machine Version

Re: Virtual Machine Version

This is correct, it boots now and I am able to see it.

Thank you for making the Secured OS a LiveCD, that is what I wanted. I will try it now.

Re: Virtual Machine Version

By the way, back when I was trying the preload ISO for Secured OS I actually did already try logging in as root with the password linux. I tried the startx, sudo startx, start x, and sudo start x while logged in as root and tux and none of the commands worked. Okay, so I just tried using the LiveUSB Secured OS and it falls asleep after the UNetBootin menu; the LiveUSB of Secured OS does not show a grub menu before my monitor sleeps like the Preload ISO used to. I'm curious which setting has changed this? I think it may have been changing from Preload. All you had to change was Configuration>Appliance>Additional Options>Add Live Installer to CDs and DVDs; but I'm not sure if it should be included or excluded in order to show the boot options. It seems you changed more than this because now I don't see the menu where I can enter boot options this time. Was the additional change you incurred by Configuration>Startup>Default Runlevel? It needs to be the same as it was before when I was able to enter boot options like nomodeset. I'm willing to do a clean installation with the Preload, especially since it might be the only way to set boot options. I already erased the extra partition I had in place for it to be ready to install to anyway.

Last edited by tau (2012-09-03 02:16:52)

Re: Virtual Machine Version

11

Re: Virtual Machine Version

I discovered which one out of preload, live, or USB is the one with boot options because I tried all of them. It is the USB one (so i.e. how you can directly control the boot options environment, by building the USB appliance that you just did along with a couple others). I have a couple pictures I will send you of the errors I get when trying # startx    while signed into root with the linux password. But, I think I just need it (specifically the USB appliance) built one more time which might surpass the errors or avoid them. This time build it with the runlevel set to 5: Graphical Login, please. Then we'll see if this will work.

Re: Virtual Machine Version

I switched back to Graphical. Try now.

13

Re: Virtual Machine Version

You/I/We did it! I'm reporting from the LiveUSB right now. If you plan on making more FAQs for this latest succes, be sure to say that if one encounters a black screen try using the USB & disk image download (with graphical runlevel and Live Installer, more on this later) in order to be able to type and enter boot options like nomodeset like I do.

But, I'm sorry to say that it looks like you forgot to add Configuration>Appliance>Additional Options>Add Live Installer to CDs and DVDs. If you check it on SuSeStudio and you find it says it was on with version 4.0.9, maybe the Live installer does not go on the USB build no matter what you try and only goes on the CD/DVD and Preload maybe? If that is the case, how do I install NetSecL from the Live desktop I have found my way into without a Live Installer from Yast because I can not find how to install NetSecL from Yast; it looks like Yast is missing the Live Installer sad .

14

Re: Virtual Machine Version

Things I did differently in addition to using your update to Secured OS that includes the graphical login is that instead of uncompressing and untaring the download with $ tar xvzf foo.tar.gz    or $ tar -xvzf foo.tar.gz    I did $ tar -zxvf foo.tar.gz    which may do different stuff than the two former tar commands because they are the only two orders of letters which will not return an error and make a visible .raw file. Hmm, I should check if the md5sums of the /dev/sdb and the .img ($ mv fu.raw fu.img) file are the same with this new $ tar -zxvf foo.tar.gz    structure that the $ tar xvzf foo.tar.gz    and $ tar -xvzf foo.tar.gz    were unable to do... I'll let you know when I boot into my hard drive again once I'm off the Live Secured OS desktop because I'm still on it--enjoying the success smile ! Another thing step I did differently is the way I formated my USB drive before using ImageWriter, which may not matter as much because ImageWriter probably formats it itself anyway, but this time the different part I did there is format to ext4 instead of all formats. All formats compatibility is what I had been formatting the USB  drive with before writing to it, but for the reason I stated previously this difference in procedure probably didn't aid our success? So, in degrees of certainty of why I am now able to both keep a waking monitor and experience the LiveUSB desktop is because of using the USB & disk image, then the graphical login runlevel, on to the different tar terminal, and finally with the least amount of certainty formatting to ext4. Let me know if you want me to try all the consequences of the last two procedures in order to give the FAQ the exact information one needs to succeed like I did (e.g. or you could just make sure to instruct  $ tar -zxvf foo.tar.gz    right off the bat because the instructions on the download website do not say which exact terminal to use; all it very vaguely says is to uncompress and untar, leaving the user up to find out how to do so specifically).

Re: Virtual Machine Version

16

Re: Virtual Machine Version

Last edited by tau (2012-09-04 20:26:20)

Re: Virtual Machine Version

You don't need another computer to use the dd tool. Do the transfer the way you did to the USB.

18

Re: Virtual Machine Version

Sorry, the instruction you gave say how to use netcat to install from another machine over a network.

So, if I'm to disregard the link and try to think about how to change the dd to USB into dd to partition it would be like the following, right? $ sudo dd if=/dev/sdb/Secured_OS.x86_64-4.0.9.raw of=/dev/sda2 bs=4k conv=fdatasync    where sda2 is the empty partition (i.e. once I make it again and then do $ df    again to see what it will actually be). I'll try it.

Re: Virtual Machine Version

Try this should work, finally. The link was for the comment actually which got me to the idea of doing it the same way nothing more.

20

Re: Virtual Machine Version

I tried to make an USB image with SuSe Studio to include the .raw file but it is not accepting any of my file uploads to the Studio, not from my file manager nor the download link for your appliance from the Studio itself. Even if I could I think I would still need to get a larger USB drive in order to fit the .raw file onto the USB within the Live Desktop.

Can I use dd to palimpsest the blank partition with the .raw file from within another partition that is on the same mounted drive or does the whole hard drive have to be unmounted to do what I need to with the extra partition? I tried this already and failed so I think I need instructions. Did I fail to dd the .raw file to one partition from another partition on the same drive because it isn't possible or did it not work because I need to format the new partition? If so, which format (e.g. ext4, unformatted, etc.) am I supported to make out of the unused partition with GParted Live and does that matter?

21

Re: Virtual Machine Version

I don't think it is possible what you asking. Has dd ever even been used in the way you want me to?

Re: Virtual Machine Version

Re: Virtual Machine Version

I spoke to SuSe Studio I really hope they do any ofmy suggestions, I have been requesting some improvemnts in the boot options since alot of time it is unfortunate that none of these came trough. I will wait for their reply. If not I'm  thinking of the following option, but I will need more time for this - I will manually edit the preload ISO and I will set this boot option (nomodeset) for you so you can install normally.

24

Re: Virtual Machine Version

Yes, getting SuSe Studio to have boot options in all their builds would be nice. Then, I could use the Live Installer. I was thinking of asking you to ask SuSe Studio to get the Live Installer on the USB build, but putting boot options on the others is another way to solve that. I think you should wait for a reply on your suggestion, and if it is negative then wait for a reply on my suggestion to add the Live Installer to the USB build instead, before manually editing the Preload ISO yourself. I'm going to look at the instructions now big_smile .

25

Re: Virtual Machine Version

The only thing I'm left that I need to understand is how set up dual booting because those instructions say how dd a whole hard drive, not only one of the partitions in a drive. I found another 4GB flash drive to put the SecuredOS onto. Then, I booted into the LiveUSB desktop of GParted. I'm to the point where I've used dd from the second USB stick with SecuredOS to copy it to the extra partition. Now, I just need to know how to make the two partitions cooperate and be aware of each other's existence. Do I edit grub? How? Which partition's/OSe's grub do I edit? Both?

Should I risk everything (my current Ubuntu OS) to follow the instructions completely by dding the whole drive after I make only one partition out of it and format it? I probably won't have to deal with grub then, right?

Last edited by tau (2012-09-06 01:16:17)