openSUSE Factory February 2007

factory@lists.opensuse.org

76 participants
59 discussions

[opensuse-factory] ifolder server on 10.3

by Ted Bullock

Will the ifolder server be available as a package in the 10.3 release or will it remain as an external package? -Ted Bullock --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 8 months

[opensuse-factory] meeting minutes of last dist meeting

by Andreas Jaeger

Our last meeting was moved by a week and I forgot to inform you. Sorry about that. Here're the minutes, Andreas * libata per default We're going to use libata by default for future products. For 10.3, we will implement the following in YaST to handle disks with more than 15 partitions (libata uses the SCSI stack that only allows 15 partitions): If YaST recognizes that an IDE disk has more than 15 partitions and we use libata on it, YaST will display something like the following message: "openSUSE is switching to the new IDE drivers using the libata modules. These do only support partitions with up to 15 partitions. You have the following options with openSUSE 10.3: - Use the old IDE drivers: Boot again and add 'hwprobe=-modules.pata' as argument to the kernel - Repartition your system so that maximal 15 partitions are used. To repartition, use your existing operating system. In the future only the new libata drivers will be supported, so we advice to repartition. Installation will be aborted now." * Hal vs USB backends for cups. The use cases we like to solve are: * Detecting a printer when plugged into the machine and prompting the user to configure it - or even automatically selecting a driver like OS X and have the printer just work. * Not needing root to configure a printer * Detecting when a printer is connected/disconnected and offering virtual feedback * Ability to remove printers from copy when they are unplugged Basically cups is using its USB backend to detect printers. There is a hal backend we are kind of using for GNOME (Fedora also ships it) that only partially integrates. Since the rest of our hardware detection is running through hal, this seems like a sensible move. The discussion showed that there are many open questions and a smaller group will discuss how to move forward. * Splitting languages out of packages Usecases: * Reduced image size especially of thin clients and Live images * Reduced image size for distributions * Updating of single translation should be easier We do not want to make a $lang sub-package for every package, this way we get far too many. The following ideas exist: * convince upstream, e.g. GNOME, to do this similar to KDE. But this will only solve one part of the problem and not the base system. * Alter autobuild to split out languages itself. * Use the lang support in RPM, ie: rpm -i --define "_install_langs fr:es" <package> This would break delta RPMs. The idea is to add to spec file of packages a new rpm macro so that subpackages are created and then related subpackages are repacked for each language in our build system. This way we would get e.g. basesystem-$lang and gnome-$lang packages and those can then be installed. -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

13 years, 11 months

[opensuse-factory] Printing in openSUSE 10.3

by JP Rosevear

A couple weeks ago at the dist meeting we discussed improving how printers are configured on openSUSE. Specifically we discussed the following use cases as something we would want to achieve for 10.3, and we'd like to open up the discussion on implementation: 1) Detecting a local USB printer when plugged into the machine and prompting the user to configure it or automatically selecting a driver and configuring the printer We have a lot of the detection code, both usb and hal cups backends can detect the usb printer. Hal being a general hardware detection layer actually sends a message when its plugged in and GNOME uses this to pop up a dialog to configure the printer via a hal backend for cups. However the hal backend is not a standard upstream cups backend and its very difficult to convert a cups hal:// uri to a usb:// one - but not entirely impossible, there is some code in /usr/bin/add-unknown-printer (part of the gnome-volume-manager) to do some of this. Yast also does not support the hal backend currently. The usb cups backend is the standard upstream cups backend but it does no polling so we'd need to poll somehow (gnome-volume-manager and kmediamanager are possiblities). For true zero config printer, we'd need to build up a database of printer ids and driver mappings and include that in the distro. We also need to make this configurable so that you have the possibility of not doing zeroconfig printing on servers. 2) Not needing root to configure a printer Couple of thoughts here, for a hal based solution we might be able to leverage PolicyKit and unify our hardware access permissions system with an upstream default. We could also alter resmgr for this or use sudo. We need to make sure this is configurable though, because it needs to be turned off for servres. 3) Detecting when a printer is connected/disconnected and offering visual feedback via a notification area icon, or some other ui feedback An easy thing to do here would be to patch cups to send out dbus signals and both GNOME and KDE could put up tray icons or whatever. HAL could also be used to detect disconnects reconnects 4) Ability to remove printers from cups (even shared printers) when they're unplugged to prevent jobs from accumulating in the queue or being default If we can get to zeroconfig printing we could optionally just remove a printer from cups when its unplugged. A little more unclear how useful it would be. If someone wants to throw up some info as an openSUSE project http://en.opensuse.org/Projects that would be great. I suspect items 1) and 2) are really the keys, if they work then 3) or 4) should be pretty straightforward. -JP -- JP Rosevear <jpr(a)novell.com> Novell, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 11 months

