Re: FreeBSD 5.0 RC3 now available

[Bruce A. Mah]

If memory serves me right, "Craig Reyenga" wrote:
> >No matter what, disc#1 has a finite amount of space and it's going to be
> >impossible to come up with a combination of packages that keeps everyone
> >happy.  Sooner or later, "popular" comes down to somebody's judgement.
> >
> >To see what's currently in the package split, look at
> >src/release/scripts/print-cdrom-packages.sh (for whatever branch
> >interests you).  Note that in addition to the packages listed there, we
> >also need to put all of their dependencies on disc#1 as well.  These
> >dependencies likely account for a lot of the "small packages and
> >ones that are not popular seem to make in on the first CD".
> >
> 
> Looking at the script, it would appear that the current method used is
> simply a combination of the two different ideas. I guess now I should be
> saying, "Please add Mozilla and Apache to the script."

We've talked about adding mozilla.  That will probably happen 
(actually, it was just added to HEAD's package split, and will probably 
get MFC-ed to RELENG_5_0).  Haven't seen any discussion of apache, not 
sure why it's not there.

I'm not real keen on making lots of changes to the package split at this
point (if you look at where we are in the release schedule, we're *real*
close to releasing).  Every unnecessary change we make carries with it a
certain risk that could delay the release.

Hoping to forestall a flood of email to re@ saying "Please add my
favorite package!", let me say:  The time to advocate changes is
*between* releases, not when you've just seen the last RC snapshot
and want the RE team to make some change in the few days before rolling 
the final product.  We're more likely to give some actual thought to 
changes proposed in the early stages of the process, as opposed to near 
the end when it seems like we're always fighting various fires that 
blaze up.

> >(FYI, the 5.0-RC3 package set occupies 339MB of a 560MB ISO image.)
> 
> If the ISO is currently 560MB, then we have 90MB to spare right?

Yeah, but:  1) We need to leave some space for vendors to add other
stuff they might want to put on the disc.  2) Some of the packages I've
seen discussed would eat up a lot of that (I have an OpenOffice package
sitting on my workstation that weighs in at 66MB, not counting any 
dependencies it may have).

FYI, my preferred window manager isn't on disc#1, nor are my preferred
MUA or Web browser.  But I think that disc#1 has a package set that's
useful to most people.

Cheers,

Bruce.





msg50299/pgp0.pgp
Description: PGP signature

Re: FreeBSD 5.0 RC3 now available

[Craig Reyenga]

>No matter what, disc#1 has a finite amount of space and it's going to be
>impossible to come up with a combination of packages that keeps everyone
>happy.  Sooner or later, "popular" comes down to somebody's judgement.
>
>To see what's currently in the package split, look at
>src/release/scripts/print-cdrom-packages.sh (for whatever branch
>interests you).  Note that in addition to the packages listed there, we
>also need to put all of their dependencies on disc#1 as well.  These
>dependencies likely account for a lot of the "small packages and
>ones that are not popular seem to make in on the first CD".
>

Looking at the script, it would appear that the current method used is
simply a combination of the two different ideas. I guess now I should be
saying, "Please add Mozilla and Apache to the script."

>(FYI, the 5.0-RC3 package set occupies 339MB of a 560MB ISO image.)

If the ISO is currently 560MB, then we have 90MB to spare right?

-Craig


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[David Cuthbert]

Harald Hanche-Olsen wrote:

Indeed.  There is an old story from the days of the big irons, when
IBM had an "objective" release criterion stating that no new release
of their OS would be shipped with more than 100 major bugs.

As a result, before each release, the engineers would have a big
meeting with the purpose of redefining major bugs as minor bugs.


You make it sound like that doesn't happen anymore.  Ah, sadly, it does, 
and I've been known to be an unwilling participant... :-\

Though we actually go as far as to reclassify bugs as enhancement requests.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Bruce A. Mah]

If memory serves me right, "Craig Reyenga" wrote:
> These mentioned licensing issues make sense, however I still think that
> there should be some sort of system to ensure big and/or popular packages to
> make it to CD #1.

No matter what, disc#1 has a finite amount of space and it's going to be
impossible to come up with a combination of packages that keeps everyone
happy.  Sooner or later, "popular" comes down to somebody's judgement.

To see what's currently in the package split, look at 
src/release/scripts/print-cdrom-packages.sh (for whatever branch 
interests you).  Note that in addition to the packages listed there, we 
also need to put all of their dependencies on disc#1 as well.  These 
dependencies likely account for a lot of the "small packages and 
ones that are not popular seem to make in on the first CD".

(FYI, the 5.0-RC3 package set occupies 339MB of a 560MB ISO image.)

Bruce.





msg50259/pgp0.pgp
Description: PGP signature

Re: FreeBSD 5.0 RC3 now available

[Kris Kennaway]

On Tue, Jan 14, 2003 at 09:44:06PM -0500, Craig Reyenga wrote:
> These mentioned licensing issues make sense, however I still think that
> there should be some sort of system to ensure big and/or popular packages to
> make it to CD #1.

Request it.

Bear in mind that disc 1 has limited free space.

Kris



msg50256/pgp0.pgp
Description: PGP signature

Re: FreeBSD 5.0 RC3 now available

[Kris Kennaway]

On Tue, Jan 14, 2003 at 08:14:11PM -0500, Craig Reyenga wrote:
> I haven't actually tried 5.0RC3 yet, so what I'm about to say may be
> irrelevant, but here goes:
> 
> One thing I noticed in previous releases is that the choice of packages is a
> little odd. Many small packages and ones that are not popular seem to make
> it on the first CD, while bigger and/or more popular ones are stuck being
> fetched+built manually after. This can be a pain on slower computers,
> especially with ports such as mozilla and openoffice. I guess what I am
> suggesting is that more attention be paid to _which_ ports make in onto CD
> #1. Perhaps one way of doing this is to give each port a "pkg-priority" that
> the release build scripts scan for. Anyways, that's just my $0.02, might be
> $0.00 in this case.

mozilla will probably be included on cd #1, but the openoffice package
still does not build automatically (problems with the JDK dependency).
Regardless, thousands of packages are included on the other CDs
available for purchase, and they're all (6525 on i386) on the FTP site
for automatic download with pkg_add -r.

Kris



msg50255/pgp0.pgp
Description: PGP signature

Re: FreeBSD 5.0 RC3 now available

[Craig Reyenga]

These mentioned licensing issues make sense, however I still think that
there should be some sort of system to ensure big and/or popular packages to
make it to CD #1.

-Craig

> > One thing I noticed in previous releases is that the choice of
> > packages is a
> > little odd. Many small packages and ones that are not popular seem to
make
> > it on the first CD, while bigger and/or more popular ones are stuck
being
> > fetched+built manually after. This can be a pain on slower computers,
> > especially with ports such as mozilla and openoffice. I guess what I am
> > suggesting is that more attention be paid to _which_ ports make in onto
CD
> > #1.
>
>
> Doesn't OpenOffice.Org require the Sun JDK? If so, might that be a bit
> of a problem due to licensing restrictions?
>
> I wouldn't see a problem with Mozilla, though. Except that it is quite,
> quite bloated. ;)
>
> Keith
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[James Pole]

On Wed, 2003-01-15 at 14:25, Keith Jones wrote:
> Craig Reyenga wrote:
> 
> > One thing I noticed in previous releases is that the choice of 
> > packages is a
> > little odd. Many small packages and ones that are not popular seem to make
> > it on the first CD, while bigger and/or more popular ones are stuck being
> > fetched+built manually after. This can be a pain on slower computers,
> > especially with ports such as mozilla and openoffice. I guess what I am
> > suggesting is that more attention be paid to _which_ ports make in onto CD
> > #1.
>
> Doesn't OpenOffice.Org require the Sun JDK? If so, might that be a bit 
> of a problem due to licensing restrictions?

