October 2010 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307628] give client a way to indicate preferred country for mirror choice
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Duncan Mac-Vicar (dmacvicar) Feature #307628, revision 1 Title: give client a way to indicate preferred country for mirror choice openSUSE-11.3: New Priority Requester: Desirable Requested by: Peter Poeml (poeml) Description: Hi, the mirror selection is based on precise, but relatively narrow network topology knowledge, as well as the "mostly" precise and sometimes lacking GeoIP information. For the cases where the IP cannot resolved, or cannot be resolved correctly, to a country, we can give the client a way to specify the country it is located in, to influence the mirror choice into the right direction. There are several groups of users that are affected by this: * users connected through satellite links can often be resolved only as country=A2, which is not a real country, it only indicates that this is a satellite link. * AOL users outside the US are not resolved (pseudo country A1). * IPs unknown to the GeoIP database, and not in one of the AS's which contain a mirror either * clients connected through a VPN that uses address space that's allocated in another country (e.g. clients in the Netherlands, whose employer is based in the US and runs a VPN that uses IP addresses that geolocate to the US) * Ipv6 clients (no GeoIP for that yet) Thus, it is desirable to give clients a way to indicate their location. CentOS uses something like that to influence or override mirror choice: http://www.centos.org/modules/news/article.php?storyid=118 In 11.2 libzypp, this could be implemented relatively easily (I believe) by adding a configuration directive "download-preferred-country" to /etc/zypp/zypp.conf, taking an ISO3166-1 two-letter code, and adding an HTTP request header (X-Preferred-Country) _if_ something is configured there. On another hand, since we intend to mainly use metalinks in the future, we could just use another aria2c option that makes this configurable: --metalink-location=LOCATION[,...] The location of the preferred server. A comma-delimited list of locations is acceptable, for example, JP,US. On the server side, the latter doesn't require anything to do. The former would be easy to implement. Something similar already exists, through ?country=xy request parameter, so one only needs to pick up the new header, which is a few lines of code. It could be used to deal with libcurl downloads, but in the light of metalink usage we should be able to neglect them. Relations: - give client a way to indicate preferred country for mirror choice (novell/bugzilla/id: 482894) https://bugzilla.novell.com/show_bug.cgi?id=482894 Discussion: #1: Peter Poeml (poeml) (2009-03-06 10:20:33) Duncan, can I assign this to you? I look into the git repository, tried to update but I stupidly failed with a file conflict and resolving it, else I would have given it a go... -- openSUSE Feature: https://features.opensuse.org/307628

1 1

[openFATE 306966] No Shutdown/Suspend During Package Update
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #306966, revision 1 Title: No Shutdown/Suspend During Package Update openSUSE-11.3: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: During a package update, it should not be possible to shutdown or suspend the system. Such requests should be delayed until the package update is finished. You do not want to bring the system in an inconsistent state. I consider this a desktop feature, so if somebody runs halt/shutdown on the console, this might not need to work - but if the GNOME/KDE shutdown/suspend options are used, it should finish the update first. Note: Windows does not allow shutdown during an update. What happened and let me to report this as feature: A user installed a kernel update and thought the update was finished. But only one out of the three kernel packages was updated and therefore after a reboot, the system did not came up completely. Business case (Partner benefit): openSUSE.org: If this feature is not implemented, people can get broken systems - which might result in support calls. -- openSUSE Feature: https://features.opensuse.org/306966

1 17

[openFATE 306767] Yast2 package manager: add more filters
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Vincent Petry (PVince81) Feature #306767, revision 1 Title: Yast2 package manager: add more filters openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Vincent Petry (pvince81) Description: It would be nice to have the following additional filters, maybe in the "view" menu: 1) Only show the packages that have a major version update 2) Same as 1) with minor version 3) Only show packages that appeared since the last refresh (see https://features.opensuse.org/306766) 4) Only show packages which version has changed since the last refresh (see https://features.opensuse.org/306766) 5) Only show installed packages 6) Only show non-installed packages The filters should be toggles/checkboxes, so that it's possible to combine them. Such filters are already available in the smart package manager. -- openSUSE Feature: https://features.opensuse.org/306767

1 7