[opensuse-factory] Invisible Network: tree connect failed: NT_STATUS_BAD_NETWORK_NAME

by M9.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The strange thing is, that the networkfolder, i made for easy acces, is accessible, but the printer is not, while it is attached to the PC which can be accessed from the networkfolder... (ty (Default Printer) "Unable to connect to CIFS host, will retry in 60 seconds..." Description: ty Location: Make and Model: Epson Stylus C64 - CUPS+Gutenprint v5.0.0 Simplified Printer State: processing, accepting jobs, published. Device URI: smb://mshome/192.168.1.2/EPSONSty) What can i do to get rid of the tree connect failure? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.2-34-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.2" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF5WvzX5/X5X6LpDgRAig0AJ9w1+rKfmsXfUFuCj/InjLwFA87RgCgu5V7 0/yJBJEyNykwvps6lWoQUXc= =1MdR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 12 months

[opensuse-factory] Network profiles in NetworkManager

by Alberto Passalacqua

An interesting enhancement, which seems to be already present in Fedora, was suggested by a user (psp250) in IRC. NetworkManager at the moment is able to connect to manage only a single static IP, and if static DNS are specified, it's unable to update them when it connects to a dynamic network. The suggestion is to: * Make NM able to manage more configurations for the same network card (for example, if the wireless card is used to connect to different AP's, some with fixed configurations, some with dynamic ones). * Make NM able to manage static and dynamic DNS without having to change the settings in Yast. Regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 12 months

[opensuse-factory] feature adds to Yast

by Donn Washburn

Hey Group; Running SuSE 10.3 upgraded. A feature that I would like to again see in Yast during the installation 1. A select everything button for those that would like to load everything. 2. A way to save a copy of the files configured to a floppy or HD 3. maybe selection for End User KDE or Gnome developer with or without graphic All servers Anyway this is just a selection idea. There is likely a better way. -- 73 de Donn Washburn 307 Savoy Street Email: " n5xwb(a)hal-pc.org " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 Did you know? The transistor was invented by three white men. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 12 months

[opensuse-factory] How to enable swat in SuSE10.2?

by M9.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As a result of not being able to control the shares, (invisible network), i wanted to enable swat, but the files are not were they supposed to be.... Can anyone help me for x86_64 ? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.2-34-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.2" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF5FoAX5/X5X6LpDgRAgQ1AKDg52LtNRsafeuc1Hs9SL1w2OvBXQCeOE7b OVelzYzZHw4FoF79WvXvBLA= =oOYD -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 12 months

[opensuse-factory] yast2-packager-2.15.16-2 problem

by Sid Boyce

# yast2 inst_source No such client module inst_source Run 'yast2 -h' for help on usage # l /usr/share/YaST2/clients/inst_source.ycp -rw-r--r-- 1 root root 22898 2007-02-21 17:02 /usr/share/YaST2/clients/inst_source.ycp I shall check bugs. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 12 months

[opensuse-factory] fglrx compilation

by Fred Blaise

Hi all I am running 10.2, but with factory kernel (2.6.20-5-default) and gcc 4.1.3 (this allows my laptop to go to s2d with no problem). I am trying to compile the latest fglrx (8.34.8-1) driver against it, but I get some 800 lines of errors... rpm builds fine, but installing the rpm fails horribly when compiling the kernel module. Is the driver simply not meant to work with this kernel yet? Attached a trace of the error. Thanks. Best, fred -- http://theopenstandard.com/blogs/chapeaurouge [GPG info] Key fingerprint = 8928 BAE9 1BEF 6757 E286 85A5 4E2E 2B4D 9E30 C537 gpg --keyserver pgp.mit.edu --recv-key 9E30C537

13 years, 12 months

[opensuse-factory] Apt update - opinions needed

by Philipp Thomas

Hi folks, I've been asked by Richard Bos if I could update apt in factory to the version he has in the BS. This is based on a beta version of apt and offers repomd support but does *not* work with synaptic. So If I'd update apt, I'd drop synaptic. As I use neither of them, I need your input to decide whether to update or not. The choices are: [ ] Stay with stable apt and synaptic [ ] Update to beta apt with repomd support and forgo synaptic Philipp -- Anything whose specification is too complicated to explain easily probably needs to be redesigned. David Abrahams on boost --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years, 12 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory February 2007