October 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] The KDE4 bugzilla Nonsense hits All-Time high.
by David C. Rankin 28 Oct '09

28 Oct '09

Will, List, You are not going to believe this. What's with the kde developers? You try and help and get the "kiss off" response. That's one of the big things that is wrong with KDE4. This was files as a "Wish" and "Closed INVAL" -- Huh?? Go figure... https://bugs.kde.org/show_bug.cgi?id=211288 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

12 16

[opensuse] Can't select window manager at login
by Jim Sabatke 28 Oct '09

28 Oct '09

I've gone through about a thousand google searches and I can't find out how to make my system (11.1, KDE4.1 with KDE3 and Gnome installed) allow a window manager selection at login. There is nothing on the login screen besides users and password fields. I know this works for some people. Any ideas what I could be doing wrong? TIA, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4

[opensuse] LIRC for default kernel not available.
by Mike McMullin 28 Oct '09

28 Oct '09

I'm using the 2.6.27.29-0.1-default kernel, and looking for the LIRC package that matches it, I'm unbale to access the oss repo for 11.1 and web-pin shows only the following available: Mike@P-733-Lin:~> webpin lirc-kmp-default ... performing request on http://software.opensuse-community.org/ws/searchservic 4 results (1 packages) found for "lirc-kmp-default" in openSUSE_111 * lirc-kmp-default: LIRC kernel modules - 0.8.4_2.6.27.7_9.1 [suse-oss] - 0.8.5~2.6.31~jen90 [http://jftp.medozas.de/SUSE-11.1] - 0.8.5pre2_2.6.27.7_9.1 [home:/rehar:/imontouch] - 0.8.6_2.6.27.7_9.1 [vdr] It looks like there isn't a version available for the kernel that I'm using. Where can I find the source to build the modules and lirc support for the kernel, or better yet the packaged rpm for the kenel? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] How do I prevent an interface getting an IPv6-address on boot-up?
by Per Jessen 27 Oct '09

27 Oct '09

