August 2014 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] Why using postfix at all? [Was: Why is dovecot using user home directory?]
by Carlos E. R. 23 Aug '14

23 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2014-08-19 at 09:51 -0400, Patrick Shanahan wrote: > * Anton Aylward <> [08-19-14 09:22]: >> 2. The spam/av processing can be done within procmail so why not >> eliminate the sendmail/postfix step and have fetchmail hand off >> to local procmail directly? >> >> >> What this boils down to is this: >> >> Do you have a good reason to apply the processing that can >> *only* be carried out by sendmail/procmail in this path? >> >> >> I poured over this and could not find any. >> >> >> Please note: I'm not saying "Postfix is not needed" in any universal >> sense. I said "in this path". > > I have postfix and by fetchmail handing to postfix I get *all* mail logged > in /var/log/mail, ie: not just fetchmail's and procmail's logs. > > It was a *conscious* decision :^). We forgot another important reason(s): parallelization, speed, and safety. spamd/spamc called from procmail takes 1..3 seconds per email in my machine, but often it goes up to 5 seconds per email (I see this in the log), and even more. This is due not to lack of cpu power, but for waiting for online tests to respond or timeout. See (all are entries trimmed from the 2014-08-15 log): _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD scantime=1.1,size=5696,user=cer,uid=1000,required_score=5.0, _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD scantime=1.2,size=6345,user=cer,uid=1000,required_score=5.0, _00,DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLOCKED scantime=1.7,size=7578, _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,URIBL_BLOCKED scantime=1.9,size=5677,user=cer,uid=1000,re _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_TVD_MIME_EPI,URIBL_BLOCKED scantime=1.6,size=6297,user=cer _00,DKIM_SIGNED,RCVD_IN_DNSWL_HI,T_DKIM_INVALID,URIBL_BLOCKED scantime=2.7,size=7320,user=cer,uid _00,DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALI _00,DKIM_SIGNED,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLOCKED scantime=1.6,size=7151 _00,RCVD_IN_DNSWL_HI,URIBL_BLOCKED scantime=13.3,size=6114,user=cer,uid=1000,required_score=5.0 _00,RCVD_IN_DNSWL_HI scantime=13.3,size=5946,user=cer,uid=1000,required_score=5.0,rhost=localhost 00,RCVD_IN_DNSWL_HI scantime=4.0,size=7131,user=cer,uid=1000,required_score=5.0,rhost=localhost 00,DKIM_SIGNED,RCVD_IN_DNSWL_HI,T_DKIM_INVALID,URIBL_BLOCKED scantime=4.1,size=8650,user=cer 0,RCVD_IN_DNSWL_HI,URIBL_BLOCKED scantime=5.3,size=6182,user=cer,uid=1000,required_score=5.0 00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,SPF_SOFTFAIL,URIBL_BLOCKED scantime=6.6,size=45027, You can see one scantime=13.3 8seconds) in there (with size=6114). Two, actually. On occasion, 12 seconds per email becomes typical, till I find out that a particular online spamassassin test has to be disabled because the internet server it queries no longer responds. Well, if you use fetchmail calling procmail directly, only one email at a time can be processed, but if you put postfix in the toolchain, it queues email internally, and does so safely, because fetchmail can not tell the imap/pop server to delete that email till postfix has saved it to a file in the queue, and tells fetchmail "Ok, I got it". This is so in the entire chain of servers and daemons, local and remote (should be). Old Unix hands would tell you to mount the partition used for mail processing with the option "sync", for this safety reason. This way fetchmail can run at top speed, without waiting for spam/av processing, because postfix is safely storing email in queues on disk, prior to processing it. And postfix can feed typically 2 procmail processes per user, but if you have the power, you can let it call dozens simultaneously, and that means several spamc/spamd processes running simultaneously. When each email takes a few seconds to be processed, most of that time waiting idle (no cpu used), well, feeding say, 5 emails simultaneously does speed things up a bit. This is a big issue when you get a queue of a thousand emails. It can takes hours if you do one at a time. Ah, and procmail can handle several simultaneous processes, even when using mbox files, because it by default uses a different lock file per destination folder. Of course, if all email goes to the same folder, it has to wait. And typically, the spamc call is in another rule. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlP0fMgACgkQtTMYHG2NR9XyyACZAUfz1CJnLJALhrajtbcEkI1O 9kMAn0z1fYqL1JJNMPXn1kHX62gJRC3c =UAnX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 36

