Geekly Articles each Day
📜 ⬆️ ⬇️

Installing openSUSE 11.3 with a kettle

Preamble


I am a "winyzyatnik" diligently seeking to join the world of Linux. My main goal was to see KDE4. * Live, for which the openSUSE 11.3 distribution was chosen. Actually, there was not much to choose from, because I can only get this amount of data from the Hacker DVD magazine, and all the other distros I have got from Gnome.
A couple of months ago, in exchange for a long-lost laptop, I bought a netbook, naturally, without a DVD-drive. And it didn't bother me too much: I installed Windows using a 4-gigabyte flash drive, and I simply copy the files from another laptop using a cross-over cable.
But then it's Linux time ...


Many fail and one success


Well ... Copying to my hard file, opensuse-i386-11.3.iso, I could not even imagine how many hours I would spend on installing the “chameleon”.
Naturally, the easiest way was the first to go into action:
Flash-drive + ISO

Armed with my own combat, which had seen dozens of images, thousands of files, a couple of controller flashing, and an incredibly buggy Kingston DT100 and UNetbootin drive, I set about putting the chameleon on the chip.
The image did not fit on the disk. There is nothing more to say. Fail.

VirtualBox + real partition

In the magazine "Hacker" was published allegedly a very common way to install different operating systems from under Windows: connect a real hard disk (or a separate partition) to a virtual machine.
So, what we need:
  1. go to the folder with VirtualBox and command:
    VBoxManage internalcommands createrawvmdk -filename d:\realhd.vmdk -rawdisk \\.\PhysicalDrive0
  2. Create a new VM. allocating more resources to it, and connect the resulting d:\realhd.vmdk as a hard disk;
  3. we connect the image we have with the distribution kit;
  4. we start.

Works. But this feeling remained exactly until I remembered that the Atom was inside my calculator, even the N550. Moving the cursor - with a huge delay, about the reaction to pressing silent.
In the end, by hook or by crook, the installation comes to partitioning the disk into partitions and mounting them. Here it is plugging. Up to this point I reached and failed on it 3 or 4 times:
  1. error mounting NTFS partitions;
  2. check the previous one;
  3. canceled mount. Got an error when cutting the disc.

In general, I began to sin on VirtualBox and its crooked connection to the physical disk (and in vain, and further experiments confirmed this).
On this patience ran out, the disc lay down on the shelf, the image went to the basket, I climbed with the “man” to create more productive ways to implement my evil plans ... Ah, yes: fail.
')
GRUB4DOS + ISO

Shoveling the folder with the distributions of various programs, I came across WinSetup. But now it's not about the “setup”, but about the magic thing that is for him official - GRUB4DOS.
I already read that he was able to directly load the OS from ISO, but the first attempts did not succeed - and it was hard to reboot each time (then I did not connect the VM to HD, nor did I know about the command line in Grub) . Let's apply a more scientific method - reading configs templates.
But first, using grubinst_gui.exe install the bootloader on the disk.
In order not to interfere much with the life of the OS, I had previously prepared a hundred-megabyte partition (as it turned out, so later there was less fuss and more tasty buns).
So:
  1. choose a hard disk;
  2. update the Part List using the “Refresh” button, select the required section in the list that is full, focusing on the file system and volume size.
  3. check the box “Grub 2” and install (“Install”);
  4. Copy the coarse files to the root of the tortured section and get down to the menu, in my case the following items were added:

    # (hd0,0)
    # 7, .
    title Windows 7
    rootnoverify (hd0,1)
    chainloader +1

    # "d:\sys\Images\openSUSE11.3.iso"
    # Win- () *nix- ()
    title Install openSUSE 11.3
    map (hd0,2)/sys/Images/openSUSE11.3.iso (hd32)
    map --hook
    chainloader (hd32)

Another important point: the image must be contiguous, without holes, or, more simply, defragmented. Take the advice of Grub and call on the contig utility from the Sysinternals kit:
contig d:\sys\Images\*
Reboot, select the second menu item. Installer. Textual. Requests to insert a disc by number one. Let's play the fool and click "Cancel". Settings ... let's send him an isosnik as a repository ... It didn't work out. Well, okay. Fail.

Smoke break and thinking

I hear, I hear the whistles of the venerable and not very linuxoids and the hooting command line gurus. The cries of “Googling!” ...
Of course, it would be possible, but ... deep Adygea, Beeline modem, speed 32Kb / s ... It’s better a scientific tyk.
In general, additional methods formed by poking a finger into the screen and the brain.

Flash-drive + ISO trimmed

