October 2008 - openSUSE Features - openSUSE Mailing Lists

[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 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 305343] Partitioner: Support RAID10
by fate_noreply＠suse.de 25 Sep '09

25 Sep '09

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305343, revision 1, last change by Title: Partitioner: Support RAID10 openSUSE-11.2: New Priority Requester: Important SLES-12: New Priority Requester: Important Requested by: V K <truckk(a)inbox.lv> Partner organization: openSUSE.org Description: There is interesting raid-10 config on 2 disks witch can be created like that: mdadm --create /dev/md1 --bitmap=internal --metadata=1.0 --level=raid10 --raid-devices=2 --layout=f2 /dev/sda2 /dev/sdb2 such configuration gives about 2x sequential read performance in comparison with plain raid-1 partitioner shows only RAID Type: RAID_UNKNOWN. Discussion: #1: Arvin Schnell <aschnell(a)novell.com> (2008-10-17 04:05:48) I know, same is true for RAID6. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305343

1 8

[openFate 305345] Replace cups-autoconfig with hal-cups-utils
by fate_noreply＠suse.de 07 Sep '09

07 Sep '09

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305345, revision 1, last change by Title: Replace cups-autoconfig with hal-cups-utils openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal-cups-utils seems to be the long-term solution. Switching to hal-cups-utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups-backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig.conf. We might want to keep the configuration option of /etc/cups-autoconfig.conf in hal-cups-utils. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305345

1 9

[openFate 305308] Installation into Windows Partition (Wubi-like)
by fate_noreply＠suse.de 27 Aug '09

27 Aug '09

Feature added by: Stephan Binner <stbinner(a)novell.com> Feature #305308, revision 1, last change by Title: Installation into Windows Partition (Wubi-like) openSUSE-11.2: New Priority Requester: Desirable Requested by: Stephan Binner <stbinner(a)novell.com> Partner organization: openSUSE.org Description: Wubi allows the installation of Ubuntu on a MS Windows System without changing the partition setup. Users can test-drive a Linux system without major performance loss like when using a Live-CD, have data persistence beyond reboot and an easy way to deinstall like any other application after trial. References: http://wubi-installer.org , https://wiki.ubuntu.com/WubiGuide , http://en.wikipedia.org/wiki/Wubi_(Ubuntu) Business case (Partner benefit): openSUSE.org: Having a Wubi-alike installer for openSUSE would be a great way to promote openSUSE to Windows users. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305308

1 14

[openFate 305320] Show accessed mirror(s)
by fate_noreply＠suse.de 18 Aug '09

18 Aug '09