AFAIK It actually dosn't require JDK in order to run althought it does
require it to build from ports. This is AFAIK though. Every time I
install OpenOffice (either on Windows or FreeBSD) I tend to avoid
installing or using Java and it still works flawlessly (even on
Windows!).

OpenOffice is written in C/C++ anyway.

- James

-- 
James Pole

ICQ: 21721828
AIM: kiwijames1986
MSN: [EMAIL PROTECTED]
SMS: +64-210-455-139


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Keith Jones]

Craig Reyenga wrote:


One thing I noticed in previous releases is that the choice of 
packages is a
little odd. Many small packages and ones that are not popular seem to make
it on the first CD, while bigger and/or more popular ones are stuck being
fetched+built manually after. This can be a pain on slower computers,
especially with ports such as mozilla and openoffice. I guess what I am
suggesting is that more attention be paid to _which_ ports make in onto CD
#1.


Doesn't OpenOffice.Org require the Sun JDK? If so, might that be a bit 
of a problem due to licensing restrictions?

I wouldn't see a problem with Mozilla, though. Except that it is quite, 
quite bloated. ;)

Keith


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Craig Reyenga]

I haven't actually tried 5.0RC3 yet, so what I'm about to say may be
irrelevant, but here goes:

One thing I noticed in previous releases is that the choice of packages is a
little odd. Many small packages and ones that are not popular seem to make
it on the first CD, while bigger and/or more popular ones are stuck being
fetched+built manually after. This can be a pain on slower computers,
especially with ports such as mozilla and openoffice. I guess what I am
suggesting is that more attention be paid to _which_ ports make in onto CD
#1. Perhaps one way of doing this is to give each port a "pkg-priority" that
the release build scripts scan for. Anyways, that's just my $0.02, might be
$0.00 in this case.

-Craig


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Andy Farkas]

On Tue, 14 Jan 2003, Trish Lynch wrote:

> I just want to point out, POLA really only applies to -STABLE, and we're
> talking very specifically about -CURRENT.
>
> IN -CURRENT, substantial changes can be made with little warning, and only
> documentation sometimes (most of the time, people give a ***HEADS UP!***
> email on this list).
>
> However don;t assume because something is one way in the 4.x branch that
> it will be the same in 5.x. If this were the case, we'd have very little
> progress.
>
> -Trish
>

This makes sense, and I can live with it. I guess I'll have to 'forget'
how FreeBSD has always done things in the past and relearn...

Lots of things are very different - just this morning, I found out there
is no 'visual configure'. Only took an hour to figure out why GENERIC was
not finding the Adaptec 1542CF scsi card...

While I'm here, dc(4) is still telling me its ethernet address is
00:00:00:00:00:00 and that there is 'no carrier'. It works fine otherwise.

>
> --
> Trish Lynch  [EMAIL PROTECTED]
> Ecartis Core Team   [EMAIL PROTECTED]
> EFNet IRC Operator @ efnet.demon.co.ukAilleCat@EFNet
> Key fingerprint = C44E 8E63 6E3C 18BD 608F  E004 9DC7 C2E9 0E24 DFBD
>
>

--

 :{ [EMAIL PROTECTED]

Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Keith Jones]

[EMAIL PROTECTED] wrote:


In message 
<[EMAIL PROTECTED]
..com>, "local.freebsd.current" writes:

>That sounds like "it's time to ship so we're going to ship".

That's it.

>I'm not trying to get up anyone's nose here, but aren't there
>objective release criteria?

yes:  "No more delays" :-)

I think there's an old saying that can be applied here. "Projects are 
never finished, only released." So let's release it. As it's a point-oh 
release, it can be expected that a few errata may have to follow. That's 
the way of things.

Keith (currently tracking RELENG_5_0)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Nate Lawson]

