From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: testing 2.13 RC1
Date: Tue, 05 Feb 2013 11:18:05 +0100 [thread overview]
Message-ID: <1360059485.2003.3.camel@hughes.tremer.info> (raw)
In-Reply-To: <assp.07474e5d0b.5110437A.9050407@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Yeah, RC1 is totally stable, so you can use it for this purpose.
I would recommend to backup your CF media. That would not be much
trouble to dd it to some other storage and you will have the option to
go back to your original installation - just in case.
Frankly, I don't think that there might be any problems. Especially in
the OpenVPN area, where no too significant changes have been done.
I'd like to hear your feedback about CoDel :D
-Michael
On Mon, 2013-02-04 at 17:25 -0600, R. W. Rodolico wrote:
> Quick question. I have a local IPFire router that I use to connect my
> office to the "world" and to a remote network over a site-to-site
> OpenVPN Tunnel.
>
> I'd love to test 2.13 for you. Is it stable enough to do that? I'm the
> only one who uses the network currently, so if something breaks, it
> would not be a disaster (I could keep a backup of the config and just
> replace the CF in the router).
>
> This would be much more realistic for me, to simply replace my existing
> router with the RC1 software, but I just want to know what I'm letting
> myself in for.
>
> Rod
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2013-02-05 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 23:25 R. W. Rodolico
2013-02-05 10:18 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1360059485.2003.3.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox