March 2009 - openSUSE Features - openSUSE Mailing Lists

[openFate 305705] Types of installation
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Agustin Chavarria (dj_ubun_1) Feature #305705, revision 1, last change by Title: Types of installation openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Agustin Chavarria (dj_ubun_1) Partner organization: openSUSE.org Description: would be good, that at the time of installation opensuse, ask what you want to install, like a template, without having to go to edit to add software. An example for that will be: Multimedia install Full install server install developer install -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305705

1 12

[openFate 305633] Support installation with encrypted root file system
by fate_noreply＠suse.de 10 Aug '13

10 Aug '13

Feature added by: Andreas Jaeger <aj(a)novell.com> Feature #305633, revision 1, last change by Title: Support installation with encrypted root file system openSUSE-11.2: Unconfirmed Requested by: Stephan Kleine (bitshuffler) Partner organization: openSUSE.org Description: One thing openSUSE is really missing, compared with other popular distributions, is the ability to install into an encrypted root file system so _everything_ is encrypted. While the manual installation / setup like described at http://en.opensuse.org/Encrypted_Root_File_System_with_SUSE_HOWTO works, it is still cumbersome and error-prone to setup - especially on systems with small hard disks like e.g. laptops. IMHO this subject gets more and more important not only for laptops but also for normal workstations with respect to the global decline of privacy protection. Since all the necessary software is in place and Yast already has the option (including the GUI) to encrypt /home this shouldn't be that hard to do and would be a great feature for 11.1 (especially if you keep in mind that this will be the base for the next SLE version and corporations love security functionality provided out of the box as an option). Important points are: 1. it should work with LVMs as well 2. it should be possible to automatically generate a key on startup to encrypt the swap partition (given, this would disable suspend) 3. one should be able to use the same password for several partitions so one has to enter it just one time instead of once for every partition. Related reports: * Bug #397411 - Hibernation won't work with encrypted swap * Bug #399298 - encrypt swap partions by default on every boot using a random key * Bug #166067 - sysinfo:/ does not list encrypted /home partition Relations: - Easy to use Full Disk Encryption (feature/id: 304470) - Support installation with encrypted root file system (novell/bugzilla/id: 415479) https://bugzilla.novell.com/show_bug.cgi?id=415479 Discussion: #1: Arvin Schnell (aschnell) (2008-08-08 11:39:11) Full disk encryption is already under discussion in fate #304470. Sorry, but it's not public. #2: Stephan Kleine (bitshuffler) (2008-12-17 09:49:10) Reopened because the whole installer was rewritten but still no one cared to add this. I'm sorry, but this feature request is about adding root file system encryption to openSUSE. When, or if at all, you add it to SLE, I couldn't care less about it, but I surely don't want to wait till SLE 12 ;) Also I understand that you don't want to track and update 2 different locations but, since that feature is asked for quite often, IMHO there should be a location for openSUSE users to express their need (as in vote) for it and to CC themself to get notified on updates / when it finally is implemented. Making the fate entry public at https://features.opensuse.org/ would be nice to have as well (since it isn't actual rocket science and suse is one of the last distributions to add this feature there shouldn't be a reason to track this behind closed doors) but I can happily live without it as long as you leave this request open so people can vote for it & cc themself. Thanks a lot. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305633

1 53

[openFATE 305874] Enable peer to peer downloading of patches/software
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Johan Kotze (gogga) Feature #305874, revision 1, last change by Title: Enable peer to peer downloading of patches/software Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Johan Kotze (gogga) Description: It would be great if we could somehow include a peer to peer functionality for the download of patches/packages. This would greatly reduce the number of mirrors required and would increase the performance for many users in countries with limited international bandwidt. I was thinking that we host a torrent tracker on opensuse.org and build a torrent client into zypper/libzypp and allow the user to allocate a portion of disk space for downloaded packages. Most modern systems have ample disk space and should be able to spare around 4GB for downloaded packages. This is also in line with the spirit of community where we help each other out. If it works well, it could also be used to distribute patched internally inside an organization when they deploy SLE. -- openSUSE Feature: https://features.opensuse.org/305874

