Re: fsck_ufs running too often
On Sat, Jun 23, 2012 at 10:15:19PM -0500, Adam Vande More wrote: On Sat, Jun 23, 2012 at 9:54 PM, Jason Hellenthal jhellent...@dataix.netwrote: At one point it was proven that background fsck was not benefitial. Where can we find this proof? It was in the lists amongst many conversations. -- - (2^(N-1)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Masoom Shaikh invited you to Dropbox
This is probably some automated service where he thought he was only sending it to his friends and forgot about the email addresses google gmail automatically adds to your contact list. In general it is best practice not to reply to these sort of events else you subject your inbox to the same sort of torture. On Wed, Apr 20, 2011 at 01:05:28PM +0930, David H wrote: Come on mate, that is low, this is a FreeBSD list, not an advertising list. On Wed, Apr 20, 2011 at 12:15 PM, Dropbox no-re...@dropboxmail.com wrote: Masoom Shaikh wants you to try Dropbox! Dropbox lets you bring all your photos, docs and videos with you anywhere and share them easily. Get started here: http://www.dropbox.com/link/20.f0ibMeMfFG/Njg3MzIzMzY1Nw?src=referrals_bulk9 - The Dropbox Team To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/162777a02941/stable%40freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Regards, J. Hellenthal WWJD pgpOFq1hlGxIK.pgp Description: PGP signature
Re: conf/156396: Make 220.backup-pkgdb cd(1) and backup only the package database.
On Fri, Apr 15, 2011 at 12:57:15PM +0400, Pan Tsu wrote:
J. Hellenthal jh...@dataix.net writes:
[...]
@@ -33,7 +33,8 @@
new_bak_file=`mktemp ${bak_file}-X`
-if tar -cjf ${new_bak_file} $pkg_dbdir; then
+cd $pkg_dbdir/..
+if tar -cjf ${new_bak_file} $(basename $pkg_dbdir); then
Why not use `-s' (substitution) option of bsdtar(1)?
if tar -cjf ${new_bak_file} -s |$pkg_dbdir|| $pkg_dbdir; then
$(basename $pkg_dbdir) is technically wrong as PKG_DBDIR points not to
/var/db but to /var/db/pkg by default and is not guaranteed to contain
`pkg' at the tail, e.g.
I think you misunderstood how this works. You should test it...
With a pkg_dbdir pointing to /var/db/pkg basename strips off /var/db/.
The cd(1) you notice before that line makes sure your in the directory
just before the actual pkg_dbdir so therefore calling tar on $(basename
$pkg_dbdir) tar's up only the actual name of the 'pkg' directory and not
the path before it.
I suppose this could also be achieved simply by:
tar -C $pkg_dbdir/.. -cjf ${new_bak_file} $(basename $pkg_dbdir)
which is equivalent to:
tar -C /var/db/pkg/.. -cvjf /tmp/foo.tbz `basename /var/db/pkg`
'-v' added for show.
But I don't think the author is willing to take any improvements and has
the wrong impression of why the '/..' is where it is and how that
suffices for the same motive behind archiving a direct path.
PS: The PR says this was committed... It was not AFAIK.
--
Regards,
J. Hellenthal
pgpe6VAW3ejRr.pgp
Description: PGP signature
Make 220.backup-pkgdb cd(1) and backup only the package database.
Submitter-Id: current-users
Originator:J. Hellenthal
Organization:
Confidential: no
Synopsis: Make 220.backup-pkgdb cd(1) and backup only the package
database.
Severity: non-critical
Priority: medium
Category: conf
Class: change-request
Release: FreeBSD 8.2-STABLE i386
Environment:
System: FreeBSD 8.2-STABLE #0 r220564M Tue Apr 12 10:02:17 EDT 2011 i386
Description:
Currently the backup script archives a full path starting from '/' and then
strips the leading slash off of the path which is correct. Upon extraction that
full path without the leading slash is extracted in the current directory as
var/db/pkg/contents with the first two and possibly more directories left
empty.
If a user has a different PKG_DBDIR as designated by ports(7) that is larger
this can lead to frustration with the length of emptiness in the archive with
the leading paths.
How-To-Repeat:
Run ( /etc/periodic/daily/220.backup-pkgdb ) and extract the archive located in
/var/backups/
Fix:
This patch makes 220.backup-pkgdb respectifully cd to where the pkgdb is
located and create the archive from the relative path so there is only the
pkgdb directory and contents upon extraction.
http://patches.jhell.googlecode.com/hg/220.backup-pkgdb_cd.patch?r=f60df831e62d64fd336b6c6612a6619eaf17a17f
diff -r aa37d382121b -r 3fbae1ba29a4 etc/periodic/daily/220.backup-pkgdb
--- a/etc/periodic/daily/220.backup-pkgdb
+++ b/etc/periodic/daily/220.backup-pkgdb
@@ -33,7 +33,8 @@
new_bak_file=`mktemp ${bak_file}-X`
- if tar -cjf ${new_bak_file} $pkg_dbdir; then
+ cd $pkg_dbdir/..
+ if tar -cjf ${new_bak_file} $(basename $pkg_dbdir); then
chmod 644 ${new_bak_file}
if [ -e ${bak_file}.2 -a -e ${bak_file} ]; then
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS pool on FreeBSD 8.2-STABLE broken?
On Tue, 29 Mar 2011 14:34, mark@ wrote: On Mon, 28 Mar 2011 13:38:54 -0500 Scot Hetzel wrote: On Mon, Mar 28, 2011 at 1:17 PM, Mark Morley wrote: Hi there, I have a small backup server (8.2-STABLE). ???It boots from ufs and has azfs pool for backups that consists of 8 drives configured as 4 mirrored devices, totally around 2.5 TB. Been working great, no issues, until the past few days when remote rsyncsto it have started to get very slow (it's only at around %50 capacity). ???Rebooting it helps for a while, then it gets slow again. ???But this isn't the problem now... After the last reboot, it froze while booting right at the point where the file system gets mounted. ???No errors, it just doesn't proceed past the ZFS version message. I rebooted single user and tried to access it with zpool status, and the command hangs in the same way. ???Any attempt to access it (zfs list, for example) does the same thing. The disks themselves seem fine. ???They are all connected to a pair of Adaptec RAID controllers (configured as individual drives, with mirroring handled by zfs) and the controller software shows them all to be intact. I disabled zfs in rc.conf and was able to boot, but I can't access the pool. Any ideas on how to diagnose and hopefully repair this? Your going to need to download a recent -CURRENT ISO that contans zfs v28, then you can try to recover the pool as outlined in this post http://opensolaris.org/jive/message.jspa?messageID=445269 Well, what I did was rebuild world and kernel top 9.0-CURRENT and reboot. It was able to see and access the zfs file system immediately without having to import it. I did a zpool upgrade to v28 and all seems well so far. He specifically does not need -9 to get v28 code for this recovery operation. Martin Matuska does a pretty swell job of keeping these [1] up-to-date so in-case something does go wrong it can be fixed fairly quickly without having to go through and rebuild this and that. 1. http://mfsbsd.vx.sk/ -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best first desktop BSD distro
First I would recommend posting to the correct mailing list. Second I would recommend as much googling as your fingers can stand. Third BSD != Linux and this has been discussed in depth in previous articles. Fourth and foremost I would place a pretty good bet that Paris Hilton could setup and run a FreeBSD desktop. Followup-to: questions@ Remove-to: stable@ On Tue, 29 Mar 2011 15:16, jhsu802701@ wrote: Thanks for your thoughts on making the move from Linux to BSD. I'm not making the move because I don't like Linux. Instead, I want to learn BSD. I find that the best way to familiarize myself with a distro is to adopt it as my main distro (for web browsing, email, word processing, etc.). But the challenge of BSD have so far proven too much for me. It would take too long to configure FreeBSD to my liking. I couldn't figure out what to enter in GRUB to multi-boot Linux and BSD. I tried PC-BSD, GhostBSD, and DragonflyBSD in VirtualBox. I've found PC-BSD agonizingly slow to install and operate, and KDE didn't even boot up when I logged in. GhostBSD has too many things that don't work, such as the keyboard on my laptop and my Internet connection on my desktop. DragonflyBSD didn't boot up in Virtualbox. I recommend Linux Mint as a first Linux distro. It's user-friendly, well-established, widely used, includes codecs/drivers that Ubuntu doesn't, and has a Windows-like user interface. For those with older computers, I recommend Puppy Linux or antiX Linux as a first distro. I'm looking for the analogous choice in the BSD world. So what do you recommend as my first desktop BSD distro? What desktop BSD distro is so easy to use that even Paris Hilton can handle it? Please keep in mind that I have a slow Internet connection, and these BSD distros are ENORMOUS. It took some 12-14 hours to download PC-BSD. -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Backup tool fot ZFS with all classic dump(8) fetatures -- what should I use? (or is here any way to make dump -L works well on large FFS2+SU?)
On Mon, 28 Mar 2011 03:20, lev@ wrote: Hello, Freebsd-stable. Now I'm backing up my HOME filesystem with dump(8). It works perfectly for 80GiB FS with many features: snapshot for consistency, levels, nodump flag (my users use it a lot!), ability to extract only one removed file from backup without restoring full FS, simple sctipy wrap-up for levels schedule, etc. On new server I have huge HOME (500GiB). And even if it is filled up only with 25GiB of data, creating snapshot takes about 10 minutes, freeze all I/O, and sometimes FAILS (!!!). I'm thinking to transfer GOME filesystem to ZFS. But I can not find appropriate tools for backing it up. Here is some requirements: (1) One-file (one-stream) backup. Not directory mirror. I need to store it on FTP server and upload with single command. (2) Levels increment backups. Now I have Monthly (0) - Weekly (1,2,3) - daily (4,5,6,7,8,9) scheme. I could afford other schemes, but if they doesn't store full backup every day and doesn't need full backup more often than weekly. (3) Minimum of local metadata. Storing previous backups locally to calculate next one is not appropriate solution. zfs send needs previous snapshots for incremental backup, for example. (4) Working with snapshot (I think, it is trivial in case of ZFS). (5) Backup exclusions should be controlled by users (not super-user) themselves, like nodump flag in case of FFS/dump(8). zfs send can not provide this. I have very responsible users, so full backup now takes only up to 10GiB when all HOME FS is about 25GiB, so it is big help when backup is sent over Internet to other host. (6) Storing of ALL FS-specific information -- ACLs, etc. (7) Free :) Is here something like this for ZFS? zfs send looks promising, EXCEPT item (5) and, maybe, (3) :( gnu tar looks like everything but (6) :( There is information all over the place for this. I would suggest that you take the time and go over the required reading to understand ZFS and its concepts before you jump into conclusions. Here is some docs to start with. http://download.oracle.com/docs/cd/E19253-01/819-5461/index.html http://hub.opensolaris.org/bin/view/Community+Group+zfs/faq http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: install: aibs.ko: No such file or directory
On Mon, 28 Mar 2011 11:25, mdonada@ wrote: Hi Geoge, without the option-j to make the error is exactly the same. You will have to re-build kernel. Start from scratch. -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: .zfs directory: snapshot: Bad file descriptor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 25 Mar 2011 13:10, demelier.david@ wrote: On 21/03/2011 12:23, Olaf Seibert wrote: On my production system (still 8.1, I haven't had time yet to upgrade to 8.2) I have a ZFS. Nightly I make snapshots of each filesystem in it. Suddenly, one of the file systems has no snapshots any more: $ ls -l /tank/vol-fourquid-1/.zfs ls: snapshot: Bad file descriptor total 0 $ ls -l /tank/vol-fourquid-1/.zfs/snapshot ls: /tank/vol-fourquid-1/.zfs/snapshot: Bad file descriptor Snapshots in other file systems seem ok, for example: $ ls -l /home/local/.zfs total 0 dr-xr-xr-x 9 root wheel 9 Oct 21 2009 snapshot/ $ ls -l /home/local/.zfs/snapshot/ total 32 drwxr-xr-x 48 root vb 48 Apr 19 2010 friday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 monday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 saturday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 sunday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 thursday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 tuesday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 wednesday/ zpool status thinks all is ok: $ zpool status pool: tank state: ONLINE status: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 raidz2ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 errors: No known data errors How worried should I be about corruption anyway, say if I unmount and remount the affected file system? At this point I wouldn't be to worried yet, Its for a snapshot directory and as I see you are running cross versions here, not judging that is what is making the difference or the cause of this but can you attempt the following and report back. Provide output from: zfs upgrade ; zpool upgrade ; zdb run: zpool scrub tank And add to the report back the output of: zpool status -v PS: There was a problem with the .zfs directories somewhere around 8.0 8.1 that could cause a crash, core dump and this was fixed in stable before 8.2-RELEASE. I would highly suggest you update your system to a kernel from 8.2-RELEASE to test this as the problem may just up and disappear before your eyes. Even if you just have to extract a 8.2 kernel into boot/testkernel it may be well worth it. I don't know how to manage ZFS filesystem but usually on UFS file system when you have a bad file descriptor you must run fsck(8) manually to check up the disk. Cheers, - -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x89D8547E iQEcBAEBAgAGBQJNjXOpAAoJEJBXh4mJ2FR+uUoH/3kqZ7ff7f4ireFeXEJ5iwwD hK1D6sNxC4oavW54U9Uw/uNrldERxYXOXsKARgs9JR9AMmXYvNGhy29K13vtUP67 9IOI8Q5uhc5ctF4vOFonLdvy8P/JfdDKgYTI2pvPP3JronUigIKqofjWseZZ5vvq Nk9lN5f0GNwUe1j/YVtPwZcntcUoXE2afSiab6QcQPjCfT4K50+VjMMOmzuzqXnE 9/3a4qdr3eCI6gbZrIk/pgZcvhjNuOmElvqZR5qHxo74qO4ZJnZ+5QMwRFKR2bmQ dmLmFC1fGOsonjHDe1o76NpchFmNfkKViBtHSsVubBb+gG1MduET2HL9vhiYuFY= =qbIt -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Firefox startup impacted by distributed.net client
to this that might or might not make a bit of difference to you. Link [1] that has some scheduling changes that were done in HEAD/-CURRENT that were not merged to -STABLE might be able to help you out some \o/. Also, I found in the past adjusting idprio(1) of processes proves to work out quite well for processes you want to just run in the background and not interrupt your day to day momentary work and especially for dnetc works out quite well. Link [2] I have extracted directly from the email out of convenience and applied and compiled directly into my running test kernels already and has no side effects so far with the 2-3 days its been running. 1. http://lists.freebsd.org/pipermail/freebsd-current/2011-January/022270.html 2. http://patches.jhell.googlecode.com/hg/sched-priority.patch -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: WANTED: good server tutorial
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 22 Mar 2011 05:52, erob@ wrote: On 21/03/11 08:31 PM, Jason Hsu wrote: I'm looking for a good step-by-step quick-and-dirty FreeBSD server tutorial for the current stable version. Most of the tutorials I've seen are for outdated versions of FreeBSD. My setup is: Internet - Modem - Firewall/server computer - Ethernet switch - Other computers For an example of what I'd like to see, check out my tutorial for setting up Debian Lenny on the server at http://www.jasonhsu.com/linux-server-debian.html . Is there something analogous for FreeBSD version 7.4? The handbook documentation is probably what you're looking for. http://www.freebsd.org/doc/handbook/ Unofficially, http://www.freebsddiary.org Also has some good information. http://www.bsdtips.org has some pretty nifty tips as well. Officially, There has also been some work done on the forums to, check the website for further information. - -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN -BEGIN PGP SIGNATURE- Comment: THIS SOFTWARE AND/OR CONTENTS IS PROVIDED BY THE AUTHOR ``AS IS'' AND Comment: ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE Comment: IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR Comment: PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY Comment: DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL Comment: DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS Comment: OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) Comment: HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, Comment: STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING Comment: IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE Comment: POSSIBILITY OF SUCH DAMAGE. iQEcBAEBAgAGBQJNiVndAAoJEJBXh4mJ2FR+CDgH+gMYcCv4tkFkHKXSii7oBIr3 9VngYeKEtctwM7BJjSfvgmj1HqrdEgg1UENa8tesy1ixffmKxoarmx7qDVuCo+Ne m8jAomDSkHiKdpt3eTOLRFrjJd7PnuNJKm+ZrgEcbYv7vdZn7hlfsopTDvsdXwuM 56/zTGaET0W7ds4OSg/lMzyhu6Ug3obT9EjZHLNU1TneucWtXpKDBRKaAGa0pDNG HMQwzFRsKy3Rxyj1YcogEoFwp1thwd/WkpMEfTCqHEoHj75mIFGLqeGYjTDKJmME cfaJqod96sNPe+OkUESP9zXTItpYorGP0XuZL0e755W8Tk1EoIgkgR9Nc6LoRZM= =1yWD -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func'
Hello Stable@, Compiling a kernel on stable/8 with DTrace support is failing with the above subject line upon linking kernel.debug. The text leading up to this is: ... ctfconvert -L VERSION -g vers.o linking kernel.debug clock.o(.text+0x84c): In function `clkintr': /usr/src/sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func' And upon inspection of clock.c: #ifdef KDTRACE_HOOKS #include sys/dtrace_bsd.h #endif And in clkintr(): #ifdef KDTRACE_HOOKS /* * If the DTrace hooks are configured and a callback function * has been registered, then call it to process the high speed * timers. */ int cpu = PCPU_GET(cpuid); if (cyclic_clock_func[cpu] != NULL) (*cyclic_clock_func[cpu])(frame); #endif It seems for some odd reason that sys/dtrace_bsd.h is being forgotten when it comes time for linking ? What is going on here ? Id like to just remove the ifdef's for KDTRACE_HOOKS just to get the build to finish but in the case that I want to build another kernel without dtrace I would have to add them back. Anyone have a better fitting solution to this ? Would it be just as good to re-ifdef this to ?WITH_CTF? instead. Anyway... this is latest code from stable/8 on i386. And yes options KDTRACE_HOOKS is in the kernel config. And the command that caused all this: ( make kernel WITH_CTF=1 ) -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 8 Mar 2011 03:29, jhell@ wrote:
Hello Stable@,
Compiling a kernel on stable/8 with DTrace support is failing with the above
subject line upon linking kernel.debug.
The text leading up to this is:
...
ctfconvert -L VERSION -g vers.o
linking kernel.debug
clock.o(.text+0x84c): In function `clkintr':
/usr/src/sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func'
And upon inspection of clock.c:
#ifdef KDTRACE_HOOKS
#include sys/dtrace_bsd.h
#endif
And in clkintr():
#ifdef KDTRACE_HOOKS
/*
* If the DTrace hooks are configured and a callback function
* has been registered, then call it to process the high speed
* timers.
*/
int cpu = PCPU_GET(cpuid);
if (cyclic_clock_func[cpu] != NULL)
(*cyclic_clock_func[cpu])(frame);
#endif
It seems for some odd reason that sys/dtrace_bsd.h is being forgotten when
it comes time for linking ? What is going on here ?
Id like to just remove the ifdef's for KDTRACE_HOOKS just to get the build to
finish but in the case that I want to build another kernel without dtrace I
would have to add them back. Anyone have a better fitting solution to this ?
Would it be just as good to re-ifdef this to ?WITH_CTF? instead.
Anyway... this is latest code from stable/8 on i386. And yes options
KDTRACE_HOOKS is in the kernel config.
And the command that caused all this:
( make kernel WITH_CTF=1 )
In light of this I decided to just remove the effected section of clock.c
and move forward as this part of the kernel with DTrace is not what I am
looking into.
Attached is a small patch that removes it in case someone else comes
across the same thing and needs a quick workaround.
- --
Regards,
J. Hellenthal
(0x89D8547E)
JJH48-ARIN
-BEGIN PGP SIGNATURE-
Comment: THIS SOFTWARE AND/OR CONTENTS IS PROVIDED BY THE AUTHOR ``AS IS'' AND
Comment: ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
Comment: IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
Comment: PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
Comment: DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
Comment: DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
Comment: OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
Comment: HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
Comment: STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
Comment: IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
Comment: POSSIBILITY OF SUCH DAMAGE.
iQEcBAEBAgAGBQJNdfSCAAoJEJBXh4mJ2FR+K18H/A1KD0Ki1GR696dCvn2iJByH
ym2nrsREjdVzFS2P7tW5PO0fmIc8eiFvqimeKHjexDS9JUH+3ybJ2ccF8JqHrR50
G/lNluptzLibPsqQY3+l/EsOUe//8NZUrUYV0ymOGfMsO5v49fBIfSKAT3JBFmY7
nq8wXMP5ncP8cjGdT6abSryIHmXVxY+E2R2DUOyfmbwZ+J/8fjfNEqxZta+Vc2Bv
N2BJlEW1eJQBHrq2YuEM3iMBGqRkYywaG7hAWnJXXGUf+/8A/B3SgE1zLBlyCbfB
osUjJE/AA7TtBawG6b5V10GCBSMxLaFdhaEzzyd4MtrRPnhuFWsjnPi4ACqnrhc=
=3a8e
-END PGP SIGNATURE-changeset: 947:6dc8de7b9735
branch: DataIX
tag: tip
user:J. Hellenthal jh...@dataix.net
date:Tue Mar 08 03:56:34 2011 -0500
summary: clkintr removal of cyclic_clock_func KDTRACE_HOOKS
diff -r b8f7392deaf6 -r 6dc8de7b9735 sys/x86/isa/clock.c
--- a/sys/x86/isa/clock.c Mon Mar 07 13:06:50 2011 -0500
+++ b/sys/x86/isa/clock.c Tue Mar 08 03:56:34 2011 -0500
@@ -179,17 +179,6 @@
KASSERT(using_lapic_timer == LAPIC_CLOCK_NONE,
(clk interrupt enabled with lapic timer));
-#ifdef KDTRACE_HOOKS
- /*
-* If the DTrace hooks are configured and a callback function
-* has been registered, then call it to process the high speed
-* timers.
-*/
- int cpu = PCPU_GET(cpuid);
- if (cyclic_clock_func[cpu] != NULL)
- (*cyclic_clock_func[cpu])(frame);
-#endif
-
if (using_atrtc_timer) {
#ifdef SMP
if (smp_started)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 8 Mar 2011 04:18, jhell@ wrote: On Tue, 8 Mar 2011 03:29, jhell@ wrote: Hello Stable@, Compiling a kernel on stable/8 with DTrace support is failing with the above subject line upon linking kernel.debug. The text leading up to this is: ... ctfconvert -L VERSION -g vers.o linking kernel.debug clock.o(.text+0x84c): In function `clkintr': /usr/src/sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func' And upon inspection of clock.c: #ifdef KDTRACE_HOOKS #include sys/dtrace_bsd.h #endif And in clkintr(): #ifdef KDTRACE_HOOKS /* * If the DTrace hooks are configured and a callback function * has been registered, then call it to process the high speed * timers. */ int cpu = PCPU_GET(cpuid); if (cyclic_clock_func[cpu] != NULL) (*cyclic_clock_func[cpu])(frame); #endif It seems for some odd reason that sys/dtrace_bsd.h is being forgotten when it comes time for linking ? What is going on here ? Id like to just remove the ifdef's for KDTRACE_HOOKS just to get the build to finish but in the case that I want to build another kernel without dtrace I would have to add them back. Anyone have a better fitting solution to this ? Would it be just as good to re-ifdef this to ?WITH_CTF? instead. Anyway... this is latest code from stable/8 on i386. And yes options KDTRACE_HOOKS is in the kernel config. And the command that caused all this: ( make kernel WITH_CTF=1 ) In light of this I decided to just remove the effected section of clock.c and move forward as this part of the kernel with DTrace is not what I am looking into. Attached is a small patch that removes it in case someone else comes across the same thing and needs a quick workaround. To my best belief the cause is this i386 build is being done without device apic that includes I/O APIC (local_apic.c) which defines in a ifdef KDTRACE_HOOKS ( cyclic_clock_func_t cyclic_clock_func[MAXCPU]; ). Since the lack of I/O APIC being used, sys/x86/isa/clock.c needs its own definition of the same cyclic_clock_func, so I have added this in the same way that its implemented in local_apic.c to clock.c and the build succeeds and is usable. Would it be best to just move cyclic_clock_func definition to dtrace_bsd.h instead ? and remove the definition in local_apic.c ? Additional references: ( Thanks to rwatson@ ) http://fxr.watson.org/fxr/ident?v=FREEBSD8i=cyclic_clock_func Attached is the patch that solved this here but its just adding another definition that could probably be avoided by adding it somewhere else. - -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN -BEGIN PGP SIGNATURE- Comment: THIS SOFTWARE AND/OR CONTENTS IS PROVIDED BY THE AUTHOR ``AS IS'' AND Comment: ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE Comment: IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR Comment: PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY Comment: DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL Comment: DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS Comment: OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) Comment: HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, Comment: STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING Comment: IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE Comment: POSSIBILITY OF SUCH DAMAGE. iQEcBAEBAgAGBQJNdkkMAAoJEJBXh4mJ2FR+8j4H/3qcymOBXvbMj2fqILJA/2xx Xj+Og+INWT+3NAM95Ljeq375lLeV0h3FzXUKrHB+z/bQlY8NYdBdZHOtEUWl1ZvV 5W5RGAncSJq1cBU+EMOoGprvmwWaNIYIHJUUHSpSrJbhwdW53unP285ts4bqvk0I eirtOitgmaiyOzBpJAIfDBBWU7RgQWCc/IFsm6GAU90JmjATy65kEeBtba6fNVcV SlHqu5OmtuVN6eHEq/rf3Ai8jGktwvuS9Flgf4rM+u/tZTA1nC9cfo97Rbtek9TH lQ/yZe9U7Wz4OFSdidMoY1nJN3CYisp3Kq+gqabsd3XDkJQQiXcBIIh61hnnjog= =tC6l -END PGP SIGNATURE-changeset: 952:5eb7de8dcdc0 branch: DataIX tag: tip user:J. Hellenthal jh...@dataix.net date:Tue Mar 08 08:20:28 2011 -0500 summary: cyclic_clock_func_t cyclic_clock_func[MAXCPU]; definition. diff -r e1c8a20eb4b2 -r 5eb7de8dcdc0 sys/x86/isa/clock.c --- a/sys/x86/isa/clock.c Tue Mar 08 08:16:59 2011 -0500 +++ b/sys/x86/isa/clock.c Tue Mar 08 08:20:28 2011 -0500 @@ -82,6 +82,7 @@ #ifdef KDTRACE_HOOKS #include sys/dtrace_bsd.h +cyclic_clock_func_tcyclic_clock_func[MAXCPU]; #endif #defineTIMER_DIV(x) ((i8254_freq + (x) / 2) / (x)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func'
On Tue, 8 Mar 2011 16:31, jhb@ wrote: On Tuesday, March 08, 2011 10:19:30 am J. Hellenthal wrote: On Tue, 8 Mar 2011 04:18, jhell@ wrote: On Tue, 8 Mar 2011 03:29, jhell@ wrote: Hello Stable@, Compiling a kernel on stable/8 with DTrace support is failing with the above subject line upon linking kernel.debug. The text leading up to this is: ... ctfconvert -L VERSION -g vers.o linking kernel.debug clock.o(.text+0x84c): In function `clkintr': /usr/src/sys/x86/isa/clock.c:189: undefined reference to `cyclic_clock_func' And upon inspection of clock.c: #ifdef KDTRACE_HOOKS #include sys/dtrace_bsd.h #endif And in clkintr(): #ifdef KDTRACE_HOOKS /* * If the DTrace hooks are configured and a callback function * has been registered, then call it to process the high speed * timers. */ int cpu = PCPU_GET(cpuid); if (cyclic_clock_func[cpu] != NULL) (*cyclic_clock_func[cpu])(frame); #endif It seems for some odd reason that sys/dtrace_bsd.h is being forgotten when it comes time for linking ? What is going on here ? Id like to just remove the ifdef's for KDTRACE_HOOKS just to get the build to finish but in the case that I want to build another kernel without dtrace I would have to add them back. Anyone have a better fitting solution to this ? Would it be just as good to re-ifdef this to ?WITH_CTF? instead. Anyway... this is latest code from stable/8 on i386. And yes options KDTRACE_HOOKS is in the kernel config. And the command that caused all this: ( make kernel WITH_CTF=1 ) In light of this I decided to just remove the effected section of clock.c and move forward as this part of the kernel with DTrace is not what I am looking into. Attached is a small patch that removes it in case someone else comes across the same thing and needs a quick workaround. To my best belief the cause is this i386 build is being done without device apic that includes I/O APIC (local_apic.c) which defines in a ifdef KDTRACE_HOOKS ( cyclic_clock_func_t cyclic_clock_func[MAXCPU]; ). Since the lack of I/O APIC being used, sys/x86/isa/clock.c needs its own definition of the same cyclic_clock_func, so I have added this in the same way that its implemented in local_apic.c to clock.c and the build succeeds and is usable. Would it be best to just move cyclic_clock_func definition to dtrace_bsd.h instead ? and remove the definition in local_apic.c ? I think DTrace requires the local APIC to work as it hooks directly into the local APIC timer interrupt IIRC. I was starting to think that myself but after adding the above to clock.c it fixed the issue I was seeing. It appears that clock.c is providing enough of a interrupt to at least hotkernel and dtruss + procsystime. hotkernel ... kernel`bzero 28 0.1% kernel`copyout 31 0.1% kernel`syscallret 31 0.1% kernel`uma_zfree_arg 33 0.1% kernel`fget_unlocked 35 0.1% kernel`cpu_fetch_syscall_args 37 0.1% kernel`sopoll_generic 39 0.1% kernel`uma_zalloc_arg 41 0.1% kernel`poll44 0.1% kernel`copyin 48 0.1% kernel`soreceive_generic 60 0.1% kernel`kern_select 66 0.2% kernel`syscallenter93 0.2% kernel`sched_idletd 135 0.3% kernel`spinlock_exit 337 0.8% kernel`acpi_cpu_c1 40525 95.1% I would say at least for the tests I ran with this so far it fixes it¿ procsystime ... Elapsed Times for all processes, SYSCALL TIME (ns) getppid 13579 sigreturn 18646 fcntl 27752 getpid 36201 fstat 45574 close 47142 socket 55193 sigpending 86178 mmap 111586 connect 171967 swapcontext 224511 write 360017 sigprocmask 369920 setitimer 409114 sigaction 650495 writev 667841 gettimeofday1480759 ioctl3403788 stat4044830 clock_gettime4704770 __sysctl7789725 read 9526207068 kevent10024305765 _umtx_op10142262643 poll15037340342 select34427328326
Re: New ZFSv28 patchset for 8-STABLE
On 01/02/2011 03:45, Attila Nagy wrote: On 01/02/2011 05:06 AM, J. Hellenthal wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/01/2011 13:18, Attila Nagy wrote: On 12/16/2010 01:44 PM, Martin Matuska wrote: Link to the patch: http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.patch.xz I've used this: http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101223-nopython.patch.xz on a server with amd64, 8 G RAM, acting as a file server on ftp/http/rsync, the content being read only mounted with nullfs in jails, and the daemons use sendfile (ftp and http). The effects can be seen here: http://people.fsn.hu/~bra/freebsd/20110101-zfsv28-fbsd/ the exact moment of the switch can be seen on zfs_mem-week.png, where the L2 ARC has been discarded. What I see: - increased CPU load - decreased L2 ARC hit rate, decreased SSD (ad[46]), therefore increased hard disk load (IOPS graph) Maybe I could accept the higher system load as normal, because there were a lot of things changed between v15 and v28 (but I was hoping if I use the same feature set, it will require less CPU), but dropping the L2ARC hit rate so radically seems to be a major issue somewhere. As you can see from the memory stats, I have enough kernel memory to hold the L2 headers, so the L2 devices got filled up to their maximum capacity. Any ideas on what could cause these? I haven't upgraded the pool version and nothing was changed in the pool or in the file system. Running arc_summary.pl[1] -p4 should print a summary about your l2arc and you should also notice in that section that there is a high number of SPA Mismatch mine usually grew to around 172k before I would notice a crash and I could reliably trigger this while in scrub. What ever is causing this needs desperate attention! I emailed mm@ privately off-list when I noticed this going on but have not received any feedback as of yet. It's at zero currently (2 days of uptime): kstat.zfs.misc.arcstats.l2_write_spa_mismatch: 0 Right but do you have a 'cache' 'l2arc' vdev attached to any pool in the system ? This suggests to me that you do not at this time. If not can you attach a cache vdev and run a scrub on it and monitor the value of that MIB ? -- Regards, jhell,v JJH48-ARIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: New ZFSv28 patchset for 8-STABLE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/01/2011 13:18, Attila Nagy wrote: On 12/16/2010 01:44 PM, Martin Matuska wrote: Link to the patch: http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101215.patch.xz I've used this: http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101223-nopython.patch.xz on a server with amd64, 8 G RAM, acting as a file server on ftp/http/rsync, the content being read only mounted with nullfs in jails, and the daemons use sendfile (ftp and http). The effects can be seen here: http://people.fsn.hu/~bra/freebsd/20110101-zfsv28-fbsd/ the exact moment of the switch can be seen on zfs_mem-week.png, where the L2 ARC has been discarded. What I see: - increased CPU load - decreased L2 ARC hit rate, decreased SSD (ad[46]), therefore increased hard disk load (IOPS graph) Maybe I could accept the higher system load as normal, because there were a lot of things changed between v15 and v28 (but I was hoping if I use the same feature set, it will require less CPU), but dropping the L2ARC hit rate so radically seems to be a major issue somewhere. As you can see from the memory stats, I have enough kernel memory to hold the L2 headers, so the L2 devices got filled up to their maximum capacity. Any ideas on what could cause these? I haven't upgraded the pool version and nothing was changed in the pool or in the file system. Running arc_summary.pl[1] -p4 should print a summary about your l2arc and you should also notice in that section that there is a high number of SPA Mismatch mine usually grew to around 172k before I would notice a crash and I could reliably trigger this while in scrub. What ever is causing this needs desperate attention! I emailed mm@ privately off-list when I noticed this going on but have not received any feedback as of yet. [1] http://bit.ly/fdRiYT - -- Regards, jhell,v JJH48-ARIN -BEGIN PGP SIGNATURE- iQEcBAEBAgAGBQJNH/msAAoJEJBXh4mJ2FR+bFYH/0bBJbLYU5zzbqpUUXX1M/B9 +g8RwQ9Tek4/fxwpD8DNIfkpzO0MvUcx5Nhwld69jk7sSys9IUpYhuYVggcOgavx sl6AwNNUG0XD/spO2RvV3jD4tVbR6TjlSdLCyBG7iPFU2nNB6wZM+UfWxGYwEyUE loOr13Vk4eU2l2cepUwJH0oGu2hsDZ7qR/fTd+d33NfS6/PT43vbCjPNTsnDJeY9 MdeC5vBUPl3AW3iC/5hxBi9WABGMHeAXTolpAtBQVBNi22mINacYFO6FEdfANy9E Xo207Cd6vBmZb8aTs0BFHs5ZdTHUco/iNysaWvzx9TlIWlyyBRgOXgtBweB+6d4= =lcxW -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Signing Request
If you do not need to pgp/gpg sign email message to the lists please don't. I know I probably don't have your pgp public key and a lot more users probably do not either. Please use your best judgment. Thank you and best regards. -- J. Hellenthal jhellent...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Signing Request
On Wed, 2009-09-23 at 11:40 -0400, J. Hellenthal wrote: If you do not need to pgp/gpg sign email message to the lists please don't. I know I probably don't have your pgp public key and a lot more users probably do not either. Please use your best judgment. Thank you and best regards. BTW, it also helps to mitigate messages like this one... robert. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Signing Request
On Wed, 23 Sep 2009 11:40 -, jhellenthal wrote: If you do not need to pgp/gpg sign email message to the lists please don't. I know I probably don't have your pgp public key and a lot more users probably do not either. Please use your best judgment. Thank you and best regards. Alright If I must. Let me explain this email for the uncommon circumstances and big heads on the subject line. This was just a request not an authoritative (must do) and certainly not spam as some have had a concern over. If I do not have your public key in my keyring then I do not want it, do not need it and have no use for it at this time. This keeps my keyring small and manageable. I do not feel the need to explain my process or setup on this matter as this email was intended as just a request as I don't see the need to sign a message to a mailing list when the information that is contained in more than half of the incoming email is not important enough to be signed. For an example of the emails I am referring to (ports@): I am having problems with such/and/such/port/ Why should it be signed ? I understand, shit happens but I don't need to verify that it happened to Random Joe. Now on the other hand I firmly believe that a patch that is submitted by a maintainer or someone @FreeBSD.org should be signed. I am not referring to these emails at all in the last message and I apologize if that was unrecognizable to you. There is a purpose for signing messages that contain information that someone needs to verify is actually from a trusted source but not all information that is transmitted needs to be verified. And that is all I was referring to when saying use your best judgment. I will not be posting back on this subject as I never intended for this to be a off topic matter (just a request). Best regards -- J. Hellenthal (0x87337C16) gmail.com!jhellenthal :wq ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: zpool scrub hangs on 7.2-stable
On Sun, 20 Sep 2009 17:42 -, christof.schulze wrote: Hello, currently I am running a 7.2 stable with zfs v13. Things work nicely except that zpool scrub hangs without disk activity. I do not get any error messages in dmesg or /var/log/messages and therefore I do not know where to look further. Is this a known issue or should I investigate? If the latter is the case I would need some help doing so. % uname -a ~ FreeBSD ccschu935 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue Jul 7 04:56:00 CEST 2009 r...@ccschu935:/usr/obj/usr/src/sys/GENERIC amd64 % zpool status ~ pool: tank state: ONLINE scrub: scrub in progress for 0h3m, 0,00% done, 3370h48m to go config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 ad0s6 ONLINE 0 0 0 ad0s3fONLINE 0 0 0 ad0s3eONLINE 0 0 0 cache mmcsd0UNAVAIL 0 0 0 cannot open errors: No known data errors kind Regards Christof I see you cache is disabled no available. Even though I don't think this should or might be the problem can you remove the device from the pool and re-scrub to see if that relieves the problem. -- Jason J. Hellenthal http://www.DataIX.net/ jas...@dataix.net 0x691411AC - (2^(N-1)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Fixup manpath.config suggestion
Fix manpath.config optional manpath of /usr/X11R6. This has not been a actual path for some time now and is just a symlink to /usr/local which is already in the manpath.config. The attached patch just deletes the referenced lines, it might be better off just commenting them out and adding a comment next to them referring to the symlink usage. -- Jason J. Hellenthal http://www.DataIX.net/ jas...@dataix.net 0x691411AC - (2^(N-1))--- manpath.config.orig 2009-09-14 06:41:11.0 -0400 +++ manpath.config 2009-09-17 17:29:37.088290738 -0400 @@ -17,14 +17,12 @@ # check if the directory exists and if it does, add it to MANPATH # OPTIONAL_MANPATH /usr/local/man -OPTIONAL_MANPATH /usr/X11R6/man # # set up PATH to MANPATH mapping # MANPATH_MAP/bin/usr/share/man MANPATH_MAP/usr/bin/usr/share/man MANPATH_MAP/usr/local/bin /usr/local/man -MANPATH_MAP/usr/X11R6/bin /usr/X11R6/man # # set man locales, if needed # ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Version nomenclature [was RELENG_7 to 8]
On Sat, 15 Aug 2009 01:48:27 -0400 grarpamp grarp...@gmail.com wrote: Wanted to put in a suggestion. Users are constantly confused and asking questions about the FreeBSD version naming scheme, somehow not quite picking it up right, which is which, where to use it, etc. And though I know what it is, it still seems silly to me. Because we've got logical pointers _loosely_ correlating to formal repo tag and branch names. Worst case I've seen was when FreeBSD had 4, 5, 6 all in flux at once. STABLE and CURRENT could only point to two things and there were about 10 potential tags involved. Basically, I'm proposing FreeBSD should relegate the terms STABLE and CURRENT out to the marketing portion of the web team. You can't check them out of any repo as tags, 4 and 5 were 'stable' when 6 was 'current' and so on. CURRENT means nothing more than cvs HEAD or svn trunk or git nonce. So use those terms instead of leading people think they can check out 'CURRENT' or that it has some magical command line, config file or source properties. website: 'The latest snapshots from our FreeBSD-STABLE and FreeBSD-CURRENT branches are also available'... checking out those branch names gets you HEAD. There are references to 7-STABLE, 8-CURRENT and parhaps other bastardizations on a theme :-) in the handbook that are not valid tags. STABLE is pretty much the same way, only more confusing if more than one thing is 'stable'. Back in the 4/5/6 days it could have referred to any number of branches. And on the main page, we now have more buzzwords... 'production' and 'legacy'. In fact, I'd venture that the proper place for such words, CURRENT/STABLE/production/legacy, is only on the release/download/support related pages of the website, with little '-'s to the actual tag they imply. More importanly, with descriptions that say something like which trains are developed/supported when, for how long. ie: why the deserve such words to be applied to them. Anyone who has a need to refer to CURRENT/STABLE is obviously getting beyond the release iso's and into the cvs/svn/git level of things. So just use the right terms then. Encourage people to use proper tags and for reporting bugs and things. They could probably make it into uname somehow. RELENG_x_y_RELEASE RELENG_x_y [date/serial] RELENG_x [date/serial] HEAD/trunk [date/serial] uname: '7.2-STABLE #0 date of compile' isn't quite the same solid reference as RELENG_7 as of yesterdays code. Which is what it is, not the zero-eth 7.2 errata/security/stability commit. And maybe figure out a way that each commit bumps a serial counter in UPDATING or some stampfile or uname so people can report the serial. Or maybe use the git crypto hash thing. FreeBSD needs a crypto hash reference inside the primary source tree anyways, not just on the n steps removed iso's. I dunno, just seen year after year of these questions on the lists :) Thought I'd put at least something out there. Not meant to be a bikeshed or anything. More like something to be addressed by doc project or whatever. Nice document. I believe a lot of people get confused by these situations due to a matter of not using CVS, SVN, etc... etc... and have never heard of tags and such before. While more people have heard of and used these in their own environment at one point and are not used to the scheme that FreeBSD uses. While at some point everyone should come across http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html not everyone has been pointed to it for reference. I feel this document states these very clearly and besides what else are you going to call the development trunk/tree for FreeBSD-STABLE FreeBSD-CURRENT ? call them both trunk ?. This is really based upon a well defined method of development that is fairly easy to understand if pointed in the right direction. A key factor in the what is RELENG_X type of situation is a Am I missing something ?, What branch am I running again ?, What branch should I pick ? and a good answer to that is right in the handbook telling yo u what these are all about. -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: USB mouse not detected on boot of 7-STABLE
On Thu, 13 Aug 2009 13:16:12 -0700 Kevin Oberman ober...@es.net wrote: Date: Thu, 13 Aug 2009 14:32:48 -0500 From: Paul A. Procacci pproca...@datapipe.net Sender: owner-freebsd-sta...@freebsd.org I had the exact same problem. Not only did my mouse not work on boot-up, neither did my usb cable connecting my machine to my modem. The only solution that I tried was upgrading to 8, and presto, worked fine. 8.0 has an all new USB stack (thank HPS and a host of others) and it ROCKS! Hardware that simply would not work on the old stack is operating flawlessly on 8.0-BETA2. One note if you want to try 8.0. You will probably need to update all of your ports to avoid library version mis-matches. Most notably, you need to rebuild any port that uses libusb and it is now a standard system library. Ports linked against the old ports libusb will not work after the upgrade. I suggest upgrading to 8.0, deleting libusb, and then doing a portupgrade -fa (or the portmaster equivalent). -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.netPhone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 Another workaround may be upgrading to 8.0-* and using sysutils/libchk to parse through all your binaries and libs for discrepancies using script(1) to log the output so you have a reference to look back to. If all else fails you can always resort to the method above if your confidence is not very high on this method. And you can always second guess a port and then reinstall it when or if it gives you problems. ( /usr/bin/script /root/libchk_output /usr/local/sbin/libchk ) This process could actually take much more time and intervention than what is actually needed on some minimal systems so I will let you be the judge for your self on whether this may be right for you. Best regards. -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
