> I am currently running FreeBSD 2.1.5, and would like to upgrade to 3.1
> without losing the tremendous amounts of data on my drive (backups are
> unfortunately not an option).
> I have seen several posts containing advice for accomplishing this task
> by altering sysinstall options, but this see
Sheldon Hearn wrote:
> > First, the setting in /etc/defaults/rc.conf should default to
> > off, as defaulting it to on violates POLA for the many many people who
> > haven't updated to 3.x from 2.2 yet.
>
> If we were integrating TCP Wrapper support into the base system for the
> very firs
ÓÒ , 30 ÉÀÎ 1999, Thomas Dean ÎÁÐÉÓÁÌ:
> I installed -current on a notebook with WINNT on the disk. The
> notebook has the ide disk limitation. So, I chopped the disk do get
> around it. Maybe I should buy a new notebook, but, this one works.
>
> Everything worked OK, except the boot manager.
On Wed, 30 Jun 1999 00:41:54 MST, Doug wrote:
> > This is a situation in which we can't make _everyone_ happy. For the
> > particular case you've provided, anyone who upgrades from 2.2 to 3.3
> > without reading the release notes will get what's coming to him.
>
> That's always true, but
On Wed, 30 Jun 1999 12:07:31 +0200, Sheldon Hearn wrote:
> Okay, so let's say we've got Joe Bloggs upgrading from 2.2.8 to 3.3 . He
> doesn't read the release notes, so he doesn't notice that inetd now
> wraps by default. The impact on him is:
Damnit! I forgot the most important part of my arg
On Wed, Jun 30, 1999 at 12:09:13PM +0200, Sheldon Hearn wrote:
>
>
> Damnit! I forgot the most important part of my argument -- people
> upgrading from 2.2.8 and don't read the release notes are going to have
> an /etc/rc.conf that sets inetd_flags="", hence their systems won't
> wrap!
Wouldn't
On Wed, 30 Jun 1999, Mike Nowlin wrote:
> > I am currently running FreeBSD 2.1.5, and would like to upgrade to 3.1
> > without losing the tremendous amounts of data on my drive (backups are
> > unfortunately not an option).
> > I have seen several posts containing advice for accomplishing this ta
This is a bit of a tangent from the original post, but when did the FreeBSD
kernel start supporting ELF natively (not talking about Linux emulation).
I made the mistake of attempting to run a 3.0 ELF world with a 2.2.5 kernel,
and it worked (mostly). I was unaware that anything that "old" support
"David E. Cross" wrote:
> This is a bit of a tangent from the original post, but when did the FreeBSD
> kernel start supporting ELF natively (not talking about Linux emulation).
> I made the mistake of attempting to run a 3.0 ELF world with a 2.2.5
> kernel, and it worked (mostly). I was unaware
Hello,
Here is a 'little' problem with vm_zone structure and field
'zname' in it.
zinit() function takes a pointer to name of zone and assigns it to
field zname. Since nfs module defines this name in the static module
memory pointer to name becomes invalid when module unl
So far I've run the latest buffer cache related fixes overnight on my
SMP test box without any problems.
Is anyone still experiencing buffer-cache related problems with CURRENT?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
wit
Sometime this weekend (July 3-5) I am planning to repository-copy
the soft-updates sources from their current location in
"src/contrib/sys/softupdates" to "src/sys/contrib/softupdates". All
of you using soft-updates will need to adjust your symbolic links in
"src/sys/ufs/ffs" after this change ha
Here is the 1-question FAQ:
Q. These symbolic links are a pain. Why don't you just edit
"src/sys/conf/files" appropriately?
A. The license terms for soft-updates do not permit that. See the
FreeBSD mailing list archives (the FreeBSD-current list, probably) for
more details.
On Wednesday, 30 June 1999 at 17:56:33 -0700, Matthew Dillon wrote:
> So far I've run the latest buffer cache related fixes overnight on my
> SMP test box without any problems.
>
> Is anyone still experiencing buffer-cache related problems with CURRENT?
My problems are gone. But I'm
George Michaelson wrote:
> Q. These symbolic links are a pain. Why don't you just edit
> "src/sys/conf/files" appropriately?
>
> A. The license terms for soft-updates do not permit that. See the
> FreeBSD mailing list archives (the FreeBSD-current list, probably) for
> more details.
cool. endit.
-George
--
George Michaelson | DSTC Pty Ltd
Email: [EMAIL PROTECTED]| University of Qld 4072
Phone: +61 7 3365 4310| Australia
Fax: +61 7 3365 4311| http://www.dstc.edu.au
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
The discussion(s) took place on [EMAIL PROTECTED]
The search string in the archives which works is:
kirk AND soft-update AND integration
note the soft-update, not softupdates.
note hackers. not current or stable. If you search anywhere else you
will get techno-related issues.
cheers
George Michaelson wrote:
>
> The discussion(s) took place on [EMAIL PROTECTED]
>
> The search string in the archives which works is:
>
> kirk AND soft-update AND integration
>
> note the soft-update, not softupdates.
Thanks! I couldn't remember for sure where the discussion had been.
18 matches
Mail list logo
