On Thu, Aug 1, 2013 at 12:40 PM, Amitabh Kant wrote:
> Devin Teske & Rick Miller have a fairly extensive explanation on their
> blogs on how to create your own modified iso's. Search the archives for
> links. Hopefully they can chime in with their respective links.
Sorry to show up late for the d
On Aug 1, 2013, at 10:58 AM, Teske, Devin wrote:
>
> On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote:
>
>> On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin
>> wrote:
>> I'm hoping that my very open development documentation on customizing the
>> release(7) process for producing DruidBSD releases
On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote:
> On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin
> wrote:
> I'm hoping that my very open development documentation on customizing the
> release(7) process for producing DruidBSD releases can help you out here.
>
> I've documented much of the inte
On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin wrote:
> I'm hoping that my very open development documentation on customizing the
> release(7) process for producing DruidBSD releases can help you out here.
>
> I've documented much of the internals of the release(7) process (albeit,
> relevant to th
On Thu, Aug 1, 2013 at 10:10 PM, Amitabh Kant wrote:
> Devin Teske & Rick Miller have a fairly extensive explanation on their
> blogs on how to create your own modified iso's. Search the archives for
> links. Hopefully they can chime in with their respective links.
>
> I the meantime , the follow
Devin Teske & Rick Miller have a fairly extensive explanation on their
blogs on how to create your own modified iso's. Search the archives for
links. Hopefully they can chime in with their respective links.
I the meantime , the following link has somewhat of my own notes for
creating a custom cd;
On Aug 1, 2013, at 9:14 AM, Sam Fourman Jr. wrote:
> one specific question I have, that I can't find in the handbook...
> To make a FreeBSD release, that is to build the install images... you build
> world, and kernel.. then go to /etc/src/release and type make release...
> after this, the releas
On 05/23/2013 06:52 AM, Jack Mc Lauren wrote:
> Hi
> find //usr/obj/usr/src/release/dist/doc -empty -delete
> find: -delete: //usr/obj/usr/src/release/dist/doc: relative path potentially
> not
> safe
> *** [distributeworld] Error code 1
> What's wrong with this?
> Thanks in advance
Huh. Appare
On Dec 11, 2012, at 2:13 PM, Rick Miller wrote:
> On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske
> wrote:
>>
>> Though, to resize the mfsroot, I still rely on release(7) and the above
>> patches.
>
> Here's another question, have you applied this approach to
> boot_crunch.conf? I simply replac
On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske wrote:
>
> Though, to resize the mfsroot, I still rely on release(7) and the above
> patches.
Here's another question, have you applied this approach to
boot_crunch.conf? I simply replaced the default boot_crunch.conf with
my own in the source tree.
On Dec 11, 2012, at 1:50 PM, Rick Miller wrote:
> Hi Devin,
>
> On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske
> wrote:
>> Hi Rick,
>>
>> If you want, you could follow my approach which is to take the completed
>> mfsroot.gz and use a Makefile to manage the creation of custom mfsroots
>> (keepi
Hi Devin,
On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske wrote:
> Hi Rick,
>
> If you want, you could follow my approach which is to take the completed
> mfsroot.gz and use a Makefile to manage the creation of custom mfsroots
> (keeping the original unmodified, making it simpler to test different
>
Hi Rick,
If you want, you could follow my approach which is to take the completed
mfsroot.gz and use a Makefile to manage the creation of custom mfsroots
(keeping the original unmodified, making it simpler to test different
iterations).
The advantage is that you don't have to re-perform the re
Thanks Rob and Lowell,
I will keep this information handy. It was helpful.
On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer wrote:
> On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller
> wrote:
>> Thanks Rob...
>>
>> I put the kernel conf file in the source tree as opposed to linking to
>> it and it cer
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller wrote:
> Thanks Rob...
>
> I put the kernel conf file in the source tree as opposed to linking to
> it and it certainly did compile the custom kernel.
>
> What confuses me (not that I expect you to have the answer) is that
> Chapter 9 of the handbook h
Rick Miller writes:
> Thanks Rob...
>
> I put the kernel conf file in the source tree as opposed to linking to
> it and it certainly did compile the custom kernel.
>
> What confuses me (not that I expect you to have the answer) is that
> Chapter 9 of the handbook has a tip that recommends keeping
Thanks Rob...
I put the kernel conf file in the source tree as opposed to linking to
it and it certainly did compile the custom kernel.
What confuses me (not that I expect you to have the answer) is that
Chapter 9 of the handbook has a tip that recommends keeping the kernel
config in /root/kernel
2012-01-29 18:03, Rick Miller skrev:
Hi All,
I am performing a `make release` to build a new release with a custom
kernel. The `make release` fails with the following error:
cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64
KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/M
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller wrote:
> Hi All,
>
> I am performing a `make release` to build a new release with a custom
> kernel. The `make release` fails with the following error:
>
> cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64
> KERNCONF=MYKERNEL kernel DESTDIR
O. Hartmann wrote:
> I followed the steps making a release on FreeBSD 8.0-RC2/AMD64 on my
> box, the target CHROOTDIR is located on a ZFS volume. I searched the
> list for a solution, but did not find any.
> sysctl kern.securelevel shows
> kern.securelevel: -1
>
> Is there any solution? I guess tho
On Thursday 27 November 2008 06:12:37 michael wrote:
> Beech Rintoul wrote:
> > On Thursday 27 November 2008 04:44:19 michael wrote:
> >> Beech Rintoul wrote:
> >>> On Wednesday 26 November 2008 20:40:21 michael wrote:
> will make release work for current? i've built a nice working system
> >>
Beech Rintoul wrote:
On Thursday 27 November 2008 04:44:19 michael wrote:
Beech Rintoul wrote:
On Wednesday 26 November 2008 20:40:21 michael wrote:
will make release work for current? i've built a nice working system
that i would like to be able to install on several identica
On Thursday 27 November 2008 04:44:19 michael wrote:
> Beech Rintoul wrote:
> > On Wednesday 26 November 2008 20:40:21 michael wrote:
> >> will make release work for current? i've built a nice working system
> >> that i would like to be able to install on several identical machines.
> >
> > Yes, bu
Beech Rintoul wrote:
On Wednesday 26 November 2008 20:40:21 michael wrote:
will make release work for current? i've built a nice working system
that i would like to be able to install on several identical machines.
Yes, but read all the docs completely there are a number of options y
On Wednesday 26 November 2008 22:54:35 Valentin Bud wrote:
> Hello Beech,
>
> Could you be more specific on what documentation to read.
>
> thank you and a great day,
> v
>
> On Thu, Nov 27, 2008 at 8:20 AM, Beech Rintoul <[EMAIL PROTECTED]> wrote:
> > On Wednesday 26 November 2008 20:40:21 michael
Hello Beech,
Could you be more specific on what documentation to read.
thank you and a great day,
v
On Thu, Nov 27, 2008 at 8:20 AM, Beech Rintoul <[EMAIL PROTECTED]> wrote:
> On Wednesday 26 November 2008 20:40:21 michael wrote:
>> will make release work for current? i've built a nice working s
On Wednesday 26 November 2008 20:40:21 michael wrote:
> will make release work for current? i've built a nice working system
> that i would like to be able to install on several identical machines.
Yes, but read all the docs completely there are a number of options you need,
like telling it to us
On Sat, Aug 30, 2008 at 11:06 AM, Matias Surdi <[EMAIL PROTECTED]> wrote:
> The problem arises when I do a "make release" as, as far as I can see,
> /etc/src.conf is completly ignored. I think it's an issue with the chroot
> environment that "make release" uses. Wich is the correct way to let "make
> Another question:
>
> Suppose I create my own install.cfg for sysinstall and then I do a "make
> release".If my sysinstall contains a couple of freeBSD packages (bash,
> python, etc..) plus a custom package created by me.. How must I instruct
> "make release" to include just those packages in the
Hi,
This should help:
http://www.gsoft.com.au/~doconnor/FreeBSD-release.html
http://www.gsoft.com.au/~doconnor/release/install.cfg
I made my own release with ports on board without additional
post-installing.
This ports, are configured and ready to work "out of box".
Best regards,
Sebastian Ty
Hi Riaan,
Thanks a lot for your explanation, it's been very usefull to me, really.
I've been looking about Freesbie, but it seems abandoned and on
their mailing list there is no post since a couple of months.
PfSense, which I use here, uses bsdInstaller but it's last "new" is from
Aug 02
Sysinstall has a configuration file with wich you can specify several
options, see man sysinstall(8) for more details. When making a
release you set the sysinstalls configuration file with the
LOCAL_PATCHES option to patch it to the chroot environment release
build environment.
We use it to creat
[ cc line trimmed a bit... ]
On Sun, 2007-08-12 at 08:55 +0800, Put PostgreSQL to Work for Your
Business. wrote:
> Dear all
>
> I am building a custom FreeBSD for internal use for the various
> platforms we used (x86 platform). I am encountering a issue write
> failed, filesystem is full when cr
Maxim Vetrov <[EMAIL PROTECTED]> writes:
> I'm running 5.4 and trying to make release of 6.0.
You do realize the documentation says that's not supported, right?
You're kind of on your own there.
>While making
> release, I got next error:
>
> .
pirat sriyotha <[EMAIL PROTECTED]> writes:
> hi sirs,
>
> am trying to make my own release by `make release -DNOGAME' at
> /usr/src/release
> with 5.4 notebook. i want to have packages that have been built included into
> disc1.iso too but i get only 198mb of src and ports and some others inste
Beecher Rintoul wrote:
I just did a release snapshot and everything worked except the last steps
creating the CD iso files. they simply don't exist. All of the supporting
files are in place and I can do a mkisofs and create a bootable working disk.
Can someone shed some light on how to get the
On Fri, Jun 04, 2004 at 09:41:46AM -0400, Sven Willenberger wrote:
> I seem to be running into brick walls making a 5.2.1-RELEASE-P8 for
> sparc64 arch on an i386 system. I have tried the following using the
> latest sources from cvsup:
I don't think you can cross-target releases. For example, th
I wrote:
> We might be able to move the de, em, or vx drivers to the mfsroot
> floppy, if there's space. I'll try playing around with this, if I get
> some time. (Obviously that shouldn't preclude someone else from
> working on this problem.)
I moved the em driver to mfsroot.flp and was able
If memory serves me right, "Igor B. Bykhalo" wrote:
[kern.flp overflow again]
> I don't get it:
[snip]
> > goshik# ls -l *kern*
> > image.kern:
> > total 1346
> > drwxr-xr-x 2 root wheel 512 22 ÑÎ× 21:19 boot
> > -r-xr-xr-x 1 root wheel 1344894 22 ÑÎ× 21:19 kernel.gz
> >
> > kernels:
39 matches
Mail list logo
