[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: News 2009-08-31

From: Arne Babenhauserheide
Subject: Re: News 2009-08-31
Date: Sun, 6 Sep 2009 15:20:04 +0200
User-agent: KMail/1.12.0 (Linux/2.6.30-hh2; KDE/4.3.1; x86_64; ; )

Am Sonntag, 6. September 2009 13:30:46 schrieb Sergiu Ivanov:
> I'm inclined to occupy a similar position.  However, I'd say that we
> somehow failed to discuss how exactly to make the code public :-( Of
> course, I can just create a master-unionmount branch in the unionfs
> repository, but I'm not sure antrik will approve of that.  OTOH, I
> could push my repository to something like github.

Can't you just push it to github first and then integrate it cleanly once we 
decided how to do that? 

> The usage of unionmount is simple:
>  $ settrans -a <node> unionfs -ut <translator>
> This will union-mount <translator> on <node>.


> Also (if required) I can provide a short explanation on some Hurd wiki
> page.  

That would be great! 

Ideally with some nifty examples what we can do with your translator :) 
(examples make docs far easier to understand). 

> This will take less time than writing full-fledge documentation
> (which means that I'll be able to do it much sooner) and should be
> enough for the majority of use-cases.

Maybe you can also use it as starting point.  Then you won't have to write 
everything over again, but can just reuse the short description to turn it 
into full fledged docs later on. 

> > $ ls blah.xml,,xml2dir

> One can actually do that now already.  Just give me the xml2dir
> translator :-) 


> > Will unionfs and nsmux be shipped with the Hurd LiveCDs/Qemu images,
> > so people can easily test them?
> I'm rather inclined to consider that shipping unionfs and nsmux with
> LiveCDs and QEMU images is not an imperative to encourage their
> testing.  Potential users could just as well download the code or
> clone the repositories locally.  Note that as opposed to some other
> translators (like Zheng's eth-multiplexer), both unionfs and nsmux
> were designed to be stand-alone, i.e. building unionfs and nsmux
> basically resumes to getting the code and running make.

Does that mean, I could just do 

        git clone <future unionfs repo> unionfs
        cd unionfs
        settrans -a shared unionfs -ut ftp / ftp.gnu.org

to union the files from ftp into my own dir? 

Where will changed files be written in that case? In the dir where they 

Best wishes, 

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]