July 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306194] openFATE Client
by fate_noreply＠suse.de 27 Oct '10

27 Oct '10

Feature added by: Raúl García (bgta) Feature #306194, revision 1, last change by Title: openFATE Client openFATE: Unconfirmed Priority Requester: Desirable Requested by: Raúl García (bgta) Description: It would be interesting to create a client like Bug Buddy to openFATE. With a desktop shortcut, the users can suggest new requirements for future developments. -- openSUSE Feature: https://features.opensuse.org/306194

1 6

[openFate 305690] Replace System-V init with upstart init
by fate_noreply＠suse.de 27 Oct '10

27 Oct '10

Feature added by: Vitaliy Tomin (HighwayStar) Feature #305690, revision 1, last change by Title: Replace System-V init with upstart init openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Vitaliy Tomin (highwaystar) Partner organization: openSUSE.org Description: Upstart - an event-based init daemon. It can provide more flexible init system for more faster and effective boot and communication with the init daemon over D-Bus. upstart home page http://upstart.ubuntu.com/ -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305690

1 56

[openFATE 306341] Show developer assigned information
by fate_noreply＠suse.de 26 Oct '10

26 Oct '10

Feature added by: Michael Löffler (michl19) Feature #306341, revision 1, last change by Title: Show developer assigned information openFATE: Unconfirmed Priority Requester: Important Requested by: Michael Löffler (michl19) Description: Currently its not visible for community outside Novell if a developer is set or not. To ease community conribution this information needs to be visible outside the company as well. People then can find features where help is needed much easier and/or a call for contribution can be made. -- openSUSE Feature: https://features.opensuse.org/306341

1 8

[openFate 305312] OpenSUSE <= 11.1 Alpha 2 don't install on SD card
by fate_noreply＠suse.de 06 Oct '10

06 Oct '10

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305312, revision 1, last change by Title: OpenSUSE <= 11.1 Alpha 2 don't install on SD card openSUSE-11.2: New Priority Requester: Important Requested by: Harald Welte <haraldwelte(a)viatech.com> Partner organization: openSUSE.org Description: [Please note that I'm working for the CPU+Chipset maker VIA and this is an actually important feature for the 'netbook' class of devices in the coming months] Recently, BIOS vendors have been starting to implement a 'boot from SD card' feature, much like they have added 'boot from USB memory stick' some years ago. The only SD-card host controller that I've seen this implemented for is SDHCI compliant host controllers. While this is a nice feature to support, for most systems it is just a gimmick and not something neccessarry. However, there are hand-held devices such as netbooks in the pipeline which do not have any other mass storage device. No hard disk and no IDE-attached flash disk or the like. They just have one (more likely two or more) SD card slots and you install and store not only your data but the entire operating system on that SD card. Furthermore, there are products like Samsung moviNAND which are basically a SDcard in a BGA package that can be soldered onto a PCB. So from a protocol and software point of view it is a SD card, but it is mechanically soldered onto the board. Such device have gained some popularity in ARM-based designs, but we'll likely see them in the x86 world, too. To make this happen, The distribution installation initrd needs to 1. include and auto-load the sdhc.ko and sdhci_pci.ko kernel modules 2. create the /dev/mmcblk* device nodes as per udev/hotplug events The actual distribution installation program needs to 1. recognize /dev/mmcblk* as block devices that can be used as target device 2. use a grub-install or similar program that can discover the bios drive number to /dev/mmcblk* device name mapping I have outlined the full details at http://wiki.gpl-devices.org/wiki/Installing_Linux_on_booting_SD_card -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305312

1 18

[openFATE 306591] entropy daemons in 11.2
by fate_noreply＠suse.de 06 Oct '10

06 Oct '10

