Fresh "Alpha 3" ftp install

[doktor5000]

Not exactly. The production of Beta1 started last thursday. Cauldron got frozen, synced to an internal repo, and that is used to build the isos.
As Beta1 is released to the public next Tuesday, currently it's undergoing internal QA and for that there are several iterations of builds needed,
and for that, also often some specific problems get fixed in cauldron packages, after which a resync from cauldron is needed.
BUT if cauldron changed otherwise during that time (new versions of many packages, configuration changes etc.) then that makes it really
hard to build those isos due to all those unrelated changes, do you comprehend?

Big blocker bugs (like the kernel one, or the one with dracut) will definitely get fixed during this process. Because where's the point in releasing a Beta1 to the public, which boots nowhere?

[wilcal]

Big blocker bugs (like the kernel one, or the one with dracut) will definitely get fixed during this process. Because where's the point in releasing a Beta1 to the public, which boots nowhere?

I'm with you on that one.

[wobo]

[laidlaws]

At the moment I can't get a display or even a desktop with Cauldron. It freezes after 4 ttys are set up, at best I was able to open one of these ttys and update the system from the command line, but just now it stopped at loading dracut. I didn't wait very long to see if it would continue further. Before these updates, I couldnt get into single user (Failsafe mode) either. Should I simply do a fresh install of Beta 1?

[laidlaws]

May be you did not understand what the doctor wrote: if it is stable now it will be stable on 20th, if it is not stable now it will not be stable on 20th.

Thanks, then we should see a usable Beta 1 for both KDE & Gnome.
I just need something to install to get back working with.

You still did not understand? Freeze has been yesterday and so the situation is not likely to change before Beta 1.
BTW: I can't remember having such a messed up Beta 1, not with Mageia and not in >10 years of Mandrake/Mandriva.
BBTW: Cauldron is not something you should work with, it's a system to work on.

"You still did not understand? Freeze has been yesterday and so the situation is not likely to change before Beta 1."

That answers the question I put earlier this evening (my time):

Beta 1 will be a snapshot of how the distro stood last Thursday (was it?) If I couldn't get my Cauldron up and running on Thursday, I won't see anything different in Beta 1.

I wondered what happened in the release procedure. I thought that there would be a freeze on updates, so that the developers had no new bugs to contend with, then the beta would be a fixed up version.

[jaywalker]

So how can I influence how HAL is mounting the floppy?

I think I can now answer that question, at least in part. Ir would seem that HAL is not responsible for mounting the floppy. My evidence is that using the "click on the icon" method to mount removable drives does not create an entry in /media/.hal-mtab. The only entry there at the moment is for a vfat USB hard drive partition which I plugged in after booting.

I have looked at /etc/mtab as well. It is hard to draw any firm conclusions about what agent mounted the removable drives at the end of the list. The only point of interest is in the differences in the options listed for the vfat hard drive partition and the vfat floppy:

Code: Select all

/dev/sdg15 /media/Xchange vfat rw,nosuid,nodev,relatime,uid=501,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,flush,errors=remount-ro 0 0
/dev/fd0 /media/disk vfat rw,nosuid,nodev,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0


To me the use of the "uid=501" option in mounting the floppy would appear to solve some of the problem. Well, most really, though it will likely introduce another problem in unmounting the drive.

So we are back to the core question. Which agent is mounting these drives and where is it getting its confused notion of which options to use?

Richard

PS. When you have had enough of the "What will Beta 1 be?" question you might want to have a go at figuring out how many angels can dance on the head of a pin.

[wilcal]

Example: There was a kernel panic with the previous kernel - which may be the kernel for Beta-1. The fix (rather workaround") for this bug was found only yesterday, so it will not be in the Beta-1 ISO. Correct or not?

Last thing we need is another uninstallable iso ( ie some of the M2A3 isos )
FWIW I'm seeing over 500 additions and/or changes to the Cauldron repo
17/18/19 Feb

[jaywalker]

I understand that people can get quite exercised discussing possible outcomes of a plan in motion which can have only one outcome. There will be only 1 Beta 1 release. It will be available on Tuesday-ish. We will all know then what Beta 1 will or will not do.

You may speculate what problems may still be embodied in Beta 1, but why not wait until Tuesday to find out?

In the time since I completed this Alpha 3 install (I think it was the same day the Beta 1 snapshot was made) 3 of my 4 bugzillas have been fixed. I expect those fixes will be present in the Beta 1 release, or at the very least, they will come down in the first post-install updates. Another problem with LXDM (maxing out 1 of 3 cpus) not reported by me has also been fixed. I am quite sure there will be others I would not notice.

Fixing problems does seem, to me, to be a worthwhile use of the waiting time. I understand perfectly if nobody here has any interest in getting floppy discs to work like other removable disc formats on MGA2. After all, many (most?) new PCs don't include one in the build. Then again, I daresay that systems with floppy disc may still outnumber those without.

But the fact remains, we have a system to do things with stuff and there is no good reason why that should be artificially limited to only some stuff we think people should use, even if that is easiest.