[openFATE 306520] Redesign "Format and Mount Dialog" in YaST Expert Partitioner
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Arvin Schnell (aschnell) Feature #306520, revision 1 Title: Redesign "Format and Mount Dialog" in YaST Expert Partitioner openSUSE-11.2: New Priority Requester: Important Requested by: Arvin Schnell (aschnell) Description: The "Format and Mount Dialog" in the YaST Expert Partitioner has several technical mistakes and limitations. * The mount-by method is in the fstab options dialog. This is wrong since volumes are also addressed in crypttab when they are not mounted. The same applies to the "Do Not Mount at System Start-up" setting. So these settings cannot be modified for e.g. encrypted volumes that are not mounted. * The filesystem label is in the fstab options. Thus it is not possible to set a filesystem label when not mounting the filesystem. This field should be moved from the mount options to the filesystem options. * Some filesystem options, e.g. "Disable regular checks", cannot be changed without formatting the filesystem although the filesystem tools support this. There should be a differentiation between filesystem options that can only be set during formatting and those that can be changed afterwards. One trouble is that this differentiation depends on the filesystem used. -- openSUSE Feature: https://features.opensuse.org/306520

1 5

[openFATE 306437] yast2 disk: easy way to mount all ntfs partitions rw
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Stefan Behlert (sbehlert) Feature #306437, revision 1, last change by Title: yast2 disk: easy way to mount all ntfs partitions rw openSUSE-11.2: New Priority Requester: Desirable Requested by: Jigish Gohil (cyberorg) Description: Taken from Bugzilla: Please provide a check box that says something like this: "Detect and mount all NTFS partitions Read-Write for all users" I do over 100 installations of openSUSE every month, all on PC that have windows installed, and manually changing it in /etc/fstab is bit tedious. Reproducible: Always Relations: - yast2 disk: easy way to mount all ntfs partitions rw (novell/bugzilla/id: 487126) https://bugzilla.novell.com/show_bug.cgi?id=487126 Discussion: #1: Arvin Schnell (aschnell) (2009-03-23 11:53:17) Stefan, please make a feature request if you want this. -- openSUSE Feature: https://features.opensuse.org/306437

1 13

[openFATE 306383] Browsing available repositories from YaST level
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Piotrek Juzwiak (BenderBendingRodriguez) Feature #306383, revision 1, last change by Title: Browsing available repositories from YaST level openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Piotrek Juzwiak (benderbendingrodriguez) Description: After test driving mandriva i found one idea there really great, you can browse repositories from the tool used for managing software. It would be great to have such thing in openSUSE (the community repositories isn't enough i think). So instead of browsing for repositories from web browser level we could browse it from YaST level (include something like novice and advanced level, the difference would be repositories shown for the end user). -- openSUSE Feature: https://features.opensuse.org/306383

1 8