Feature added by: Peter Poeml <poeml(a)novell.com> Feature #305320, revision 1, last change by Title: Show accessed mirror(s) openSUSE-11.1: New Priority Requester: Mandatory Requested by: Peter Poeml <poeml(a)novell.com> Partner organization: openSUSE.org Description: This concerns both YaST and zypper. It would help a lot if they would show the mirror which is accessed when downloading a package. (Technically, the download client is following redirects and the actually URL needs to be shown, not just the first URL that was contacted but that redirected to another URL) It is a long-standing problem that this information is lacking and it makes debugging and optimizing much harder than necessary, because this information is only available deeply buried in some logfile. We need this information for two reasons: 1) Debugging - to see which URL was accessed when something goes wrong, like a mirror timing out. For example, Whenever a mirror returns garbage, it takes a lot of additional time to find out which one, because all reports are lacking the critical detail, and it is usually hard to find it out later. 2) Optimizing the load sharing between different mirrors - to distinguish slow mirrors from fast ones. For example, I am very much in need of information about the situation in the US, but even though people in the US run installations for me and are willing to send me logs, I can't get this information. In reply to a question from Stano: > Do you want the information in the log or to be shown in e.g. zypper -vvv ? Shown, in normal output. It is already in some log I believe, I don't know which one exactly anymore though. Thing is, users won't be able to tell us anything useful if they weren't shown the information. And later it is not reproducible. At least in a failure situation the URLs must be shown. That alone wouldn't give us the chance to find out about slow mirrors, but at least it would allow to debug problems. Real life example #1: If a mirror is behind a firewall that lets every 10th connection stall (so the transfer hangs or the connection is reset), it usually takes weeks (!) to find out about it. But it hits virtually every user from mirrors country during the time. We have had this 4 times during the last 18 months. Real life example #2: I got feedback from someone who did a network install of openSUSE 11.0 from download.opensuse.org, located in the US. He had to let it running overnight because it took a long time. Next morning, the install hadn't even completed. YaST was hanging and waiting for somebody to hit retry. Problem is, it took us a lot of work to find out which mirror was at fault. We actually had to repeat the install, I had to follow the log and live watching his machine accessing download.opensuse.org, to see where it was redirected, and where it spent most time (while downloading some package). We found a mirror which was really slow, and I could disable it. I have a suspicion though, that we have more such mirrors, because I have got some similar reports from recently. But how to find out? People only complain about slowness, without the ability to give any useful detail. See http://news.opensuse.org/2008/09/23/upcoming-factory-changes/#comments (http://news.opensuse.org/2008/09/23/upcoming-factory-changes/#comments) for examples of this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305320

1 18

[openFate 305318] Move gconf schemas to /usr
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305318, revision 1, last change by Title: Move gconf schemas to /usr openSUSE-11.2: New Priority Requester: Desirable Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: We store gconf schemas in /etc/gconf. However, the schemas are not configuration files, but simply data. Therefore, we should move the schemas to /usr. Simply changing a line in /etc/gconf/2/path should make gconf work with the new location. Note that Debian already implements this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305318

1 7

[openFate 305149] [Feature-request] Yast Expert Partitioner: should not require mounting "/" root partition
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305149, revision 1, last change by Title: [Feature-request] Yast Expert Partitioner: should not require mounting "/" root partition openSUSE-11.2: New Priority Requester: Desirable Requested by: Alexey Eremenko <al4321(a)gmail.com> Partner organization: openSUSE.org Description: Hi All ! Since openSUSE 11.1 will have brand new expert partitioner, I would like to request the ability to use SUSE's partitioner for partition hard disks for other operating systems. Currently it is not possible, because SUSE requires mounting "/" root partition. In some cases I need to install third-party OSes before I install openSUSE, so I want to use SUSE flexible partitioner to partition and format the hard disk, then install the other OSes and only in the end I want to install openSUSE. -Alexey Discussion: #1: Arvin Schnell <aschnell(a)novell.com> (2008-08-04 08:41:18) So in a nutshell you want to use the partitioner as a separate program (started from the DVD) without the other installation features like package managment. Right? #2: Arvin Schnell <aschnell(a)novell.com> (2008-08-05 12:11:02) Not mounting "/" during installation will certainly lead to a failure so I hesitate to remove the check. But we could add a special mode with disabled checks. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305149

1 9

[openFate 305146] Use old system network configuration when updating instead of demanding a new one
by fate_noreply＠suse.de 24 Jun '09

24 Jun '09

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305146, revision 1, last change by Title: Use old system network configuration when updating instead of demanding a new one openSUSE-11.2: New Priority Requester: Desirable Requested by: Pacho Ramos <pacho(a)condmat1.ciencias.uniovi.es> Partner organization: openSUSE.org Description: Currently, when I try to update from opensuse 10.3 to 11.0 with DVD and I want to add network repositories, I have to configure again my network for opensuse installer even when it is already configured on my opensuse-10.3 I think that would be much better try to use network configuration from old installation and only ask user if a problem occurs Business case (Partner benefit): openSUSE.org: System update from media: Start installation / Update, select network-based repositories to be used, you will be asked to configure the network. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305146

1 5

[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