Bug 299625

Summary: YaST Partitioner and partition active (boot) flag status
Product: [openSUSE] openSUSE 11.0 Reporter: Forgotten User Xh41Ao4q6j <forgotten_Xh41Ao4q6j>
Component: YaST2Assignee: Duncan Mac-Vicar <dmacvicar>
Status: RESOLVED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P5 - None CC: aj, dmacvicar, locilka, mrmazda
Version: Alpha 2   
Target Milestone: ---   
Hardware: 64bit   
OS: Linux   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User Xh41Ao4q6j 2007-08-12 07:25:48 UTC
With use of generic boot sector ability to change active flag on partitons can help to restore previously active grub configuration in an easy way. 

Now it is possible to do that using console tools like fdisk or cfdisk.
Comment 1 Stefan Fent 2007-08-13 06:59:39 UTC
This should already be done, in cases where we can guarantee that the system is bootable, eg /boot on a primary partition.

But, I'm not really sure, want the bug here is.
Comment 2 Forgotten User Xh41Ao4q6j 2007-08-14 02:36:21 UTC
I changed severity to enhancement. That is what I missed first time. 

In question is missing ability to set/change/view active (boot) flag on partition using YaST partitioner. There are other programs (fdisk, cfdisk) that can be used for that task, but I guess that YaST and it's modules should be central point of system administration. 

For a long time this feature was irrelevant as GRUB specific code was installed in MBR and it was not important what partition was active. With generic MBR that looks for a bootable partition this is important feature for YaST partitioner. 

I stumbled over this looking how to explain what to do in case that boot screen installed with 10.3 Beta version is not what user wants, and he wants to have back previous installed with 10.2. I got to resort to explanation using cfdisk as you can't use YaST Partitioner. 
Comment 4 Thomas Fehr 2007-08-14 09:23:19 UTC
New features need to go through FATE, not bugzilla.
Comment 5 Forgotten User Xh41Ao4q6j 2007-08-20 01:49:09 UTC
How to access FATE? 
Comment 6 Thomas Fehr 2007-08-20 09:55:00 UTC
To my knowledge, it is not publicly accessible.
Comment 7 Forgotten User Xh41Ao4q6j 2007-08-20 23:23:48 UTC
That seems to be kind of catch 22. 

New features need to go through FATE.
FATE is not publicly accessible. 

I guess that the only way would be to have faith that you are going to put it in a FATE ;-) 
Comment 8 Lukas Ocilka 2007-10-19 12:32:47 UTC
Thomas, sorry for being so picky, but is RESOLVED/INVALID really the correct way to close an enhancement that 'should be filed into FATE' :)?

If there is a FATE request filed (based on this enhancement), we often close the bug as LATER. Rajko hasn't any access to FATE so he can't file a FATE request ;)

So a better RESOLUTION would be probably LATER or WONTFIX.
Comment 9 Thomas Fehr 2007-10-22 10:53:57 UTC
If an feature request comes in via bugzilla I consider INVALID the correct
resolution.
But if you prefer WONTFIX, finw with me.
Comment 10 Felix Miata 2007-10-22 12:41:47 UTC
You guys are missing the point. How are OpenSUSE alpha/beta testers and users supposed to request new features except via Bugzilla when FATE is not accesible to them? Why does Bugzilla have an ENHANCEMENT status if not for new/enhanced features requests?
Comment 12 Andreas Jaeger 2007-10-22 16:45:26 UTC
We're going to open FATE so that openSUSE users can contribute to it as well.

We will continue to handle enhancements requests here - and make the process clear and visible to everyone.  I'm sorry for this confusion here.

Thomas, could you add this *yourself* as feature to FATE, please?  Once you've done that, feel free to resolve the bug.
Comment 13 Thomas Fehr 2007-10-22 16:47:50 UTC
No, since I do not consider this a enhancement that is worth the effort 
needed to handle this correctly.
Comment 17 Duncan Mac-Vicar 2007-10-24 16:10:16 UTC
Rajko, this enhancement will be closed as the implementation effort seems to be high for the benefit it gives according to the developers.

If you have better usecases, feel free to post them here, but please don't reopen it unless there is a good reason.

About the FATE/bugzilla issue, nevermind. Use bugzilla enhancements with a good use case to file enhancement proposals, unless you are in contact with some developer.
Comment 18 Felix Miata 2007-10-25 00:05:02 UTC
Duncan, AJ reopened, not Rajko, so I would think there must be some justification internal to Novell to keep it open and valid as an enhancement.
Comment 19 Andreas Jaeger 2007-10-25 08:08:34 UTC
Felix, this is fine now for me.  I reopened and asked for a proper evaluation and an answer to both comment #9 and #13 - and that's what Duncan did.

Thanks!
Comment 20 Felix Miata 2007-10-25 12:38:46 UTC
As is typical of bugs resolved as a result of Novell internal discussion, it wasn't explicitly noted as such. The lack of that small bit of information makes it look like resolution was a unilateral act of the assignee, unless it came from a Novell non-assignee.