Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-26-2012, 04:55 AM
|
#1
|
Member
Registered: Mar 2012
Location: England
Distribution: Debian, Kali, CentOS 7
Posts: 64
Rep:
|
stuck with > at start of command line?
Using Centos ive come across something ive not seen before - for a newb!
i've logged in and then set about config my nics
after a while i wrote
[root@alexandria} if config
the space between if and config was an error this resulted in all following lines to start with
>
and no matter what command i entered it did nothing and repeated a new line starting
>
how can i ezxit this mode?
what is this > mode for?
thanks
|
|
|
04-26-2012, 04:57 AM
|
#2
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
just hit "Ctrl C". Or type in "fi"
it's just expecting you to continue the "if" statement you accidentally started, so until it sees a "fi" it will keep that block open.
|
|
1 members found this post helpful.
|
04-26-2012, 04:58 AM
|
#3
|
LQ 5k Club
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian
Posts: 8,578
|
Did you try Ctrl+C? > is the conventional prompt indication incomplete input. Ctrl+C should kill the command and allow you to continue.
|
|
1 members found this post helpful.
|
04-26-2012, 05:00 AM
|
#4
|
Member
Registered: Mar 2012
Location: England
Distribution: Debian, Kali, CentOS 7
Posts: 64
Original Poster
Rep:
|
Oww gosh! that really was simple!
haha thanks!
|
|
|
04-26-2012, 05:16 AM
|
#5
|
Bash Guru
Registered: Jun 2004
Location: Osaka, Japan
Distribution: Arch + Xfce
Posts: 6,852
|
The character you see is the PS2 prompt, which is the string that the shell prints out for multi-line input.
As the others have pointed out, any command you type that is considered "unfinished" by the shell, such as unpaired quotes or keyword blocks (if..fi, for..done, etc.), results in a new line being provided for you to continue on. Either complete the command as it expects or crtl+c to terminate it.
|
|
|
All times are GMT -5. The time now is 04:55 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|