May 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305584] Do not assume fixed and contiguous device numbers in installation and management tools for storage
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Stanislav Visnovsky (visnov) Feature #305584, revision 11 Title: Do not assume fixed and contiguous device numbers in installation and management tools for storage openSUSE-11.2: Evaluation Priority Requester: Mandatory + Projectmanager: Important Requested by: Matthias Eckermann (mge1512) Requested by: Tejun Heo (teheo) Description: Subject: [Research] head up on upcoming extended block devt change From: Tejun Heo <tj(a)kernel.org> Date: Thu, 18 Dec 2008 12:59:21 +0900 Reply-To: research(a)suse.de Hello, all. From soon to be released 2.6.28, the kernel contains extended block devt support, which basically allocates block device numbers dynamically from major number 259 (might expand to other major numbers if ever necessary). This means that device numbers belonging to the same device become non-contiguous and can be on different major numbers. This will remove the 15 partition limit on /dev/sdX's and increase the total number of supported SCSI disks considerably. Also, it's used by md to allow partitioning of /dev/mdX's thus removing the distinction of partitionable and non-partitionable md devices. For example, /dev/sda with 60 partitions can look like as follows. # cat /proc/partitions major minor #blocks name 8 0 156290904 sda 8 1 8001 sda1 8 2 8032 sda2 8 3 8032 sda3 8 4 1 sda4 ... 8 15 8001 sda15 259 0 8001 sda16 259 1 8001 sda17 259 2 8001 sda18 ... 259 43 8001 sda59 259 44 8001 sda60 For detailed overview, please take a look at the following message. http://article.gmane.org/gmane.linux.kernel/701825 As device node creation is completely dynamic these days, installed systems usually can cope fine with this change; however, in installation and management tools, there seem to be many places which assume fixed and contiguous device numbers. To ease hunting down those areas, a debug option is available which forces every block device to be allocated on the dynamic major non-consecutively. With the debug option turned on, the above disk will look like the following. # cat /proc/partitions major minor #blocks name 8 0 156290904 sda 259 262144 8001 sda1 259 786432 8032 sda2 259 131072 8032 sda3 259 655360 1 sda4 259 393216 8001 sda5 259 917504 8001 sda6 259 65536 8001 sda7 ... 259 114688 8001 sda55 259 638976 8001 sda56 259 376832 8001 sda57 259 901120 8001 sda58 259 245760 8001 sda59 259 770048 8001 sda60 So, the installation / management tools need to follow /sys/block/*/device/driver to determine which type of device it is and use /sys/block/*/dev to determine its device number. I'll add a kernel parameter (say, block.force_ext_devt) so that this debug option can be turned on and off during boot so that people who don't work on related subsystems don't have to suffer. I'm not sure how and when to proceed with this yet but I definitely think we'll need plenty of time to sort this out completely. Any ideas on how to proceed on this? Thanks. -- tejun Discussion: #1: Tejun Heo (teheo) (2008-12-22 13:31:11) So... when and how do we proceed with things like this? I wanna enable it in HEAD but SLES11 hasn't branched out from HEAD yet but I don't think we should wait till SLES11 is released. #2: Matthias Eckermann (mge1512) (2008-12-22 10:24:58) (reply to #1) SLE 11 has precedence over anything else we currently do - with respect to focus and time spent on it. Thus we should concentrate on SLE 11 and wait with those changes after release of SLE 11. There are more than enough P1 and P2 issues with the SLE 11 kernel to work on, ... Vojtech? #3: Vojtech Pavlik (vojtech_pavlik) (2008-12-22 12:14:19) I agree, Matthias, and I see no reason why this couldn't wait until SLES11 branches out of HEAD. #4: Tejun Heo (teheo) (2008-12-23 11:52:19) Alright, then. I'll enable it when SLES11 branches out. Thanks. -- openSUSE Feature: https://features.opensuse.org/305584

1 0

[openFATE 305317] Default to hidden bootloader menu
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Stanislav Visnovsky (visnov) Feature #305317, revision 8 Title: Default to hidden bootloader menu openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Jiri Srain (jsrain) Description: As long as there is no other operating system present (SUSE is the only system), it makes sense to default to hidden bootloader menu (and booting directly). References: http://www.gnu.org/software/grub/manual/grub.html#Hidden-menu-interface https://bugzilla.novell.com/show_bug.cgi?id=425717 Discussion: #1: Stephan Kulow (coolo) (2009-04-16 10:34:48) I like that idea. I guess it's a tiny change for bootloader, but has possibly some docu impact. + #2: Stanislav Visnovsky (visnov) (2009-05-28 16:45:13) + How should it behave with option to keep kernels from updates (libzypp + option)? What about failsafe? -- openSUSE Feature: https://features.opensuse.org/305317

1 0

[openFATE 305313] creating nonexistent directories with Autoyast
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Stanislav Visnovsky (visnov) Feature #305313, revision 10 Title: creating nonexistent directories with Autoyast openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Uwe Gansert (ug) Description: from bug #429491 It should be possible to create directories just like files with its permissions and ownership. Today it is impossible (using just "files") to put for example /root/.ssh/authorized_keys. To anticipate possible comments, the "file_script" is not IMHO the right way to deal with the problem since it is invoked after writing the file to a filesystem. Yet it may be considered a workaround as of today. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-23 14:19:55) up for Engineering's comment. Is workaround adequate ? #2: Milisav Radmanic (radmanic) (2009-04-16 14:06:01) The workaround is effective but technically not adequate. We should support creating directories like we do it for files. The request is off the mailinglist and makes sense. + #3: Stanislav Visnovsky (visnov) (2009-05-28 16:41:02) + Isn't it better to have support for untarring root.tar.gz to the + filesystem like kiwi does? -- openSUSE Feature: https://features.opensuse.org/305313

1 0

[openFATE 306327] Add DB2 Express-C
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Robert Schweikert (rjschwei) Feature #306327, revision 8 Title: Add DB2 Express-C openSUSE-11.2: New Priority Requester: Desirable Requested by: Robert Schweikert (rjschwei) Description: IBM is interested to providing an easy mechanism for users to install DB2 Express C, the free version of DB2. It would be nice if we could add DB2 Express C to the openSUSE non-oss repository. + Relations: Discussion: #3: Glenn Doig (doiggl) (2009-04-24 06:16:56) http://www-01.ibm.com/software/data/db2/express/ http://www-01.ibm.com/software/data/db2/express/download.html #4: Pascal Bleser (pbleser) (2009-05-20 22:00:05) Why not, let's go for it. If IBM wants to see openSUSE as a vehicle to drive the adoption of their products, even if not opensource, and as long as it doesn't affect the license/EULA/redistribution of the distribution itself, I don't see any reason not to support that initiative. IBM can choose to either have it in the non-OSS repository, or host it in a repository of their own, with openSUSE builds. What is involved on our side of things ? + #5: Robert Schweikert (rjschwei) (2009-05-28 09:21:00) + - IBM has a distribution agreement that needs to be signed. + In addition I think when somone installs DB2-Express C from the non-oss + repo we should pop up a box telling them about the agreement if they + intend to distribute DB2 Express with a product. No registration + required for private use. + #6: Robert Schweikert (rjschwei) (2009-05-28 09:22:04) + Added attachment Distribution agreement + (IBM_DB2_and_WAS_CE_Distribution_Form_and_Agreement_4_17_2009.pdf) -- openSUSE Feature: https://features.opensuse.org/306327

1 0

[openFate 305272] Definition in the Yast2 samba server module for "workgroup" host
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305272, revision 1, last change by Title: Definition in the Yast2 samba server module for "workgroup" host openSUSE-11.2: New Priority Requester: Desirable Requested by: Andreas van dem Helge <andrew(a)joako.net> Partner organization: openSUSE.org Description: Add a definition in the samba server module for "workgroup" host. I.E. in a SOHO it isn't always necessary to setup a true "domain" server, however if there were a set of options for things like "LMB" aka "local master browser" and a quick set of clicks to join a "Workgrp" as a client. this tutorial highlights the amount of script editing that could be avoided if the samba server were more "workgroup" friendly http://www.swerdna.net.au/linhowtolanprimer.html#samba (http://www.swerdna.net.au/linhowtolanprimer.html#samba) References: Originally reported as BNC #420766 (https://bugzilla.novell.com/show_bug.cgi?id=420766) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305272

1 3

[openFATE 305403] Bootloader beep configuration
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #305403, revision 10 Title: Bootloader beep configuration openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Desirable Requested by: Jiri Srain (jsrain) Description: Allow to configure whether the acoustic signal should be used for installed bootloader. Acoustic signal is valuable for visually impaired people, while it may be disturbing e.g. in libraries. Discussion: #1: Jiri Srain (jsrain) (2008-11-12 15:58:43) Default can be set depending on whether braille display was found or whether text-to-speech in isolinux was used. #2: Stefan Behlert (sbehlert) (2008-11-12 17:15:07) Is this feature meant as 'allow atuomatic setting of'? The beep is afaik already configurable to be 'off'. If not, this would be a bug. #3: Stefan Seyfried (seife) (2008-11-12 18:09:40) Please reject this feature. This is seriously overengineered. The beep now defaults to off int the installed system. If somebody wants to enable it, he can do so with gfxboot --change-config "boot::beep=1" Marco only needs to document that for his customers and everything is fine. Please, no YaST module for that. #4: Jiri Srain (jsrain) (2008-11-13 09:39:44) (reply to #3) It's not about a new module, just about a check box in the bootloader configuration. -- openSUSE Feature: https://features.opensuse.org/305403

1 0

[openFATE 305443] Support of Bluetooth Mouse and Keyboard on installation
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #305443, revision 7 Title: Support of Bluetooth Mouse and Keyboard on installation - openSUSE-11.2: Evaluation + openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) + reject date: 2009-05-28 15:38:59 + reject reason: Out of resources for 11.2. Priority Requester: Desirable + openSUSE-11.3: New + Priority + Requester: Desirable Requested by: Vladimir Botka (vbotka) Description: On Installation the user should be able to decide to use the bluetooth mouse/keyboard. Maybe just in the case that no other mouse/keyboard is detected. Relations: - Bluetooth mouse not detected (novell/bugzilla/id: 445583) https://bugzilla.novell.com/show_bug.cgi?id=445583 -- openSUSE Feature: https://features.opensuse.org/305443

1 0

[openFATE 305535] Improve samba yast modules
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #305535, revision 11 Title: Improve samba yast modules openSUSE-11.2: Evaluation Priority Requester: Important Requested by: James McDonough (jmcdough) Partner organization: openSUSE.org Description: Improve the design of the yast samba modules. More details to come. References: https://bugzilla.novell.com/show_bug.cgi?id=444603 Business case (Partner benefit): openSUSE.org: Many customers report difficulties with various areas of samba yast administration, both with new features requested and layout of current ones. + Discussion: + #1: Christoph Thiel (cthiel1) (2009-05-28 15:34:16) + James, do you have more details yet? Otherwise, we'll have to reject it + for openSUSE 11.2 right away. -- openSUSE Feature: https://features.opensuse.org/305535

1 0

[openFATE 305546] Support for NTLM authentication (proxy) in YaST and libzypp
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #305546, revision 7 Title: Support for NTLM authentication (proxy) in YaST and libzypp openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Desirable Requested by: Katarina Machalkova (kmachalkova) Partner organization: openSUSE.org Description: YaST and libzypp should work in an environment with proxy server requiring NTLM authentication. The feature consists of two parts: 1) YaST proxy module has to provide UI to let user choose NTLM and write configuration file (/root/.curlrc) accordingly 2) libzypp media backend needs to be adapted to read and understand such configuration( that is, accept also --proxy-ntlm option instead of bare --proxy only) References: https://bugzilla.novell.com/show_bug.cgi?id=440296 https://bugzilla.novell.com/show_bug.cgi?id=412137 Business case (Partner benefit): openSUSE.org: Significant for adoption in mixed datacenters where the proxy infrastruture is on MSFT assets. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-26 20:57:23) Sadly, there is a realistic business case for this in mixed datacenters. Some odd people like to use NTLM proxies, I will never understand why. this will be a headache to do :-/ -- openSUSE Feature: https://features.opensuse.org/305546

1 0

[openFATE 303555] Create a home-user-readable partitioning summary
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #303555, revision 8 Title: Create a home-user-readable partitioning summary openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-08 15:38:07 reject reason: Postponing. More important stuff to do. Priority Requester: Important - openSUSE-11.2: Evaluation + openSUSE-11.2: Duplicate of #305158 Priority Requester: Important Requested by: Jiri Srain (jsrain) Description: The partitoiner installation summary contains all detailed information about the disk changes, however, for home users it is not easily understandable. If we have a workflow prior the partitioning proposal, it will not be that important to contain all detailed information in the proposal. + Relations: + - feature/duplicate: 305158 Discussion: #1: Arvin Schnell (aschnell) (2008-03-28 16:27:43) I don't understand the reasoning: If the user doesn't understand the summary in the installation proposal neither can he understand the proposal in the workflow before. If that is the case we have to change both. #2: Jiri Srain (jsrain) (2008-03-31 13:39:55) (reply to #1) You are right, that with current workflow anything that contains less information is bad. However, for 11.1, we should improve the workflow and afterwards we can also simplify the summary. -- openSUSE Feature: https://features.opensuse.org/303555

1 0