Re: Diskless boot NFS server image
In case anyone is interested, I have an alpha version of my package,
diskless, available at http://snoopy.apana.org.au/~ftp/linux/
It works on my computer ;-)
I have applied to become a Debian maintainer, but this will take longer.
What do people think of my package name, diskless? nfsroot probably
would be better, but this name is already taken by an earler orphaned
package.
In article <[🔎] 19990217101114.13197.qmail@snoopy.apana.org.au> you write:
>Jim Pick wrote:
>>> I have been developing perl scripts that enable easy to configure and
>>> maintain NFS images for diskless clients. I have packaged these into
>>> a debian package, and I can provide my current version on request if
>>> anybody is interested.
>>
>>Did you take a look at nfsroot (in project/orphaned)? It's a similar
>>idea.
>
>I once looked at it ages ago, but didn't know what had happened to it. I
>think my solution is more general (in theory), but I will try and find
>nfsroot and see if I can learn anything from it.
I have had a quick look at nfsroot, but it doesn't seem to be as flexible
as my package, which has user friendly prompts that defines what files
are copied contain according to a set of rules. These prompts
are also used to define fields in certain config files (eg hostname, ip
address, masterdir, root password (encrypted), nameserver, domain,
nis, devfs, and shadow are currently supported, but not all combinations
has been tested.)
I think nfsroot supports creating diskless boot clients on the fly.
I don't know what others think, but I very much dislike this feature.
I don't like having major changes to the file structure occuring
behind my back.
However if anyone wants it should be easy to make diskless-newhost
100% non-interactive (currently it prompts the admistrator if a
source file conflicts with the destination file, a bit like the
way dpkg handles config files). The hardest bit is deciding what
the default option should be.
Reply to: