July 2011 - openSUSE Features - openSUSE Mailing Lists

[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 311341] Yast Partitioning give SSD best practice option
by fate_noreply＠suse.de 23 Feb '13

23 Feb '13

Feature added by: Hans de Raad (hcderaad) Feature #311341, revision 1 Title: Yast Partitioning give SSD best practice option openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Hans de Raad (hcderaad) Partner organization: openSUSE.org Description: More and more laptops, netbooks, pc's, servers, actually anything with some kind of storage need is equipped with Solid State Disks. Although at first glance they may seem quite similar to harddisks, they really are a completely different species with some very different characteristics. It might be convenient for having an "SSD Best practise enabler" switch when creating partitions on disks in Yast, which would then automatically setup the features (and possibly others) mentioned in the "Why do we want this" part of this feature. Use Case: During installation (or partition editing) when a user configures a partition, the option would be presented to enable SSD Best practises. Business case (Partner benefit): openSUSE.org: Especially in the partitioning stage of the installation process one can make or break the extra performance one might gain from using SSD's. Especially aligning a filesystem to SSD erase block size and enabling TRIM on partitions are really noticeable performance enhancers. Also, when the SSD option is activated, the Swap partition would be suggested to be removed from the partition setup (if one is set). -- openSUSE Feature: https://features.opensuse.org/311341

1 8

[New: openFATE 312406] Support for ISC DHCP client for IPv6
by fate_noreply＠suse.de 18 Feb '13

18 Feb '13

Feature added by: Björn Voigt (bjoernv) Feature #312406, revision 1 Title: Support for ISC DHCP client for IPv6 openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Björn Voigt (bjoernv) Partner organization: openSUSE.org Description: Currently only "dhcp6c" (https://fedorahosted.org/dhcpv6/) can be selected as a DHCPv6 client in /etc/sysconfig/network/dhcp: # Which DHCPv6 client should be used? # Currently only the dhcp6c client is supported. # DHCLIENT6_BIN="" Since this client has been obsoleted by ISC dhcp, the DHCPv6 client of ISC should be used as default and as an alternative. -- openSUSE Feature: https://features.opensuse.org/312406

1 2

[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

[New: openFATE 312048] KDE "System settings" intergration of YaST
by fate_noreply＠suse.de 11 Feb '13

11 Feb '13

Feature added by: Lukas Sommer (sommerluk) Feature #312048, revision 1 Title: KDE "System settings" intergration of YaST openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Lukas Sommer (sommerluk) Partner organization: openSUSE.org Description: Integrate the YaST modules in the KDE "System settings" application. Not only with just 1 item that launched YaST, but with 1 item for each YaST module being directly visible in KDE System settings - in the right group. YaST NTP for example in the "Networking" group, YaST Boot loader in "System" ... -- openSUSE Feature: https://features.opensuse.org/312048

1 3

[New: openFATE 312581] Define destination file name for source service download
by fate_noreply＠suse.de 06 Feb '13

06 Feb '13

Feature added by: Justin Yaple (yaplej) Feature #312581, revision 1 Title: Define destination file name for source service download Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Justin Yaple (yaplej) Partner organization: openSUSE.org Description: To build my package I need to download two files with specific names. Unfortunately svn hosted at sourceforge.net when I download the tar files both have a name of "trunk" this is because of the path used to download them. <services> <service name="download_url"><param name="path">viewvc/opennop/daemon/trunk/?view=tar</param><param name="host">opennop.svn.sourceforge.net</param></service> <service name="download_url"><param name="path">viewvc/opennop/module/trunk/?view=tar</param><param name="host">opennop.svn.sourceforge.net</param></service> </services> To fix this you should add an optional parameter named "destination" or something like that so we can specify the destination filename. Then I can stop manually uploading the tar files after renaming them manually. Thank, -- openSUSE Feature: https://features.opensuse.org/312581

1 1

[New: openFATE 310075] Rss Owl
by fate_noreply＠suse.de 23 Jan '13

23 Jan '13

Feature added by: matthias propst (l1zard) Feature #310075, revision 1 Title: Rss Owl Package Wishlist: Unconfirmed Priority Requester: Neutral Requested by: matthias propst (l1zard) Description: Applications that collect data from RSS-compliant sites are called RSS readers or "aggregators." RSSOwl is such an application. RSSOwl lets you gather, organize, update, and store information from any compliant source in a convenient, easy to use interface, save selected information in various formats for offline viewing and sharing, and much more. It's easy to configure and the best of all: It's platform-independent . http://www.rssowl.org/overview -- openSUSE Feature: https://features.opensuse.org/310075

1 1