Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
On Mon, Aug 21, 2006 at 11:11:50AM +0200, Christoph Thiel wrote: Hi there, to proceed with the SuSEconfig clearance initiative, let's take a look at SuSEconfig.gdm and SuSEconfig.wdm. Both of them are used to (re)generate config files, by reading some options from /etc/sysconfig/*. To get rid of those SuSEconfig scripts, their logic needs to be moved to /etc/init.d/xdm, to have it (re)generate the according config files prior to launching gdm or wdm. And probably also /etc/init.d/earlygdm /etc/init.d/earlykdm Since /etc/init.d/xdm is in aaa_base, I agree that changes to this file could be done by KDE/Gnome maintainers. Best regards, Stefan Public Key available -- Stefan Dirsch (Res. Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.deGermany -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
On Monday 21 August 2006 12:07, Christian Boltz wrote: Generating config files every time *dm is started is a bad idea IMHO. Reason: It is done _at every boot_ instead of sometimes after installing packages or alike. So you will speedup SuSEconfig, but slow down booting a bit :-( By using a suitable dependency-based system to invoke the file's regeneration (such as GNU make), or trivially by comparing timestamps (easy for simple cases, but make would help for anything non-trivial), it should be possible to render this slowdown almost non-existent, by only regenerating the file when it is necessary to do so (i.e. when the generated config file(s) is/are out-of-date with respect to the /etc/sysconfig parent file(s)). Is there an easy way to make *dm (or the initscript) read the sysconfig file directly (without reducing speed) and then starting X with some parameters instead a config file? This would be the best solution. I may be wrong, but I belive that the _next_ version of Xorg will support this config-file-free parameterised mode of startup. I'm not in favour of any modification to xdm to support reading alternative config file formats, since that adds more of a maintenance headache than it solves. It's important to keep the sysconfig stuff separate from the upstream sources. Propagating sysconfig variables in to the native config file format of the target software as SuSEconfig does allows SuSE's config methodology not to have an impact on the target software, but to be kept separate, which is a good thing. Switching to an on-demand SuSEconfig approach, whereby files are regenerated just-in-time when necessary, would seem to be a positive step. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
On Mon, 21 Aug 2006, Christian Boltz wrote: to proceed with the SuSEconfig clearance initiative, let's take a look at SuSEconfig.gdm and SuSEconfig.wdm. Both of them are used to (re)generate config files, by reading some options from /etc/sysconfig/*. To get rid of those SuSEconfig scripts, their logic needs to be moved to /etc/init.d/xdm, to have it (re)generate the according config files prior to launching gdm or wdm. Comments, criticism, better ideas? Generating config files every time *dm is started is a bad idea IMHO. Reason: It is done _at every boot_ instead of sometimes after installing packages or alike. So you will speedup SuSEconfig, but slow down booting a bit :-( Oh, regenerating those config files unconditional isn't an option, of course! Is there an easy way to make *dm (or the initscript) read the sysconfig file directly (without reducing speed) and then starting X with some parameters instead a config file? This would be the best solution. (If there are only one or two setting left that would require to regenerate config files, you should consider dropping this sysconfig variable.) No, there isn't an easy way, I guess ;) Regards Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
Dominique Leuenberger [EMAIL PROTECTED] writes: What are other Distros doing? Why don't they need anything alike? What is so much more special about the SuSE way that others don't need anything alike? The have similar problems - or force you to run scripts manually AFAIK. Is it just because of a 'lazy' coding stile for YaST? As YaST is reading / modifyng most of these files afaik. So: why not fix these tools? The user changes a file but the change needs to be propagated to others... Fixing tools is one option, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpyMBM4lk0An.pgp Description: PGP signature
[opensuse-factory] Re: SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
Hello, Christian Boltz [EMAIL PROTECTED] [2006-08-21]: Am Montag, 21. August 2006 11:11 schrieb Christoph Thiel: to proceed with the SuSEconfig clearance initiative, let's take a look at SuSEconfig.gdm and SuSEconfig.wdm. Both of them are used to (re)generate config files, by reading some options from /etc/sysconfig/*. To get rid of those SuSEconfig scripts, their logic needs to be moved to /etc/init.d/xdm, to have it (re)generate the according config files prior to launching gdm or wdm. Comments, criticism, better ideas? Generating config files every time *dm is started is a bad idea IMHO. Reason: It is done _at every boot_ instead of sometimes after installing packages or alike. So you will speedup SuSEconfig, but slow down booting a bit :-( Is there an easy way to make *dm (or the initscript) read the sysconfig file directly (without reducing speed) and then starting X with some parameters instead a config file? This would be the best solution. (If there are only one or two setting left that would require to regenerate config files, you should consider dropping this sysconfig variable.) It could be done according to a time stamp, i.e. only if the sysconfig file changed. Checking a timestamp is fast, so I don't think that the slow down of the boot process is noticable by the user. Regards, Bernhard -- Pasteurs Theorie von Bazillen ist lächerliche Fiktion. -- Pierre Pachet, Professor der Physiologie in Toulouse (1872) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Call for discussion: pattern definition language
The current format to define patterns - the .pat file - is rather awkward to use and specific to one type of repository. So I created http://en.opensuse.org/Patterns/Definition_Language to start a discussion on defining a more generic way to describe patterns. Comments welcome ! Klaus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] distmeeting minutes
Here are the minutes from our last meeting, Andreas * PolicyKit/resmgr The upstream Hal authors are preparing to require PolicyKit. PolicyKit is a system daemon, applications ask the daemon about permissions. This is a similar concept as resmgr. The question is how to move forward for our distribution. Will be further discussed next time. * Starting daemons by default A reminder: Daemons will only be started by default from their packages if the dist meeting has approved this. Otherwise the autobuild team is authorized to reject this. PolicyKit is a new daemon, it was approved to be started for now. * Move to GNOME 2.16 Not discussed since nobody involved attended, postponed for next meeting (or discussion via email). * SuSEconfig removal SuSEconfig is currently run after each package installation by YaST and is a huge bottleneck. Some scripts have already been removed and we have to discuss how to move on. The purpose of SuSEconfig was to not run one script several times during package installation but just once at the end. We plan to fix scripts that can be done differently, remove obsolete ones and the autobuild team will not check in new SuSEconfig scripts. A review of scripts showed that some are really obsolete, the first 5 scripts were removed already. We need a superior solution, e.g. some way to do delayed execution. This should also work if just rpm or smart is used. An overview of SuSEconfig is appended below. * update messages general/conditional (e.g. bind) During update of packages they could notify users about changes via email and/or the SuSEplugger (until 10.0, this is not anymore in 10.1). Most of these are outdated and not really usefull anymore and should be removed. The question is how to handle situations like bind where config files get rewritten and the user should be informed if this fails. In general, it is not possible to send emails from rpm install scripts. Most cases could be handled by the release notes but there are cases that cannot and we need a better solution to present this, especially since many people to not read the local emails. * Dropping UP Kernel on i386/x86-64 No objection by the dist meeting. This should be done for Alpha4. * Linker Options and Optimizations LDFLAGS=-Wl,-z relro is now the default and works fine. The hash table optimization will be enabled in binutils and glibc by default as well. ~~ SUSEconfig has around 4 classes of different scripts, the first two are the most common cases: a) /etc/sysconfig has two types of data. * data read by rc-scripts and used directly there * data used by SuSEconfig and spread over /etc/* or /var/* The second type is handled by one class of SuSEconfig scripts, called CLASS-A. Solutions: - extend rc-scripts to do this - extend daemons to read /etc/sysconfig - ... b) directory index caches scripts that keep index files in several directories up to date. The underlying problem is that rpm can not trigger based on directory modification, but that's currently not in sight. In many cases SuSEconfig is just the cheap solution. A related problem is, that if you install 10 packages, you don't want to regenerate these indexes 10 times. Solutions: - call individually in each related package (the install-info way) - error prone - many modifications to many packages (and over again for any change) - extend usage of these index files to update cache themselves - ... This type will be called CLASS-B below. (some of these have also been moved to cron.daily in the past) c) similar to b but generate other filetypes from installed files, usually hacks for special programs CLASS-C d) set a symlink according to installation CLASS-D (probably easiest for a postinstall solution) (modulename) (packagename)(class) SuSEconfig.automake (automake) CLASS-B SuSEconfig.cjk-latex (cjk-latex)CLASS-C SuSEconfig.desktop-file-utils (desktop-file-utils) CLASS-B SuSEconfig.fonts (fonts-config) CLASS-B (mostly) SuSEconfig.gdm (gdm)CLASS-A SuSEconfig.ghostscript-cjk (ghostscript-cjk) CLASS-A? SuSEconfig.gnome-vfs2 (gnome-vfs2) CLASS-B SuSEconfig.groff (groff)CLASS-A SuSEconfig.gtk2 (gtk2) CLASS-B SuSEconfig.guile (guile)CLASS-B SuSEconfig.icu (icu)CLASS-D SuSEconfig.isdn (i4l-base) CLASS-A SuSEconfig.ispell (ispell) CLASS-A/CLASS-D SuSEconfig.kde (kdebase3-NLD,kdebase3-SuSE) CLASS-A SuSEconfig.kdm3 (kdebase3-NLD,kdebase3-SuSE) CLASS-A SuSEconfig.libxml2 (libxml2)CLASS-B SuSEconfig.lyx-cjk (cjk-lyx)CLASS-B SuSEconfig.mailman (mailman)CLASS-A SuSEconfig.news (aaa_base) CLASS-A SuSEconfig.pango (pango)CLASS-B SuSEconfig.pbs (OpenPBS)
Re: [opensuse-factory] Call for discussion: pattern definition language
Am Monday 21 August 2006 14:27 schrieb Klaus Kaempf: The current format to define patterns - the .pat file - is rather awkward to use and specific to one type of repository. So I created http://en.opensuse.org/Patterns/Definition_Language to start a discussion on defining a more generic way to describe patterns. btw, we think about to use the same patterns within the build service to be used within the installers or to create images or complete distributions. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Per Jessen [EMAIL PROTECTED] writes: Andreas Jaeger wrote: I only made a minimal list of patterns - and now want to open a new discussion on what kind of patterns we should have. I can add everything I find usefull - but please tell me what you find usefull ;-) Without having thought a lot about it - the initial selection by patterns/groupings is meant to give the user a system with a set software suitable for the primary purpose(s) of the machine being installed. So what are the typical main roles of an openSUSE system? Desktop | +--- Desktop for/with multimedia +--- Desktop for development +--- Desktop for office/backoffice +--- etcetera I added for now - and did this only for KDE, GNOME will come later - a generic KDE desktop pattern and a few sub patterns: * KDE-BASIS * KDE-Devel * KDE-Edutainment * KDE-Games * KDE-Help * KDE-IMAGE * KDE-Internet * KDE-Multimedia * KDE-Office * KDE-System * KDE-Utilities | Laptop +--- (not sure how to divide this) I don't know either. | Server | +--- Fileserver +--- Internetserver (DNS, web etc.) +--- Database +--- Directory +--- Firewall, network server +--- etcetera I have now: * Directory (LDAP) * Fileserver * Mailserver * LAMP * XEN * Internet Gateway | [other roles?] Development - not sure how to structure this. This is only a proposal - I really just wrote it up in five minutes. Maybe it's entirely in appropriate. Maybe the selection is 1-2-3 step: Primary qualifier, secondary qualifier, plus add-ons (things you might want to do regardless of which type of system): Experienced User, Kernel development, I don't like Experienced user - this should be split into several patterns... Primary and secondary qualifier could fit into one page/window in a tree-style display as the above, and going to the 2nd window for add-ons could be made optional, such that new-bies or non-techies would have a fast-path, whereas techies and/or experienced users would still have the option of a detailed selection etc. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpoRHdaF4J3w.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
* Andreas Jaeger [EMAIL PROTECTED] [Aug 21. 2006 14:48]: I added for now - and did this only for KDE, GNOME will come later - a generic KDE desktop pattern and a few sub patterns: * KDE-BASIS * KDE-Devel * KDE-Edutainment * KDE-Games * KDE-Help * KDE-IMAGE * KDE-Internet * KDE-Multimedia * KDE-Office * KDE-System * KDE-Utilities In order to facilitate discussions about patterns, I used some scripts and graphviz to generate dependency graphs. See http://en.opensuse.org/Patterns/Content#Pattern_Content and ftp://ftp.suse.com/pub/people/kkaempf/graphs/index.html (sync in progress) I don't like Experienced user - this should be split into several patterns... So what is an 'experienced user' and what does he expect from a system ? Klaus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Re: SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
Hello, Christoph Thiel [EMAIL PROTECTED] [2006-08-21]: On Mon, 21 Aug 2006, Andreas Jaeger wrote: What are other Distros doing? Why don't they need anything alike? What is so much more special about the SuSE way that others don't need anything alike? The have similar problems - or force you to run scripts manually AFAIK. ... plus, some of the things that we do with SuSEconfig are really unique. (Just look at the fonts stuff, which is mostly relevant for Asian fonts. SuSEconfig is doing an awesome job there -- but it still can be optimized.) ACK! Fonts are _really_ great in SUSE and it was the main problem I had with Debian on the desktop and one of many reasons why I switched back. Regards, Bernhard -- If you really want pure ASCII, save it as text... or browse it with your favorite browser... -- Alexandre Maret [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] simple packaging
For Requires you usually done have to do anything. Autoreqprov is on by default and that means that RPM compiles the list of Requires from the binarys/scripts. For BuildRequires you have to do exactly what you are doing.. Henne Thank you! It's nice to know that I'm on the right path :) -- Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Am Montag, 21. August 2006 14:48 schrieb Andreas Jaeger: Per Jessen [EMAIL PROTECTED] writes: Andreas Jaeger wrote: [...] I added for now - and did this only for KDE, GNOME will come later - a generic KDE desktop pattern and a few sub patterns: * KDE-BASIS * KDE-Devel * KDE-Edutainment * KDE-Games * KDE-Help * KDE-IMAGE * KDE-Internet * KDE-Multimedia * KDE-Office * KDE-System * KDE-Utilities What about kdesdk (Kbabel,etc)? Will it be part of KDE-Devel? Laptop +--- (not sure how to divide this) I don't know either. I don't think there is need for a special laptop pattern. Powersave stuff should work with any PC. All the rest depends on specific laptops, so it shouldn't be installed on each laptop. E.g if you have an Acer laptop, why would you need sony laptop settings in Kcontrol? Or if you have a Dell, your probably not interested in IBM Thinkpad settings. These moduls are only workarounds for non working hard/software. Of course it would be great, if such packages could be installed automatically for the specific laptop only. Server +--- Fileserver +--- Internetserver (DNS, web etc.) +--- Database +--- Directory +--- Firewall, network server +--- etcetera I have now: * Directory (LDAP) * Fileserver Samba, NFS? * Mailserver * LAMP * XEN * Internet Gateway [other roles?] Database (MySQL, PostgreSQL) Development - not sure how to structure this. This is only a proposal - I really just wrote it up in five minutes. Maybe it's entirely in appropriate. Maybe the selection is 1-2-3 step: Primary qualifier, secondary qualifier, plus add-ons (things you might want to do regardless of which type of system): Experienced User, Kernel development, I don't like Experienced user - this should be split into several patterns... Primary and secondary qualifier could fit into one page/window in a tree-style display as the above, and going to the 2nd window for add-ons could be made optional, such that new-bies or non-techies would have a fast-path, whereas techies and/or experienced users would still have the option of a detailed selection etc. Actually I would recommend to take over the old selections for the new patterns in expert mode. For newbies/non techies we should make new patterns, e.g First choice: [] KDE system [] Gnome system [] System with minimal desktop [] System without graphical desktop [] Expert Second choice (if choosen one of the above): [x] KDE system (base, help included) [] Edutainment [] Games [] Graphics [] Internet-Tools [] Multimedia [] Office [] System Utilities [] Development [] Artwork [] Wallpapers [] Fonts [] Screensavers [] Icons [ ] Gnome system (base, help included) [] Edutainment [] Games [] Graphics [] Internet-Tools [] Multimedia [] Office [] System Utilities [] Development [] Artwork [] System with minimal desktop [] Windowmaker [] Graphics [] Internet-Tools [] Multimedia [] Artwork [] Icewm [] Fvwm2 [] Xfce4 [] File and printserver [] Directory server (LDAP) [] Mailserver [] LAMP [] XEN [] Internet Gateway [] System without graphical desktop [] File and printserver [] Directory server (LDAP) [] Mailserver [] LAMP [] XEN [] Internet Gateway There should always be an Expert button, which gives back the possibility to choose one of the selections we had until 10.1, so old users wont be frustrated. Here there is also place for things like LaTeX. And: please keep the very good patterns for kde-development and gnome-development including almost everything one needs to compile a KDE/GTK app! -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.automake
On Fri, 18 Aug 2006, Robert Schiele wrote: Comments, criticism, better ideas? Not a better idea, just an alternative one: Patch aclocal to read the /usr/share/aclocal/dirlist.d/* files directly. Is that possible? The advantage is that people can still easily add more directories without knowing any details about what %post scripts to use. Maybe such a patch could even be pushed upstream because it really makes sense generally (IMHO). It might make sense -- however, /usr/share/aclocal/dirlist.d/* is a SUSE-only thingy, IIUC. Stock automake only uses /usr/share/aclocal/dirlist, which is a symlink to /etc/aclocal_dirlist on SUSE. Then stock automake should be enhanced here because having such *.d config directories is a _big_ help for packaging. Feel free to forward the following patch upstream and reference to me for further discussions. Do you have a patch to extend automake? ;) That's an easy one: [...] Further comments or suggestions welcome. Thanks for the patch, Robert! I'd really appreciate if you could take the time to push it upstream. As soon as we have the patch in upstream, please file an enhancement request to get it included in our automake package as well. For now we will remove SuSEconfig.automake and add a static /usr/share/aclocale/dirlist -- Stanislav Brabec will take care of this change. Regards Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Symbolic link /media/cdrom
My personal feature request for 10.2 set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. /media/SUSE_LINUX_10.1 is cool, but its hard to work with CDs on command line and writing documentation for Suse is also very hard. So please let's become cd /media/cdrom true for Suse Linux 10.2. Konqueror,etc should/can still show the label of the disk. -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Symbolic link /media/cdrom
Am Montag, 21. August 2006 17:51 schrieb Marcel Hilzinger: My personal feature request for 10.2 set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. So if you have two trays, the last one wins? Hardly a convincing concept. Especially as you can mount and unmount CDs at free will. Greetings, Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Symbolic link /media/cdrom
Am Montag, 21. August 2006 17:56 schrieb Stephan Kulow: Am Montag, 21. August 2006 17:51 schrieb Marcel Hilzinger: My personal feature request for 10.2 set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. So if you have two trays, the last one wins? Hardly a convincing concept. You can also work with /media/cdrom /media/cdrom0 /media/cdrom1 etc for several trays, but the last one wins seems more user friendly for me. Especially as you can mount and unmount CDs at free will. Why should I have to mkdir /media/cdrom mount foo bla manually, if it can be done automatically? -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Symbolic link /media/cdrom
Am Montag, 21. August 2006 18:09 schrieb Marcel Hilzinger: Am Montag, 21. August 2006 17:56 schrieb Stephan Kulow: Am Montag, 21. August 2006 17:51 schrieb Marcel Hilzinger: My personal feature request for 10.2 set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. So if you have two trays, the last one wins? Hardly a convincing concept. You can also work with /media/cdrom /media/cdrom0 /media/cdrom1 etc for several trays, but the last one wins seems more user friendly for me. Well, you can add /media/cdrom to your fstab and then every CD inserted in /dev/hdc will be mounted there - but I'd see it as a regression. Greetings, Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Symbolic link /media/cdrom
Hello, Marcel Hilzinger schrieb: set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. /media/SUSE_LINUX_10.1 is cool, but its hard to work with CDs on command line and writing documentation for Suse is also very hard. So please let's become cd /media/cdrom true for Suse Linux 10.2. Konqueror,etc should/can still show the label of the disk. I always though this was the case since 10.0: It is mounted to /media/device (device could be dvdram, cdrom, cdwriter etc.) and there is a symbolic link from /media/LABEL to /media/device. I cannot check at the moment (no CD around), but I though this was the case. See SUSE Linux 10.0 bugreport: https://bugzilla.novell.com/show_bug.cgi?id=98347 -cut- /From Danny Kukawka 2005-08-28 02:23:46 MST /Changed for beta 4 to this behavior: * if we ge a new volume /device for mount check if the device / volume is already mounted (this was also in the current solution) * if not mounted: ask udevinfo for known symlinks * check if there is a free symlink with a related existing directory in /media -- if there is a existing, not mounted dir in /media: - mount to this mountpoint and add a link with volume label -- if there is a existing, mounted dir in /media: - try to find an other -- if no dir available: - mount to volume label / desired_mount_point from HAL (if the user want a mount to a special device: change udev rule and add the needed directories to /media) -cut- Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Symbolic link /media/cdrom
Am Montag, 21. August 2006 18:27 schrieb Tobias Burnus: Hello, Marcel Hilzinger schrieb: set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. /media/SUSE_LINUX_10.1 is cool, but its hard to work with CDs on command line and writing documentation for Suse is also very hard. So please let's become cd /media/cdrom true for Suse Linux 10.2. Konqueror,etc should/can still show the label of the disk. I always though this was the case since 10.0: It is mounted to /media/device (device could be dvdram, cdrom, cdwriter etc.) and there is a symbolic link from /media/LABEL to /media/device. That's true for 10.0, but not for 10.1. That's why I suggest to always keep the simple /media/cdrom The intermezzo with /media/cdrwriter, /media/dvdram, /media/dvdwriter was not very successful I guess. Coolo: Please ask also the documentation team. It's really hard to write docu for Suse Linux if you cannot tell users, where CDs/DVDs will be mounted! -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Marcel Hilzinger [EMAIL PROTECTED] writes: Am Montag, 21. August 2006 17:11 schrieben Sie: [...] I did not add Artwork, that's in the base for me. Yes, but there are tonns of icon themes, window decos etc. Also the screensaver modules are not mandatory. Some more fonts for a default install would also be nice (see Ubuntu/Mandriva). What about the pictures in /usr/share/wallpapers are they Gnome/KDE only? Perhaps one wallpaper package would be enugh for both desktops. Ok, I'm considering it now ;-). [...] Have a look at factory by the end of the week (or at Alpha4) and then let's refine them together... OK. That's a better way. You're doing the work, we will complain ;-) Mmmh :-(. I'll have to figure something out so that it works the other way round ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpqIxMTSkx3M.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Anders Johansson [EMAIL PROTECTED] writes: Here's an idea that I've been toying with for a long time now: How about a SUSE-CORE that is really CORE? Something that contains only the bare essentials of the system, such as glibc, kernel and a few other things. A really barebones system. We currently have a base pattern that is an extended core. I'm appending the list below and would like you to send me a proposal - either as definition or as list of what you would consider such a CORE. The question is then also what to do with the packages that are currently in the basis but should not be in the new CORE. If people like this, we can use it. I'm open for ideas... On top of this you have add-on products on separate media, such as KDE Desktop, Gnome Desktop, development tools, mail server, gaming system and so on. In each, the relevant configuration utilities, yast modules etc are included, so you only see on your system what you have installed That's more radical then I think - but something to discuss further. This would have two benefits: with a core system that is really core, it would be far easier to maintain separate from everything else. The subsystems could also be developed, tested and maintained separately, so you could have a two year release cycle of core, and a 1 year release cycle of KDE Desktop (for example). You want the kernel to be updated more often than every 2 years... The second benefit would be that it would be much easier for third party companies to create offerings that go in as an add-on on top of SUSE-CORE. Far fewer combinations to test, Moving away from the monolithic distribution is my idea. I think it would improve maintainability a lot Having a defined CORE has its merits, Andreas Required (must have packages): aaa_base aaa_skel acl ash attr audit-libs autoyast2 autoyast2-installation autoyast2-utils bash bzip2 checkmedia coreutils cpio cpp cracklib cups-client cups-libs curl cyrus-sasl cyrus-sasl-saslauthd db db-utils dbus-1 device-mapper diffutils e2fsprogs ed eject ethtool evms file filesystem fillup findutils glibc gnome-icon-theme grep groff gzip hwinfo insserv iproute2 iptables iputils kbd klogd krb5 ksymoops ldapcpplib less libacl libattr libcap libcom_err libgcc libnscd libxcrypt liby2util libzypp limal limal-bootloader limal-perl logrotate lvm2 m4 mailx make mdadm mingetty mkinitrd mkisofs mktemp module-init-tools multipath-tools ncurses net-tools netcfg openssh openssl pam pam-modules parted perl permissions procps psmisc pwdutils reiserfs rpm sed openSUSE-release suse-build-key sysconfig sysfsutils syslog-ng sysvinit tar tcpd util-linux vim w3m wget yast2 yast2-bootloader yast2-core yast2-country yast2-dhcp-server yast2-dns-server yast2-firewall yast2-hardware-detection yast2-installation yast2-instserver yast2-ldap yast2-ldap-client yast2-mail-aliases yast2-mouse yast2-ncurses yast2-network yast2-nfs-client yast2-nfs-server yast2-nis-client yast2-nis-server yast2-ntp-client yast2-online-update yast2-online-update-frontend yast2-packager yast2-pam yast2-perl-bindings yast2-pkg-bindings yast2-printer yast2-runlevel yast2-samba-client yast2-samba-server yast2-schema yast2-security yast2-storage yast2-storage-lib yast2-support yast2-sysconfig yast2-tftp-server yast2-theme-SuSELinux yast2-trans-stats yast2-transfer yast2-tune yast2-update yast2-users yast2-xml zlib #ifdef __ia64__ elilo efibootmgr ia32el #endif #if defined(__i386__) || defined (__x86_64__) microcode_ctl grub lilo #endif #ifdef __powerpc__ lilo #endif Recommended (should have - selected by default) packages: qlogic-firmware OpenIPMI SuSEfirewall2 acpid at autofs bc bind-libs bind-utils binutils blocxx bootcycle bootsplash compat compat-libstdc++ compat-openssl097g convmv cpufrequtils cron dbus-1-glib delayacct-utils deltarpm dhcpcd dmraid dos2unix dosfstools expat fbset finger freetype2 gawk gdb gdbm gettext glib2 glibc-i18ndata glibc-locale gnome-filesystem gpart gpg gpm hal hdparm hfsutils ifplugd info initviocons ipmitool ivman jfsutils joe ksh libevent libgcrypt libgpg-error libgssapi libidn libjpeg liblcms libmng libpcap libpfm libpng librpcsecgss libstdc++ libtiff libtool libusb libxml2 libxslt libzio linux32 log4net lsof lukemftp man man-pages master-boot-code mcelog mono-core mono-data mono-web mpt-status netcat nfs-utils nfsidmap nscd ntfsprogs numactl openct openldap2-client opensc openslp openslp-server patch pax pciutils pcre pcsc-lite pdisk pfmon pmtools popt portmap postfix powerpc32 powersave powersave-libs ppp pptp prctl procinfo procmail providers readline recode release-notes resmgr rsh rsync rug salinfo sash scpm screen scsi sharutils siga smartmontools smpppd sqlite star strace sudo suseRegister suspend syslinux tcpdump tcsh telnet terminfo timezone udev unzip usbutils utempter vlan wireless-tools wol wvdial wvstreams xfsprogs xinetd xntp yast2-backup yast2-boot-server yast2-bootfloppy yast2-cd-creator yast2-heartbeat
Re: [opensuse-factory] Konsole crash
Hi, Arto Viitanen schrieb: As I told about OpenSUSE 10.2 Alpha 2, it crashed the konsole (KDE terminal emulator). I installed Alpha 3 (I tried to upgrade, but there was some problems on glibc.rpm), and konsole crashes still. Actually Alpha 3 seems to be step to worse, since Firefox crashes also. Also automount (of my external harddisk where I keep my backups) complaint that it will not mount to uid 1001 (the first normal user). I tried as root; same stuff. Use Bugzilla. A single report for every single issue, of course. Hint: The Firefox thing is already known and fixed in Factory, no need to report that. Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.automake
Hi, JP Rosevear schrieb: I suspect the gnome-filesystem one isn't really required anymore since /etc/profile.d/ is used by gnome to set ACLOCAL_FLAGS which is respected by gnome-autogen. Stanislav could comment more accurately though. Doesn't suffice for me. Running autoreconf -fi on inkscape with just ACLOCAL_FLAGS set does not work for me. The dirlist entry is really needed there. Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] permissions for sound, dvd, etc
I would like to change the default permissions for the sound devices and the removable media. Right now (10.2 Alpha 3) the first user wins, meaning whoever logs on first gets the exclusive rights on the devices. Not very user friendly, except when you're the first one. So I tried changing the rules for udev as laid out in /etc/udev/rules.d, but to no avail. I managed to change the group for the devices, but not the permissions (from 0600 to 0666 or at least 0644). I then learned about resmgr and went and changed the file /etc/resmgr.conf.d/99-desktop.conf and added some rules for sound and cdrom devices. Still no success. The next stop was in/etc/PolicyKit/privilege.d. There is a bunch of files which allegedly take care of permissions for all kinds of devices. I changed the file hal-storage-removable-mount-privilege, but that did not have any effect on the permissions for my dvd drive or the usb stick. Before I finally mess up the hal configuration (I already checked: it's in /usr/share/hal and /etc/hal) I was wondering if anyone knows where I actually have to tweak my system to let the other users hear sound and mount dvd's (or at least play a video dvd with kaffeine friends). I figured it's got to be somewhere between udev, hal, resmgr and PolicyKit. Perhaps with pam also involved? Or is there another mechanism I didn't even think of (yet)? -- confused Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Fwd: Network and yast fails after the last update
Yesterday I made a complete update in the actual 10.2 alpha 3, and could'nt start the dsl connection, I got pppd died, options error 2. If I try to reconfigure the dsl connection via yast, it closes when reads the configuration. With the network card, yast closes again. I downgrading dbus from *.92 to *.91 and the problem continues. The adsl modem is connected via ethernet. In var/log/messages I found: pppd[4246]: Plugin rp-pppoe.so loaded. Aug 20 20:04:58 kernel: CSLIP: code copyright 1989 Regents of the University of California Aug 20 20:04:58 kernel: PPP generic driver version 2.4.2 Aug 20 20:04:58 pppd[4246]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4 Aug 20 20:04:58 pppd[4246]: Plugin passwordfd.so loaded. Aug 20 20:04:58 pppd[4246]: unrecognized option 'replacedefaultroute' I could'nt fiind the configuration file in which are the option 'replacedefaultroute' The problem was resolved downgrading the ppp package. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] permissions for sound, dvd, etc
2006/8/21, Andreas [EMAIL PROTECTED]: I would like to change the default permissions for the sound devices and the removable media. Right now (10.2 Alpha 3) the first user wins, meaning whoever logs on first gets the exclusive rights on the devices. Not very user friendly, except when you're the first one. So I tried changing the rules for udev as laid out in /etc/udev/rules.d, but to no avail. I managed to change the group for the devices, but not the permissions (from 0600 to 0666 or at least 0644). I then learned about resmgr and went and changed the file /etc/resmgr.conf.d/99-desktop.conf and added some rules for sound and cdrom devices. Still no success. The next stop was in/etc/PolicyKit/privilege.d. There is a bunch of files which allegedly take care of permissions for all kinds of devices. I changed the file hal-storage-removable-mount-privilege, but that did not have any effect on the permissions for my dvd drive or the usb stick. Before I finally mess up the hal configuration (I already checked: it's in /usr/share/hal and /etc/hal) I was wondering if anyone knows where I actually have to tweak my system to let the other users hear sound and mount dvd's (or at least play a video dvd with kaffeine friends). I figured it's got to be somewhere between udev, hal, resmgr and PolicyKit. Perhaps with pam also involved? Or is there another mechanism I didn't even think of (yet)? I have similar problems, and as user I can't mount any removable device (CD, DVD, pendrive, etc. In /media I found the file .hal-mtab-lock, and the content of mtab is: /dev/sda2 / reiserfs rw,acl,user_xattr 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 debugfs /sys/kernel/debug debugfs rw 0 0 udev /dev tmpfs rw 0 0 devpts /dev/pts devpts rw,mode=0620,gid=5 0 0 /dev/sda4 /home reiserfs rw,acl,user_xattr 0 0 /dev/sda3 /windows/C vfat rw,noexec,nosuid,nodev,gid=100,umask=0002 0 0 automount(pid2991) /misc autofs rw,fd=4,pgrp=2991,minproto=2,maxproto=4 0 0 automount(pid2993) /net autofs rw,fd=4,pgrp=2993,minproto=2,maxproto=4 0 0 When I insert a Cd appear the popup window in kde asking what to do, and I press ok, appear other window empty and a label Permiso denegado. Only can mount as root in Konsole, with the command: mount /dev/hda /media The other problem is with digikam, when it try to connect to the cam, it closes. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] permissions for sound, dvd, etc
Juan Erbes wrote: In /media I found the file .hal-mtab-lock, Remove it and try again. It might be leftover of some crash. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: Problem with bold fonts
Did you try the Inkscape 0.44 package from guru? This works fine here! Same problem. I do not think it is related to Inkscape, though I do not have any GTK app handy that could have a font dialog that I know of. Jan Engelhardt -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Now even smart is boken :-(
On Sun, 20 Aug 2006, Marcus Rueckert wrote: smart broke your /usr/lib/rpm/gnupg/pubring.gpg* delete the 2 files. --verbose please! Regards Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Suse 10.1 ff and repositories
I was accustomed to yast, but somehow I did not understand the package management possibilities that came up with 10.1 - using additional package repositories - using another tool apart from rpm or yast ... Can you recommend a good intro into the subject? Christophe
Re: [opensuse] Suse 10.1 ff and repositories
AFAIK, the additional package repositories were already supported before 10.1 and RPM is always used. You could also use a different package management tool before 10.1, like apt-rpm for instance. So the most important new thing in the YaST of 10.1 is the chance to use different types of repositories, and now they need to be signed with GPG. You may use traditional YaST repositories, YUM repositories and others (APT, I think). For the software management, you may also use Smart, which is a different tool not directly related to YaST. For all those questions, opensuse.org is your friend. ;) http://en.opensuse.org/Additional_YaST_Package_Repositories http://en.opensuse.org/Add_Package_Repositories_to_YaST http://en.opensuse.org/Smart El Lunes, 21 de Agosto de 2006 10:03, Christophe Veber escribió: I was accustomed to yast, but somehow I did not understand the package management possibilities that came up with 10.1 - using additional package repositories - using another tool apart from rpm or yast ... Can you recommend a good intro into the subject? Christophe -- Víctor Fernández Martínez Enviado especial a Innsbruck (Austria) para informar de las fiestas Erasmus en la capital tirolesa. Usuario de Linux registrado #312284 en http://counter.li.org. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Reply-To Poll Results (was: Reply-To decision by vote)
Hi, In the time between Tue, 15 Aug 2006 12:00 CEST and Mon, 21 Aug 2006 12:00 CEST 103 out of 926 subscribers (subscribed by Tue, 15 Aug 2006 00:01) voted. The results of this poll are: Vote | Count - Insert Reply-To: | 27 Dont insert Reply-To: | 42 I dont care: | 29 Invalid: | 5 So by majority decision we stay with the current setup without a Reply-To header that points to the list address. Henne -- Henne Vogelsang, Core Services Rules change. The Game remains the same. - Omar (The Wire) pgpJ02raSQIwr.pgp Description: PGP signature
[opensuse] Adressing SUSEs weakness
WARNING: Long e-mail. I have still not seen a good explanation of how you should install SUSE 10.1 on the website. Therefore I have put this up on the wiki in plain sight: '''BEFORE YOU INSTALL READ THIS:''' The package manager in SUSE 10.1 is regrettably broken on most systems. To correct this you should do the following after you have installed SUSE: * Open Yast chose online update configuration , click next and wait until finished. * Press the updater icon on you taskbar/panel * If it updates, congratulations, all is well. * If it throws up an error. Close it. * Install the alternativ package manager/updater SMART. Read the how to [[SMART HowTO|here]] You probably also want to read about [[Using_10.1|Using 10.1]] and the [[Bugs:Most_Annoying_Bugs#SUSE_Linux_10.1_.28Final.29|Most Annoying Bugs]]. Do with it as you please. I think it's a start. We must admit our weaknesses before we can be truly strong. The reason for this is as follows: There were only two places on the opensuse website about how to make the package management work: Opensuse.org - Download SUSE Linux - Scroll abit - Click Most annoying Bugs - Click SUSE Linux 10.1 (Final) And even though It is the first bug to hit you after you install SUSE 10.1 It's pushed back to second place. And what does it say? Fixed with first package management update (please install using YaST Online Update for instance via kdesu yast2 online_update): It says that it's Fixed! You got to be kidding! Or you could go to: Opensuse.org - Download SUSE Linux - Scroll abit - Click Using 10.1 - Read a long and not very consise article about all the strange things that aren't working in suse until you come to Work around. Where it doesn't really say what to do or how unless you clik - SMART. Phew! Hope this stirs things up. -- Regards Kenneth Aar begin:vcard fn:Kenneth Aar n:Aar;Kenneth org:Grafikern.no adr:;;Hasselbakken;Tangen;Hedmark;2337;Norge email;internet:[EMAIL PROTECTED] title:Grafisk/Web Designer tel;work:92899989 tel;fax:92575725 tel;cell:92899989 x-mozilla-html:TRUE url:http://www.grafikern.no version:2.1 end:vcard
Re: [opensuse] Adressing SUSEs weakness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I completely agree with Kenneth. I just had the pleasure to fix my colleague's fresh from the DVD SuSE 10.1 install. - From my impression, SuSE 10.1 is really just broken when freshly installed, and that fact should be clearly stated on the website at a prominent place together with the fix-up procedure, just as proposed by Kenneth. When I started searching on hints on the opensuse Website, I got the impression that everything's ok. In other words it was very hard to get hints on how to bootstrap SuSE 10.1 into a working state. I'd have appreciated his remarks very much. Don't get me wrong, I really like openSUSE and will keep on using this distribution. (I am still on 10.0 aka paradise ;-), so I was not familiar with the 10.1 problems yet...) Kenneth's statement makes 10.1 better than it was before. Regards, Tilman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE6ZiY9ZPu6Yae8lkRAhQGAKCOpX6D+lOM9KZfmZzQPlV7lcNH1ACcCOq5 87EFqYfHCGduexQpbximAB8= =Dbex -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Adressing SUSEs weakness
Kenneth Aar, Grafikern.no [EMAIL PROTECTED] writes: WARNING: Long e-mail. I have still not seen a good explanation of how you should install SUSE 10.1 on the website. Therefore I have put this up on the wiki in plain sight: '''BEFORE YOU INSTALL READ THIS:''' The package manager in SUSE 10.1 is regrettably broken on most systems. And should be fixed with an online update - and will be better with the next one... To correct this you should do the following after you have installed SUSE: * Open Yast chose online update configuration , click next and wait until finished. And restart until everything is installed. * Press the updater icon on you taskbar/panel * If it updates, congratulations, all is well. * If it throws up an error. Close it. * Install the alternativ package manager/updater SMART. Read the how to [[SMART HowTO|here]] You probably also want to read about [[Using_10.1|Using 10.1]] and the [[Bugs:Most_Annoying_Bugs#SUSE_Linux_10.1_.28Final.29|Most Annoying Bugs]]. Do with it as you please. I think it's a start. We must admit our weaknesses before we can be truly strong. The reason for this is as follows: There were only two places on the opensuse website about how to make the package management work: Opensuse.org - Download SUSE Linux - Scroll abit - Click Most annoying Bugs - Click SUSE Linux 10.1 (Final) And even though It is the first bug to hit you after you install SUSE 10.1 It's pushed back to second place. And what does it say? Fixed with first package management update (please install using YaST Online Update for instance via kdesu yast2 online_update): It says that it's Fixed! You got to be kidding! What is still wrong for you with the current update? Or you could go to: Opensuse.org - Download SUSE Linux - Scroll abit - Click Using 10.1 - Read a long and not very consise article about all the strange things that aren't working in suse until you come to Work around. Where it doesn't really say what to do or how unless you clik - SMART. Phew! Hope this stirs things up. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpqvYAC2PMRb.pgp Description: PGP signature
Re: [opensuse] Adressing SUSEs weakness
On Mon, Aug 21, 2006 at 01:14:46PM +0200, Kenneth Aar, Grafikern.no wrote: WARNING: Long e-mail. I have still not seen a good explanation of how you should install SUSE 10.1 on the website. Therefore I have put this up on the wiki in plain sight: '''BEFORE YOU INSTALL READ THIS:''' The package manager in SUSE 10.1 is regrettably broken on most systems. To correct this you should do the following after you have installed SUSE: * Open Yast chose online update configuration , click next and wait until finished. * Press the updater icon on you taskbar/panel * If it updates, congratulations, all is well. * If it throws up an error. Close it. * Install the alternativ package manager/updater SMART. Read the how to [[SMART HowTO|here]] You probably also want to read about [[Using_10.1|Using 10.1]] and the [[Bugs:Most_Annoying_Bugs#SUSE_Linux_10.1_.28Final.29|Most Annoying Bugs]]. Do with it as you please. I think it's a start. We must admit our weaknesses before we can be truly strong. I added some better HOWTOs and killed the SMART reference. Ciao, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Adressing SUSEs weakness
Mandag 21 august 2006 13:36 skrev Marcus Meissner: I added some better HOWTOs and killed the SMART reference. Where? I look here: http://en.opensuse.org/Download There's still a Smart reference and no better howto. Why does the howto refer to Zen-updater (updater icon on you taskbar/panel)? And no reference to YOU? I was under the impression that the way to patch a fresh install was with YOU. Btw. I'm working on a script for patching the package manager. It should be a feature in the next release of konvenientSUSE - the Kommander script I work on to make SUSE more convenient for n00bs. I plan on doing something like this: rpm -i --no-deps http://something.smart.rpm rpm -i --no-deps http://something.python-rpm.rpm smart channel -y --add update type=rpm-md name=update baseurl=http://ftp.belnet.be/linux/suse/suse/update/10.1/ smart update update smart upgrade -y libzypp zmd zen-updater etc. rczmd restart I need to do some testing to work out the details better but does anyone see any major pitfalls with the general idea? Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Adressing SUSEs weakness
Why does the howto refer to Zen-updater (updater icon on you taskbar/panel)? And no reference to YOU? I was under the impression that the way to patch a fresh install was with YOU. On 10.1, I found it effective to uninstall zmd, zen-updater, mono, etc. Then YaST and its online update module can be used to maintain a system with a manually added update server. It ends up working like in 10.0. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [opensuse] Adressing SUSEs weakness
Title: RE: [opensuse] Adressing SUSEs weakness Why does the howto refer to Zen-updater (updater icon on you taskbar/panel)? And no reference to YOU? I was under the impression that the way to patch a fresh install was with YOU. On 10.1, I found it effective to uninstall zmd, zen-updater, mono, etc. Then YaST and its online update module can be used to maintain a system with a manually added update server. It ends up working like in 10.0. A couple of weeks ago, I did exactly as you did (unistalled manually zmd, rug, zen-updater etc), but since then YOU says There are no patches and in the kernel messages I get a line about missing rug/zmd or something like that when I open YOU. It is over a month now since I installed that SUSE version and no update yet (except a huge update YOU did before I erased zmd/rug etc). Something is wrong, right? How do I add manually an update server? I was under the impression that there is a module of YaST doing this...Am I wrong? IMHO, there should be a straightforward message of warning in the frontpage of openSUSE.org website about the problems with system maintenance in 10.1 along with a straighforward solution. Don't get me wrong. It just seems to me that a casual/new user will never find out that something is wrong with his/her fresh 10.1 install unless somebody warns him. --Dimitris Kalamaras
Re: [opensuse] Adressing SUSEs weakness
On Mon, Aug 21, 2006 at 03:46:41PM +0300, Dimitris Kalamaras wrote: Why does the howto refer to Zen-updater (updater icon on you taskbar/panel)? And no reference to YOU? I was under the impression that the way to patch a fresh install was with YOU. On 10.1, I found it effective to uninstall zmd, zen-updater, mono, etc. Then YaST and its online update module can be used to maintain a system with a manually added update server. It ends up working like in 10.0. A couple of weeks ago, I did exactly as you did (unistalled manually zmd, rug, zen-updater etc), but since then YOU says There are no patches and in the kernel messages I get a line about missing rug/zmd or something like that when I open YOU. It is over a month now since I installed that SUSE version and no update yet (except a huge update YOU did before I erased zmd/rug etc). Something is wrong, right? How do I add manually an update server? I was under the impression that there is a module of YaST doing this...Am I wrong? IMHO, there should be a straightforward message of warning in the frontpage of openSUSE.org website about the problems with system maintenance in 10.1 along with a straighforward solution. Don't get me wrong. It just seems to me that a casual/new user will never find out that something is wrong with his/her fresh 10.1 install unless somebody warns him. http://en.opensuse.org/SDB:ZEN-Update_System_problem_in_10.1 Ciao, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] rpm's do not recognize system architechure
All of a sudden my system does not know what it is: 09:25 wahoo:~ uname -a Linux wahoo 2.6.16.21-0.13-smp #1 SMP Mon Jul 17 17:22:44 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux 09:29 wahoo:~ # hwinfo --cpu --short cpu: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, 2200 MHz AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, 2200 MHz 09:25 wahoo:~ # rpm -hiv http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm Retrieving http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm Preparing...### [100%] package smart-0.42-8.guru.suse101 is intended for a x86_64 architecture What have I done wrong and/or, what do I need to change? -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Hi,
Patrick Shanahan schrieb:
09:25 wahoo:~ # rpm -hiv
http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm
Retrieving
http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm
Preparing...### [100%]
package smart-0.42-8.guru.suse101 is intended for a x86_64
architecture
What's the output of these commands:
rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm --showrc | head
rpm --eval '%_arch'
rpm --eval '%_target_cpu'
rpm -V rpm
Andreas Hanke
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Andreas Hanke [EMAIL PROTECTED] [08-21-06 10:55]:
Patrick Shanahan schrieb:
09:25 wahoo:~ # rpm -hiv
http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm
Retrieving
http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm
Preparing...###
[100%]
package smart-0.42-8.guru.suse101 is intended for a x86_64
architecture
What's the output of these commands:
rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm --showrc | head
rpm --eval '%_arch'
rpm --eval '%_target_cpu'
rpm -V rpm
14:13 wahoo:~ # rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n'
rpm
rpm-4.4.2-43.4.i586
rpm-4.4.2-43.4.x86_64
14:13 wahoo:~ # rpm --showrc | head
ARCHITECTURE AND OS:
build arch: i586
compatible build archs: athlon i686 i586 i486 i386 noarch fat
build os : Linux
compatible build os's : Linux
install arch : athlon
install os: Linux
compatible archs : athlon i686 i586 i486 i386 noarch fat
compatible os's : Linux
14:13 wahoo:~ # rpm --eval '%_arch'
i386
14:13 wahoo:~ # rpm --eval '%_target_cpu'
i586
14:13 wahoo:~ # rpm -V rpm
S.5T/bin/rpm
...T/etc/init.d/rpmconfigcheck
...T/usr/bin/gendiff
S.5T/usr/bin/rpm2cpio
S.5T/usr/bin/rpmgraph
...T/usr/lib/rpm/Specfile.pm
...T/usr/lib/rpm/brp-compress
...T/usr/lib/rpm/brp-java-gcjcompile
...T/usr/lib/rpm/brp-lib64-linux
...T/usr/lib/rpm/brp-python-bytecompile
...T/usr/lib/rpm/brp-redhat
...T/usr/lib/rpm/brp-sparc64-linux
...T/usr/lib/rpm/brp-strip
...T/usr/lib/rpm/brp-strip-comment-note
...T/usr/lib/rpm/brp-strip-shared
...T/usr/lib/rpm/brp-strip-static-archive
...T/usr/lib/rpm/brp-symlink
...T/usr/lib/rpm/check-files
...T/usr/lib/rpm/check-prereqs
...T/usr/lib/rpm/config.guess
...T/usr/lib/rpm/config.site
...T/usr/lib/rpm/config.sub
S.5T/usr/lib/rpm/convertdb1
...T/usr/lib/rpm/convertrpmrc.sh
...T/usr/lib/rpm/cross-build
S.5T/usr/lib/rpm/debugedit
...T/usr/lib/rpm/find-debuginfo.sh
...T/usr/lib/rpm/find-lang.sh
...T/usr/lib/rpm/find-prov.pl
...T/usr/lib/rpm/find-provides
...T/usr/lib/rpm/find-provides.ksyms
...T/usr/lib/rpm/find-provides.perl
...T/usr/lib/rpm/find-req.pl
...T/usr/lib/rpm/find-requires
...T/usr/lib/rpm/find-requires.ksyms
...T/usr/lib/rpm/find-requires.perl
...T/usr/lib/rpm/find-supplements
...T/usr/lib/rpm/find-supplements.ksyms
...T/usr/lib/rpm/freshen.sh
...T/usr/lib/rpm/get_magic.pl
...T/usr/lib/rpm/getpo.sh
...T/usr/lib/rpm/http.req
S.5T/usr/lib/rpm/javadeps
S.5T/usr/lib/rpm/macros
...T/usr/lib/rpm/magic
...T/usr/lib/rpm/magic.mgc
...T/usr/lib/rpm/magic.mime
...T/usr/lib/rpm/magic.mime.mgc
...T/usr/lib/rpm/magic.prov
...T/usr/lib/rpm/magic.req
...T/usr/lib/rpm/mkinstalldirs
S.5T/usr/lib/rpm/noarch-linux/macros
...T/usr/lib/rpm/perl.prov
...T/usr/lib/rpm/perl.req
...T/usr/lib/rpm/perldeps.pl
S.5T/usr/lib/rpm/permlist
...T/usr/lib/rpm/pythondeps.sh
...T/usr/lib/rpm/rpm.daily
...T/usr/lib/rpm/rpm.log
...T/usr/lib/rpm/rpm.xinetd
...T/usr/lib/rpm/rpm2cpio.sh
S.5T/usr/lib/rpm/rpmb
S.5T/usr/lib/rpm/rpmcache
S.5T/usr/lib/rpm/rpmd
S.5T/usr/lib/rpm/rpmdb_archive
S.5T/usr/lib/rpm/rpmdb_checkpoint
S.5T/usr/lib/rpm/rpmdb_deadlock
S.5T/usr/lib/rpm/rpmdb_dump
S.5T/usr/lib/rpm/rpmdb_load
...T/usr/lib/rpm/rpmdb_loadcvt
S.5T/usr/lib/rpm/rpmdb_printlog
S.5T/usr/lib/rpm/rpmdb_recover
S.5T/usr/lib/rpm/rpmdb_stat
S.5T/usr/lib/rpm/rpmdb_upgrade
S.5T/usr/lib/rpm/rpmdb_verify
S.5T/usr/lib/rpm/rpmdeps
...T/usr/lib/rpm/rpmdiff
...T/usr/lib/rpm/rpmdiff.cgi
S.5T/usr/lib/rpm/rpmfile
S.5T/usr/lib/rpm/rpmi
S.5T/usr/lib/rpm/rpmk
...T/usr/lib/rpm/rpmpopt-4.4.2
S.5T/usr/lib/rpm/rpmq
S.5T/usr/lib/rpm/rpmqpack
...T/usr/lib/rpm/rpmrc
...T/usr/lib/rpm/rpmsort
...T/usr/lib/rpm/sql.prov
...T/usr/lib/rpm/sql.req
...T/usr/lib/rpm/suse_macros
...T/usr/lib/rpm/symset-table
...T/usr/lib/rpm/tcl.req
...T/usr/lib/rpm/tgpg
...T/usr/lib/rpm/trpm
...T/usr/lib/rpm/u_pkg.sh
...T/usr/lib/rpm/vpkg-provides.sh
...T/usr/lib/rpm/vpkg-provides2.sh
...T/usr/share/locale/cs/LC_MESSAGES/rpm.mo
...T/usr/share/locale/da/LC_MESSAGES/rpm.mo
...T
Re: [opensuse] rpm's do not recognize system architechure
On Mon, Aug 21, 2006 at 02:22:08PM -0400, Patrick Shanahan wrote:
* Andreas Hanke [EMAIL PROTECTED] [08-21-06 10:55]:
Patrick Shanahan schrieb:
09:25 wahoo:~ # rpm -hiv
http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm
Retrieving
http://ftp.skynet.be/pub/suser-guru/rpm/packages/System/smart/smart-0.42-8.guru.suse101.x86_64.rpm
Preparing...###
[100%]
package smart-0.42-8.guru.suse101 is intended for a x86_64
architecture
What's the output of these commands:
rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm --showrc | head
rpm --eval '%_arch'
rpm --eval '%_target_cpu'
rpm -V rpm
14:13 wahoo:~ # rpm -q --queryformat
'%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm-4.4.2-43.4.i586
rpm-4.4.2-43.4.x86_64
Ah, a user of 'smart'. Smart automatically installs all architectures
it can find for a package, effectively breaking them. Please
deinstall 'rpm.i586' and reinstall 'rpm.x86_64'.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Hi,
Patrick Shanahan schrieb:
14:13 wahoo:~ # rpm -q --queryformat
'%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm-4.4.2-43.4.i586
rpm-4.4.2-43.4.x86_64
Ouch. rpm itself is installed twice, once for i586 and once for x86_64.
That's what I suspected...
What you need in the end is that
rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
returns exactly
rpm-4.4.2-43.4.x86_64
and that
rpm -V
returns exactly nothing.
How to get there? Difficult. ;)
Usually I'd say uninstall both versions and reinstall the desired one,
but reinstalling rpm with rpm will be tricky.
Andreas Hanke
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Michael Schroeder [EMAIL PROTECTED] [08-21-06 14:32]: Ah, a user of 'smart'. Smart automatically installs all architectures it can find for a package, effectively breaking them. Please deinstall 'rpm.i586' and reinstall 'rpm.x86_64'. tks, will report back. -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Andreas Hanke schrieb: Usually I'd say uninstall both versions and reinstall the desired one, but reinstalling rpm with rpm will be tricky. 's/rpm with rpm/rpm without rpm/' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Andreas Hanke [EMAIL PROTECTED] [08-21-06 14:40]: Andreas Hanke schrieb: Usually I'd say uninstall both versions and reinstall the desired one, but reinstalling rpm with rpm will be tricky. 's/rpm with rpm/rpm without rpm/' yes, I have reached that problem. What next, manually copy files from midnight commander to the correct locations ?? -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Patrick Shanahan [EMAIL PROTECTED] [08-21-06 15:00]: * Andreas Hanke [EMAIL PROTECTED] [08-21-06 14:40]: Andreas Hanke schrieb: Usually I'd say uninstall both versions and reinstall the desired one, but reinstalling rpm with rpm will be tricky. 's/rpm with rpm/rpm without rpm/' yes, I have reached that problem. What next, manually copy files from midnight commander to the correct locations ?? and this does not work, probably mc uses rpm for access ?? -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Hi, On Mon, 21 Aug 2006, Patrick Shanahan wrote: * Andreas Hanke [EMAIL PROTECTED] [08-21-06 14:40]: Andreas Hanke schrieb: Usually I'd say uninstall both versions and reinstall the desired one, but reinstalling rpm with rpm will be tricky. 's/rpm with rpm/rpm without rpm/' yes, I have reached that problem. What next, manually copy files from midnight commander to the correct locations ?? rpm -e --justdb i386 version rpm -Uhv x86_64 version Cheers -e -- Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Patrick Shanahan [EMAIL PROTECTED] [08-21-06 15:03]: * Patrick Shanahan [EMAIL PROTECTED] [08-21-06 15:00]: * Andreas Hanke [EMAIL PROTECTED] [08-21-06 14:40]: Andreas Hanke schrieb: Usually I'd say uninstall both versions and reinstall the desired one, but reinstalling rpm with rpm will be tricky. 's/rpm with rpm/rpm without rpm/' yes, I have reached that problem. What next, manually copy files from midnight commander to the correct locations ?? and this does not work, probably mc uses rpm for access ?? made simlinks from: /usr/lib64/librpm-4.4.so /usr/lib64/librpmbuild-4.4.so /usr/lib64/librpmdb-4.4.so /usr/lib64/librpmio-4.4.so to: /usr/lib/librpm-4.4.so /usr/lib/librpmbuild-4.4.so /usr/lib/librpmdb-4.4.so /usr/lib/librpmio-4.4.so THAT doesn't work either:^( -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Hi, Patrick Shanahan schrieb: yes, I have reached that problem. What next, manually copy files from midnight commander to the correct locations ?? Now you have basically two choices: 1. Use a program or script that can unpack RPMs without using rpm. 2. Use the rescue system. Try 1. first. The script is here: http://www.iagora.com/~espel/rpm2cpio Download it, rename it to rpm2cpio.pl (to avoid confusion with the real rpm2cpio), copy it to /usr/local/bin and make it exectuable. Now download rpm.x86_64 http://download.uni-hd.de/ftp/pub/linux/suse/update/10.1/rpm/x86_64/rpm-4.4.2-43.4.x86_64.rpm and extract it somewhere (preferably an otherwise empty directory): rpm2cpio.pl rpm-4.4.2-43.4.x86_64.rpm | cpio -id Now copy the extracted files manually to their location. Important: rpm will probably work again, but copying the files manually will not register rpm itself in the rpm database. So you should rpm-install rpm on top of the manually extracted files: rpm -Uvh rpm-4.4.2-43.4.x86_64.rpm And a general hint: Use rpm -U, not rpm -i when installing packages. This might help avoiding double installed packages (-U replaces an existing package which is the right thing in most situations, -i will install a new package in addition to the existing one). If that fails, try 2. Boot into the rescue system, mount your / file system and use rpm -Uvh --root=/mountpoint rpm-4.4.2-43.4.x86_64.rpm to reinstall rpm on the rpm-less system. Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Patrick Shanahan schrieb: made simlinks from: /usr/lib64/librpm-4.4.so /usr/lib64/librpmbuild-4.4.so /usr/lib64/librpmdb-4.4.so /usr/lib64/librpmio-4.4.so to: /usr/lib/librpm-4.4.so /usr/lib/librpmbuild-4.4.so /usr/lib/librpmdb-4.4.so /usr/lib/librpmio-4.4.so NO! Never ever create any symlink from a /lib directory into a /lib64 directory or vice versa. These directories are separated for a reason. Please remove the symlinks again before doing anything else. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Eberhard Moenkeberg [EMAIL PROTECTED] [08-21-06 15:14]: Hi, On Mon, 21 Aug 2006, Patrick Shanahan wrote: * Andreas Hanke [EMAIL PROTECTED] [08-21-06 14:40]: Andreas Hanke schrieb: Usually I'd say uninstall both versions and reinstall the desired one, but reinstalling rpm with rpm will be tricky. 's/rpm with rpm/rpm without rpm/' yes, I have reached that problem. What next, manually copy files from midnight commander to the correct locations ?? rpm -e --justdb i386 version rpm -Uhv x86_64 version Cheers -e Thanks but t late, I have no rpm available: rpm: error while loading shared libraries: librpm-4.4.so: cannot open shared object file: No such file or directory how about the tarball? could you make the tarball available for rpm-4.4.2-43.4.x86_64.rpm? I could config/make/make-install -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Andreas Hanke [EMAIL PROTECTED] [08-21-06 15:19]: Patrick Shanahan schrieb: made simlinks from: /usr/lib64/librpm-4.4.so /usr/lib64/librpmbuild-4.4.so /usr/lib64/librpmdb-4.4.so /usr/lib64/librpmio-4.4.so to: /usr/lib/librpm-4.4.so /usr/lib/librpmbuild-4.4.so /usr/lib/librpmdb-4.4.so /usr/lib/librpmio-4.4.so NO! Never ever create any symlink from a /lib directory into a /lib64 directory or vice versa. These directories are separated for a reason. Please remove the symlinks again before doing anything else. done -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Andreas Hanke [EMAIL PROTECTED] [08-21-06 15:16]: Now download rpm.x86_64 http://download.uni-hd.de/ftp/pub/linux/suse/update/10.1/rpm/x86_64/rpm-4.4.2-43.4.x86_64.rpm and extract it somewhere (preferably an otherwise empty directory): rpm2cpio.pl rpm-4.4.2-43.4.x86_64.rpm | cpio -id Now copy the extracted files manually to their location. Important: rpm will probably work again, but copying the files manually will not register rpm itself in the rpm database. So you should rpm-install rpm on top of the manually extracted files: rpm -Uvh rpm-4.4.2-43.4.x86_64.rpm And a general hint: Use rpm -U, not rpm -i when installing packages. This might help avoiding double installed packages (-U replaces an existing package which is the right thing in most situations, -i will install a new package in addition to the existing one). If that fails, try 2. Boot into the rescue system, mount your / file system and use rpm -Uvh --root=/mountpoint rpm-4.4.2-43.4.x86_64.rpm to reinstall rpm on the rpm-less system. tks, I'm working on it now... -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
On Mon, Aug 21, 2006 at 08:37:51PM +0200, Andreas Hanke wrote:
Hi,
Patrick Shanahan schrieb:
14:13 wahoo:~ # rpm -q --queryformat
'%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm-4.4.2-43.4.i586
rpm-4.4.2-43.4.x86_64
Ouch. rpm itself is installed twice, once for i586 and once for x86_64.
That's what I suspected...
What you need in the end is that
rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
returns exactly
rpm-4.4.2-43.4.x86_64
and that
rpm -V
returns exactly nothing.
How to get there? Difficult. ;)
Doesn't 'rpm -e rpm.i586' work? And don't forget to install the
right version of rpm afterwards...
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Michael Schroeder [EMAIL PROTECTED] [08-21-06 15:27]:
On Mon, Aug 21, 2006 at 08:37:51PM +0200, Andreas Hanke wrote:
Hi,
Patrick Shanahan schrieb:
14:13 wahoo:~ # rpm -q --queryformat
'%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm-4.4.2-43.4.i586
rpm-4.4.2-43.4.x86_64
Ouch. rpm itself is installed twice, once for i586 and once for x86_64.
That's what I suspected...
What you need in the end is that
rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
returns exactly
rpm-4.4.2-43.4.x86_64
and that
rpm -V
returns exactly nothing.
How to get there? Difficult. ;)
Doesn't 'rpm -e rpm.i586' work? And don't forget to install the
right version of rpm afterwards...
yes, but then rpm does not work. see my recent posts. Trying rpm2cpio
at the moment..
tks,
--
Patrick ShanahanRegistered Linux User #207535
http://wahoo.no-ip.org@ http://counter.li.org
HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] gaim segfaults at startup.
Filed as BUG #200704 Did somebody experience this problem too? I can' believe to be the only one :-) Text of filed report: -- On my installation of SuSE Linux 10.1, gaim segfaults upon startup. Current Version of gaim installed: gaim-1.5.0-50 (from SuSE FTP Updates) Message on the command line: *** Gaim has segfaulted and attempted to dump a core file. This is a bug in the software and has happened through no fault of your own. It is possible that this bug is already fixed in CVS. If you can reproduce the crash, please notify the gaim maintainers by reporting a bug at http://gaim.sourceforge.net/bug.php Please make sure to specify what you were doing at the time, and post the backtrace from the core file. If you do not know how to get the backtrace, please get instructions at http://gaim.sourceforge.net/gdb.php. If you need further assistance, please IM either SeanEgn or LSchiere and they can help you. Aborted * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
* Andreas Hanke [EMAIL PROTECTED] [08-21-06 15:16]: rpm2cpio.pl rpm-4.4.2-43.4.x86_64.rpm | cpio -id 15:47 wahoo:~/work # rpm2cpio.pl ./rpm-4.4.2-43.4.x86_64.rpm | cpio -id Error: header not recognized cpio: premature end of archive guess I'll have to go the 'RESCUE' route. be back soon -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Patrick Shanahan schrieb: 15:47 wahoo:~/work # rpm2cpio.pl ./rpm-4.4.2-43.4.x86_64.rpm | cpio -id Error: header not recognized cpio: premature end of archive I know. The script does not work. I should have checked that before. guess I'll have to go the 'RESCUE' route. Not if you can get rpm.x86_64 in a different format from somewhere. And you can. It's already in your inbox. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
On 8/21/06, Andreas Hanke [EMAIL PROTECTED] wrote: Patrick Shanahan schrieb: 15:47 wahoo:~/work # rpm2cpio.pl ./rpm-4.4.2-43.4.x86_64.rpm | cpio -id Error: header not recognized cpio: premature end of archiveI know. The script does not work. I should have checked that before. guess I'll have to go the 'RESCUE' route.Not if you can get rpm.x86_64 in a different format from somewhere.And you can. It's already in your inbox.OK, thanks. rpm works correctly now, but I have lost myself as user. I cannot log in or access any files. It's like I no longer have permission. I cannot even log onto a console. I went to init 1 and back to three but still cannot login :^( ??? Do I need to reboot (wouldn't think)? To install rpm, I opened the tarball in mc and copied each directory across to the proper locations. Did that screw the system ??All I can think to do atm, is add a new user and then move my home directory across ?? tks,-- Patrick ShanahanRegistered Linux User #207535http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album:http://wahoo.no-ip.org/photos
Re: [opensuse] rpm's do not recognize system architechure
Hi, Patrick Shanahan schrieb: To install rpm, I opened the tarball in mc and copied each directory across to the proper locations. Did that screw the system ?? No. All I can think to do atm, is add a new user and then move my home directory across ?? Try that. I guess that the problem is not caused by a particular account, but by something more general. But try it anyway. Actually I guess that whatever transaction caused rpm.i586 to be installed screwed up more things than just rpm. Maybe it installed some nice i586 versions of important pam modules... who knows. Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
On Mon, Aug 21, 2006 at 09:47:11PM +0200, Andreas Hanke wrote:
Patrick Shanahan schrieb:
yes, but then rpm does not work.
I guess that it's because your /bin/rpm is still i586 and you've lost
your i586 shared libraries while doing rpm -e rpm.i586.
Hmm, this should work then:
rpm -e rpm.x86_64
and later on 'rpm -hUv rpm-x86_64.rpm'.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
On 2006-08-21 14:22:08 -0400, Patrick Shanahan wrote:
14:13 wahoo:~ # rpm -q --queryformat
'%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' rpm
rpm-4.4.2-43.4.i586
rpm-4.4.2-43.4.x86_64
maybe another fuckup due the smart bug. :|
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
Hi, Patrick Shanahan schrieb: Possible, but I did not have the user/login problem before replacing rpm. Did you log out and log in between the transaction where rpm.i586 was installed and the point where you fixed rpm manually? Copying the rpm files manually cannot break the login. rpm does not have anyhing to do with that. rpm.i586 did not install itself, it was installed during a package transaction, and the reason why the login is now broken might be linked to the reason why rpm was broken. But rpm is clearly not the reason why the login is now broken. I can't really help you here because I have no idea how the login process works. Since you cannot even log in to a console, X is not the problem and since you cannot even log in to a new account, nothing in your home directory can be the reason. So the reason must be something involved in the login process. How does the login process work? Try to investigate in that direction, associate it to packages and then verify that these packages are correctly installed. Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] rpm's do not recognize system architechure
On 8/21/06, Patrick Shanahan [EMAIL PROTECTED] wrote: On 8/21/06, Andreas Hanke [EMAIL PROTECTED] wrote: Try that. I guess that the problem is not caused by a particularaccount, but by something more general. But try it anyway.Actually I guess that whatever transaction caused rpm.i586 to beinstalled screwed up more things than just rpm. Maybe it installed some nice i586 versions of important pam modules... who knows.Possible, but I did not have the user/login problem before replacing rpm. I have added another user, but still have the same problem. No use copying the home directory as the new user cannot login. I used yast to create the user and the accounts are both enabled. Is there a way to regenerate permissions? Will try rebooting while awaiting an answer.hard working on a wdoz box. Thanks all for vmware :^)..AND, of course, rebooting solves nada. will reboot to the install disk and try recovering the user, but am very unfamiliar with the recovery function :^( Pointers, direction, appreciated.tks,-- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.orgHOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
[opensuse] Re: rpm's do not recognize system architechure
On 8/21/06, Eberhard Moenkeberg [EMAIL PROTECTED] wrote: You should see something in /var/log/messages. attempting to su from root to pat show the attempt but no error or other message other than an attempt nothing shows from attempting logins to X. tks, -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] home directory access problems, permissions???
I am haveing logon problems and believe that I may have found the problem, permissions for home directory. I have: drwxr-xr-x+ 84 pat users 8192 Aug 21 16:56 pat ^ What does the '+' (plus) indicate above and how may I clear it, if that is indeed my problem. Many of the files below /home/pat also have the 'x' in the same location. tks, -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] home directory access problems, permissions???
On Monday 21 August 2006 22:30, Patrick Shanahan wrote: I am haveing logon problems and believe that I may have found the problem, permissions for home directory. I have: drwxr-xr-x+ 84 pat users 8192 Aug 21 16:56 pat ^ What does the '+' (plus) indicate above and how may I clear it, if that is indeed my problem. Many of the files below /home/pat also have the 'x' in the same location. Hi Patrick, I can't tell you off the top of my head how to fix this, but the plus sign indicates the directory has an ACL (Access Control List) associated with it. Does the reported UID (ls -n) match your real UID? Carl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] home directory access problems, permissions???
On Monday 21 August 2006 23:48, Robert Schiele wrote: On Mon, Aug 21, 2006 at 11:21:56PM -0400, Carl Hartung wrote: On Monday 21 August 2006 22:30, Patrick Shanahan wrote: I am haveing logon problems and believe that I may have found the problem, permissions for home directory. I have: drwxr-xr-x+ 84 pat users 8192 Aug 21 16:56 pat ^ What does the '+' (plus) indicate above and how may I clear it, if that is indeed my problem. Many of the files below /home/pat also have the 'x' in the same location. Hi Patrick, I can't tell you off the top of my head how to fix this, but the plus sign indicates the directory has an ACL (Access Control List) associated with it. Type man setfacl to find information about to set that stuff. Thanks, Robert! I hope when Patrick figures out what's going on he'll post the solution and maybe some pointers ;-) Carl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Now even smart is boken :-(
Hello! On 8/20/06, Andreas Hanke [EMAIL PROTECTED] wrote: Hi, Pascal Bleser schrieb: Until that issue is solved (I guess it's a problem with the RPM that is unsigned): smart config --set rpm-check-signatures=False I will try this what Pascal wrote. Thanks. (I know that signatures would be good, but I'm not sure if it really makes a difference. I mean, do we really check all the random keys? And if they are not all signed by some OpenSUSE kay, then we should... well we've been fine installing software before without signatures :-) The package is signed. [...] HG just needs to import Manfred Tremmel's key and that's it. Basic rpm usage. Andreas, if you did look at the output smart gave me... it says that I did in fact import the (Manfred Tremmel) key (it says The above GPG key has been imported successfully.) I even answered that I want to trust it forever. Still it didn't work. Unless you can tell me what I did wrong (here are my smart commands: smart update; smart upgrade - did I have to do something else?), I consider this kind of stuff nonsense and getting boring. I will also check my GPG pubring that others said might have been broken by smart. Thanks again to all! -- HG. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-wiki] Media Wiki skin on OpenSuse.org
Hey, I am one of the organizers of http://foss.in , India's biggest free and open source events. For the event site we would very much like to re-use the media wiki skin being used on http://opensuse.org. Is the skin copyrighted to someone (Novell?) or owned by someone in the community. We would be very grateful if we could reuse for our site. Thanks for the help in advance. -- Shreyas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-wiki] Media Wiki skin on OpenSuse.org
On 2006-08-21 19:24:04 +0530, Shreyas Srinivasan wrote: I am one of the organizers of http://foss.in , India's biggest free and open source events. For the event site we would very much like to re-use the media wiki skin being used on http://opensuse.org. Is the skin copyrighted to someone (Novell?) or owned by someone in the community. We would be very grateful if we could reuse for our site. Thanks for the help in advance. I dont think it would be a good idea to use the same skin. We put much afford in creating an unique skin for our wiki. If you want to use 100% the same skin ... i would say .. no. For copyright questions i pinged Frank. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-wiki] Media Wiki skin on OpenSuse.org
On Mon, 2006-08-21 at 17:11 +0200, Frank Sundermeyer wrote: On Monday 21 August 2006 17:02, Shreyas Srinivasan wrote: Hi, Thanks, for the response. If there is no issue with the copy right then we would like to look at the skin and modify it accordingly. Needless to say as an event which is run by the community the last thing we would like to do is to duplicate/dilute all the branding that wiki and its layout has given to OpenSuse. I will send you the PHP and CSS files via PM. It would be nice if you would give openSUSE credits on your server. Will do so, thanks a lot. I will forward a link to the list once we have modified it to suit our requirements. Thanks again, Shreyas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