[openFate 305716] [openSUSE 11.1] Disk partitioning under installation (Disk)
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Matthias Eckermann (mge1512) Feature #305716, revision 1, last change by Title: [openSUSE 11.1] Disk partitioning under installation (Disk) openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Sebastian Furdal (resus) Partner organization: openSUSE.org Description: We all know, that openSUSE as a default wants use on its own entire disk. This is VERRY BAD setting. On this website exist a pool: http://suse.ehelp.pl/modules/xoopspoll/pollresults.php?poll_id=24 POLISH: Czy os11 powinien miec przy instalacji mozliwosc wyboru, na ktorej partycji zainstalować system? ENGLISH: Should os11 installation program have make a choice on what partition install the system? 94% users sad YES (tak) Try my proposal... "See the attachments" Relations: - [openSUSE 11.1] Disk partitioning under installation (Disk) (novell/bugzilla/id: 383886) https://bugzilla.novell.com/show_bug.cgi?id=383886 Discussion: #1: Sebastian Furdal (resus) (2008-04-25 12:36:23) Created an attachment (id=210574) Disk (GIMP) #2: Sebastian Furdal (resus) (2008-04-25 12:37:01) Created an attachment (id=210575) Button "create" #3: Arvin Schnell (aschnell) (2008-04-28 03:44:40) Something for PM to decide. #4: Stephan Kulow (coolo) (2008-04-28 04:10:30) Actually this fits the feedback I got during fosdem - the _HUGE_ majority of (power) users has to change the proposal. But the "Create" and "Edit" buttons are already more prominently as they were in previous releases. This was on the behalf of this feedback. #5: Sebastian Furdal (resus) (2008-04-28 07:47:26) Created an attachment (id=210885) Version 2 #6: Matthias Eckermann (mge1512) (2008-04-29 04:06:15) I do not completly understand the request, I fear:-( Is it (1) about leaving space for windows or other OSes? (2) or about _how_ the Linux partitioning should look like? (3) or about both? I personally have a rather "sophisticated" partitioning (people say: "crazy"), thus I am planning to propose a LVM based partitioning as one(!) option (and default for our Enterprise Server product) with roughly(!) this layout. /dev/sda1 /boot /dev/sda2 /swap /dev/sda3 # system VG / /usr /opt /var /dev/sda4 # data VG /tmp /home /srv This more or less resembles the defaults of Unix/BSD systems. As said: it is the "extended" variant of what I can imagine for systems, where Linux is allowed to control the whole harddisk. For systems with shared windows partitions the layout should be different. And suggestions? Comments? Ideas? Proposals? Thanks in advance - so long - MgE #8: Sebastian Furdal (resus) (2008-05-01 02:19:50) (1)(1)does the idea of „automatic partitioning” is to make monopoly in one OS on one computer? [sarcasm] (2)(2)Yes, its only a proposal, more details I can make in some free time. (3)(3)Yap (4)(4)but openSUSE is mostly installed by less advanced users, who mostly do not know anything about Servers (5)(5)Most people on the world have a Windows and they install GNU/Linux with curiosity, and GNU/Linux should not propose to delete their favorite system and all precious data that where collected for years. This is something that makes openSUSE behind almost all major GNU/Linux distributions. And even I do not use Windows, but GNU/Linux (doesn't matter if its not openSUSE/SUSE) but I want check this distro [...] (6)(6)Propose: 1. After detecting disks and partitions Yast2 should propose mount points for all existed partitions. 2. When it finds completely free partition (doesn't matter with what file system - sometimes users prepare before installation free partition under different OS for a new system) OR/AND unallocated space with more size than installation required it should mark it with a green color – that on this partition/space You can install openSUSE with options /boot, /swap, /, /usr, ... etc. 3. When it doesn't find good partition then it should ask “Create automatic disk partitioning?”. a) YES - Automatically create partition setup for home users (example only with “/” and “/home” and ”/boot” - boot is very important for grub, because for example when a user delete under windows Linux partition grub is still in the MBR but it cant find config files - “OH MY GOD, LOOK LINUX DESTROYED MY SYSTEM – I WILL NEVER USE LINIX AGAIN” and most people do not know anything about windows installation “fixmbr”) - ALL DATA WILL BE LOST [red color] - Automatically create partition setup for server - ALL DATA WILL BE LOST [red color] b) NO - Edit partition setup (all proposed mount points in step 1. should remain even without “/” but whit red warning “To install openSUSE You have to create partition with minimal size $MINIMAL_INSTALLATION_SIZE GB”). #9: Matthias Eckermann (mge1512) (2008-05-06 20:56:51) Hello and thanks for the answers. Please see my comments below.? (In reply to comment #8 from Sebastian Furdal) > > (1) about leaving space for windows or other OSes? > (1)(1)does the idea of „automatic partitioning” is to make monopoly in one > OS on one computer? [sarcasm] I agree: I have at least 3 openSUSE/SLES systems on my systems, and every fresh installation tries to kill my "vg_data". This is just annoying and will be fixed. > > (2) or about _how_ the Linux partitioning should look like? > (2)(2)Yes, its only a proposal, more details I can make in some free time. I also have some ideas there, ... > (4)(4)but openSUSE is mostly installed by less advanced users, > who mostly do not know anything about Servers Well, that does not necessarily be true according to other requests I see:-) But I agree that the "less advanced users" have to be covered in the most save way. > [...] This is something that makes openSUSE behind almost all major > GNU/Linux distributions. [...] Well, you might simply avoid those type of comments, please, as it weakens your very valid points above and below ( because people might become angry ). > (6)(6)Propose: > [...] Instead of your proposal let me post a proposal I wrote roughly 2 years ago here in bugzilla (closed bug); in meta-programming-language (and covering also datacenter use e.g. of SLES product): if( SAN-storage-found ) { expert-partitioning(); } else if( num-of-harddisks > 1 ) { expert-partitioning(); } else if( only-one-windows-partition_on( first_harddisk ) ) { # case 2 below partitioning-with-shrink( first_harddisk ) | expert-partitioning(); } else if( some-partitions-but-free-space_on( first_harddisk ) ){ # case 3 below partitioning-without-shrink-or-delete_on (first_harddisk ) | expert-partitioning(); } else if( some-partitions-but-no-free-space_on( first_harddisk ) ) { expert-partitioning(); } else if( multiple-existing-OSes-found ){ expert-partitioning(); } else { # empty harddisk, case 1 below default-partitioning(); } I would like to see that a little bit less complex, but I hope it could be a good start; I also hope we can agree that there are only three relatively "safe" & easy cases: 1. one empty harddisk 2. one harddisk full with another OS (most probably windows) 3. (at least) one (bigger) empty primary partition on first harddisk Everything else needs "knowledge" by the person in front of the computer, i.e. an "expert partitioner" YaST module to support this person, HTH - MgE #10: Matthias Eckermann (mge1512) (2008-05-26 06:19:13) What do you think? #11: Sebastian Furdal (resus) (2008-07-20 03:40:24) I think advanced partitioning should be rewritten, sometimes it is to complicated ... Your proposal is good but openSUSE should automatically propose simple and automatic solutions ... such as: - propose partitions where oS could be installed - propose automatic mount points - propose some profiles of partitioning etc. What You think? #12: Andreas Jaeger (a_jaeger) (2008-10-24 05:24:05) Information was provided. #13: Matthias Eckermann (mge1512) (2009-01-21 11:57:03) Moved to openFATE from bugzilla. Let's proceed for openSUSE 11.2 based on what we have in openSUSE 11.1. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305716

