Re: /tmp full (newbie)
On Thursday 12 February 2004 22.05, Jez Hancock wrote: On Thu, Feb 12, 2004 at 09:44:27PM +0100, gaf wrote: Thank you for answering. I?d hoped not to reinstall but. Partitioning is no problem, I?ve installed all versions from 4.8 to5.2 on my old computer just for training and trying. The problem with the current scheme is you have only 4Gb or so for everything apart from /home - I don't have KDE / X installed, but I'm fairly sure KDE on it's own would eat up 3-4Gb of space without too much problem. If you reinstalled I'd say assign 20Gb to /usr if you're going to use KDE. This is way *way* overestimated. du -sh on my /usr/local shows 3.6Gb - that's with *two* installations of KDE (one in it's own prefix, still in /usr/local though), an unpacked set of sources for it, a jdk (hey, they're getting pretty big these days), and a fairly full install of GNOME to boot. Plus various other random things. I would hate to see how much you'd have to install to fill up 20 Gb of /usr, especially with a separate /home.On the other hand, I can find a million ways to fill up as much /home as I'm given, and I frequently do (fill it up, that is) With some judicious cleaning up of the cruft in /usr/ports/* (try portsclean, part of the portupgrade suited), possibly nuking /usr/obj (although you'll want space back for that if you build world again) and some investigation into maybe rolling over logs more often, and emptying out /tmp, there's no pressing reason the OP should need to repartiiton and reinstall, especially not for the sake of either KDE or GNOME. I think for most people the installers auto defaults are not pretty workable, and that merging the suggested file systems is probably not advisable until you have more experience with the system and know what your pattern of usage really is. Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ pgp0.pgp Description: signature
Re: /tmp full (newbie)
On Thursday 12 February 2004 22.38, Lauri Watts wrote: With some judicious cleaning up of the cruft in /usr/ports/* (try portsclean, part of the portupgrade suited), possibly nuking /usr/obj (although you'll want space back for that if you build world again) and some investigation into maybe rolling over logs more often, and emptying out /tmp, there's no pressing reason the OP should need to repartiiton and reinstall, especially not for the sake of either KDE or GNOME. To clarify this, since I'm editing my silly typo below, personally, I think I would reinstall in the current situation. I just meant it's probably not urgently in need of doing right this minute just to get KDE running. There's probably a fair amount of cleanup, and the other posters symlinking suggestions, that will provide the immediate solution of 'get back up and running' for the present. A reorganisation in the future, is not a bad idea though. I think for most people the installers auto defaults are not pretty s/not/now/ I meant here, honest. Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ pgp0.pgp Description: signature
Re: fish sftp and konqueror
On Tuesday 14 October 2003 05.46, Robert Froese wrote: I'm confused. I didn't get any response to my last post, in which I asked for information about getting fish working in Konqueror. Does nobody else use Konqueror as an sftp or fish GUI interface? Or, have I done something uniquely stupid to break it on my 5.1-R box? You wil linvariably get better results posting to the KDE FreeBSD list ([EMAIL PROTECTED]). Neither are working for me: sftp not at all and fish not if I try to connect to a FreeBSD box. Funny, but fish works if I try to connect a linux box. I've searched the list archives, the KDE bug database, and the FreeBSD bug database with no luck. Perhaps there's a great alternative to sftp or fish in Konqueror that I'm not aware of? Any advice would be greatly appreciated! Cheers, Off the top of my head, fish on FreeBSD is currently not working with password connections if it's already tried (and failed) a key exchange. If this is your situation, try either using keys, or switching the authentication challenge order in the server's sshd configuration. Other things that trip people up: For fish to work right, both machines must be able to reach each other by hostname, and if you have installed the openssh port, make sure the right sshd configuration is being picked up - the one from the port, not the original base one, a couple of people have hit problems when the configs were different, and their edits were not having any effect, and this was why. Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ pgp0.pgp Description: signature
Re: Problem installing/upgrading QT3.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 21 September 2003 04.24, Dragoncrest wrote: Bad philosophy! In that case, revert the Qt port back to the previous working Qt 3.1 port ASAP and fix it in the meantime. Actually, he said he used the package off of the freebsd website to reinstall the older version and by doing that he's up and running again. So he's good there. Myself, I haven't had this issue with QT to date. It's installed and upgraded fine for me. But then again I've been lucky so far too. No major issues at all with KDE...yet. (*crosses fingers*) Ok, I withdraw my previous statement. It appears I'm now having the same issues he is. Decided to do a CVS update on my ports then check my KDE versions. Found out I didn't have the latest version like I thought, so I tried updating QT as well and got the exact same issue he did to the letter. So I'm guessing the port is broken somehow. Oh well, I guess I wait for a patched version right along with the rest of ya. Patch may be a while forthcoming, Qt seems to think your machines are running windows during the install, when they perfectly well figured out they weren't during the build. In any case, it appears that the fix at this point is simply uninstall any existing Qt version, and install the new one. Packages are available for 4-STABLE and 5.1-RELEASE, instructions at the second address in my .sig Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/bPtk/gUyA7PWnacRAueHAKCUTS0mmSwmVXvQbecHXHS9GQSVzgCfUmVz iV/DOVMwybhHolBUjgd/F40= =kTi5 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ok, KDE/Help .. after my moans what now ?
further: How to Ask Questions the Smart Way: http://catb.org/~esr/faqs/smart-questions.html How to Report Bugs Effectively: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Writing FreeBSD Problem Reports: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ pgp0.pgp Description: signature
Re: Ok, KDE/Help .. after my moans what now ?
On Monday 03 March 2003 19.04, Cliff Sarginson wrote: On Mon, Mar 03, 2003 at 09:43:25AM +0100, Lauri Watts wrote: That's not a requirement, it's an option, if you want special support for that card from something that offers it. Probably X itself, certainly nothing related to KDE. Ok, but no choice in portupgrade. Matrox cards are common as muck, even I know how to find out how a system has one or not. Put the option in pkg_tools.conf *What* says libintl is missing? which binary? there is no binary called KDE, something specifically must be giving these problems. I am aware of that. It is startkde that is complaining. startkde is a script, that runs several commands, we need to narrow down which of them is the problem. Plus the fact I cannot even re-intall KDE from the 4.7 ISO CD's. I get the highly useful message Error -1. From what? The CD-Rom drive? KDE? What KDE binary? From pkg_add? from Portupgrade? from tcsh? From Raelian clones? Who knows. I know. I tried to restore the status quo ante. This, in my mind, was not so very unreasonable. The information about ports given out is that they are not dependent on a release. They clearly are. This is a fault in the system, not in yours truly. No, this is *packages*. Binary *packages* are built on a particular system. and may differ between versions of that particular system. The same port, built on 5.0-Release and 4.7-Release and 4.8-Prerelease will be different compiled binaries from the same source. Now, correct me if I am wrong. The tag for ports should always be ., since the do not follow any kind of upgrade system like the release does. Why does portupgrade try to find 4.8-PRELEASE ports ? This is nonsense. From where is it getting this idea ? uname -a Ok, see above. It should not be caring about my release. Ports, according to all information sources I have read, are not RELEASE dependent. Of course they may have dependencies, but that is not the same thing. Right. They are. Only package installs will care about the OS. 3: Have an up to date portsdb -u. Run it after every cvsup. Most If it actually fails, cut and paste what it says into an email and ask. Don't give anecdotes or paraphrase the errors, if you do we *cannot* help you. I run it every time. I am not paraphrasing errors. You are paraphrasing errors, or cutting them short. One single line of error output from gcc is useless without knowing what it was trying to compile or link, and knowing what other packages are installed so we can guess why it's not finding the files it wants. So you need to paste at least several complete lines above the actual error message before we are able to help you. You seem to be feeling very hostile, but there are several of us out here *trying* to help. You're not making it very easy. If you want the problems fixed, we need more information. If you just want to rant, then this conversation is done, I won't participate anymore. 4: Don't try to upgrade piecemeal if other ports are out of date. The problem you describe above probably relate to a out of date dependency ports, but I can't be totally sure without the info from pkg_info -Ia. Don't paraphrase that output, cut and paste it into an email, or I can't help you (are you seeing a pattern here?) No. Because you are assuming I am an idiot. I tried, following the bouncing ball, not assuming I knew better, to bring a system up to date. It failed. I'm assuming no such thing. I'm telling you that I need specific information that you have not so far provided. If you provide this information, I can help, if you don't, I cannot. It's up to you. Ok, point taken. I don't paraphrase. I can cut and paste Error -1 or type it in. It still remains Error -1. And you still haven't told us *what* command gave that reply. Or any of the other information you have been asked for. - The ports system is supposed to be independent of the OS/Release, it is not. It is. The packages are not, they cannot be, because the OS itself is an evolving thing. Packages are not ports, they are single snapshots of a port built on a single snapshot of a released version of the OS. - KDE is unbuildable. KDE is entirely buildable, very many people have built it successfully on very many versions of this operating system, and on many other operating systems (even HP/UX). If it's not buildable on your system, we still don't have enough information to even begin to diagnose why. As I've asked already, start with posting uname -a, pkg_info -Ia, and the configure results of the first port to fail (that'd be arts, if Qt 3.1 is ok - I haven't seen you yet complain about Qt, so I'll guess it is.) Then we might well be able to start fixing the problems. - Shoving latest releases of KDE (and Gnome) into ports without the binary install of them is bad news. I have a fast high speed ADSL
Re: aRts-1.1.1, FreeBSD 4.7
On Wednesday 19 February 2003 17.30, Willie Viljoen wrote: Sorry, this may be off topic. I'm running KDE 3.1 compiled from ports, including latest kdelibs and kdebase and latest aRts (1.1.1). I used to have sound in KDE, but decided to turn this off as I was running applications that didn't want to go with aRts. These are now more willing to talk to aRts, but I can't get aRts to talk to my sound card anymore. The card is a Creative Labs SB16, I have it running with the newpcm and sbc drivers, and everything works fine other than aRts not cooperating. I have tried all sorts of tinkering with aRts settings, nothing helps. Once you have it set up again, http://freebsd.kde.org/faq.shtml (question 11) will sort out any aRts is hogging the soundcard issues you had. What kind of tinkering have you tried? Can you look at the output of ps axwww |grep artsd and show me the entire command line? Mine looks something like tihs, these are fairly safe settings: artsd -F 10 -S 4096 -s 60 -m artsmessage -l 3 -f If you have no arts running, and you run this commandline in a terminal what happens? CC'ing the kde list, likely more input there. -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ msg19883/pgp0.pgp Description: signature
Re: Basic Ports Question, KDE, Korganizer
On Tuesday 18 February 2003 22.58, humbert wrote: Hello - I basically run xwindows so I can have a browser and a PIM program. I recently installed fbsd 4.7 from the mini-install CD. I used sysinstall to set up KDE and everything went perfectly. The version of korganizer in ports is 3.0.x something. But it looks ugly and I would like to upgrade to the latest version. I download the source and tried to compile, but it couldn't find any Qt headers or normal stuff like that. I tend to prefer funtionality over worrying about a default appearance. http://www.kde-look.org if it's ugly was the only complaint you had. So my questions are these: 1) How can I install kdepim/korganizer from ports originally, but then continue to compile from source to keep current? Do people normally just wait until the ports collection is updated? The ports collection is updated generally the same day the official release is made (this is true for both KDE and GNOME, and many many other applications, less true for others. In a very broad generalisation, the bigger and more visible the project, the sooner the ports get updated.) KDE 3.1, for example, has been in the ports for a few weeks now. You have no need to compile from sources to keep current, what you need to do is: a: read the handbook and learn about cvsup and the ports collection b: install sysutils/portupgrade, read it's man pages thoroughly, and use it to keep your system up to date. 2) Does anyone know why gnomepim wouldn't install? This is the error I am getting: === Extracting for gnomevfs-1.0.5_4 Checksum mismatch for gnome/gnome-vfs-1.0.5.tar.bz2. Make sure the Makefile and distinfo file (/usr/ports/devel/gnomevfs/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 The distribution file you downloaded wasn't complete, or was otherwise damaged. Remove it (it'll be in /usr/ports/distfiles/gnome-vfs-1.0.5.tar.bz2) and try again. It'll probably work even better if you follow points a and b above. Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ msg19777/pgp0.pgp Description: signature
Re: FreeBSD Media Player equivalent...
On Wednesday 19 February 2003 00.13, Antoine Jacoutot wrote: On Tuesday 18 February 2003 21:44, Stijn Hoop wrote: Even better, check out http://mplayerplug-in.sourceforge.net/. A simple cvs co gmake will do. I can't make it work with Konqueror... Anyone succeded in making in work ? Thanks. Make what work? so you can click on a file and it opens in mplayer? Run kappfinder, let it find your mplayer binary and add it to the K menu. In KControl, go to the file associations module, and make sure mplayer is associated with the file formats you want. Move it up to the top to make it the default player (the one that runs when you click on a file), or leave it where it is, and it will be available in the right click - open with menu for any associated file type. For what it's worth, Lioux and I just spent the whole night working (ok, him mostly working, me mostly cheerleading) on fixing the xine arts plugin - giving noatun and kaboodle the ability to directly play any video format that libxine provides, a feature that previously hasn't worked on FreeBSD. Video thumbnail previews in Konqueror, and an embeddable sidebar player to come as soon as we figure out how to make them work too. Look for ports in a cvsup near you any hour now. Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ msg19786/pgp0.pgp Description: signature
Re: FreeBSD Media Player equivalent...
On Wednesday 19 February 2003 02.01, Antoine Jacoutot wrote: On Wednesday 19 February 2003 00:33, Lauri Watts wrote: Make what work? so you can click on a file and it opens in mplayer? Run kappfinder, let it find your mplayer binary and add it to the K menu. In KControl, go to the file associations module, and make sure mplayer is associated with the file formats you want. Move it up to the top to make it the default player (the one that runs when you click on a file), or leave it where it is, and it will be available in the right click - open with menu for any associated file type. No, that never worked for me, at least not in using Konqueror as a web browser when the video is embedded in the web page. They are two very different things. Mplayer is not embeddable by Konqueror. Doesn't stop you right clicking on a link and sending it to mplayer there, using mplayer as a viewer in file manager mode, or, waiting for the libxine things to show up in the ports. Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ msg19807/pgp0.pgp Description: signature
Re: suggested reinstall of KDE when original was from CD-Rom
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 31 January 2003 15:26, Jim Trigg wrote: On Thu, Jan 30, 2003 at 10:22:32PM -0500, Lowell Gilbert wrote: BSD Baby [EMAIL PROTECTED] writes: In this case, does make deinstall work? Or is there a better way? pkg_delete(1) I want to install the new KDE 3.1 from ports in its place. Any advice appreciated. Even better, portupgrade to take care of both parts at once. Unfortunately, neither portupgrade nor a plain make nor a pkg_add work terribly well with a KDE metaport upgrade across version numbers (3.0.x - 3.0.x seems to be ok, 2.2 - 3.0, and 3.0 - 3.1, is not proving too successful for most people). Some of us would very much like the kde metaport to die an unseemly death, however, it *is* a convenient way to install a functional set of KDE packages, so it's unlikely to happen soon. In any case, if you have individual KDE packages installed, portupgrade will more than happily upgrade them. If you have the metaport installed, you likely need to deinstall and reinstall, or for masochists, portupgrade -Rrf will probably work, but will rebuild a whole lot more than just KDE. Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+OpYT/gUyA7PWnacRAqgmAJ4nOCarI6K2x4A9EZFHEctzOQUdkACeOBT1 maIT440wkowaDIQjGJDoUy4= =T2Hu -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: kde+nvidia = crash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 30 January 2003 16:09, Antoine Jacoutot wrote: Hi ! I'm under FreeBSD-4.7-STABLE with the NVidia proprietary binary drivers. I was running KDE 3.05 and I'm now running 3.1 which I though would fix my problem... but no ! Here it is: often when I close Konsole, Kmail... and some other KDE apps, I get a crash. Here is the backtrace: 0x29230cb8 in __sys_poll () from /usr/lib/libc_r.so.4 #0 0x29230cb8 in __sys_poll () from /usr/lib/libc_r.so.4 #1 0x2923019d in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 #2 0x2922fb52 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 #3 0x0 in ?? () Unfortunately, this backtrace is not much use, and the information it contains is mostly rubbish. I looked in the archives and on Google and found that people had similar problem with NVidia+KDE, but they were running 4.7-RELEASE. Is it normal that under 4.7-STABLE, the problem still occurs ? I've been using the NVidia drivers since the day they were released, and I've never seen a KDE crash that could be attributed to them. That's multiple versions of -STABLE and multiple versions of KDE, everything from 3.0.x to KDE CVS.I have seen twice X crash entirely (and in fact, spontaneously reboot the machine) apparently from the nvidia drivers, but in both those cases I was playing movies via the tv-out port, and there was no window manager or desktop environment running at all. Just X, an xterm, and mplayer. If there's a bad interaction with KDE and the nvidia binary drivers, it apparently isn't affecting all nvidia based cards, making it pretty hard to work on unfortunately :(. To try: Does the problem go away entirely if you use the nv drivers? Does the problem go away if you switch to the kde-classic window decoration in KDE? You'll also probably get more input by asking on [EMAIL PROTECTED] Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+OUQr/gUyA7PWnacRAqZqAKCFZd2gHP05JrlsS8TrbutIE3G1KACcC64p rBGJvZcbgK9x+Ka3tUqXLNU= =wIKB -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: kde meta port, how to make a package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 29 January 2003 14:17, Wiroth Didier wrote: Hey, Is that possible? Is there something like: make package in the /usr/ports/kde meta-port, I could execute on my networked PC? There is precisely make package Also, portupgrade's -p switch, which is very nice, and i use it in very similar circumstances to you (in my case, a single nfs server on the network has the ports installed, and packages are kept up to date on it there) The packages are kept in /usr/ports/packages/All/, do check that making a package in the kde metaport does in fact package up each and all the dependencies as well, I know portupgrade does. Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+N9od/gUyA7PWnacRArKXAKCD7tbbNxg2sfbUJWMDZDRmCInNwACgho64 tzEZaxKSzZO92UR3UJAPvm4= =O1Zc -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: KDE 3.1 port?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 29 January 2003 17:40, Andrew Y Ng wrote: I got KDE 3.1 installed and it's absolutely worth the wait! simply amazing! I got the packages from fruitsalad and recompiled kdenetwork and kdegraphics to get mozilla plugins and kamera/gphoto2 support. now I'm compiling kdepim3. i looked into getting s/mime working with gpg in KMail, looks like it's some work just to get the plugin to do s/mime, so i didn't feel like wasting too much time as I use Mutt for my mails most of the time... let me know if there is an easier way to get openpgp s/mime mails without doing all that stuff on the kmail website... :) i dont think kmail came standard with x.509 support either, but both of these are listed as the new features of KDE 3.1. hmm... Some of the team are working on the libs that are needed for s/mime Ägypten support right now, so if you'd like to be our test bunny with it, drop by irc.freenode.net #kde-freebsd later this evening, or if you want, I can mail you later when they are ready to test. Once the support libraries are in ports, it will be a very simple operation to set up. Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+OAk2/gUyA7PWnacRAmi1AJ9jwWaMqVPAJQVqzLkYYLn5l4lZZACfRLQV qxDrkP4xrgQNuSR+IWYx9NI= =s7Jm -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: anyone tried KDE 3.1?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 08 January 2003 22:03, Andrew Y Ng wrote: I'm highly interested in a few new features in KDE 3.1, like tabbed-browsing support in Konqueror, and the new MS Exchange 2000 plugin for the konganizer. if that stuff works well I don't need Linux at work (now I need it for Ximian Connector). I'm wondering if anyone here tried to compile KDE 3.1, maybe somebody from the freebsd KDE team can give us some headsup for their progress? It's ready to go when 3.1 is released. The changelog is already on the KDE website, so there's little point repeating it here :) None of the features listed are known to be in a non-working state on FreeBSD. This time round, we've done extensive testing on -CURRENT as well as Some of the Safari code is already in, more being added almost by the minute. Don't expect to see that in 3.1 though, most of it will probably be in KDE 3.1.1 rather than 3.1 (a month to 6 weeks after a major release, we usually make a bugfix only release, this time there will be a few feature improvements plugged in, notably these.) These are changes made in a very different environment, rushing them in and not testing wouldn't be a great idea, but The Kolab server (Exchange Server replacement) is a standalone, not part of KDE proper, and is definitely high on the list for getting into ports, it is however, still a work in progress, and I personally would prefer to wait until it's not quite such a moving target. It's going to take quite some environment to test it, it's pretty hard to know if a groupware server is working right without setting up a workgroup and using it, so that takes time. The client side groupware stuff is nearly there, sharing calendars is perfect, and I can tell you that the the development versions for 3.2 are supporting imap, and disconnected imap, sieve, ldap, and much more. You can read about all that stuff on KDE's own sites but it's really coming along amazingly nicely if you're in need of groupware stuff. Once KDE 3.1 is out the door, we'll turn the package building cluster back to doing CVS builds, and you're welcome to help test them, drop by the IRC channel or on the mailing list, or keep an eye on our website (in my sig.) Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+Hceg/gUyA7PWnacRAua/AKCHEQRhMfjuoAHtCde48CybZJG1YQCgiFpo Qn08Gl1vMaaav/hXQyQ/N14= =svf2 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: artsd ogle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 21 November 2002 21.14, Peter J. Blok wrote: My question: does artsd need to keep /dev/dsp open all the time? Should ogle be able to open /dev/dsp at the same time and not get an error while opening it? No, you can tell it to exit when idle, arts aware applications will restart it if they want it. More useful, configure arts to not just exit when idle, but to also use a different device than /dev/dsp when it's on. http://freebsd.kde.org/faq.shtml (Question 11, and it's answer) Regards, - -- Lauri Watts -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE93V0A/gUyA7PWnacRAjcmAKCG4RUSUFbE9Ld8M91b3LlmyyHevACfb42d pdwT1Uh8YLKmgZJFNHSUm4Y= =ANPe -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Mail client preferred?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 10 October 2002 09.53, Brian Astill wrote: Pine, Mutt, Elm, Emacs ... probably others. Anyone care to make a recommendation for a console-based mail client? I'm currently using Kmail. It would be nice if there was a way to transfer Kmail message files to the console client. There's nothing really to transfer. KMail writes perfectly normal messages files, in either maildir or mbox format (configurable in it's options.) If you use it's default maildir format, mutt will happily use them without change. If you already had mbox format mail folders, then mutt or pine will use them without configuration. I don't know if pine speaks maildir, I don't use it myself. You might have to link KMail's default ~/Mail to ~/mail You should always take care about using multiple mail clients at the same time on the same mail folders (I mean literally at the same time, with both open.) I've used KMail over imap for ages, and if it's not available, ssh and pine, or webmail (Squirrelmail) if ssh isn't even convenient. One mail folder, multiple clients from multiple locations, no problems. Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE9pT3W/gUyA7PWnacRAo73AJ4jSEUM1vVZoDEmV34+v0HlPKnIRwCfToL2 rwhzZKege/I1iZfatYMxbNk= =9Jz8 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: KDE, sound, artsd and xmms
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 02 October 2002 13.59, Irvine Short wrote: Hey All How do you guys get all the above to play together? I'd like to keep artsd going. At the moment I can get xmms to play by running artsdsp xmms. Is there a neater/better way? There's a plugin for xmms to talk directly to artsd but by all accounts it's old and buggy and not in the ports subsystem. Any suggestions much appreciated. I'm running FreeBSD 4.7RX, KDE 3,03, and XMMS 1.2.7 The sound card is an Ensoniq AudioPCI ESS1371 If you have it (and most modern sound cards can handle this) go into KControl's Sound Server setting, and tell aRts to use a custom device. Point it at /dev/dsp0.1, and let xmms (and any other sound utilities) have /dev/dsp. Do check in /dev/ that the alternate devices are present. If your sound card doesn't support this option, you can in the same KControl module, tell aRts to exit after a certain amount of idle time (0 seconds is never, so set it to something low, like 5 seconds.) All aRts aware applications are able to restart it if they want it. You'll notice a small delay when starting something like Noatun, as it restarts the server, but nothing unreasonable. Regards, - -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9mvwT/gUyA7PWnacRAs4WAJ4uyPHEf4BB10Bl4ZcjduKyM8Wc/QCffzVX +qznD8P7NmcQuNe6XWILijk= =w+gp -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
