Re: Performance and mouse problems
Le 02/05/2012 ? 22:44:19+0200, Jerome Herman a écrit Hi. Ok here is what happens, In your system you have your touchpad declared both in a static way in your xorg config, and probed by HAL. What happens is that when xorg starts it first install the touchpad as required by the config file, and then tries to install it again via autodetection. Of course the second installation of the same device doesn't work as the device is already busy with xorg, and xorg stops to try to auto-install devices. When you plug another mouse, xorg is notified that there are new devices, but starts by trying to reinstall the touchpad, fails again for the same reason as above and stops trying. OK. In order to solve your problem you can try the following : a) remove the touchpad lines from your xorg config. This way the touchpad should be installed by auto detection. (simply comment it as you might be needing it back soon) I've no idea how I can do that. Here my xorg.conf (without font/driver for graphics etc..): Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 # InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Module Load extmod Load record Load dbe Load glx Load dri Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection I've try to comment out Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 without any result. b) forbid hal from probing the touchpad. If solution a fails, I would explain to you how to do this if solution a) fails. Any solution ;-) Thanks again. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: jeu 3 mai 2012 09:27:51 CEST ___ 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: Performance and mouse problems
Le 02/05/2012 ? 10:27:56-0600, Warren Block a écrit On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. Sorry. I forget to thanks you the first time you answer me. But just after you send the message, I already try that, without any result. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: jeu 3 mai 2012 09:32:16 CEST ___ 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
newbie- install to i-mac from usb
hi, I hope this is the correct mailing list for this question. I am a newbie. I want to install FreeBSD 9.0 to an i-mac g3/g4 which doesn't have a working cd drive. I want to use a usb stick to do this. My question is what relevant doc explains how to do this? I searched google and could not find an answer that worked, even for NetBSD. I tried issuing a dd command to cp the powerpc memstick image to usb, but I can't figure out how to get openfirmware to boot the usb. It is openfirmware version 3. I welcome any help and/or suggestions. Thanks, ___ 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: UFS Crash and directories now missing
On Mon, Apr 30, 2012 at 6:42 PM, Jerome Herman jher...@dichotomia.fr wrote: [...] I must admit that Robert Bonomi tone was highly insulting for this list, and though I completely condemn the form of his post, I cannot say I disagree with the content. I disagree with both the form and the content and I will tell you why later... I do appreciate however the time you and everyone else (including Robert Bonomi's), have taken to answer and post such lengthy insights. I believe everyone's opinion is important and should be respected. There are quite a lot of things that are wrong with Alejandro Imass' post and analysis. The fist thing is that he did not give is setup in one go. It took quite a while to figure what happened, what system he was using and how he was using it. At first he had to hard reboot an unresponsive system, then at reboot he would have lost all of his jail. Then it appeared that all the jails where inside another jail and that the unresponsiveness came from MySQL. Then we learn that all his daemons are inside jails. Then we learn that ftp-proxy is not. Then we learned that jail are not handled manually but through EZJail. Then we are told that the problem with MySQL is known and comes from a client using TigerCRM with a too much data. There are litterally dozens of little pieces of important knowledge all over the thread. And you have to read it all to make sure you have the global view. Not really a good start. It is OK to forget to mention a thing or two, discarding what you think is irrelevant to the problem at hand, but it is not OK to force people who are trying to help you to read 50+ posts to learn about the basics of your installation. Granted. Nevertheless, the EzJail part (which I admit was a very important piece of information) was left out my first and second post was in fact established in the third post, so it was quite early in the thread. I think that it is not hard to put yourself in my shoes, and understand that in a moment of crisis, your first priority is NOT articulating the most complete and technical bug report you can. On the contrary, it's a cry for help from your peer users to see if you can gain some insight on solving the problem as quickly as possible. What is even more irritating is the fact that Alejandro Imass ignores pretty much anything that would leads toward a human mistake. Most posts implying a possible bad use of jails/nullfs/ezjail are ignored or answered by a simple I have done everything by the book. Now from my experience someone with 6 servers, each containing multiple jails will not do everything by the book every time. It might be that Alejandro is exceptional, but it is more likely Well, we do run everything by the book, precisely to avoid problems. We find one recipe that works and stick to it like religion. I have only used EzJail commands and **normal** use of EzJail. I am not expected to know _extactly_ how it works, I trust that to the experts in each field. As a user I am only expected to RTFM, and use it accordingly. Again let me remind everyone here, this list is precisely for that: FreeBSD ***GENERAL QUESTIONS***. It is NOT a technical list. When you and Robert Bonobi and everyone elese here subscribed to this particular list, it should have been pretty clear: - General lists: The following are general lists which anyone is free (and encouraged) to join: - freebsd-questions: User questions and technical support - About freebsd-questions English (USA) :This is the mailing list for questions about FreeBSD. You should not send how to questions to the technical lists unless you consider the question to be pretty technical. So I am entitled to post general questions and provide information as I see it fit, or if an expert on the list may ask for more. When I posted the first few posts, that's all the information I had, if you thought you needed more information, then you should have said so, but instead your personal guess is a priori judgment call, which I found almost as insulting as all of Bonobi's posts and I simply ignored you. In retrospective, and after re-reading you first post and this one, I can understand that having left EzJail out in the first post was a key piece of information that would have probably caused you to answer very differently, so I can somewhat justify your initial post, but to me at that moment, you should have already known I was using EzJail. that at least one if not more of these jails were not made by the book. Nothing to blame anyone in here, we all get tired/bored/overconfident sometime - but refusing to admit the very possibility of a human mistake won't help at all in finding a solution. Reading the thread I realized that my suggestion that he might have over-used ln had been discarded as stupid, but the information came a lot later in answer to another post. Of Yes, I must apologize for having ignored your post, but I found your a priori *assumption* of
Re: UFS Crash and directories now missing
Alejandro Imass a...@p2ee.org wrote: [ megasnip ] Things to investigate : - When was the last time this box was rebooted normally ? Did it went fine ? After I moved the jails to the right place I archived the jails with ezjail-admin and rebooted the server several times, and everything worked as expected. Rephrasing -- when was the last time _before_the_problem_was_discovered_ that the machine was re-booted? Were the jails created at this time ? No. Most of these jails have been operational for over a year on this server without any incidents. Clarifying the question -- were the jails created at the time of the last _prior_ reboot? i.e., had the machine been re-booted successfully _after_ the jails were installed, or was this the _first_ such reboot? It appears you misunderstood the 'at this time' reference -- it did ot mean 'at the time of the incident', but 'at the time of the last prior reboot'. If English is not your primary language, it is an understandable misread. As I told you earlier, this server has been running for over a year and we have rebooted many times. I don't believe you ever mentioed that particular point (multiple successful reboots after istallation) before. Repeating a prior question, _how_long_ before the problem showed up was the most recent re-boot? (Doesn't have to be exact -- an 'order of magnitude' estimate [a day, a week, a month, several months] is sufficient.) If there are such problems they exist by using the EzJail commands and I find this unlikely. What you 'find unlikely' is irrelevant. The entire situation is 'unlikely', yet it happened. So one -has- to look at unlikely things. wry grin here is the mount output is that's of any help: [ first disk, and 'fdescfs', and 'procfs' references removed, for clarity ] /dev/ad6s1.journal on /usr/jails (ufs, asynchronous, local, gjournal) /usr/jails/basejail on /usr/jails/yabarana-php53/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/yabarana-php52/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/yabarana-cat58/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/testbed/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/pyugmao/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/php53base/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/php52base/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/mcs-cat58/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/http-proxy/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/corcaribe-php53/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/cm-website/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/cm-idvida/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/cat58base/basejail (nullfs, local, read-only) /usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local, read-only) Yes, that is a good start at useful detail. It is, presumably, _after_ the problem, and _after_ you had restored things to their proper places. Is it safe to assume that you do -not- have such a 'mount' output from some time 'before' the problem? ( There's no rational reason why you -would- have such, but _if_ it existed, and there were any differences between 'then' and 'now', it could be very informative.) Aother critical piece of information is what diretories -- by full path name -- disappeared from 'where they were', and where -- by full path name, again -- did you find them, and _with_what_names_? If everything was moved from the same source point to the same destination, it's not necessary to itemize each one, but the details of _one_ 'typicaal' migration is needed. It is also significant if there was 'anything else' in the 'where they belonged' directory that was -not- moved. *OR* if there was anything else (something other than the '/' of a jail) there, that was _also_ moved. Narrative descriptions, as previously provided, and while clear to someone familiar with the machcine in question, are not sufficiently precise to allow an 'outsider' to follow the events without 'logically' replicating the setup, and then guessing at the meaning of any shorthands employed. One comment: for 'defensive' purposes it would be useful to break ad6 up into two slices, putting 'basejail' in it's own slice. Then, for production use, that slice can be mounted RO, and with the 'system immutable' flag set on everything in that filesystem. ___ 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: Performance and mouse problems
On Thu, 3 May 2012, Albert Shih wrote: Le 02/05/2012 ? 10:27:56-0600, Warren Block a écrit On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. Sorry. I forget to thanks you the first time you answer me. But just after you send the message, I already try that, without any result. Different hardware, possibly. For completeness, this machine has dbus running, hal is not installed, moused_enable=YES is in /etc/rc.conf, and it requires a restart. Probably the touchpad on this system is USB internally, and a normal moused can't be started after devd starts a nondefault moused. xorg.conf has no InputDevice entries at all. The scroll wheel and middle click buttons work.___ 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: Unresolvable links
On Fri, 27 Apr 2012 21:59:08 + (UTC) Walter Hurry walterhu...@gmail.com wrote: Arising from a very useful link posted by Warren Block in another thread: http://forums.freebsd.org/showpost.php?p=163415postcount=17 , I have been running libchk. It now gives the following (relevant) output: Unresolvable link(s) found in: /usr/local/lib/libreoffice/program/ configmgr.uno.so libxmlreader.so Unresolvable link(s) found in: /usr/local/lib/firefox/sdk/lib/libxul.so libmozsqlite3.so Unresolvable link(s) found in: /usr/local/lib/firefox/components/ libmozgnome.so libmozalloc.so libxpcom.so Unresolvable link(s) found in: /usr/local/lib/firefox/components/ libdbusservice.so libmozalloc.so libxpcom.so Unresolvable link(s) found in: /usr/local/lib/firefox/components/ libbrowsercomps.so libmozalloc.so libxul.so libxpcom.so All these shared object files are present in one lib or another, so my suspicion is that somehow the 'parent' shared objects are looking for them in the wrong place. Any ideas on fixing this please? Unresolved symbol warning are normal for the mozilla stuff, since they use their own non-standard library paths. Just disregard them. -- Conrad J. Sabatier conr...@cox.net ___ 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: UFS Crash and directories now missing
Alejandro Imass ait at p2ee.org writes: ... devfs on /usr/jails/cmm-php52-1/dev (devfs, local, multilabel) ... /usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local, read-only) fdescfs on /usr/jails/cmm-php52-1/dev/fd (fdescfs) procfs on /usr/jails/cmm-php52-1/proc (procfs, local) There is one thing that looks like an anomaly. For each jail, should the master template basejail be mounted into it first, followed by /dev and anything else in there ? /usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local, read-only) devfs on /usr/jails/cmm-php52-1/dev (devfs, local, multilabel) fdescfs on /usr/jails/cmm-php52-1/dev/fd (fdescfs) procfs on /usr/jails/cmm-php52-1/proc (procfs, local) Does it matter ? jb ___ 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: Performance and mouse problems
Can you disable the touchpad? In my laptop (Asus K5) if i press Fn+F9 the touchpad is disabled via ACPI and not detected by HAL nor Xorg. ___ 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
Adding a Static Route to rc.conf?
On Tue, May 1, 2012 at 8:31 AM, Chris Maness chris at chrismaness.com wrote: How do add a static route to rc.conf? Thanks, Chris Maness http://www.freebsd.org/doc/handbook/network-routing.html see section 32.2.5.2 Persistent Configuration -- Noel Jones I added: # Add Internal Net 2 as a static route static_routes=internalnet2 route_internalnet2=-net 44.18.44.0/24 192.168.1.33 to rc.conf per the section above. I rebooted and it was a no go. Did I miss something? Thanks, Chris Maness ___ 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
Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
The following message appears when I do freebsd-update install The following files will be added as part of updating to 8.2-RELEASE-p7: /usr/src/lib/libc/gen/libc_dlopen.c The following files will be updated as part of updating to 8.2-RELEASE-p7: /boot/kernel/kernel /lib/libcrypto.so.6 /usr/bin/openssl /usr/include/openssl/ssl.h /usr/include/openssl/ssl3.h /usr/lib/libcrypto.a /usr/lib/libssl.a /usr/lib/libssl.so.6 /usr/lib32/libcrypto.a /usr/lib32/libcrypto.so.6 /usr/lib32/libcrypto_p.a /usr/lib32/libssl.a /usr/lib32/libssl.so.6 /usr/lib32/libssl_p.a /usr/src/sys/conf/newvers.sh /var/db/mergemaster.mtree WARNING: FreeBSD 8.2-RELEASE-p6 is approaching its End-of-Life date. It is strongly recommended that you upgrade to a newer release within the next 2 months. root@bljbsd01~:freebsd-update install Installing updates...install: ///usr/src/lib/libc/gen/libc_dlopen.c: No such file or directory done. Should I worry about the libc_dlopen.c, or is it ok? Thanks /Leslie ___ 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: UFS Crash and directories now missing
On Thu, May 3, 2012 at 9:35 AM, Robert Bonomi bon...@mail.r-bonomi.com wrote: Alejandro Imass a...@p2ee.org wrote: [ megasnip ] Things to investigate : - When was the last time this box was rebooted normally ? Did it went fine ? After I moved the jails to the right place I archived the jails with ezjail-admin and rebooted the server several times, and everything worked as expected. Rephrasing -- when was the last time _before_the_problem_was_discovered_ that the machine was re-booted? The jails moved Friday 27th so the last reboot before that was Apr 4 and before Feb 29 Feb 29 10:18:46 nune reboot: rebooted by aimass Apr 4 19:45:03 nune reboot: rebooted by aimass Apr 27 19:47:06 nune reboot: rebooted by aimass Apr 28 02:03:57 nune reboot: rebooted by aimass Were the jails created at this time ? No. Most of these jails have been operational for over a year on this server without any incidents. Clarifying the question -- were the jails created at the time of the last _prior_ reboot? i.e., had the machine been re-booted successfully _after_ the jails were installed, or was this the _first_ such reboot? No not at all. Most of these jails were created last year, but here is the detail. cmm_php52_1 is the problematic jail with the MySQL, you will see a recent date in the config file because I recently added some cpuset as a band-aid to limit the jail's ability to bring down the whole system, leaving at least a couple of CPUs free to be able to ssh and shut it down. There is however a new jail corcaribe_php53 and was the reason we rebboted the server on Apr 4th, just to make sure that eveything would boot OK after reboot. -rw-r--r-- 1 root wheel 917 Feb 16 2011 cat58base -rw-r--r-- 1 root wheel 917 Apr 29 2011 cm_idvida -rw-r--r-- 1 root wheel 937 Apr 3 2011 cm_website -rw-r--r-- 1 root wheel 960 May 2 09:48 cmm_php52_1 -rw-r--r-- 1 root wheel 1037 Apr 4 20:00 corcaribe_php53 -rw-r--r-- 1 root wheel 950 Feb 16 2011 http_proxy -rw-r--r-- 1 root wheel 917 Aug 3 2011 mcs_cat58 -rw-r--r-- 1 root wheel 917 Feb 10 2011 php52base -rw-r--r-- 1 root wheel 917 Feb 12 2011 php53base -rw-r--r-- 1 root wheel 877 Dec 27 20:33 pyugmao -rw-r--r-- 1 root wheel 877 Mar 21 22:03 testbed -rw-r--r-- 1 root wheel 1017 May 13 2011 yabarana_cat58 -rw-r--r-- 1 root wheel 1017 Feb 13 2011 yabarana_php52 -rw-r--r-- 1 root wheel 1017 Feb 13 2011 yabarana_php53 It appears you misunderstood the 'at this time' reference -- it did ot mean 'at the time of the incident', but 'at the time of the last prior reboot'. If English is not your primary language, it is an understandable misread. As I told you earlier, this server has been running for over a year and we have rebooted many times. I don't believe you ever mentioed that particular point (multiple successful reboots after istallation) before. Repeating a prior question, _how_long_ before the problem showed up was the most recent re-boot? (Doesn't have to be exact -- an 'order of magnitude' estimate [a day, a week, a month, several months] is sufficient.) Apr 4th If there are such problems they exist by using the EzJail commands and I find this unlikely. What you 'find unlikely' is irrelevant. The entire situation is 'unlikely', yet it happened. So one -has- to look at unlikely things. wry grin funny here is the mount output is that's of any help: [ first disk, and 'fdescfs', and 'procfs' references removed, for clarity ] /dev/ad6s1.journal on /usr/jails (ufs, asynchronous, local, gjournal) /usr/jails/basejail on /usr/jails/yabarana-php53/basejail (nullfs, [...] Yes, that is a good start at useful detail. It is, presumably, _after_ the problem, and _after_ you had restored things to their proper places. Yes. Is it safe to assume that you do -not- have such a 'mount' output from some time 'before' the problem? ( There's no rational reason why you -would- have such, but _if_ it existed, and there were any differences between 'then' and 'now', it could be very informative.) No, but from what I remember it's mostly very similar. I can pull off similar mount statement from other server(s) where we run similar set-ups and that have never failed if needed. Aother critical piece of information is what diretories -- by full path name -- disappeared from 'where they were', and where -- by full path name, again -- did you find them, and _with_what_names_? If everything was moved from the same source point to the same destination, it's not necessary to itemize each one, but the details of _one_ 'typicaal' migration is needed. It is also significant if there was 'anything else' in the 'where they belonged' directory that was -not- moved. *OR* if there was anything else (something other than the '/' of a jail) there, that was _also_ moved. I took a screen shot because I somehow suspected no one would
Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
2012-05-03 19:04, Leslie Jensen skrev: The following message appears when I do freebsd-update install The following files will be added as part of updating to 8.2-RELEASE-p7: /usr/src/lib/libc/gen/libc_dlopen.c The following files will be updated as part of updating to 8.2-RELEASE-p7: /boot/kernel/kernel /lib/libcrypto.so.6 /usr/bin/openssl /usr/include/openssl/ssl.h /usr/include/openssl/ssl3.h /usr/lib/libcrypto.a /usr/lib/libssl.a /usr/lib/libssl.so.6 /usr/lib32/libcrypto.a /usr/lib32/libcrypto.so.6 /usr/lib32/libcrypto_p.a /usr/lib32/libssl.a /usr/lib32/libssl.so.6 /usr/lib32/libssl_p.a /usr/src/sys/conf/newvers.sh /var/db/mergemaster.mtree WARNING: FreeBSD 8.2-RELEASE-p6 is approaching its End-of-Life date. It is strongly recommended that you upgrade to a newer release within the next 2 months. root@bljbsd01~:freebsd-update install Installing updates...install: ///usr/src/lib/libc/gen/libc_dlopen.c: No such file or directory done. Should I worry about the libc_dlopen.c, or is it ok? Thanks /Leslie ___ 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 After a reboot my system now has the following label FreeBSD 8.2-RELEASE-p3 #0 How come it downgrades the label from p6 to p3 when upgrading to p7. I'm aware that I can rebuild the kernel but I just wanted to know. /Leslie ___ 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: UFS Crash and directories now missing
On Thu, May 3, 2012 at 12:05 PM, jb jb.1234a...@gmail.com wrote: Alejandro Imass ait at p2ee.org writes: ... devfs on /usr/jails/cmm-php52-1/dev (devfs, local, multilabel) ... /usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local, read-only) fdescfs on /usr/jails/cmm-php52-1/dev/fd (fdescfs) procfs on /usr/jails/cmm-php52-1/proc (procfs, local) There is one thing that looks like an anomaly. For each jail, should the master template basejail be mounted into it first, followed by /dev and anything else in there ? /usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local, read-only) devfs on /usr/jails/cmm-php52-1/dev (devfs, local, multilabel) fdescfs on /usr/jails/cmm-php52-1/dev/fd (fdescfs) procfs on /usr/jails/cmm-php52-1/proc (procfs, local) Does it matter ? I have no idea, but cmm-php52-1 is in fact the problematic jail with the MySQL problem. ___ 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: UFS Crash and directories now missing
Alejandro Imass ait at p2ee.org writes: ... I have no idea, but cmm-php52-1 is in fact the problematic jail with the MySQL problem. Could you please include displays of 1. your troubled machine's $ cat /etc/fstab Note: you already showed us 'mount' output. 2. your other trouble-free server's $ cat /etc/fstab $ mount jb ___ 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: Adding a Static Route to rc.conf?
On 5/3/2012 11:45 AM, Chris Maness wrote: On Tue, May 1, 2012 at 8:31 AM, Chris Maness chris at chrismaness.com wrote: How do add a static route to rc.conf? Thanks, Chris Maness http://www.freebsd.org/doc/handbook/network-routing.html see section 32.2.5.2 Persistent Configuration -- Noel Jones I added: # Add Internal Net 2 as a static route static_routes=internalnet2 route_internalnet2=-net 44.18.44.0/24 192.168.1.33 to rc.conf per the section above. I rebooted and it was a no go. Did I miss something? Looks OK, and works for me. Wild guess is you need to enable netwait in rc.conf http://www.freebsd.org/cgi/man.cgi?query=rc.confsektion=5 (near the bottom) -- Noel Jones ___ 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: UFS Crash and directories now missing
On Thu, May 3, 2012 at 1:40 PM, jb jb.1234a...@gmail.com wrote: Alejandro Imass ait at p2ee.org writes: ... I have no idea, but cmm-php52-1 is in fact the problematic jail with the MySQL problem. Could you please include displays of 1. your troubled machine's $ cat /etc/fstab Note: you already showed us 'mount' output. 2. your other trouble-free server's $ cat /etc/fstab $ mount The fstab was in a previous mail but here it is again... From the troubled server: # DeviceMountpoint FStype Options DumpPass# /dev/ad4s1b noneswapsw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s1d /tmpufs rw 2 2 /dev/ad4s1f /usrufs rw 2 2 /dev/ad4s1e /varufs rw 2 2 /dev/ad6s1.journal /usr/jails ufs rw,async2 2 /dev/cd0/cdrom cd9660 ro,noauto 0 0 From a good server (single disk machine): /dev/ad4s1b noneswapsw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s1d /tmpufs rw 2 2 /dev/ad4s1f.journal /usrufs rw,async 2 2 /dev/ad4s1e /varufs rw 2 2 /dev/ad4s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/ad4s1d on /tmp (ufs, local, soft-updates) /dev/ad4s1f.journal on /usr (ufs, asynchronous, local, gjournal) /dev/ad4s1e on /var (ufs, local, soft-updates) /usr/jails/basejail on /usr/jails/httpProxy/basejail (nullfs, local, read-only) devfs on /usr/jails/httpProxy/dev (devfs, local, multilabel) fdescfs on /usr/jails/httpProxy/dev/fd (fdescfs) procfs on /usr/jails/httpProxy/proc (procfs, local) /usr/jails/basejail on /usr/jails/cat58base/basejail (nullfs, local, read-only) devfs on /usr/jails/cat58base/dev (devfs, local, multilabel) fdescfs on /usr/jails/cat58base/dev/fd (fdescfs) procfs on /usr/jails/cat58base/proc (procfs, local) /usr/jails/basejail on /usr/jails/watwkyTesting/basejail (nullfs, local, read-only) devfs on /usr/jails/watwkyTesting/dev (devfs, local, multilabel) fdescfs on /usr/jails/watwkyTesting/dev/fd (fdescfs) procfs on /usr/jails/watwkyTesting/proc (procfs, local) /usr/jails/basejail on /usr/jails/mta1/basejail (nullfs, local, read-only) devfs on /usr/jails/mta1/dev (devfs, local, multilabel) fdescfs on /usr/jails/mta1/dev/fd (fdescfs) procfs on /usr/jails/mta1/proc (procfs, local) /usr/jails/basejail on /usr/jails/migdev/basejail (nullfs, local, read-only) devfs on /usr/jails/migdev/dev (devfs, local, multilabel) fdescfs on /usr/jails/migdev/dev/fd (fdescfs) procfs on /usr/jails/migdev/proc (procfs, local) jb ___ 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 ___ 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: Adding a Static Route to rc.conf?
# Add Internal Net 2 as a static route static_routes=internalnet2 route_internalnet2=-net 44.18.44.0/24 192.168.1.33 to rc.conf per the section above. I rebooted and it was a no go. Did I miss something? Looks OK, and works for me. Wild guess is you need to enable netwait in rc.conf http://www.freebsd.org/cgi/man.cgi?query=rc.confsektion=5 (near the bottom) -- Noel Jones I will check that option out. I don't reboot that often, but when I do, I always forget to go back in and add my static routes. Thanks, Chris Maness ___ 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: UFS Crash and directories now missing
Alejandro Imass ait at p2ee.org writes: ... OK. There is this anomaly in your troubled jail. Because I have not been familiar with ezjail so I am learning it now as we go. I will suggest to you some steps by intuition, and you have to judge for both of us how to do it and what's appropriate. Feel free to give feedback anytime. I understand that this troubled jail can be stopped any time without any problems to your clients. Just in case do a backup of it with ezjail admin entry. Use ezjail admin entries by the way (no 'mv', 'cp', etc). I look at an ezjail tutorial right now and see the following: ezjail Default File Locations /usr/jails/ : Default location to store base jail system template. /usr/jails/flavours/ : Customization for each jail can be done via flavours. For e.g. adding default /etc/resolv.conf file or updating existing /etc/make.conf can be done here. /usr/jails/basejail/ : Base jail will be exported and mounted as read only for each jail. This will save disk space. /usr/local/etc/rc.d/ezjail.sh : Stop / Start / Restart jails script. /usr/local/etc/ezjail.conf : Configuration file for ezjail script. contains settings that control the operation of the ezjail rc script. It is also read by the ezjail-admin utility to figure out where it should perform its actions. /usr/local/etc/ezjail/ : All your jail configuration files are stored here. Now, your task is to figure out where your mounts are configured for that jail, those that are present in the 'mount' output. After that you would stop that jail and delete it (assuming no problem to your customer service) to get rid of those lines in mount output. The reconfigure that jail properly anew (do not use backup for this !) and create it again, check the 'mount' output to see proper sequence of mounts. Then restart the jail and see how it goes. Give us feedback as you go so we can follow you. jb ___ 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: Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
On Thu 2012-05-03 19:17:05 UTC+0200, Leslie Jensen (les...@eskk.nu) wrote: After a reboot my system now has the following label FreeBSD 8.2-RELEASE-p3 #0 How come it downgrades the label from p6 to p3 when upgrading to p7. This is a FAQ. There's a thread about it here: http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217031.html Short answer: The patch level (-p3) displayed by uname -r after a reboot will not change if freebsd-update has not touched the kernel. As far as I know there haven't been any patches to the 8.2-REL kernel since -p3. /usr/src/sys/conf/newvers.sh is always updated by freebsd-update when there is an update. (Although now that I think about it that might not be true if you don't have the kernel sources installed?) Not exactly intuitive. Several Linux distros have a file named /etc/issue that shows the distro name and version. Perhaps this or something similar could be provided in future FreeBSD releases and updated by freebsd-update. $ cat /etc/issue Ubuntu 12.04 LTS \n \l Regards Andrew ___ 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: Adding a Static Route to rc.conf?
On 5/3/2012 1:08 PM, Michael Sierchio wrote: On Thu, May 3, 2012 at 10:34 AM, Noel noeld...@gmail.com mailto:noeld...@gmail.com wrote: On 5/3/2012 11:45 AM, Chris Maness wrote: On Tue, May 1, 2012 at 8:31 AM, Chris Maness chris at chrismaness.com http://chrismaness.com wrote: How do add a static route to rc.conf? Thanks, Chris Maness http://www.freebsd.org/doc/handbook/network-routing.html see section 32.2.5.2 Persistent Configuration -- Noel Jones I added: # Add Internal Net 2 as a static route static_routes=internalnet2 route_internalnet2=-net 44.18.44.0/24 http://44.18.44.0/24 192.168.1.33 to rc.conf per the section above. I rebooted and it was a no go. Did I miss something? Looks OK, and works for me. Wild guess is you need to enable netwait in rc.conf http://www.freebsd.org/cgi/man.cgi?query=rc.confsektion=5 http://www.freebsd.org/cgi/man.cgi?query=rc.confsektion=5 (near the bottom) This is 9.X-specific advice, and this option doesn't exist in 8- or prior. Indeed, I should have mentioned that if you have freebsd-8x or earlier, this feature isn't built-in but can be easily added: http://freebsd.1045724.n5.nabble.com/Re-rc-8-script-waiting-for-the-network-to-become-usable-td4242157.html Or the earlier discussion: http://lists.freebsd.org/pipermail/freebsd-stable/2010-April/056521.html -- Noel Jones ___ 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: Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
2012-05-03 20:35, andrew clarke skrev: On Thu 2012-05-03 19:17:05 UTC+0200, Leslie Jensen (les...@eskk.nu) wrote: After a reboot my system now has the following label FreeBSD 8.2-RELEASE-p3 #0 How come it downgrades the label from p6 to p3 when upgrading to p7. This is a FAQ. There's a thread about it here: http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217031.html Short answer: The patch level (-p3) displayed by uname -r after a reboot will not change if freebsd-update has not touched the kernel. As far as I know there haven't been any patches to the 8.2-REL kernel since -p3. /usr/src/sys/conf/newvers.sh is always updated by freebsd-update when there is an update. (Although now that I think about it that might not be true if you don't have the kernel sources installed?) Not exactly intuitive. Several Linux distros have a file named /etc/issue that shows the distro name and version. Perhaps this or something similar could be provided in future FreeBSD releases and updated by freebsd-update. $ cat /etc/issue Ubuntu 12.04 LTS \n \l Regards Andrew ___ 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 Thank you :-) I have read similar answers and was partly aware of this. But I was just curious to why. I'll accept it and let a kernel rebuild be a part of my updates. /Leslie ___ 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: Adding a Static Route to rc.conf?
On Thu, May 3, 2012 at 11:17 AM, Noel noeld...@gmail.com wrote: Indeed, I should have mentioned that if you have freebsd-8x or earlier, this feature isn't built-in but can be easily added: http://freebsd.1045724.n5.nabble.com/Re-rc-8-script-waiting-for-the-network-to-become-usable-td4242157.html Or the earlier discussion: http://lists.freebsd.org/pipermail/freebsd-stable/2010-April/056521.html The link to the script in this thread is dead. ___ 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: Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
On Thu 2012-05-03 20:48:17 UTC+0200, Leslie Jensen (les...@eskk.nu) wrote: Short answer: The patch level (-p3) displayed by uname -r after a reboot will not change if freebsd-update has not touched the kernel. ... I have read similar answers and was partly aware of this. But I was just curious to why. I'll accept it and let a kernel rebuild be a part of my updates. If you're running the GENERIC kernel then you're only creating extra work for yourself by rebuilding it for the sole purpose of having uname -r show the correct patchlevel... On the other hand if you're running a custom kernel then you only need to rebuild the kernel when freebsd-update touches the kernel sources. I don't recall the kernel was touched at all with the most recently -p7 patch (openssl), for example, so there's absolutely no need to rebuild it. Apologies if this was already obvious. Regards Andrew ___ 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: Adding a Static Route to rc.conf?
On 5/3/2012 1:54 PM, Michael Sierchio wrote: On Thu, May 3, 2012 at 11:17 AM, Noel noeld...@gmail.com mailto:noeld...@gmail.com wrote: Indeed, I should have mentioned that if you have freebsd-8x or earlier, this feature isn't built-in but can be easily added: http://freebsd.1045724.n5.nabble.com/Re-rc-8-script-waiting-for-the-network-to-become-usable-td4242157.html Or the earlier discussion: http://lists.freebsd.org/pipermail/freebsd-stable/2010-April/056521.html The link to the script in this thread is dead. Then use the second thread, which includes the script in-line. ___ 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
WITH_OPENSSL_PORT=yes
If WITH_OPENSSL_PORT=yes exists in /etc/make.conf, will the system compile against that as well or only applications? Darrel ___ 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
freebsd-update not updating reported patchlevel
I installed 8.2-RELEASE when it was new, and have been just using freebsd-update since then. I run freebsd-update whenever there are new critical patches. But for some reason, my system's reported patchlevel number hasn't updated since p3. For example, with this latest OpenSSL security update, running 'freebsd-update fetch' says (among other things) The following files will be updated as part of updating to 8.2-RELEASE-p7 and WARNING: FreeBSD 8.2-RELEASE-p3 is approaching its End-of-Life date. It is strongly recommended that you upgrade to a newer release within the next 2 months. So apparently it really thinks I'm at -p3, when I know I'm at -p6, and was at -p5 before that, and -p4 before that. The fact that the latest update only included the OpenSSL files confirms that the relevant files have been getting updated when I 'freebsd-update install'. But 'uname -r' continues to return 8.2-RELEASE-p3. Rebooting doesn't help. Is there something I need to do in order to bump the reported patchlevel? I thought this was supposed to happen automatically, since I didn't have to do anything to get it up to -p3. Thanks, Mike ___ 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: freebsd-update not updating reported patchlevel
Mike Brown m...@skew.org wrote; I installed 8.2-RELEASE when it was new, and have been just using freebsd-update since then. I run freebsd-update whenever there are new critical patches. But for some reason, my system's reported patchlevel number hasn't updated since p3. [sneck] But 'uname -r' continues to return 8.2-RELEASE-p3. Rebooting doesn't help. Is there something I need to do in order to bump the reported patchlevel? I thought this was supposed to happen automatically, since I didn't have to do anything to get it up to -p3. Amazingly, this very question was covered on this list within the last few hours. grin Executive summary: the kernel ID string that uname reports changes only when the -kernel- is changed. -p4, -p5, -p6, and -p7. have -not- involved any changes to the kernel. hence the ID string has stayed at '-p3'. While this _is_ counter-intuitive, it does make sense to avoid pushing a new k ernel out, and/or forcing an admin to rebuild a custom kernel, when the -only- change would be to the ID string. ___ 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: HOWTO: FreeBSD ZFS Madness (Boot Environments)
Hi, I just tested your tool the last few days and I must say I love it already. Though I can get one of the commands to work - might be me or the syntax beadm create [-e nonActiveBe | beName@snapshot] beName I read it as you can do the following beadm create beName@snapshot beName Is that correct or is it beadm create -e beName@snapshot beName Well neither of those seems to work for me, can you give an example of the use? Thanks Kalle There are only 3 possible ways: 1. beadm create beName - this will create BE beName from currently booted BE. 2. beadm create -e nonActiveBe beName - this will create BE beName from other BE called nonActiveBe 3. beadm create -e beName@snapshot beName - this will create BE beName from existing beName@snapshot snapshot At least these are the same possibilities that beadm(1M) at Illumos/Solaris provides. Hope that helps ;) Regards, vermaden -- ... ___ 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: HOWTO: FreeBSD ZFS Madness (Boot Environments)
Kalle Møller freebsd-questi...@k-moeller.dk: And I forgot If I do a create and destroy, I would assume my system was back to same state, but you keep the snapshot when I destroy the clone, dont know if its working as intended (better safe to keep it than sorry) or you just didn't think of it :) I added automatic deletion of snapshot origins at later versions, the 0.1 is now in Ports, but at SourceForge [1] or GitHub [2] there is 0.4 version already, so get the latest one, test more and let me know how the latest version works for You ;) [1] https://sourceforge.net/projects/beadm/ [2] https://github.com/vermaden/beadm Regards, vermaden -- ... ___ 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
