Linux stty

[SeriousCat]

I'm an educated man but this might be the thread that I understand the least, ever. I assume it's about computers but I'm not 100% on that. Just thought I'd share. Kudos to anybody who does get this stuff.

Carry on

it translates as "i want to do something that only 17 people in the world have ever done of which fifteen only did it once and dont remember how it worked off the top of their heads - can someone here ask one of the other two because i cant be arsed?"

[rocktron]

......However - and this is probably the cause of it - the PC running Linux has been booted since. The port setup has been lost and I've had to reconfigure it. I know the port speed, character size, and number of stop bits is right, but there's something else I've forgotten to do and I can't remember what!.....

Possibly a system.conf file which you need to edit, so that when the system is rebooted, the changes you made are not lost?

[musophilr]

Possibly a system.conf file which you need to edit, so that when the system is rebooted, the changes you made are not lost?

That is not beyond possibility. However I think there has to be something else, as I can see from other indicators that I am transmitting data to the remote end, and in such form as it understands and can reply, because the same indicators reveal a reply being transmitted in the reverse direction. Except that the reply does not make it from the port to the buffer I supplied to fread.

[cacofonix]

You have overwritten the /dev/USB0 file with the data.

It should be a pipe, not a >

so | rather than >

I overwrote my cups driver this way. I was most embarassed when /dev/cups0 turned out to be the result of ls al ~/


(actually, it was /dev/lpr but who's counting?)

[jalapeno]

Holy crap on a cycle - this takes me back a couple of decades to titting* around with RS232 comms

* = very technical term

[musophilr]

Holy crap on a cycle - this takes me back a couple of decades to titting* around with RS232 comms

* = very technical term

Isn't that becuase of how you pronounce /dev/tty as slash dev slash titty?

[musophilr]

You have overwritten the /dev/USB0 file with the data.

It should be a pipe, not a >

so | rather than >

I overwrote my cups driver this way. I was most embarassed when /dev/cups0 turned out to be the result of ls al ~/


(actually, it was /dev/lpr but who's counting?)

Not according to the help pages that came up when i googled. Although it's not a file, you address it as though it is one, Linux knows its a character device.

Anyway, using the > operator worked before

[musophilr]

I tried the open/read/write/close family of syscalls instead of the fopen/fread/fwrite/fclose family of library routines. The program is working again