[opensuse] How would you do this?
by Lew Wolfgang 23 Aug '14

23 Aug '14

Hi Folks, I've got a web site that's being "retired", so to speak, and will be replaced with a shiny new presentation. But I want to keep the old one on-line for historical reference at a different domainname. For example, the domain hosting the new content would be foobar.org, the one I want to keep for history would be foobar.info. So I need to go through the old html and substitute any references of foobar.org to foobar.info. There are 3705 separate lines in probably 1000 files in a large filesystem hierarchy containing the string that needs swapping. I'd rather not do it by hand! What would you use? awk? A shell script? Something using grep and sed? Thanks in advance for any advice, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 11

[opensuse] most frequently used applications in top part of KDE4 application launcher
by Istvan Gabor 22 Aug '14

22 Aug '14

Hello: I would like to have the list of the most frequently used applications instead of recently used applications in KDE4 application launcher (start menu, set to classic style). I see there is a favorites menu but launching application from there requires a more complex, two-way mouse navigation, easy to lose focus. Starting applications from the top part of the launcher easier and requires only one way mouse movement. Shortly, I want favorites to be placed where recently used applications are now. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] MSI touch screen all-in-one screen brightness
by Istvan Gabor 22 Aug '14

22 Aug '14

Hello: I have a new MSI AIO (all in one) AE200 touch screen computer. I installed openSUSE 13.1 with its default KDE4 on it. The installation was very smooth, and - as a very pleasant surprise - the touch screen has been working "out of the box". I have configured KDE more or less to my liking, it's OK. But there is one thing I don't know is normal or not: The device has buttons to increase/decrease screen brightness but they don't have any effect. Is it possible that they don't adjust the brightness directly but require the OS for an effect? I have worked only with regular monitors so far where I can change monitor settings directly using the buttons/monitor's menu. How can I change the screen brightness in this device? I googled but could not find anything. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] procmail, dovecot-lda, and lockfiles: problems.
by Carlos E. R. 22 Aug '14

