9.1 on Dell Vostro Desktop 470 MT
Hi, we are considering a desktop from dell (vostro 470 mt) and I would like to know if someone has experience with freebsd (9.1) and this machine. Regards, Jens -- 23. Hornung 2013, 16:05 Homepage : http://www.jan0sch.de Mount St. Helens should have used earth control. pgpeF9VIy6eGC.pgp Description: PGP signature
Why not simplify Copyright at boot/dmesg?
Why not simplify that: | Copyright (c) 1992-2013 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 | The Regents of the University of California. All rights reserved. | FreeBSD is a registered trademark of The FreeBSD Foundation. | (...) ... into that: | Copyright (c) 1992-2013 The FreeBSD Project. | Copyright (c) 1979-1994 The Regents of the University of California. | FreeBSD is a registered trademark of The FreeBSD Foundation. | (...) Regards, vermaden ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why not simplify Copyright at boot/dmesg?
On Sat, 23 Feb 2013 16:47:10 +0100, vermaden wrote: > Why not simplify that: > > | Copyright (c) 1992-2013 The FreeBSD Project. > | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > | The Regents of the University of California. All rights reserved. > | FreeBSD is a registered trademark of The FreeBSD Foundation. > | (...) > > ... into that: > > | Copyright (c) 1992-2013 The FreeBSD Project. > | Copyright (c) 1979-1994 The Regents of the University of California. > | FreeBSD is a registered trademark of The FreeBSD Foundation. > | (...) Because you need to exclude 1981, 1982, 1984, 1985, 1987 and 1990 which are missing in list of years. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why not simplify Copyright at boot/dmesg?
Od: "Polytropon" Do: "vermaden" ; Wysłane: 17:11 Sobota 2013-02-23 Temat: Re: Why not simplify Copyright at boot/dmesg? > On Sat, 23 Feb 2013 16:47:10 +0100, vermaden wrote: > > Why not simplify that: > > > > | Copyright (c) 1992-2013 The FreeBSD Project. > > | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > | The Regents of the University of California. All rights reserved. > > | FreeBSD is a registered trademark of The FreeBSD Foundation. > > | (...) > > > > ... into that: > > > > | Copyright (c) 1992-2013 The FreeBSD Project. > > | Copyright (c) 1979-1994 The Regents of the University of California. > > | FreeBSD is a registered trademark of The FreeBSD Foundation. > > | (...) > > Because you need to exclude 1981, 1982, 1984, 1985, 1987 and 1990 > which are missing in list of years. :-) It may sound like ignorance, but why we need to exclude them? We do not exclude any years for FreeBSD Project ;) ___ 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: Why not simplify Copyright at boot/dmesg?
On Sat, 23 Feb 2013 18:14:48 +0100, vermaden wrote: > > > Od: "Polytropon" > Do: "vermaden" ; > Wysłane: 17:11 Sobota 2013-02-23 > Temat: Re: Why not simplify Copyright at boot/dmesg? > > > On Sat, 23 Feb 2013 16:47:10 +0100, vermaden wrote: > > > Why not simplify that: > > > > > > | Copyright (c) 1992-2013 The FreeBSD Project. > > > | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > | The Regents of the University of California. All rights > > > reserved. > > > | FreeBSD is a registered trademark of The FreeBSD Foundation. > > > | (...) > > > > > > ... into that: > > > > > > | Copyright (c) 1992-2013 The FreeBSD Project. > > > | Copyright (c) 1979-1994 The Regents of the University of California. > > > | FreeBSD is a registered trademark of The FreeBSD Foundation. > > > | (...) > > > > Because you need to exclude 1981, 1982, 1984, 1985, 1987 and 1990 > > which are missing in list of years. :-) > > It may sound like ignorance, but why we need to exclude them? To be honest: I have no idea. It's just that I noticed this at first sight. I would assume there is some specific legal sense behind this naming and counting convention; "two lawyers, three opinions" might apply. :-) > We do not exclude any years for FreeBSD Project ;) But "The FreeBSD Project" as a copyright holder covers a different time frame than "The Regents of the University of California", so this seems to be some specific difference causing two lines of copyright information. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why not simplify Copyright at boot/dmesg?
On Sat, 23 Feb 2013 17:11:50 +0100 Polytropon wrote: > On Sat, 23 Feb 2013 16:47:10 +0100, vermaden wrote: > > Why not simplify that: > > > > | Copyright (c) 1992-2013 The FreeBSD Project. > > | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > > | 1994 The Regents of the University of California. All rights reserved. > > | FreeBSD is a registered trademark of The FreeBSD Foundation. > > | (...) > > > > ... into that: > > > > | Copyright (c) 1992-2013 The FreeBSD Project. > > | Copyright (c) 1979-1994 The Regents of the University of California. > > | FreeBSD is a registered trademark of The FreeBSD Foundation. > > | (...) > > Because you need to exclude 1981, 1982, 1984, 1985, 1987 and 1990 > which are missing in list of years. :-) There's that, also that copyright message belongs to the Regents of the University of California and unless I misremember one of the license conditions is retaining their copyright notice - altering it would probably be a license violation. -- Steve O'Hara-Smith ___ 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: Why not simplify Copyright at boot/dmesg?
On 02/23/13 12:32, Steve O'Hara-Smith wrote: On Sat, 23 Feb 2013 17:11:50 +0100 Polytropon wrote: On Sat, 23 Feb 2013 16:47:10 +0100, vermaden wrote: Why not simplify that: | Copyright (c) 1992-2013 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, | 1994 The Regents of the University of California. All rights reserved. | FreeBSD is a registered trademark of The FreeBSD Foundation. | (...) ... into that: | Copyright (c) 1992-2013 The FreeBSD Project. | Copyright (c) 1979-1994 The Regents of the University of California. | FreeBSD is a registered trademark of The FreeBSD Foundation. | (...) Because you need to exclude 1981, 1982, 1984, 1985, 1987 and 1990 which are missing in list of years. :-) There's that, also that copyright message belongs to the Regents of the University of California and unless I misremember one of the license conditions is retaining their copyright notice - altering it would probably be a license violation. It seems the regents copyright claims end in 1994. Perhaps some underlying piece of code is still in FreeBSD requiring this notice? -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://copyfree.org/licenses/owl/license.txt ___ 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 svn to checkout a deprecated port.
On Mon, Feb 18, 2013 at 11:23:09PM -0500, Christopher Sean Hilton wrote: > On Tue, Feb 19, 2013 at 11:43:03AM +1030, Shane Ambler wrote: > > On 19/02/2013 05:53, Christopher Sean Hilton wrote: > > > Hi, > > > > > > I need to use svn to checkout the old "security/cfs" port so I can > > > do a one-time transfer of some data off of a USB drive. At the end of > > > the day, I just need the one port so if the cvs repository is > > > available I could also get it that way. In either case, I'm trying to > > > do the equivalent of: > > > > > > $ cvs co -r '2011/10/01' $FreeBSDportsRepo security/cvs > > > > > > in English, I want to checkout security/cvs from ports as it existed > > > on October 1st, 2011 (the port was deprecated on November 1st 2011. > > > > > > > It appears that checking out a deleted path doesn't work even if you > > specify a rev that it exists in. But checking out the parent works. > > I'd check it out to another dir then copy the specific files over. > > > > svn co -r 282000 svn://svn.freebsd.org/ports/head/security/ > > > > You can change the svn.freebsd.org to svn0.us-east.FreeBSD.org or > > svn0.us-west.FreeBSD.org > > > > For reference I went to http://svnweb.freebsd.org/ports and clicked the > > revision number at the top (above the sticky revision box) then tried# > > jumping to a few different rev numbers till I got close to a commit date > > just before 2011/10/01. Once you have the rev you want you can go back > > up to ports (link at top of page) and enter a sticky revision. Then you > > can go to security/cfs and view the files. > > > > Thanks for the quick answers everyone, the trick seems to be three steps: > > # prime the tree with a guess as to the revision that you need. > > svn co -r --depth immediates svn:///security > > # refine the guess using the svn logs. > > cd security/cfs && svn log > > # checkout the revision that you wanted. ( updating didn't work...) > > cd ../.. && rm -rf security && svn co -r svn > In the case of cfs, this also worked: $ svn co -r 282000 --depth immediates svn:///security $ (cd security/cfs && svn log) | less ## the log revealed that the last revision was 281170 $ cd security $ svn up -r 281170 cfs $ cd cfs && su $ make; make install; make package clean Thanks again for the help. -- Chris "There will be an answer, Let it be." e: chris -at- vindaloo -dot- com ___ 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: HAST - detect failure and restore avoiding an outage?
On Fri, Feb 22, 2013 at 12:00:43AM +0200, Mikolaj Golub wrote: > It looks currently logs are only way to detect errors from hastd side. > Here is a patch that adds local i/o error statistics, accessable avia > hastctl: > > http://people.freebsd.org/~trociny/hast.stat_error.1.patch > > hastctl output: > > role: secondary > provname: test > localpath: /dev/md102 > extentsize: 2097152 (2.0MB) > keepdirty: 0 > remoteaddr: kopusha:7771 > replication: memsync > status: complete > dirty: 0 (0B) > statistics: > reads: 0 > writes: 366 > deletes: 0 > flushes: 0 > activemap updates: 0 > local i/o errors: 269 > > Pawel, what do you think about this patch? I'm fine with the patchi except for missing breaks in switch added to hastd/primary.c. I'm also wondering... You count all those errors separately just to print them as one number. If we do that already let's print them separately, eg. local i/o errors: read(0), write(3), delete(5), flush(9) BTW. Why not to count activemap update errors as write and flush errors? -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgpX_5TbRWObv.pgp Description: PGP signature
Re: Why not simplify Copyright at boot/dmesg?
On 2/23/2013 1:10 PM, Joseph A. Nagy, Jr wrote: On 02/23/13 12:32, Steve O'Hara-Smith wrote: On Sat, 23 Feb 2013 17:11:50 +0100 Polytropon wrote: On Sat, 23 Feb 2013 16:47:10 +0100, vermaden wrote: Why not simplify that: | Copyright (c) 1992-2013 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, | 1994 The Regents of the University of California. All rights reserved. | FreeBSD is a registered trademark of The FreeBSD Foundation. | (...) ... into that: | Copyright (c) 1992-2013 The FreeBSD Project. | Copyright (c) 1979-1994 The Regents of the University of California. | FreeBSD is a registered trademark of The FreeBSD Foundation. | (...) Because you need to exclude 1981, 1982, 1984, 1985, 1987 and 1990 which are missing in list of years. :-) Copyright counts for published years. Look at the copyright on a book that's not a first edition, try classic children's books. They'll list several years decades apart. If nothing was published in 1983, there's no new copyright for that year. In 2077, what was released in 1982 will be public domain, and nothing more until 2079. There's that, also that copyright message belongs to the Regents of the University of California and unless I misremember one of the license conditions is retaining their copyright notice - altering it would probably be a license violation. It seems the regents copyright claims end in 1994. Perhaps some underlying piece of code is still in FreeBSD requiring this notice? Perhaps the creation of FreeBSD and the release of 4.4BSD? Nothing from Berkley's been added, so no new copyright. There's little need to incorporate later patches to 4.4BSD because divergences between the 4.4BSD and 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: Why not simplify Copyright at boot/dmesg?
On 02/23/13 15:33, Joshua Isom wrote: On 2/23/2013 1:10 PM, Joseph A. Nagy, Jr wrote: It seems the regents copyright claims end in 1994. Perhaps some underlying piece of code is still in FreeBSD requiring this notice? Perhaps the creation of FreeBSD and the release of 4.4BSD? Nothing from Berkley's been added, so no new copyright. There's little need to incorporate later patches to 4.4BSD because divergences between the 4.4BSD and FreeBSD. Not that I find it an issue, but could whatever is left over be removed? Just a thought, not a concern. -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://copyfree.org/licenses/owl/license.txt ___ 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: Why not simplify Copyright at boot/dmesg?
Thank You all for explanations, it seems logical now ;) Regards, vermaden ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why not simplify Copyright at boot/dmesg?
On Sat, 23 Feb 2013 15:56:46 -0600 "Joseph A. Nagy, Jr" wrote: > On 02/23/13 15:33, Joshua Isom wrote: > > On 2/23/2013 1:10 PM, Joseph A. Nagy, Jr wrote: > > >> It seems the regents copyright claims end in 1994. Perhaps some > >> underlying piece of code is still in FreeBSD requiring this notice? > >> > > > > Perhaps the creation of FreeBSD and the release of 4.4BSD? Nothing from > > Berkley's been added, so no new copyright. There's little need to > > incorporate later patches to 4.4BSD because divergences between the > > 4.4BSD and FreeBSD. It's even simpler than that 4.4 BSD Lite2 was the final release from Berkeley CSRG in 1994. There have been no later patches to 4.4BSD from Berkeley, that was the last release of any kind from CSRG. FreeBSD 2.0 was based on 4.4-Lite, the updates in Lite2 were merged in pretty quickly IIRC. > Not that I find it an issue, but could whatever is left over be removed? > Just a thought, not a concern. I can't think why anyone would want to, and I expect there's a *lot* left over, certainly their copyright notice appears in many files in /usr/src. -- Steve O'Hara-Smith ___ 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: Why not simplify Copyright at boot/dmesg?
On 2/23/2013 4:23 PM, Steve O'Hara-Smith wrote: On Sat, 23 Feb 2013 15:56:46 -0600 "Joseph A. Nagy, Jr" wrote: On 02/23/13 15:33, Joshua Isom wrote: On 2/23/2013 1:10 PM, Joseph A. Nagy, Jr wrote: It seems the regents copyright claims end in 1994. Perhaps some underlying piece of code is still in FreeBSD requiring this notice? Perhaps the creation of FreeBSD and the release of 4.4BSD? Nothing from Berkley's been added, so no new copyright. There's little need to incorporate later patches to 4.4BSD because divergences between the 4.4BSD and FreeBSD. It's even simpler than that 4.4 BSD Lite2 was the final release from Berkeley CSRG in 1994. There have been no later patches to 4.4BSD from Berkeley, that was the last release of any kind from CSRG. FreeBSD 2.0 was based on 4.4-Lite, the updates in Lite2 were merged in pretty quickly IIRC. It would matter when it was released, not merged. If it was merged in 1996 but the code was released in 1994, the copyright's still 1994. Not that I find it an issue, but could whatever is left over be removed? Just a thought, not a concern. I can't think why anyone would want to, and I expect there's a *lot* left over, certainly their copyright notice appears in many files in /usr/src. That also ties in with NIH syndrome. Gnu does that a lot just to make sure they can change to GPLv4 without problems, while Linux is still GPLv2. It's also not just Berkeley, but other people and organizations hold copyrights. From a quick glance, netatalk is by the University of Michigan. Mounting a cd using cd9660, which is still listed as Berkeley, is probably so tested and proven by now, that there would be no benefit to rewriting it other than to change the copyright. ___ 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: Why not simplify Copyright at boot/dmesg?
On 23/02/2013 23:17, Joshua Isom wrote: That also ties in with NIH syndrome. Gnu does that a lot just to make sure they can change to GPLv4 without problems, while Linux is still GPLv2. It's also not just Berkeley, but other people and organizations hold copyrights. From a quick glance, netatalk is by the University of Michigan. Mounting a cd using cd9660, which is still listed as Berkeley, is probably so tested and proven by now, that there would be no benefit to rewriting it other than to change the copyright. Other open source projects require contributors to sign copyright assignment agreements so all the code is under a single owner. -- Bruce Cran ___ 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 kernel
On 22 February 2013 18:56, Andre Goree wrote: > cc1: warnings being treated as errors Need to set NO_WERROR perhaps? -- -- ___ 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"
Strange delays in ZFS scrub or resilver
I have a raidz of three 1 TB SATA drives, in USB enclosures. One of the disks went bad, so I replaced it last night and it's been resilvering ever since. I can watch the activity lights on the disks and it cranks away for a minute or so, then stops for a minute, then cranks for a minute, and so forth. If I do a zpool status while it's stopped, the zpool waits until the I/O resumes, and a ^T shows it waiting for zio->io_cv. I'm running FreeBSD 9.1, amd64 version, totally vanilla install on a mini-itx box with 4GB of RAM. The root/swap disk is an SSD separate from the zfs disks. When the disks are active, top shows about 10% system time and 4% interrupt. When it isn't, top shows about 99.8% idle. The server isn't doing much else, and nothing else currently touches the disks. (They're for remote backup of a system somewhere else, and I have the backup job turned off until resilvering completes.) I'm running this on the console, and there are no disk error messages. Any idea what's going on or how to fix it? I could move the disks to an ESATA enclosure if USB is losing interrupts or something. My recollection is that when I've done a scrub, it does the same thing, work, pause, work, pause. R's, John ___ 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"