Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jan 2011 19:05:02 -0800
From:      Doug Barton <dougb@FreeBSD.org>
To:        Glen Barber <glen.j.barber@gmail.com>
Cc:        doc@freebsd.org
Subject:   Re: Fenestrating the Handbook memstick section
Message-ID:  <4D35035E.6010304@FreeBSD.org>
In-Reply-To: <4D34F8B3.1010803@gmail.com>
References:  <alpine.BSF.2.00.1101171342240.13096@wonkity.com> <4D34F8B3.1010803@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 01/17/2011 18:19, Glen Barber wrote:
> Hi,
>
> On 1/17/11 8:41 PM, Warren Block wrote:
>> Currently, the Handbook only shows how to create a FreeBSD install
>> memstick by using dd(1).  This leaves the Windows crowd unaddressed.
>>
>> I've done some searching for a Windows utility to write memory sticks
>> that is freely available and simple to use.
>>
>
> Thank you for looking into this, by the way.

>> Finally, there's https://launchpad.net/win32-image-writer, which is
>> Image Writer for Windows or win32diskimager depending on how you look.
>> Done by the Ubuntu folks.  GPLV2.  Easy to use.  The best option I've
>> found so far.
>
> IMHO, this sounds like the easiest option for the end-user.

Agreed. I've used this, it's a nice tool.

>> The questions:
>>
>> If we recommend Image Writer for Windows, seems like it would be polite
>> to ask the project before taking advantage of their download capacity.
>> Or would it be better to have a copy hosted on a FreeBSD server?
>
> I'm curious what the general consensus is on this last question myself.

Well asking first is the bare minimum of politeness. And yes, I think we 
should be prepared to host it ourselves, and commit to the maintenance 
task that this implies.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D35035E.6010304>