1 6

[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

[openFate 305472] Support transaction triggers for rpms
by fate_noreply＠suse.de 21 Jan '13

21 Jan '13

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305472, revision 1, last change by Title: Support transaction triggers for rpms openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: It's important to be able to run once after all packages have been installed a command (instead of running the command after each of x packages getting installed, which would make the process much slower). That's basically a post-transaction trigger. For background, see https://bugzilla.novell.com/show_bug.cgi?id=365649 and especially comment #14 from Stanislav. (note that this is work that should be done in upstream rpm, not as patches) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305472

1 8

[openFate 305112] Add webcam configuration module for yast
by fate_noreply＠suse.de 19 Oct '12

19 Oct '12

Feature added by: Michael Loeffler <michl(a)novell.com> Feature #305112, revision 1, last change by Title: Add webcam configuration module for yast openSUSE-11.1: New Priority Requester: Desirable Requested by: Michael Loeffler <michl(a)novell.com> Partner organization: openSUSE.org Description: Webcam is configured automatically. But for users having trouble with configuration a webcam configuration module would be useful. See also bug #359729 Business case (Partner benefit): openSUSE.org: Users in trouble with webcam configuration need a webcam configuration possibility in YaST. As the usage of webcams is rising, eg. through instant messanger this feature request adresses more and more users -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305112

1 25

[openFate 305148] Automatic Compiling of Kernel Modules
by fate_noreply＠suse.de 04 Sep '12

04 Sep '12

Feature added by: Andreas Jaeger <aj(a)novell.com> Feature #305148, revision 1, last change by Title: Automatic Compiling of Kernel Modules openSUSE-11.2: New Priority Requester: Important Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: The Standard Linux-Kernel provides a lot of hardware drivers/kernel modules. Nevertheless there are still devices not supported by the kernel. If a user compiles a kernel module by himself, he has to redo this step after each kernel update (if he is aware at all, that this step is needed). My idea was to install kernel-source, kernel-syms, gcc and make with each standard installation and to define a standard directory for the source code of kernel modules, e.g /usr/src/updates. When a Kernel Update is done, the system looks on boot in /usr/src/updates for directories and does there a 'make' and 'make install'. (build a kmp-package ?) If this could become a standard for other distributions (LSB) as well and corresponding init scripts would exist, third party kernel modules could be installed automagically after extracting code to /usr/src/update, so there would be some kind of standard for installing external kernel modules. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305148

1 21

[openFate 305493] Look at plymouth for splash during boot
by fate_noreply＠suse.de 27 Aug '12

27 Aug '12

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305493, revision 1, last change by Title: Look at plymouth for splash during boot openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: I wanted to open a fate feature about this when I first heard of plymouth, but reading http://fedoramagazine.wordpress.com/2008/10/21/interview-fedora-10s-better-… really makes me think we should go this way. Ray's comment starting with "Every flicker and mode change in the boot process takes away from the whole experience." is especially interesting. Is it okay to track the "don't show grub by default" here? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305493

1 94

[openFATE 305881] Add a simple way to access the rpmlint report
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Vincent Untz (vuntz) Feature #305881, revision 1, last change by Title: Add a simple way to access the rpmlint report Buildservice: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: Right now, to see the rpmlint report of a build, you have to get the complete build log, which can be slow (because it's big). Having a faster way to read the rpmlint report could result in some tools to highlight what should be fixed, and therefore in better packages. -- openSUSE Feature: https://features.opensuse.org/305881

1 6

[openFATE 306232] Quality Classification Of Projects
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #306232, revision 1, last change by Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * BROKEN -- project is known to be not working atm. -- openSUSE Feature: https://features.opensuse.org/306232

1 8