Description of problem: When typing drakboot, the default behaviour is to configure the autologin. To configure the bootloader one needs to add the --boot option. This is very unfriendly. Is it possible to have drakboot behave like --boot by default? And can we maybe create a drakautologin for the autologin feature? One advantage is that it makes it tab completion friendly on the command line. It is also not intuitive at all to type drakboot to configure the autologin.
Blocks: (none) => 7161
Those bugs are unrelated.
Blocks: 7161 => (none)
This has always been the behavior of drakboot. The odds are high that users will alter autologin settings more often than their bootloader which get updated when new kernels are installed/removed
Closing
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
I don't agree. It's not about the odds that someone wants to change the autologin. There is more odds that someone wants to install software than to configure the bootloader, so you want to have 'drakboot' launch rpmdrake by default? drakboot is called drakboot because it configures the bootloader. Back in the mdv days, drakboot was doing that (I tested it on Mdv 2008.1). By some strange circumstance, drakboot came to do the autologin thing as well and the autologin was made the default. This is not right. Anyway, this is definitely a bug, and it's a usability bug. When I want to change the autologin thing when my X fails, why would it make sense to type 'drakboot'??? Reopening, as "it has been like that for a long time" or "The odds are high that users will alter autologin settings more often than their bootloader" are not good reasons not to fix this bug.
Status: RESOLVED => REOPENEDResolution: WONTFIX => (none)
A solution is to have drakboot configure the bootloader, and a drakautologin to configure the autologin. This would make sense, and probably not be very hard to implement. PS: I can propose a patch if needed.
Current behavior is here since 2004. And it's not a bug. We've different opinion about the default mode and me the maintainer won't change it hence the resolution.
Status: REOPENED => RESOLVEDResolution: (none) => WONTFIX
I don't understand your position and how it could make sense to type 'drakboot' and get the autologin configuration tool ... If you give me a reason like "it's too complicated to change it and it doesn't affect many users since it's been many years like that", I can get it (especially if it means changing the installer and a lot of other occurrences of the call to drakboot). We can only speculate how many people got affected by that, but I got affected by that several times and could not find the draktool to configure the bootloader in console mode (I never thought that drakboot would need a --boot option to do what its name says it should do). I had to get a cd and use the bootloader configuration tool from the installer instead ... BTW it's not like that since 2004, since I tested on an old machine with mdv 2008.1, and drakboot was correctly starting the bootloader configuration tool.
commit 41fc00cea5d49e46870db72a5612cbe9f67f8e26 Author: Thierry Vignaud <thierry.vignaud@...> Date: Fri May 22 03:09:37 2015 -0400 split drakautologin from drakboot (mga#7160) --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=41fc00cea5d49e46870db72a5612cbe9f67f8e26
commit 53931631390aac9ffe8fc0a81cbe86f866823ad6 Author: Thierry Vignaud <thierry.vignaud@...> Date: Fri May 22 03:09:37 2015 -0400 split drakautologin from drakboot (mga#7160) --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=53931631390aac9ffe8fc0a81cbe86f866823ad6
Fixed
Resolution: WONTFIX => FIXED
Reopening to reuse this report for Docteam. Docteam will need to adjust the MCC manual for Mga6 'drakboot' became 'drakautologin' 'drakboot --boot' became 'drakboot' So: * drakboot.xml will need to be moved to drakautologin.xml (and its xml:id needs to change accordingly) * drakboot--boot.xml then needs to be moved to drakboot.xml (and xml:id) * the CLI commands in those xml files need to be updated * the links to those two xml files in mcc-boot.xml need to be corrected. * drakboot.png needs to be moved to drakautologin.png * update the xml:id and fileref for that screenshot in drakautologin.xml Is there an easy way to download http://docteam.mageia.nl/en/MCC/content/images/drakboot.png and any other http://docteam.mageia.nl/*/MCC/content/images/drakboot.png so that they end up locally in content/en/drakboot.png content/fr/drakboot.png etc. ? They could then be renamed with one command, zipped and uploaded (I don't think any drakboot --boot screenshot needs to be renamed)
Status: RESOLVED => REOPENEDCC: (none) => marja11Resolution: FIXED => (none)Assignee: thierry.vignaud => doc-bugsSummary: drakboot should have the --boot behaviour by default => update the Mga6 MCC manual: the drakboot command became drakautologin, drakboot --boot became drakboot
This was kindly fixed by lebarhon and yurchor updated the .pot and .po files, after new manuals are generated the changes will end up in the mageia-doc package and on doc.mageia.org. Closing
Status: REOPENED => RESOLVEDResolution: (none) => FIXED