> Emacs indents it nicely, and colorizes the
> keywords so that it stands out.
Indentification is not a problem, it work both
in geany and vim.
Probably I haven't made clear what I meant ;)
Take a look at this picture:
http://ompldr.org/vZG50bQ
The brackets in that specific section (asd) are
hi
> "vermaden" == vermaden writes:
>> Good to see you've finally been burned.
>> You'll never make that mistake again. :)
vermaden> I liked that syntax:
vermaden> ASD && {
vermaden> asd
vermaden> } || {
vermaden> bsd
vermaden> }
vermaden> mostly because of syntax highlighting, to be pre
> Good to see you've finally been burned.
> You'll never make that mistake again. :)
I liked that syntax:
ASD && {
asd
} || {
bsd
}
mostly because of syntax highlighting, to be precise highlighting
of the second bracket of a pair at editors, nor VIM neither GEANY
highlight if/then/elif/else/
> "vermaden" == vermaden writes:
vermaden> To the point, check these two code snippets, they should
vermaden> do EXACLY the same, logic is the same, the differece is
vermaden> only the syntax.
vermaden> snippet 1:
vermaden> [ ${MOUNT} -eq 0 ] && {
vermaden> zfs set mount
> And no difference on 8.3 :(
>
> Should there have been a "promote" in there somewhere? It looks like
> the boot env is still dependent on the very old zroot.
Hi,
I have just recreated from scratch Your zroot root
setup under VirtualBox and tested it deeply.
There was an interesting BUG in th
On 5/4/2012 5:10 PM, Randal L. Schwartz wrote:
>> "Randal" == Randal L Schwartz writes:
>
> Randal> Oh wait, it looks like zroot is still holding 1.04G of data... will
> Randal> that ever go away? Shouldn't all the data be in the /ROOT/xxx
> Randal> items?
>
> And worse, the things from t
> "Randal" == Randal L Schwartz writes:
Randal> This is FreeBSD 8.2.
And no difference on 8.3 :(
Should there have been a "promote" in there somewhere? It looks like
the boot env is still dependent on the very old zroot.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 5
> "Randal" == Randal L Schwartz writes:
Randal> Oh wait, it looks like zroot is still holding 1.04G of data... will
Randal> that ever go away? Shouldn't all the data be in the /ROOT/xxx
Randal> items?
And worse, the things from the readme don't work:
locohost# ./beadm create upgrade
cannot
> "Randal" == Randal L Schwartz writes:
> "vermaden" == vermaden writes:
vermaden> # fetch https://github.com/vermaden/beadm/blob/master/beadm
Randal> and after reboot, "zfs set mountpoint=none zroot" would also seem to
Randal> clean that up.
Oh wait, it looks like zroot is still hold
> "vermaden" == vermaden writes:
vermaden> # fetch https://github.com/vermaden/beadm/blob/master/beadm
Heh. That's HTML. I think you want
fetch https://raw.github.com/vermaden/beadm/master/beadm
vermaden> # chmod +x beadm
vermaden> # ./beadm list
vermaden> # ./beadm activate default
ver
> I have zfs-on-root using the classical documentation (everything under
> zpool, possibly with some sub-mounts, but I've left those out lately).
>
> Is there a way to transition my system to a form that beadm expects?
> I tried just running it, and it's upset that zpool/ROOT doesn't exist.
Hi,
> "vermaden" == vermaden writes:
vermaden> I have just created new HOWTO [1] on how to use Boot Environments on
vermaden> FreeBSD with new created utility *beadm* that I put on
vermaden> SourceForge [2].
I have zfs-on-root using the classical documentation (everything under
zpool, possibly
"Kalle Møller" :
> And I forgot
>
> If I do a create and destroy, I would assume my system
> was back to same state, but you keep the snapshot
> when I destroy the clone, dont know if its working as
> intended (better safe to keep it than sorry) or you just
> didn't think of it :)
I added automat
Hi,
> I just tested your tool the last few days and I must say I love
> it already. Though I can get one of the commands to work
> - might be me or the syntax
>
> beadm create [-e nonActiveBe | beName@snapshot] beName
>
> I read it as you can do the following
>
> beadm create beName@snapshot be
And I forgot
If I do a create and destroy, I would assume my system was back to
same state, but you keep the snapshot when I destroy the clone, dont
know if its working as intended (better safe to keep it than sorry) or
you just didn't think of it :)
http://pastebin.com/XdYZ2eGR
main# zfs list -
Hi vermaden
I just tested your tool the last few days and I must say I love it
already. Though I can get one of the commands to work - might be me or
the syntax
beadm create [-e nonActiveBe | beName@snapshot] beName
I read it as you can do the following
beadm create beName@snapshot beName
Is t
> Hi,
>
> do you know manageBE? Google for it, it is the first
> hit. This works for me like a charm since about a year.
>
> Bye,
> Alexander.
Hi,
yes I know and used manageBE for a while, I even mentioned it
in the HOWTO (quote below) but thought that making *beadm*
that is compatible with Ill
Hi,
I have just created new HOWTO [1] on how to use Boot Environments on
FreeBSD with new created utility *beadm* that I put on SourceForge [2].
Feel free to send Your ideas/critique about it.
[1] http://forums.freebsd.org/showthread.php?t=31662
[2] https://sourceforge.net/projects/beadm/
Regar
18 matches
Mail list logo