Feature added by: Brandon Philips (philipsb) Feature #306591, revision 1 Title: entropy daemons in 11.2 openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Brandon Philips (philipsb) Description: Headless and diskless servers with limited input have relied on entropy added by interrupts flagged with IRQF_SAMPLE_RANDOM. However, this feature will be disappearing from the Kernel soon. One solution is to run a daemon to add entropy from userspace to the pool. Example daemons can be found here: * http://www.vanheusden.com/aed/ * http://www.vanheusden.com/ved/ * http://egd.sourceforge.net/ 11.2 should provide these or similar daemons as options for users who require additional entropy sources to keep /dev/random from blocking on read. The Kernel thread discussing this thread can be found here: http://lkml.org/lkml/2009/4/6/283 commit 9d9b8fb0e5ebf4b0398e579f6061d4451fea3242 What: IRQF_SAMPLE_RANDOM Check: IRQF_SAMPLE_RANDOM When: July 2009 Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy sources in the kernel's current entropy model. To resolve this, every input point to the kernel's entropy pool needs to better document the type of entropy source it actually is. This will be replaced with additional add_*_randomness functions in drivers/char/random.c Who: Robin Getz & Matt Mackall -- openSUSE Feature: https://features.opensuse.org/306591

1 13

[openFATE 306616] test feature
by fate_noreply＠suse.de 02 Oct '10

02 Oct '10

Feature added by: Michael Löffler (michl_test) Feature #306616, revision 1 Title: test feature openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Michael Löffler (michl_test) Description: test feature -- openSUSE Feature: https://features.opensuse.org/306616

1 2

[openFate 305706] Facebook chat/Pidgin Integration
by fate_noreply＠suse.de 07 Sep '10

07 Sep '10

Feature added by: Kevin Dupuy (kdupuy9) Feature #305706, revision 1, last change by Title: Facebook chat/Pidgin Integration openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Kevin Dupuy (kdupuy9) Partner organization: openSUSE.org Description: Facebook is currently the most popular social networking site, and it's chat functionality is being used as an IM client for many people. With pidgin-facebookchat (http://code.google.com/p/pidgin-facebookchat/) , Pidgin seamlessly integrates Facebook friends and chats as it would any other IM service. The plugin is already there, and licensed under the GPLv3 (see website above). -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305706

1 7

[openFATE 306571] Make project and package maintainers easily accessible
by fate_noreply＠suse.de 12 Aug '10

12 Aug '10

Feature added by: Susanne Oberhauser (froh) Feature #306571, revision 1 Title: Make project and package maintainers easily accessible Buildservice: New Priority Requester: Important Requested by: Susanne Oberhauser (froh) Partner organization: openSUSE.org Description: obs automatically creates aliases package-$package@... , project-$project@... , maybe @hermes.opensuse.org . The mail should get a additional subject tag [pkg:$package] ... or [prj:$project] ... , and is Cc: ed to o-factory(a)o.o with this tag. Business case (Partner benefit): openSUSE.org: Currently it's a pita to reach package maintainers, either for the whole developer community on factory (because the mails are private and not archived) or for the maintainers (as they drown in the signal / noise ration on factory. Discussion: #1: Susanne Oberhauser (froh) (2009-06-25 14:46:16) Caution is needed to avoid spam What strategies do we have for this? can we benefit from the spam filtering that's done for o-factory@... ? #2: Susanne Oberhauser (froh) (2009-06-25 14:52:39) How do we deal with non o-factory@... subscribers? I see two alternatives: Block them from using the aliases (with a corresponding automatic reply). Or allow the posts, as they come from hermes.o.o --- and make hermes deal smartly with replies, e.g. by appropriately adding the original autor of the message to the bounced message. -- openSUSE Feature: https://features.opensuse.org/306571

1 10

[openFate 305267] Installation using Orca (screen reader) to Improve Accessibility
by fate_noreply＠suse.de 10 Aug '10