1 12

[New: openFATE 309445] Make yast proxy work with Microsoft ISA
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: francesco nigro (frappa_nigro) Feature #309445, revision 1 Title: Make yast proxy work with Microsoft ISA openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: francesco nigro (frappa_nigro) Description: The yast proxy module doesn't work with Microsoft ISA proxy, the ntlm authentication is not managed correctly and fails. The only viable solution at the moment (the only one I found at least) is to install cntlm on every machines... -- openSUSE Feature: https://features.opensuse.org/309445

1 3

[New: openFATE 310759] job dispatching based on capabilities
by fate_noreply＠suse.de 26 Feb '13

26 Feb '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #310759, revision 1 Title: job dispatching based on capabilities Buildservice: New Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: We will need to have more detail configuration options during job assignment to build instances based on the capabilities of the build hosts. Possible usecases are: * packager wants to specify the needed amount of hard disc space, memory, kernel version or any other hardware requirement like CPU features. * OBS admin wants to enforce the usage of a build enviroment (like chroot, XEN or KVM) for certain packages or projects. These requirements must stay when doing a branch, link or copy operation to another place. -- openSUSE Feature: https://features.opensuse.org/310759

1 7

[New: openFATE 310070] openSUSE support for ARM
by fate_noreply＠suse.de 17 Feb '13

17 Feb '13

Feature added by: peter czanik (czanik) Feature #310070, revision 1 Title: openSUSE support for ARM openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: peter czanik (czanik) Description: As indicated by this [1] thread, and many earlier, there is demand for openSUSE ARM support. As discussed on the mailing list: - the build infrastructure is already there - there is a number of cheap and easily available existing ARM based devices (EFIKA MX [2], Sheeva Plug [3], Beagle Board [4], etc.) and many more are expected to arrive in the coming months - we need developers This last point is the most important, as creating an ARM port is more than just enabling ARM in the build service. Without enough developers this port can't be started, as there is a lot of work to do: - sometimes it is enough just to fix packaging errors (where only x86 is considered in the spec file) - often compiling on ARM needs some patching (either to find existing patches from other distributions or develop new ones) - the openSUSE (YaST, etc.) tools need to be made aware of ARM - testing on different target machines Please add your comment, if you are interested in the ARM port and also that how you could help this initiative! 1. http://lists.opensuse.org/opensuse-buildservice/2010-06/msg00293.html 2. http://www.genesi-usa.com/products/efika 3. http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit-us.aspx 4. http://beagleboard.org/ -- openSUSE Feature: https://features.opensuse.org/310070

1 26