On Tue, 14 Jan 2003, Trish Lynch wrote:
> On Tue, 14 Jan 2003, Andy Farkas wrote:
> > Perhaps I do things in a non-standard way, but its worked for the last 8
> > years from 2.x through to 4.7-stable.
> >
> > Firstly, I download 'floppies' and create the 2 boot disks, kern.flp and
> > mgsroot.flp. Then I download 'bin' (now called 'base'!?) to my fileserver.
> >
> > Next, I boot the box with 2 the new floppies, and tell sysinstall to use
> > 'FTP' to the fileserver URL (ftp://172.22.2.2) and install 'minimal' (in
> > other words, just install 'bin' (now called 'base'!? - anyone remember
> > the acronym POLA?)).
> 
> I just want to point out, POLA really only applies to -STABLE, and we're
> talking very specifically about -CURRENT.
> 
> IN -CURRENT, substantial changes can be made with little warning, and only
> documentation sometimes (most of the time, people give a ***HEADS UP!***
> email on this list).

POLA is overridden by "you can't have a combined rescue/install CD without
this change".

-Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Nate Lawson]

On Tue, 14 Jan 2003, Sheldon Hearn wrote:
> On (2003/01/14 10:22), local.freebsd.current wrote:
> 
> > >In the meantime we _really_ have to ship 5.0-RELEASE, we keep
> > >slipping it.
> > 
> > That sounds like "it's time to ship so we're going to ship".
> > 
> > I'm not trying to get up anyone's nose here, but aren't there
> > objective release criteria?
> 
> Yes.  One of the release criteria is that it come into existence. :-)

And to be fair, the problem is on sparc64 which is a tier 1 platform but
just barely so (pthread support was just finished a few days ago).  Nearly
all the freebsd installed base is x86 and to hold up the release for a bug
on a new platform's first release is ludicrous.

This is not an insult to sparc64.

-Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Trish Lynch]

On Tue, 14 Jan 2003, Andy Farkas wrote:

> >
> > Once again it's my pleasure to announce Release Cadidate 3 of
> > FreeBSD 5.0.
>
> Perhaps I do things in a non-standard way, but its worked for the last 8
> years from 2.x through to 4.7-stable.
>
> Firstly, I download 'floppies' and create the 2 boot disks, kern.flp and
> mgsroot.flp. Then I download 'bin' (now called 'base'!?) to my fileserver.
>
> Next, I boot the box with 2 the new floppies, and tell sysinstall to use
> 'FTP' to the fileserver URL (ftp://172.22.2.2) and install 'minimal' (in
> other words, just install 'bin' (now called 'base'!? - anyone remember
> the acronym POLA?)).

I just want to point out, POLA really only applies to -STABLE, and we're
talking very specifically about -CURRENT.

IN -CURRENT, substantial changes can be made with little warning, and only
documentation sometimes (most of the time, people give a ***HEADS UP!***
email on this list).

However don;t assume because something is one way in the 4.x branch that
it will be the same in 5.x. If this were the case, we'd have very little
progress.

-Trish


--
Trish Lynch[EMAIL PROTECTED]
Ecartis Core Team [EMAIL PROTECTED]
EFNet IRC Operator @ efnet.demon.co.uk  AilleCat@EFNet
Key fingerprint = C44E 8E63 6E3C 18BD 608F  E004 9DC7 C2E9 0E24 DFBD



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Harald Hanche-Olsen]

+ Sheldon Hearn <[EMAIL PROTECTED]>:

| On (2003/01/14 10:22), local.freebsd.current wrote:
| 
| > I'm not trying to get up anyone's nose here, but aren't there
| > objective release criteria?
| 
| Yes.  One of the release criteria is that it come into existence. :-)

Indeed.  There is an old story from the days of the big irons, when
IBM had an "objective" release criterion stating that no new release
of their OS would be shipped with more than 100 major bugs.

As a result, before each release, the engineers would have a big
meeting with the purpose of redefining major bugs as minor bugs.

I have no idea if the story is true, but there is a lesson in there
somewhere, so in a deeper sense it must be true.

- Harald

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[phk]