10 Aug '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305267, revision 1, last change by Title: Installation using Orca (screen reader) to Improve Accessibility openSUSE-11.2: New Priority Requester: Desirable Requested by: Darragh Ó Héiligh <d(a)digitaldarragh.com> Partner organization: openSUSE.org Description: Original title: Accessibility for installation could be automated with better results. Users can currently press F9 at the boot screen to hear the boot options spoken. THis is a fantastic new feature and is one that OpenSuSE is the first to add. For this you should be very proud. However, I would ask that you further build upon this success by recognising that accessibility at the boot menu has been enabled and automatically start the Orca screen reader with also setting gnome accessibility to enabled. One further consideration should be taken into account. To enable Orca to access the installation screen, Orca must be run as root. However, if Orca is run as root, the rest of the desktop is not accessible due to permissioning issues. Therefore, the installation should be run automatically if the f9 key si pressed. Note, a similar feature excluding the accessible boot menu has also been added to Ubuntu 8.04. Note that they also have a key press (F5) to automatically enable assistive technologies for installation on their live CD. References: See bnc #417874 (https://bugzilla.novell.com/show_bug.cgi?id=417874) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305267

1 5

[openFate 305589] Checkbox "include user home projects in search"
by fate_noreply＠suse.de 30 Jul '10

30 Jul '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305589, revision 1, last change by Title: Checkbox "include user home projects in search" Buildservice: New Priority Requester: Desirable Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: Here's one idea to start with: on the search page, have a checkbox labeled "Include user home projects in search" which defaults to OFF. Then at least you have one level of separation (between "official" and home projects) that is clear to both developers and users. And developers will be motivated to move their generally useful packages into an "official" project by the fact that the default checkbox is OFF. http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00088.html -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305589

1 4

[openFATE 306968] rewrite yast in C#
by fate_noreply＠suse.de 29 Jul '10

29 Jul '10

Feature added by: Sharque uddin Ahmed Farooqui (safknw) Feature #306968, revision 1 Title: rewrite yast in C# openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Sharque uddin Ahmed Farooqui (safknw) Description: Yast is the best control panel for any ditro. It has become quite big and it has alot of modules and many more to come Since yast is wrriten in its own language ( http://en.opensuse.org/YaST/Research/Make_YaST_Independent_of_YCP ) which quite few people know, so it is difficult others to get involved. I think we should start thinking about rewriting yast in a popular and advanced () language like C++, python or C#.... It will make development of yast faster and people find it easy to write modules according thier own requirements. My suggestion is to write it in C#. Writting it in such an advance can make app arch much simpler and also make it easy to maintain. My target relase is 12.0, sisnce it is not in option so I'm selecting 11.3 -- Sharique -- openSUSE Feature: https://features.opensuse.org/306968

1 11

[openFATE 306646] add option to yast to disable tcp window scaling
by fate_noreply＠suse.de 13 Jul '10

13 Jul '10

Feature added by: Jose Ricardo De Leon Solis (derhundchen) Feature #306646, revision 1 Title: add option to yast to disable tcp window scaling openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Jose Ricardo De Leon Solis (derhundchen) Description: I live in Guatemala and like most people in countries like mine I don't have a broadband connection, so everytime I install openSUSE I see myself opening a terminal to disable tcp window scaling and opening kate with root permisions to edit /etc/sysctl.conf to make the change permanent. Though is not complicated to do, it has become an expensive operation to perform. So it would be nice for me and for those of us who need to disable this feature to have an option to disable it in yast. It would be nice to see it in the same tab in which one can disable ipv6. -- openSUSE Feature: https://features.opensuse.org/306646

1 11

[openFATE 306766] Show new and updated package versions in zypper/yast
by fate_noreply＠suse.de 13 Jul '10

13 Jul '10

Feature added by: Vincent Petry (PVince81) Feature #306766, revision 1 Title: Show new and updated package versions in zypper/yast openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Vincent Petry (pvince81) Description: After refreshing a repository, it would be nice to have a feature that allows to see which new packages have appeared and which package version has changed since the last refresh, like smart does. This could be done by adding an extra information in the package list row, either as icon or color, or field. -- openSUSE Feature: https://features.opensuse.org/306766

1 4

[openFATE 306903] Ship Xorg 7.5 / x-server 1.7
by fate_noreply＠suse.de 23 Jun '10

23 Jun '10

Feature added by: Michael Löffler (michl19) Feature #306903, revision 1 Title: Ship Xorg 7.5 / x-server 1.7 openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Michael Löffler (michl19) Partner organization: openSUSE.org Description: Xorg 7.5 / x-server 1.7 (due: mid august) By the time 11.2 arrives in mid november the x-server 1.6 will already be over six months old, and X.org 7.4 itself will be over a year old. The inclusion of X.org 7.5 and kernel 2.6.31 will keep 11.2 fresh and relevant throughout its nine month life, and prevent the perception of staleness among suse enthusiasts in 2010. Business case (Partner benefit): openSUSE.org: The inclusion for X.org 7.5 will keep 11.2 fresh and relevant throughout its life time and prevent the perception of staleness among SUSE enthusiasts in 2010. -- openSUSE Feature: https://features.opensuse.org/306903

1 20

[openFATE 306635] Gnome main menu should have openSUSE logo, not generic computer
by fate_noreply＠suse.de 07 Jun '10

07 Jun '10

Feature added by: Drew Kwashnak (dragonbite) Feature #306635, revision 1 Title: Gnome main menu should have openSUSE logo, not generic computer openSUSE-11.2: Unconfirmed Priority Requester: Neutral openSUSE-11.3: Unconfirmed Priority Requester: Neutral Requested by: Drew Kwashnak (dragonbite) Description: The Gnome version of openSUSE should have the openSUSE logo either squared (like the head used in KDE) or a horizontile button instead of the generic computer icon. As unimportant as it seems, that is a marketing aspect that should not be overlooked. -- openSUSE Feature: https://features.opensuse.org/306635

1 18

[openFATE 305905] Package and Project Marking
by fate_noreply＠suse.de 02 Jun '10

02 Jun '10

Feature added by: Will Stephenson (wstephenson) Feature #305905, revision 1, last change by Title: Package and Project Marking Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Add the ability to have a 'status update' on packages AND projects * * status updates are not package changelogs; logs refer to changes to the contents of the package, status updates relate to ongoing work on the packages * * 1:N relationship, status updates are timestamped. Like facebook or $microblogging service. * show current status on checkout or list * Add a command to read all the status updates on a package. Examples: 1) Jack is updating Commodore:Amiga:Workbench:Factory to 23.2 and disables publish on the whole project before the actual release date with the status message '20090224 - disabled publish pending 23.2 release' 2) Jill is triaging breakages in Commodore:Amiga:Workbench:Factory and marks packages without checking them out before assigning work to team members Denise and Paula, with "osc mark -m 'broken by input.device changes' Commodore:Amiga:Workbench:Factory Preferences" 3) Paula is fixing a breakage in Commodore:Amiga:Workbench:Factory Preferences and locks (see #305899) the package with status update using "osc co -l -m '20090225 - fixing build failure due to input.device changes' Commodore:Amiga:Workbench:Factory Preferences" -- openSUSE Feature: https://features.opensuse.org/305905

1 3

[openFATE 306502] Disable automount
by fate_noreply＠suse.de 14 Apr '10

14 Apr '10

Feature added by: Jakub Rusinek (liviopl) Feature #306502, revision 1 Title: Disable automount openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jakub Rusinek (liviopl) Description: When repartitioning HDD, automount can hurt. The same when installing system. At least for partitioners and installers "lifetime", automount should be disabled. -- openSUSE Feature: https://features.opensuse.org/306502

1 5

[openFATE 306192] Make BuildService accessible for anonymous users
by fate_noreply＠suse.de 22 Mar '10

