Get the SHA1 hash of the commit that you wish to revert to.
% git log
...
commit 9ce5e10ac4fe43e9b580344454dd27172b6c4456
Author: Simon Cornelius P. Umacob
Date: Tue Jan 20 16:30:42 2009 +0800
show/hide icmp6box
commit f193cf92b2c925a2f3f71a713d766efd1e4d81e0
Author: Simon Cornelius P. Umacob
Date: Tue Jan 20 15:52:39 2009 +0800
Merge IPv6 changes
commit 1f9f2a95b7b42cf33e730535092e56e214fdb848
Author: Simon Cornelius P. Umacob
Date: Tue Jan 20 14:55:07 2009 +0800
Merge IPv6 changes
commit ce996bd3014b05fea5eaffd7c738c5c549fd7677
Author: Simon Cornelius P. Umacob
Date: Tue Jan 20 14:30:27 2009 +0800
add IPv6.inc and NetUtils.js
...
% git reset --hard ce996bd3014b05fea5eaffd7c738c5c549fd7677
HEAD now points to ce996bd3...
To go back to the "original" HEAD, find its SHA1 hash and reset your current HEAD to that state.
% git reflog
simoncpu@pfsense:/home/pfsense/simoncpu-IPv6> git reflog
74fb85b... HEAD@{0}: pull git@rcs.pfsense.org:pfsense/mainline.git: Fast forward
9ce5e10... HEAD@{1}: commit: show/hide icmp6box
f193cf9... HEAD@{2}: commit: Merge IPv6 changes
1f9f2a9... HEAD@{3}: commit: Merge IPv6 changes
ce996bd... HEAD@{4}: commit: add IPv6.inc and NetUtils.js
cfc4dab... HEAD@{5}: clone: from http://gitweb.pfsense.org/pfsense/simoncpu-IPv6.git
% git reset --hard 74fb85b
Note that you need not use the full SHA1 string to refer to an object.
The first few characters is enough.
Showing posts with label pfsense. Show all posts
Showing posts with label pfsense. Show all posts
Wednesday, January 21, 2009
HOWTO Revert your Git repo to a certain commit
Friday, January 16, 2009
pfSense IPv6
I'm currently merging our IPv6 changes to pfSense by hand so that I can commit our changes upstream once their migration from CVS to git is complete.
"With a thousand eyes, all bugs are shallow", they say. Sharing this code to the world will most likely uncover many bugs and make our code more stable. I just hope that with a thousand eyes, I won't receive a thousand flak from users in case I break something.
I'll probably break something. :)
UPDATE: As of January 16, 2011, development has been stopped. If you wish to continue development, please contact me (simoncpu at gmail.com) or post a bounty. Thanks! :)
(whoah, I realized that this post was made exactly 2 years ago lol)
"With a thousand eyes, all bugs are shallow", they say. Sharing this code to the world will most likely uncover many bugs and make our code more stable. I just hope that with a thousand eyes, I won't receive a thousand flak from users in case I break something.
I'll probably break something. :)
UPDATE: As of January 16, 2011, development has been stopped. If you wish to continue development, please contact me (simoncpu at gmail.com) or post a bounty. Thanks! :)
(whoah, I realized that this post was made exactly 2 years ago lol)
Tuesday, February 26, 2008
pfSense 1.2
It's official! pfSense 1.2 has now been released.
pfSense is a free, open source customized distribution of FreeBSD tailored for use as a firewall and router. In addition to being a powerful, flexible firewalling and routing platform, it includes a long list of related features and a package system allowing further expandability without adding bloat and potential security vulnerabilities to the base distribution. pfSense is a popular project with more than 1 million downloads since its inception, and proven in countless installations ranging from small home networks protecting a PC and an Xbox to large corporations, universities and other organizations protecting thousands of network devices.
This project started in 2004 as a fork of the m0n0wall project, but focused towards full PC installations rather than the embedded hardware focus of m0n0wall.
Monday, October 08, 2007
pfSense HTTPS fixed
OK, I found the problem. The fix is very simple:
I'll commit this change soon.
$SERVER["socket"] == "0.0.0.0:443" {
ssl.engine = "enable"
ssl.pemfile = "/var/etc/cert.pem"
}I'll commit this change soon.
fixing pfSense' HTTPS support
lighttpd seems to have an issue when enabling both IPv4 and IPv6. With plain HTTP, enabling them both is a simple matter of adding the following lines:
With HTTPS, however, $SERVER["socket"] == "0.0.0.0:443" doesn't seem to work. Although sockstat reports that lighttpd is indeed listening to port 443, https://<ip_address> doesn't work. http://<ip_address>:443 work, but this is just plain HTTP served on port 443. Weird. the following is sockstat's output:
server.use-ipv6 = "enable"
$SERVER["socket"] == "0.0.0.0:80" { }
With HTTPS, however, $SERVER["socket"] == "0.0.0.0:443" doesn't seem to work. Although sockstat reports that lighttpd is indeed listening to port 443, https://<ip_address> doesn't work. http://<ip_address>:443 work, but this is just plain HTTP served on port 443. Weird. the following is sockstat's output:
root lighttpd 53320 4 tcp6 *:443 *:*
root lighttpd 53320 5 tcp4 *:443 *:*
Friday, August 10, 2007
pfSense IPv6
Basic IPv6 support in pfSense is almost ready now. Although I expect that this still has some bugs, IPv6 support is already usable.
This is only available in the HEAD branch as of this moment. I may merge it to RELENG_1 as soon as it is deemed stable. You may download the daily snapshot at http://snapshots.pfsense.org/FreeBSD6/head/iso/.
This is only available in the HEAD branch as of this moment. I may merge it to RELENG_1 as soon as it is deemed stable. You may download the daily snapshot at http://snapshots.pfsense.org/FreeBSD6/head/iso/.
Wednesday, August 08, 2007
I'm setting up a pfSense CVS mirror right now, and I'm using nginx server for the CVS Web interface. nginx server is kindda weird-- everything has to done manually, even for setting up a Perl process that will bind to a Unix socket in order to run Perl scripts.
Here's the URL for my mirror:
http://www.simoncpu.com/freedom/pfSense/CVS/cvsweb.cgi
Please note that not everything will work, as this is still highly experimental.
Here's the URL for my mirror:
http://www.simoncpu.com/freedom/pfSense/CVS/cvsweb.cgi
Please note that not everything will work, as this is still highly experimental.
Subscribe to:
Posts (Atom)