On 28/08/2011, at 1:09, Aryeh Friedman wrote:
> I have made a custom install USB drive from R/cdrom/dvd1 and pkg_add works
> fine for everything but xorg/nvidia-driver so part of the post install
> script I made is "portmaster xorg/nvidia-driver" the only problem is it then
> needs to fetch the di
I have made a custom install USB drive from R/cdrom/dvd1 and pkg_add works
fine for everything but xorg/nvidia-driver so part of the post install
script I made is "portmaster xorg/nvidia-driver" the only problem is it then
needs to fetch the distfiles (the target install machine{s) will not have
ni
On 07/21/11 10:42, Aryeh Friedman wrote:
Where does "make release" place the disk images (iso's) by default
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any m
Where does "make release" place the disk images (iso's) by default
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
On Mon, May 17, 2010 at 12:20:07PM +0200, Bernd Walter wrote:
> On Sat, May 15, 2010 at 05:32:41PM +0200, Tjado M?cke wrote:
> >
> > > Thanks for trying to help :-) But this is in Wrong.
> > > Line 4 on that page:
> > > Last updated: 2005-08-11
> > > 5 years later, FreeBSD-8.0 has via ls -l /de
On Sat, May 15, 2010 at 05:32:41PM +0200, Tjado Mäcke wrote:
>
> > Thanks for trying to help :-) But this is in Wrong.
> > Line 4 on that page:
> > Last updated: 2005-08-11
> > 5 years later, FreeBSD-8.0 has via ls -l /dev/null
> > crw-rw-rw- 1 root wheel0, 31 May 15 14:17 /dev/null
>
> Thanks for trying to help :-) But this is in Wrong.
> Line 4 on that page:
> Last updated: 2005-08-11
> 5 years later, FreeBSD-8.0 has via ls -l /dev/null
> crw-rw-rw- 1 root wheel0, 31 May 15 14:17 /dev/null
> so both major & minor numbers have changed, command now would be
>
Hi,
=?ISO-8859-15?Q?Tjado_M=E4cke?= wrote:
> Am 13.05.2010 19:44, schrieb Julian H. Stacey:
> > Hi Hackers,
> > Problem with /dev/null & /dev/zero inside a chroot:
> > I wanted to build a release from inside a chroot
> >
> > What sort of null & zero should be in chroot ?
> > man mknod ... deprecate
On Sat, May 15, 2010 at 09:12:04AM +0200, Tjado Mäcke wrote:
> Am 13.05.2010 19:44, schrieb Julian H. Stacey:
> > Hi Hackers,
> > Problem with /dev/null & /dev/zero inside a chroot:
> > I wanted to build a release from inside a chroot
> > What sort of null & zero should be in chroot ?
> > man mkno
http://www.ijs.si/software/amavisd/README.chroot
mknod dev/nullc 2 2 # FreeBSD
Best regards
tjado
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-h
Am 13.05.2010 19:44, schrieb Julian H. Stacey:
> Hi Hackers,
> Problem with /dev/null & /dev/zero inside a chroot:
> I wanted to build a release from inside a chroot
>
> What sort of null & zero should be in chroot ?
> man mknod ... deprecated ...
> Should I be running a devfs (I'm not currently)
>
Hi,
Garrett Cooper wrote:
> On May 13, 2010, at 2:06 PM, Jilles Tjoelker wrote:
>
> > On Thu, May 13, 2010 at 07:44:58PM +0200, Julian H. Stacey wrote:
> >> Problem with /dev/null & /dev/zero inside a chroot:
> >> I wanted to build a release from inside a chroot
> >
> >> What sort of null & zero
On May 13, 2010, at 2:06 PM, Jilles Tjoelker wrote:
> On Thu, May 13, 2010 at 07:44:58PM +0200, Julian H. Stacey wrote:
>> Problem with /dev/null & /dev/zero inside a chroot:
>> I wanted to build a release from inside a chroot
>
>> What sort of null & zero should be in chroot ?
>> man mknod ... d
On Thu, May 13, 2010 at 07:44:58PM +0200, Julian H. Stacey wrote:
> Problem with /dev/null & /dev/zero inside a chroot:
> I wanted to build a release from inside a chroot
> What sort of null & zero should be in chroot ?
> man mknod ... deprecated ...
> Should I be running a devfs (I'm not currentl
Hi Hackers,
Problem with /dev/null & /dev/zero inside a chroot:
I wanted to build a release from inside a chroot
( So /var/db/pkg matches what's required by make release,
without changing packages on outside the chroot, + Also to
experiment with
1440 K, 196 left
+ echo *** 4 bytes/inode, 38 left
*** 4 bytes/inode, 38 left
+ umount /mnt
+ mdconfig -d -u md0
touch floppies.2
touch floppies.3
Setting up FTP distribution area
0 blocks
0 blocks
touch ftp.1
Release done
+ LC_ALL=C TZ=GMT date
+ echo >>> make release for
Quoting Ruben de Groot :
On Mon, Oct 26, 2009 at 02:36:39PM +0700, ???
? typed:
hi sirs,
apologized me for disturbing this list but ireally have problem s.
i make my own release by follwoing document in releng articles.
here is my command
cd /usr/src/release
On Mon, Oct 26, 2009 at 02:36:39PM +0700, ??? ?
typed:
> hi sirs,
>
> apologized me for disturbing this list but ireally have problem s.
> i make my own release by follwoing document in releng articles.
>
> here is my command
>
> cd /usr/src/release
> time make C
Quoting Ruben de Groot :
On Mon, Oct 26, 2009 at 02:36:39PM +0700, ???
? typed:
hi sirs,
apologized me for disturbing this list but ireally have problem s.
i make my own release by follwoing document in releng articles.
here is my command
cd /usr/src/release
hi sirs,
apologized me for disturbing this list but ireally have problem s.
i make my own release by follwoing document in releng articles.
here is my command
cd /usr/src/release
time make CHROOTDIR=/kaitag/KAITAG BUILDNAME=7.2-RELEASE \
CVSROOT=/var/ftp/pub/ncvs RELEASETAG=RELENG_7_2_0_RELEASE
John Baldwin wrote:
> On Tuesday 21 April 2009 4:17:53 am Manolis Kiagias wrote:
>
>> in the iso.1 target to print the values of CD and CD_DISC1_PKGS variables:
>>
>> echo "CD is ${CD}"
>> echo "CD_DISC1_PKGS is ${CD_DISC1_PKGS}"
>>
>&g
On Tuesday 21 April 2009 4:17:53 am Manolis Kiagias wrote:
> John Baldwin wrote:
> > On Saturday 18 April 2009 6:30:54 pm Manolis Kiagias wrote:
> >
> >> # make release CHROOTDIR=/data/release BUILDNAME=7.2-PRERELEASE
> >> CVSROOT=/data/ncvs EXTSRCDIR=/usr/sr
John Baldwin wrote:
> On Saturday 18 April 2009 6:30:54 pm Manolis Kiagias wrote:
>
>> # make release CHROOTDIR=/data/release BUILDNAME=7.2-PRERELEASE
>> CVSROOT=/data/ncvs EXTSRCDIR=/usr/src CD_PACKAGE_TREE=/data/packages
>> -DNODOC -DNOPORTS -DNO_FLOPPIES -DMAKE_IS
On Saturday 18 April 2009 6:30:54 pm Manolis Kiagias wrote:
> # make release CHROOTDIR=/data/release BUILDNAME=7.2-PRERELEASE
> CVSROOT=/data/ncvs EXTSRCDIR=/usr/src CD_PACKAGE_TREE=/data/packages
> -DNODOC -DNOPORTS -DNO_FLOPPIES -DMAKE_ISOS
>
> which completes, without err
Hey all,
I've been experimenting recently with 'make release' and I have a couple
of questions. A little background first:
- I've read the releng, releng-packages articles (probably out of date)
and the release man page
- I've been able to successfully run a make
Hi,
I ran into a wrongly named INDEX file today after I did a 'make release' of
RELENG_7 on a RELENG_6 system which includes the Ports Collection. The index
file is named INDEX-6 instead of INDEX-7.
A quick look in Mk/bsd.port.subdir.mk shows me that it will read the version
from t
way to do a cross release build ?
> For example release building RELENG_7 on a RELENG_6_3 system.
>
Yes, it's possible:
cd .../releng_7/src/release
make release WORLDDIR=/usr/src ...
Regards,
Marco Walraven
--
Terantula - Industrial Strength Open Source
phone:+31 64
the chrooted environment using
> 'make installkernel DESTDIR=/dir_to_chroot' and run a
> 'make rerelease' mdconfig happily accepts it and the make
> release builds successfully. The kernel I run has support
> for mdconfig; I can use memory disks without problems.
The md(4) d
at the chrooted environment I see that /boot/kernels is not populated
whereas in old builds it is. If I install a kernel into the chrooted
environment using 'make installkernel DESTDIR=/dir_to_chroot' and run a 'make
rerelease' mdconfig happily accepts it and the make release
Nar that was just me formatting it for mail commands all on one line
but thanks for the idea :)
Steve
- Original Message -
From: "Sam Lawrance" <[EMAIL PROTECTED]>
Missing a backslash on the end of NOPORTS=YES?
This e.mail is private and
On Tue, 2005-05-10 at 18:22 +0100, Steven Hartland wrote:
> My old make release command no longer works for 5.4 and I'm at a loss
> to track down the cause or to find a nice solution.
> Basically I have one build box which builds all the various releases
> structure:
> /usr
rom: "Steven Hartland" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 10, 2005 6:22 PM
Subject: make release changes?
My old make release command no longer works for 5.4 and I'm at a loss
to track down the cause or to find a nice solution.
Basically I have one build box which b
My old make release command no longer works for 5.4 and I'm at a loss
to track down the cause or to find a nice solution.
Basically I have one build box which builds all the various releases structure:
/usr/$VERSION/src
/usr/$VERSION/obj
e.g.
/usr/5.4/src
/usr/5.4/obj
With all the relavent
I knew it had to be something silly
WORLDDIR=/usr/src had been typed as WORDDIR=/usr/src
So was being ignored :( Dam
Steve
- Original Message -
From: "Steven Hartland" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 07 May 2004 16:49
Subject: make release
Im sure I must be doing something stupid but I can see what for
the file of me
cd /usr/5.2/src/release
make release \
BUILDNAME=5.2.1-RELEASE-p6 \
CHROOTDIR=/usr/local/release-5.2 \
CVSROOT=/home/ncvs \
RELEASETAG=RELENG_5_2 \
NOPORTS=YES
DOC_LANG=en_US.ISO8859-1
On Monday 17 November 2003 21:42, Dag-Erling Smørgrav wrote:
> "Daniel O'Connor" <[EMAIL PROTECTED]> writes:
> > but the way I do it is not 'normal' - I don't use the CVS repo
> > because I can't commit into that tree
>
> Be careful what you wish for :)
Heheh..
I predict great bike sheds ahoy if I
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
> but the way I do it is not 'normal' - I don't use the CVS repo
> because I can't commit into that tree
Be careful what you wish for :)
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED]
On Sat, Nov 15, 2003 at 10:14:35PM -0800, Wes Peters wrote:
> Patches or additions to existing documentation, or even just providing
> text to one of our many dedicated doco contributors, would be greatly
> appreciated. What can you do for FreeBSD today? ;^)
That's all I needed to hear. I'l
On Friday 14 November 2003 02:57 pm, Clifton Royston wrote:
> On Fri, Nov 14, 2003 at 10:48:13PM +0100, Wilko Bulte wrote:
> > On Fri, Nov 14, 2003 at 11:37:05AM -1000, Clifton Royston wrote:
> > > Is this as good a list as any for observations on the FreeBSD
> > >
rnal release with a reduced set of base binaries, different
> packages available on CD for install, etc. However, I certainly ran
> into more pitfalls than I expected along the way, and a lot less detail
> and more handwaving than I expected in the docs I could find.
I have a procedure for
On Fri, Nov 14, 2003 at 10:48:13PM +0100, Wilko Bulte wrote:
> On Fri, Nov 14, 2003 at 11:37:05AM -1000, Clifton Royston wrote:
> > Is this as good a list as any for observations on the FreeBSD "make
> > release" process? I can't see any other list that fits the
On Fri, Nov 14, 2003 at 11:37:05AM -1000, Clifton Royston wrote:
> Is this as good a list as any for observations on the FreeBSD "make
> release" process? I can't see any other list that fits the subject.
Did you dig into http://www.freebsd.org/releng/
Is this as good a list as any for observations on the FreeBSD "make
release" process? I can't see any other list that fits the subject.
I have some observations fairly fresh in my mind from trying to build
a version of FreeBSD 4.8.12 with the IBM Propolice anti-stack-smash
p
On Wed, Jul 17, 2002 at 11:40:01AM -0700, Terry Lambert wrote:
> The "normal" way to do this, barring any gratuitous system call
> changes(*), is to take the "DISC2" FS image, copy it into a
> directory, chroot into the directory, and do the build in the
> chroot'ed environment.
I was considering
Brian Reichert wrote:
> What I had hoped to do was maintain a single build box, on
> which I could maintain the presence of several releases.
>
> I had explored trying to mirror various FTP archives, but I was
> finding difficult to gauge what I needed for diskspace, and how to
> selectively pare
On Tue, Jul 16, 2002 at 11:09:15PM -0700, Terry Lambert wrote:
> Brian Reichert wrote:
> > Can someone suggest the be FreeBSD mailing list wherein I could
> > explore issues I'm having with trying to build a 4.6-STABLE release
> > on a 4.5-RELEASE box?
> >
> > I don't know if this is a -hackers q
Brian Reichert wrote:
> Can someone suggest the be FreeBSD mailing list wherein I could
> explore issues I'm having with trying to build a 4.6-STABLE release
> on a 4.5-RELEASE box?
>
> I don't know if this is a -hackers question, or a -stable question,
> or what. (I've looked at the list of lis
Can someone suggest the be FreeBSD mailing list wherein I could
explore issues I'm having with trying to build a 4.6-STABLE release
on a 4.5-RELEASE box?
I don't know if this is a -hackers question, or a -stable question,
or what. (I've looked at the list of lists majordomo knows about,
and I do
reichert> How to I transform a RELEASETAG into a BUILDNAME? I suspect
reichert> I really need some meta-knowledge about what tags are in the
reichert> CVS tree...
I used to check src/sys/conf/newvers.sh.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
ned.
>
> Ya, it should be documented in release(7) IMO...
>
> reichert> Now, if only I could automate a relationship between
> reichert> RELEASETAG and BUILDNAME...
>
> You can set both RELEASETAG and BUILDNAME in your own shell script
> which kicks "make releas
could automate a relationship between
reichert> RELEASETAG and BUILDNAME...
You can set both RELEASETAG and BUILDNAME in your own shell script
which kicks "make release". That's just a shell-script programming problem:)
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EM
co -r $RELEASETAG src && cd src && \
/usr/bin/time make $WORLD_FLAGS buildworld && \
cd release && /usr/bin/time make release
...
2693.85 real 2818.31 user 1007.08 sys
>>> make release started on Tue Jul 9 16:59:46 GMT 200
y, you did ask a specific question. No, I hadn't tried those
flags, so I can't say that they would have worked...
> Yes, it would be better that whole release procedure works with make
> -jN, but most of the time spent is "make buildworld/buildkernel" during
> "ma
is "make buildworld/buildkernel" during
"make release," so setting WORLD_FLAGS/KERNEL_FLAGS may be enough to do.
reichert> ===> Patching for ghostscript-gnu-nox11-7.05_1
reichert> ===> Applying FreeBSD patches for ghostscript-gnu-nox11-7.05_1
reichert>
On Sun, Jul 07, 2002 at 03:41:28AM +0900, Makoto Matsushita wrote:
>
> reichert> It was rather disappointing that I couldn't run 'make release' in
> reichert> parallel via the '-j' option, though. :/
>
> WORLD_FLAGS and/or KERNEL_FLAGS don
reichert> It was rather disappointing that I couldn't run 'make release' in
reichert> parallel via the '-j' option, though. :/
WORLD_FLAGS and/or KERNEL_FLAGS don't work for you?
reichert> How disparate can the host OS version be from the version
re
On Wed, Jul 03, 2002 at 11:33:04AM +0900, Makoto Matsushita wrote:
>
> src/release/Makefile assumes that src/release directory is actually
> /usr/src/release. It seems that your source code location is /home/src.
Woo-hoo! I finally got a 'make release' to work! Thanks for
> /usr/bin/time make release \
> reichert> CHROOTDIR=/home/release \
> reichert> BUILDNAME=4.5-RELEASE \
> reichert> CVSROOT=/home/ncvs \
> reichert> RELEASETAG=RELENG_4_5_0_RELEASE
>
> DOCDISTFILES=/your/ports/distfile/directory will help you.
src/release/Makefile assumes that src/release directory is actually
/usr/src/release. It seems that your source code location is /home/src.
reichert> /usr/bin/time make release \
reichert> CHROOTDIR=/home/release \
reichert> BUILDNAME=4.5-RELEASE \
reichert> CVSROO
On Tue, Jul 02, 2002 at 03:46:18PM -0700, Don Lewis wrote:
> On 2 Jul, Brian Reichert wrote:
> > I'm mucking with 'make release' under 4.5-RELEASE, and keep running
> > into a stumbling block:
> >
> > When the documentation toolset is being built in
On 2 Jul, Brian Reichert wrote:
> I'm mucking with 'make release' under 4.5-RELEASE, and keep running
> into a stumbling block:
>
> When the documentation toolset is being built in the chrooted
> environment, at one point docbook-dsssl-doc is built, a
I'm mucking with 'make release' under 4.5-RELEASE, and keep running
into a stumbling block:
When the documentation toolset is being built in the chrooted
environment, at one point docbook-dsssl-doc is built, among other
things, via ports.
Regrettably, this is hosted on Sour
kerberus> There is not a
kerberus> /usr/release/usr/src/contrib/nvi/docs/USD.doc/vi.ref/ref.so?
kerberus> in the directory.
That file should be there. It's your local problem if it is not
extracted from your CVS repository copy.
kerberus> i modified the usr/src/release/Makefile to use the
kerb
There is not a
/usr/release/usr/src/contrib/nvi/docs/USD.doc/vi.ref/ref.so?
in the directory. and i modified the usr/src/release/Makefile to use the
4.4-stable tag.
>
> Would you please check that your buildbox has a file
> /usr/release/usr/src/contrib/nvi/docs/USD.doc/vi.ref/ref.so?
>
> And, y
Repeat again.
kerberus> it builds a tree, cvs's the src goes into its build stage, and again,
kerberus> fails with a fresh cvsup from today, which did a complete make world
kerberus> kernel from the standard /usr/src, now can some one tell me what im
kerberus> missing or doing wrong ?? and yes i
Okay ive setup a /usr/cvs, exported CVSROOT /usr/cvs, cd'd into
/usr/cvs, cvs init, cd'd to /usr/src, cvs import src devel beta, all
went fine and created a /usr/cvs/src . cd'd to /usr/src
setenv CVSROOT /usr/cvs
setenv CHROOTDIR /usr/release
make release
churn churn churn
i
Its a 4.4-Stable box, actually it does the same thing on three different
4.4-Stable boxes. make world works, so does installworld, make release
barfs. It exists in my standard /usr/src, but not in the checked out
chrooted build tree.
On Sun, 2001-12-02 at 00:50, Makoto Matsushita wrote:
>
&g
You may want to mention that which branch (5-current, 4-stable, etc)
you wanna try. Also you may want to clear that when you sup your code.
kerberus> ===> share/doc/usd/13.viref
kerberus> make: don't know how to make ref.so. Stop
kerberus> *** Error code 2
src/contrib/nvi/docs/USD.doc/vi.ref/r
It just fails ...
touch _stamp.extraobjs
(cd
/usr/src/share/doc/usd/11.vitut/../../../../contrib/nvi/docs/USD.doc/edit; g
roff -mtty-char -Tascii -t -ms -o1-
/usr/src/share/doc/usd/11.vitut/../../../../
contrib/nvi/docs/USD.doc/edit/edittut.ms) | gzip -cn > paper.ascii.gz
===> share/doc/usd/12.v
On Sat, Dec 01, 2001 at 05:05:21AM -0800, Seth Kingsley wrote:
> On Sat, Dec 01, 2001 at 01:22:35AM -0500, kerberus wrote:
> > Okay ill ask again just in case nobody saw this!
> > is make release broken in 4.4-STABLE ?? Or is there a definitive
> > guide/FAQ on how to properl
On Sat, Dec 01, 2001 at 01:22:35AM -0500, kerberus wrote:
> Okay ill ask again just in case nobody saw this!
> is make release broken in 4.4-STABLE ?? Or is there a definitive
> guide/FAQ on how to properly use make release to cut a modified
> distribution ? cause either im doing som
Okay ill ask again just in case nobody saw this!
is make release broken in 4.4-STABLE ?? Or is there a definitive
guide/FAQ on how to properly use make release to cut a modified
distribution ? cause either im doing something wrong, or its definatley
broken. Thanks in Advance
To Unsubscribe
Hello there!
I just read FAQ on making release and have one question. FAQ says I must
be having full CVS source tree (or be able to access it via CVSROOT), but
I'm behind modem connection. So I'm curious why it is not enough to have
a cvsupped src-all/doc-all/ports-all collections? And is there a
On Tue, Aug 08, 2000 at 05:36:26PM -0500, Alan Edmonds wrote:
> This was brought up last week; I'm not sure if it was this list.
>
> See /usr/share/examples/worm for a couple of scripts used
> to create the FreeBSD release CDs. Very informative.
>
> Ben Smithurst wrote:
> >
> > Mario Sergio Fu
This was brought up last week; I'm not sure if it was this list.
See /usr/share/examples/worm for a couple of scripts used
to create the FreeBSD release CDs. Very informative.
Ben Smithurst wrote:
>
> Mario Sergio Fujikawa Ferreira wrote:
>
> > 1) (cont.) I could use burncd but I am bug
Mario Sergio Fujikawa Ferreira wrote:
> 1) (cont.) I could use burncd but I am bugged by the fact
> that I can't use cdrecord. :)
Why? I think it was designed for SCSI devices, and you don't have one, so
just use burncd.
> 2) How do I make it a full-fledged FreeBSD bootable
> distr
Hi,
I know I should know better. Please do not flame me. Well,
I did a good 1st make release on my little stable (cvsupped
07/08/2000) machine. I have disc[12] under cdrom. Everything looks
fine. But (there is always a but)
Does anyone have a 'burn the CD' cook
On Tue, 1 Feb 2000, Daniel O'Connor wrote:
>
> On 31-Jan-00 R.I.Pienaar wrote:
> > how do i incorporate the XFree stuff into a freebsd release so that
> > it is in
> > acceptable format for sysinstall?
>
> Download the binary packages from XFree86.org..
>
> Someone was working on making the
On 31-Jan-00 R.I.Pienaar wrote:
> how do i incorporate the XFree stuff into a freebsd release so that
> it is in
> acceptable format for sysinstall?
Download the binary packages from XFree86.org..
Someone was working on making the port produce tarballs that look like
the XFree86 ones but I d
hi,
I have been looking at the make release process, and have succesfully made a
3.4 snapshot release, my problem is it doesnt build/install any X stuff.
how do i incorporate the XFree stuff into a freebsd release so that it is in
acceptable format for sysinstall?
--
R.I. Pienaar [EMAIL
80 matches
Mail list logo
