Keeping FreeBSD uptodate with svn, freebsd-update complaining
[I wasn't sure what the most appropriate list for this issue is...] Hello! Recently (after the latest OpenSSL security issue) I have updated my FreeBSD install from source. i.e., I have updated my source tree (under /usr/src) with svn and did the buildworld/buildkernel/installkernel/mergemaster/installworld/mergemaster procedure. For completeness: My source tree contains this code revision: URL: https://svn0.us-west.freebsd.org/base/releng/9.1 Repository Root: https://svn0.us-west.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 249029 This was my first time, but I was following the handbook closely and everything seems to have worked just fine. # uname -a FreeBSD XXX 9.1-RELEASE-p2 FreeBSD 9.1-RELEASE-p2 #5 r249029: Wed Apr 3 12:29:28 CEST 2013 root@XXX:/usr/obj/usr/src/sys/FUGLOS amd64 But what I don't understand is the following. Whenever I execute 'freebsd-update fetch' (I had added a 'freebsd-update cron' to my crontab), the output below(!) is generated. It's not clear to me what this actually means: * Why does freebsd-update want to update my system to 9.1-RELEASE-p2, although I _am_ running that version already? * Why does it want to update that specific list of files? This is just a subset of of the the binary files which should have been installed from installworld. What is special about this subset? * What is the proper way to 'resolve' this situation? I would be happy about some insights/pointers/help here! Thank you very much, melanie -- From: Charlie root@XXX Date: Thu, 11 Apr 2013 03:58:36 +0200 To: root Subject: XXX security updates Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree The following files will be updated as part of updating to 9.1-RELEASE-p2: /lib/libc.so.7 /lib/libcrypto.so.6 /rescue/[ /rescue/atacontrol /rescue/atmconfig /rescue/badsect /rescue/bsdlabel /rescue/bunzip2 /rescue/bzcat /rescue/bzip2 /rescue/camcontrol /rescue/cat /rescue/ccdconfig /rescue/chflags /rescue/chgrp /rescue/chio /rescue/chmod /rescue/chown /rescue/chroot /rescue/clri /rescue/cp /rescue/csh /rescue/date /rescue/dd /rescue/devfs /rescue/df /rescue/dhclient /rescue/disklabel /rescue/dmesg /rescue/dump /rescue/dumpfs /rescue/dumpon /rescue/echo /rescue/ed /rescue/ex /rescue/expr /rescue/fastboot /rescue/fasthalt /rescue/fdisk /rescue/fsck /rescue/fsck_4.2bsd /rescue/fsck_ffs /rescue/fsck_msdosfs /rescue/fsck_ufs /rescue/fsdb /rescue/fsirand /rescue/gbde /rescue/geom /rescue/getfacl /rescue/glabel /rescue/gpart /rescue/groups /rescue/gunzip /rescue/gzcat /rescue/gzip /rescue/halt /rescue/head /rescue/hostname /rescue/id /rescue/ifconfig /rescue/init /rescue/ipf /rescue/kenv /rescue/kill /rescue/kldconfig /rescue/kldload /rescue/kldstat /rescue/kldunload /rescue/ldconfig /rescue/link /rescue/ln /rescue/ls /rescue/lzcat /rescue/lzma /rescue/md5 /rescue/mdconfig /rescue/mdmfs /rescue/mkdir /rescue/mknod /rescue/mount /rescue/mount_cd9660 /rescue/mount_msdosfs /rescue/mount_nfs /rescue/mount_ntfs /rescue/mount_nullfs /rescue/mount_udf /rescue/mount_unionfs /rescue/mt /rescue/mv /rescue/nc /rescue/newfs /rescue/newfs_msdos /rescue/nos-tun /rescue/pgrep /rescue/ping /rescue/ping6 /rescue/pkill /rescue/ps /rescue/pwd /rescue/rcorder /rescue/rcp /rescue/rdump /rescue/realpath /rescue/reboot /rescue/red /rescue/rescue /rescue/restore /rescue/rm /rescue/rmdir /rescue/route /rescue/routed /rescue/rrestore /rescue/rtquery /rescue/rtsol /rescue/savecore /rescue/sed /rescue/setfacl /rescue/sh /rescue/spppcontrol /rescue/stty /rescue/swapon /rescue/sync /rescue/sysctl /rescue/tail /rescue/tar /rescue/tcsh /rescue/tee /rescue/test /rescue/tunefs /rescue/umount /rescue/unlink /rescue/unlzma /rescue/unxz /rescue/vi /rescue/whoami /rescue/xz /rescue/xzcat /rescue/zcat /rescue/zfs /rescue/zpool /sbin/restore /sbin/rrestore /usr/bin/dc /usr/bin/dig /usr/bin/ftp /usr/bin/gate-ftp /usr/bin/host /usr/bin/kadmin /usr/bin/login /usr/bin/nslookup /usr/bin/nsupdate /usr/bin/ntpq /usr/bin/openssl /usr/bin/pftp /usr/bin/sftp /usr/bin/slogin /usr/bin/ssh /usr/bin/ssh-add /usr/bin/ssh-agent /usr/bin/telnet /usr/games/factor /usr/lib/libc.a /usr/lib/libc_p.a /usr/lib/libc_pic.a /usr/lib/libcrypto.a /usr/lib/libcrypto_p.a /usr/lib/libfetch.a /usr/lib/libfetch.so.6 /usr/lib/libfetch_p.a /usr/lib/libgssapi_krb5.a /usr/lib/libgssapi_krb5.so.10 /usr/lib/libgssapi_krb5_p.a /usr/lib/libgssapi_ntlm.a /usr/lib/libgssapi_ntlm.so.10 /usr/lib/libgssapi_ntlm_p.a /usr/lib/libhdb.a /usr/lib/libhdb_p.a /usr/lib/libhx509.a /usr/lib/libhx509.so.10 /usr/lib/libhx509_p.a /usr/lib/libkrb5.a
Re: Keeping FreeBSD uptodate with svn, freebsd-update complaining
On 12/04/2013 09:19, Melanie Schulte wrote: [I wasn't sure what the most appropriate list for this issue is...] Hello! Recently (after the latest OpenSSL security issue) I have updated my FreeBSD install from source. i.e., I have updated my source tree (under /usr/src) with svn and did the buildworld/buildkernel/installkernel/mergemaster/installworld/mergemaster procedure. For completeness: My source tree contains this code revision: URL: https://svn0.us-west.freebsd.org/base/releng/9.1 Repository Root: https://svn0.us-west.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 249029 This was my first time, but I was following the handbook closely and everything seems to have worked just fine. # uname -a FreeBSD XXX 9.1-RELEASE-p2 FreeBSD 9.1-RELEASE-p2 #5 r249029: Wed Apr 3 12:29:28 CEST 2013 root@XXX:/usr/obj/usr/src/sys/FUGLOS amd64 But what I don't understand is the following. Whenever I execute 'freebsd-update fetch' (I had added a 'freebsd-update cron' to my crontab), the output below(!) is generated. It's not clear to me what this actually means: * Why does freebsd-update want to update my system to 9.1-RELEASE-p2, although I _am_ running that version already? * Why does it want to update that specific list of files? This is just a subset of of the the binary files which should have been installed from installworld. What is special about this subset? * What is the proper way to 'resolve' this situation? I would be happy about some insights/pointers/help here! Thank you very much, melanie Hi, Melanie, Your main problem here is trying to mix usage of SVN with usage of freebsd-update. You can use either one of those methods but not both. Unless you prefer to build your own, I'd recommend sticking with freebsd-update. It's much simpler and quicker to keep your systems up to date than the alternative. To recover from the mix of files you have from freebsd-update and self-compiled, it should be sufficient to run 'freebsd-update install' This is going to rewrite all the files that freebsd-update knows about that were altered by your self-built update: ie. most of the OS. Definitely make sure you have good backups before doing that. Yes, it may say 'upgrading to 9.1-RELEASE-p2' but that's because it is comparing against the previous version you got from freebsd-update, not what you compiled yourself. The list of files it shows are specifically the files that were changed between FreeBSD 9.1-RELEASE-p1 and 9.1-RELEASE-p2. freebsd-update is fast largely because it only installs the changed bits onto your system. Cheers, Matthew ___ 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 FreeBSD uptodate with svn, freebsd-update complaining
Thank you, Matthew! That answers all of my questions. :-) I've done a freebsd-update install and it seems to have resolved the situation alright. ~ melanie -- M. Schulte -- mail jabber: m...@fuglos.org http://m.fuglos.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[no subject]
Good afternoon, dear FreeBSD enthusiasts. Is there anyone who has attempted to install a TP-LINK TL-WDN4800 p.c.i.-express wireless network interface card? I am using FreeBSD 9.1 on a Hewlett-Packard xw4400 workstation. The card works perfectly under Windows XP. However, it seems that the FreeBSD operating system does not even recognize the existence of the device; at least, I cannot find any mention of it in the dmesg.boot file. Any and all comments or suggestions will be appreciated. Also, many thanks to those of you who have responded to my previous inquiries. Yours truly, Newby Lee P.S. I failed to mention that the integrated circuit is an Atheros AR9380. ___ 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: none
leeoliveshackelf...@surewest.net writes: Good afternoon, dear FreeBSD enthusiasts. Is there anyone who has attempted to install a TP-LINK TL-WDN4800 p.c.i.-express wireless network interface card? I am using FreeBSD 9.1 on a Hewlett-Packard xw4400 workstation. The card works perfectly under Windows XP. However, it seems that the FreeBSD operating system does not even recognize the existence of the device; at least, I cannot find any mention of it in the dmesg.boot file. Any and all comments or suggestions will be appreciated. Also, many thanks to those of you who have responded to my previous inquiries. Yours truly, Newby Lee P.S. I failed to mention that the integrated circuit is an Atheros AR9380. When you asked this yesterday, you got the following response: ---BeginMessage--- [1. text/plain] You'll need to run -CURRENT instead of 9.1, and all the caveats that apply. You'll also need the special HAL that hasn't yet been commited to -CURRENT. There are instructions on the freebsd-wireless mailing list. I'm using that exact card right now. Run `pciconf -lv` and you should see it, but there's no driver in 9.1. On 4/10/2013 3:39 PM, leeoliveshackelf...@surewest.net wrote: Good afternoon, dear FreeBSd enthusiasts. Is there anyone who has attempted to install a TP-LINK TL-WDN4800 p.c.i.-express wireless network interface card? I am using FreeBSD 9.1 on a Hewlett-Packard xw4400 workstation. The card works perfectly under Windows XP. However, it seems that the FreeBSD operating system does not even recognize the existence of the device; at least, I cannot find any mention of it in the dmesg.boot file. Any and all comments or suggestions will be appreciated. Also, many thanks to those of you who have responded to my previous inquiries. Yours truly, Newby Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ---End Message--- ___ 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: none
On Fri, 12 Apr 2013 14:07:30 -0400 Lowell Gilbert articulated: You'll need to run -CURRENT instead of 9.1, and all the caveats that apply. You'll also need the special HAL that hasn't yet been commited to -CURRENT. There are instructions on the freebsd-wireless mailing list. I'm using that exact card right now. Really off-topic, but HAL is now deprecated on many modern systems. Why is FreeBSD continuing to use it? It is being replaced by udev. You would think that FreeBSD-10 would be a perfect time to put HAL to bed and take a more modern approach. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: none
Jerry je...@seibercom.net writes: On Fri, 12 Apr 2013 14:07:30 -0400 Lowell Gilbert articulated: No, I didn't. It was part of an attachment in my message. You'll need to run -CURRENT instead of 9.1, and all the caveats that apply. You'll also need the special HAL that hasn't yet been commited to -CURRENT. There are instructions on the freebsd-wireless mailing list. I'm using that exact card right now. Really off-topic, but HAL is now deprecated on many modern systems. Why is FreeBSD continuing to use it? It is being replaced by udev. You would think that FreeBSD-10 would be a perfect time to put HAL to bed and take a more modern approach. udev is tightly tied to the Linux kernel. I understand why you would refer to Linux as many modern systems, but it's really not available on anything non-Linux, and it's so tightly tied to the Linux kernel device implementation that there's no reasonable way it could be. ___ 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:
On 12.04.2013 19:50, leeoliveshackelf...@surewest.net wrote: Good afternoon, dear FreeBSD enthusiasts. Is there anyone who has attempted to install a TP-LINK TL-WDN4800 p.c.i.-express wireless network interface card? I am using FreeBSD 9.1 on a Hewlett-Packard xw4400 workstation. The card works perfectly under Windows XP. However, it seems that the FreeBSD operating system does not even recognize the existence of the device; at least, I cannot find any mention of it in the dmesg.boot file. Any and all comments or suggestions will be appreciated. Also, many thanks to those of you who have responded to my previous inquiries. Yours truly, Newby Lee P.S. I failed to mention that the integrated circuit is an Atheros AR9380. ___ 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 Have you load ath and wi? http://www.freebsd.org/doc/en/books/handbook/network-wireless.html I don't know, if Atheros AR9380 is supported. https://www.google.de/search?q=tP-LINK+TL-WDN4800+freebsd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: none
On 4/12/2013 1:43 PM, Jerry wrote: Really off-topic, but HAL is now deprecated on many modern systems. Why is FreeBSD continuing to use it? It is being replaced by udev. You would think that FreeBSD-10 would be a perfect time to put HAL to bed and take a more modern approach. It's not the gnu hal/dbus/bloat, it's an Atheros hardware abstraction layer. It's not really that much different than using VFS for file systems instead of going straight to disk. ___ 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
