Re: [netbsd-users] About using NetBSD as a guest, why, how etc.
>is doing a manual from-scratch install from the command-line >documented anywhere? would this be of help?: https://archive.unitedbsd.com/t/netbsd-desktop-part-1-manual-netbsd-installation-on-gpt-uefi/284 /ts
Re: [netbsd-users] About using NetBSD as a guest, why, how etc.
On Wed, 11 Dec 2019, at 09:33, Rhialto wrote: > On Tue 10 Dec 2019 at 18:39:00 +1100, Malcolm Herbert wrote: > > is doing a manual from-scratch install from the command-line > > documented anywhere? : : > But you can try another approach: you can have sysinst create a shell > script which contains everything it does (at least when I tried it once > upon a time it seemed to work). ... I had no idea this feature was available, that's certainly a workable solution for me, thanks very much! Regards, Malcolm -- Malcolm Herbert m...@mjch.net
Re: [netbsd-users] About using NetBSD as a guest, why, how etc.
On Tue 10 Dec 2019 at 18:39:00 +1100, Malcolm Herbert wrote: > is doing a manual from-scratch install from the command-line > documented anywhere? I think it probably is in several places (the broad outlines are a) partition disk b) newfs file system(s) c) install bootblocks d) extract all tar sets and that's mostly it; but the details are what counts of course and if you're doing it for the first time it can be a bit tricky to get right). But you can try another approach: you can have sysinst create a shell script which contains everything it does (at least when I tried it once upon a time it seemed to work). So you go through the procedure once interactively and then you can just use the recorded script to repeat the procedure. You can enable the script in sysinst from the start by following e: Utility menu, e: Logging function, b: Scripting: On. The main trick is at the end, to make sure that the recorded script gets copied to the installed system, because it is stored in the install image and it will be lost on reboot. Also, I seem to remember that the install image had very little space and even the modestly sized shell script didn't fit. But that was years ago and all sizes of everything are now different, so you can just try and see where it gets you :) > Regards, > Malcolm -Olaf. -- Olaf 'Rhialto' Seibert -- rhialto at falu dot nl ___ Anyone who is capable of getting themselves made President should on \X/ no account be allowed to do the job. --Douglas Adams, "THGTTG" signature.asc Description: PGP signature
Re: [netbsd-users] About using NetBSD as a guest, why, how etc.
Mayuresh - I find NetBSD in a VirtualBox VM under Ubuntu quite nice. In my case I also use encrypted zpools for my data which Linux supports now. I like using VirtualBox+packer+vagrant with the bento[1] packer configs to spin out VMs of different types. My only gripe with VirtualBox is that it doesn't have native client tools support for the *BSD family and the vboxfs filesystem isn't available - ordinarily these provide file-level access to the host filesystem and vagrant heavily uses this. Instead (for example), the packer+vagrant config for FreeBSD will use NFS which works but is a bit more fiddly to set up. Unfortunately there is no bento recipe for NetBSD at all, so you'd have to build out the VM manually ... I would like to create a bento recipe for NetBSD, however the bit that's preventing me doing this is understanding how to properly add disk labels and bootblocks from the command-line - one can stuff keys into the VM to drive sysinst but this is a nightmare to debug ... is doing a manual from-scratch install from the command-line documented anywhere? Regards, Malcolm [1] https://github.com/chef/bento -- Malcolm Herbert m...@mjch.net
