> On 29 Dec 2017, at 02:44, Colin Percival wrote:
>
> us-east-1 ami-e6a6ea9c is a FreeBSD 11.1-RELEASE AMI-building AMI.
Many thanks, Colin. And a Happy New Year!
May I ask you if what I am hoping to do makes sense? Taking the gist from
http://www.daemonology.net/blog/2015-11-21-FreeBSD-AMI-b
PS. Could it be as easy as make DESTDIR=/mnt installkernel in the config init?
> On 29 Dec 2017, at 02:44, Colin Percival wrote:
>
> us-east-1 ami-e6a6ea9c is a FreeBSD 11.1-RELEASE AMI-building AMI.
Many thanks, Colin. And a Happy New Year!
May I ask you if what I am hoping to do makes sense?
> On 1 Jan 2018, at 22:39, Colin Percival wrote:
>
> Maybe a dumb question, but do you really need to use a configinit script
> for this? I know I showed that as an example in my blog post, but I
> expected that the main way the AMI builder would be used would be by
> SSHing in and setting thin
On 2/1/18 12:16 am, Rafal Lukawiecki wrote:
On 29 Dec 2017, at 02:44, Colin Percival wrote:
us-east-1 ami-e6a6ea9c is a FreeBSD 11.1-RELEASE AMI-building AMI.
Many thanks, Colin. And a Happy New Year!
May I ask you if what I am hoping to do makes sense? Taking the gist from
http://www.daemon
> On 1 Jan 2018, at 17:42, Rafal Lukawiecki wrote:
>
> PS. Could it be as easy as make DESTDIR=/mnt installkernel in the config init?
I went ahead and tried the script. It is not working yet, and I need to debug
it further, which means connecting to the instance etc, which I have not yet.
So
On 01/01/18 11:00, Rafal Lukawiecki wrote:
> On 1 Jan 2018, at 17:42, Rafal Lukawiecki wrote:
>> PS. Could it be as easy as make DESTDIR=/mnt installkernel in the config
>> init?
That is indeed how to install the kernel you built into the right place.
> I went ahead and tried the script. [...]
