Trouble deploying code from new laptop

[Alan Anderson]

You can put the password in the build preferences. You probably have already done that on the Classmate.

According to a couple of the Beta Test teams, you cannot remove the password without reloading the roboRIO image. The option to do so is not part of the BusyBox Linux shell.

[plnyyanks]

Originally Posted by Alan Anderson

You can put the password in the build preferences. You probably have already done that on the Classmate.

According to a couple of the Beta Test teams, you cannot remove the password without reloading the roboRIO image. The option to do so is not part of the BusyBox Linux shell.

I don't have access to a RIO to test with, but it seems possible to change a password with a config file and chpasswd. Although chpasswd isn't available in the busybox version on my phone (v1.23.1), so go figure...

[Alan Anderson]

Originally Posted by plnyyanks

...it seems possible to change a password with a config file and chpasswd.

Changing a password is simple. Doing so is what caused the deployment failures described in the original post. Removing a password is not supported.

[ozrien]

Is there a reason to change the Rio's password? It makes csa-ing more difficult and breaks code deployment. There is no upside, even if you hack the scripts to make it work

[virtuald]

Originally Posted by ozrien

Is there a reason to change the Rio's password? It makes csa-ing more difficult and breaks code deployment. There is no upside, even if you hack the scripts to make it work

I suspect that people are (correctly) conditioned to change passwords when there's an option to do so, particularly if the password is empty. It's "more secure", after all.

Of course, since you can anonymous FTP on the roborio with impunity, seems like it's a silly thing to do.