What keypress will take me to tty13?
Trying out Ubuntu Intrepid, I have discovered that RightAlt+F1 doesn't take me to tty13.
I've exhaustively tried every option presented to me in dpkg-reconfigure console-setup
, the best I've been able to manage thus far has been to have both Alt keys behave the same (LeftAlt+F1 and RightAlt+F1 both going to tty1).
Please note that using GNU screen
is not considered a valid response to the question - this is specifically about how to get the keyboard to behave properly with multiple consoles under Ubuntu. The crazy thing is that every other distro I've tried just handles this correctly, including Debian Lenny.
console tty
migrated from stackoverflow.com Aug 18 '11 at 22:59
This question came from our site for professional and enthusiast programmers.
add a comment |
Trying out Ubuntu Intrepid, I have discovered that RightAlt+F1 doesn't take me to tty13.
I've exhaustively tried every option presented to me in dpkg-reconfigure console-setup
, the best I've been able to manage thus far has been to have both Alt keys behave the same (LeftAlt+F1 and RightAlt+F1 both going to tty1).
Please note that using GNU screen
is not considered a valid response to the question - this is specifically about how to get the keyboard to behave properly with multiple consoles under Ubuntu. The crazy thing is that every other distro I've tried just handles this correctly, including Debian Lenny.
console tty
migrated from stackoverflow.com Aug 18 '11 at 22:59
This question came from our site for professional and enthusiast programmers.
add a comment |
Trying out Ubuntu Intrepid, I have discovered that RightAlt+F1 doesn't take me to tty13.
I've exhaustively tried every option presented to me in dpkg-reconfigure console-setup
, the best I've been able to manage thus far has been to have both Alt keys behave the same (LeftAlt+F1 and RightAlt+F1 both going to tty1).
Please note that using GNU screen
is not considered a valid response to the question - this is specifically about how to get the keyboard to behave properly with multiple consoles under Ubuntu. The crazy thing is that every other distro I've tried just handles this correctly, including Debian Lenny.
console tty
Trying out Ubuntu Intrepid, I have discovered that RightAlt+F1 doesn't take me to tty13.
I've exhaustively tried every option presented to me in dpkg-reconfigure console-setup
, the best I've been able to manage thus far has been to have both Alt keys behave the same (LeftAlt+F1 and RightAlt+F1 both going to tty1).
Please note that using GNU screen
is not considered a valid response to the question - this is specifically about how to get the keyboard to behave properly with multiple consoles under Ubuntu. The crazy thing is that every other distro I've tried just handles this correctly, including Debian Lenny.
console tty
console tty
edited Mar 29 '13 at 5:13
Kevin Bowen
14.7k155970
14.7k155970
asked Feb 3 '09 at 3:55
TMLTML
367212
367212
migrated from stackoverflow.com Aug 18 '11 at 22:59
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Aug 18 '11 at 22:59
This question came from our site for professional and enthusiast programmers.
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
After a lot of attempts to fix this various ways, I finally figured out how to use dumpkeys
and loadkeys
to modify the kernel's "keyboard translation table". Here are the loadkeys
strings to set RightAlt+F1 through RightAlt+F12 to their respective offsets from tty12:
altgr keycode 59 = Console_13
altgr keycode 60 = Console_14
altgr keycode 61 = Console_15
altgr keycode 62 = Console_16
altgr keycode 63 = Console_17
altgr keycode 64 = Console_18
altgr keycode 65 = Console_19
altgr keycode 66 = Console_20
altgr keycode 67 = Console_21
altgr keycode 68 = Console_22
altgr keycode 87 = Console_23
altgr keycode 88 = Console_24
Why Ubuntu doesn't include this in the default setup remains a mystery. :)
add a comment |
On most systems, if you are at a text console, you can use Alt + the arrow keys to move to next and previous console.
add a comment |
In Debian, I would just edit /etc/inittab
, but Ubuntu uses Upstart.
Apparently, you're supposed to edit /etc/default/console-setup
and set the ACTIVE_CONSOLES
variable to be /dev/tty[1-13]
in your case.
Before changing this, Right-Alt + Ctrl + F1 would bring me to tty1
. Now, I just get a blank screen that I can't do anything on. I also had to manually copy the file /etc/event.d/tty1
to /etc/event.d/tty13
and change the settings inside appropriately.
I can't seem to get it to work.
shrug
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
add a comment |
There's a nice program called chvt that takes you to another virtual console. (e.g. 'sudo chvt 1' would pop me right out of X, right now.) It's a bit obnoxious in that X drivers don't always like vt-switching. On the other hand, it's saved me more than once when X has gotten wedged. You might also want to look at a program called "open" which opens a new virtual terminal.
...But if your problem is really that you want more terminals, what I'd really recommend is to look into screen. It does all kinds of nifty things. Like being able to ssh in and connect to the same session you worked on locally, in what I think of as "multiplayer".. (well, you can be attached to the same (backend-) session from multiple frontends.) It kicks ass. I use it every day at work, where I have a very long-running session on one of the anarchic dev-servers.
As for your actual reported problem, well.. hmm.. how's your keyboard configured? Does it work with some more 'popular' keymap?
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
add a comment |
Are you running X? If so, check your Gnome or KDE keyboard shortcuts to make sure that this isn't bound to something else.
If you're not using X, then why not just use "screen" for console / shell management? That's a much more elegant solution than relying on Linux's multiple consoles. man screen
2
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f57736%2fwhat-keypress-will-take-me-to-tty13%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
After a lot of attempts to fix this various ways, I finally figured out how to use dumpkeys
and loadkeys
to modify the kernel's "keyboard translation table". Here are the loadkeys
strings to set RightAlt+F1 through RightAlt+F12 to their respective offsets from tty12:
altgr keycode 59 = Console_13
altgr keycode 60 = Console_14
altgr keycode 61 = Console_15
altgr keycode 62 = Console_16
altgr keycode 63 = Console_17
altgr keycode 64 = Console_18
altgr keycode 65 = Console_19
altgr keycode 66 = Console_20
altgr keycode 67 = Console_21
altgr keycode 68 = Console_22
altgr keycode 87 = Console_23
altgr keycode 88 = Console_24
Why Ubuntu doesn't include this in the default setup remains a mystery. :)
add a comment |
After a lot of attempts to fix this various ways, I finally figured out how to use dumpkeys
and loadkeys
to modify the kernel's "keyboard translation table". Here are the loadkeys
strings to set RightAlt+F1 through RightAlt+F12 to their respective offsets from tty12:
altgr keycode 59 = Console_13
altgr keycode 60 = Console_14
altgr keycode 61 = Console_15
altgr keycode 62 = Console_16
altgr keycode 63 = Console_17
altgr keycode 64 = Console_18
altgr keycode 65 = Console_19
altgr keycode 66 = Console_20
altgr keycode 67 = Console_21
altgr keycode 68 = Console_22
altgr keycode 87 = Console_23
altgr keycode 88 = Console_24
Why Ubuntu doesn't include this in the default setup remains a mystery. :)
add a comment |
After a lot of attempts to fix this various ways, I finally figured out how to use dumpkeys
and loadkeys
to modify the kernel's "keyboard translation table". Here are the loadkeys
strings to set RightAlt+F1 through RightAlt+F12 to their respective offsets from tty12:
altgr keycode 59 = Console_13
altgr keycode 60 = Console_14
altgr keycode 61 = Console_15
altgr keycode 62 = Console_16
altgr keycode 63 = Console_17
altgr keycode 64 = Console_18
altgr keycode 65 = Console_19
altgr keycode 66 = Console_20
altgr keycode 67 = Console_21
altgr keycode 68 = Console_22
altgr keycode 87 = Console_23
altgr keycode 88 = Console_24
Why Ubuntu doesn't include this in the default setup remains a mystery. :)
After a lot of attempts to fix this various ways, I finally figured out how to use dumpkeys
and loadkeys
to modify the kernel's "keyboard translation table". Here are the loadkeys
strings to set RightAlt+F1 through RightAlt+F12 to their respective offsets from tty12:
altgr keycode 59 = Console_13
altgr keycode 60 = Console_14
altgr keycode 61 = Console_15
altgr keycode 62 = Console_16
altgr keycode 63 = Console_17
altgr keycode 64 = Console_18
altgr keycode 65 = Console_19
altgr keycode 66 = Console_20
altgr keycode 67 = Console_21
altgr keycode 68 = Console_22
altgr keycode 87 = Console_23
altgr keycode 88 = Console_24
Why Ubuntu doesn't include this in the default setup remains a mystery. :)
edited Mar 29 '13 at 3:46
Eric Carvalho
42.4k17116147
42.4k17116147
answered May 4 '09 at 18:01
TMLTML
367212
367212
add a comment |
add a comment |
On most systems, if you are at a text console, you can use Alt + the arrow keys to move to next and previous console.
add a comment |
On most systems, if you are at a text console, you can use Alt + the arrow keys to move to next and previous console.
add a comment |
On most systems, if you are at a text console, you can use Alt + the arrow keys to move to next and previous console.
On most systems, if you are at a text console, you can use Alt + the arrow keys to move to next and previous console.
answered Feb 13 '09 at 23:13
gbarrygbarry
1413
1413
add a comment |
add a comment |
In Debian, I would just edit /etc/inittab
, but Ubuntu uses Upstart.
Apparently, you're supposed to edit /etc/default/console-setup
and set the ACTIVE_CONSOLES
variable to be /dev/tty[1-13]
in your case.
Before changing this, Right-Alt + Ctrl + F1 would bring me to tty1
. Now, I just get a blank screen that I can't do anything on. I also had to manually copy the file /etc/event.d/tty1
to /etc/event.d/tty13
and change the settings inside appropriately.
I can't seem to get it to work.
shrug
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
add a comment |
In Debian, I would just edit /etc/inittab
, but Ubuntu uses Upstart.
Apparently, you're supposed to edit /etc/default/console-setup
and set the ACTIVE_CONSOLES
variable to be /dev/tty[1-13]
in your case.
Before changing this, Right-Alt + Ctrl + F1 would bring me to tty1
. Now, I just get a blank screen that I can't do anything on. I also had to manually copy the file /etc/event.d/tty1
to /etc/event.d/tty13
and change the settings inside appropriately.
I can't seem to get it to work.
shrug
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
add a comment |
In Debian, I would just edit /etc/inittab
, but Ubuntu uses Upstart.
Apparently, you're supposed to edit /etc/default/console-setup
and set the ACTIVE_CONSOLES
variable to be /dev/tty[1-13]
in your case.
Before changing this, Right-Alt + Ctrl + F1 would bring me to tty1
. Now, I just get a blank screen that I can't do anything on. I also had to manually copy the file /etc/event.d/tty1
to /etc/event.d/tty13
and change the settings inside appropriately.
I can't seem to get it to work.
shrug
In Debian, I would just edit /etc/inittab
, but Ubuntu uses Upstart.
Apparently, you're supposed to edit /etc/default/console-setup
and set the ACTIVE_CONSOLES
variable to be /dev/tty[1-13]
in your case.
Before changing this, Right-Alt + Ctrl + F1 would bring me to tty1
. Now, I just get a blank screen that I can't do anything on. I also had to manually copy the file /etc/event.d/tty1
to /etc/event.d/tty13
and change the settings inside appropriately.
I can't seem to get it to work.
shrug
edited May 25 '18 at 15:42
Adeel
1035
1035
answered Feb 3 '09 at 4:52
Nick PrestaNick Presta
1412
1412
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
add a comment |
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
I have no trouble getting tty13 to start, it's simply a question of how do I get to it once it's started (other than LeftAlt+F12 followed by LeftAlt-RightArrow), but thanks. :)
– TML
Feb 3 '09 at 5:36
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
Blank screen may be a (second) X window
– gbarry
Feb 13 '09 at 23:13
add a comment |
There's a nice program called chvt that takes you to another virtual console. (e.g. 'sudo chvt 1' would pop me right out of X, right now.) It's a bit obnoxious in that X drivers don't always like vt-switching. On the other hand, it's saved me more than once when X has gotten wedged. You might also want to look at a program called "open" which opens a new virtual terminal.
...But if your problem is really that you want more terminals, what I'd really recommend is to look into screen. It does all kinds of nifty things. Like being able to ssh in and connect to the same session you worked on locally, in what I think of as "multiplayer".. (well, you can be attached to the same (backend-) session from multiple frontends.) It kicks ass. I use it every day at work, where I have a very long-running session on one of the anarchic dev-servers.
As for your actual reported problem, well.. hmm.. how's your keyboard configured? Does it work with some more 'popular' keymap?
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
add a comment |
There's a nice program called chvt that takes you to another virtual console. (e.g. 'sudo chvt 1' would pop me right out of X, right now.) It's a bit obnoxious in that X drivers don't always like vt-switching. On the other hand, it's saved me more than once when X has gotten wedged. You might also want to look at a program called "open" which opens a new virtual terminal.
...But if your problem is really that you want more terminals, what I'd really recommend is to look into screen. It does all kinds of nifty things. Like being able to ssh in and connect to the same session you worked on locally, in what I think of as "multiplayer".. (well, you can be attached to the same (backend-) session from multiple frontends.) It kicks ass. I use it every day at work, where I have a very long-running session on one of the anarchic dev-servers.
As for your actual reported problem, well.. hmm.. how's your keyboard configured? Does it work with some more 'popular' keymap?
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
add a comment |
There's a nice program called chvt that takes you to another virtual console. (e.g. 'sudo chvt 1' would pop me right out of X, right now.) It's a bit obnoxious in that X drivers don't always like vt-switching. On the other hand, it's saved me more than once when X has gotten wedged. You might also want to look at a program called "open" which opens a new virtual terminal.
...But if your problem is really that you want more terminals, what I'd really recommend is to look into screen. It does all kinds of nifty things. Like being able to ssh in and connect to the same session you worked on locally, in what I think of as "multiplayer".. (well, you can be attached to the same (backend-) session from multiple frontends.) It kicks ass. I use it every day at work, where I have a very long-running session on one of the anarchic dev-servers.
As for your actual reported problem, well.. hmm.. how's your keyboard configured? Does it work with some more 'popular' keymap?
There's a nice program called chvt that takes you to another virtual console. (e.g. 'sudo chvt 1' would pop me right out of X, right now.) It's a bit obnoxious in that X drivers don't always like vt-switching. On the other hand, it's saved me more than once when X has gotten wedged. You might also want to look at a program called "open" which opens a new virtual terminal.
...But if your problem is really that you want more terminals, what I'd really recommend is to look into screen. It does all kinds of nifty things. Like being able to ssh in and connect to the same session you worked on locally, in what I think of as "multiplayer".. (well, you can be attached to the same (backend-) session from multiple frontends.) It kicks ass. I use it every day at work, where I have a very long-running session on one of the anarchic dev-servers.
As for your actual reported problem, well.. hmm.. how's your keyboard configured? Does it work with some more 'popular' keymap?
answered Feb 7 '09 at 23:26
Anders EureniusAnders Eurenius
1312
1312
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
add a comment |
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
I've exhaustively tried every keymap available. I'm fully aware of screen, and use it daily for remote sessions, but there are features of a vt that screen can't give-e.g., the (gpm) mouse support is spotty at best. As I'm not using X I'll see if I can discover some way to map chvt to keystrokes.
– TML
Feb 13 '09 at 9:08
add a comment |
Are you running X? If so, check your Gnome or KDE keyboard shortcuts to make sure that this isn't bound to something else.
If you're not using X, then why not just use "screen" for console / shell management? That's a much more elegant solution than relying on Linux's multiple consoles. man screen
2
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
add a comment |
Are you running X? If so, check your Gnome or KDE keyboard shortcuts to make sure that this isn't bound to something else.
If you're not using X, then why not just use "screen" for console / shell management? That's a much more elegant solution than relying on Linux's multiple consoles. man screen
2
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
add a comment |
Are you running X? If so, check your Gnome or KDE keyboard shortcuts to make sure that this isn't bound to something else.
If you're not using X, then why not just use "screen" for console / shell management? That's a much more elegant solution than relying on Linux's multiple consoles. man screen
Are you running X? If so, check your Gnome or KDE keyboard shortcuts to make sure that this isn't bound to something else.
If you're not using X, then why not just use "screen" for console / shell management? That's a much more elegant solution than relying on Linux's multiple consoles. man screen
answered Feb 13 '09 at 22:44
slacyslacy
22314
22314
2
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
add a comment |
2
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
2
2
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
Thanks for responding. As I mentioned earlier to Anders Eurenius, there are a number of features that a true "VT" gives that are missing from GNU screen - the biggest one being the inconsistent support for the console mouse server "gpm".
– TML
Feb 18 '09 at 18:42
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f57736%2fwhat-keypress-will-take-me-to-tty13%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown