I downloaded the live KDE (64 bit). I first tried it on my work computer, but the display was blank (it has a primitive graphic card).
Next I tried on a home system. It ran quite nicely. After a while, the apper icon showed 26 updates. I’m not sure it makes sense to install those when running a live system (from a USB). So I decided to install (in test partitions, not as a replacement of my primary 12.2).
The install went well, except that it would not import my prior partitioning so I had to go to expert mode for that.
After booting, I quickly disabled apper, then logged out and logged back in without apper (and without desktop effects).
Then I tried Yast online update. Conflicts for two updates. I resolved those by choosing to not install the updates.
The list of updates now showed up. It included updating firefox to 15.0. Now that is strange, since it came with 15.0.1.
I checked the repo list. I showed the 12.2 repos.
Okay, I tried editing those to the 12.3 equivalent names. That worked for the main repos, but gave an error for the update repos (they presumably don’t exist). So I disabled the update repos.
I then tried to install “rcs” and “csh”. It is now busy downloading 241 packages. I’m not sure what I’ll get when all is done.
It used to be the case updates via [YaST] Online Update were not provided for Milestone releases. Sometimes dummy updates were placed there for testing, maybe.
After the first reboot when you reach the Desktop, [KDE] liveCD installation normally expects you to install the list of packages waiting to go, that completes the installation. Those are listed by Software Management under Installation Summary. Are those the packages you refer to (which are technically not updates)?
Yes, I’m aware of that. However, I had expected the update repos to exist, even if empty. But not a problem. Disabling the 2.2 update repos is enough for now.
Yes.
I was expecting that to happen. However, I did not expect the number of packages to be quite that large. I guess space is becoming stressed for KDE live distros, so more has to be left out until after the install.
Right now, I am trying to understand a different problem, namely why does it work at all.
I told the installer to put grub2 on “/boot”, which in my case is “/dev/sda6”. I already have a chainloader entry for that in my boot setup for 12.2. And that worked to boot 12.3M0. However, when I look at the boot sector of “/dev/sda6”, it appears to be empty (binary zeros). So I am puzzled as to how I am even managing to boot the system with that chainloader entry. Perhaps grub2 on my 12.2 install is noticing the problem and falling back to treat it as a “configfile” boot instead of a “chainloader” boot. If anyone knows what is happening, please tell me. I expect that is also a bug that needs reporting, but I would like to understand what is happening before I report.
I forgot to mention in earlier posts. Apart from the problems mentioned, everything seems to be running smoothly. KDE is at 4.9.1. The kernel is 3.6.0-rc7-1-desktop.
Indeed, as I found when installing 12.2 KDE recently. No longer just a few additional packages (like flash-player, and multimedia stuff), but also majors such as digikam, gimp, and some libreoffice components.
On 10/04/2012 08:06 AM, nrickert wrote:
>
> dd@home.dk;2493107 Wrote:
>> isn’t that a bug (which should be reported)?
>
> That’s my assumption. I’ll get to it eventually.
>
> Right now, I am trying to understand a different problem, namely why
> does it work at all.
>
> I told the installer to put grub2 on “/boot”, which in my case is
> “/dev/sda6”. I already have a chainloader entry for that in my boot
> setup for 12.2. And that worked to boot 12.3M0. However, when I look
> at the boot sector of “/dev/sda6”, it appears to be empty (binary
> zeros). So I am puzzled as to how I am even managing to boot the system
> with that chainloader entry. Perhaps grub2 on my 12.2 install is
> noticing the problem and falling back to treat it as a “configfile” boot
> instead of a “chainloader” boot. If anyone knows what is happening,
> please tell me. I expect that is also a bug that needs reporting, but I
> would like to understand what is happening before I report.
>
> I forgot to mention in earlier posts. Apart from the problems
> mentioned, everything seems to be running smoothly. KDE is at 4.9.1.
> The kernel is 3.6.0-rc7-1-desktop.
Your system has the Microsoft initial boot loader in the MBR. When that code
starts, it looks for the active partition and transfers control to the boot
loader code there. As the MBR code can only access a primary partition, your
bootstrap cannot be in /dev/sda6. You will find it in the extended partition.
That code can access /dev/sda6, and it loads the grub2 files from there.