Re: Unable to access http://sane-project.org/
On Thursday 01 Aug 2013 11:58:01 Jerry wrote: Not really a FreeBSD problem; however, I was wondering if anyone else had been unable to access http://sane-project.org/ in the last 24 hours? http://www.isup.me/ is a useful site for instantly checking this sort of thing. -- 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: Saving scanned document
On Tuesday 23 Jul 2013 23:37:45 Jerry wrote: . There is a application that controls printing, scanning, faxing and copying but that is only available on a Windows or Mac machine. Might it work with wine? -- 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
Exim has stopped using SpamAssassin
I've just noticed that for the last month Exim does not appear to have been using SpamAssassin to check incoming emails. Previously all my incoming emails contained the following headers: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: X-Spam-Checker-Version: X-Spam-Level: X-Spam-Status: But I'm not seeing any of them now. I've compared things with a ZFS snapshot from a time when it was working and both Exim and SpamAssassin are the same versions as before and there has been no changes in /usr/local/etc/exim/configure or /usr/local/etc/exim/sa-exim.conf. Current versions are: FreeBSD curlew.lan 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64 builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 exim-sa-exim-4.80.1+4.2_2 p5-Mail-SpamAssassin-3.3.2_8 perl-5.14.4 (was 5.14.2_3 when SpamAssassin was working) I've re-installed Exim and SpamAssassin using the same make options as before to see if that had any effect but still no joy. I've set SAEximDebug to 1 in sa-exim.conf but there's still nothing in the logs to help. Any suggestions where I should look next? -- 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
[Solved] Error upgrading sysutils/nepomuk-core - Could not find parser plugin for encoding trig
On Friday 12 Jul 2013 18:15:18 Mike Clarke wrote: Could anyone advise how to get round this problem? [ 3%] Generating nie.h, nie.cpp cd /usr/ports/sysutils/nepomuk-core/work/.build/libnepomukcore /usr/local/bin/onto2vocabularyclass --name NIE --encoding trig --namespace Nepomuk2::Vocabulary --export-module nepomuk /usr/local/share/ontology/nie/nie.trig Could not find parser plugin for encoding trig The original problem arose when I ran portmaster -r apr -r kdelibs-4\*. It turned out that raptor is a dependency of kdelibs but for some reason portmaster had not selected it for upgrading. After manually running portmaster raptor I was able to build nepomuk-core and continue the mega update with portmaster -R -r apr -r kdelibs-4\* -- 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
Error upgrading sysutils/nepomuk-core - Could not find parser plugin for encoding trig
Could anyone advise how to get round this problem? [ 3%] Generating nie.h, nie.cpp cd /usr/ports/sysutils/nepomuk-core/work/.build/libnepomukcore /usr/local/bin/onto2vocabularyclass --name NIE --encoding trig --namespace Nepomuk2::Vocabulary --export-module nepomuk /usr/local/share/ontology/nie/nie.trig Could not find parser plugin for encoding trig *** [libnepomukcore/nie.h] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core/work/.build. *** [libnepomukcore/CMakeFiles/nepomukcore.dir/all] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core/work/.build. *** [all] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core/work/.build. *** [do-build] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core. -- 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: Keeping my system up to date with CTM or subversion?
On Wednesday 22 May 2013 21:23:39 Ed Flecko wrote: When security vulnerabilities are discovered and patches released by FBSD, the patch will tell you what steps you need to take to apply the patch and stay up to date, won't it? Yes, if you subscribe to the FreeBSD Security Notifications mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications you'll get email notifications when security parches are available. These give details of the background and impact of the vulnerability along with instructions of how to obtain and apply the patches. -- 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: Problems Printing
On Tuesday 05 Mar 2013 09:57:30 Matthias Apitz wrote: Looks like you have FreeBSD's lpr(1) in front of CUPS' lpr(1) in /usr/local/bin/lpr in your PATH; just do as root: # chmod /usr/bin/lpr And for full CUPS functionality you should do the same for /usr/bin/lp, /usr/bin/lpq and /usr/bin/lprm -- 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
Portmaster runs make config three times for some ports
I started off portmaster on a massive update on Thursday evening. Everything started off OK and I kept responding to all the make config screens until they were all finished and the compilation was well underway then went to bed and left it to get on with it. The next morning I discovered that things had progressed as far as starting to build en-apache-openoffice but it was sitting there with the config screen again despite having already gone through make config earlier. I clicked on OK and left it to get on with the compilation while I went away to get on with other things with just occasional checks to make sure it was still running. About 6 hours later when I checked it had completed the compilation and had started to install en-apache-openoffice but was waiting yet again with the config screen. Once again I clicked on OK and left things to continue. The job was still running last night and I expected to find it completed by this morning but on checking at 9:30 this morning I discovered that it had done the same thing with py27-gobject and had been sitting there with the config screen since shortly after midnight. Both openoffice and py27-gobject had gone through make config in the initial stage (I've checked the log file) but for some reason make config was repeated immediately before the compile and install stages. I invoked portmaster with: portmaster -r libffi -r boost-libs -r gnutls -r libtasn1 and these are the only options set in /usr/local/etc/portmaster.rc # Never search for stale distfiles to delete (-D) DONT_SCRUB_DISTFILES=Dopt # # Do not prompt the user for failed backup package creation PM_IGNORE_FAILED_BACKUP_PACKAGE=pm_ignore_failed_backup_package Any ideas how I can avoid this happening. -- 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: Starting with ZFS on fresh install
On Monday 28 Jan 2013 12:55:06 Carmel wrote: I have a spare amd64 PC that I want to install FreeBSD 9.x on. I want it to utilize ZFS right from the start. There are two HD's in the PC. One will handle the /var partition and the other everything else. If you're going to be using ZFS then you'll probably be better off not having separate partitions and letting ZFS manage space allocation if you want to limit the size of /var or any other part of the system, You can install everything on a single disk to start with. Afterwards you can dynamically increase the size of the pool if you need more space by using the zpool add command to add the second drive into the storage pool. Alternatively if you have enough space and the second drive is at least as large as the first you can make your system more resilient by using it to create a mirrored pool with zpool attach. It's well worth doing some initial reading about ZFS before you start so you have a good idea of how to make the best use of it, these links could be a good starting point: * the FreeBSD ZFS wiki - https://wiki.freebsd.org/ZFS * Oracle's ZFS Administration Guide - http://hub.opensolaris.org/bin/download/Community+Group+zfs/docs/zfsadmin.pdf -- 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: Cronjob Cvsup - What?
On Sunday 27 Jan 2013 09:46:51 Matthew Seaman wrote: to get yourself a portsnap-ready copy of the ports tree. You only need to do that once, but you should move aside any pre-existing copy of /usr/ports obtained by any means other than portsnap(8) before you do (but keep anything under /usr/ports/distfiles and maybe /usr/ports/packages). Something like: cd /usr mv ports ports.old mkdir ports mv ports.old/distfiles ports/distfiles mv ports.old/packages ports/packages portsnap fetch extract Although this may be complicated if any of /usr/ports, /usr/ports/distfiles or /usr/ports/packages are on a separate partition or ZFS. I suppose the best approach with ZFS would be to make a snapshot immediately prior to running portsnap. -- 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: KDE Mouse Themes
On Sunday 27 Jan 2013 14:47:11 Carmel wrote: On Sun, 27 Jan 2013 08:09:10 -0600 ajtiM articulated: Do you have: System Settings - Input Devices - and there are Keyboard, Mouse and Remote control. Yes, and there is suppose to be a themes setting according to the KDE documentation; however, there is none. I have checked under every item setting in system settings for one. Try System Settings - Workspace Appearance - Cursor Theme -- 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: FreeBSD 8.2 with pre-built KDE 3.5 package from FreeBSD 7.1 DVD
On Friday 18 January 2013 16:58:11 RW wrote: You can carry on using 3.5 on any current release. The problem is when it's eventually removed from ports, updating other ports may result in dependency problems. I'm already starting to experience some problems which I assume are due to incompatibility with some recently upgraded dependencies and I've finally, and somewhat reluctantly, switched to KDE 4.8. It's certainly more bloated than 3.5 but after getting rid of some unwanted eye candy it's not as bad as I expected, certainly better than last time I tried it out about a year ago. The most noticeable deterioration in performance is that it's much slower to start up than 3.5 was and kmail takes much longer to open a mail folder than it used to. -- 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: what replaces javaws? using icedtea-web and openjdk6.
On Friday 30 November 2012 16:39:17 Antonio Olivares wrote: I need an application that requires /usr/local/bin/javaws and it is not found what should I do to install it or substitute it to make it work? curlew:/tmp% ls -l /usr/local/bin/javaws lrwxr-xr-x 1 root wheel 21 6 Nov 09:32 /usr/local/bin/javaws@ - /usr/local/bin/javavm curlew:/tmp% pkg_info -W /usr/local/bin/javavm /usr/local/bin/javavm was installed by package javavmwrapper-2.4_2 -- 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: How to create a partition for FreeBSD 9.0?
On Tuesday 27 November 2012 15:15:52 Ralf Mardorf wrote: And could I then run something similar to # echo gpart show ada0s1 /path/to/usbstick/logfile # gpart show ada0s1 /path/to/usbstick/logfile # echo gpart add -t freebsd -i1 ada0 /path/to/usbstick/logfile # echo gpart add -t freebsd -i1 ada0 /path/to/usbstick/logfile oops, but I guess you know what I mean etc.? I would like to post the output to the list. The neater way # script /path/to/usbstick/logfile # gpart show ada0 # gpart add -t freebsd -i1 ada0 # gpart show ada0 # CTRL+D Then /path/to/usbstick/logfile will contain a full log of your commands and output showing the partition information for ada0 before and after creating the new partition. -- 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: When Is The Ports Tree Going To Be Updated?
On Monday 26 November 2012 13:49:05 Odhiambo Washington wrote: I am starting to switch, and after all the discussions in this thread, I replaced my csup cron entry with the following: portsnap fetch portsnap extract portsnap update portsnap fetch should only be used interactively; for non-interactive use, you should use portsnap cron portsnap extract is only needed for initialising your portsnap-maintained ports tree. So, after your initial portsnap run, what you need in your cron file is just portsnap fetch update -- 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: Mounting SD card.
On Thursday 15 November 2012 02:06:02 Warren Block wrote: true /dev/da0 is a little shorter and safer. The search keywords for this are GEOM retaste or retasting. Thanks Warren. I wasn't aware of that option, it's certainly much neater and less prone to typing errors. -- 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: Mounting SD card.
On Wednesday 14 November 2012 19:43:30 Fernando Apesteguía wrote: If I boot the system and plug the SD card in, the green led doesn't even switch on and there is only a /dev/da0 that I can not mount. If I boot the system with the card plugged in, the green led is on and there is a /dev/da0s1 device that I can't still mount because mount_msdosfs returns an Input/Output error after some time. I think that's pretty much standard behaviour. The solution appears to be to wake it up with the following incantation: dd if=/dev/null of=/dev/da0 count=0 That's what works here. See the thread starting with http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/212109.html -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sunday 28 October 2012 01:17:46 Manish Jain wrote: Consider me a newbie here. How do I do wide-reinstall ? You can do this with ports-mgmt/portmaster. See the section Using portmaster to do a complete reinstallation of all your ports at the end of the examples section of the man page. I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport Rebuilding everything is the least complicated way of fixing the problem. It's a big job but if you don't do that then you're likely to have to keep doing even more firefighting in the future. -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Saturday 27 October 2012 09:42:10 Alexandr Alexeev wrote: Sometimes placing symlink to the newer version of library instead of older version helps. Specifying the alternative version in /etc/libmap.conf (5) is a neater way of doing this. The man page also shows you how to restrict the mapping to apply for only specified executables. -- 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
freebsd-update IDS
I've installed 9.1-RC2 after using svn to download /usr/src. Shortly after rebooting into the new system, and just out of curiosity, I ran freebsd-update IDS and was surprised to see that it reported 735 hash mismatches. Some of these were for files modified locally like /etc/hosts but the majority were for files that I've not changed, e.g. /usr/bin/clang-cpp has SHA256 hash 8937eebfc2bd2d18d05b786a568fbff980cf1b5a7333b8133cb197e7cd48ffcc, but should have SHA256 hash 36b39d8f00b1c5aab193d594ff67bfdb7a382b2bdb5b30c824254e9d658fbf8c. Are svn and freebsd-update looking at different versions of the system or do I have a problem? Considering the very short time interval between installing the system and checking IDS I'm quite confident my system hasn't been hacked from outside. -- 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
Gimp - problem opening images using URI's
Gimp has recently become unable to open images using URI's, e.g.- -- curlew:/home/mike% gimp -c http://www.freebsd.org/layout/images/beastie.png; Failed to connect to socket /tmp/fam-mike/fam- (gimp:27650): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 GIMP-Error: Opening 'http://www.freebsd.org/layout/images/beastie.png' failed: Could not open 'http://www.freebsd.org/layout/images/beastie.png' for reading: No such file or directory -- The above is with gimp-app-2.6.12_1,1 compiled from ports with default options running under FreeBSD 9.0-RELEASE, all ports are up to date and there are no missing dependencies. I had similar problems in the past and managed to fix it by adding --without-gvfs to the options in the Makefile but the problem reappeared after a recent upgrade to my ports. The port upgrade didn't touch gimp-app so I assume the problem is caused by some dependency which has been upgraded. I've tried rebuilding gimp-app both with and without my Makefile hack and with and without GVFS in the config options but with no success. The error message above is after rebuilding from a freshly downloaded copy of the port to ensure none of my old edits remained and with the default options in make config. It might be significant that the directory /tmp/fam-mike does not exist. I tried creating it but gimp produced an error Socket directory /tmp/fam-mike has wrong permissions and promptly deleted the directory. Recreating /tmp/fam-mike with permissions 700 got rid of the wrong permissions message but still failed to cure the problem. Google searches haven't come up with anything directly relevant to my problem but do imply that the problem could be related to devel/gamin. Could anyone offer any suggestions on how to go about resolving this? -- 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: editing pdf files
On Saturday 13 October 2012 21:47:01 Gary Kline wrote: SO: Is pdfimages going to spit of 6t50 files? as noted in last email, only a couple of these images are of any interest Probably. But Gimp accepts PDF files and gives you the option of importing images of individual selected pages. You might then be able to extract the text with some OCR software. -- 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: FreeBSD9 - Fresh install (2)
On Sunday 14 October 2012 19:05:32 Jos Chrispijn wrote: The slice one and two idea is perhaps Windows related, but I thought if I want to update my FreeBSD9 t0, let's say 10 or 11, I only have to clean slice one and put BSD on that again (having the backup slice untouched). My approach would be to go for 3 slices. Slice 1 would be a suitable size to hold the OS and swap, I have quite a lot of ports installed on my desktop PC so would go for about 20 to 30 GB. This could be less for a server but with 1TB you can afford to be generous. This can then be partitioned to suit with whatever combinations of /, /usr, /usr/local, /var. /tmp and swap suits your fancy. The second slice would be the same size as the first and be left empty for now as a spare. The third slice, the rest of the disk, would be for all of your data and could be partitioned (or not) to suit your needs for /home and any other local data requirements. If there's to be any large mysql databases then I'd put them here with symlinks from /var where mysql normally expects to find them. When you come to upgrade to the next FreeBSD release just install it into the spare second slice and boot from that instead of the first. If you experience any serious problems with the upgrade then nothing has been lost and you can just revert to booting of the first slice until things are sorted out. The above is all assuming you're using UFS. If you're going to use ZFS then there are other possibilities like using sysutils/beadm from ports http://forums.freebsd.org/showthread.php?p=175325 to manage multiple boot environments in a single partition. -- 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
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: older version of programs in freebsd
On Sunday 30 September 2012 10:14:23 Istvan Gabor wrote: 2012. szeptember 29. 13:16 napon Polytropon free...@edvax.de írta: Use portdowngrade. This tool is excellent in obtaining older versions of a specific port, for example to make it functional again (like the xzgv image viewer where the last usable version has been xzgv-0.8_9). Thank you. I will try it. If you use portsnap to keep your ports up to date then you can add a REFUSE line in /etc/portsnap.conf to stop new versions of the port being downloaded in the future. -- 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: Questions about ZFS Tuning
On Monday 17 September 2012 13:20:14 Jamie Paul Griffin wrote: I set zfs.zfs.prefetch_disable=0 because some dmesg line suggested/implied it would benefit. I don't recall the exact output now. If you look in /var/run/dmesg.boot you should find the message saying ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add vfs.zfs.prefetch_disable=0 to /boot/loader.conf. Since you have 2GB RAM then it's best to leave things as they are with prefetch disabled. -- 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: what is the best kind of KVM Switch?
On Sunday 12 August 2012 02:41:57 Bob Hall wrote: I'm currently on my third year with an Aten and have had no problems. I've been using a cheap Aten CS-64A 4 Port Mini KVM for nearly 6 years now with no problems. -- 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: Webpage screenshot
On Sunday 05 August 2012 19:41:38 Polytropon wrote: The idea of taking a screenshot from the web browser may look sufficient at first, but it is problematic when the web page doesn't fit horizontally or vertically snip How would you suggest to solve this task? How about the Pixlr Grabber extension for Firefox. You can specify the entire page, an area defined with the mouse or just the visible area and save the result to a .PNG file or copy it to the clipboard to paste directly into the Gimp. -- 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: How to mirror the FreeBSD OS on two disks
On Wednesday 11 July 2012 16:20:41 Joseph Lenox wrote: What about a ZFS root? Just make sure both disks are in the BIOS/EFT boot order. http://www.aisecure.net/2011/11/28/root-zfs-freebsd9/ Something else we noticed on our site is that backup of a system snapshot can be quickly restored using just a live CD (do up to step 5, then replace steps 6-7 with a zfs receive of the desired snapshot). Since the system is to be restored from the snapshot then I suppose most of steps 8 to 12 wouldn't be needed either. But what about step 5 before the restore: zpool export zroot zpool import -o cachefile=/var/tmp/zpool.cache zroot And then step 10 after running zfs receive cp /var/tmp/zpool.cache /mnt/boot/zfs/zpool.cache Are these steps needed when restoring from a snapshot? -- 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: USB device activity when not mounted
On Thursday 14 June 2012 07:05:11 Polytropon wrote: I don't think that's a problem. I've got a USB stick here that has a blinkenlight as soon as it's powered on (plugged in), even if there is no reading / writing / mounting activity. After you've successfully performed umount, the USB stick _is_ synced and can safely be removed, no matter what you assume the funny lights want to tell you. Maybe that's just a modern feature to make the USB stick more entertaining. :-) I have a Kingston one here which does appear to only blink while data is being transferred but one thing I have noticed is that the light continues to blink for a few seconds after the umount command completes. Presumably syncing is not compled until a few seconds after umount. Perhaps it's always safer to wait a few seconds after umounting before removing any USB storage device? -- 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: USB device activity when not mounted
On Thursday 14 June 2012 15:45:46 Polytropon wrote: However, as you said it might be possible that _inside_ the USB stick there is still an action that needs to be performed and therefore requires power. That's a possibility. But I doubt this takes several seconds to complete... I've just run a test here. The umount command returns almost instantaneously and the light, which is normally only lit while data is flowing, flickers for about 2 seconds after the umount command. But further testing showed that it flickers for 2 seconds after reading single byte file so perhaps the blinkenlight is configured with a minimum activation time. Being cautious however, I always wait a few seconds before removing any USB stick from any computer. -- 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: Making a bootable backup (hard)disk... how?
On Sunday 10 June 2012 23:14:57 Ronald F. Guilmette wrote: Well, nevermind about that. I get the general idea, i.e. that dumping at level N causes dumping of everything that has changed since the last dump at level N-1. A point to be aware of is that if you restore from a full backup followed by one or more incrementals then you will restore ALL files which were present when each dump was made - including any files which have been intentionally deleted since the dump was created. This isn't normally a problem but there might be some obscure situations where it could be. -- 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: Making a bootable backup (hard)disk... how?
On Monday 11 June 2012 00:03:59 Daniel Feenberg wrote: It does occur to me that /etc is not a felicitous place to keep this information, but given the desirability of dumping filesystems in read only state, placing the dump dates in the filesystem itself isn't feasible. Dumping with the -L option creates a temporary read only snapshot which is used as the source for the backup. This enables you to safely backup a live filesystem, More background on snapshots at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/snapshots.html -- 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: Making a bootable backup (hard)disk... how?
On Sunday 10 June 2012 03:30:53 Ronald F. Guilmette wrote: I don't care to take own my system to make backups... and don't believe that I should have to do so, and thus, this is one of the reasons why I would prefer to use something like cpio. Also, I don't like backups taking longer than absolutely necessary, and this is why I am specifically _not_ attracted to either the dd solution or to dump/restore, Not an immediate solution but have you considered switching from UFS to ZFS ? If you have sufficient memory and CPU power then this might be worth the effort. Creating ZFS snapshots and backing them up incrementally with zfs send | zfs receive should be very quick. -- 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: Address to reach human operator regarding problems with list?
On Thursday 31 May 2012 11:06:24 Thomas Mueller wrote: I contacted my Internet service provider, Insight Cable, about the problem, and they need a copy of any message that bounces, so they can see what went awry. I had the same problem a while ago with my ISP (Plusnet). Standard response from front line support is to say you need to send a copy of the message that you never had. Eventually I diverted my questions@ mail to a server that I had control of and relayed the messages from there to my ISP account so I could monitor the logs. The spam was being rejected with 552 Spam Message Rejected and no information was returned to identify the email. Most of the rejected mail was spam but there were a small number of false positives. When I managed to get past the ISP's front line support they removed the addresses for the false positives from the blacklist but this is only a temporary fix since more addresses keep wrongly finding heir way onto the list over time, though they do eventually drop off it again. Plusnet use Cloudmark spam filtering and I see from the OP's headers that Insight also use Cloudmark so I'd expect similar things are happening there. I was able to stop the bounces by adding freebsd.org to the whitelist on my ISP account - but with the downside of seeing more spam on the list. -- 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: Filesystem dump incremental?
On Thursday 17 May 2012, Matthias Petermann wrote: dump -a -1 -f /mnt/da0/backup-compaq.1.dump / Try a new full backup with dump -0aLuf /mnt/da0/backup-compaq.1.dump / then for the incremental use dump -1aLuf /mnt/da0/backup-compaq.1.dump / The option you're missing is u, but L is worth using as well when you're backing up a mounted filesystem. You could hack the contents of /etc/dumpdates to avoid having to repeat the level zero dump if you know the date and time when the original one was started. -- 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
Preventing portmaster from using packages for specified ports
I'm happy to use the -P option to let portmaster use packages for most of my ports but there's a few that must be compiled from the port instead because I need to configure non default options, e.g. to enable GIMP plugin support in graphics/xsane Is there any way of forcing portmaster to never use packages for certain specified ports? -- 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: Preventing portmaster from using packages for specified ports
On Tuesday 08 May 2012, John Webster wrote: Would this work for you? From the manpage: For those who wish to be sure that specific ports are always compiled instead of being installed from packages the PT_NO_INSTALL_PACKAGE vari- able can be defined in the make(1) environment, perhaps in /usr/local/etc/ports.conf if using /usr/ports/ports-mgmt/portconf, or in /etc/make.conf. This setting is not compatible with the -PP/--packages-only option. Yes, that looks like exactly what I need. I don't know how I missed it, I must have searched through the manpage several times and had a total blind spot for that paragraph - sorry for looking so dumb. -- 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: FTP oddness, over SSH session.
On Wednesday 11 April 2012, Dave B wrote: I just found however, that though I can reliably send a file to the FTP server and it get's saved just fine, that's not true when connecting this way using a SSH tunnel. Would it not be simpler just to use sftp directly rather than tunnelling ftp through ssh? -- 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: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Wednesday 21 March 2012, Lowell Gilbert wrote:
/data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-
4.1.10/out/freebsd.x86/
release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405:
error: invalid type argument of '-'
*** Error code 1
That line is supposed to be an assignment in between a VM_OBJECT_LOCK
and the corresponding VM_OBJECT_UNLOCK. Can you confirm that the
patches cause this to be the case?
Yes, that's where it is.
401 if (fContiguous)
402 {
403 Assert(enmType == RTR0MEMOBJTYPE_PHYS);
404 VM_OBJECT_LOCK(pMemFreeBSD-pObject);
405 pMemFreeBSD-Core.u.Phys.PhysBase =
VM_PAGE_TO_PHYS(vm_page_find_least(pMemFreeBSD-pObject, 0));
406 VM_OBJECT_UNLOCK(pMemFreeBSD-pObject);
407 pMemFreeBSD-Core.u.Phys.fAllocated = true;
408 }
It is a little tricky for me to
edit files in an i386 environment, but the next step is to track down
the definition of PRTR0MEMOBJFREEBSD, assuming that is the
dereference giving the error on your system, and determining whether
it ought to have the structure entry being dereferenced.
This takes me out of my depth in my very limited experience of C but would it
be
this, also in memobj-r0drv-freebsd.c:
50 /**
51 * The FreeBSD version of the memory object structure.
52 */
53 typedef struct RTR0MEMOBJFREEBSD
54 {
55 /** The core structure. */
56 RTR0MEMOBJINTERNAL Core;
57 /** Type dependent data */
58 /** The VM object associated with the allocation. */
59 vm_object_t pObject;
60 } RTR0MEMOBJFREEBSD, *PRTR0MEMOBJFREEBSD;
and then:
109 PRTR0MEMOBJFREEBSD pMemFreeBSD = (PRTR0MEMOBJFREEBSD)pMem;
[snip]
You might want to try updating your system or trying the -legacy
version of the port.
Version 4.1.8_1 seems to be working OK for me so I'll probably stick with that
for
the time being unless a fix turns up before I upgrade to 9.0-RELEASE which I'm
planning to do shortly.
--
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: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Friday 16 March 2012, Lowell Gilbert wrote:
My best advice is: clean out the directory for that port, update
again, and see if the problem is the same.
I've now deleted everything in /usr/ports/emulators/virtualbox-ose-kmod and
downloaded a fresh copy of the
port (4.1.10) from the FreeBSD website but still get the same problem when
compiling.
/data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.10/out/freebsd.x86/
release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error:
invalid type argument of '-'
*** Error code 1
I've also updated the source files for the base system and built a new kernel
in case it's a header problem
since I noticed that /usr/src/include/unistd.h and
/usr/src/lib/libc/include/libc_private.h were both updated
in security advisory SA-11:07 (for which I only did a binary update at the
time) but this didn't cure the
problem.
I've had no problem building earlier versions but it went pear shaped with
4.1.8_2
As an experiment I've used portdowngrade to try compiling a few older versions
number date portversion comment
1 2012/03/15 09:32:29 VirtualBox-${DISTVERSION} - Update to 4.1.10
2 2012/03/09 21:46:18 VirtualBox-${DISTVERSION}_2 - Reenabled fixed
memobj r0 patch
3 2012/02/22 22:09:41 VirtualBox-${DISTVERSION}_1 - Revert memobj r0
patch until the problems on i386
are solved
4 2012/02/21 14:31:54 VirtualBox-${DISTVERSION} - Update to 4.1.8
Of these, the only one to compile OK was 4.1.8_1 so it looks like the fixed
memobj r0 patch still has problems
on my system.
FreeBSD curlew.lan 8.1-RELEASE-p8 FreeBSD 8.1-RELEASE-p8 #0: Tue Mar 20
19:00:39 GMT 2012
r...@curlew.lan:/usr/obj/usr/src/sys/GENERIC i386
--
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: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Friday 16 March 2012, Adam Vande More wrote: On Tue, Mar 13, 2012 at 9:13 AM, Mike Clarke jmc-freeb...@milibyte.co.ukwrote: in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox- 4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? Did you follow the relevant /usr/src/UPDATING instructions? The latest relevant one appears to be this: 20120221: AFFECTS: users of emulators/virtualbox-ose AUTHOR: de...@freebsd.org virtualbox-ose has been updated to 4.1.8 and requires the latest devel/kBuild-devel now. It is only a build dependency so it is safe to remove it before updating. # pkg_delete -f kBuild-\* I did this some time ago and the earlier version, 4.1.8_1, compiled fine but I started to have problems with 4.1.8_2 -- 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
Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
portmaster -a fails with: cc -O -pipe -march=athlon-mp -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: In function 'rtR0MemObjFreeBSDAllocPhysPages': /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error: invalid type argument of '-' *** Error code 1 Stop in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? -- 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
Can't build en-freebsd-doc-20120205
/freebsd-doc-en. -- 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: Can't build en-freebsd-doc-20120205
On Saturday 11 February 2012, Mark wrote: I had this a few days ago. A search returned keep restarting make install and it will build and install. You will notice it will stop at different place each time, just restart the buld. Thanks for the tip. It completed on the second pass. -- 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: fixating USB Storage
On Saturday 04 February 2012, Conrad J. Sabatier wrote: I don't know if anyone else has already mentioned it to you in response to this question, but I just very recently switched over to using volume labels to mount my partitions instead of device names. I was having an ongoing issue where this external USB drive's device number assignment would change from one boot to the next, toggling back and forth between da0 and da4 (strange!). Sounds similar to my experience. Normally my internal 4 slot memory card reader is assigned devices da[0-3] and when the USB memory stick is inserted it comes up as da4. If the USB stick is present on booting then it appears as da0 and the card reader is da[1-4]. So it looks like occupied slots are given priority when numbers are assigned at boot time. -- 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: fixating USB Storage
On Saturday 04 February 2012, Jonathan Vomacka wrote: On Feb 4, 2012 4:54 AM, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: ? Sounds similar to my experience. Normally my internal 4 slot memory card reader is assigned devices da[0-3] and when the USB memory stick is inserted it comes up as da4. If the USB stick is present on booting then it appears as da0 and the card reader is da[1-4]. So it looks like occupied slots are given priority when numbers are assigned at boot time. Do you know if it is different with zfs system? That was with a UFS basedFreeBSD 8.1-RELEASE system but I've just tested it 9.0-RELEASE booting from ZFS and it does just the same. -- 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: upgrade from 8.2 to 9.0
On Saturday 14 January 2012, Dick Hoogendijk wrote: My system is running ZFS on root now, so I would very much like to hear if the binary upgrade through freebsd-update works well for such a system (w/ zfs on root). I don't want to get stuck with a system that won't boot again because something goes wrong with zfs. Have you considerd using manageBE http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE? With this tool you can set up cloned alternative Boot-Environments (BE) so that you can go back to your old BE if the new one doesn't work. I'm in the process of upgrading to 9.0 and taking the opportunity of changing over to ZFS. I needed to re-arrange my filesystem structure to boot from tank/ROOT/someBEname/ instead of tank/ (and make sure the mountpoints of any descendent file systems are suitably adjusted) but it was worth the effort. I installed 9.0-RC2 from the ISO onto a spare drive so I haven't done an 8 to 9 binary upgrade but I have used freebsd-update to upgrade from 9.0-RC2 to 9.0-RELEASE and that went through without any problems. -- 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: upgrade from 8.2 to 9.0
On Saturday 14 January 2012, Dick Hoogendijk wrote:
I had not heard of this project before. Sounds very nice if it works.
Manging BE's is one of the main things I miss in the FreeBSD ZFS
support. Coming from (open)Solaris this was quite a disappointment.
BE's rock!
Yes, it's working fine here.
You can even upgrade a new environment while you continue working with
the current one with
manageBE create -n newBE -s sourceBE -p pool
manageBE freebsd-upgrade -n newBE -p pool -r release
manageBE activate -n newBE -p pool
Then reboot into the new BE and complete the upgrade with the
final freebsd-update install step. But I needed to
change chroot /${bootfs} near the end of the script
to chroot /${pool}/ROOT/${bootfs} to get manageBE freebsd-upgrade
command to work.
Along similar lines, if you need to do a massive ports upgrade which you
suspect might go pear shaped then you can do it in a new BE without
upsetting your working system:
chroot /tank/ROOT/newBE mount -t devfs devfs /dev
chroot /tank/ROOT/newBE portmaster -a
chroot /tank/ROOT/newBE umount /dev
... then, if all went well, activate the new BE and reboot.
--
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: OT: Root access policy
On Thursday 29 December 2011, Damien Fleuriot wrote: [snip] sudo su - or sudo sh and the customer gets a native root shell which does *not* log commands ! [snip] Say the customer can sudo commands located in /usr/local/libexec/CUSTOMER/ All he has to do is write a simple link to sh/bash, and sudo it. But if it's possible to determine exactly what commands the customer needs to run as root then putting suitable incantations into /usr/local/etc/sudoers should prevent the customer from being able to use tricks like that. -- 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
9.0RC2 IPV6 warnings from ntpd
After installing 9.0RC2 I'm getting the following warnings at boot time: Dec 9 10:31:09 curlew ntpd[1081]: bind() fd 23, family AF_INET6, port 123, scope 3, addr fe80::6ef0:49ff:fe9e:8897, mcast=0 flags=0x11 fails: Can't assign requested address Dec 9 10:31:09 curlew ntpd[1081]: unable to create socket on nfe0 (3) for fe80: :6ef0:49ff:fe9e:8897#123 I'm puzzled by this because I've only configured the system for IPV4 and yet my network interface has been configured for both: nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE ether 6c:f0:49:9e:88:97 inet 192.168.1.13 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::6ef0:49ff:fe9e:8897%nfe0 prefixlen 64 scopeid 0x3 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active /etc/rc.conf: hostname=curlew.lan ifconfig_nfe0=inet 192.168.1.13 netmask 255.255.255.0 defaultrouter=192.168.1.138 zfs_enable=YES moused_enable=YES keymap=uk.iso ntpd_enable=YES ntpd_sync_on_start=YES sshd_enable=YES inetd_enable=YES powerd_enable=YES /etc/ntp.conf contains just a single line: server ntp.plus.net maxpoll 9 The boot messages appear to be just warnings because ntpd is working fine over IPV4 but I feel that I should try to fix this in case it leads to problems later. I certainly don't need IPV6, neither my router nor my ISP provide the facility but I haven't managed to find any way of disabling it. -- 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: umass to /dev/da* mapping
On Wednesday 07 December 2011, Zane C. B-H. wrote: Why are you using a custom Perl script for this instead of the built in tools for this? Below is how I have it setup on my system... In /etc/devfs.rules... [localrules=10] add path 'da*s*' mode 0660 group 5001 Because devfs only relates to boot time and I want to deal with usb sticks inserted while the system is running. The allocation of device numbers is dynamic and depends on what other umass devices are already connected. Normally my internal memory card reader is allocated da[0-3] at boot time and the memory stick will appear as da4 when subsequently inserted but if it's already plugged in when the system boots then it appears as da0 and the card reader is da[1-4]. If I insert an extra memory stick it will be allocated the next available device number. I don't want the user to have to hunt around to determine which device to mount so my script takes the umass device number supplied by devd and determines the relevant da* device then it sets the permission to 660 for that device and creates a link, /dev/usbstick, pointing to it. All the user then has to do is mount /dev/usbstick on his mount point. Following the earlier tip from Polytropon I now have a working script which does exactly what I need. -- 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: umass to /dev/da* mapping
On Wednesday 07 December 2011, Zane C. B-H. wrote: On Wed, 7 Dec 2011 08:39:30 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Wed, 7 Dec 2011, Zane C. B-H. wrote: Still you will want to investigate what I've mentioned. It will drastically simplify permission stuff as well as make automatic. The devfs stuff is just not boottime only, but will be applied to any new device added etc post boot. Are you sure of that? Seems like devfs permissions are only applied when devfs(8) apply/applyset commands are run, directly or through /etc/rc.d/devfs. Yeah, I am sure of that. It is what I have setup here. /etc/devfs.conf - This one only affects boot time stuff. /dec/devfs.rules - This one contains the rules will be applied during and post boot. It will also require you to specify which to use in /etc/rc.conf as this file can contain multiple rule sets. But can I use that to dynamically set up my link to the new device when the memory stick is inserted? -- 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
umass to /dev/da* mapping
I have a fairly simple perl script which is run by devd when I plug in a USB memory stick. The script sets up some permissions and a link to make life easy for a user to mount the memory stick. This normally works fine but there are problems if the memory stick is already inserted before booting. Normally my internal 4 slot memory card reader is detected as umass0 with devices da[0-3] and when the USB memory stick is inserted it comes up as umass1 with device da4 and my script works on that assumption. If the USB stick is present on booting then it appears as da0 on umass0 and the card reader is da[1-4] on umass1 so the script fails. Is there any convenient way for my script to determine which da* devices correspond to the umass device name? -- 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: umass to /dev/da* mapping
On Monday 05 December 2011, Polytropon wrote: On Mon, 5 Dec 2011 17:08:15 +, Mike Clarke wrote: [snip] Is there any convenient way for my script to determine which da* devices correspond to the umass device name? Maybe you could use a matching against match bus 0x; match vendor 0x; match product 0x; match release 0x; to determine which device you're currently accessing. As the USB IDs stay the same for at least the card reader, it should be easy to conclude. :-) USB devices are usually enumerated in the order they appear to the system. Thanks for that idea. I'd originally thought in terms of not being able to use the vendor info to identify a usb stick since that can't be known in advance for every stick that might ever be inserted but I'd overlooked using the info to eliminate the built in card reader. So now when any umass device is attached devd calls my script which just iterate over sysctl dev.umass | grep %pnpinfo building up a list of devices, adding four if it's the card reader or one for each other umass, and it works a treat. -- 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: upcoming 9.0 release
On Friday 02 December 2011, Dick Hoogendijk wrote: I always use portmaster. What steps do I take to get from installed ports on 8.2-release to 9.0? Is there a nice and working procedure to follow? Thanks for the advice. You need to re-install all your ports after upgrading between major revisions. The final example on the portmaster man page provides a good checklist of what you need to do. -- 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
Installing ZFS on 9.0-RC2
I'm planning to upgrade to 9.0 soon and thought this might be a good opportunity to switch over to ZFS so I'm currently experimenting on a spare drive with the 9.0-RC2 DVD. I started off following the procedure in http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot but hit a problem in that the the new installer doesn't appear to provide a Fixit option. I've tried the shell and live cd options in the installer and also tried booting single user from the DVD but these all use the DVD as a read only root file system instead of the memory based file system in Fixit mode. I was able to get as far as creating a zpool but the first zfs create comand produced an error saying that it was unable to mount zroot/tmp. What's the correct approach to go about this with the 9.0-RC2 installer? -- 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: Installing ZFS on 9.0-RC2 - Solved
On Tuesday 22 November 2011, Mike Clarke wrote: I started off following the procedure in http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot but hit a problem in that the the new installer doesn't appear to provide a Fixit option. I've tried the shell and live cd options in the installer and also tried booting single user from the DVD but these all use the DVD as a read only root file system instead of the memory based file system in Fixit mode. OK, I found a workaround at http://www.aisecure.net/2011/05/01/root-on-zfs-freebsd-current/ -- 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: poppler-qt-0.16.7
On Monday 14 November 2011, n dhert wrote: Has anything been done to fix this? I don't believe it was already done: nothing changed in /usr/ports/UPDATING, also no instructions for portupgrade yet. I still get # pkg_version -VIL= poppler-qt-0.16.7 ! Comparaison failed # pkgdb -F Stale origin: 'graphics/poppler-qt': perhaps moved or obsoleted. Just pkg_delete poppler-qt-0.16.7 and everything will be fine providing you've updated kdegraphics3. It was a bit more of a problem for me. I'm using portmaster and it refused to continue with the rest of the upgrade until I'd deleted poppler-qt. -- 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: update packages by pkg_add
On Saturday 29 October 2011, hvn wrote: Using version 8.2, can somebody tell me how I can upgrade packages that I installed using pkg_add? I'm trying to install more packages but get messages that there are package-conflicts because of older installed version. pkg_delete -f name-of-package pkg_add name-of-package-file The pkg_delete command needs the full name of the package including the version number at the end. Since you're going to immediately re-install the package you don't need to worry about any warning messages saying that the package is needed by other packages. The above pkg_add command will install a package from a file that you've already downloaded. If you don't have the package file then you can fetch and install the package from an FTP site with the command: pkg_add -r name-of-package -- 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: video acceleration on vbox
On Tuesday 25 October 2011, Aryeh Friedman wrote re guest additions for windows: What port do I find them in? You don't. They're a Windows thing. You should be able to download and install them into the guest Windows system by selecting Install Guest Additions at the bottom of the Virtualbox Devices menu. -- 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: pkg_upgrade seems to try server that isn't right
On Sunday 09 October 2011, Conrad J. Sabatier wrote: I assume you mean pkg_upgrade (not upgrade_pkg)? See the ENVIRONMENT section of the man page. All of the pkg_* tools are consistent in how they reference these variables. There isn't a pkg_upgrade in the base system and I'm not aware of one in ports either but I'm open to correction. There is a python script, pkgupgrade, developed by Michel Talon which might meet the OP's needs http://www.lpthe.jussieu.fr/~talon/. Alternatively the OP could use either portmaster or portupgrade from ports, both of these can be forced to use packages instead of building from source by using the -P or -PP options. -- 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: Trying to build Nessus 4 from ports
On Monday 26 September 2011, Michael D. Norwick wrote: Still no joy trying to build from source via ports or installing the binary from tenable.com on FreeBSD 9. nessusd is installed but errors out with 'libz.so.5 not found. I have; $ ls -l /lib/libz.* -r--r--r-- 1 root wheel 90328 Sep 26 05:46 /lib/libz.so.6 I see from the download page that the package is for FreeBSD 8.x which uses libz.so.5 so you might have compatibility problems with 9-beta2. As a workaround you could try putting the following line in /etc/libmap.conf libz.so.5 libz.so -- 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: Help with devd.conf
On Saturday 24 September 2011, Rod Person wrote:
I'm trying to understand devd.conf to auto mount usb devices. For
example I have a usb drive that will show up as da1 so as a test I
just want to write something to syslog when it is plugged in.
[snip]
Any help would be appreciated, thanks.
This works for me:
attach 10 {
match device-name umass[0-9];
action logger you plugged in some usb device;
};
--
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: build ports from not a root user?
On Thursday 21 July 2011, Peter Vereshagin wrote: As long as I saw the instructions on building from source they wre generally all like this: $ cd /tarball-expanded-0.x.y $ ./configure $ make $ su - # cd /tarball-expanded-0.x.y # make install That important 'su -' is omitted from the ports. And it is about the security. But this requires /usr/ports to be writable by the non-root user and creates a security risk. This cannot be overcome by limiting the installation to root only because you can no longer be sure that the source or installation scripts have not been tampered with by a non-privileged user. -- 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
Odd behaviour with portmaster -r gnutls
From /usr/ports/UPDATING --- 20110605: AFFECTS: users of security/gnutls and any port that depends on it AUTHOR: no...@freebsd.org gnutls has been updated to 2.12.6.1 and all shared libraries' versions have been bumped. So you need to rebuild all applications that depend on gnutls. Do something like: portupgrade -rf gnutls portmaster -r gnutls --- pkg_info -Rx gnutls shows that gnutls is required by 92 of my installed ports so before running portmaster -a I duly ran portmaster -r gnutls. This ran without any errors but only 4 ports were updated... curlew:/root# portmaster -r gnutls [snip] === Done displaying pkg-message files The following actions were performed: Re-installation of GeoIP-1.4.7 Upgrade of python26-2.6.6_1 to python26-2.6.7 Upgrade of gnutls-2.8.6_2 to gnutls-2.12.6.1_1 Upgrade of wireshark-1.4.6 to wireshark-1.4.7_1 curlew:/root# Should I worry about this huge discrepancy? I haven't got round to running portmaster -a yet and I haven't come across any problems so far, apart from having to add an entry for libgnutls.so.40 in /etc/libmap.conf to keep cups happy. pkg_version -vL= shows that 70 ports are due for updating, only some of these depend on gnutls so even after running portmaster -a there will be a considerable number of ports depending on gnutls which will not have been updated. -- 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
Upgrading ImageMagick fails 2 of 48 tests
I'm trying to upgrade ImageMagick from 6.6.5.10 to 6.6.6-10 on FreeBSD 8.1-RELEASE but 2 tests fail with segmentation faults - validate-formats-in-memory.sh and validate-formats-on-disk.sh. I'll stick with 6.6.5.10 for now but would welcome suggestions on how to deal with this problem = ImageMagick 6.6.6: ./test-suite.log = 2 of 48 tests failed. .. contents:: :depth: 2egmentation fault FAIL: tests/validate-formats-in-memory.sh (exit: 139) = Version: ImageMagick 6.6.6-10 2011-02-14 Q16 http://www.imagemagick.org Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC ImageMagick Validation Suite (FormatsInMemory) validate image formats in memory: test 0: ART/Undefined/TrueColor/8-bits... pass. test 1: ART/Undefined/TrueColorMatte/8-bits... pass. test 2: ART/Undefined/Grayscale/8-bits... pass. [Snip lots of passes] test 291: JPEG/Undefined/PaletteMatte/8-bits... pass. test 292: JPEG/Undefined/PaletteBilevelMatte/8-bits... pass. test 293: JPEG/Undefined/Bilevel/1-bits... pass. teSegmentation fault FAIL: tests/validate-formats-on-disk.sh (exit: 139) === Version: ImageMagick 6.6.6-10 2011-02-14 Q16 http://www.imagemagick.org Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC ImageMagick Validation Suite (FormatsOnDisk) validate image formats on disk: test 0: ART/Undefined/TrueColor/8-bits... pass. test 1: ART/Undefined/TrueColorMatte/8-bits... pass. test 2: ART/Undefined/Grayscale/8-bits... pass. [Snip lots more passes] test 291: JPEG/Undefined/PaletteMatte/8-bits... pass. test 292: JPEG/Undefined/PaletteBilevelMatte/8-bits... pass. test 293: JPEG/Undefined/Bilevel/1-bits... pass. test 2Segmentation fault -- 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: Follow a port of a specific major verion
On Tuesday 08 February 2011, Mikael Bak wrote: I was not aware I could just install the same software over the other without first removing it. Shouldn't I do that? I would not want to end up with a broken software or a broken ports database. If in doubt you could create a backup package first with pkg_create -b pkg-name. That would give you a fair chance of rolling back to the previous version if things went pear-shaped. -- 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: Using Multiple -prune directives in a find command
On Monday 07 February 2011, Martin McCormick wrote: Can one use the -prune directive multiple times in a find command to specify a list of directories not to descend? It would be like find . -name * -prune dir1 -prune dir2 -print or whatever you wanted find to do, but that does not work or I wouldn't be asking. Find appears to get confused and thinks dir1 is a command. find . -type d -name dir1 -prune -o -name dir2 -prune -o -name \* ... should list all files except those in dir1 or dir2 -- 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: wine questions
On Thursday 27 January 2011, Yuri Pankov wrote: On Thu, Jan 27, 2011 at 10:50:31PM +, Mike Clarke wrote: [snip] But VirtualBox OSE doesn't support USB. VirtualBox 4 *seems* to support USB (I have the option in the GUI, haven't tried it though). It's available for testing from http://svn.bluelife.at/ at the moment. That's very welcome news. I have a USB printer (Canon iP4500) which works very well with FreeBSD as far as printing is concerned but it's a bit of a pain having to move it over to a Windows PC if I want to run any of the utilities like checking ink levels or head cleaning. USB support with VirtualBox would be very useful for that. I'm usually rather hesitant when it comes to experimenting with 'bleeding edge' versions of software but I'm seriously tempted to give this one a try. -- 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: wine questions
On Thursday 27 January 2011, Dmitri Brengauz wrote: On Thu, Jan 27, 2011 at 11:48 AM, Fred f...@blakemfg.com wrote: Hello, I need to buy an expensive logic device programmer that connects to a PC through USB. [snip] Have you tried VirtualBox? You still have to shell out for a Windows license, but at least the Gates virus will be contained securely on your computer. For me, Virtual Box + FreeBSD has been running better than VMWare + OS X. Once again, free software, more than worth the price. But VirtualBox OSE doesn't support USB. -- 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: Which network driver for RTL8211 or 8201 NIC's?
On Thursday 20 January 2011, Pyun YongHyeon wrote: On Wed, Jan 19, 2011 at 11:54:54PM +, b. f. wrote: Mike Clarke wrote: I need to replace a failing motherboard. I'm aiming to keep the existing Athlon CPU so I'm tied down to to a socket AM2(+) board and the majority of those available seem to have nForce 630a chipsets and RTL8211CL or 8201EL NIC's which aren't explicitly mentioned in the release notes http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET. I see that the strings RTL8211C(L) and RTL8201L (but not EL) appear in /usr/src/sys/dev/rgephy.c and rlphy.c but the man page for the rl driver only mentions RealTek 8129/8139 and I'm not sure which driver is built from rgephy.c. Am I going to have problems if I get a motherboard with one of these NIC's? It's a bit confusing, because there are product numbers associated with NICs, and with different individual component chipsets, and some Correct. Identifying exact model number is the one of hardest thing in Realtek controllers. I think RTL8211CL or 8201EL are not MAC controller but the PHY model name. These PHY are supported by rlphy(4) since they are not gigabit PHY(e.g. Fast Ethernet). I recently found someone with a motherboard with the same chipset in a Windows PC and was able to experiment with it by booting off a FreeBSD install CD to confirm that the RTL8211CL was recognised. So I went ahead and bought my new motherboard (Gigabyte GA-M68M-S2P) and things are working fine. According to the specs the RTL8211CL is Fast Ethernet, claiming 10/100/1000 Mb/sec. I'm only using 100Mb/sec so can't confirm the 1000Mb capability. In case the information is of use to anyone, here's an extract from dmesg: nfe0: NVIDIA nForce MCP61 Networking Adapter port 0xec00-0xec07 mem 0xfe02d000-0xfe02dfff irq 20 at device 7.0 on pci0 miibus0: MII bus on nfe0 rgephy0: RTL8169S/8110S/8211B media interface PHY 3 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe0: Ethernet address: 6c:f0:49:9e:88:97 nfe0: [FILTER] ... and pciconf -lv nfe0@pci0:0:7:0:class=0x068000 card=0xe0001458 chip=0x03ef10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'Nvidia Networking Card (nForce 405)' class = bridge -- 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: Upgrade path from STABLE to RELEASE
On Friday 07 January 2011, Matthew Seaman wrote: Your choices are to backup and reinstall using a release version, or to grab the latest -STABLE or -RELEASE sources and upgrade by compiling from source. Note that last option still won't allow you to use freebsd-update subsequently: you have to stick with the binaries from the install media for that to work. This has got me puzzled. I appreciate that freebsd-update won't update the sources so an attempt to recompile after using freebsd-update to change between versions will lead to trouble unless the new sources are also downloaded but I'd assumed that freebsd-update would manage to update the binaries irrespective of whether they'd been installed as binary downloads or compiled locally. My present system started as 8.0-RELEASE, installed as a binary from DVD. I subsequently used csup to upgrade through 8.1-STABLE and 8.1-RELEASE. I've been using freebsd-update to keep 8.1-RELEASE up to date with the latest security patches. I didn't see any error messages when I ran freebsd-update so I assumed that everything went fine. Is there something I've overlooked and should I recompile from source to be safe? -- 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
Which network driver for RTL8211 or 8201 NIC's?
I need to replace a failing motherboard. I'm aiming to keep the existing Athlon CPU so I'm tied down to to a socket AM2(+) board and the majority of those available seem to have nForce 630a chipsets and RTL8211CL or 8201EL NIC's which aren't explicitly mentioned in the release notes http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET. I see that the strings RTL8211C(L) and RTL8201L (but not EL) appear in /usr/src/sys/dev/rgephy.c and rlphy.c but the man page for the rl driver only mentions RealTek 8129/8139 and I'm not sure which driver is built from rgephy.c. Am I going to have problems if I get a motherboard with one of these NIC's? -- 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: Clean up / filesystem
On Saturday 09 October 2010, Arthur Chance wrote: Not if running an X desktop, as all sorts of things get stuck in /tmp that are needed. In single user mode it should be safe, and it probably is when simply running on the console. As a long term solution, if you wish to clear /tmp every reboot add clear_tmp_enable=YES # Clear /tmp at startup. to your /etc/rc.conf Also consider using periodic(8) to do a safe daily cleanup deleting files in /tmp not accessed in the last 3 days. You need to add daily_clean_tmps_enable=YES to /etc/periodic.conf. If you prefer a different retention period you can set it by adding a line setting daily_clean_tmps_days to the desired value. You can also modify the default list of files to ignore with the variable daily_clean_tmps_ignore -- 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: Free BSD 8.1
On Tuesday 28 September 2010, per...@pluto.rain.com wrote: Mike Clarke jmc-freeb...@milibyte.co.uk wrote: [snip] The problem is if/when you need to update a port as a result of a security advisory. If your ports tree is very much out of date then it's likely that updating that one port will require a number of dependencies to be updated as well, sometimes all the ports depending on one or more of the updated dependencies need to be updated as well and the resultant bag of worms can take quite a lot of sorting out. The little and often approach of keeping the ports tree up to date could be less traumatic. and, in this context, your point is? I'm advocating starting from a stable and self-consistent baseline, consisting of a release _and_ its corresponding port/package collection, and then considering whether any updates are needed. Isn't that orthogonal to the question of whether or not to follow ports updates, once the baseline has been established? ___ Well I'd normally happy to stay with the original release state without having to have the latest greatest version of each application but I prefer to update any ports which have been flagged by portaudit as having security vulnerabilities and this is when the problem could arise. Updating a single port in isolation without updating the ports tree can lead to problems with dependencies so you invariably need to update your ports tree and update the dependencies for the port in question. If, for example, you were to build a web server by installing 8.1-RELEASE and the matching package for apache you would have apache-2.2.15_9 which suffers from a remote DoS bug and should be upgraded to 2.2.16 http://www.vuxml.org/freebsd/CVE-2010-1452.html. As Warren Block has pointed out elsewhere in this thread there's usually a flurry of port updates when the ports tree is unfrozen just after a release so if you now update the ports tree and upgrade your ports there could be a large number of ports to upgrade, most of them can be upgraded quite painlessly with portmaster or portupgrade but you'd need to check /usr/ports/UPDATING to see if any of them needed special attention, fixing a single special case is usually quite straightforward but things sometimes get more complex when there's several. If on the other hand you installed the base system, updated your ports tree and then built what you needed from ports (or the latest packages) you'd get the latest versions without having to sort out any conflicts. If you wait a long time before a new vulnerability pushes you into doing your next upgrade then you'll still probably have quite a lot to sort out but updating small numbers of ports more frequently usually involves less work than an occasional mega upgrade. Well, that's just my 2 cents worth and it does depend on how many ports you have. A minimal server setup with few ports will probably not need very frequent port upgrades but something like a desktop could easily have 700 or more ports and it can be quite messy to upgrade your ports if it's been a long time since the last upgrade. -- 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: Free BSD 8.1
On Tuesday 28 September 2010, Ian Smith wrote: I agree with Mike about the worms :) I have an 8.0-RELEASE system with many ports installed and quite a few configured to taste with a recently upgraded 8-STABLE world, working through a huge portversion update list, started by fetching over 900MB of packages so far including X and KDE by portupgrade -aFPP. It's going to take a while, and I'll be surprised if I don't skin a few knuckles on circular dependencies along the way. I used to use packages in preference to ports but, being on a PAYG broadband account rather than unlimited, I'm more concerned about bandwidth than compile time. I found that upgrading ports often involved just a few packages which had actually been changed while the rest just had their version number bumped as a result of dependencies but still needed the entire package to be downloaded. Switching to building the ports instead means that I usually only need to download a relatively small number of distfiles with the remaining ports being recompiled from my existing collection of distfiles using the new makefiles in the updated ports tree. -- 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: Free BSD 8.1
On Monday 27 September 2010, per...@pluto.rain.com wrote: I've recently started on a new system, and am planning to install 8.1-RELEASE, including the corresponding ports tree; then install what ports I can from packages and also fetch the corresponding distfiles; and finally build -- from release-corresponding ports -- any that aren't available as packages or where I want non-default OPTION settings. That approach should avoid most nasty surprises while getting things set up and working. _After_ everything is installed and configured properly will be plenty soon enough to consider whether any ports need to be updated -- and the already- installed-and-working package collection will provide a fallback in case of trouble trying to build any updated versions. The problem is if/when you need to update a port as a result of a security advisory. If your ports tree is very much out of date then it's likely that updating that one port will require a number of dependencies to be updated as well, sometimes all the ports depending on one or more of the updated dependencies need to be updated as well and the resultant bag of worms can take quite a lot of sorting out. The little and often approach of keeping the ports tree up to date could be less traumatic. -- 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: port upgrading
On Sunday 26 September 2010, Roland Smith wrote: If you are upgrading to another major version of FreeBSD (say 7.x to 8.x), make a list of all used ports with `portmaster -l ports.list`. Then delete all ports before updating the system. After the update, re-install the 'root' and 'leaf' ports from ports.list. A more convenient approach is to run 'portmaster --list-origins' which produces a list of root and leaf ports which you can feed back into portmaster when reinstalling the ports, all the other dependencies should sort themselves out. There is a good description of this in the final example near the bottom of the portmaster man page. -- 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: apropos returning same item twice
On Sunday 26 September 2010, Steven Friedrich wrote: Another check is that the output of manpath(1) doesn't include /usr/X11R6/man. manpath /usr/share/man:/usr/local/man:/usr/local/kde4/man:/usr/share/open ssl/man: /usr/local/lib/perl5/5.12.2/man:/usr/local/lib/perl5/5.12.2/perl/ man Ok. There's also: %man -a -w mysql to see the origins of the multiple man pages, although it seems that you may have already confirmed the /usr/X11R6 path connection. From what you've presented so far I'd say it's looking like a problem man -a -w mysql /usr/local/man/man1/mysql.1.gz /usr/X11R6/man/man1/mysql.1.gz Same here - until I realised that I still had /usr/X11R6/bin in $PATH, left over from the days before /usr/X11R6 was a link to /usr/local. Removing /usr/X11R6/bin from $PATH fixed it for me. According to the man page for manpath it tries to determine the user's manpath from a set of system defaults and the user's PATH. -- 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: GUI Suggested?
On Thursday 23 September 2010, Andrea Venturoli wrote: After years of KDE3 I tried KDE4 and switched back in half a day. I found it crawling slowly, with continuous crashes, rendering bugs and missing features... Of course, YMMV. That's very similar to my experience too but I'm getting the feeling that I might have to move over to KDE4 before much longer due to reduced KDE3 support with some of the apps: 1) There's a problem with gnupg 2.0.9 and Kgpg with KDE 3.5 which prevents kgpg parsing the keyring https://bugs.kde.org/188473. Apparently the code is totally different from what is in KDE4 and is scattered over several places so fixing this for KDE3 will (understandably) not be done. I've stuck with gnupg-2.0.9_3 which is still working OK but the recent removal of libassuan-1 causes a problem if I ever need to rebuild gnupg-2.0.9_3 2) kaffeine-1.0_1 now depends on some KDE4 libraries, I suspect other apps will follow in due course with the result that I'll start to see more bloat and potential conflicts. When I first tried KDE4 it was much slower than KDE3, have things improved sufficiently since then for me to think about upgrading? -- 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: GUI Suggested?
On Thursday 23 September 2010, Adam Vande More wrote: If you tried on KDE 4.1, 4.2, then yes things have improved a lot. 4.3 was pretty big update in terms of stability, and 4.4 has been far more solid than not. All the base KDE apps seem to work appropriately, at least the ones I use. However in my use while KDE4 was unstable early, it was always faster than 3 at least when an app wasn't hung ;). Also for me, I went back and forth between 3 and 4 several times before finally sticking with 4. The UI does take some getting used too. I think the version I tried was 4.3.1 so it looks like it might be worth giving 4.4 a try on my spare partition. My other problem with upgrading KDE is that I'd like to run both versions for a while until I'm happy, dual booting into one of 2 different FreeBSD systems but using the same /home partition. KMail seems to use different directories for storing mail for versions 3 and 4 so how do I go about being able to access all my mail from both systems? -- 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: freebsd-update newbie
On Tuesday 31 August 2010, Kyle Dippery wrote: I've just installed 8.1 from distribution CDs and updated stable with cvsup. I want to enable freebsd-update to keep the system, well, updated. First try, 'freebsd-update fetch' yielded a number of failure messages freebsd-update will only track the RELEASE branch. If you want to track STABLE you'll have to use csup and rebuild the entire system from source each time. Unless you really want to track the latest developments in STABLE you can stay with RELEASE and use freebsd-update to ensure that you get all the security patches. See section 24.5.2 in the FreeBSD Handbook to help you decide if you really need STABLE http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html If you choose to stick with RELEASE then it's worth subscribing to the FreeBSD Security Advisories mailing list and only running freebsd-update after any updates have been announced. http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications -- 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: how do i scp .dotfiles??
On Sunday 29 August 2010, Polytropon wrote: The problem (i. e. a convention) is that .* is not part of *, which includes everything else, even nothing, and the form *.* (that looks like the DOS equivalent of all files) does seem to omit .*; the spaced form * .* would work as it contains * (which does not contain .*) and .* (not in *). :-) The problem with using .* as a wildcard for hidden files is that it will include .. which is almost certainly not what you want. For example rm -r .* can be disastrous. A safer wildcard for hidden dotfiles and everything else could be .[^.]* * -- 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: Is KDE 4.4.5 on FreeBSD 8.1 this bad?
On Sunday 01 August 2010, Michel Talon wrote: Firefox3 also chokes on Google maps while seamonkey and konqueror work ok. There are obviously javascript problems. Finally i have installed flash10 with the pluginwrapper, and it works wonderfully fine in seamonkey and firefox3, including sound, fullscreen images, etc. But konqueror doesn't work with Flash, for an unknown reason. Hence seamonkey is the only browser which allows me to look at google maps with street view. Are you by any chance using the flashblock extension with firefox? This extension has a problem with streetview and you need to add maps.google.com to the flashblock whitelist. -- 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
Problems with first attempts to use ZFS
Thinking that it's about time to learn a bit about ZFS I started with the tutorial at http://flux.org.uk/howto/solaris/zfs_tutorial_01 I'm currently running 8.1-RELEASE i386 with a generic kernel and 3 disk slices, each mirrored across 2 drives with gmirror. I appreciate the current configuration is far from ideal for ZFS but I could use a file based ZFS pool and the reduced performance shouldn't matter for a small learning exercise. Though it appears that running a disk based pool on a gmirror system was not a good thing. First I created a couple of file based pools: mkdir /disk1/z cd /disk1/z dd if=/dev/zero of=disk1 count=128 bs=1m dd if=/dev/zero of=disk2 count=128 bs=1m zpool create trout mirror /disk1/z/disk1 /disk1/z/disk2 zpool list zpool status trout That looked ok, the ZFS filesystem /trout was created and I was able to create data on it with dd if=/dev/zero of=/trout/foo count=32 bs=1m. The next step was to test it by overwriting the first disk label with random data dd if=/dev/random of=/disk1/z/disk1 bs=512 count=1 Then force ZFS to check with the zfs scrub command. zpool scrub trout At this point everything went pear shape, the whole system stopped and I finally had to force a reboot with a hard reset. On rebooting gmirror reported that all 3 slices on one of the drives were degraded and rebuilt them. Subsequent attempts to run zpool commands like list or status just lead to kernel panics followed by gmirror rebuilds on rebooting. How do I clear up this mess either by fixing the existing test ZFS pool or just getting rid of it so that zpool list returns the no pools available message instead of crashing the system. And, yes, I do have backups so I can restore any files which might be needed. -- 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: I donot like using mergemaster ?
On Monday 26 July 2010, zaxis wrote: I want to upgrade my freebsd 8.0 to 8.1. I have read all the steps about upgrading freebsd. I feel mergemaster is difficult to use e.g. which parameters should i use ? (you may wish to use -U or -ai or -Fi) I have the following in /etc/mergemaster.rc instead of having to remember the command line options each time: # Install the new file if it differs only by VCS Id (-F) FREEBSD_ID=yes # # Automatically upgrade files that have not been user modified (-U) AUTO_UPGRADE=yes # # Automatically install files not on the system already (-i) AUTO_INSTALL=yes # # Preserve files that you replace PRESERVE_FILES=yes # # Delete stale files in /etc/rc.d without prompting DELETE_STALE_RC_FILES=yes # # Compare /etc/rc.conf[.local] to /etc/defaults/rc.conf (-C) COMP_CONFS=yes # ## # The following options have no command line overrides ## # # Files to always avoid comparing IGNORE_FILES='/etc/motd /etc/printcap' # # Additional options for diff. This will get unset when using -s. DIFF_OPTIONS='-Bb' # Ignore changes in whitespace -- 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: Convert all packages to ports
On Friday 02 July 2010, Chris Stankevitz wrote: --- On Thu, 7/1/10, Chris Stankevitz chrisstankev...@yahoo.com wrote: Q: Is there a simple way to replace each package with the locally compiled port? portmaster -f -a Ideally the procedure will not ask me any questions Be prepared to answer hundreds of options questions. To take the default option you must press TAB, ENTER to each query. Have fun! Would portmaster -Gfa help ? From the man page: -G prevents the recursive 'make config' (overrides --force-config) -- 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
/usr/sbin/periodic security check changing date format
The daily security check run by /usr/sbin/periodic has started to change the date format when checking suid files with the result that all the files are flagged as changed. On Wednesday I had the following ... curlew.lan setuid diffs: --- /var/log/setuid.today 2010-06-06 09:01:14.0 +0100 +++ /tmp/security.6Np9Q7Bn 2010-06-30 11:30:48.0 +0100 @@ -1,70 +1,70 @@ - 164937 -r-sr-xr-x 1 rootwheel 18560 Jun 1 18:34:35 2010 /bin/rcp [snip] + 164937 -r-sr-xr-x 1 rootwheel 18560 1 Jun 18:34:35 2010 /bin/rcp Anacron wasn't running yesterday so the next report was today when it switched back from day month to month day... curlew.lan setuid diffs: --- /var/log/setuid.today 2010-06-30 11:30:48.0 +0100 +++ /tmp/security.Y7M72oUL 2010-07-02 00:08:44.0 +0100 @@ -1,70 +1,70 @@ - 164937 -r-sr-xr-x 1 rootwheel 18560 1 Jun 18:34:35 2010 /bin/rcp [snip] + 164937 -r-sr-xr-x 1 rootwheel 18560 Jun 1 18:34:35 2010 /bin/rcp And I'm sure I haven't made any changes to the system in the last few days which might cause this format change. -- 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: Staying up to date with security patches
On Friday 02 July 2010, Ed Flecko wrote: Since I will be doing a custom kernel at some point, I won't use freebsd-update, I'm using cvsup instead. The alternative would be to just use the source code patches from the security-advisories mailing list. That way you don't have to rebuild the whole base system each time, though some of the patches will require the kernel to be rebuilt. -- 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
Updating ports - KDE3.5 and phonon
I'm about to upgrade my ports, since it's over 3 months since the last upgrade I'm expecting this to be a mega upgrade. In preparation for this I've run portmaster -na to get all the configs up to date and avoid the need for frequent manual intervention when I run the upgrade. This highlighted a potential problem with multimedia/qt4-phonon === Port directory: /usr/ports/multimedia/qt4-phonon === This port is marked IGNORE === conflicts with multimedia/phonon. You have defined WITH_KDE_PHONON to override Qt4 phonon === If you are sure you can build it, remove the IGNORE line in the Makefile and try again. === Update for qt4-phonon-4.6.1 failed === Aborting update Well WITH_KDE_PHONON might have been defined somewhere, but not by me! Checking with UPDATING shows: WITH_QT_PHONON global knob has been introduced to allow selection between multimedia/qt4-phonon* ports (a bit outdated Phonon, which is shipped with Qt4) and multimedia/phonon* ports. Since KDE SC 4.4 requires fresh Phonon, multimedia/phonon* ports are installed by default. If you don't use KDE, you may set WITH_QT_PHONON=yes in /etc/make.conf and continue to use Qt4 Phonon implementation ports. If you want to use KDE SC 4.4 (or if you want the latest Phonon), do not define WITH_QT_PHONON, delete multimedia/qt4-phonon* ports, and install multimedia/phonon*: If you use portmaster: portmaster -o multimedia/phonon multimedia/qt4-phonon portmaster -o multimedia/phonon-gstreamer multimedia/qt4-phonon-gst I'm using KDE but it's version 3.5 which isn't mentioned above so am I right in assuming that in my case I put WITH_QT_PHONON=yes in /etc/make.conf because I'm not using KDE 4.4, even though I'm using KDE? -- 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: no more possible to use any usb storage device/usb flash drive, when pluged or unpluged
On Saturday 24 April 2010, Aiza wrote: harvey dent wrote: Hi everybody I try to make a functional custom kernel for a i386 machine. Here the uname -a: *FreeBSD k 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 16:02:27 UTC 2010 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386* I maked, and I installed a new kernel. But, there are several problems with it. Under GNOME, any usb hard drive or usb flash drive are no more mounted automaticaly, causing errors, unlike GENERIC kernel. So I have to use *mount *command. [snip] Well the simple answer is you removed something from the new kernel that you shouldn't have. Return to the generic kernel and only remove one or two options and compile and test. cycle through this method until your system finally misbehaves again. Then you know one of the last 2 options has to be kept in the kernel. An alternative to making a copy of GENERIC and then editing it is to create a new file from scratch containing an include GENERIC directive and an appropriate ident along with nooptions and nodevice directives to remove unwanted features and options and device directives to add additional ones, as outlined at the start of section 8.6 of the FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html. The PAE config file provides an example of this approach. This way your kernel file shows only the changes you've made to the standard kernel and should make it easier to identify the cause of problems. -- 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
Which CPUTYPE in make.conf?
I have a AMD Athlon 4850e which is described as Athlon 64 X2 Dual-Core processor. /usr/share/examples/etc/make.conf lists recognised CPU types, but which of athlon64, athlon-mp or athlon-xp is the most appropriate for this CPU? I've been using athlon64 so far without any problems but I don't know if it's the most appropriate choice or if there's even any significant difference between them. -- 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: Copying mirrored partitions - will this work?
On Saturday 20 March 2010, Mike Clarke wrote: I'm currently running 8.0-RELEASE and am considering experimenting with 8.0-STABLE. I'd like to preserve my existing system in case things go pear-shaped so I'll copy the entire system onto a spare slice and then use csup to upgrade the copy to STABLE. Normally I'd go through the steps of bsdlabel, newfs and then dump|restore to create the copy but I'm wondering if I can take advantage of my recently created gmirror to cut down the work. I have two 500GB disks, /dev/ad4 and /dev/ad8, each partitioned into 4 slices of 88, 88, 42 and 259GB. My system is installed on the first slices (ad4s1 and ad8s1) which are mirrored as /dev/mirror/gm0. The second slices (ad4s2 and ad8s2) are currently unused. My thoughts are to temporarily add ad4s2 into gm0 with gmirror insert gm0 ad4s2 and wait for the mirror to synchronise. I should then be able to remove the temporary addition with gmirror remove gm0 /dev/ad4s2 at which point ad4s2 should be a duplicate of the original system and I can then go ahead and create a new mirror with gmirror label -b load gm1 ad4s2 and gmirror insert gm1 ad8s2. After editing /etc/fstab in the new mirror to use gm1 instead of gm0 I should then be able to boot into the system on slice 2 and upgrade it to STABLE while still keeping my original system to fall back to if required. Is this approach of moving disks from one mirror to another workable, or have I missed something that would lead me into deep trouble? I don't mind unduly if I make a mess of the second slice and have to start again but I don't want to lose the contents of my original system on slice 1. I decided to give it a try and the process went through very smoothly. It was much less tedious than bsdlabel - newfs - dump|restore, and quicker too. The mirror synchronised at a bit over 100 MB/sec but dump| restore only gave me about 10 MB/sec. The system has now been running for a bit over a week without any problems with either the original or cloned slices so I'm quite confident that things are OK. -- 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: Copying mirrored partitions - will this work?
On Wednesday 31 March 2010, krad wrote: On 31 March 2010 10:22, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: On Saturday 20 March 2010, Mike Clarke wrote: [snip] I have two 500GB disks, /dev/ad4 and /dev/ad8, each partitioned into 4 slices of 88, 88, 42 and 259GB. My system is installed on the first slices (ad4s1 and ad8s1) which are mirrored as /dev/mirror/gm0. The second slices (ad4s2 and ad8s2) are currently unused. My thoughts are to temporarily add ad4s2 into gm0 with gmirror insert gm0 ad4s2 and wait for the mirror to synchronise. I should then be able to remove the temporary addition with gmirror remove gm0 /dev/ad4s2 at which point ad4s2 should be a duplicate of the original system and I can then go ahead and create a new mirror with gmirror label -b load gm1 ad4s2 and gmirror insert gm1 ad8s2. After editing /etc/fstab in the new mirror to use gm1 instead of gm0 I should then be able to boot into the system on slice 2 and upgrade it to STABLE while still keeping my original system to fall back to if required. Is this approach of moving disks from one mirror to another workable, or have I missed something that would lead me into deep trouble? I don't mind unduly if I make a mess of the second slice and have to start again but I don't want to lose the contents of my original system on slice 1. I decided to give it a try and the process went through very smoothly. It was much less tedious than bsdlabel - newfs - dump|restore, and quicker too. The mirror synchronised at a bit over 100 MB/sec but dump| restore only gave me about 10 MB/sec. [snip] One thing about your dump/restore speed. Did you play around with larger block sizes? Increasing it should give you better throughput. I used 32 MB for the cache size but I expect the reduced speed comes about from the need to find and open a large number of files whereas synchronising the mirror just does a sequential disk to disk copy at block level. -- 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: dd cloning slightly different disks
On Tuesday 30 March 2010, Christoph Kukulies wrote: At the moment I'm copying (dd) from the WD internal disk to the SSD which I had put into an external SATA Icybox. I'm hoping to be able to use my FreeBSD and Windows partitions afterwards somehow, possibly with some geometry tweaking or what. Due to the different disk geometry I'm expecting that the partition table entries will be wrong. Having created problems for myself by doing something similar in the past I'd be wary of using dd for this, http://preview.tinyurl.com/yzckfx5 will take you to Google Groups for the relevant thread in comp.unix.bsd.freebsd.misc. The safe approach would be to use fdisk to create the desired slices on the new disk, use bsdlabel to partition the FreeBSD slice and then use dump|restore to copy the data. You should be able to copy your Windows partition with DriveImage XML, free for private use from http://www.runtime.org/driveimage-xml.htm -- 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: Copying mirrored partitions - will this work?
On Sunday 21 March 2010, Modulok wrote: On 3/20/10, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: [snip] I have two 500GB disks, /dev/ad4 and /dev/ad8, each partitioned into 4 slices of 88, 88, 42 and 259GB. My system is installed on the first slices (ad4s1 and ad8s1) which are mirrored as /dev/mirror/gm0. The second slices (ad4s2 and ad8s2) are currently unused. My thoughts are to temporarily add ad4s2 into gm0 with gmirror insert gm0 ad4s2 and wait for the mirror to synchronise. I should then be able to remove the temporary addition with gmirror remove gm0 /dev/ad4s2 at which point ad4s2 should be a duplicate of the original system and I can then go ahead and create a new mirror with gmirror label -b load gm1 ad4s2 and gmirror insert gm1 ad8s2. After editing /etc/fstab in the new mirror to use gm1 instead of gm0 I should then be able to boot into the system on slice 2 and upgrade it to STABLE while still keeping my original system to fall back to if required. How valuable is your data? In financial terms not very, but still valuable enough to not want to lose it. I recommend you make an offline backup. Yes, I take regular backups but regard them as the emergency parachute and prefer to not put myself in a position where I'm doing something risky and the backup files are the only protection, so I'll be making additional backups anyway. There's a lot of steps in your procedure which introduce room for error. Yes, it's a bit of unknown territory for me but with 6 partitions on the slice it does require fewer potentially dangerous manual steps (like newfs or restore to the wrong device) so looks like an interesting experiment. You could perhaps disconnect one of the hard drive's data cable (same thing). Also, make a backup copy of your geom meta data somewhere. That's a possibility to consider but would result in additional changes to the mirror configuration, something I'd prefer to keep to a minimum. -- 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
Copying mirrored partitions - will this work?
I'm currently running 8.0-RELEASE and am considering experimenting with 8.0-STABLE. I'd like to preserve my existing system in case things go pear-shaped so I'll copy the entire system onto a spare slice and then use csup to upgrade the copy to STABLE. Normally I'd go through the steps of bsdlabel, newfs and then dump|restore to create the copy but I'm wondering if I can take advantage of my recently created gmirror to cut down the work. I have two 500GB disks, /dev/ad4 and /dev/ad8, each partitioned into 4 slices of 88, 88, 42 and 259GB. My system is installed on the first slices (ad4s1 and ad8s1) which are mirrored as /dev/mirror/gm0. The second slices (ad4s2 and ad8s2) are currently unused. My thoughts are to temporarily add ad4s2 into gm0 with gmirror insert gm0 ad4s2 and wait for the mirror to synchronise. I should then be able to remove the temporary addition with gmirror remove gm0 /dev/ad4s2 at which point ad4s2 should be a duplicate of the original system and I can then go ahead and create a new mirror with gmirror label -b load gm1 ad4s2 and gmirror insert gm1 ad8s2. After editing /etc/fstab in the new mirror to use gm1 instead of gm0 I should then be able to boot into the system on slice 2 and upgrade it to STABLE while still keeping my original system to fall back to if required. Is this approach of moving disks from one mirror to another workable, or have I missed something that would lead me into deep trouble? I don't mind unduly if I make a mess of the second slice and have to start again but I don't want to lose the contents of my original system on slice 1. -- 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: dump warning msgs??
On Monday 22 February 2010, Jerry McAllister wrote: I don't know the exact algorithm dump uses for sorting the inodes, but this looks like a file was deleted between the time the list was made and the time dump got to reading it. I expect it's the inode for the temporary snapshot in the .snap directory. According to the man page this snapshot is unlinked as soon as the dump starts. I assume this is immediately after creating the list of inodes to be backed up, in which case it's in the list but no longer available when the data is dumped. I see the expected xxx, got yyy type of message every time I do a restore from a snapshot dump but it's never caused any problems. I've just done a test dump with the -L option and monitored the contents of the partition's .snap directory, a file named dump_snapshot with inode number 4 appeared as I started the dump and then disappeared. I then tried to restore the entire dump to a temporary destination and got a message expected next file 1319089, got 4. As I expected, the .snapshot directory in the dump was empty with no sign of the dump_snapshot file so I'm assuming that restore put out the warning message when it's list of inodes suggested that number 4 should be the next one but the next sequential file in the dump corresponded to inode 1319089. The wording of the message does however suggest that it actually found the file for inode 4 in the dump when the list of inode numbers indicated that the next sequential file should have been 1319089. I was anticipating the message to be expected next file 4, got 1319089 -- 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: dump warning msgs??
On Monday 22 February 2010, Polytropon wrote:
On Mon, 22 Feb 2010 16:37:59 +, Mike Clarke
jmc-freeb...@milibyte.co.uk wrote:
I see the expected xxx, got yyy type of message every time I do a
restore from a snapshot dump but it's never caused any problems.
The message is issued by restore, not by dump. According
to /usr/src/sbin/restore/restore.c, beginning at line 620,
the explaination is:
If we find files on the tape that have no corresponding
directory entries, then we must have found a file that
was created while the dump was in progress. Since we have
no name for it, we discard it knowing that it will be
on the next incremental tape.
This fits the snapshot theory. Use the source, Luke. :-)
Yes, I was aware that it was a message from restore and not dump but I
misunderstood how it came about. I think I can see part of what's
happening now. At line 367 in /usr/src/sbin/dump/main.c we have
snprintf(snapname, sizeof snapname,
%s/.snap/dump_snapshot, mntpt);
snprintf(snapcmd, sizeof snapcmd, %s %s %s,
_PATH_MKSNAP_FFS, mntpt, snapname);
unlink(snapname);
if (system(snapcmd) != 0)
errx(X_STARTUP, Cannot create %s: %s\n,
snapname, strerror(errno));
if ((diskfd = open(snapname, O_RDONLY)) 0) {
unlink(snapname);
errx(X_STARTUP, Cannot open %s: %s\n,
snapname, strerror(errno));
}
unlink(snapname);
... so when we make a dump of e.g. /home we've set snapcmd to the
string mksnap_ffs /home /home/.snap/dump_snapshot [1] and then
execute it to create a snapshot. We then open the snapshot and
immediately unlink it. Although this effectively deletes the snapshot
file from the working filesystem it still exists in the snapshot of the
system (and would appear in a directory listing of the snapshot if it
were to be mounted somewhere). At this point I'm starting to get lost
because dump will use the opened snapshot to traverse the system and
will see .snap/dump_snapshot when it maps the files and directories so
this file should be included in the dump and appear in its contents
list but somehow it's present in the dump (although truncated to a zero
length file) but not mapped to any name. I don't see anywhere in the
code where .snap/dump_snapshot might receive any special treatment to
exclude it from the file list, but finding my way through unfamiliar
code is something I'm definitely not very skilled at so I've probably
overlooked something really obvious. Although it's not really a problem
I'm rather curious to understand just how dump handles this.
[1] I'm also puzzled by the use of the command
mksnap_ffs /home /home/.snap/dump_snapshot. According to the man page
I'd have expected just mksnap_ffs /home/.snap/dump_snapshot but quick
experiments show that both forms appear to produce the same result?
--
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
