![]() |
2010-11-01
, 02:14
|
|
Posts: 4,365 |
Thanked: 2,467 times |
Joined on Jan 2010
@ Australia Mate
|
#2
|
![]() |
2010-11-01
, 02:18
|
|
Posts: 435 |
Thanked: 160 times |
Joined on Dec 2009
|
#3
|
![]() |
2010-11-01
, 03:04
|
Posts: 49 |
Thanked: 33 times |
Joined on Dec 2009
@ Berlin/Germany
|
#4
|
![]() |
2010-11-01
, 03:15
|
|
Posts: 255 |
Thanked: 160 times |
Joined on Oct 2010
@ Finland
|
#5
|
![]() |
2010-11-01
, 03:44
|
Posts: 49 |
Thanked: 33 times |
Joined on Dec 2009
@ Berlin/Germany
|
#6
|
![]() |
2010-11-01
, 04:08
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#7
|
![]() |
2010-11-01
, 04:37
|
Posts: 19 |
Thanked: 6 times |
Joined on Jul 2008
@ Melbourne, Australia
|
#8
|
![]() |
2010-11-01
, 12:50
|
Posts: 838 |
Thanked: 292 times |
Joined on Apr 2010
|
#9
|
I was attempting to fix my prompt (get it back to how it used to look) after installing bash as my shell for the default user (user). well I changed back to /bin/sh, ran echo $PS1 wrote down that result and changed user back to /bin/bash. I then (yes without running it on the command line which is why I call myself a dumbass *****) opened up .bashrc and put export $PS1="the output of my previous echo $PS1 command".
duh apart from not having tested it from the command line first... there should be no $. well anyway the result is the reboot process brings me to the dots flashing across my screen forever.
so is there any "backdoor" to get in and fix my .bashrc? or am I looking at a complete reflash of the device?
Last edited by extendedping; 2010-11-01 at 02:20.