he new location. Where is it?
I think the freebsd-update build code might be homeless right now. I know I
have seen emails mentioning that it needs to land somewhere but I don't recall
any decision being reached.
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder
chine hangs
> in the loader.
Do you know what version of FreeBSD this system was originally running? It
may be that there are other oddities in the old partitioning which cause
problems for the newer loader code.
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Foun
ase engineering team.
Thanks to Peter Ankerstål, Allan Jude, Warner Losh, and Glen Barber for
their help in tracking down this problem.
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the
RELENG_9_0 |9.0-RELEASE |Normal |January 10, 2012 |January 31, 2013 |
+-+
- --
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the trul
Hi all,
I forgot to upload some of the amd64 RC3 bits to the mirrors earlier. They
should be in place now.
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
, 2010|July 31, 2012|
+-+
- --
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
-BEGIN PGP SIGNATURE
ounter any
problems -- I'm aware of two systems already which didn't manage to reboot after
installing 8.0-BETA1 kernels, so this is definitely a case of "here be dragons".
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap
ound from the shell", so until I've made
some improvements to that I don't really want to have any more mirrors than
necessary.
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
__
Aristedes Maniatis wrote:
On 09/01/2009, at 7:19 AM, Colin Percival wrote:
2. Assuming the first mirror still fails, use the -s option to pick a
different
mirror.
Where can we find a list of mirrors?
The list of is distributed via DNS SRV records:
# host -t srv _http
to pick a different
mirror.
3. Assuming that the second mirror works, send me an email telling me which
mirror failed and which one worked so that I can have the load balancing
adjusted.
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsna
Hi all,
FreeBSD Update is being slow right now due to server load issues.
It will improve.
Please be patient.
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
best solution here is to make FreeBSD Update realize that you're running
7.1-BETA:
# env UNAME_r=7.1-BETA freebsd-update [...]
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubsc
't agreed to anything yet.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
#x27;t include kernel debug bits
(at least, not on 6.3-RELEASE -- I think it does on 7.0-RC1).
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
's irritating to have to rebuild all of the installed ports, but (unless some
disaster strikes) this should be the last time it is needed until FreeBSD 8.x
happens ~2 years from now.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http
Max Laier wrote:
> On Tuesday 04 December 2007, Colin Percival wrote:
>> John Baldwin wrote:
>>> Considering that /etc/pf.conf is a file that users edit to configure
>>> pf(4), removing it out from under them is probably a very bad idea.
>>
>> The heurist
John Baldwin wrote:
> On Wednesday 28 November 2007 02:47:11 pm Colin Percival wrote:
>> Miroslav Lachman wrote:
>>> I am not 100% sure, maybe I overlook something in binary major version
>>> upgrade procedure, but after upgrade from 6.2 to 7.0-BETA3 my roots
>
fact that /etc/pf.conf disappeared is due to it being removed from
the release (it is now in /usr/share/examples/etc). The fact that /.cshrc
was upgraded in spite of having been locally modified is probably a bad
idea -- I'll change the default freebsd-update.conf to deal
daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html
for upgrading from 7.0-BETA1.5 or 7.0-BETA2 to 7.0-BETA3.
Colin Percival
FreeBSD Security Officer & FreeBSD Update wrangler
___
freebsd-stable@freebsd.org mailing list
http://lists.fre
ou can use to tell FreeBSD
Update not to touch some files (even if they haven't been modified locally).
FreeBSD Update will never produce mangled files as a result of applying a
bsdiff patch to the wrong file -- it checks file hashes before and after
applying patches and gracefully falls back to
Colin Percival wrote:
> A quick heads-up to everyone here using my new FreeBSD Update "upgrade"
> code: If you have performed a minor version upgrade (e.g., 6.2-RELEASE ->
> 6.3-BETA1 or 7.0-BETA1.5 -> 7.0-BETA2) please do not attempt to roll it
> back using "fr
Jan Henrik Sylvester wrote:
> Colin Percival wrote:
>> I believe that your system is now 6.3-BETA1 with a few shared libraries
>> from 6.2-RELEASE mixed in. If you can get a copy of /lib/*.so.* and
>> /usr/lib/*.so.* from a 6.3-BETA1 system and install those into place
>
currently broken and will make your system unbootable. I
should have this fixed within the next couple of days.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t
the FreeBSD Update code thinks that it has rolled back its updates, but
I might be able to find a way to do that for you -- is it a disaster if
this system ends up stuck at 6.3-BETA1?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ETA2 will be provided
> via the freebsd-stable list when available.
As promised, instructions on upgrading from FreeBSD 6.x to 7.0-BETA2 are
now available:
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html
Colin Percival
FreeBSD S
s
running FreeBSD 6.x to 6.3-BETA1 are now available:
http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html
Instructions on using FreeBSD Update to upgrade to 7.0-BETA2 should be
here within 24 hours.
Colin Percival
FreeBSD Securit
ither FreeBSD 6.3 or FreeBSD 7.0
> once
> those have been released (hopefully by the end of December). FreeBSD 6.3 will
> be supported until the end of 2009, while FreeBSD 7.0 will be supported until
> the end of 2008.
>
> Colin Percival
> FreeBSD Security Officer
_
27;s breakage by explicitly telling it to ignore these
options via --pax-option="delete=SCHILY.*" .
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Scott Long wrote:
> Colin Percival wrote:
>> I point releases have been obsoleted by errata notices. In the past when
>> X.Y.Z-RELEASE has happened, it has been because of critical bugs in the
>> X.Y-RELEASE which there wasn't any other mechanism to fix. Now that we
lease.
> PS. This having been said I know there are some kernel fixes that were
> candidates for errata against 6.2-RELEASE...I'm not sure what their
> current state is.
Don't ask me, I just approve the errata which you send to me. Which hasn't
been anything at all latel
Steven Hartland wrote:
> - Original Message - From: "Colin Percival" <[EMAIL PROTECTED]>
>>> tar -xvzf test.tar.gz
>>> tar: Ignoring unknown extended header keyword `SCHILY.dev'
>>> tar: Ignoring unknown extended header keyword `SCHILY.ino
e fairly typical symptoms of gnutar being broken. What
makes you think that the archive created by BSD tar was invalid?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GENERIC i386
>
> C3# freebsd-update fetch
> [...]
> No updates needed to update system to 6.2-RELEASE-p3.
This may look odd, but it's actually correct. The version number reported
by `uname` is the version number of the kernel, and the change from
6.2-RELEASE-p2 to 6.2-RELEA
o a buildworld.
There isn't any good solution here, yet. I might add support for the snapshot
ISOs at some point (at least for upgrading to/from them -- there will not be
security updates built for them).
Colin Percival
___
freebsd-stable@freebs
nloaded because the files have been modified locally:
> /etc/rc.d/jail
This is correct. The version you have here is not the version which
was distributed with the release -- it's the version in the latest
RELENG_6_2.
Colin Percival
t;
> Did something go wrong?
What does `sysctl kern.bootfile` say?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
s/conf/newvers.sh 1.69.2.13.2.5
> + src/UPDATING 1.416.2.29.2.6
> + src/sys/conf/newvers.sh 1.69.2.13.2.6
I guess I ought to update my CVS tree before using it to figure out the
RCS numbers
t/kernel,
the kernel will be replaced with a GENERIC (non-SMP) kernel.
I'm working on a patch for this and will be talking to re@ about having an
Errata Notice sent out about this.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists
ack run should be sufficient. Downgrading is easier than
upgrading, since you don't start running the new kernel until you reboot.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
directory instead.
> Suggestion for the developer: either permit directory creation in
> /usr/upgrade, or document that it's a no-no.
It will be documented. :-)
Thanks,
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://list
Philipp Wuensche wrote:
> Colin Percival wrote:
>> In the end we opted to reduce functionality (the jail startup process is
>> no longer logged to /var/log/console.log inside the jail)
>
> Thats a bummer, when Dirk showed me this problem the first time my ideas
> for fix
e, as well as
the release engineering team for being very patient with us and delaying the
upcoming release to give us time to fix this.
Sincerely,
Colin Percival
FreeBSD Security Officer
FreeBSD Security Advisories wrote:
> =
ing
upon your time zone.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
id-January. This does not give
> much time for people to migrate to the newest FreeBSD release. I think it
> would be fair if support is extended for a few more months especially since
> 6.2 is so late in coming.
Your opinion has been noted.
Colin Percival
___
e fine to have the files at least ready so that user can diff them
> and decide what to do.
I'm planning on adding automatic merging of configuration files soon.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Colin Percival wrote:
> Petr Holub wrote:
>>> I'm working on it.
>> If I install RC1 now, would it be possible to upgrade to RC2
>> and RELEASE, or is it not ready yet?
>
> My intention is that anyone running 6.1-RELEASE, 6.2-BETA*, or
> 6.2-RC* will be
release.
I haven't worked out all the details yet as to how this should
be done to minimize the chance that my script will accidentally
break things, but I'm not going to release anything until I think
that accidental breakage is very unlikely. :-)
Colin Percival
_
Hans F. Nordhaug wrote:
> At daemonology.net Colin Percival has some excellent instructions on
> how to do binary upgrades - he has even written a script to do a 6.0
> to 6.1 upgrade. My question is: Can I do a 5.3 to 6.1 upgrade using
> the instructions for "5.4 system to F
y personal website,
I haven't had any complaints.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EV1Servers has never been a major supporter of FreeBSD -- back when
they were RackShack, it took a petition of several hundred people
before they started offering FreeBSD at all.
I wonder if they'll start offering more recent FreeBSD releases next
month after FreeBSD 5.4 becomes uns
Christer Solskogen wrote:
> I've tried norway's mirror (my default), the danish, the swedish mirror
> and the mirror in holland. No change.
> Just to be sure I also deletet src/crypto before I tried the different
> mirrors.
Exactly what command did you run to try to compile
an updated dh.h yet. Try running cvsup again, maybe
from a different mirror.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i386 running FreeBSD 6.2-BETA1, FreeBSD Update should be able
to fetch the updates right now.
If it doesn't, something is broken, and I'd like to hear about it.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/
ystem to the latest updates on
RELENG_n_m.
> RELENG_n (RELENG_6 at the moment)
> Has somebody just said that RELENG_6 = STABLE?
Yes.
> I'm going to guess then that RELENG_7 is CURRENT.
> No, this doesn't make sense to me at
that these dates are
> no longer accurate.
>
> What is a valid ETA for starting the 6.2R releng process?
I'm not part of the release engineering team, but I'm not aware of anything
which they're waiting for before starting the freeze. I'd be surprised if
RELENG_
Peter Jeremy wrote:
> On Sun, 2006-Jul-09 00:42:31 -0700, Colin Percival wrote:
>> I have written an automatic script
>> for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades.
>
> That sounds useful. Are you intending to provide this for future
> FreeBSD minor-rev
he process is entirely secure.
The script can be obtained from
http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/
and the SHA256 hash of the download is
29075fc5711e0b20d879c69d12bbe5414c1c56d597c8116da7acc0d291116d2f .
Colin Percival
FreeBSD Security Officer
-BEGIN PGP SIGNATURE-
V
Ken Smith wrote:
> BitTorrent
> --
>
> 5.5-RELEASE ISOs are not available via BitTorrent at this time. They
> may be made available in the future on an on-demand basis.
Thanks to ps, torrents are now available for 5.5-RELEASE:
http://torrents.freebsd.org:8080/
se visit
http://people.freebsd.org/~cperciva/survey.html
and complete the survey below before May 31st, 2006.
Thanks,
Colin Percival
FreeBSD Security Officer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubs
If you absolutely must run FreeBSD 4.11, install the RELEASE and
then run FreeBSD Update.
Personally, since FreeBSD 4.11 will reach its EoL about 8 months
from now, and the 4.x->[56].x upgrade path is non-trivial, I
recommend installing FreeBSD 6.1 instead.
Colin Perci
default server for pre-1.0
versions of portsnap from the ports tree). Given that most systems running
portsnap are FreeBSD 6.0 or 6.1, this doesn't cause much differential
loading.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lis
uld be an .eu mirror?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ease images with the number set to "6.1-RC1"?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
developed ?
> This is maybe a stupid question, but i am only curious to know why ?
> Is there any special reason for this ?
Look at the date on Scott's email. :-)
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freeb
Pete French wrote:
>> If you look at top(1), which processors do you see actually running
>> processes?
>
> Errr, 0, 1, 2 and 3!
What do
# sysctl machdep.hlt_cpus
# sysctl machdep.logical_cpus_mask
# sysctl machdep.hyperthreading_allowed
sa
ts
correctly.)
If you look at top(1), which processors do you see actually running
processes?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
upported by the project"), I'll
get to those as soon as I have time. Sadly, I have a pesky thing
called "a full time job" and my FreeBSD time has been occupied with
portsnap lately.
Colin Percival
___
freebsd-stable@freebsd.org mai
Robert Watson wrote:
> On Tue, 8 Nov 2005, Colin Percival wrote:
>> I find this argument hard to accept. The vast majority of FreeBSD
>> users will never need the NFS_ROOT option, and many systems do not
>> even have the hardware for serial or parallel ports, yet those ar
ons should go into the GENERIC kernel, I think the
question we should be asking is not "how many people use this?", but
instead "would adding this option inconvenience more people than it would
help?".
Colin Percival
___
freebsd-stable
provides and supports), you might like to
try FreeBSD Update (http://www.daemonology.net/freebsd-update,
or security/freebsd-update in the ports tree).
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
var. If anything, these are vast overkill for most
systems; on /, for example, it is hard to imagine a situation where a normal
user would use more than 150MB of space unless they were doing something which
they shouldn't be doing.
Colin Percival
grep ^+' in
> /etc/periodic/security/security.functions.
Thanks for reporting this; I've changed the grep regex to '^[>+]' in order
to catch lines from both unified and non-unified diffs. This change isn't
going to be in 6.0-BETA3, but hopefully I can get it MFCed
at
> this time wouldn't be prudent?
If I was deploying a new server today, I'd install FreeBSD 5.4. If I were
planning on installing a new server next month, I'd install FreeBSD
6.0-BETA-whatever-number-we're-up-to-by-then.
Colin Percival
__
mpile much happier.
Yeah, it looks like the mirrors managed to update at exactly the wrong time
and got one patch but not the other. Fortunately, this doesn't happen very
often.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://
> Colin Percival wrote:
>> What version of /usr/src/sys/netinet/tcp_var.h do you have on that
>> system?
Oops. I meant to ask about src/sys/netinet/tcp_seq.h of course...
Colin Percival
___
freebsd-stable@freebsd.org ma
sys/netinet/tcp_input.c:2706: warning: nested extern
> declaration of `TSTMP_GT'
What version of /usr/src/sys/netinet/tcp_var.h do you have on that system?
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
Mipam wrote:
> Thanks for the kernel.
> What parameters did you change in your SMP kernel.
> Just curious, surely gonna try your kernel. :-)
I didn't change any parameters, I just used the SMP kernel configuration
from the source tree (i.e., GENERIC plus "options SMP
Billy Newsom wrote:
> Colin Percival wrote:
>> It sounds like the SMP kernel I provided for FreeBSD 5.3 was quite
>> popular [...]
>
> I'm curious how popular. Would you like to report some statistics here
> on the list? As in, how many SMP downloads did you get
ernel/SMP
# freebsd-update fetch
# freebsd-update install
# echo 'bootfile="SMP"' >> /boot/loader.conf
and reboot. You should now find that `uname -ri` outputs "5.4-SECURITY SMP".
Colin Percival
___
fre
e added it to the stable branches, but not to -current, since
hyper-threading is still enabled by default in HEAD.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
llowed on a stable branch).
> Is the goal to have a new major branch every 2 years?
Something like that, yes.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any m
FreeBSD 5.x is expected to be supported until late 2007 (FreeBSD 5.5 plus two
years), and FreeBSD 6.x will probably be supported until early 2009 (the last
FreeBSD 6.x release plus two years).
Colin Percival
___
freebsd-stable@freebsd.org mailin
Rob wrote:
> Some time ago, there was (or still is) a similar
> conflict with hostname resolution at bootup when
> using ntpd.
Yes, but not with named -- the problem was only when
using a dns cache from the ports tree, since those
are started later in the boot sequence.
Colin
g for something which should Never Happen. :-)
Colin Percival
PS. Bravo to Ian for tracking down the bug in NFS -- I spent a while looking
for this, but got hopelessly lost.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
t). Should I upgrade to -RC3? I'm
not sure if it's worth burning another few hundred megabytes of ftp mirror
bandwidth.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
ienced
FreeBSD users I decided that some anti-foot-shooting mechanisms were a
good idea.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
processors to the operating system, so there should be no problems.
For that matter, my understanding is that dual core opterons *are*
separate processors, connected only via their normal external
interface.
Colin Percival
___
freebsd-stable@freebsd.org
Yes, that's quite correct -- although I can't imagine how a bug which
caused / to be labelled as "noexec" managed to avoid causing major
problems until now.
I don't know anything about NFS, but hopefully someone on -stable
will be able to work out what's going on from
?
Is your /etc/hosts correct? I've seen this happen when the local
hostname (i.e., the output of `hostname`) cannot be resolved.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To u
makes one attempt to look up names in DNS and then
goes into an infinite loop.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
it up
initially (about 80 hours -- but 48 hours of that was over a weekend),
but aside from that I have no complaints.
Colin Percival
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
Brett Glass wrote:
Would anyone else besides me like to see a 5.3.1 minor release
sometime around, say, February?
No, but quite a few people would like to see a 5.4 minor release
sometime around, say, late February or early March.
Colin Percival
RITY SMP".
Note again that this does not apply to any FreeBSD releases other than
5.3.
Colin Percival
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
make it continue to fit for years into the future. (Just look at the
floppy disk situation.)
Much better just to accept that it doesn't fit onto a 3" CD-R and
move on. :-)
Colin Percival
___
[EMAIL PROTECTED] mailing list
http://lists.freebs
At 20:59 19/04/2004, Doug Lee wrote:
>CVS is being updated but FreeBSD still uses v1.11.5. ...
>Any plans to update CVS in the base system?
CVS 1.11.15 was imported into -current four days ago. I
would assume that it will be merged onto -stable at some
point after 4.10-RELEASE.
#x27;s makefs (ports/sysutils/makefs)
saves about 23k on the mfsroot floppy.
Colin Percival
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ytab?rev=1.17.2.4
Colin Percival
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
time when STABLE absolutely needed to be stable, but I'm not
sure that's necessarily the case any more; now that we have all the
release/security branches, I think it's safe to say that most systems which
need absolute stability aren't going to be running STABLE.
Colin Perc
ould be a Good Thing, but nobody has actually
gotten around to doing it yet.
Colin Percival
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
99 matches
Mail list logo
