Re: Port update hosed entire system
On Tue, 2 Oct 2012 06:20:45 -0400, Rod Person wrote: It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. I find it very hard to see a correlation here. Coincidence? Yes, but I cannot imagine a way a port can dmage the system in that way so not even shell commands keep working... I did discover that my / file system had run out of space -131MB. That could show that some part of important content on / has not been written yet - it's still held in write buffers pending. So you could first check what takes up space in / that is not required to be there, and remove it, then the write buffers will be written properly. A sync command could do this on request. Check with df -h for _no_ negative values before rebooting the system into SUM. I'm not sure if the write buffers can survive a shutdown. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. That sounds that somehow calling programs (executing / forking) is not working properly anymore. As this is one of the most fundamental mechanisms of the systems, it's hard to believe that this can be triggered through a port update... I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. You'd have to find out the exact problem first, maybe the solution is simple. However, how is a ports update supposed to change stuff on /? I assume you have a partitioned system with functional separation, e. g. /, /var, /tmp and /usr (where /usr/local and maybe /usr/home are located). When updating a port, data in /var/db, /usr/ports and /usr/local will be dealt with. Nothing of that should happen on /, or even touch system shells... I assume you have no script of what happened during the port's upgrade? Using script (see man script for details) is a convenient solution if you want to run upgrades while not being able to monitor them constantly. On Tue, 2 Oct 2012 06:12:27 -0400, Rod Person wrote: This is the default shell. I didn't try that yet, because I don't want to be left with no way to login at all if something is really messed up. You have a stand-alone emergency shell in /rescue/sh (which is on the / partition, so it can even be started in single-user mode with / mounted read-only). Since I could not even switch to a no console (ctrl+alt+f2...) and login I'm not really wanting to reboot at this point. From within X, you need Ctrl+Alt+PF2; from text mode, only Alt+PF2 is needed (even though I checked... Ctrl+Alt+ also works in text mode). So you can't even switch VTs? Interesting, makes the problem much more strange... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Port update hosed entire system
On Tue, 2 Oct 2012 09:16:43 +0200 Polytropon free...@edvax.de wrote: On Tue, 2 Oct 2012 06:20:45 -0400, Rod Person wrote: It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. I find it very hard to see a correlation here. Coincidence? Yes, but I cannot imagine a way a port can dmage the system in that way so not even shell commands keep working... I did discover that my / file system had run out of space -131MB. That could show that some part of important content on / has not been written yet - it's still held in write buffers No, the negative free space simply means that you have encroached on to the reserved space (only root can do this) which is usually used to optimise the layout when writing new data. pending. So you could first check what takes up space in / that is not required to be there, and remove it, then the write buffers will be written properly. A sync command could do this on request. Having negative free space will prevent non root users from writing data, but that will be returned to the applications as error returns to write calls not held in write buffers. Check with df -h for _no_ negative values before rebooting the system into SUM. I'm not sure if the write buffers can survive a shutdown. They can't but they're not connected with negative free space reports. A normal shutdown will flush all the buffers. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. That sounds that somehow calling programs (executing / forking) is not working properly anymore. As this is one of the most fundamental mechanisms of the systems, it's hard to believe that this can be triggered through a port update... More likely one of the shared libraries they all use has been overwritten. Updating ports certainly shouldn't be able to do this though. The stuff in /rescue should work fine for getting a usable environment to go bug hunting in, but without a deep and intimate knowledge of how things are supposed to be it's going to be hard short of reinstalling. -- Steve O'Hara-Smith at...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem upgrading misc/help2man: missing language files
I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem upgrading misc/help2man: missing language files
On 10/02/2012 10:59 AM, Thomas Mueller wrote: I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory Hi Tom Isn't this just the creation of the backup package that fails? I encounter errors like this sometimes, but portmaster goed on installing the newer version. tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. Stuck? Or does portmaster continue as it should? How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem upgrading misc/help2man: missing language files
On 10/02/2012 10:59 AM, Thomas Mueller wrote: I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 Below it looks like the creation of the backup package fails, which get's deleted by default after the new port is installed. I Just update ports on a CURRENT server with csup from cvsup4.nl.FreeBSD.org and the help2man version is still 1.40.12 I will go ahead and update from cvsup9.freebsd.org . . . No help2man-1.40.13 yet. Maybe csup the portstree again and retry portmaster misc/help2man? Did portmaster end with lines like Upgrade of help2man-1.40.11 to help2man-1.40.12 But then help2man-1.40.12 to help2man-1.40.13 instead of the above? The it should be OK. ** http://lists.freebsd.org/mailman/listinfo/svn-ports-all tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
sockstat
Hi! I have FreeBSD 9.1-RC1 #0 and I running KDE 4.8.4 too. If I run KDE and try sockstat -l46 I get: sockstat -l46 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS ajtimknemo 35725 10 udp4 *:* *:* root Xorg 33842 1 tcp6 *:6000*:* root Xorg 33842 3 tcp4 *:6000*:* Is it normal root Xorg... I am running Xorg (kde) as user. Thanks in advance. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockstat
On Tue, 2 Oct 2012 05:42:51 -0500 ajtiM lum...@gmail.com wrote: Hi! I have FreeBSD 9.1-RC1 #0 and I running KDE 4.8.4 too. If I run KDE and try sockstat -l46 I get: sockstat -l46 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS ajtimknemo 35725 10 udp4 *:* *:* root Xorg 33842 1 tcp6 *:6000*:* root Xorg 33842 3 tcp4 *:6000*:* Is it normal root Xorg... I am running Xorg (kde) as user. Yes, the X server needs device access not available to normal users so it run setuid root. -- Steve O'Hara-Smith at...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Port update hosed entire system
Just a little update on this, sorry to be unresponsive but my wife had a minor surgery yesterday so I been a little busy, going to try and get back to this today... The reason I was able to get 25GB back is because there was a hidden .trash file that some file manager must of created that had lots of old files in it. The drive is only a 68GB drive that only has one partition, originally I was just testing the uses of gjounal. But somewhere down the line I forgot about this and just keep using it. /home is on a separate drive though. But everything else is on this one drive. /rescue/sh does not segfault. I still have not rebooted the system, making sure any data updated in the last to days is backed up. Then I'll have to bit that bullet. Thanks all for help and suggestions. Rod On Tue, 2 Oct 2012 09:12:09 +0100 Steve O'Hara-Smith at...@sohara.org wrote: On Tue, 2 Oct 2012 09:16:43 +0200 Polytropon free...@edvax.de wrote: On Tue, 2 Oct 2012 06:20:45 -0400, Rod Person wrote: It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. I find it very hard to see a correlation here. Coincidence? Yes, but I cannot imagine a way a port can dmage the system in that way so not even shell commands keep working... I did discover that my / file system had run out of space -131MB. That could show that some part of important content on / has not been written yet - it's still held in write buffers No, the negative free space simply means that you have encroached on to the reserved space (only root can do this) which is usually used to optimise the layout when writing new data. pending. So you could first check what takes up space in / that is not required to be there, and remove it, then the write buffers will be written properly. A sync command could do this on request. Having negative free space will prevent non root users from writing data, but that will be returned to the applications as error returns to write calls not held in write buffers. Check with df -h for _no_ negative values before rebooting the system into SUM. I'm not sure if the write buffers can survive a shutdown. They can't but they're not connected with negative free space reports. A normal shutdown will flush all the buffers. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. That sounds that somehow calling programs (executing / forking) is not working properly anymore. As this is one of the most fundamental mechanisms of the systems, it's hard to believe that this can be triggered through a port update... More likely one of the shared libraries they all use has been overwritten. Updating ports certainly shouldn't be able to do this though. The stuff in /rescue should work fine for getting a usable environment to go bug hunting in, but without a deep and intimate knowledge of how things are supposed to be it's going to be hard short of reinstalling. -- Steve O'Hara-Smith at...@sohara.org -- Rod Person http://www.rodperson.com First we got population. The world today has 6.8 billion people. That's headed up to about 9 billion. Now if we do a really great job on new vaccines, health care, reproductive health services, we lower that by perhaps 10 or 15 percent. - Bill Gates ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: BSD on IOS hardware
On Thu, 27 Sep 2012 10:18:06 -0400 Greg Freeman m...@gefreeman.com wrote: Is it possible to load FreeBSD on an Apple Mobile device designed to run IOS? There are a lot of old iPads out there. If we could repurpose them to straight Unix pads that might be cool. From there shells and then maybe an open source alternative to IOS or Android. Maybe a way for people to get free of the info pirates How do you intend to type on it? -- Rares Aioanei ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
stop and start X server in FreeBSD 9.0
Hello: I configured FreeBSD 9.0 RELEASE with X starting automatically at boot. I use kdm3 login manager, and it works. I would like to make changes to xorg.conf and test the effects. How can I stop X in a terminal temporarily? If I kill kdm it is restarted immediately. In openSUSE I could do this by switchiong runlevels but I learned that FreeBSD has no runlevels. Thanks, Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: stop and start X server in FreeBSD 9.0
On Tue, 02 Oct 2012 15:33:50 +0200, Istvan Gabor wrote: Hello: I configured FreeBSD 9.0 RELEASE with X starting automatically at boot. I use kdm3 login manager, and it works. I would like to make changes to xorg.conf and test the effects. How can I stop X in a terminal temporarily? If I kill kdm it is restarted immediately. For the desired test scenario, I'd suggest to disable KDE (kdm) startup in /etc/rc.conf, and finally stop the related service (from /usr/local/etc/rc.d probably). Then you can easily use the startx command to start an X session from a user's VT, test your settings, terminate the session, and you'll be back in text mode. If you are happy with your settings, re-enable KDE (kdm) by the corresponding /etc/rc.conf entry. In openSUSE I could do this by switchiong runlevels but I learned that FreeBSD has no runlevels. Yes, FreeBSD uses the rc.d mechanism (see man 8 rc for details). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: stop and start X server in FreeBSD 9.0
On Tuesday 02 October 2012 14:49:54 Polytropon wrote: For the desired test scenario, I'd suggest to disable KDE (kdm) startup in /etc/rc.conf, and finally stop the related service (from /usr/local/etc/rc.d probably). Then you can easily use the startx command to start an X session from a user's VT, test your settings, terminate the session, and you'll be back in text mode. The OP is using kdm3 which is normally managed through /etc/ttys instead of an rc script. To stop kdm3: * edit /etc/ttys, find the line 'ttyv8 /usr/local/bin/kdm xterm on secure' and changie on to off * kill -1 1 * killall kdm-bin To restart * edit /etc/ttys and change off back to on for kdm * kill -1 1 But it isn't necessary to do all this just to pick up changes in xorg.conf. Just make your desired changes to xorg.conf, then log out of kde and switch to a console as root and killall kdm-bin. This will stop and start X as well as kdm. You can do all this from a terminal window in your kde session but I prefer to logout cleanly instead of having the rug pulled from under my feet which has sometimes corruptedf my kdmrc file. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: stop and start X server in FreeBSD 9.0
Polytropon, Mike, Thank for your answers. 2012. október 2. 17:29 napon Mike Clarke jmc-freeb...@milibyte.co.uk írta: On Tuesday 02 October 2012 14:49:54 Polytropon wrote: For the desired test scenario, I'd suggest to disable KDE (kdm) startup in /etc/rc.conf, and finally stop the related service (from /usr/local/etc/rc.d probably). Then you can easily use the startx command to start an X session from a user's VT, test your settings, terminate the session, and you'll be back in text mode. The OP is using kdm3 which is normally managed through /etc/ttys instead of an rc script. To stop kdm3: * edit /etc/ttys, find the line 'ttyv8 /usr/local/bin/kdm xterm on secure' and changie on to off I did this one before. I hoped I could make it without editing ttys every time. * kill -1 1 * killall kdm-bin Thanks for pointing out which program has to be killed. To restart * edit /etc/ttys and change off back to on for kdm * kill -1 1 But it isn't necessary to do all this just to pick up changes in xorg.conf. Just make your desired changes to xorg.conf, then log out of kde and switch to a console as root and killall kdm-bin. This will stop and start X as well as kdm. You can do all this from a terminal window in your kde session but I prefer to logout cleanly instead of having the rug pulled from under my feet which has sometimes corruptedf my kdmrc file. I guess this is the way to go. Thanks! Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
nvidia and flash plugin problem
Hello, I have a nvidia GT 630 and use the flash plugin, I've got a very strange problem, on youtube (or any flash video), the colors are just broken. See: 1. http://markand.malikania.fr/1.png 2. http://markand.malikania.fr/2.png On the second picture, the man is supposed to wear a cyan shirt! One thing more, it is *very* *very* strange, if I open a new firefox tab, I can see some bits of the video frame in the new tab! This is happening on a FreeBSD 9.0 amd64 box with linux-f10-flashplugin-11.2r202.238 nvidia-driver-304.51 Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: BSD on IOS hardware
On 02/10/2012 22:58, Rares Aioanei wrote: On Thu, 27 Sep 2012 10:18:06 -0400 Greg Freeman m...@gefreeman.com wrote: Is it possible to load FreeBSD on an Apple Mobile device designed to run IOS? There are a lot of old iPads out there. If we could repurpose them to straight Unix pads that might be cool. From there shells and then maybe an open source alternative to IOS or Android. Maybe a way for people to get free of the info pirates How do you intend to type on it? While apple offers a bluetooth keyboard I have seen docks with a keyboard built in. The other option is that the system will need xorg installed as the minimum setup so you have a touch screen with onscreen keyboard. The ipad/ipod would be a target that netbsd may try - I don't believe they have though. I don't think they support the newer touch screen devices but rockbox is an opensource ipod (and other mp3 players) firmware replacement. It could be a starting point for booting another OS. Having said that I think your best bet would probably be jailbreaking the ipad so you get more control over what you can install. Search for cydia ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: nvidia and flash plugin problem
On 02/10/2012 21:16, David Demelier wrote: Hello, I have a nvidia GT 630 and use the flash plugin, I've got a very strange problem, on youtube (or any flash video), the colors are just broken. See: 1. http://markand.malikania.fr/1.png 2. http://markand.malikania.fr/2.png On the second picture, the man is supposed to wear a cyan shirt! One thing more, it is *very* *very* strange, if I open a new firefox tab, I can see some bits of the video frame in the new tab! This is happening on a FreeBSD 9.0 amd64 box with linux-f10-flashplugin-11.2r202.238 nvidia-driver-304.51 Cheers, After some research, it seems to be a general bug in the adobe flash plugin, to fix it, Right click on a video, click settings and disable hardware acceleration. -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: BSD on IOS hardware
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Shane Ambler Sent: Tuesday, October 02, 2012 3:13 PM To: Rares Aioanei Cc: Greg Freeman; freebsd-questions@FreeBSD.org Subject: Re: BSD on IOS hardware On 02/10/2012 22:58, Rares Aioanei wrote: On Thu, 27 Sep 2012 10:18:06 -0400 Greg Freeman m...@gefreeman.com wrote: Is it possible to load FreeBSD on an Apple Mobile device designed to run IOS? There are a lot of old iPads out there. If we could repurpose them to straight Unix pads that might be cool. From there shells and then maybe an open source alternative to IOS or Android. Maybe a way for people to get free of the info pirates How do you intend to type on it? While apple offers a bluetooth keyboard I have seen docks with a keyboard built in. The other option is that the system will need xorg installed as the minimum setup so you have a touch screen with onscreen keyboard. The ipad/ipod would be a target that netbsd may try - I don't believe they have though. I don't think they support the newer touch screen devices but rockbox is an opensource ipod (and other mp3 players) firmware replacement. It could be a starting point for booting another OS. Having said that I think your best bet would probably be jailbreaking the ipad so you get more control over what you can install. Search for cydia I hate to say it, but wouldn't it be easier to just buy a cheap android tablet in the first place? Some of the ones from china are only a hundred bucks or so but run ICS on a 7 screen. I do like the idea of trying to push BSD to more devices. Would be neat to host a full website from an ipod, but I do agree that would be more the realm of NetBSD, not FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockstat
On Tuesday 02 October 2012 05:50:57 Steve O'Hara-Smith wrote: On Tue, 2 Oct 2012 05:42:51 -0500 ajtiM lum...@gmail.com wrote: Hi! I have FreeBSD 9.1-RC1 #0 and I running KDE 4.8.4 too. If I run KDE and try sockstat -l46 I get: sockstat -l46 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS ajtimknemo 35725 10 udp4 *:* *:* root Xorg 33842 1 tcp6 *:6000*:* root Xorg 33842 3 tcp4 *:6000*:* Is it normal root Xorg... I am running Xorg (kde) as user. Yes, the X server needs device access not available to normal users so it run setuid root. Thank you. I have no in /usr/local/bin/startx clientargs=-nolisten tcp serverargs=-nolisten tcp and is okay. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockstat
On Tue, 2 Oct 2012 16:26:59 -0500 ajtiM lum...@gmail.com wrote: On Tuesday 02 October 2012 05:50:57 Steve O'Hara-Smith wrote: On Tue, 2 Oct 2012 05:42:51 -0500 ajtiM lum...@gmail.com wrote: Hi! I have FreeBSD 9.1-RC1 #0 and I running KDE 4.8.4 too. If I run KDE and try sockstat -l46 I get: sockstat -l46 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS ajtimknemo 35725 10 udp4 *:* *:* root Xorg 33842 1 tcp6 *:6000*:* root Xorg 33842 3 tcp4 *:6000*:* Is it normal root Xorg... I am running Xorg (kde) as user. Yes, the X server needs device access not available to normal users so it run setuid root. Thank you. I have no in /usr/local/bin/startx clientargs=-nolisten tcp You don't need this in clientargs, serverargs is the right place. It should be harmless though, I think. serverargs=-nolisten tcp and is okay. That serverargs should prevent those sockets being used, so no not OK if the sockets are still open. In general though it's best to pass these to startx (perhaps from another script) rather than editing it, your changes will get lost next time startx gets updated. -- Steve O'Hara-Smith at...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockstat
On Tuesday 02 October 2012 17:02:47 Steve O'Hara-Smith wrote: On Tue, 2 Oct 2012 16:26:59 -0500 ajtiM lum...@gmail.com wrote: On Tuesday 02 October 2012 05:50:57 Steve O'Hara-Smith wrote: On Tue, 2 Oct 2012 05:42:51 -0500 ajtiM lum...@gmail.com wrote: Hi! I have FreeBSD 9.1-RC1 #0 and I running KDE 4.8.4 too. If I run KDE and try sockstat -l46 I get: sockstat -l46 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS ajtimknemo 35725 10 udp4 *:* *:* root Xorg 33842 1 tcp6 *:6000*:* root Xorg 33842 3 tcp4 *:6000*:* Is it normal root Xorg... I am running Xorg (kde) as user. Yes, the X server needs device access not available to normal users so it run setuid root. Thank you. I have no in /usr/local/bin/startx clientargs=-nolisten tcp You don't need this in clientargs, serverargs is the right place. It should be harmless though, I think. serverargs=-nolisten tcp and is okay. That serverargs should prevent those sockets being used, so no not OK if the sockets are still open. In general though it's best to pass these to startx (perhaps from another script) rather than editing it, your changes will get lost next time startx gets updated. Done. Thank you. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: A problem with loader
from Zbigniew zbigniew2...@gmail.com : installed recently 9.0 - and I've got a little problem: while booting, loader somehow gets incorrect currdevice value, stopping boot process. It does get disk1s6a, but it should be disk1s7a. I can boot system, when I set currdev manually, then type boot. But how can I change it for steady, avoiding this typing each time? Of course, loader won't read its config files, when not having access to root directory. How can I pass the proper value to loader immediately? Maybe the fact, that I'm booting FreeBSD using GRUB, can be of any help? -- regards, Zbigniew Which GRUB are you using, legacy (0.97) or GRUB2? Are you sure you specify the partition correctly in GRUB? Partition numbering starts from 0 in GRUB legacy but from 1 in GRUB2. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