I come back to the first point, take the ISO and set UltraISO on it - yes, only rpm chips are flying. The image of "losing weight" by half a gigabyte and now fits perfectly on a flash drive.
This time I wrote the disk using WinSetup (detailed instructions are attached to the distro), because a recording made by UNetbootin "did not play."
Reboot. And the chameleon YaST refers us to the 4th item, namely the text installer and not a hint of the connected distribution. Fail.

GRUB4DOS + ISO + unpacked image on ntfs partition (hope for success)

We turn to the next milestone of distortions - unpacked images.
Since the text installer allows you to connect a folder to yourself, we will use this.
  1. using an archiver (7Zip, WinRAR) or by mounting a virtual CD drive, extract the contents of the disk to a folder on the HDD (I have an NTFS partition), for example “d: \ suse”;
  2. We will achieve the appearance of a text loader - I loaded using the 3rd method.
  3. we start virtualka and we try. The face is blurred in a contented smile - after the text, the graphical installer was immediately loaded, even without questions (well, why did it not alert me?), - the crash of the VM and restart the poor netbook.
  4. Download our installer and smile slowly slipping: the same question “Where is the drive?” doesn't respond to the specified folder. The most disgraceful file.

And all because some people (hands would tear him off) did not unmount the ISO from the VM during the test! It's a shame, comrades!

GRUB4DOS + ISO + unpacked image on ext2 partition (new hope)

Patience is running out, the brain is boiling. Boils and does not know that success is so close ...
To me, apparently, the insight descended, and guessed to put the distribution on the linux section. But here it was not so simple.
PartedMagic refused to run. For all the above reasons.
It's good that I already had Ubuntu in VirtalBox. In principle, it does not matter what kind of distrib, if only it can be configured sections.
  1. we connect to our realhd.vmdk our real-virtual disk realhd.vmdk ;
  2. we divide our unpartitioned area into additional sections - I did not bother and made two - for / and for swap. Format in ext4;
  3. mount our future root directory (let it be /media/suse );
  4. we connect the ISO image and copy the contents to the /media/suse/suse_inst/ ;
  5. Reset, because the hot restart forces no longer exist. Joke, you can't do that :) ;
  6. We do everything as in previous times - a text installer -> folder (now on ext4, not on NTFS) -> a graphical installer appeared -> agreement and initial setup -> disk partitioning, here you need to give up everything. selecting manual settings and mounting our sections. Swap, naturally, picked up without problems. But the root ... It turned out that it is impossible to mount and, accordingly, install on the disk where the installation files are located - so as not to accidentally damage them. That's it. Fail.

GRUB4DOS + unpacked ISO on a separate ext2-section

We do everything the same as in the previous attempt, except for points 2,3,4 - we have to create another additional partition (I did ext2), on which we place the distribution kit, which we specify when installing as a repository.
Success.

Additional Kosyachki


  1. Watch carefully what openSUSE offers to do in automatic mode. I, for example, he wanted to wipe all existing partitions and zayuzat the entire disk to fit your needs (although this was not under the virtual machine).
  2. The chameleon couldn't create entries for himself in the existing Grube, so I didn’t install a bootloader for him at all. To do this, you need to write down all the info that he wants to put in the loader - the kernels and their parameters, and after installation, attach them to Grub. I did this:

    title openSUSE 11.3 Desktop
    kernel (hd0,6)/boot/vmlinuz-2.6.34-12-desktop root=/dev/disk/by-id/ata-SAMSUNG_HM321HI_S26VJ9FB404025-part7 resume=/dev/disk/by-id/ata-SAMSUNG_HM321HI_S26VJ9FB404025-part5 splash=silent quiet showopts
    initrd (hd0,6)/boot/initrd-2.6.34-12-desktop

    title Xen
    kernel (hd0,6)/boot/vmlinuz-2.6.34-12-xen root=/dev/disk/by-id/ata-SAMSUNG_HM321HI_S26VJ9FB404025-part7 resume=/dev/disk/by-id/ata-SAMSUNG_HM321HI_S26VJ9FB404025-part5 splash=silent quiet showopts
    initrd (hd0,6)/boot/initrd-2.6.34-12-xen

    title openSUSE 11.3 Failsafe
    kernel (hd0,6)/boot/vmlinuz root=/dev/disk/by-id/ata-SAMSUNG_HM321HI_S26VJ9FB404025-part7 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
    initrd (hd0,6)/boot/initrd
  3. When installing, do not mount NTFS partitions - this led to an error for me.

Conclusion


It was such thorny paths that I became the owner of openSUSE 11.3. There were many questions, and even more appeared. But that's another story ...

PS I apologize for the lack of screenshots, but I could not get through this hell again.

Source: https://habr.com/ru/post/123872/

More articles:


All Articles