Yah, the paranoid part of my reptilian brain tells me not to issue a destroy
command on a resource I want to keep.
That said, it should be fine.
Sent from my iPhone
> On Sep 30, 2014, at 6:53 PM, Harry Putnam wrote:
>
> Tim Aslat writes:
>
>> Simplest option would be something like
>>
>
On 9/30/2014 8:31 PM, Tim Aslat wrote:
Harry Putnam wrote on 01/10/2014 09:52:
This is not so easy to find in google searches
How does one go about destroying all but a specific snapshot? The one
I want is somewhere in the middle timewise So not wanting to use
`destroy -r'.
This is in a .zfs/
Tim Aslat writes:
> Simplest option would be something like
>
> zfs list -t snapshot -o name -H -r filesystem/path > /tmp/snaplist.txt
>
> edit /tmp/snaplist.txt to remove the snapshot you want to keep
>
> for SNAP in `cat /tmp/snaplist.txt`
> do
> zfs destroy $SNAP
> done
>
> My syntax may
Harry Putnam wrote on 01/10/2014 09:52:
> This is not so easy to find in google searches
>
> How does one go about destroying all but a specific snapshot? The one
> I want is somewhere in the middle timewise So not wanting to use
> `destroy -r'.
>
> This is in a .zfs/snapshot/* where there are
This is not so easy to find in google searches
How does one go about destroying all but a specific snapshot? The one
I want is somewhere in the middle timewise So not wanting to use
`destroy -r'.
This is in a .zfs/snapshot/* where there are many auto snaps. So
looking for a way besides destroy
On Tue, 30 Sep 2014, Jim Klimov wrote:
Maybe a stupid question on my side (sorry i'm overwhelmed with
relocation and other life events), but how really is this bug
exploitable? Especially on Solaris and illumos systems with sh/ksh
by default and assumed no scripted CGI (hosts of native or jav
Centuries ago, Nostradamus predicted that Peter Tribble
would write on Mon, 29 Sep 2014 21:56:35 +0100:
>
> Actually building OpenJDK is pretty straightforward (once I had
> remembered that my first openjdk build box was corrupted). So
> I've dropped a copy of the 32-bit 8u20 build for illumos
We have tested all our systems, and the only ones that were vulnerable (in
cgi-bin) were ones that we had put in a bash script to test.
if you don't have any bash scripts in your cgi-bin, and your default system
shll is not bash (and on Solaris, and Ubuntu it isn't) then you pretty much
aren't exp
29 сентября 2014 г. 17:46:20 CEST, Jason Matthews пишет:
>paraphrasing "Joshua" from "WarGames," bash is a strange game where the
>only winning move is not to play.
>
>J.
>
>Sent from my iPhone
>
>> On Sep 29, 2014, at 2:43 AM, "Udo Grabowski (IMK)"
> wrote:
>>
>> As predicted, there's more bas
