On Thu, Aug 1, 2013 at 12:40 PM, Amitabh Kant amitabhk...@gmail.com 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
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 release images show up in /usr/obj/usr/src/release
What I WANT
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 release
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 release images show up in /usr/obj/usr/src/release
What
.
Amitabh Kant
On Thu, Aug 1, 2013 at 9:44 PM, Sam Fourman Jr. sfour...@gmail.comwrote:
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
On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin devin.te...@fisglobal.comwrote:
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
On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote:
On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin devin.te...@fisglobal.com
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
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 devin.te...@fisglobal.com
wrote:
I'm hoping that my very open development documentation on customizing the
release(7) process for producing
On 05/23/2013 06:52 AM, Jack Mc Lauren wrote:
Hi
snip
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
snip
What's wrong with this?
Thanks in advance
Huh.
Hi
I'm trying to make my own release ...
# cd /usr/src
# make buildkernel KERNCONF=MYKERN
# make -j4 buildworld
# cd release/
# make release NODOC=YES NOPORTS=YES NOSRC=YES
and that's the error while making release:
find //usr/obj/usr/src/release/dist/doc -empty -delete
find: -delete: //usr
Hello list,
I'm running 8.3-stable r245223 from a mere 2 days ago and am in the process of
building a custom release for our internal use as preconfigured firewalls.
make release works pretty fine except for a few quirks here and there.
First of all, I have set EXTLOCALDIR so
Hi All,
I generate a bootonly ISO and want to add files to the mfsroot.gz
created by the release.8 target. I want sysinstall to load an
install.cfg which makes a call to doconfig.sh. The target destination
for the files is stand/. My question is will the below patch
accomplish this for me
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
Hi Devin,
On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske devin.te...@fisglobal.com 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
On Dec 11, 2012, at 1:50 PM, Rick Miller wrote:
Hi Devin,
On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske devin.te...@fisglobal.com
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
On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske devin.te...@fisglobal.com 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
On Dec 11, 2012, at 2:13 PM, Rick Miller wrote:
On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske devin.te...@fisglobal.com
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?
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com 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
Thanks Rob and Lowell,
I will keep this information handy. It was helpful.
On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer rfar...@predatorlabs.net wrote:
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com
wrote:
Thanks Rob...
I put the kernel conf file in the source tree
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=/MYKERNEL
ERROR: Missing kernel configuration file(s) (MYKERNEL
Rick Miller vmil...@hostileadmin.com 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
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=/MYKERNEL
ERROR: Missing kernel
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com 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
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
succeeds. Then:
cd /usr/src/release
make release RELEASETAG=RELENG_8 \
PORTSRELEASETAG=HEAD \
BUILDNAME=8.2-STABLE-$DATE \
CHROOTDIR=/share/freebsd/release \
CVSROOT=/share/freebsd/ncvs
This is always fails. Each day with different errors. I want
I want to thank everyone for their suggestions. I ended up creating a
larger swap and /tmp and reran make release with much better results.
It's not completely finished yet, but has certainly progressed much
further than the other day.
==
Vincent (Rick) Miller
Systems Engineer
vmil
Hello all,
I am attempting to 'make release' 8.2-RELEASE. After running for a few hours,
it died citing lack of disk space. The filesystem has approximately 80GB
available. How much disk space is required when making a release?
==
Vincent (Rick) Miller
Systems Engineer
vmil...@verisign.com
-Original Message-
From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
questi...@freebsd.org] On Behalf Of Miller, Vincent (Rick)
Sent: Tuesday, August 16, 2011 11:39 AM
To: FreeBSD
Subject: How much disk space required for make release?
Hello all,
I am attempting
Hi,
Reference:
From: Miller, Vincent (Rick) vmil...@verisign.com
Date: Tue, 16 Aug 2011 18:38:31 +
Message-id: ca703165.3b97%vmil...@verisign.com
Miller, Vincent (Rick) wrote:
Hello all,
I am attempting to 'make release' 8.2-RELEASE. After running for a few
On Tue, Aug 16, 2011 at 1:38 PM, Miller, Vincent (Rick)
vmil...@verisign.com wrote:
Hello all,
I am attempting to 'make release' 8.2-RELEASE. After running for a few
hours, it died citing lack of disk space. The filesystem has approximately
80GB available. How much disk space is required
Where does make release place the disk images (iso's) by default
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
-- Forwarded message --
From: Aryeh Friedman aryeh.fried...@gmail.com
Date: Thu, Jul 21, 2011 at 12:35 PM
Subject: Re: make release question
To: Nathan Whitehorn nwhiteh...@freebsd.org
On Thu, Jul 21, 2011 at 12:33 PM, Aryeh Friedman
aryeh.fried...@gmail.com wrote:
found them
infrastructure
will not be able performing a make release, or do they?
Thanks in advance,
Oliver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr
with complete ZFS infrastructure
will not be able performing a make release, or do they?
Odd I though flags were now supported on the newer zfs versions.
Try NO_SCHG=yes in /etc/make.conf as a workaround.
Vince
Thanks in advance,
Oliver
:
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 use your source tree instead of CVS and if you
want
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
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, but read all
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
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.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
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 use
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
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
release
Hi,
I've set up a src.conf so that when I do a make buildworld sendmail is
not built. That works great.
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
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
.
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 final CDROM
is with sysinstall and standard FreeBSD
tools.
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
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 final
Hi again,
Suppose I build my own FreeBSD based distro, as described in release(7).
How can I script sysinstall or replace it with another installer to
customize the installation process?
Thanks a lot.
___
freebsd-questions@freebsd.org mailing
building the release
distributions/CDs with my custom changes.
I *think* what I would like to do is customize the universe that gets
built under the chroot directory and roll a release from that, but I'm
not sure how I go about getting make release (or the mk script?) to
pick up my changes
Hi, All.
release can be build by calling commands:
make release.1 ...
...
make release.7 ...
etc.
Why need to chroot and build world again ?, may be I do not understand
all cobweb of release making process... May be exist any target-name
that starts release build stages without chroot
What is the best way to add new files into the CHROOT environment when doing
a make release?
I am trying to create my own distribution using the make release, from
release(7), mechanism. The problem is, is that I wish to add files to the
CHROOT environment. These files are my own config files
[ 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
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 creating the boot.floppy on touch release.5,
can someone take a look to see what's the reason? following is the screen
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 creating the boot.floppy on touch
release.5,
can someone take a look to see what's the reason? following is the screen dump,
with cvsup and the cvs-supfile in the examples
directory.
I used the following commands:
cd /usr/src
make buildworld
cd /usr/src/release
make release CHROOTDIR=/usr/exile BUILDNAME=EXILE SECURITY \
CVSROOT=/home/ncvs
I get the following error
error missing kernel configuration file(s) (SMP
drive?
On a related note, when I make a change to this file, can I get away
with something less than a new full make release? Is make rerelase
or something else suitable when everything else is done and I'm just
fiddling with this file?
Thanks for any pointers. When I'm done with this I think
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
Hi,
I'm running 5.4 and trying to make release of 6.0. While making release,
I got next error:
...
cvs checkout: Updating doc/zh_TW.Big5/share
cvs checkout: Updating doc/zh_TW.Big5/share/sgml
if [ -d /usr/src/release/../../ports/distfiles/ ]; then cp -rp
/usr/src/release/../../ports
Hello all
When creating a release using make release is it possible to specify the
CVSROOT using pserver or ext?
Or will I have to use NFS to mount my CVSROOT directory?
--
Antoine W. Solomon Jr.
___
freebsd-questions@freebsd.org mailing list
http
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 instead
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 instead.
would you please give me some hints on doing
is the
last part of make release:
Setting up FTP distribution area
0 blocks
0 blocks
touch ftp.1
Building CDROM live filesystem image
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
Setting up CDROM boot area
touch cdrom.1
Building CDROM disc1 filesystem image
0 blocks
0
the script working? Here is the
last part of make release:
Setting up FTP distribution area
0 blocks
0 blocks
touch ftp.1
Building CDROM live filesystem image
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
Setting up CDROM boot area
touch cdrom.1
Building CDROM disc1
i'm attempting to make a release and the build of the mfs image is failing (see
below).
it's mdconfig that's failing:
+ mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot
mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device
if fact i chroot'ed into the release directory and played around
On Fri, May 20, 2005 at 06:49:44AM -0500, William Richter wrote:
i'm attempting to make a release and the build of the mfs image is failing
(see below).
it's mdconfig that's failing:
+ mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot
mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for
well, it's the kernel that's on disc1 of the 5.4 release iso's. mdconfig
works. it just doesn't work when chroot'ed into the build directory. i've
just discovered that the /sbin/mdconfig that comes with the distribution works
when copied into the release tree (i also had to copy libc.so.5 in
Hello there,
I'm about to build a whole FreeBSD system with optimized code for my own
purposes. I've read this document:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-build.html
According this I should make a CVS mirror and follow the steps that the
documention mentions. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I cannot get make release to run. I am trying to do RELENG_4 release off of
up to date stable sources. After a couple hours of running, I get:
cc -O -pipe -mpreferred-stack-boundary=2 -I/usr/src/sys/boot/ficl
-I/usr/src/sys/boot/ficl/i386
- -I/usr
buildworld
# cd release
# make release CHROOTDIR=/local3/release BUILDNAME=5.2.1-RELEASE-p9 \
CVSROOT=/usr MAKE_ISOS=YES RELEASETAG=RELENG_5.2
Is that correct?
I have doubts about the CVSROOT variable. As far as I understood, that
variable points to the cvsrepository where you have the sources you
I'd like to make a custom live CD-2 of a -STABLE release (I want to
include the asr-tools on it, so that I can tweak my raid which is
normally running 5.2.1)
I've been doing this from /usr/src/release
sudo make release CHROOTDIR=/opus/release CVSROOT=/home/ncvs BUILDNAME=GH NODOC=
It runs
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:
1)simple make buildworld to populate /usr/obj
- make -DMAKE_ISOS -DNOPORTREADMES release \
BUILDNAME=5.2.1-RELEASE-P8-Sparc64 \
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, the
Hi All.
Please help if know.
When i try build my own release i see the problem with floppy image
building. Problem looks like this:
---
/dev/md0c: 1.4MB (2880 sectors) block size 4096, fragment size 512
using 1 cylinder groups of
://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html, and
/usr/bin/time sh -c 'make release CHROOTDIR=/hog0/release NODOC=YES
NOPORTS=YES BUILDNAME=5.2-REL-FOO CVSROOT=/hog1/FreeBSD-CVS
RELEASETAG=RELENG_5_2_1_RELEASE' | tee /tmp/release.log
Now my understanding is that 'make release' honors
sh -c 'make release CHROOTDIR=/hog0/release NODOC=YES
NOPORTS=YES BUILDNAME=5.2-REL-FOO CVSROOT=/hog1/FreeBSD-CVS
RELEASETAG=RELENG_5_2_1_RELEASE' | tee /tmp/release.log
Now my understanding is that 'make release' honors the variables set
in /etc/make.conf, where I have:
-=-
NO_OPENSSH=true
to specify it in the 'make release',
etc.)
Best Wishes - Peter
--
[ http://www.plosh.net/ ] - Earth Halted : Please Reboot
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL
, avoiding me from having
to schlep around the multi-gig repository to build releases on my various
test boxes.
I cannot seem to get the correct syntax to CVSROOT to allow make release
to pull from the networked repository and keep getting connection
refused error messages. Indeed, all the handbook
At 2003-08-05T12:17:07Z, Kirk Strauser [EMAIL PROTECTED] writes:
Seriously, noone's made release for an older version before?
--
Kirk Strauser
pgp0.pgp
Description: PGP signature
follow what's going on.
However, I don't really understand at which point I'm actually supposed to
be building the release.
I'm loosely following the example from the man page:
cd /usr/src
cvs diff -u /path/to/local.patch
make buildworld
cd release
make release CHROOTDIR=/local3
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:
total 2864
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 to
goshik# uname -a
FreeBSD goshik.binep.ac.ru 4.7-STABLE FreeBSD 4.7-STABLE #55: Wed Jan 22 13:20:00 MSK
2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GO i386
goshik# make release CVSROOT=/home/ncvs CHROOTDIR=/home/release RELEASETAG=RELENG_4
DOCLANG=en_US.ISO8859-1 MAKE_ISOS=YES
[...]
touch
Michael Dexter [EMAIL PROTECTED] writes:
Having complete control over the build of my network OS is simply
revolutionary... but I was hoping this revolution would not be so
bloody.
You can get *that* with one of the supported update options. make
release was never intended for anybody
Greetings from Latvia,
I am very, very excited about FreeBSD's make release ability but
like many others I have read about on the various list archives, I my
builds are hanging on trivial failures. In this case, the
eplaser-3.0.4-651.tgz file is failing its checksum, bringing the
build
Greetings again,
Regarding the make release mentioned earlier...
After peppering my /usr/ports/distfiles/ tree with very redundant
distfiles, i.e. the same files in /usr/ports and
/usr/ports/ghostscript and /usr/ports/ghostscript-gnu, things finally
worked. (Ending on a vn present failure
85 matches
Mail list logo
