News for hackers. Stuff that matters.
Re:Writing to the Framebuffer by tbirdz on Wednesday April 04, 2018 @05:14PM (#16759166)
The reason why sudo wasn't working is that it runs the command with root privileges, but redirecting to a file with > is done through the shell, which is running under your normal user level privileges. If you want to redirect to a file that only root can write to, you can use the tee command. That command will write anything passed to it via stdin to the file given as an arg.

For example, echo "foo" | sudo tee /path/to/file

or any of the other ways listed here: https://stackoverflow.com/questions/82256/how-do-i-use-sudo-...

Re:Writing to the Framebuffer by saagarjha on Wednesday April 04, 2018 @05:27PM (#16759304)
tee also prints to standard output, so I'd suggest piping to /dev/null if you're going to produce a lot of output.
Re:Writing to the Framebuffer by digi_owl on Wednesday April 04, 2018 @06:34PM (#16759925)
My first thought was to use the sh -c method.
Re:Writing to the Framebuffer by pwg on Wednesday April 04, 2018 @09:22PM (#16760958)
Or, just use 'su' to become root, then write to the device file.
Re:Writing to the Framebuffer by rusk on Monday April 09, 2018 @04:45AM (#16791365)
su isn't an option that's available to "regular" users. In particular in an environment where sudo has been set up correctly then it may be for the reason that you want regular users to be able to perform "some" powerful functions without giving them the keys to the system.
Re:Writing to the Framebuffer by lainga on Wednesday April 04, 2018 @05:31PM (#16759340)
Or you can add your user to the `video` group.

EDIT: it says so in TFA. Oops!