Is there the equivalent of a Windows "fast format"
James Phillips
anti_spam256 at yahoo.ca
Sat Dec 5 00:04:29 UTC 2009
--- On Fri, 12/4/09, freebsd-questions-request at freebsd.org <freebsd-questions-request at freebsd.org> wrote:
> From: freebsd-questions-request at freebsd.org <freebsd-questions-request at freebsd.org>
> Subject: freebsd-questions Digest, Vol 287, Issue 12
> To: freebsd-questions at freebsd.org
> Received: Friday, December 4, 2009, 1:54 PM
> Send freebsd-questions mailing list
> submissions to
> freebsd-questions at freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> or, via email, send a message with subject or body 'help'
> to
> freebsd-questions-request at freebsd.org
>
> You can reach the person managing the list at
> freebsd-questions-owner at freebsd.org
>
> When replying, please edit your Subject line so it is more
> specific
> than "Re: Contents of freebsd-questions digest..."
>
>
> Today's Topics:
>
> 1. Hardware migration and upgrade from
> 6.3 to 8.0 advice
> (Achilleas Mantzios)
> 2. Re: Hardware migration and upgrade
> from 6.3 to 8.0 advice
> (Frank Wissmann)
> 3. Re: Hardware migration and upgrade
> from 6.3 to 8.0 advice
> (Adam Vande More)
> 4. Re: Hardware migration and upgrade
> from 6.3 to 8.0 advice
> (Robert Huff)
> 5. Re: malformed man pages (Sagara
> Wijetunga)
> 6. recovering data from this disk (Tom
> Worster)
> 7. Re: Newbie questions (updating, ports,
> etc.) (Richard Mace)
> 8. FreeBSD 8.0 not detecting hot swap
> drive insertion (Rob)
> 9. Re: FreeBSD 8.0 not detecting hot swap
> drive insertion
> (Steve Polyack)
> 10. Re: FreeBSD 8.0 not detecting hot swap drive
> insertion (Rob)
> 11. Re: malformed man pages (Boris Samorodov)
> 12. GEOM: ad0s1: geometry does not match label
> (255h,63s !=
> 16h,63s). (Alexandre L.)
> 13. Wireless network control (Sean Cavanaugh)
> 14. Re: Hardware migration and upgrade from 6.3 to
> 8.0 advice
> (Achilleas Mantzios)
> 15. PF binat rule issue - feature or bug? (Greg
> Barniskis)
> 16. Re: Wireless network control (Ricardo Jesus)
> 17. SMP and ALTQ_NOPCC (APseudoUtopia)
> 18. Setting devfs rules inside jail (Jasvinder S.
> Bahra)
> 19. Re: Wireless network control (Roland Smith)
> 20. Re: "Last login" message (Michael Schaefer)
> 21. 8.0 zfs install (William Taylor)
> 22. Re: recovering data from this disk (Henrik
> Hudson)
> 23. Re: 8.0 zfs install (Matthew Seaman)
> 24. Re: 8.0 zfs install (pete wright)
> 25. Re: recovering data from this disk (Tom
> Worster)
> 26. Is there the equivalent of a Windows "fast
> format" for UFS?
> (Peter Steele)
> 27. Re: [Solved] Having problems burning a DVD (Al
> Plant)
> 28. Re: malformed man pages (Dan Nelson)
> 29. Xorg - no mouse and no keyboard (Paul Schmehl)
> 30. Re: recovering data from this disk (Modulok)
> 31. Re: Is there the equivalent of a Windows "fast
> format" for
> UFS? (Maxim Khitrov)
> 32. FreeBSD 8 portinstall gnome2 failure (Roy
> Stuivenberg)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 Dec 2009 00:57:07 -0800 (PST)
> From: Achilleas Mantzios <mantzios.achill at yahoo.com>
> Subject: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: freebsd-questions at freebsd.org
> Message-ID: <791686.61294.qm at web113006.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
>
>
>
> Hello,
>
> i am facing this situation, where i need to upgrade from my
> 6.3 i386
> system, used as my main workstation, to a new hardware
> based on amd64
> (phenom II x4).
>
>
>
> My current system is alive since 2005, so is full of code,
> scripts,
> configurations,look&feel,ssh keys etc.. that i would
> like to keep
> handy in my new system.
>
> Also, currently i run gmirror, i am mentioning it, in case
> it affects something.
>
>
>
> Since 2005, dealing with programming/support/etc.. i
> haven't done any
> upgrade task in FreeBSD, so i dont feel that confident in
> this regard.
>
>
>
> I could:
>
> a) install a brand new 8.0-RELEASE in the new hardware and
> then
>
> a1) just mount the old disks to the new system or
>
> a2) migrate /home user data directly to the new home dirs
>
> b) migrate all current data to the new hardware,
> kernel/system
> included, and then try to upgrade to 8.0 (by sysinstall or
> makeworld/makekernel)
>
>
>
> So, its a trade-off between pain, correctness,
> effectiveness, and ease of use.
>
>
>
> What would you guys recommend? Which way to go? Any other
> options?
>
--- On Fri, 12/4/09, freebsd-questions-request at freebsd.org <freebsd-questions-request at freebsd.org> wrote:
> From: freebsd-questions-request at freebsd.org <freebsd-questions-request at freebsd.org>
> Subject: freebsd-questions Digest, Vol 287, Issue 12
> To: freebsd-questions at freebsd.org
> Received: Friday, December 4, 2009, 1:54 PM
> Send freebsd-questions mailing list
> submissions to
> freebsd-questions at freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> or, via email, send a message with subject or body 'help'
> to
> freebsd-questions-request at freebsd.org
>
> You can reach the person managing the list at
> freebsd-questions-owner at freebsd.org
>
> When replying, please edit your Subject line so it is more
> specific
> than "Re: Contents of freebsd-questions digest..."
>
>
> Today's Topics:
>
> 1. Hardware migration and upgrade from
> 6.3 to 8.0 advice
> (Achilleas Mantzios)
> 2. Re: Hardware migration and upgrade
> from 6.3 to 8.0 advice
> (Frank Wissmann)
> 3. Re: Hardware migration and upgrade
> from 6.3 to 8.0 advice
> (Adam Vande More)
> 4. Re: Hardware migration and upgrade
> from 6.3 to 8.0 advice
> (Robert Huff)
> 5. Re: malformed man pages (Sagara
> Wijetunga)
> 6. recovering data from this disk (Tom
> Worster)
> 7. Re: Newbie questions (updating, ports,
> etc.) (Richard Mace)
> 8. FreeBSD 8.0 not detecting hot swap
> drive insertion (Rob)
> 9. Re: FreeBSD 8.0 not detecting hot swap
> drive insertion
> (Steve Polyack)
> 10. Re: FreeBSD 8.0 not detecting hot swap drive
> insertion (Rob)
> 11. Re: malformed man pages (Boris Samorodov)
> 12. GEOM: ad0s1: geometry does not match label
> (255h,63s !=
> 16h,63s). (Alexandre L.)
> 13. Wireless network control (Sean Cavanaugh)
> 14. Re: Hardware migration and upgrade from 6.3 to
> 8.0 advice
> (Achilleas Mantzios)
> 15. PF binat rule issue - feature or bug? (Greg
> Barniskis)
> 16. Re: Wireless network control (Ricardo Jesus)
> 17. SMP and ALTQ_NOPCC (APseudoUtopia)
> 18. Setting devfs rules inside jail (Jasvinder S.
> Bahra)
> 19. Re: Wireless network control (Roland Smith)
> 20. Re: "Last login" message (Michael Schaefer)
> 21. 8.0 zfs install (William Taylor)
> 22. Re: recovering data from this disk (Henrik
> Hudson)
> 23. Re: 8.0 zfs install (Matthew Seaman)
> 24. Re: 8.0 zfs install (pete wright)
> 25. Re: recovering data from this disk (Tom
> Worster)
> 26. Is there the equivalent of a Windows "fast
> format" for UFS?
> (Peter Steele)
> 27. Re: [Solved] Having problems burning a DVD (Al
> Plant)
> 28. Re: malformed man pages (Dan Nelson)
> 29. Xorg - no mouse and no keyboard (Paul Schmehl)
> 30. Re: recovering data from this disk (Modulok)
> 31. Re: Is there the equivalent of a Windows "fast
> format" for
> UFS? (Maxim Khitrov)
> 32. FreeBSD 8 portinstall gnome2 failure (Roy
> Stuivenberg)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 Dec 2009 00:57:07 -0800 (PST)
> From: Achilleas Mantzios <mantzios.achill at yahoo.com>
> Subject: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: freebsd-questions at freebsd.org
> Message-ID: <791686.61294.qm at web113006.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
>
>
>
> Hello,
>
> i am facing this situation, where i need to upgrade from my
> 6.3 i386
> system, used as my main workstation, to a new hardware
> based on amd64
> (phenom II x4).
>
>
>
> My current system is alive since 2005, so is full of code,
> scripts,
> configurations,look&feel,ssh keys etc.. that i would
> like to keep
> handy in my new system.
>
> Also, currently i run gmirror, i am mentioning it, in case
> it affects something.
>
>
>
> Since 2005, dealing with programming/support/etc.. i
> haven't done any
> upgrade task in FreeBSD, so i dont feel that confident in
> this regard.
>
>
>
> I could:
>
> a) install a brand new 8.0-RELEASE in the new hardware and
> then
>
> a1) just mount the old disks to the new system or
>
> a2) migrate /home user data directly to the new home dirs
>
> b) migrate all current data to the new hardware,
> kernel/system
> included, and then try to upgrade to 8.0 (by sysinstall or
> makeworld/makekernel)
>
>
>
> So, its a trade-off between pain, correctness,
> effectiveness, and ease of use.
>
>
>
> What would you guys recommend? Which way to go? Any other
> options?
>
> Thanx in advance!
>
> Please include me in your CC, as i am not subscribed to the
> list.
>
> Achilleas Mantzios
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 04 Dec 2009 14:07:41 +0100
> From: Frank Wissmann <frank.wissmann41 at web.de>
> Subject: Re: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: Achilleas Mantzios <mantzios.achill at yahoo.com>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <4B19099D.4050409 at web.de>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> Achilleas Mantzios schrieb:
>
> Hi!
> >
>
> >
> Hello,
> >
> > i am facing this situation, where i need to upgrade
> from my 6.3 i386
> > system, used as my main workstation, to a new hardware
> based on amd64
> > (phenom II x4).
>
> Well, you know that i386 is Intel, do you? It might work
> just moving the
> old kernel to a 64-bit system but I have no experience with
> it.
> >
> >
> >
> > My current system is alive since 2005, so is full of
> code, scripts,
> > configurations,look&feel,ssh keys etc.. that i
> would like to keep
> > handy in my new system.
> >
> > Also, currently i run gmirror, i am mentioning it, in
> case it affects something.
> >
> >
> >
> > Since 2005, dealing with programming/support/etc.. i
> haven't done any
> > upgrade task in FreeBSD, so i dont feel that confident
> in this regard.
> >
> >
> >
> > I could:
> >
> > a) install a brand new 8.0-RELEASE in the new hardware
> and then
> >
> > a1) just mount the old disks to the new system
> or
> >
> > a2) migrate /home user data directly to the new
> home dirs
> >
> > b) migrate all current data to the new hardware,
> kernel/system
> > included, and then try to upgrade to 8.0 (by
> sysinstall or
> > makeworld/makekernel)
>
> Item b) is not recommended. There are so many changes AFAIK
> that it is
> no clear update. You might do so but then you should update
> the
> following way from 6.3 - 7.0 - 7.1 - 7.2 - 8.0 as was
> recommended on
> this list earlier (search the archives, please, for further
> details if
> you choose this way).
> For me, a clean install of 8.0 and a move from the old data
> to the fresh
> install is better. Use a2) !
>
> Greetings Frank
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 4 Dec 2009 07:36:19 -0600
> From: Adam Vande More <amvandemore at gmail.com>
> Subject: Re: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: Achilleas Mantzios <mantzios.achill at yahoo.com>
> Cc: freebsd-questions at freebsd.org
> Message-ID:
> <6201873e0912040536y69d278c9o5bf63d17015894f9 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, Dec 4, 2009 at 2:57 AM, Achilleas Mantzios <
> mantzios.achill at yahoo.com>
> wrote:
>
> >
> >
> >
> Hello,
> >
> > i am facing this situation, where i need to upgrade
> from my 6.3 i386
> > system, used as my main workstation, to a new hardware
> based on amd64
> > (phenom II x4).
> >
> >
> >
> > My current system is alive since 2005, so is full of
> code, scripts,
> > configurations,look&feel,ssh keys etc.. that i
> would like to keep
> > handy in my new system.
> >
> > Also, currently i run gmirror, i am mentioning it, in
> case it affects
> > something.
> >
> >
> >
> > Since 2005, dealing with programming/support/etc.. i
> haven't done any
> > upgrade task in FreeBSD, so i dont feel that confident
> in this regard.
> >
> >
> >
> > I could:
> >
> > a) install a brand new 8.0-RELEASE in the new hardware
> and then
> >
> > a1) just mount the old disks to the new system
> or
> >
> > a2) migrate /home user data directly to the new
> home dirs
> >
> > b) migrate all current data to the new hardware,
> kernel/system
> > included, and then try to upgrade to 8.0 (by
> sysinstall or
> > makeworld/makekernel)
> >
> >
> >
> > So, its a trade-off between pain, correctness,
> effectiveness, and ease of
> > use.
> >
> >
> >
> > What would you guys recommend? Which way to go? Any
> other options?
> >
> > Thanx in advance!
> >
> > Please include me in your CC, as i am not subscribed
> to the list.
> >
> > Achilleas Mantzios
> >
> >
> You may want to consider installing from scratch and
> migrating over. This
> would allow you setup zfs and make the move easier.
> Also may want to
> explore run ahci(4) as that can seriously increase disk
> speed although I
> believe many more improvements live in STABLE, not
> RELEASE.
>
> --
> Adam Vande More
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 4 Dec 2009 08:35:58 -0500
> From: Robert Huff <roberthuff at rcn.com>
> Subject: Re: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: Achilleas Mantzios <mantzios.achill at yahoo.com>,
> freebsd-questions at freebsd.org
> Message-ID: <19225.4158.806906.190990 at jerusalem.litteratus.org>
> Content-Type: text/plain; charset=us-ascii
>
>
> Frank Wissmann writes:
>
> > > i am facing this situation, where i need to
> upgrade from my 6.3 i386
> > > system, used as my main workstation, to a
> new hardware based on amd64
> > > (phenom II x4).
> >
> > > b) migrate all current data to the new
> hardware, kernel/system
> > > included, and then try to upgrade to 8.0
> (by sysinstall or
> > > makeworld/makekernel)
> >
> > Item b) is not recommended.
>
> Confirmed. _Highly_ not
> recommended. .0 releases usually
> contain ABI/API changes (among other things) and you don't
> want
> anything getting confused.
>
> > For me, a clean install of 8.0 and a move from
> the old data to
> > the fresh install is better.
>
> To the OP: the machine I'm typing on is
> also AMD Phenom II x4
> (940, if it matters) originally installed with
> 8.0-RC3/amd64.
> Once I got past the "dangerously
> dedicated disk" issue (and
> close relatives) everything went smoothly.
> Of the choices presented, I recommend
> (a1) with the old disk
> set to read-only in hardware. New disks are cheap,
> and this gives
> you a perfect backup for as long as you want it.
>
>
>
> Robert Huff
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 04 Dec 2009 22:02:41 +0800
> From: Sagara Wijetunga <sagara at tomahawk.com.sg>
> Subject: Re: malformed man pages
> To: freebsd-questions at freebsd.org
> Cc: Boris Samorodov <bsam at ipt.ru>
> Message-ID: <4B191681.8050507 at tomahawk.com.sg>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Boris Samorodov wrote:
> > Hi,
> >
> > On Fri, 04 Dec 2009 16:50:31 +0800 Sagara Wijetunga
> wrote:
> >
> >
> >> We have an issue on Tomahawk Desktop (an upcoming
> FreeBSD-based
> >> distro) that all man pages malformed.
> >>
> >
> > What is the base FreeBSD version?
> >
> >
> FreeBSD 7.2
>
> >> Eg. man tar shows as follows:
> >> 1mNAME0m
> >> 1mtar 22m-- format of tape
> archive files
> >>
> >
> >
> >> 1mDESCRIPTION0m
> >> The 1mtar 22marchive
> format collects any number of files,
> >> directories, and
> >>
> >
> > What are your terminal, locale, fonts?
> >
> >
> echo $TERM
> xterm-color
>
> How do I know what locale and fonts are effective?
>
> Our "default" in /etc/login.conf is same as FreeBSD's.
> >> What have we missed?
> >>
> >
> > Well, there were good old days ;-) when the grass was
> green
> > and manual pages were written in plain ASCII. Those
> days
> > passed, welcome to the shiny future. Manual pages
> have
> > colors, belts and whistles and can be viewed only at
> xterm
> > and with some fonts.
> >
> > *sign* bsam, who used a copy-n-paste from DISKLESS(8)
> and
> > lost nfs connectivity.
> >
> >
>
> Regards
> Sagara
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 04 Dec 2009 09:12:37 -0500
> From: Tom Worster <fsb at thefsb.org>
> Subject: recovering data from this disk
> To: "freebsd-questions at freebsd.org"
> <freebsd-questions at freebsd.org>
> Message-ID: <C73E8305.144A5%fsb at thefsb.org>
> Content-Type: text/plain;
> charset="US-ASCII"
>
> any suggestions how to recover data from either of the
> mirrored disks that i
> can't get to boot? the situation is described below.
>
> (i'm assuming, given the silence on this, that making the
> system work after
> the freebsd-update is a lost cause.)
>
>
> On 12/3/09 11:14 AM, "Tom Worster" <fsb at thefsb.org>
> wrote:
>
> > after running freebsd-update -r 8.0-RELEASE upgrade my
> system won't boot. it
> > gets stuck on mountroot and i can't find the magic
> word it wants.
> >
> > the system used to have two sata drives /dev/ad4 and
> ad6. they were
> > partitioned and sliced using the deafaults that
> sysinstall suggested.
> >
> > at the boot prompt, lsdev says:
> >
> > disk devices
> > disk0: BIOS drive C:
> > disk0s1a: FFS
> > disk0s1b: swap
> > disk0s1d: FFS
> > disk0s1e: FFS
> > disk0s1f: FFS
> > disk1: BIOS drive D:
> > disk1s1a: FFS
> > disk1s1b: swap
> > disk1s1d: FFS
> > disk1s1e: FFS
> > disk1s1f: FFS
> >
> > which looks right, although i'm not familiar with the
> "disk" nomenclature.
> >
> > entering ? at mountroot mentions ad4 and ad6.
> >
> > geom_mirror was being used.
> >
> > i've tried saying "load geom_mirror" and/or
> "enable-module geom_mirror" at the
> > boot prompt. neither made any difference.
> >
> > nothing i've said to mountroot works:
> >
> > ufs:/dev/ad4s1a
> > ufs:/dev/ad6s1a
> > ufs:/dev/mirror/gm0s1a
> > ufs:/dev/disk0s1a
> > ufs:/dev/disk1s1a
> >
> > does anyone know the magic word? i'd be very
> grateful.
> >
> > tom
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 4 Dec 2009 16:15:33 +0200
> From: Richard Mace <macerl at telkomsa.net>
> Subject: Re: Newbie questions (updating, ports, etc.)
> To: freebsd-questions at freebsd.org
> Message-ID: <200912041615.33123.macerl at telkomsa.net>
> Content-Type: Text/Plain; charset="us-ascii"
>
> Thanks to all for your detailed and informative replies to
> my questions. I
> have many new things to try out.
>
> > I can't speak for anyone else, but long posts don't
> bother me. I hope
> > > we've clarified things for you. Welcome to
> FreeBSD!
>
> Thanks. Its good to be here!
>
> -Richard
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 04 Dec 2009 08:37:06 -0600
> From: Rob <lists at midsummerdream.org>
> Subject: FreeBSD 8.0 not detecting hot swap drive
> insertion
> To: freebsd-questions at freebsd.org
> Message-ID: <4B191E92.7010007 at midsummerdream.org>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> I'm running a 10 hot-swap SATA disk ZFS pool and recently
> upgraded from
> 7.2 to 8. Since I upgraded, freebsd isn't spinning up
> or recognizing a
> new drive that is inserted. In freebsd 7.[0,2], I
> could remove a drive
> and insert a new one and freebsd would recognize it, spin
> it up, and
> create the device nodes. None of that is happening in
> 8.0, and the only
> way I've found to get it to recognize the disk is to reboot
> the system.
>
> I tried using atacontrol to force freebsd to reinit an ata
> channel, but
> that didn't have any effect. Did something change in
> 8.0 that prevents
> this auto-detection? Is there a way to re-enable it?
>
> Rob
>
>
> ------------------------------
>
> Message: 9
> Date: Fri, 04 Dec 2009 09:49:50 -0500
> From: Steve Polyack <korvus at comcast.net>
> Subject: Re: FreeBSD 8.0 not detecting hot swap drive
> insertion
> To: lists at midsummerdream.org
> Cc: freebsd-questions at freebsd.org
> Message-ID: <4B19218E.70909 at comcast.net>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> Rob wrote:
> > I'm running a 10 hot-swap SATA disk ZFS pool and
> recently upgraded
> > from 7.2 to 8. Since I upgraded, freebsd isn't
> spinning up or
> > recognizing a new drive that is inserted. In
> freebsd 7.[0,2], I could
> > remove a drive and insert a new one and freebsd would
> recognize it,
> > spin it up, and create the device nodes. None of
> that is happening in
> > 8.0, and the only way I've found to get it to
> recognize the disk is to
> > reboot the system.
> >
> > I tried using atacontrol to force freebsd to reinit an
> ata channel,
> > but that didn't have any effect. Did something
> change in 8.0 that
> > prevents this auto-detection? Is there a way to
> re-enable it?
> >
> Are you using the original (7.x) ata(4) driver or the newer
> enhanced
> SATA drivers like ahci(4) or siis(4)? If you're using
> the latter your
> devices will be labeled /dev/ada* instead of
> /dev/ad*. If you are
> indeed using the newer enhanced SATA drivers, you will need
> to use
> camcontrol to reset and rescan the associated SATA
> channels.
>
>
>
> ------------------------------
>
> Message: 10
> Date: Fri, 04 Dec 2009 09:04:25 -0600
> From: Rob <lists at midsummerdream.org>
> Subject: Re: FreeBSD 8.0 not detecting hot swap drive
> insertion
> To: Steve Polyack <korvus at comcast.net>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <4B1924F9.4060409 at midsummerdream.org>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> I don't have any /dev/ada* devices, so I assume I'm using
> the original
> ata driver. I haven't done any kernel customization,
> and am running the
> distribution's kernel (upgraded with the freebsd-update
> tool). Does the
> older driver no longer detect drive insertion?
>
> Rob
>
> Steve Polyack wrote:
> > Rob wrote:
> >> I'm running a 10 hot-swap SATA disk ZFS pool and
> recently upgraded
> >> from 7.2 to 8. Since I upgraded, freebsd
> isn't spinning up or
> >> recognizing a new drive that is inserted. In
> freebsd 7.[0,2], I could
> >> remove a drive and insert a new one and freebsd
> would recognize it,
> >> spin it up, and create the device nodes.
> None of that is happening in
> >> 8.0, and the only way I've found to get it to
> recognize the disk is to
> >> reboot the system.
> >>
> >> I tried using atacontrol to force freebsd to
> reinit an ata channel,
> >> but that didn't have any effect. Did
> something change in 8.0 that
> >> prevents this auto-detection? Is there a way
> to re-enable it?
> >>
> > Are you using the original (7.x) ata(4) driver or the
> newer enhanced
> > SATA drivers like ahci(4) or siis(4)? If you're
> using the latter your
> > devices will be labeled /dev/ada* instead of
> /dev/ad*. If you are
> > indeed using the newer enhanced SATA drivers, you will
> need to use
> > camcontrol to reset and rescan the associated SATA
> channels.
> >
> > _______________________________________________
> > freebsd-questions at freebsd.org
> mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe at freebsd.org"
> >
> >
>
>
> ------------------------------
>
> Message: 11
> Date: Fri, 04 Dec 2009 18:53:18 +0300
> From: Boris Samorodov <bsam at ipt.ru>
> Subject: Re: malformed man pages
> To: Sagara Wijetunga <sagara at tomahawk.com.sg>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <54145809 at bb.ipt.ru>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, 04 Dec 2009 22:02:41 +0800 Sagara Wijetunga wrote:
> > Boris Samorodov wrote:
> > > On Fri, 04 Dec 2009 16:50:31 +0800 Sagara
> Wijetunga wrote:
> > >
> > >> We have an issue on Tomahawk Desktop (an
> upcoming FreeBSD-based
> > >> distro) that all man pages malformed.
> > > What is the base FreeBSD version?
> > FreeBSD 7.2
>
> OK.
>
> > >> Eg. man tar shows as follows: 1mNAME0m 1mtar
> 22m-- format of tape
> > >> archive files
> > >> 1mDESCRIPTION0m The 1mtar 22marchive format
> collects any number of
> > >> files, directories, and
> > >>
> > > What are your terminal, locale, fonts?
> > >
> > echo $TERM xterm-color
>
> OK.
>
> > How do I know what locale and fonts are effective?
>
> % locale
>
> I don't remember how to detect current font, but I know how
> to
> set it up. ;-) I use x11-fonts/dejavu and set it at
> ~/XTerm:
> -----
> XTerm*faceName: DejaVu Sans Mono
> XTerm*faceSize: 12
> -----
>
> --
> WBR, Boris Samorodov (bsam)
> Research Engineer, http://www.ipt.ru Telephone &
> Internet SP
> FreeBSD Committer, http://www.FreeBSD.org The Power To
> Serve
>
>
> ------------------------------
>
> Message: 12
> Date: Fri, 4 Dec 2009 08:24:46 -0800 (PST)
> From: "Alexandre L." <axelbsd at ymail.com>
> Subject: GEOM: ad0s1: geometry does not match label
> (255h,63s !=
> 16h,63s).
> To: FreeBSD Question <freebsd-questions at freebsd.org>
> Message-ID: <517367.85304.qm at web24810.mail.ird.yahoo.com>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
> I have installed my laptop with FreeBSD 8.0-RC1 first (now
> I'm on 8.0-Release-p1) and in dmesg I got this error message
> :
> GEOM: ad0s1: geometry does not match label (255h,63s !=
> 16h,63s).
>
> I have search on the Web about the method to resolv this,
> but I haven't found anything that helps me.
>
> Here the result of #bsdlabel ad0s1
> # /dev/ad0s1:
> 8 partitions:
> #
> size offset
> fstype [fsize bsize bps/cpg]
> a: 1048576 0
> 4.2BSD 0
> 0 0
> b: 2028960 1048576
> swap
>
> c: 117210177 0
> unused 0
> 0 #
> "raw" part, don't edit
> d: 3110912 3077536
> 4.2BSD 0
> 0 0
> e: 1048576 6188448
> 4.2BSD 0
> 0 0
> f: 109973153 7237024 4.2BSD
> 0 0
> 0
>
> And the result of # gpart show
> => 63
> 117210177 ad0 MBR (56G)
> 63
> 117210177 1 freebsd [active]
> (56G)
>
> => 0 117210177
> ad0s1 BSD (56G)
> 0
> 1048576 1 freebsd-ufs
> (512M)
> 1048576 2028960
> 2 freebsd-swap (991M)
> 3077536 3110912
> 4 freebsd-ufs (1.5G)
> 6188448 1048576
> 5 freebsd-ufs (512M)
> 7237024 109973153
> 6 freebsd-ufs (52G)
>
> Thanks for your help,
>
> Alexandre L.
>
>
>
>
>
> ------------------------------
>
> Message: 13
> Date: Fri, 4 Dec 2009 11:28:02 -0500
> From: Sean Cavanaugh <millenia2000 at hotmail.com>
> Subject: Wireless network control
> To: "freebsd-questions at freebsd.org"
> <freebsd-questions at freebsd.org>
> Message-ID: <BAY126-W22B50926CD5C5658A0B975CA930 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
> I am just trying to find out if theres an easier way to do
> this.
>
>
> currently to get wireless to work on my system, i have to
> clone the wireless interface to a wlan0 interface to
> actually do any real connections. My home network uses WPA2
> encryption so i use the wpa-supplicant to set that up, but
> if i go out and about and hit free wifi spots, I have to add
> the info for them into the wpa-supplicant.conf file to get
> it to access it.
>
> keep in mind that ideally I use the latest gnome as my
> desktop. is there an easier tool to do this all with? I
> remember there was an issue with the gnome-network tool that
> it could not actually make any changes in freebsd, but i
> cannot find if that is still true or if it has been fixed.
>
> End goal, I am trying to get this set up to be equally as
> idiot-proof as most linux distros in case i have to hand
> this off to someone a bit less technically inclined.
>
>
> sorry if this is a bit hard to read, i have ADHD so it
> someti..OHLOOKASQUIRREL
>
> -Sean
>
>
>
>
> ------------------------------
>
> Message: 14
> Date: Fri, 4 Dec 2009 07:28:04 -0800 (PST)
> From: Achilleas Mantzios <mantzios.achill at yahoo.com>
> Subject: Re: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: Adam Vande More <amvandemore at gmail.com>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <900056.39583.qm at web113013.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
> Thanx to all.
> I will keep the old machine for
> development/maintenance/support, while
> bulding/testing/migrating the newest versions of software
> in the new hardware.
>
> Up to now, i got the base system/kernel working ok on the
> new beast, and currently installing additional
> distributions. All seem fine.
>
> Achilleas Mantzios
>
> --- On Fri, 12/4/09, Adam Vande More <amvandemore at gmail.com>
> wrote:
>
> From: Adam Vande More <amvandemore at gmail.com>
> Subject: Re: Hardware migration and upgrade from 6.3 to 8.0
> advice
> To: "Achilleas Mantzios" <mantzios.achill at yahoo.com>
> Cc: freebsd-questions at freebsd.org
> Date: Friday, December 4, 2009, 1:36 PM
>
> On Fri, Dec 4, 2009 at 2:57 AM, Achilleas Mantzios <mantzios.achill at yahoo.com>
> wrote:
>
>
>
>
>
>
> Hello,
>
>
>
> i am facing this situation, where i need to upgrade from my
> 6.3 i386
>
> system, used as my main workstation, to a new hardware
> based on amd64
>
> (phenom II x4).
>
>
>
>
>
>
>
> My current system is alive since 2005, so is full of code,
> scripts,
>
> configurations,look&feel,ssh keys etc.. that i would
> like to keep
>
> handy in my new system.
>
>
>
> Also, currently i run gmirror, i am mentioning it, in case
> it affects something.
>
>
>
>
>
>
>
> Since 2005, dealing with programming/support/etc.. i
> haven't done any
>
> upgrade task in FreeBSD, so i dont feel that confident in
> this regard.
>
>
>
>
>
>
>
> I could:
>
>
>
> a) install a brand new 8.0-RELEASE in the new hardware and
> then
>
>
>
> a1) just mount the old disks to the new system or
>
>
>
> a2) migrate /home user data directly to the new home dirs
>
>
>
> b) migrate all current data to the new hardware,
> kernel/system
>
> included, and then try to upgrade to 8.0 (by sysinstall or
>
> makeworld/makekernel)
>
>
>
>
>
>
>
> So, its a trade-off between pain, correctness,
> effectiveness, and ease of use.
>
>
>
>
>
>
>
> What would you guys recommend? Which way to go? Any other
> options?
>
>
>
> Thanx in advance!
>
>
>
> Please include me in your CC, as i am not subscribed to the
> list.
>
>
>
> Achilleas Mantzios
>
>
>
>
> You may want to consider installing from scratch and
> migrating over. This would allow you setup zfs and
> make the move easier. Also may want to explore run
> ahci(4) as that can seriously increase disk speed although I
> believe many more improvements live in STABLE, not RELEASE.
>
>
> --
> Adam Vande More
>
>
>
>
>
>
>
> ------------------------------
>
> Message: 15
> Date: Fri, 04 Dec 2009 10:41:20 -0600
> From: Greg Barniskis <nalists at scls.lib.wi.us>
> Subject: PF binat rule issue - feature or bug?
> To: FreeBSD Questions <freebsd-questions at freebsd.org>
> Message-ID: <4B193BB0.5000806 at scls.lib.wi.us>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> Using 7.2-RELEASE-p4 i386 with GENERIC kernel, I've found
> (the hard way)
> that if I have a pf.conf rule like
>
> nat on $ext_if proto { tcp udp icmp } from $my_subnet \
> to any -> some.public.ip.num
>
> then pfctl will perform the expected expansion of the
> listed protocols
> into three separate NAT rules.
>
> However, if I have a rule like
>
> binat on $ext_if proto { tcp udp icmp } from $server_dmz_ip
> \
> to any -> $server_public_ip
>
> then I will /only/ get one NAT rule, for TCP.
>
> Then things like NTP, DNS and ping will fail, but the
> filtering rules
> that permit such traffic will increment their byte, packet
> and state
> counters like PF is working just fine (and I suppose in
> some sense that
> the filtering part is). But only if I explicitly declare in
> pf.conf a
> separate binat rule for each desired protocol, instead of
> listing them,
> will things work as needed.
>
> Feature or bug? If the former, it is not well documented
> that I could
> see. I expected that a list of protocols for a binat rule
> would just
> work, and pfctl certainly didn't mark it as bad syntax. If
> a bug, is
> this a FreeBSD bug or OpenBSD?
>
>
> ------------------------------
>
> Message: 16
> Date: Fri, 04 Dec 2009 17:05:47 +0000
> From: Ricardo Jesus <ricardo.meb.jesus at gmail.com>
> Subject: Re: Wireless network control
> To: Sean Cavanaugh <millenia2000 at hotmail.com>
> Cc: "freebsd-questions at freebsd.org"
> <freebsd-questions at freebsd.org>
> Message-ID: <4B19416B.5090004 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> Sean Cavanaugh wrote:
> >
> > I am just trying to find out if theres an easier way
> to do this.
> >
> >
> > currently to get wireless to work on my system, i have
> to clone the wireless interface to a wlan0 interface to
> actually do any real connections. My home network uses WPA2
> encryption so i use the wpa-supplicant to set that up, but
> if i go out and about and hit free wifi spots, I have to add
> the info for them into the wpa-supplicant.conf file to get
> it to access it.
> >
> > keep in mind that ideally I use the latest gnome as my
> desktop. is there an easier tool to do this all with? I
> remember there was an issue with the gnome-network tool that
> it could not actually make any changes in freebsd, but i
> cannot find if that is still true or if it has been fixed.
> >
> > End goal, I am trying to get this set up to be equally
> as idiot-proof as most linux distros in case i have to hand
> this off to someone a bit less technically inclined.
> >
> >
> > sorry if this is a bit hard to read, i have ADHD so it
> someti..OHLOOKASQUIRREL
> >
> > -Sean
>
>
> _______________________________________________
> > freebsd-questions at freebsd.org
> mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
> >
> There was a person asking for a similar thing on this same
> list.
>
> I think the subject was something like "ifconfig - GUI
> interface". Have
> a search on the list's archive.
>
>
> ------------------------------
>
> Message: 17
> Date: Fri, 4 Dec 2009 12:12:41 -0500
> From: APseudoUtopia <apseudoutopia at gmail.com>
> Subject: SMP and ALTQ_NOPCC
> To: FreeBSD Questions <freebsd-questions at freebsd.org>
> Message-ID:
> <27ade5280912040912i53f9871cj9502afc941073bef at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hello,
>
> With the improvements in SMP in FreeBSD 8.0, is the
> ALTQ_NOPCC option
> still required? In the handbook and other older
> documentation, it says
> ALTQ_NOPCC is in fact required on SMP systems because the
> TSC is
> unstable. I was wondering if this is still the case after
> the
> improvements done with SMP.
>
> Thanks.
>
>
> ------------------------------
>
> Message: 18
> Date: Fri, 4 Dec 2009 17:07:13 -0000
> From: "Jasvinder S. Bahra" <bbdl21548 at blueyonder.co.uk>
> Subject: Setting devfs rules inside jail
> To: <freebsd-questions at freebsd.org>
> Message-ID:
> <6DBB67443EBF41B2A068C7CBD37621CB at atlantis>
> Content-Type: text/plain; format=flowed;
> charset="iso-8859-1";
> reply-type=original
>
> Hi,
>
> I'm trying to setup CUPS (in a jail) using an old parallel
> port printer on
> my server machine.
>
> I used ezjail to create a jail and the installed CUPS
> within it. I've got
> everything up and running, but i've had to work around some
> issues.
>
> Initially, the CUPS administration website didn't list the
> printer on the
> Add Printer screen. I discovered that this because
> the /dev/lpt0 and
> /dev/lpt0.ctl devices weren't showing up in the jail.
>
> I therefore (on the host system), created a
> /etc/devfs.rules file...
>
> ------------------------------------------------------------
> [devfsrules_jail_pearl=5]
> add include $devfsrules_hide_all
> add include $devfsrules_unhide_basic
> add include $devfsrules_unhide_login
> add path 'lpt*' unhide
> add path 'lpt*' mode 0660 group cups
> ------------------------------------------------------------
>
> I updated the devfs ruleset entry in
> /usr/local/etc/ezjail/pearl_domain.tld,
> and rebooted.
>
> This successfully made the /dev/lpt0 and /dev/lpt0.ctl
> devices visible in
> the jail and assigned them the correct permissions.
>
> Unfortunately, I was seeing an error message on-screen when
> the system was
> booted (when the jails were being started)...
>
> ------------------------------------------------------------
> devfs rule: error converting to integer: cups
> ------------------------------------------------------------
>
> After a moment, I realised what had happened - I installed
> CUPS in a jail,
> not on the host system. Naturally the CUPS group does
> not exist on the host
> so when the system tried to translate the group name to a
> UID, it couldn't
> do so.
>
> I modified the last line of the hosts /dev/devfs.rules line
> to as follows
> (basically removing the 'group cups')...
>
> ------------------------------------------------------------
> add path 'lpt*' mode 0660
> ------------------------------------------------------------
>
> At this point, I thought what I needed to do is setup a
> /etc/devfs.rules
> file in the jail - setting the group ownership in the jail
> where the CUPS
> group exists.
>
> I created a /etc/devfs.rules file *in* the jail...
>
> ------------------------------------------------------------
> [localrules=5]
> add path 'lpt*' group cups
> ------------------------------------------------------------
>
> I also added the following entry in my jail's /etc/rc.conf
> file...
>
> ------------------------------------------------------------
> devfs_system_ruleset="localrules"
> ------------------------------------------------------------
>
> Unfortunately, the group assignment statement never seems
> to get executed.
>
> I've gotten around this by just creating a quick script
> which explicitly
> sets the group ownership, and having the script be executed
> on boot via
> /etc/crontab.
>
> I'm not understanding why the devfs rules aren't being
> applied in the jail
> however. Can anyone help?
>
> If its relevant, i'm using FreeBSD 7.2 (FreeBSD xxx.xxx.xxx
> 7.2-RELEASE-p4
> FreeBSD 7.2-RELEASE-p4 #0: Tue Dec 1 19:05:36 GMT
> 2009
> user at xxx.xxx.xxx:/usr/obj/usr/src/sys/xxx
> i386).
>
> Regards,
>
> Jazz
>
>
>
>
>
> ------------------------------
>
> Message: 19
> Date: Fri, 4 Dec 2009 18:40:35 +0100
> From: Roland Smith <rsmith at xs4all.nl>
> Subject: Re: Wireless network control
> To: Sean Cavanaugh <millenia2000 at hotmail.com>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <20091204174035.GA26429 at slackbox.xs4all.nl>
> Content-Type: text/plain; charset="us-ascii"
>
> On Fri, Dec 04, 2009 at 05:05:47PM +0000, Ricardo Jesus
> wrote:
> > Sean Cavanaugh wrote:
> > >
> > > I am just trying to find out if theres an easier
> way to do this.
> > >
> > >
> > > currently to get wireless to work on my system, i
> have to clone the
> > > wireless interface to a wlan0 interface to
> actually do any real
> > > connections. My home network uses WPA2 encryption
> so i use the
> > > wpa-supplicant to set that up, but if i go out
> and about and hit free wifi
> > > spots, I have to add the info for them into the
> wpa-supplicant.conf file
> > > to get it to access it.
> > >
> > > keep in mind that ideally I use the latest gnome
> as my desktop. is there
> > > an easier tool to do this all with?
>
> Have a look at http://opal.com/freebsd/ports/net-mgmt/wifimgr
> It is in ports; see /usr/ports/net-mgmt/wifimgr
>
> Roland
> --
> R.F.Smith
>
> http://www.xs4all.nl/~rsmith/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email
> much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321
> A725 (KeyID: C321A725)
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 196 bytes
> Desc: not available
> Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20091204/45addc9e/attachment-0001.pgp
>
> ------------------------------
>
> Message: 20
> Date: Fri, 04 Dec 2009 18:43:41 +0100
> From: Michael Schaefer <utf128 at googlemail.com>
> Subject: Re: "Last login" message
> To: Nerius Landys <nlandys at gmail.com>
> Cc: questions at freebsd.org
> Message-ID: <4B194A4D.20802 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 04.12.2009 00:16, Nerius Landys wrote:
> > I was wondering what controls this, meaning if I get
> an IP or a
> > hostname, and why it's being truncated.
>
> don't know about the truncating, but this behavior of
> displaying the
> last login time and host is handled by pam_lastlog(8).
>
> i guess the FQHN is just displayed if a reverse dns entry
> exists for the
> corresponding ip.
>
> regards - michael
>
>
> ------------------------------
>
> Message: 21
> Date: Fri, 4 Dec 2009 10:28:39 -0800
> From: William Taylor <williamt at corp.sonic.net>
> Subject: 8.0 zfs install
> To: questions at freebsd.org
> Message-ID: <25CC9A9B-DCB3-48BB-BD0A-238957A487FA at corp.sonic.net>
> Content-Type: text/plain; charset=us-ascii
>
> Does the installer in 8.0 support zfs?
>
> If not whats the easiest way to get a full zfs install
> done?
>
>
> ------------------------------
>
> Message: 22
> Date: Fri, 4 Dec 2009 09:51:57 -0900
> From: Henrik Hudson <lists at rhavenn.net>
> Subject: Re: recovering data from this disk
> To: freebsd-questions at freebsd.org
> Message-ID: <20091204185157.GA4904 at alucard.int.rhavenn.net>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, 04 Dec 2009, Tom Worster wrote:
>
> > any suggestions how to recover data from either of the
> mirrored disks that i
> > can't get to boot? the situation is described below.
>
> If they were indeed mirrored then try a FreeBSD live distro
> boot CD
> and boot into that then just mount one of the disk
> partitions that
> you need.
>
> Henrik
>
>
> >
> > (i'm assuming, given the silence on this, that making
> the system work after
> > the freebsd-update is a lost cause.)
> >
> >
> > On 12/3/09 11:14 AM, "Tom Worster" <fsb at thefsb.org>
> wrote:
> >
> > > after running freebsd-update -r 8.0-RELEASE
> upgrade my system won't boot. it
> > > gets stuck on mountroot and i can't find the
> magic word it wants.
> > >
> > > the system used to have two sata drives /dev/ad4
> and ad6. they were
> > > partitioned and sliced using the deafaults that
> sysinstall suggested.
> > >
> > > at the boot prompt, lsdev says:
> > >
> > > disk devices
> > > disk0: BIOS drive C:
> > > disk0s1a: FFS
> > > disk0s1b: swap
> > > disk0s1d: FFS
> > > disk0s1e: FFS
> > > disk0s1f: FFS
> > > disk1: BIOS drive D:
> > > disk1s1a: FFS
> > > disk1s1b: swap
> > > disk1s1d: FFS
> > > disk1s1e: FFS
> > > disk1s1f: FFS
> > >
> > > which looks right, although i'm not familiar with
> the "disk" nomenclature.
> > >
> > > entering ? at mountroot mentions ad4 and ad6.
> > >
> > > geom_mirror was being used.
> > >
> > > i've tried saying "load geom_mirror" and/or
> "enable-module geom_mirror" at the
> > > boot prompt. neither made any difference.
> > >
> > > nothing i've said to mountroot works:
> > >
> > > ufs:/dev/ad4s1a
> > > ufs:/dev/ad6s1a
> > > ufs:/dev/mirror/gm0s1a
> > > ufs:/dev/disk0s1a
> > > ufs:/dev/disk1s1a
> > >
> > > does anyone know the magic word? i'd be very
> grateful.
> > >
> > > tom
> >
> >
> > _______________________________________________
> > freebsd-questions at freebsd.org
> mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
> --
> Henrik Hudson
> lists at rhavenn.net
> -----------------------------------------
> "God, root, what is difference?" Pitr; UF
>
>
>
> ------------------------------
>
> Message: 23
> Date: Fri, 04 Dec 2009 19:17:12 +0000
> From: Matthew Seaman <m.seaman at infracaninophile.co.uk>
> Subject: Re: 8.0 zfs install
> To: William Taylor <williamt at corp.sonic.net>
> Cc: questions at freebsd.org
> Message-ID: <4B196038.6000902 at infracaninophile.co.uk>
> Content-Type: text/plain; charset="iso-8859-1"
>
> William Taylor wrote:
> > Does the installer in 8.0 support zfs?
>
> No.
>
> > If not whats the easiest way to get a full zfs install
> done?
>
> http://wiki.freebsd.org/RootOnZFS and links referenced
> from that page.
>
> Cheers,
>
> Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil.
> 7 Priory
> Courtyard
>
>
>
> Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey
> Ramsgate
>
>
>
> Kent, CT11 9PW
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 259 bytes
> Desc: OpenPGP digital signature
> Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20091204/599ce866/signature-0001.pgp
>
> ------------------------------
>
> Message: 24
> Date: Fri, 4 Dec 2009 11:19:20 -0800
> From: pete wright <nomadlogic at gmail.com>
> Subject: Re: 8.0 zfs install
> To: William Taylor <williamt at corp.sonic.net>
> Cc: questions at freebsd.org
> Message-ID:
> <57d710000912041119o43aca29dk6575b241c474ca1d at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, Dec 4, 2009 at 10:28 AM, William Taylor <williamt at corp.sonic.net>
> wrote:
> > Does the installer in 8.0 support zfs?
> >
> > If not whats the easiest way to get a full zfs install
> done?
>
>
> This is probably the best place to start, in general the
> FreeBSD
> handbook is the best place to start looking for any
> information you
> may have regarding the OS:
>
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html
>
> You can also get more information via the FreeBSD wiki
> here:
> http://wiki.freebsd.org/ZFS
>
>
> --
> pete wright
> www.nycbug.org
>
>
> ------------------------------
>
> Message: 25
> Date: Fri, 04 Dec 2009 14:22:27 -0500
> From: Tom Worster <fsb at thefsb.org>
> Subject: Re: recovering data from this disk
> To: Henrik Hudson <lists at rhavenn.net>,
> <freebsd-questions at freebsd.org>
> Message-ID: <C73ECBA3.144E9%fsb at thefsb.org>
> Content-Type: text/plain;
> charset="US-ASCII"
>
> On 12/4/09 1:51 PM, "Henrik Hudson" <lists at rhavenn.net>
> wrote:
>
> > On Fri, 04 Dec 2009, Tom Worster wrote:
> >
> >> any suggestions how to recover data from either of
> the mirrored disks that i
> >> can't get to boot? the situation is described
> below.
> >
> > If they were indeed mirrored then try a FreeBSD live
> distro boot CD
> > and boot into that then just mount one of the disk
> partitions that
> > you need.
>
> thanks, henrik,
>
> but i wasn't able to make the live fs fixit shell work. i
> get an error
> message when i try to start the live fs shell: "ldconfig
> could not create
> the ld.so hints file" and all commands fail to work.
>
> tom
>
>
> >>
> >> (i'm assuming, given the silence on this, that
> making the system work after
> >> the freebsd-update is a lost cause.)
> >>
> >>
> >> On 12/3/09 11:14 AM, "Tom Worster" <fsb at thefsb.org>
> wrote:
> >>
> >>> after running freebsd-update -r 8.0-RELEASE
> upgrade my system won't boot. it
> >>> gets stuck on mountroot and i can't find the
> magic word it wants.
> >>>
> >>> the system used to have two sata drives
> /dev/ad4 and ad6. they were
> >>> partitioned and sliced using the deafaults
> that sysinstall suggested.
> >>>
> >>> at the boot prompt, lsdev says:
> >>>
> >>> disk devices
> >>> disk0: BIOS drive C:
> >>> disk0s1a: FFS
> >>> disk0s1b: swap
> >>> disk0s1d: FFS
> >>> disk0s1e: FFS
> >>> disk0s1f: FFS
> >>> disk1: BIOS drive D:
> >>> disk1s1a: FFS
> >>> disk1s1b: swap
> >>> disk1s1d: FFS
> >>> disk1s1e: FFS
> >>> disk1s1f: FFS
> >>>
> >>> which looks right, although i'm not familiar
> with the "disk" nomenclature.
> >>>
> >>> entering ? at mountroot mentions ad4 and ad6.
> >>>
> >>> geom_mirror was being used.
> >>>
> >>> i've tried saying "load geom_mirror" and/or
> "enable-module geom_mirror" at
> >>> the
> >>> boot prompt. neither made any difference.
> >>>
> >>> nothing i've said to mountroot works:
> >>>
> >>> ufs:/dev/ad4s1a
> >>> ufs:/dev/ad6s1a
> >>> ufs:/dev/mirror/gm0s1a
> >>> ufs:/dev/disk0s1a
> >>> ufs:/dev/disk1s1a
> >>>
> >>> does anyone know the magic word? i'd be very
> grateful.
> >>>
> >>> tom
> >>
> >>
> >> _______________________________________________
> >> freebsd-questions at freebsd.org
> mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>
>
>
> ------------------------------
>
> Message: 26
> Date: Fri, 4 Dec 2009 13:23:35 -0600
> From: Peter Steele <psteele at maxiscale.com>
> Subject: Is there the equivalent of a Windows "fast format"
> for UFS?
> To: "freebsd-questions at freebsd.org"
> <freebsd-questions at freebsd.org>
> Message-ID:
> <7B9397B189EB6E46A5EE7B4C8A4BB7CB33C6C072 at MBX03.exg5.exghost.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I suspect I know the answer to this question but I'll ask
> it anyway. We're dealing with some very large disks (11TB
> raid array) and a newfs operation takes a significant time.
> Is there any way to get a volume formatted faster than the
> typical newfs does?
>
>
>
> ------------------------------
>
> Message: 27
> Date: Fri, 04 Dec 2009 09:26:55 -1000
> From: Al Plant <noc at hdk5.net>
> Subject: Re: [Solved] Having problems burning a DVD
> To: James Phillips <anti_spam256 at yahoo.ca>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <4B19627F.7020908 at hdk5.net>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> James Phillips wrote:
> > Hello,
> >
> > After making two coasters with a graphical CD burning
> program using Ubuntu, I decided to try using FreeBSD: I want
> to start backing up to DVD anyway.
> >
> > After some searching I learned I missed some details
> in the handbook on the first and second reads such as:
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html
> > "The program growisofs(1) will be used to perform DVD
> recording. This command is part of the dvd+rw-tools
> utilities (sysutils/dvd+rw-tools). The dvd+rw-tools support
> all DVD media types."
> >
> > I had hard time finding the non-existent growisofs
> package!
> >
> > "These tools use the SCSI subsystem to access to the
> devices, therefore the ATAPI/CAM support must be added to
> your kernel. If your burner uses the USB interface this
> addition is useless, and you should read the Section 18.5
> for more details on USB devices configuration."
> >
> > Using the atapicd driver generated the following error
> message:
> > :-( unable to CAMGETPASSTHRU for /dev/acd0:
> Inappropriate ioctl for device
> >
> > After the command:
> > $ growisofs -dvd-compat -Z
> /dev/acd0=8.0-RELEASE-i386-dvd1.iso
> > before you ask:
> > MD5 (8.0-RELEASE-i386-dvd1.iso) =
> 5336cd827991e4d4cff6d73c4a5ca105
> > Release announcement:
> 5336cd827991e4d4cff6d73c4a5ca105
> >
> > I tried playing with /etc/devfs.conf as suggested by
> Predrag Punosevac
> > $ id
> > uid=1002(backup) gid=1002(backup)
> groups=1002(backup),5(operator),1003(Share)
> > $ cat /etc/devfs.conf |sed 's/#.*//g'
> > link cd0 cdrom
> > link cd0 dvd
> > link cd0 rdvd
> > own cdrom
> root:operator
> > own dvd
> root:operator
> > own rdvd
> root:operator
> > perm cd0 0660
> > perm cdrom 0660
> > perm dvd 0660
> > perm rdvd 0660
> > perm xpt0 0660
> > perm pass0 0660
> > -> that sed command was stolen from a script
> expecting <CR><lf>
> > ->originally used device acd0 (until enabling
> atapicam)
> > $ cat /boot/loader.conf
> > acpi_load="no"
> > apm_load="yes"
> > atapicam_load="yes"
> > #ata_load="yes" # enabled by default
> > scbus_load="yes"
> > cd_load="yes"
> > pass_load="yes"
> > atapicd_load="no"
> > #hw.ata.atapi_dma="1" # enabled by default
> >
> > With the atapicam driver I was able to somehow get
> growisofs to go through the motions of burning the DVD, even
> have a kernel message from GEOM reading the BSD label:
> > $ tail /var/log/messages
> > Dec 3 20:00:00 dusty newsyslog[833]: logfile
> turned over due to size>100K
> > Dec 3 20:00:28 dusty kernel: GEOM_LABEL: Label
> for provider acd0t01 is iso9660/FreeBSD_Install.
> >
> > but can't read the disk to verify it:
> > $ dd if=/dev/cd0 bs=2048 | md5
> > 996592+0 records in
> > 996592+0 records out
> > 2041020416 bytes transferred in 1292.388284 secs
> (1579263 bytes/sec)
> > 19b087536234b316b64232ba6b1c1799
> >
> > Umm. Nevermind. I added the block size so nobody would
> try suggesting it has an effect :P previous error:
> > $ dd if=/dev/cd0 | md5
> > dd: /dev/cd0: Invalid argument
> > 0+0 records in
> > 0+0 records out
> > 0 bytes transferred in 0.000721 secs (0 bytes/sec)
> > d41d8cd98f00b204e9800998ecf8427e
> >
> >
> > I noticed that the hash does not match the ISO file.
> Is that normal for DVDs? For CD images I often get the md5
> hash to match.
> >
> > The man page for atapicam(4) warns:
> > "atapicam and ATAPI-specific target drivers (acd(4),
> ast(4), and afd(4))
> > can be configured in the same kernel.
> Simultaneous access to the same
> > device through the SCSI generic drivers and the
> ATAPI-specific drivers
> > may cause problems and is strongly
> discouraged."
> >
> > Is there anything special I should do to try to
> disable the atapicd driver? I don't think my
> 'atapicd_load="no"' line in /boot/loader.conf has much of an
> effect.
> >
> > Regards,
> >
> > James Phillips
> >
> >
> >
> >
> __________________________________________________________________
> > Looking for the perfect gift? Give the gift of Flickr!
>
> >
> > http://www.flickr.com/gift/
> > _______________________________________________
> > freebsd-questions at freebsd.org
> mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
> Aloha JP,
>
> This is what I use on FreeBSD from the command line to burn
> DVD's.
> I have used it on FreeBSD 8* for a while. (Simple and it
> works.)-
>
>
> ##########
>
> dvdburner.doc
> DVD+R burner Setup and operation
>
>
> From sysutils/dvd+rw-tools
> Intall the DVD port
>
> # growisofs
>
> ( used the following from all the suggestions and it worked
> with Manolis
> DVD p1 7.2)
>
> 1st> Put hw.ata.atapi_dma="1" in the
> /boot/loader.conf
> 2nd> Put apticam_load="YES" in the /boot/loader.conf
>
> (That 2nd 18.7.2 instruction is not clear in the Handbook
> section and
> should be added.)
>
>
> Then> Run # growisofs -dvd-compat -Z
> dev/cd0=/usr/home/alp/FreeBSD_7/7.2-RELEASE-p1-i386-disc1.iso
> (all on one line)
>
> Then> Use cd0 as a DVD burner and make the DVD-R
>
> I tested the DVD on a spare box and it installed just
> fine.
>
> ##############
>
>
> ~Al Plant - Honolulu, Hawaii - Phone:
> 808-284-2740
> + http://hawaiidakine.com + http://freebsdinfo.org +
> + http://aloha50.net -
> Supporting - FreeBSD 7.2 - 8.0 - 9* +
> < email: noc at hdk5.net >
> "All that's really worth doing is what we do for others."-
> Lewis Carrol
>
>
>
> ------------------------------
>
> Message: 28
> Date: Fri, 4 Dec 2009 13:32:19 -0600
> From: Dan Nelson <dnelson at allantgroup.com>
> Subject: Re: malformed man pages
> To: Sagara Wijetunga <sagara at tomahawk.com.sg>
> Cc: freebsd-questions at freebsd.org
> Message-ID: <20091204193219.GA84026 at dan.emsphone.com>
> Content-Type: text/plain; charset=us-ascii
>
> In the last episode (Dec 04), Sagara Wijetunga said:
> > Hi FreeBSD community
> >
> > We have an issue on Tomahawk Desktop (an upcoming
> FreeBSD-based distro)
> > that all man pages malformed.
> >
> > Eg. man tar shows as follows:
> > 1mNAME0m
> > 1mtar 22m-- format of tape archive
> files
> >
> > 1mDESCRIPTION0m
> > The 1mtar 22marchive format
> collects any number of files,
> > directories, and
>
> That looks sort of like malformed ANSI escape codes (bold
> would be "ESC [ 1
> m", but the man utilities shouldn't be generating
> those. If you run "man 5
> tar | hd | head", what do you get? I get this:
>
> 00000000 54 41 52 28 35 29 09 09 09 20 20 46 72
> 65 65 42 |TAR(5)... FreeB|
> 00000010 53 44 20 46 69 6c 65 20 46 6f 72 6d 61
> 74 73 20 |SD File Formats |
> 00000020 4d 61 6e 75 61 6c 09 09 09 54 41 52 28
> 35 29 0a |Manual...TAR(5).|
> 00000030 0a 4e 08 4e 41 08 41 4d 08 4d 45 08 45
> 0a 20 20 |.N.NA.AM.ME.E. |
> 00000040 20 20 20 74 08 74 61 08 61 72 08 72 20
> 2d 2d 20 | t.ta.ar.r -- |
> 00000050 66 6f 72 6d 61 74 20 6f 66 20 74 61 70
> 65 20 61 |format of tape a|
> 00000060 72 63 68 69 76 65 20 66 69 6c 65 73 0a
> 0a 44 08 |rchive files..D.|
> 00000070 44 45 08 45 53 08 53 43 08 43 52 08 52
> 49 08 49 |DE.ES.SC.CR.RI.I|
> 00000080 50 08 50 54 08 54 49 08 49 4f 08 4f 4e
> 08 4e 0a |P.PT.TI.IO.ON.N.|
> 00000090 20 20 20 20 20 54 68 65 20 74 08 74 61
> 08 61 72 | The t.ta.ar|
>
> The doubled letters are handled by /usr/bin/less and
> converted to bold
> before displaying. If you get the same hd output as I
> have above, then we
> know that the manpage is fine, and your problem is in
> /usr/bin/less or your
> terminal type is incorrect. If you see ANSI escape
> codes in the hd output,
> then we know the problem is with the manpage tools.
>
> --
> Dan Nelson
> dnelson at allantgroup.com
>
>
> Date: Fri, 4 Dec 2009 13:23:35 -0600
> From: Peter Steele <psteele at maxiscale.com>
> Subject: Is there the equivalent of a Windows "fast format"
> for UFS?
> To: "freebsd-questions at freebsd.org"
> <freebsd-questions at freebsd.org>
> Message-ID:
> <7B9397B189EB6E46A5EE7B4C8A4BB7CB33C6C072 at MBX03.exg5.exghost.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I suspect I know the answer to this question but I'll ask
> it anyway. We're dealing with some very large disks (11TB
> raid array) and a newfs operation takes a significant time.
> Is there any way to get a volume formatted faster than the
> typical newfs does?
>
I'm no expert, but I think doing a newfs without zeroing the drive (array) first IS the equivalent of the Windows "Fast Format."
According to the manpage, increasing the fragment size should reduce the number of inodes written. Do you have (or expect) 11TB of small files?
Regards,
James Phillips
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
More information about the freebsd-questions
mailing list