22 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had this type of rule in .procmailrc: :0f * ^X-Mailinglist: opensuse | /usr/bin/formail -bfi 'Reply-To: "OS-en" <opensuse(a)opensuse.org>' :0 a: $HOME/Mail/_Lists/os-en which, following talks here, I change to this type of rule: DELIVER="/usr/lib/dovecot/dovecot-lda" ... :0f * ^X-Mailinglist: opensuse | /usr/bin/formail -bfi 'Reply-To: "OS-en" <opensuse(a)opensuse.org>' :0 aw: | $DELIVER -m _Lists/D-os-en which produces these entries in the procmail log: procmail: Couldn't determine implicit lockfile from "/usr/lib/dovecot/dovecot-lda" procmail: Locking ".lock" procmail: Executing "/usr/lib/dovecot/dovecot-lda,-m,lists/D-os-en" procmail: Assigning "LASTFOLDER=/usr/lib/dovecot/dovecot-lda -m lists/D-os-en" procmail: Unlocking ".lock" procmail: Notified comsat: "cer@:/usr/lib/dovecot/dovecot-lda -m lists/D-os-en" The reason is explained in this section of the manual: Local lockfile If you put a second (trailing) ':' on the first recipe line, then procmail will use a locallockfile (for this recipe only). You can optionally specify the locallockfile to use; if you don't however, procmail will use the destination filename (or the filename following the first '>>') and will append $LOCKEXT to it. It also says this about that error message: Couldn't determine implicit lockfile from "x" There were no `>>' redirectors to be found, using simply `$LOCKEXT' as locallockfile. The manual also discourages against using a global lock: LOCKFILE Global semaphore file. If this file already exists, procmail will wait until it has gone before proceeding, and will create it itself (cleaning it up when ready, of course). If more than one lockfile are specified, then the previous one will be removed before trying to create the new one. The use of a global lockfile is discouraged, whenever possible use locallock- files (on a per recipe basis) instead. The working is thus. In the first type of recipe: :0 a: $HOME/Mail/_Lists/os-en procmail easily determines that it has to use "$HOME/Mail/_Lists/os-en.lock" as local lock file. On the second type, however: :0 aw: | $DELIVER -m _Lists/D-os-en It knows that there is a pipe, so it looks for the redirect to file at the end of the line to find out what is the destination "folder" of the recipe to create a lock with that name, and not finding one, it simply creates one with the default name of ".lock", which ends being a global lock and breaks parallelization of procmail. The solution, it would seem, is for me to specify a lock file myself: :0f * ^X-Mailinglist: opensuse | /usr/bin/formail -bfi 'Reply-To: "OS-en" <opensuse(a)opensuse.org>' :0 aw: HOME/Mail/_Lists/os-en.lock | $DELIVER -m _Lists/os-en But this creates a new problem: procmail: [20651] Thu Aug 21 12:02:34 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: Unlocking "/home/cer/Mail/_Lists/yp-os-en.lock" procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20702] Thu Aug 21 12:02:34 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20815] Thu Aug 21 12:02:35 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20773] Thu Aug 21 12:02:35 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20652] Thu Aug 21 12:02:42 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" ... procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20652] Thu Aug 21 12:04:27 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: Executing "/usr/lib/dovecot/dovecot-lda,-m,_Lists/os-en" 2 minutes timeout. procmail: [20702] Thu Aug 21 12:05:31 2014 procmail: [20794] Thu Aug 21 12:05:31 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" ... procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20773] Thu Aug 21 12:06:03 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20651] Thu Aug 21 12:06:08 2014 procmail: Assigning "LASTFOLDER=/usr/lib/dovecot/dovecot-lda -m _Lists/os-en" procmail: Unlocking "/home/cer/Mail/_Lists/os-en.lock" procmail: Couldn't unlock "/home/cer/Mail/_Lists/os-en.lock" procmail: Notified comsat: "cer@:/usr/lib/dovecot/dovecot-lda -m _Lists/os-en" From opensuse+bounces-162890-......... Thu Aug 21 12:02:10 2014 Subject: [opensuse] Re: on why maildir isn't standard... Folder: /usr/lib/dovecot/dovecot-lda -m _Lists/os-en 9722 The problem is that dovecot-lda also checks and creates a lock file, using that same lock file, of course (/home/cer/Mail/_Lists/os-en.lock). As the lock already exists, it waits... for ever, or till I manually delete the lock file. What should I do? I think that I should tell procmail to abstain from creating a lock file at that point, and let "dovecot-lda" handle it itself. But I have not found a setting for that in procmail. Perhaps removing the last ":" from the recipe :-? But that would instead create a global lock file instead, which breaks parallellization. The manual says: Recipes A line starting with ':' marks the beginning of a recipe. It has the following format: :0 [flags] [ : [locallockfile] ] <zero or more conditions (one per line)> <exactly one action line> ... Local lockfile If you put a second (trailing) ':' on the first recipe line, then procmail will use a locallockfile (for this recipe only). You can optionally specify the locallockfile to use; if you don't however, procmail will use the destination filename (or the filename following the first '>>') and will append $LOCKEXT to it. So I think I should specify a dummy lock file somewhere, perhaps under "/run/user/[UID]/" for speed. But I don't know how to automatically create a folder hierarchy there for my use, on every boot. And link to it by name, not UID. I may concoct something. I will try that. Reading material: The documentation on the dovecot site doesn't mention the issue at all: <http://wiki2.dovecot.org/procmail> And on the procmail site: <http://www.procmail.org/>, many of the links are dead. * a searchable archive of the procmail mailing list <http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/> --> Error 404 * Era Eriksson's Procmail Mini-FAQ <http://www.iki.fi/era/procmail/mini-faq.html> redirects to <http://partmaps.org/>, which is in German, I think. Google translate translates: +++······························· Simple shower enclosure or shower cubicle luxury Posted by Maxi on August 14, 2014 . No comments . Besides shower enclosures, which are available in different shapes, you can buy individual shower elements, such as a shower door or a shower wall or a shower enclosure for the tub. Especially handy are the foldable shower enclosures, which are simply placed on the bathtubs and there it ·······························++- I guess that does not help me. :-} * Peter Hartzler's SmartList FAQ <http://www.hartzler.net/smartlist/SmartList-FAQ.html> - --> The requested URL /smartlist/SmartList-FAQ.html was not found on this server. * Jari Aalto's Procmail resources <http://pm-doc.sourceforge.net/> There is nothing here, just a stub from sourceforge. But it links to "Procmail Documentation main page" at <http://pm-doc.sourceforge.net/doc/>, which finally contains real text. I'll read that. There is an interesting section: «4.11 Local lockfile usage» [...] Nope, no way to disable the lock. «5.4 Flag w, lock file and recipe with pipe(|) » It says that if you do not use 'w', the lock file is inmediately removed after handling over to the pipe. BUT, if the pipe fails, procmail would not learn about it, and the email would be lost (if it fails and knows about it, the email is sent instead to the default folder). * Nancy McGough's Procmail Quick Start page at it's primary server or from a mirror. - --> <http://www.ii.com/internet/robots/procmail/qs/>, and the site is up (PROCMAIL QUICK START - An introduction to email filtering with a focus on procmail). Last modified: 2007-11-27T14:37:28 CET There is an interesting info here: it says to run "procmail -v" to find out the lock strategy used by procmail (<http://www.ii.com/internet/robots/procmail/qs/#lock>). It turns out to be: Locking strategies: dotlocking, fcntl() The procmail people aparently decided, long ago, not to use kernel locks - see <http://pm-doc.sourceforge.net/doc/#compiling_procmail_and_choosing_locking_…> +++······························· General advice: Everything except dot locking is usually broken. [stephen, <199607292139.XAA12433(a)hera.cuci.nl>]. Remove fcntl() and lockf(), only allow flock() (or omit it completely) Kernel locks don't work. But that's all some programs use. Across a networked filesystem, lockf() doesn't work, fcntl() and flock() should, but they don't either because the lockd is buggy. Mailtool uses fcntl() but does it wrong, so that's another problem. The only thing that works on all platforms, all networks, all the time are .lock files. ·······························++- The above mentioned link on <http://www.ii.com/internet/robots/procmail/qs/#lock> has very interesting info on locking, but some of the links are dead. +++······························· Mailbox Locking If you use a mail or news client to change a mailbox that is receiving messages — for example, to delete a message — make sure that both procmail and your client use the same locking scheme. To determine what locking strategies are used by your installation of procmail, and the order in which these locking strategies are used, run: procmail -v and look at the value of “Locking strategies.” To learn about file locking, see: 11.4 How does folder locking work? and questions 11.5, 11.6, & 11.16 in the UW Pine Information Center's Info for systems administrators, developers, etc. This is useful to read even if you do not use Pine. (working link). File locking in the Era's Procmail FAQ (redirects to page about showers) 4.11 Local lockfile usage and 4.12 Global lockfile in Jari's Procmail Tips (broken link: 404) The thread "Lock files - confused" in the Procmail mailing list archives (working link) Configuring Netscape Mail on Unix by Jamie Zawinski — this is useful to read even if Netscape is not your mail client. (redirects to silly netscape.aol.com page) [!] Make sure that you are not delivering to mailboxes in Unix spool (mbox) format on an NFS or any other network file system since locking does not help on those systems. For a possible workaround to this, see the comp.mail.imap message Re: UoW IMAP, lock files and multiple servers by Mark Crispin. The Netscape mail client does no locking of its local mailboxes, meaning that there is no safe way to deliver directly to them. Kmail seems to be flaky about locking local mailboxes. For details, search the KDE Documentation for procmail. ·······························++- * Timo Salmi's procmail tips and recipes <http://www.uwasa.fi/~ts/info/proctips.html> redirects to <http://www.netikka.net/tsneti/info/proctips.php>, with the correct info. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlP2VLgACgkQtTMYHG2NR9XWwgCfagPCZRpg31oX5LcNzlXz1Kvz i8wAn3D59PZBDvqsas8QEvNc9uUycGfb =A9yO -----END PGP SIGNATURE-----

3 2

[opensuse] Connecting to MS communicator
by Klaus Vink Slott 22 Aug '14

22 Aug '14

On my work they are replacing our telephone system with a Microsoft lync 2010 solution (sigh). One colleague using Pidgin on Ubuntu have had success in using Pidgin with pidgin-sipe on top. He claims he is able to make and receive voice calls using this combo. I have found the same packet for OpensSUSE and my pidgin now registers with the MS phone server. My colleagues can see my status. But I have no sign of a voice call possibility in any menu. Does anybody have a guess on what I am missing to get voice support in pidgin/sipe? Any other suggestions on a framework for connecting to MS-com are also welcome (other than running windows in a VM). I have tried Telepathy for IM in the past but back then it was a pain to keep connected and often broke after a update. -- Regards Klaus -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] hylafax/avantfax with php 5.4+ (any fixes or interest in helping fix it?)
by David C. Rankin 21 Aug '14

21 Aug '14

All, The elegant fax handling solution of hylafax/avantfax will not work with php >= 5.4. I have discussed the issue with the developer on the hylafax list and understand that avantfax is basically broken until it can be rewritten but the developer hasn't, and probably won't, have time to fix/rewrite avantfax over the next few months. The purpose of the post here is to ask: (1) are there any users of avantfax that have patched avantfax to work with php 5.4+; (2) any interest in doing so? If there is anyone fluent in php that is interested, I'm interested in helping and have a couple of installs to test with. However, I don't have the time or php fluency required to shoulder the rewrite. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] Re: on why maildir isn't standard...
by Linda Walsh 21 Aug '14

21 Aug '14

Anton Aylward wrote: > On 08/20/2014 07:57 PM, Linda Walsh wrote: >> That it takes almost 4x the space is bad enough, but that >> it 200-300 times slower is the real bear. > > That makes no sense. > If space were the issue then we would not use HTML mail, it would be > banned from all major servers and archives. There would also be a ban > on attachments: selfies, lolcats, ftp-by-email of documents and > spreadsheets. ---- That's not space on an ISP... that's local space. Though the peformance hit is worse than the space hit. > So no I don't buy that. I'm not an ISP trying to sell you something. > > As for the 'slower', no I don't but that either; its just a matter of > juggling your metrics. You have made no provision for the spin-lops of > mbox locking or the hassle that is needed to deliver mail while a user > has the file open reading it; all of which involves copying the whole > file back and forth. ---- Yes, I did. I don't need locks for grepping through my local mail. Mail is MOST often an append, then read-only resource. It's not generally used as a random access database. Dovecot keeps meta indexes for other info outside of the mbox with the data stored in 1 compact form. > You 234 Megabyte mailbox. Deleting or tagging a > single message with maildir involves deleting a single file. With mbox > it involves copying the whole file, stopping in the middle, skipping, > the copying the rest. --- NO IT DOESN'T... That's not the way Dovecot works. It keeps meta changes in it's index files. The data in the mbox is remarkably unchanged except when automated processes expire the email. > Your view of resources is a static one, driven by 1970s economics. > The forces that apply today have more to do with the user experience. ---- ?? Sorry, I prefer to wait .05 seconds to search through my 200MB mailbox rather than up to 60 seconds... > > Personally I think your obsession is irrelevant and I'm more concerned > that your absolutist attitude is spreading misinformation. ---- performance of 200-300x is relevant. > > As far as I'm concerned all the MTAs and MDAs and mail readers I use can > handle both mbox and maildir, so I pick what suits the context I work > in. My INBOX is maildir; my archives, which I seldom access and never > delete anything from, are mbox. ---- Nearly everything in my mail directory is an archive. I rarely if ever need random access updates to mailboxes. As for spreading misinformation -- I documented my claims in 2 cases, by using the sources you referred to. You are glossing over the fact that these things are not default and though your alligators won't stay off my crocodiles, our initial intent was to drain the swamp... trying to find out why something isn't working in it's initial setup -- that was the problem. In initial setup, things are in default state -- so that is what I try to use as a baseline in suggesting debugging and setup attempts. I certainly would not recommend how I have my system setup for most people. But I'm a computer person and I thihk you are two. Things that we do to computers would give most people nightmares... It's not about what we can do, but about going with the simplest setup from the defaults. Once that is working, THEN scale up complexity.. > >> It might come down to usage, but putting each message in a separate file >> generally will waste space, time, resources... human time and cpu time... > > Yes, that was the mentality of the 1970s when resources were scarce and > cost more than human time. --- No, it is today... from a cold cache, 0.2 seconds w/mbox, vs. 60+ seconds for maildir. You cannot claim 60 seconds is a reasonable time to wait for a spur of the moment search. > One of the reasons that Postfix and qmail are so popular is that > sendmail has the ${DEITY}-${PERDITION} awful configuration setup. > Postfix is not only more secure, and can run with lower privilege; qmail > is almost trivial to set up and is also more secure; Smail3 setup is > about the level that Marcus Ranum's proverbial cat can manage. --- I will not argue that point. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

Re: [opensuse] unwanted obligation to move to ubuntu because of outdated kernel with SuSE
by Julien Michielsen 21 Aug '14

21 Aug '14

> > >> check in build system. >> for example here >> https://build.opensuse.org/package/binaries/Kernel:linux-next/kernel-vanill… > AFAIK it is 3.17 there. >> > Thanks for your suggestion. I'll try it. > Julien I did try to get it, but could not find a downloadable kernel at that spot ("404-not found errors" only) Julien > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > -W- Julien Michielsen julien(a)michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] unwanted obligation to move to ubuntu because of outdated kernel with SuSE
by Julien Michielsen 21 Aug '14

21 Aug '14

> check in build system. > for example here > https://build.opensuse.org/package/binaries/Kernel:linux-next/kernel-vanill… AFAIK it is 3.17 there. > Thanks for your suggestion. I'll try it. Julien > > On Thu, Aug 21, 2014 at 12:48 PM, Julien Michielsen < > julien(a)michkloo.xs4all.nl> wrote: > >> I do have a hp 650 notebook, and I cannot have internet-acces with it because it has a Ralink chip in it. The older linux kernels cannot "talk" with this chip because of an unpatched kernel error. This patch is part of kernels from 3.12 on. I did try to compile and install kernel 3.12.6, but this kernel failed to communicate on notebook, supposedly because I should also upgrade Ralinks firm- ware. I tried to do so, but did not manage to get it working, as it gave compilation-errors. An example: >> >> /home/julien/local/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:43:23: error: expected '=', ',', ';', 'asm' or '__attribute__' before >> 'rt2860_remove_one'static VOID __devexit rt2860_remove_one(struct pci_dev >> *pci_dev); >> >> I do not know how to solve this, and moved to Ubuntu-14.4, with a 3.14 kernel. This worked fine, but I'd like to stay with SuSE. (although in the end Ubuntu might prove a good change) >> Could I possibly find a 3.12 kernel at SuSE? >> thanks >> Julien >> >> -W- >> Julien Michielsen >> julien(a)michkloo.xs4all.nl > >> -- >> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse+owner(a)opensuse.org >> >> > -W- Julien Michielsen julien(a)michkloo.xs4all.nl -W- Julien Michielsen julien(a)michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1