22 Mar '10

Feature added by: Michal Vyskocil (mvyskocil) Feature #306192, revision 1, last change by Title: Make BuildService accessible for anonymous users Buildservice: Unconfirmed Priority Requester: Important Requested by: Michal Vyskocil (mvyskocil) Description: We hides many useful information about our distribution behind a Novell login, which makes a participation harder. Other distributions are much more opened even for anonymous users, so you can browse source codes, patches, changelogs, build logs, ... even if you are an anonymous users. We should be opened as much as possible if we want to be a community based distribution. Some examples: * Fedora CVS (http://cvs.fedoraproject.org/viewvc//) expose all Fedora packages with full history and for anonymous users * kojibuild info (http://koji.fedoraproject.org/koji/buildinfo?buildID=81815) - you have a full access to building informations from koji system and some of them are not available for OBS users at all. * Debian changelog browsing (http://packages.debian.org/changelogs/pool/main/c/cdbs/cdbs_0.4.52/changelog) Debian offers a changelog browsing (they don't use a centralized VCS) without registration. * lintian reports (http://lintian.debian.org/maintainer/build-common-hackers@lists.alioth.debi…) you can see a lintian issues for every package. * Debian build log (http://buildd.debian.org/pkg.cgi?pkg=libmatthew-java) Debian also offers an access to a build log of package. * Gentoo package information (http://packages.gentoo.org/package/app-office/nostaples?ts=2009-03-11T05:57…) Gentoo offers many information about package Those examples are only for illustrate of other approaches. I don't try to tell we must implement CVS because Fedora has it. And some issues like an alternative of Gentoo package view should be implemented in upcoming Software Portal. We should publish (at least for openSUSE:* projects) sources of packages and a build logs. -- openSUSE Feature: https://features.opensuse.org/306192

1 25

[openFATE 306852] YaST2 screen title needs a machine-name in it
by fate_noreply＠suse.de 15 Mar '10

15 Mar '10

Feature added by: Greg Riedesel (Gracal) Feature #306852, revision 1 Title: YaST2 screen title needs a machine-name in it openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Greg Riedesel (gracal) Description: The nomenclature, "[YaST control panel] @ [machine name]' is very useful for figuring out which window belongs to which server. Especially if the managing workstation is also openSUSE. Formerly Bug 385625 Use Case: When managing openSUSE servers over X-forwarding via SSH, it is possible to have multiple YaST screens up at the same time, each belonging to a different remote server. Having a way to differentiate between YaST instances in the title-bar will reduce confusion, and help avoid config mistakes. -- openSUSE Feature: https://features.opensuse.org/306852

1 5

[openFate 305104] Provide possibility to configure WEP/WPA/WPA2/... at installation
by fate_noreply＠suse.de 09 Mar '10

09 Mar '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305104, revision 1, last change by Title: Provide possibility to configure WEP/WPA/WPA2/... at installation openSUSE-11.1: New Priority Requester: Desirable Requested by: Jim Creech <jacreech(a)suddenlink.net> Partner organization: openSUSE.org Description: It is possible to configure a network in the first stage installation but it is only possible to select DHCP or Static + configure proxy. It is impossible to configure a secure wireless connection. See also: Bug 293609 (https://bugzilla.novell.com/show_bug.cgi?id=293609) - No provision for entering WEP at installation -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305104

1 9

[openFATE 306379] Use rsync when refreshing repositories
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Piotrek Juzwiak (BenderBendingRodriguez) Feature #306379, revision 1, last change by Title: Use rsync when refreshing repositories openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Piotrek Juzwiak (benderbendingrodriguez) Description: It would be a great idea to use rsync when refreshing repositories, one of the bad things is the refresh speed. It gets worse when people have many repositories. I'm not sure but it already compares if something has changed in the repo but to speed things up it would be great to use rsync. -- openSUSE Feature: https://features.opensuse.org/306379

