[rear-users] [rear/rear] c5bb39: Allow running Rear from checkout.

Schlomo Schapiro schlomo at schapiro.org
Thu Jun 7 17:14:38 CEST 2012


OUTPUT=PLAIN_FILES

and name kernel and initrd in a consistent way:

kernel-$HOSTNAME-$DATE
initrd-$HOSTNAME-$DATE

or something like this.

On 7 June 2012 17:06, Dag Wieers <dag at wieers.com> wrote:

> On Thu, 7 Jun 2012, Jeroen Hoekx wrote:
>
> > On 7 June 2012 15:15, Schlomo Schapiro <schlomo at schapiro.org> wrote:
> >> On 7 June 2012 15:09, Jeroen Hoekx <jeroen.hoekx at hamok.be> wrote:
> >>> We currently default to OUTPUT=PXE for reasons I don't know. Any
> >>> reason to keep that? I think ISO is a better default.
> >>
> >> That is the only output that does not process the kernel and initrd any
> >> further. Hence it is the fastest and the one without external
> requirements
> >> like genisofs etc.
> >
> > Ok, that is a valid reason. We might want to add a new output method
> > that does not even create the pxe directory structure, but just writes
> > the kernel and ramdisk to the output location. Useful for qemu direct
> > booting.
>
> Yup, that would be a good trade-off.
>
>     OUTPUT=BARE
> or
>     OUTPUT=FILES
> or
>     OUTPUT=RAMDISK
> or
>     OUTPUT=INITRD
> or
>     OUTPUT=IMAGE
>
> Given that we already named OUTPUT=USB incorrectly, we might want to avoid
> it this time ;-) And do we really need to make a copy of the kernel ?
> Maybe we can symlink it instead ?
>
> Imagine that, much like OUTPUT=ISO we want to push this over e.g. http, I
> wonder how we could make it clear what kernel matches what initrd (if
> pushed to one central directory).
>
> Shall we make another issue out of this ?
>
> --
> -- dag wieers, dag at wieers.com, http://dag.wieers.com/
> -- dagit linux solutions, info at dagit.net, http://dagit.net/
>
> [Any errors in spelling, tact or fact are transmission errors]
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> rear-users mailing list
> rear-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pikachu.3ti.be/pipermail/rear-users/attachments/20120607/34e6affd/attachment.html 


More information about the rear-users mailing list