- Goals
- User guide
- History
- Application testing list
- Getting Started
- Hardware Compatibility List
- Hardware requirements
- JNode Commands
- acpi
- alias
- arp
- basename
- beep
- bindkeys
- bootp
- bsh
- bzip2
- cat
- cd
- class
- classpath
- clear
- compile
- console
- cpuid
- date
- del
- device
- df
- dhcp
- dir
- dirname
- disasm
- echo
- edit
- eject
- env
- exit
- gc
- grep
- gzip
- halt
- help
- hexdump
- history
- ifconfig
- java
- kdb
- leed, levi
- loadkeys
- locale
- log4j
- ls
- lsirq
- man
- memory
- mkdir
- mount
- namespace
- netstat
- onheap
- page
- ping
- plugin
- propset
- pwd
- ramdisk
- reboot
- remoteout
- resolver
- route
- rpcinfo
- run
- startawt
- syntax
- tar
- tcpinout
- thread
- time
- touch
- unzip
- utest
- vminfo
- wc
- zip
- JNode GUI
- JNode Shell
- Performance
- Status
- Classlib developers guide
- Developer guide
- Tester guide
- Porting guide
- Blogs
- Project development
- Glossary
- Proposals
- FAQ
- Papers & presentations
- References
- Research
cd
cd
| Synopsis | ||
| cd | [ <dirName> ] | change the current directory |
|
Details | ||
|
The cd command changes the "current" directory for the current isolate, and everything running within it. If a <dirName> argument is provided, that will be the new "current" directory. Otherwise, the current directory is set to the user's "home" directory as given by the "user.home" property.
JNode currently changes the "current" directory by setting the "user.dir" property in the system properties object. |
||
|
Bugs | ||
| The global (to the isolate) nature of the "current" directory is a problem. For example, if you have two non-isolated consoles, changing the current directory in one will change the current directory for the other, | ||
