From 75d9e14fe513d1f04f605bc1159cb9a316e89209 Mon Sep 17 00:00:00 2001 From: Bluebie Date: Tue, 17 Dec 2013 19:49:22 +1100 Subject: commandline: no functional changes - improved readme info on configuring linux to not require root access, and included udev rules file - thanks @sodabrew! --- commandline/Readme | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'commandline/Readme') diff --git a/commandline/Readme b/commandline/Readme index 00e91f7..1781e36 100644 --- a/commandline/Readme +++ b/commandline/Readme @@ -12,9 +12,10 @@ Usage on Mac: Usage on Windows micronucleus.exe --run name_of_the_file.hex -Raw binary file writing hasn't been tested much yet and is suspected to not -work. +Raw binary file writing hasn't been tested as much as hex files. Every now and then the program fails once it reaches the Writing stage - this is a known bug - but if you simply rerun the micronucleus command immediately, it -will succeed the second time usually. Most of the time this issue is not present. \ No newline at end of file +will succeed the second time usually. Most of the time this issue is not present. + +To linux users: sudo is used above because the default configuration under most modern linux distributions is to not allow userspace apps to communicate directly to unknown USB devices. You can fix this by installing some config files, or you can just use sudo. Either way you're going to need root. To configure your system to allow micronucleus access from non-root users, copy 49-micronucleus.rules from this folder to /etc/udev/rules.d/ -- cgit v1.2.3 From bfad6fd1716773c2872ca2b161775b3a2dbc24e6 Mon Sep 17 00:00:00 2001 From: Bluebie Date: Tue, 17 Dec 2013 19:50:17 +1100 Subject: commandline: no functional changes - getting rid of tab chars --- commandline/Readme | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'commandline/Readme') diff --git a/commandline/Readme b/commandline/Readme index 1781e36..8f3d5f3 100644 --- a/commandline/Readme +++ b/commandline/Readme @@ -6,7 +6,7 @@ three. To make and install, do the regular 'make; sudo make install' on unixes. On windows just 'make' with mingw and do whatever people do with windows exes. Usage on Ubuntu: - sudo micronucleus --run name_of_the_file.hex + sudo micronucleus --run name_of_the_file.hex Usage on Mac: micronucleus --run name_of_the_file.hex Usage on Windows -- cgit v1.2.3 From 04e0d950d18fba8af17e844f9d6d0bb868cb5981 Mon Sep 17 00:00:00 2001 From: Bluebie Date: Tue, 17 Dec 2013 19:51:50 +1100 Subject: commandline: readme.. My brain is bad today. no functional changes, just style stuff --- commandline/Readme | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'commandline/Readme') diff --git a/commandline/Readme b/commandline/Readme index 8f3d5f3..329247a 100644 --- a/commandline/Readme +++ b/commandline/Readme @@ -18,4 +18,9 @@ Every now and then the program fails once it reaches the Writing stage - this is a known bug - but if you simply rerun the micronucleus command immediately, it will succeed the second time usually. Most of the time this issue is not present. -To linux users: sudo is used above because the default configuration under most modern linux distributions is to not allow userspace apps to communicate directly to unknown USB devices. You can fix this by installing some config files, or you can just use sudo. Either way you're going to need root. To configure your system to allow micronucleus access from non-root users, copy 49-micronucleus.rules from this folder to /etc/udev/rules.d/ +To linux users: sudo is used above because the default configuration under most +modern linux distributions is to not allow userspace apps to communicate +directly to unknown USB devices. You can fix this by installing some config +files, or you can just use sudo. Either way you're going to need root. To +configure your system to allow micronucleus access from non-root users, copy +49-micronucleus.rules from this folder to /etc/udev/rules.d/ -- cgit v1.2.3