In message <[EMAIL PROTECTED]
.com>, "local.freebsd.current" writes:
>On Mon, 13 Jan 2003 11:46:43 -, [EMAIL PROTECTED] wrote:
>
>>In the meantime we _really_ have to ship 5.0-RELEASE, we keep
>>slipping it.
>
>That sounds like "it's time to ship so we're going to ship".

That's it.

>I'm not trying to get up anyone's nose here, but aren't there
>objective release criteria?

yes:  "No more delays" :-)

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Terry Lambert]

Sheldon Hearn wrote:
> On (2003/01/14 10:22), local.freebsd.current wrote:
> > >In the meantime we _really_ have to ship 5.0-RELEASE, we keep
> > >slipping it.
> >
> > That sounds like "it's time to ship so we're going to ship".
> >
> > I'm not trying to get up anyone's nose here, but aren't there
> > objective release criteria?
> 
> Yes.  One of the release criteria is that it come into existence. :-)

Eventualy, a software company must ship software.

The saying works for free software projects, too...

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Sheldon Hearn]

On (2003/01/14 10:22), local.freebsd.current wrote:

> >In the meantime we _really_ have to ship 5.0-RELEASE, we keep
> >slipping it.
> 
> That sounds like "it's time to ship so we're going to ship".
> 
> I'm not trying to get up anyone's nose here, but aren't there
> objective release criteria?

Yes.  One of the release criteria is that it come into existence. :-)

Ciao,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[local.freebsd.current]

On Mon, 13 Jan 2003 11:46:43 -, [EMAIL PROTECTED] wrote:

>In the meantime we _really_ have to ship 5.0-RELEASE, we keep
>slipping it.

That sounds like "it's time to ship so we're going to ship".

I'm not trying to get up anyone's nose here, but aren't there
objective release criteria?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Bruce A. Mah]

If memory serves me right, Andy Farkas wrote:

> > Once again it's my pleasure to announce Release Cadidate 3 of
> > FreeBSD 5.0.
> 
> Perhaps I do things in a non-standard way, but its worked for the last 8
> years from 2.x through to 4.7-stable.
> 
> Firstly, I download 'floppies' and create the 2 boot disks, kern.flp and
> mgsroot.flp. Then I download 'bin' (now called 'base'!?) to my fileserver.
> 
> Next, I boot the box with 2 the new floppies, and tell sysinstall to use
> 'FTP' to the fileserver URL (ftp://172.22.2.2) and install 'minimal' (in
> other words, just install 'bin' (now called 'base'!? - anyone remember
> the acronym POLA?)).

...which was documented (along with the reason why this change was
made) in the release notes.  :-)

Cheers,

Bruce.





msg50115/pgp0.pgp
Description: PGP signature

Re: FreeBSD 5.0 RC3 now available

[Andy Farkas]

>
> Le Monday 13 January 2003 18:22, Andy Farkas a écrit :

French is such a sexy language... :)

> indeed :
> (see
> 
>)
>

Again, the acronym POLA springs to mind

--

 :{ [EMAIL PROTECTED]

Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Thierry Herbelot]

Le Monday 13 January 2003 18:22, Andy Farkas a écrit :

[SNIP]
>
> # pkg_add cvsup-without-gui-16.1f.tgz
> /usr/libexec/ld-elf.so.1: Shared object "libssl.so.2" not found
> #
>
> Why does pkg_install now need libssl?

indeed : 
(see 
)

machine# ldd /usr/sbin/pkg_add
/usr/sbin/pkg_add:
libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28074000)
libmd.so.2 => /usr/lib/libmd.so.2 (0x2808)
libssl.so.2 => /usr/lib/libssl.so.2 (0x2808a000)
libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x280b9000)
libc.so.5 => /usr/lib/libc.so.5 (0x2817f000)
machine# uname -a
FreeBSD YYY 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Fri Jan 10 14:11:57 CET 2003 
XXX@YYY:/files3/obj/usr/src/sys/SMP  i386
machine#