1 14

[openFATE 306921] s390(x) dump analysis on x86/x86_64 using crosscrash
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Petr Tesařík (ptesarik) Feature #306921, revision 1 Title: s390(x) dump analysis on x86/x86_64 using crosscrash Hackweek IV: Unconfirmed Priority Requester: Important openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Petr Tesařík (ptesarik) Description: crosscrash is an unfinished tool, though interesting. One of the major drawbacks is its inability to open dumps from big-endian architectures on little-endian hosts, most importantly s390x dumps on x86_64. -- openSUSE Feature: https://features.opensuse.org/306921

1 5

[openFATE 306760] upgrade dmraid to RC16
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Marcin Labun (mlabun) Feature #306760, revision 1 Title: upgrade dmraid to RC16 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Marcin Labun (mlabun) Description: RC16 version of dmraid (not yet published) will include following features/bug fixes (full description of bugs can be RH BZ): 479419 [SEC] OROM/DMRAID metadata inconsistency 479425 Incorrect status displayed when disk is missing [status] 483282 dmraid -r will falsely toggle the OROM back to 'normal' status after a failed rebuild 481735 [SEC] dmraid does not allow to activate RAID arrays in degraded state 481749 [SEC] DMRAID does not receive and process kernel events for active devices 505005 dmraid always creates error mapping for the last device in an isw RAID5 set 505007 dmraid regression on raid45 target kernel status interface 506893 Segmentation fault for RAID5 when starting manual rebuild 473282 [SEC] Include support for compatibility with IMSM 9.0 metadata in dmraid 505011 dmraid doesn't update isw metadata to OK during rebuild -- openSUSE Feature: https://features.opensuse.org/306760

1 1

[openFATE 306600] A small change that would make openSUSE a bit easier to use
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Glöm Det (Searching_for_Answers) Feature #306600, revision 1 Title: A small change that would make openSUSE a bit easier to use openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Glöm Det (searching_for_answers) Description: I'm not the most exprienced Unix/Linux user and as a nuub I see how you could make it easier for other nuubs coming from Windows. When I look at the openSUSE directory(is it shared with Linux and Unix?) I see alot complicated abbriviations like sbin, var, opt, mnt, proc and stuff. Now I could google what they stand for and what types of files are in there but it would be easier if I didn't have too. There for I suggest that you rename... DON'T GIVE UP... those files to their full extension names. I know this wouldn't work out well since it might be important for developers and the speed of terminal writing that the remain as they are. Instead here is my solution. Keep the directory as it is but add this feature too openSUSE. When you hold/right click your mouse over the folder the full name appears. If you for exampel hold it over the lib folder the full name of library appears and a short description telling what kinds of files that are stored here. When you comes to making your own folders you are are able too write description and the full name if you want. That can't be too complicated to make right. It is a small change that will make it alot better. But maybe I'm not asking the right persons here. Maybe Dolphin the file manager's crew is the one to tell about this suggestions. In that case or if you have any questions. Send a private message to Searching_for_answers . P.S. I discoverd this Use and Test cases now. I don't know what they're for so I leave them blank -- openSUSE Feature: https://features.opensuse.org/306600

1 7

[openFate 305724] Allow to take over old users by home directory
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Jiří Suchomel (jsuchome) Feature #305724, revision 1, last change by Title: Allow to take over old users by home directory openSUSE-11.2: New Priority Requester: Neutral Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: (from bug reporter:) I have a seperate /home partition and whenever I reinstall/upgrade I just set up the same user as before and he gets assigned the same uid (1000) so nothing gets broken. But I guess with more users and corresponding home directories this aproach begs for wrong permissions, so I suggest the following: In case /home isn't empty it could take all directories available and list them as users to specify their data (Name, login, passwort etc as usual) and then assign corresponding uid. References: https://bugzilla.novell.com/show_bug.cgi?id=464238 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305724

1 7