freebsd-stable Digest, Vol 349, Issue 3
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. Re: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS
(doesn't link with libzfsboot) (John Baldwin)
2. 7.3-RELEASE sysinstall netDev feature (David Boyd)
3. Re: 7.3-RELEASE sysinstall netDev feature (Rink Springer)
4. RE: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS
(doesn't link with libzfsboot) (Alexander Zagrebin)
5. Re: 7.3-RELEASE sysinstall netDev feature (Randi Harper)
6. Re: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS
(doesn't link with libzfsboot) (John Baldwin)
7. Re: 7.3-RELEASE sysinstall netDev feature (Randi Harper)
8. FYI - FreeBSD 7.3 has been released... (Ken Smith)
9. Re: Complete ports thaw (Mark Linimon)
10. Re: Can't boot after make installworld (Mark Linimon)
11. Re: Can't boot after make installworld (Jeremy Chadwick)
----------------------------------------------------------------------
Message: 1
Date: Tue, 23 Mar 2010 10:09:54 -0400
From: John Baldwin <j...@freebsd.org>
Subject: Re: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS
(doesn't link with libzfsboot)
To: freebsd...@freebsd.org
Cc: Alexander Zagrebin <al...@visp.ru>
Message-ID: <20100323100...@freebsd.org>
Content-Type: Text/Plain; charset="koi8-r"
On Tuesday 23 March 2010 3:41:06 am Alexander Zagrebin wrote:
> I have tried to build RELENG_7_3_0_RELEASE and have noticed that zfsloader
> really doesn't supports ZFS due to incomplete Makefiles (LOADER_ZFS_SUPPORT
> issue).
> Will be this issue fixed in 7.3-RELEASE?
Can you provide the output of the errors you are seeing?
--
John Baldwin
------------------------------
Message: 2
Date: Tue, 23 Mar 2010 12:19:11 -0400
From: "David Boyd" <David...@insightbb.com>
Subject: 7.3-RELEASE sysinstall netDev feature
To: <freebsd...@freebsd.org>
Message-ID: <OJEBKOFDEOADELCOBJC...@insightbb.com>
Content-Type: text/plain; charset="iso-8859-1"
The 7.3-RELEASE release notes indicate that sysinstall now supports a list
of network interfaces in the netDev (install.cfg) parameter.
After upgrading to 7.3-RELEASE (via csup) sysinstall does not seem to
support that feature.
Also, the man page doesn't contain any mention of the new feature.
Is this the code committed by Rink Springer last October?
This feature would sure be great for our many scripted installs (avoiding
the hassles associated with plugging the cable into the wrong interface or
having the interface type change unexpectedly due to hardware swaps).
Thanks.
------------------------------
Message: 3
Date: Tue, 23 Mar 2010 17:47:25 +0100
From: Rink Springer <ri...@FreeBSD.org>
Subject: Re: 7.3-RELEASE sysinstall netDev feature
To: David Boyd <David...@insightbb.com>
Cc: freebsd...@freebsd.org
Message-ID: <20100323164...@rink.nu>
Content-Type: text/plain; charset=us-ascii
Hi David,
On Tue, Mar 23, 2010 at 12:19:11PM -0400, David Boyd wrote:
> Is this the code committed by Rink Springer last October?
The code I committed (revision 198317) added support for 'netDev=ANY';
this would select the first device that has an active link.
Note that the value is case sensitive, so only using 'ANY' will work.
> This feature would sure be great for our many scripted installs (avoiding
> the hassles associated with plugging the cable into the wrong interface or
> having the interface type change unexpectedly due to hardware swaps).
What exactly happens in such a case? Is the line planly ignored? Are you
using a non-interactive install?
Regards,
--
Rink P.W. Springer - http://rink.nu
"Beauty often seduces us on the road to truth."
- Dr. Wilson
------------------------------
Message: 4
Date: Tue, 23 Mar 2010 22:27:24 +0300
From: "Alexander Zagrebin" <al...@visp.ru>
Subject: RE: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS
(doesn't link with libzfsboot)
To: "'John Baldwin'" <j...@freebsd.org>
Cc: freebsd...@freebsd.org
Message-ID: <B7C3DB99508C418A...@vosz.local>
Keywords: freebsd-stable
Content-Type: text/plain; charset="koi8-r"
> On Tuesday 23 March 2010 3:41:06 am Alexander Zagrebin wrote:
> > I have tried to build RELENG_7_3_0_RELEASE and have noticed
> that zfsloader
> > really doesn't supports ZFS due to incomplete Makefiles
> (LOADER_ZFS_SUPPORT
> > issue).
> > Will be this issue fixed in 7.3-RELEASE?
>
> Can you provide the output of the errors you are seeing?
There are no build errors.
IMHO, to support a ZFS, the loader have to be linked with the libzfsboot.
But (IMHO again) in the RELENG_7_3_0_RELEASE zfsloader builds without
this library.
To build zfsloader, the /usr/src/sys/boot/i386/zfsloader/Makefile contains
the following most important lines:
LOADER_ZFS_SUPPORT=yes
...
.include "${.CURDIR}/../loader/Makefile"
So the /usr/src/sys/boot/i386/loader/Makefile have to set required CFLAGS
and so on,
but it don't. It contains the folowing ZFS related lines:
# Set by zfsloader Makefile
#.if ${MK_ZFS} != "no"
#CFLAGS+= -DLOADER_ZFS_SUPPORT
#LIBZFS= ${.OBJDIR}/../../zfs/libzfsboot.a
#.else
LIBZFS=
#.endif
As you can see, all ZFS related stuff is commented out.
So "LOADER_ZFS_SUPPORT=yes" (/usr/src/sys/boot/i386/zfsloader/Makefile)
doesn't
affects a build process.
--
Alexander Zagrebin
------------------------------
Message: 5
Date: Tue, 23 Mar 2010 12:58:13 -0700
From: Randi Harper <ra...@freebsd.org>
Subject: Re: 7.3-RELEASE sysinstall netDev feature
To: Rink Springer <ri...@freebsd.org>
Cc: David Boyd <David...@insightbb.com>, freebsd...@freebsd.org
Message-ID:
<e277d6c81003231258k58d...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Mar 23, 2010 at 9:47 AM, Rink Springer <ri...@freebsd.org> wrote:
> Hi David,
>
> On Tue, Mar 23, 2010 at 12:19:11PM -0400, David Boyd wrote:
>> Is this the code committed by Rink Springer last October?
>
> The code I committed (revision 198317) added support for 'netDev=ANY';
> this would select the first device that has an active link.
>
> Note that the value is case sensitive, so only using 'ANY' will work.
>
>> This feature would sure be great for our many scripted installs (avoiding
>> the hassles associated with plugging the cable into the wrong interface or
>> having the interface type change unexpectedly due to hardware swaps).
>
> What exactly happens in such a case? Is the line planly ignored? Are you
> using a non-interactive install?
>
> Regards,
>
> --
> Rink P.W. Springer - http://rink.nu
> "Beauty often seduces us on the road to truth."
> - Dr. Wilson
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
If you can enable debugging and take a look at the debug console, that
output would be helpful. What exactly are you specifying for netDev?
ANY or a comma delimited list of interfaces? Is it saying that it
can't find a network interface or is it prompting you to select one?
-- randi
------------------------------
Message: 6
Date: Tue, 23 Mar 2010 17:39:36 -0400
From: John Baldwin <j...@freebsd.org>
Subject: Re: upcoming 7.3-RELEASE: zfsloader doesn't support ZFS
(doesn't link with libzfsboot)
To: freebsd...@freebsd.org
Cc: Alexander Zagrebin <al...@visp.ru>
Message-ID: <20100323173...@freebsd.org>
Content-Type: Text/Plain; charset="koi8-r"
On Tuesday 23 March 2010 3:27:24 pm Alexander Zagrebin wrote:
> > On Tuesday 23 March 2010 3:41:06 am Alexander Zagrebin wrote:
> > > I have tried to build RELENG_7_3_0_RELEASE and have noticed
> > that zfsloader
> > > really doesn't supports ZFS due to incomplete Makefiles
> > (LOADER_ZFS_SUPPORT
> > > issue).
> > > Will be this issue fixed in 7.3-RELEASE?
> >
> > Can you provide the output of the errors you are seeing?
>
> There are no build errors.
>
> IMHO, to support a ZFS, the loader have to be linked with the libzfsboot.
> But (IMHO again) in the RELENG_7_3_0_RELEASE zfsloader builds without
> this library.
Oh, gah. Fixed in 7. Probably too late for 7.3.
--
John Baldwin
------------------------------
Message: 7
Date: Tue, 23 Mar 2010 15:09:31 -0700
From: Randi Harper <ra...@freebsd.org>
Subject: Re: 7.3-RELEASE sysinstall netDev feature
To: David Boyd <David...@insightbb.com>
Cc: Rink Springer <ri...@freebsd.org>, freebsd...@freebsd.org
Message-ID:
<e277d6c81003231509l359...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Mar 23, 2010 at 1:51 PM, David Boyd <David...@insightbb.com> wrote:
> Randi,
>
> Sorry for taking so long to reply.
>
> I won't be able to retry this today.
>
> But I looked at the code in tcpip.c and the support for the comma separated
> list of interface names (or netDev=ALL) is just not there in 7.3-RELEASE.
>
> I looked at the csup'd source and at the source from the dvd1 image.
Yeah, I suspect this wasn't MFC'ed and the release notes will need to
be corrected. I'm going to double check this later tonight. FWIW, if
this is something you are really that interested in having work, it
will work just fine in 7.3-RELEASE, you'd just have to build it
yourself.
-- randi
------------------------------
Message: 8
Date: Tue, 23 Mar 2010 18:29:34 -0400
From: Ken Smith <kens...@buffalo.edu>
Subject: FYI - FreeBSD 7.3 has been released...
To: freebsd...@freebsd.org
Message-ID: <4BA940CE...@buffalo.edu>
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just a quick note for any of you who are not subscribed to the
freebsd-announce@ mailing list.
7.3-RELEASE was announced today. The announcement message is
available here:
http://www.freebsd.org/releases/7.3R/announce.html
Thanks.
- --
Ken Smith
- - From there to here, from here to | kens...@buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkupQM4ACgkQ/G14VSmup/ZXLgCdF63w0KJV6fU/NbeNWHAQ4lar
3TsAoIwRSTyijFSb8SiZh2+91WDr0Gh1
=CUdv
-----END PGP SIGNATURE-----
------------------------------
Message: 9
Date: Tue, 23 Mar 2010 17:31:26 -0500
From: Mark Linimon <lin...@lonesome.com>
Subject: Re: Complete ports thaw
To: FreeBSD portmgr secretary <portmgr-...@FreeBSD.org>
Cc: po...@FreeBSD.org, sta...@FreeBSD.org, cur...@FreeBSD.org
Message-ID: <2010032322...@lonesome.com>
Content-Type: text/plain; charset=us-ascii
It probably bears repeating that the tree will be unstable for the next
few days while a number of large commits hit the tree. These were held
off during the release process to make life easier in case portmgr had
to do tag-slips.
Image processing libraries, xorg, kde, and gnome are scheduled to be
updated, among others.
mcl
------------------------------
Message: 10
Date: Wed, 24 Mar 2010 02:54:51 -0500
From: Mark Linimon <lin...@lonesome.com>
Subject: Re: Can't boot after make installworld
To: Krzysztof Dajka <alte...@gmail.com>
Cc: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>, Dan
Naumov <dan.n...@gmail.com>
Message-ID: <20100324075...@lonesome.com>
Content-Type: text/plain; charset=us-ascii
On Mon, Mar 22, 2010 at 08:41:35PM +0000, Krzysztof Dajka wrote:
> But still I am confused with FreeBSD naming and it's relation with
> tags which are used in standard-supfile.
Please see the following for an overview:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html#CURRENT
The definition of the -STABLE branches is that we try to keep the interfaces
to the kernel stable. While this helps also keep the src tree itself stable,
from time to time regressions will be introduced as changes are merged back
from the -CURRENT branch.
So, for the src tree, there are:
- releases, which are not updated;
- releases plus security fixes;
- -STABLE branches;
- the -CURRENT branch.
The ports tree is not branched, so you can consider that everything is
"current". If you need to stay with a ports tree that is more tested,
you'll need to stay with the ports tree that came with a -release.
mcl
------------------------------
Message: 11
Date: Wed, 24 Mar 2010 01:49:23 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: Can't boot after make installworld
To: Krzysztof Dajka <alte...@gmail.com>
Cc: freebsd...@freebsd.org
Message-ID: <20100324084...@icarus.home.lan>
Content-Type: text/plain; charset=us-ascii
On Mon, Mar 22, 2010 at 08:41:35PM +0000, Krzysztof Dajka wrote:
> At first I didn't knew that I am upgrading to bleeding edge/developer
> branch of FreeBSD.
You're not. There seems to be some misconceptions with regards to what
the tags represent, because people's opinions get in the way (mine
included).
I'll give you the run down as someone who's been using FreeBSD since the
2.2 days. I'm speaking strictly about src (base system, OS, etc.) and
not ports. Ports are their own thing, and aren't tagged (the ports
infrastructure should work on any of the below tags, which is why ports
are always tag=.).
I also include correlations to Debian release nomenclature. Hope this
helps.
-RELEASE (tag=RELENG_x_y)
An official release of the OS when a new version comes out. Changes to
this tag are rarely made; the exceptions to the rule are security fixes
and *serious* (major/extreme) stability fixes. "Serious" means
something that would impact the OS from functioning for all systems and
is considered volatile -- it does not mean "feature X doesn't work
right" or "driver X doesn't function correctly". Users who encounter a
problem of this nature are told to run -STABLE where the fix is.
The FreeBSD user community often totes this as "the most rock solid
release tag there is", which in my opinion hasn't been the case since
the 4.x days. We've used the STABLE branches since the 4.x days and
have only run into problems on rare occasion (rolling back to a previous
commit is as easy as using csup's "date" tag in the supfile).
In the Debian world, this tag would correlate with stable/lenny.
-STABLE (tag=RELENG_x)
Identical to RELEASE except changes to this tag are made fairly
regularly. OS/kernel, drivers, base system/userland, and security
issues are all addressed here. Meaning: if you encounter something
broken in non-CURRENT FreeBSD, the fix/change will most likely go into
this branch. The more you read popular FreeBSD mailing lists
(freebsd-stable, freebsd-users, freebsd-questions, etc.), the more
you'll realise that's the case.
MFCs ("merge from CURRENT") are also occasionally brought down from HEAD
(see below) into this branch for usability testing. This is where
anti-STABLE advocates get their "STABLE isn't stable at all, use RELEASE
if you want stability" viewpoint.
The FreeBSD user community has split opinions of this branch; some
believe it to be "a development/unstable" branch, while others (like
myself) believe it to be more solid than RELEASE, since developers are
much more focused on STABLE than RELEASE. Developers who break the
STABLE branch are usually lectured/reprimanded in some way; such
breakage usually appears as buildworld/buildkernel failing. Turnaround
time for fixing such breakage is usually 24-48 hours tops.
In the Debian world, this tag would correlate with testing/squeeze.
-CURRENT (tag=., otherwise known as HEAD)
This is where all the crazy, in-development code and features go. That
includes library API changes, kernel ABI changes, kernel threading
adjustments, experimental drivers ("it works on this one system I have
at home but that's it"), or anything else a developer/committer is
working on which is brand-spanking-new. It also encapsulates major
underlying configuration changes in the OS, including pathname changes
or syntactical changes. The OS is also significantly slower
(kernel-wise out-of-the-box due to the default kernel configs enabling
debugging/analysis features which are necessary for development.
This branch is known to break quite often, and that's 100% OK. Data
loss can happen as well, depending on what breaks or what bugs are
introduced, so if you run this you should absolutely do back-ups.
In the Debian world, this tag would correlate with unstable/sid.
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
------------------------------
End of freebsd-stable Digest, Vol 349, Issue 3
**********************************************