whereas :
other_mach% ldd /usr/sbin/pkg_add
/usr/sbin/pkg_add:
libfetch.so.3 => /usr/lib/libfetch.so.3 (0x2806f000)
libmd.so.2 => /usr/lib/libmd.so.2 (0x28079000)
libc.so.4 => /usr/lib/libc.so.4 (0x28082000)
other_mach% uname -a
FreeBSD ZZZ 4.7-STABLE FreeBSD 4.7-STABLE #0: Sat Jan  4 12:51:32 CET 2003 
XXX@ZZZ:/usr/obj/usr/src/sys/ZZZ  i386
other_mach%

TfH

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Andy Farkas]

> >
> > Why does pkg_install now need libssl?
> >
>
> troutmask:kargl[251] ldd /usr/sbin/pkg_add
> /usr/sbin/pkg_add:
> libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28074000)
> libmd.so.2 => /usr/lib/libmd.so.2 (0x2808)
> libssl.so.2 => /usr/lib/libssl.so.2 (0x2808a000)
> libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x280b9000)
> libc.so.5 => /usr/lib/libc.so.5 (0x2817f000)
>
> I suspect your previous success in upgrading was accomplished
> because the version number of libssl didn't change.  Many of
> the shared libraries in 5.0 have version number bumps,
> including libssl.so.2.
>
> --
> Steve
>

FreeBSD 4.7-STABLE #1: Sat Jan 11 16:15:40 EST 2003:

# ldd /usr/sbin/pkg_add
/usr/sbin/pkg_add:
libfetch.so.3 => /usr/lib/libfetch.so.3 (0x2806f000)
libmd.so.2 => /usr/lib/libmd.so.2 (0x2807a000)
libc.so.4 => /usr/lib/libc.so.4 (0x28083000)


--

 :{ [EMAIL PROTECTED]

Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Steve Kargl]

On Tue, Jan 14, 2003 at 03:22:02AM +1000, Andy Farkas wrote:
> >
> > Once again it's my pleasure to announce Release Cadidate 3 of
> > FreeBSD 5.0.
> 
> 
> Sysinstall complains about not being able to find the 'crypto' stuff, but
> thats ok - its always done that.

Obviously, this isn't okay.

> 
> No go for 5.0-RC3:
> 
> # pkg_add cvsup-without-gui-16.1f.tgz
> /usr/libexec/ld-elf.so.1: Shared object "libssl.so.2" not found
> #
> 
> Why does pkg_install now need libssl?
> 

troutmask:kargl[251] ldd /usr/sbin/pkg_add
/usr/sbin/pkg_add:
libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28074000)
libmd.so.2 => /usr/lib/libmd.so.2 (0x2808)
libssl.so.2 => /usr/lib/libssl.so.2 (0x2808a000)
libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x280b9000)
libc.so.5 => /usr/lib/libc.so.5 (0x2817f000)

I suspect your previous success in upgrading was accomplished
because the version number of libssl didn't change.  Many of
the shared libraries in 5.0 have version number bumps,
including libssl.so.2.

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Andy Farkas]

>
> Once again it's my pleasure to announce Release Cadidate 3 of
> FreeBSD 5.0.

Perhaps I do things in a non-standard way, but its worked for the last 8
years from 2.x through to 4.7-stable.

Firstly, I download 'floppies' and create the 2 boot disks, kern.flp and
mgsroot.flp. Then I download 'bin' (now called 'base'!?) to my fileserver.

Next, I boot the box with 2 the new floppies, and tell sysinstall to use
'FTP' to the fileserver URL (ftp://172.22.2.2) and install 'minimal' (in
other words, just install 'bin' (now called 'base'!? - anyone remember
the acronym POLA?)).

Sysinstall complains about not being able to find the 'crypto' stuff, but
thats ok - its always done that.

Next, I reboot the newly installed 'base' system, login as root, then
'shutdown now' to return back to network-enabled single user mode.