For PPPOE I need an ethernet interface that comes up on boot, but has no IP-address - configuring this manually is no problem, but what would I put in /etc/sysconfig/network/ifcfg-ethX to get it started on boot-up? For now, I've got the following: STARTMODE='auto' BOOTPROTO='' IPADDR= This makes the interface come up without an IPv4 address, but I still get an IPv6 address assigned. I don't know if this causes a problem for pppoe, but there must be a way of getting rid of it? /Per -- Per Jessen, Zürich (8.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 8

[opensuse] Practicalities of IPv6 - tcpdump?
by Per Jessen 27 Oct '09

27 Oct '09

AFAICT, tcpdump has had the necessary ipv6 support for a while, but I can't get it to work. I'm trying to dump ICMPv6 packets with variations of: tcpdump -n -i eth0 ip6 proto \\icmp6 It just won't work - it keeps telling me that 'icmp6' is bad syntax. 'ip6 proto \\icmp' works, but doesn't catch any icmpv6 packets. I think I've got the options right, according to manpage: http://www.tcpdump.org/tcpdump_man.html Any hints or suggestions? Even a polite rtfm .... /Per -- Per Jessen, Zürich (10.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Partition filled up
by Bob S 27 Oct '09

27 Oct '09

Hello Suse people, Running 11.0 with KDE3.5. I keep getting constant warnings that my /home partition is 99% full. Of course it is not. But.......my / partition is,..... according to KDiskFree . That partition is 15GB. Almost impossible. My /home, /var. and /tmp are all on there own separate partitions and are a fraction of their usabe space. I have looked and looked. I cannot find anything that could possibly take up that much space on the / partition. This happened to me a few years ago, on 9.0 or 9.1 and it was eventually resolved, but darned if I can remember how or what it was or the commands the good folks on this list suggested that I use to solve the problem. Anyone for ideas on how to figure out what is going on? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

8 16

[opensuse] KDE 4.4
by Chuck Payne 27 Oct '09

27 Oct '09

Guys, When will openSUSE be supporting KDE 4.4, there is a nasty bug in KWIN that a user here is using, it has been post that the bug is fixed in 4.4. He has reached out to me asking. -- ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- http://en.opensuse.org/User:Terrorpup openSUSE Ambassador openSUSE Member skype -- terrorpup twitter -- terrorpup Identica -- terrorpup freenode(irc) -- terrorpup/lupinstein. friendfeed -- http://friendfeed.com/terrorpup Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. http://www.susestudio.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] Re: Practicalities of IPv6
by Joachim Schrod 27 Oct '09

27 Oct '09

Adam Tauno Williams wrote: > >> My argument has nothing to do with technology at all, > > No, it doesn't. And you haven't given a single sound reason why not to > have an IPv6 deployment strategy. Do you not understand me, or do you not want to understand me? I didn't explain how the situation *should* be, but why it *is* as it is. The reason that most companies don't have an IPv6 deployment strategy is that they think that it is not necessary and doesn't contribute to their bottom line. And if I wouldn't be the CEO/CTO of an IT company, I would probably think the same. Repeat after me: "The bottom line counts. Period." Joachim PS: For the record: I know a lot about IPv6, being involved in big-data-center-level deployments. And I know that it is not as easy as you describe, from personal experience with transition teams. Retraining the network ops is not done in one week, that's dreamland. You have very obviously no experience concerning the level of technical expertise of the common IT staff, for me this is my daily business. And now I'll finish my lunch break and continue with that presentation I should be doing instead of posting here... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Dovecot & Multiple identities
by Koenraad Lelong 27 Oct '09

27 Oct '09

Hi, Since about a week I moved from courier-imap to dovecot, to be able to work with managesieve. I use version 1.2.5, on suse 10.3. It seems to work fine except for one problem : I use a number of aliasses and with Thunderbird is can select which alias to use as my identity when sending a mail. When I use such an alias, I can send the mail (smtp), but it can't be copied to the sent-folder. I'm trying to debug this but dovecot does not help much. I tried rawlog but there is no output (that I see) from it, no files in the maildir. Any hints how to proceed ? Output op dovecot -n : # 1.2.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.22.19-0.4-default x86_64 openSUSE 10.3 (X86-64) base_dir: /var/run/dovecot/ log_path: /var/log/dovecot log_timestamp: %Y-%m-%d %H:%M:%S listen: *:143 ssl_listen: *:993 ssl_ca_file: /etc/postfix/certificate/cacert.org.pem ssl_cert_file: /etc/postfix/certificate/mailbox.pem ssl_key_file: /etc/postfix/certificate/mailboxkey.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 499 last_valid_uid: 499 mail_location: maildir:/var/vmail/%d/%u mail_debug: yes mail_executable: /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap lda: postmaster_address: postmaster(a)mydomain.com sendmail_path: /usr/lib/sendmail auth_socket_path: /var/run/dovecot/auth-master mail_plugins: cmusieve auth default: mechanisms: plain login user: nobody verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail -- Met vriendelijke groeten, Koenraad Lelong -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] Re: Practicalities of IPv6
by Joachim Schrod 27 Oct '09

27 Oct '09

Adam Tauno Williams wrote: > On Sat, 2009-10-24 at 19:53 +0200, Joachim Schrod wrote: >> Adam Tauno Williams wrote: >> > 2001::/16 - Allocated to RIRs >> > 2002::/16 - Allocated to 6t4 >> > fe80::/10 - Link local, those-MAC-derived addresses, at least for >> > Ethernet. It uses a mechanism knows as SLAAC to come up with, at least >> > on Ethernet, theoretically unique address. >> > fec0::/10 - Site local, like 192.168.x.x, 10.x.x.x, etc... >> > fc00::/8 - Unique Local, allocation still up in the air last I knew. >> > But these are like a real network address but not routeable (?). >> > fd00:/8 - Another kind of Unique Local, even more mysterious than >> > fc00::/8. But you can get one from SixXS who seem to have appointed >> > themselves as a registrar. This is what we use internally (one of >> > these) for now. >> I.e., it is too difficult to plan and thus to set up in a small to >> medium company environment. > > How so? > > When you upgrade a service or router, crank up a new site, or replace > some component you just make bringing up IPv6 part of the procedure. > We just added it to our inspection / refresh cycle and in ~2 years we > had IPv6 connectivity across the entire enterprise. We are hardly > all-new-equipment [much of our production equipment is even EOL by the > OEM] but it turns out *everything* except some printers, a couple > DS1/DS3 banks, and a few IPMI interfaces supported IPv6. I.e., you see this from the viewpoint of an IT professional. Most IT support personal in small to medium companies wouldn't even know what IPMI is. They will never have a DS3 connection to their company, much less a whole bank of it. This is also very visible from your other comments; i.e., that all companies that you have ever visited have Cisco or 3com network gear. You're looking at the problem from the very high-end of network deployments. (This is a factual statement, not an evaluation.) With DS1/DS3 banks, you might even work in a networking company. You are aware that this kind of work environment is very special and highly advanced, aren't you? >> This is still a technology for big >> companies or trivial SOHO deployments. > > Why? 1. SOHO IPv6 deployments work out of the box, no need to configure anything. 2. Big companies have a department with IT professionals that can spend the time to learn about IPv6, its advantages and its problems, and they might even be good enough to convince their management to spend money for the transition. As you wrote, IPv6 has actually very interesting features for complex and/or larger environments. And in companies of this size, there is (hopefully) a strategic approach towards IT: Here your argument that one runs IPv6 anyhow by plugging in new systems and one must control such deployments hits home. 3. Small- to medium-sized companies work under completely different premises. They often have an IT workforce of one or two persons who do application management, infrastructure management, system operations, network operations, and end user support. These guys (a) won't have the time to learn about address allocations like the one cited above, or other basic IPv6 principles. (And when they read the recommendation that they should run a daemon for such a simple thing as a default route, they are even less inclined to spend the time learning this "overengineered complex new stuff". After all, they have to keep their gear going.) And (b) the owner of such companies don't have an IT strategy where they are willing to spend money for work that does not bring short-term returns. Their IT strategy is "I have hired two guys and they shall keep my staff happy without asking for more money all the time". All your arguments in this thread are technical and are concerned with the 2nd use case. My argument has nothing to do with technology at all, and is all about the work dynamics of the 3rd use case. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2