Search results

Contributing can be pretty tiring, months or even years can pass till a patch gets committed if no committer is currently involved with the affected code.

Does anyone know about any progress lately? I'm talking about suspend/resume, which is way more important to me than fast booting.

The -f will cause portupgrade to reinstall everything, even what is already up to date.

It does. Login.conf settings apply everywhere. Of course with such a broken login.conf it's no wonder things don't work. The following lines are obsolete: lang=fr_FR.ISO8859-15:\ lc_all=fr_FR.ISO8859-15:\ lc_collate=fr_FR.ISO8859-15:\ lc_cty pe=fr_FR.ISO8859-15:\...

To my luck I did the update before the instructions were added to /usr/ports/UPDATING. So I applied my default update strategy: portmaster -Da pkg_libchk -qo | xargs -o portmaster -D Everything was built fine, but X didn't start any more, so I read my Xorg.0.log file, removed the offending...

I use portmaster with pkg_libchk.

Well, I sure don't.

I used to be in the habit of using splash screens, but honestly. i386 only? As long as this is not addressed there is no real need for them in my opinion.

XDM runs as a terminal session and thus obeys the login.conf settings. If you start your DM from /etc/ttys, it should work.

Yes, you get a free membership in the No Life Club.

So do I on amd64.

Just reduce your wpa_supplicant.conf to the minimum. Get rid of the lines scan_ssid=1, proto=RSN, pairwise=CCMP TKIP, key_mgmt=WPA-PSK. That might work, or not. With wpa_supplicant you can never be sure. Also, I recommend you the [code]-Block.

I'm perfectly happy with the way eclipse runs on FreeBSD and have quite a number of plugins installed as well (through the FreeBSD Ports). So I'm slightly mystified about the nature of your problems, which you haven't specified unfortunately, so this will remain a meta discussion and it is...

You can set the time with the date command. You can also run ntpd to automatically sync your time with a time server.

I don't see is how it's possible to execute the files. This is an application problem, you cannot do anything on the OS side of things.

Just set TARGET=amd64. This should do it. About the Ports, yes you can. However you should set WRKDIRPREFIX to somewhere outside the ports on these systems, so that you only require read access.

Better change that back. Anyway, did you try clearing your ~/.mozilla/firefox directory?

I use inetd to run the fingerd.

Your system needs a serious security hole for someone to be able to remotely execute the scripts in these files. Unless there is some kind of stack or buffer overflow exploit for your software, it won't do anything. What you can do is to use some image processing library and deny everything that...

How did you try to start it? Ever ran a terminal and started it from there?