Then I download 'cvsup-without-gui-16.1f.tgz' (into /root) and do a
'pkg_install cvsup-without-gui-16.1f.tgz' so I can cvsup the entire source
tree onto the new box and do the make build{world,kernel} thing on the new
box.

No go for 5.0-RC3:

# pkg_add cvsup-without-gui-16.1f.tgz
/usr/libexec/ld-elf.so.1: Shared object "libssl.so.2" not found
#

Why does pkg_install now need libssl?

--

 :{ [EMAIL PROTECTED]

Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[phk]

In message <[EMAIL PROTECTED]>, 
"Roderick van Domburg" writes:
>I would like to point to a currently unresolved issue that Thomas Moestl is
>helping me solve on freebsd-sparc@. It isn't listed on the Open Issues page,
>but I'd say it's something that needs to be resolved before the release is
>rolled.
>
>The thread is titled "panic: trap: fast data access mmu miss" and is about
>an error causing the sym SCSI controller to fail to mount root at best, and
>panic at worst.

Well, we all want our pet bug fixed before the release rolls, but at
some point we simply have to call it quits and ship the release.

I personally know this particular bug very well, I have rebooted the
AC/DC200 netra I had borrowed about 10 times more than I needed to
to get past this bug :-)

>The sym controller is listed as supported hardware, and used in several Sun
>boxes, so IMHO I'd say it warrants the attention.

All bugs warrent attention.  Some of them get it.

Don't worry, that bug, like all the others will get fixed and you will
be able to get an update for it in due time.

In the meantime we _really_ have to ship 5.0-RELEASE, we keep
slipping it.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Roderick van Domburg]

I would like to point to a currently unresolved issue that Thomas Moestl is
helping me solve on freebsd-sparc@. It isn't listed on the Open Issues page,
but I'd say it's something that needs to be resolved before the release is
rolled.

The thread is titled "panic: trap: fast data access mmu miss" and is about
an error causing the sym SCSI controller to fail to mount root at best, and
panic at worst.

The sym controller is listed as supported hardware, and used in several Sun
boxes, so IMHO I'd say it warrants the attention.

Regards,

Roderick



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD 5.0 RC3 now available

[Joe Laughlin]

(see below, my question got answered already)

Joe Laughlin wrote:

> Scott Long wrote:
>
> > All,
> >
> > Once again it's my pleasure to announce Release Cadidate 3 of
> > FreeBSD 5.0.  i386, pc98, alpha, ia64, and sparc64 releases are
> > available on most mirrors now.  Thanks to Marcel Moolenaar
> > for providing the ia64 bits, Takahashi Yoshihiro for proving the
> > pc98 bits, and David Obrien for the sparc64 bits.
> >
> > Please test this release as much as possible.  We are planning
> > on tagging the tree for the 5.0 release on January 15 and starting
> > the finals builds soon afterwards.  The TODO list is almost
> > polished off, and we are waiting for a couple of last minute
> > issued to be resolved.
> >
> > Again, I thank everyone for the effort that has gone into 5.0.
> >
> >
> > The Release Engineering Team
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
> >
>
> Is it possible to cvsup this release?


We don't tag the release candidates in CVS.  You can get close
by updating to the RELENG_5_0 branch.

Scott


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

FreeBSD 5.0 RC3 now available

[Scott Long]

All,

Once again it's my pleasure to announce Release Cadidate 3 of
FreeBSD 5.0.  i386, pc98, alpha, ia64, and sparc64 releases are
available on most mirrors now.  Thanks to Marcel Moolenaar
for providing the ia64 bits, Takahashi Yoshihiro for proving the
pc98 bits, and David Obrien for the sparc64 bits.

Please test this release as much as possible.  We are planning
on tagging the tree for the 5.0 release on January 15 and starting
the finals builds soon afterwards.  The TODO list is almost
polished off, and we are waiting for a couple of last minute
issued to be resolved.

Again, I thank everyone for the effort that has gone into 5.0.


The Release Engineering Team


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message