>
> > The problem is how do we keep up with -STABLE
> > afterwards? Using CVSup, out changes will get clobbered
> every time. Is
> > there a facility where you can keep up with the source but let local
> > modifications through?
>
> Yup, just use cvsup to maintain an up to date copy of the rep
Aaron Smith <[EMAIL PROTECTED]> writes:
> i've done some searching and i've seen discussion of userland fs
> before. has there been any progress in the user-space filesystem area? i
> have a nifty project and i would like to avoid using loopback NFS; have we
> got anything akin to linux's userfs y
Brooks Davis <[EMAIL PROTECTED]> writes:
> Yup, just use cvsup to maintain an up to date copy of the repository
> localy and then cvs checkout your source tree from there. This allows
> you to keep in sync and keep local modifications in your tree. Updates
> take longer and I recommend updating
On Mar 3, 11:47am, Assar Westerlund wrote:
} Subject: Re: Keeping using locally modified source
} There's even a hack in FreeBSD cvs and cvsup to allow you to keep a
} `local' branch that's not clobbered by cvsup, namely the environment
} variable CVS_LOCAL_BRANCH_NUM.
I thought about using this
Don Lewis <[EMAIL PROTECTED]> writes:
> I thought about using this, but it doesn't appear to be easy to track
> changes to an official branch. I was looking for something that would
> be as easy tracking changes made by infrequent imports on the vendor
> branch.
No, it's just a hack. Having hie
Hi Sergey!
I think you wrote on Fr , 03 Mär 2000:
> Christian Gusenbauer wrote:
> >
> > Hi David!
> >
> > I'm sorry for you, but FBSDBOOT will never support ELF binaries :-(! As
> > developer of this utility I had a discussion about supporting ELF when ELF was
> > introduced into FreeBSD. The r
"Koster, K.J." wrote:
>
> Oh, those Americans. :-)
>
> Let's see: $1 per gallon in the US. $1.2 per litre in the Netherlands, times
> 4.5 (or thereabouts) is $5.4 per gallon in the Netherlands.
>
> Everyone in the Netherlands drives cars; everyone thinks gas is expensive.
> This means that the
For anyone interested in reading about netgraph(4), including
technical information about developing your own node types, etc.,
here is an article that I wrote for this month's Daemon News
'blueprints' column..
http://www.daemonnews.org/23/netgraph.html
-Archie
___
Upon reading of Microsoft's fabulous innovations in the filesystem arena,
I started playing with some ideas of my own (not to be confused with
ORIGINAL ideas)
Can someone tell me why copy-on-write filesystems would be bad?
Imagine: cp file file2, file and file2 reference the same exact blocks,
On Fri, 3 Mar 2000, Michael Bacarella wrote:
> Can someone tell me why copy-on-write filesystems would be bad?
It's a good idea. Peter Braam and I have written a device (called memdev)
for linux (sorry!) that implements a virtual-memory-backed copy-on-write
block device (like the loopback device
On Fri, 3 Mar 2000, Michael Bacarella wrote:
>
>
> Upon reading of Microsoft's fabulous innovations in the filesystem arena,
> I started playing with some ideas of my own (not to be confused with
> ORIGINAL ideas)
>
> Can someone tell me why copy-on-write filesystems would be bad?
>
> Imagine
:It's a good idea. Peter Braam and I have written a device (called memdev)
:for linux (sorry!) that implements a virtual-memory-backed copy-on-write
:block device (like the loopback device, but uses anon vm pages for store).
:
:It's pretty interesting. It's quite fast, and copy-on-write does seem
On Fri, 3 Mar 2000, Michael Bacarella wrote:
>
>
> Upon reading of Microsoft's fabulous innovations in the filesystem arena,
> I started playing with some ideas of my own (not to be confused with
> ORIGINAL ideas)
>
> Can someone tell me why copy-on-write filesystems would be bad?
>
> Imagin
On Fri, 3 Mar 2000, Michael Bacarella wrote:
>
>
> Upon reading of Microsoft's fabulous innovations in the filesystem arena,
> I started playing with some ideas of my own (not to be confused with
> ORIGINAL ideas)
>
> Can someone tell me why copy-on-write filesystems would be bad?
It wouldn't
David Scheidt wrote:
>
> On Fri, 3 Mar 2000, Michael Bacarella wrote:
>
> >
> >
> > Upon reading of Microsoft's fabulous innovations in the filesystem arena,
> > I started playing with some ideas of my own (not to be confused with
> > ORIGINAL ideas)
> >
> > Can someone tell me why copy-on-write
> Sounds very intriquing. The biggest problem I see, right away is fitting
> it's use into a UNIX environment, were, file copies are made with the
> write system call, making it impossible to implement for the general case.
> You could certainly rewrite the "cp" command and that would get a ma
> > It wouldn't be. This is how NetApp do their .snapshot direcotries. I think
> > they have some white papers on it on their website. It's very handy.
>
> Kirk McKusick is implementing a Copy-on write functionality
> for UFS. It is used in conjunction with Soft updates to produce
> snapshots
> Christian Gusenbauer wrote:
> >
> > Hi David!
> >
> > I'm sorry for you, but FBSDBOOT will never support ELF binaries :-(! As
> > developer of this utility I had a discussion about supporting ELF when ELF was
> > introduced into FreeBSD. The reason, why ELF support was not integrated is, that
Archie Cobbs wrote:
>
> For anyone interested in reading about netgraph(4), including
> technical information about developing your own node types, etc.,
> here is an article that I wrote for this month's Daemon News
> 'blueprints' column..
>
> http://www.daemonnews.org/23/netgraph.html
A
On Fri, 3 Mar 2000, Michael Bacarella wrote:
>
> > > It wouldn't be. This is how NetApp do their .snapshot direcotries. I think
> > > they have some white papers on it on their website. It's very handy.
> >
> > Kirk McKusick is implementing a Copy-on write functionality
> > for UFS. It is us
On Fri, Mar 03, 2000 at 01:39:54PM -0800, Julian Elischer wrote:
> David Scheidt wrote:
> >
> > On Fri, 3 Mar 2000, Michael Bacarella wrote:
> >
> > > Upon reading of Microsoft's fabulous innovations in the filesystem arena,
> > > I started playing with some ideas of my own (not to be confused w
> > No one will appreciate that happening to their "permanent" data,
> > especially if the OS decides that the best way to get out of debt is by
> > deleting a file :)
>
> Actually, since this is copy-on-write, you do not need the block, until
> you write. If you need to make a copy, it will be
On Fri, Mar 03, 2000 at 09:56:08AM -0700, Wes Peters wrote:
> "Koster, K.J." wrote:
>
> > Oh, those Americans. :-)
> > Let's see: $1 per gallon in the US. $1.2 per litre in the Netherlands,
> > times 4.5 (or thereabouts) is $5.4 per gallon in the Netherlands.
> > Everyone in the Netherland
On Mon, 21 Feb 2000 10:05:55 +0800, Peter Wemm wrote:
> I would love to make a port of this, for reasons that become obvious
> once you see the page. (Think of all the mailing list archives and
> mirrors)
>
> http://www.totse.com/DeCSS/
Screw the cascading style sheets business, I wanna distr
On Saturday, 4 March 2000 at 10:12:13 +1030, Mark Newton wrote:
> On Fri, Mar 03, 2000 at 09:56:08AM -0700, Wes Peters wrote:
>
>> "Koster, K.J." wrote:
>>
>>> Oh, those Americans. :-)
>>> Let's see: $1 per gallon in the US. $1.2 per litre in the Netherlands,
>>> times 4.5 (or thereabouts) is $5.
On 2000-03-03 09:24 -0800, Archie Cobbs <[EMAIL PROTECTED]> wrote:
> For anyone interested in reading about netgraph(4), including
> technical information about developing your own node types, etc.,
> here is an article that I wrote for this month's Daemon News
> 'blueprints' column..
>
> http:
:> > I think. One problem with "Copy-on-write, when applied to
:> > file copies is that you need to assign the blocks up front, even if you
:> > don't copy the data, as otherwise you could run out of space
:> > when the copy is actually needed.
:>
:> That's the only real drawback I've considered
On Fri, 3 Mar 2000, Matthew Dillon wrote:
> :> > I think. One problem with "Copy-on-write, when applied to
> :> > file copies is that you need to assign the blocks up front, even if you
> :> > don't copy the data, as otherwise you could run out of space
> :> > when the copy is actually needed.
>
:Swap? I thought we were talking about a copy-on-write filesystem
:i.e. disk block, not memory, or did I really miss something
:
:Brian Beattie| The only problem with
Where are you copy-on-writing to? Unbacked memory? No way that
would ever work, at least not for any reason
Mark Newton wrote:
> > Fourth, I'm paying $1.48/gal right now, and I want the price to go
> > DOWN, not UP.
>
> I'm paying A$0.83c/L right now, which is roughly A$3.73/gal, which is
> roughly US$2.76. That means the US price of petroleum can rise by almost
> 100% and people still still drive
In reply:
> Imagine: cp file file2, file and file2 reference the same exact blocks,
> but modified chunks of file2 would be given their own private blocks.
This is not a microsoft innovation, actually, I believe it was a VMS
innovation. It's called a generational filesystem. the original is
sto
In reply:
> On Fri, 3 Mar 2000, Michael Bacarella wrote:
>
> > Can someone tell me why copy-on-write filesystems would be bad?
>
> It's a good idea. Peter Braam and I have written a device (called memdev)
> for linux (sorry!) that implements a virtual-memory-backed copy-on-write
> block device (
On Sat, 4 Mar 2000, Sheldon Hearn wrote:
> > http://www.totse.com/DeCSS/
>
> Screw the cascading style sheets business, I wanna distribute the real
> thing. I'd like to see these wankers try to sue me. Especially if it
> means a free plane trip to the States. :-)
You know, I half want to add
On Wed, 1 Mar 2000, Marc Frajola wrote:
> > What are you using for your command lines? You have to target the
> > disklabel specifically at slice 1 on the disk otherwise disklabel will
> > think you're trying to overwrite the slice table and get mad.
>
> Here's what I did:
>
> fdisk
On Thu, 2 Mar 2000, Warren Welch wrote:
> Is it possible to create FreeBSD partitions from the command line?
> I'd really like to be able to script creating a FreeBSD partitions, so
> that I could create /, /var, /usr, etc. without having to edit the
> disklabel manually.
See src/release/picob
35 matches
Mail list logo
