8.0-RELEASE completed...
Ken Smith
Just a quick note in case there are people here who aren't subscribed to
the freebsd-announce@ mailing list.
We have completed the 8.0-RELEASE cycle. Details about the release are
available from the main web site, in particular the announcement itself
is available here:
http://www.freebsd.org/releases/8.0R/announce.html
Thanks for all the help with testing during the release process, as well
as your continued support of FreeBSD.
--
Ken Smith
- From there to here, from here to | kens...@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
Kevin Oberman
> Date: Thu, 26 Nov 2009 20:06:23 -0500
> Sender: owner-free...@freebsd.org
>
>
> Just a quick note in case there are people here who aren't subscribed to
> the freebsd-announce@ mailing list.
>
> We have completed the 8.0-RELEASE cycle. Details about the release are
> available from the main web site, in particular the announcement itself
> is available here:
>
> http://www.freebsd.org/releases/8.0R/announce.html
>
> Thanks for all the help with testing during the release process, as well
> as your continued support of FreeBSD.
And congratulations and thanks to the entire FreeBSD release engineering
team and the contributors. It's a .0 release, but my experience with it
through the release cycle has been excellent. I especially appreciate the
new USB stack which has fixed all sorts of annoying issues (and a couple
that were a lot more than annoying) in the old stack.
Great job!
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: obe...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Gary Kline
Some questions that I hope are not too far OT::
On Thu, Nov 26, 2009 at 07:06:01PM -0800, Kevin Oberman wrote:
> > From: Ken Smith <kens...@cse.buffalo.edu>
> > Date: Thu, 26 Nov 2009 20:06:23 -0500
> > Sender: owner-free...@freebsd.org
> >
> >
> > Just a quick note in case there are people here who aren't subscribed to
> > the freebsd-announce@ mailing list.
> >
> > We have completed the 8.0-RELEASE cycle. Details about the release are
> > available from the main web site, in particular the announcement itself
> > is available here:
> >
> > http://www.freebsd.org/releases/8.0R/announce.html
> >
> > Thanks for all the help with testing during the release process, as well
> > as your continued support of FreeBSD.
>
> And congratulations and thanks to the entire FreeBSD release engineering
> team and the contributors. It's a .0 release, but my experience with it
> through the release cycle has been excellent. I especially appreciate the
> new USB stack which has fixed all sorts of annoying issues (and a couple
> that were a lot more than annoying) in the old stack.
>
/*
I echo Kevin's congrats, of course; it ain't getting any
*easier*, certainly.
*/
Altho I am still some time from having my migration from the
1998 Kayak -> 2009 Dell done and working, will it be possible
to upgrade my 32bit 7.2-R, p4 to a 64bit 8.0? Even tho i am
documenting __everything__, it isn't something I would care to
do more than necessary. In going from 32bits to 64, does the
filesystem change? My hunch is that it does, but thought I
would get that clear as a first step. My Intell duo-core is
very fast; would moving to the 64-bit system be a net gain or
loss [in performance].
Eventuaaly, I *will* have 64-bit micros, killers or
otherwise, :-) ...
thanks in advance.
> Great job!
> --
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: obe...@es.net Phone: +1 510 486-8634
> Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php
Roland Smith
>
> Altho I am still some time from having my migration from the
> 1998 Kayak -> 2009 Dell done and working, will it be possible
> to upgrade my 32bit 7.2-R, p4 to a 64bit 8.0?
It is possible, but not easy. Upgrading from 7.x to 8.0 on the same
architecture is not that hard IMHO. Upgrading from i386 to amd64 on the same
release is doable but tricky; you need a spare root partition to install the
amd64 binaries. Combining these two sounds like a big can of worms to me. My
advice would be _not_ to do it.
It would be far easier to just install 8.0 on the new machine and migrate your
data and configuration files. You are going to have to build your ports from
scratch anyway, because you're switching to another architecture and another
major release.
As far as I know, the on-disk filesystem format hasn't changed. (unless your
old machine is still running UFS1. The default now is UFS2)
There are a couple of differences between 7.x and 8.0;
* The USB stack has been rewritten. I've had to change the following in
/etc/devfs.rules: replace "add path 'usb*' mode 0660 group usb" with "add
path 'usb/*' mode 0660 group usb"
* The name of the tty devices has changed in /etc/ttys; ttydN -> ttyuN
(impacts /etc/ttys)
* There have been a lot of changes in the kernel configuration. If you want a
custom kernel, start anew from the 8.0 GENERIC kernel so you don't miss
anything.
* A lot of changes as well in /etc/src.conf (the file that defines which parts
of the system are built from source)
* Network cards show up in dmesg and ifconfig, but not as devices in /dev (but
that could be a configuration error on my part.)
All my configuration files are kept in a directory that is under revision
control by git(1), so I could show you exactly what changes I've made.
> would get that clear as a first step. My Intell duo-core is
> very fast; would moving to the 64-bit system be a net gain or
> loss [in performance].
There is no clear gain or loss answer to that one. It depends on the workload
you are running. On the plus size, amd64 has a lot more general registers
available in the CPU than i386. On the other hand, the binaries are
bigger.
Since you're switching to another CPU, things like cache size will have a
major inpact. WRT single versus multi cores, my impression has been that the
individual cores in a multi-core intel CPU are somewhat slower that the core
of a similarly clocked single-core CPU. (based on some informal testing I've
done with povray). If your workloads are capable of running on multiple cores
(e.g. make jobs, different programs running concurrently) there will be a
significant speed increase.
You only _need_ amd64 if you are running out of address space on the i386
architecture. Having said that, I've been running amd64 on my desktop since
5.3-RELEASE more or less because I can, and it has worked fine ever since. Be
aware though that there are a few (most binary) ports that do not work on
amd64. You can see that in the port Makefiles by looking for things like
NOT_FOR_ARCHS and ONLY_FOR_ARCHS.
HTH,
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
Randy Bush
boring. this is a feature. thanks all.
randy
Robert Watson
On Thu, 26 Nov 2009, Ken Smith wrote:
> Just a quick note in case there are people here who aren't subscribed to the
> freebsd-announce@ mailing list.
>
> We have completed the 8.0-RELEASE cycle. Details about the release are
> available from the main web site, in particular the announcement itself is
> available here:
>
> http://www.freebsd.org/releases/8.0R/announce.html
>
> Thanks for all the help with testing during the release process, as well as
> your continued support of FreeBSD.
For those wanting to do advocacy work for the release, in addition to the
release announcement and highly detail release notes, there's also a press
release:
http://www.freebsd.org/releases/8.0R/pressrelease.html
It is a bit more verbose and salesy than the announcement, but a lot shorter
than the release notes.
Robert N M Watson
Computer Laboratory
University of Cambridge
Kurt Jaeger
> Just a quick note in case there are people here who aren't subscribed to
> the freebsd-announce@ mailing list.
>
> We have completed the 8.0-RELEASE cycle. Details about the release are
> available from the main web site, in particular the announcement itself
> is available here:
>
> http://www.freebsd.org/releases/8.0R/announce.html
Thanks!
One question:
http://www.freebsd.org/releases/8.0R/relnotes-detailed.html
says:
----------
The route(8) utility now supports show, weights, and sticky commands.
For more details, see the route(8) manual page.
----------
I do not have those things in my man page or route(8) command ?
--
p...@opsec.eu +49 171 3101372 11 years to go !
Dag-Erling Smørgrav
> It is possible, but not easy. Upgrading from 7.x to 8.0 on the same
> architecture is not that hard IMHO. Upgrading from i386 to amd64 on the same
> release is doable but tricky; you need a spare root partition to install the
> amd64 binaries.
Not at all, just make a backup of /etc, extract the amd64 dist on top of
your existing system, then restore whichever parts of /etc got clobbered.
DES
--
Dag-Erling Smørgrav - d...@des.no
Gary Kline
> Roland Smith <rsm...@xs4all.nl> writes:
> > It is possible, but not easy. Upgrading from 7.x to 8.0 on the same
> > architecture is not that hard IMHO. Upgrading from i386 to amd64 on the same
> > release is doable but tricky; you need a spare root partition to install the
> > amd64 binaries.
>
> Not at all, just make a backup of /etc, extract the amd64 dist on top of
> your existing system, then restore whichever parts of /etc got clobbered.
>
> DES
> --
Thanks, gentlemen. Mostly, my post was just a pondering;
wondering if it might be better to re-do stuff now, But then
my new server still isn't finished and probably won't be until
next week. So best to stick with what I'm familar with.
gary
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php
_______________________________________________
Bruce Cran
Gary Kline <kl...@thought.org> wrote:
> { One far, far OT question here: who can explain what dovecot
> is/does? why it even exists? I'm familiar with MTA's, like
> sendmail; likewise with MUA's, like evo, kmail, and mutt.
> It's time to learn another level of complexity, evidently....}
Dovecot is an IMAP/POP3 server - sendmail lets you send mail, dovecot
lets you fetch it from a remote server.
--
Bruce Cran
Gary Kline
> On Thu, Nov 26, 2009 at 09:57:58PM -0800, Gary Kline wrote:
> >
> > Altho I am still some time from having my migration from the
> > 1998 Kayak -> 2009 Dell done and working, will it be possible
> > to upgrade my 32bit 7.2-R, p4 to a 64bit 8.0?
>
> architecture is not that hard IMHO. Upgrading from i386 to amd64 on the same
> release is doable but tricky; you need a spare root partition to install the
> advice would be _not_ to do it.
Yes, and for now I'll stick with simply going from v7 to
v8--in the 32-bit release... Lots of stuff to get-working
PLUS the server migration from ancient to new. ---eventually
i'll take a _long_ breath.
>
> It would be far easier to just install 8.0 on the new machine and migrate your
> data and configuration files. You are going to have to build your ports from
> scratch anyway, because you're switching to another architecture and another
> major release.
>
> As far as I know, the on-disk filesystem format hasn't changed. (unless your
> old machine is still running UFS1. The default now is UFS2)
Pretty sure I'm using the default. UFS2.
>
> There are a couple of differences between 7.x and 8.0;
> * The USB stack has been rewritten. I've had to change the following in
> /etc/devfs.rules: replace "add path 'usb*' mode 0660 group usb" with "add
> path 'usb/*' mode 0660 group usb"
Roland, would you please update your webpage? No hurry, but
by sometime early in '10. I do rely on others' datapoints.
But now tat I'm having to do some real work in this migration,
it's time to learn about some things I've let slide.
{ One far, far OT question here: who can explain what dovecot
is/does? why it even exists? I'm familiar with MTA's, like
sendmail; likewise with MUA's, like evo, kmail, and mutt.
It's time to learn another level of complexity, evidently....}
> * The name of the tty devices has changed in /etc/ttys; ttydN -> ttyuN
> (impacts /etc/ttys)
What impact is this likely to have on my server? The more
ttys we've got, the better, for a term/xterm/<cmdline> like me.
But because I've only used my Kayak as a server, I don't think
I touched much in tty-land. *But* I probably will. I can't see
just letting a heavy-duty dual-core suck up so many kilowats.
--Okay, I'll get off the soapbox now:)
> * There have been a lot of changes in the kernel configuration. If you want a
> custom kernel, start anew from the 8.0 GENERIC kernel so you don't miss
> anything.
Could somebody who's running a 32biter send a GENERIC from
8.0 so I can diff?
> * A lot of changes as well in /etc/src.conf (the file that defines which parts
> of the system are built from source)
> * Network cards show up in dmesg and ifconfig, but not as devices in /dev (but
> that could be a configuration error on my part.)
>
Sorry, you left me in the dust with "/etc.src.conf". I though
the entire system was built from source. Examples, please?
>
> Since you're switching to another CPU, things like cache size will have a
> major inpact. WRT single versus multi cores, my impression has been that the
> individual cores in a multi-core intel CPU are somewhat slower that the core
> of a similarly clocked single-core CPU. (based on some informal testing I've
> done with povray). If your workloads are capable of running on multiple cores
> (e.g. make jobs, different programs running concurrently) there will be a
> significant speed increase.
>
> You only _need_ amd64 if you are running out of address space on the i386
> architecture. Having said that, I've been running amd64 on my desktop since
> 5.3-RELEASE more or less because I can, and it has worked fine ever since. Be
> aware though that there are a few (most binary) ports that do not work on
> amd64. You can see that in the port Makefiles by looking for things like
> NOT_FOR_ARCHS and ONLY_FOR_ARCHS.
For whatever I do, 32 bits has been fine. I spend virtually
my entire bg working in the 64bit world, which used to be:
supercomputer-level processing.
>
> HTH,
Yup; this has been a serious help; you it will robably keep me
from stepping in it [[ a mine-field ]] when I move to 8.0 or
8.1 next year.
gary
>
> Roland
> --
> R.F.Smith http://www.xs4all.nl/~rsmith/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php
_______________________________________________
Giorgos Keramidas
>> * There have been a lot of changes in the kernel configuration. If
>> you want a custom kernel, start anew from the 8.0 GENERIC kernel so
>> you don't miss anything.
>
> Could somebody who's running a 32biter send a GENERIC from 8.0 so I
> can diff?
You can always grab the latest version of GENERIC for 8.X from:
http://svn.freebsd.org/viewvc/base/stable/8/sys/i386/conf/GENERIC
Just follow the "view" link of the latest revision.
Gary Kline
> On Sun, 29 Nov 2009 11:30:18 -0800
> Gary Kline <kl...@thought.org> wrote:
>
> > is/does? why it even exists? I'm familiar with MTA's, like
> > sendmail; likewise with MUA's, like evo, kmail, and mutt.
> > It's time to learn another level of complexity, evidently....}
>
> lets you fetch it from a remote server.
>
Well, I gotta fess up and admit that I've been living in the
past century for a long time! Weren't these IMAP/POP servers
originally for people to use their FreeBSD computers at home
from their university [or work] accounts? I had an IP from
work for several years, then set up sendmail to deliver mail
to my individual machines. i really have let things slide
since I went back to school; now it's time to get back on
track. For the past two years I've relied on one guy ... and
until I am back up to par, if he should get hit by a bus, I'm
up the creek. --Thus all these recent questions... .
> --
> Bruce Cran
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php
_______________________________________________
Miroslav Lachman
> Hi!
>
>> Just a quick note in case there are people here who aren't subscribed to
>> the freebsd-announce@ mailing list.
>>
>> We have completed the 8.0-RELEASE cycle. Details about the release are
>> available from the main web site, in particular the announcement itself
>> is available here:
>>
>> http://www.freebsd.org/releases/8.0R/announce.html
>
> Thanks!
>
> One question:
>
> http://www.freebsd.org/releases/8.0R/relnotes-detailed.html
>
> says:
>
> ----------
> The route(8) utility now supports show, weights, and sticky commands.
> For more details, see the route(8) manual page.
> ----------
>
> I do not have those things in my man page or route(8) command ?
I have one more question about relnotes-detailed.html
-----------
"Specific CPU binding by using cpuset(1) has been implemented. Note that
the current implementation allows the superuser inside of the jail to
change the CPU bindings specified."
-----------
Is it true? I don't have 8.0-RELEASE installed, but I think it was fixed
in 7-STABLE right after the 7.2-RELEASE
PR kern/134050 was reported by me
Miroslav Lachman
John Baldwin
I believe it is fixed in 8.0.
--
John Baldwin
pluknet
This is what is in BUGS section of cpuset(1) manpage in 7.2-RELEASE,
and not (fixed) in 8.0-RELEASE.
It looks like it was leaved here by accident, since it was fixed on
April in HEAD, MFC'ed on August to 7 after 7.2.
The practice was to mention such misdescription on Errata page (e.g.
see errata for 7.1).
--
wbr,
pluknet