[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: creating official Debian images for ARM-based NAS devices



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 13/04/16 18:26, Vagrant Cascadian wrote:
> On 2016-04-13, Martin Michlmayr wrote:
>> * Daniel Pocock <daniel@pocock.pro> [2016-04-13 10:41]:
>>> I had a look at the instructions[1] for preparing firmware for
>>> the Seagate NAS[2]
>>> 
>>> There is a link to download a binary image file that somebody
>>> has already prepared and instructions to prepare an image file
>>> yourself.
>> 
>> I think we should let the user run Debian installer instead of 
>> providing binary images.  Installing such images is often much
>> harder on NAS devices than simply running Debian installer.
> 
> There is, of course, the option of an installer image with
> preseeding to automate the install targeted at specific devices.
> Shipping some preseeding files like these might be an interesting
> middle-ground between running an installer and shipping a
> ready-to-run image.
> 

There are two things that come to mind for me:

- - making it quick for advanced users, if they are installing 10 or 20
of these devices they will be frustrated having to go through the full
installer but they may not feel it is enough inconvenience to go and
learn about preseeding

- - making it feasible for less advanced users.  They say that for every
extra question or field in a form, half the users give up

How are people actually using the installer on these devices?  Are
they booting it with TFTP and then accessing it over ssh?  Or does the
installer run on a traditional x86 machine and create some image that
they can flash into the NAS?  If people are relying upon TFTP, it
would not be hard to produce a Debian Live DVD that has a
preconfigured DHCP/BOOTP/TFTP services for people to initialize other
devices like this.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXDyo5AAoJEGxlgOd711bErdAP/1FkyHvclTW0LcpAlkoWSnQ0
/EC9ILp6ML6JTXRKd1ZWHrXzBVM+wxmizjA5iQUXOO1PZX+9HWfUOD7cq0Y2lzTe
xWMD3DKTL+siLaee7aY0rNq/gMPVMJUYgeN35o4Fb1rGSt66dyQM69UfklJCrIRh
eE481loo0kh+myc5SKRi5qm33tzDy2oXoT3ytQ78i+Cs/5DUfAIy9mVx1+XF1GFI
XElwrH1R6PLj5XcXD8MIfJTqDfYYVi1aEavgw43xlEbjHvm/jiipHkKn/OBqhb0V
4XD9RyRga6LLZxYkdpXpUxmS7STatcJpg+mrOelLBgzOnyWMZv329GLanCU1Ng6x
DeGy01wkqZR8kihPnEKtQzyH28lTKA61QK+wiKFp0oqTTeNl11nQtSM9dpMZeKyj
1LOzaTyeBcsIfsmcU3y3Gf+BF0skF5EmgETnhbFhzpa19pJerbyA9uQsbNMnf0LZ
RPCDDqQe21te5mum7GdDYxr4u7FRet2ewyMEKqpM4Lm8aq7iEbjf5U2LdeskEy9t
tnPJxqV3SopUbRD8G+zzMqPy/S9HsY5zq0/Hxr8BfGYJgoftCRnSMTeYv8XOvtVY
oo+HJTXCjWe6NtngH4O9hjex5lmN59xTxbXqAE0+m8jvBxQG8Wq9ZtE9pjmqjL29
za95/XPrKGBMSFg1F2An
=pGN3
-----END PGP SIGNATURE-----


Reply to: