/tech/ - Technology★

>Isn't there a better way to implement a text input and output environment?

What are you asking me this for? Go find out yourself

>>961471

>yes it's ugly;

no u

>>961472

amiga OS had the benefit of being developed for one specific hardware (Amiga models only differed by cpu speed and ram, there's basically only 2 custom chipsets), where unix was supposed to run on anything.

>>961503

>amiga OS had the benefit of being developed for one specific hardware (Amiga models only differed by cpu speed and ram, there's basically only 2 custom chipsets), where unix was supposed to run on anything.

Supremely ignorant.

Are you saying an 68030 is similar to a 68000? Fucking retard. How about that variety of crazy video modes. How about all of those SCSI and IDE controllers, video card expansions & genlocks, professional video editing setups.

Linux on PeeCees is easy mode. Just because you millennial bitches are rewriting everything in jabashit and rust doesn't mean you know up from down, dogshit from dinner.

>>961445 (OP)

it's a pile of dicks, which is what happens when you use an emulation of a 100 year old terminal to implement a framebuffer. literally all your green text is a satire of linux. it doesn't have modularity, "everything is a file" is retarded, etc.

>>961445 (OP)

What's wrong with it?

>>961445 (OP)

HURD did it better https://www.gnu.org/software/hurd/hurd/console.html

>>961507

I didn't say that, but these variations did not influence the keyboard reading code in any way.

>>961584

>Known problems and important missing features

>Squeezed at the end so nobody sees it ;)

>console server: Is probably too lax in permission checking. Does not implement settable tab stops. Does not allow to change encoding at run time. Does not allow any other screen size but 80x25.

>Combining characters is not supported.

>libcons/console-client: If you have one virtual console active, and another one receives a bell character, you don't hear the bell. This is because only the active virtual console is watched for anything interesting to happen. I think that is ok, but you might be surprised if you are used to how it works on GNU/Linux.

>Copy & Paste not supported.

>vga driver: Does not recalculate the mode lines if the font height is changed. This makes font heights below 13 or over 16 infeasible.

>Should support other text modes (integrate svgatextmode?)

>pc_kbd driver: No keyboard layout but US supported! Maybe in some cases left/right shift/ctrl/alt is allowed where both left and right should be allowed. Keyboard LEDs are only supported when using OSKIT-Mach or the CVS branch gnumach-1-branch of GNU Mach.

>ncursesw driver: Doesn't work properly on other terminals but UTF-8. Should not use C-w, this should be configurable. Does not support use of scroll back buffer.

>Other programs: Readline doesn't support multibyte encodings (4.2 and earlier). term doesn't either (all versions).

Well, that's okay. Maybe in another 35 years, they'll have it all sorted out.

>>961456

Fuck you I'm on nofap 2nd week

>Be linux terminal

>My user accidentally cats a binary file

>Get sick and start vomiting all over the place

>Start hallucinating and trying to execute random shit

>Finally done, that was rough.

>Sometime later

>my user scrolls up through his bash history

>nearly die again.

Such is life of a terminal in CY+3.

On a serious note, catting a file causing the terminal to execute commands is a tip-top vulnerabily right.

>>961676

CVE-2003-0063, CVE-2008-2383, CVE-2010-2713, CVE-2012-3515, CVE-2003-0020, CVE-2014-3121, OSVDB 3881

>>961660

I feel like cat should be responsible and know it's outputting to a console and stop you, or at least give you a "are you sure you want to continue? y/N"

>>961680

no??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

anti-sage btw

>>961456

What the fuck did you just fucking say about me, you little bitch? I'll have you know I graduated top of my class in Bridgewater, and I've been involved in numerous secret raids on Goldman and Berkshire, and I have over 300 confirmed high-profile sabotages. I am trained in gorilla trading and I'm the top hedge fund manager in the entire investment banking industry. You are nothing to me but just another dollar. I will wipe you the fuck out with precision the likes of which has never been seen before on this Earth, mark my fucking words. You think you can get away with saying that shit to me over the Internet? Think again, fucker. As we speak I am contacting my secret network of interns across the USA and your IP is being traced right now so you better prepare for the storm, maggot. The storm that wipes out the pathetic little thing you call your life. You're fucking bankrupt, kid. I can be anywhere, anytime, and I can ruin your finances in over seven hundred ways, and that's just with my bare hands. Not only am I extensively trained in unarmed financial sabotage, but I have access to the entire arsenal of Bridgewater and I will use it to its full extent to wipe your miserable ass off the face of the continent, you little shit. If only you could have known what unholy retribution your little "clever" comment was about to bring down upon you, maybe you would have held your fucking tongue. But you couldn't, you didn't, and now you're paying the price, you goddamn idiot. I will shit debt all over you and you will drown in it. You're fucking bankrupt, kiddo.

>>961680

How about you as the user try not being a retard and stat the random file you're catting first. Alternatively, use xxd if you're too lazy to bother reading stat output.

>>961660

The brain damage that causes that is the same kind of brain damage that requires you to use a program designed for concatenating files to display their contents.

>>961711

>you as the user try not being a retard

  Subject: Re: Design Cretins
  Date: Saturday, October 17, 1992 3:08PM

        You Just Don't Understand.  Writing Code To Run
        Inside Kernels Is A Hard Problem.  ...  You can't
        just allow unbounded recursion inside the
        Kernel. ...

  Am I missing something?  Couldn't this have been handled
  by a *loop*?


And from another of your recent posts:

  The idea of using in-band "escape" sequences to do
  out-of-band control functions is so far from being
  Unix-specific that I'm not sure what you're trying to
  say.

Yes, you are missing something.  The whole damn point.  Here
we have an obviously losing piece of software that is as ad
hoc as all Hell.  It doesn't work and it doesn't scale.
Typical Unix braindeath.  That's the forest.  You're looking
at trees.

Re the second point about of-band-control.  It is stupid and
unwarranted to confuse keystrokes, cursor commands, and
output glyphs into a large smelly stew.  ITS got this right,
so did other OS's.  The fact that most everyone else farts
in public is NO EXCUSE for Unix to do so.  This is software
that doesn't work.  WHY THE H*LL SHOULD LISTING A FILE
CHANGE TERMINAL CHARACTERISTICS FOR GOD'S SAKE!?!


You have obviously been brainwashed.  You can't tell working
software from broken software.  If you don't have some
horror story, or some misdesign to point out, KEEP YOUR
POSTS OFF THIS LIST!!  Kapeesh?  We don't want to hear your
confused blathering.  Go bleat with the rest of the sheep in
New Jersey.

>>961711

wew lad

>>961445 (OP)

>this thread WILL be slid

Do you feel persecuted? You little neurotic pussy.

>>961753

>those fucked up legs

absolutelyfuckingdisgusting.jpg

>>961660

>using a concatenation piece of software to view a file's contents

>instead of using less

people deserve their faith

>>961660

showing anything to the terminal is a vulnerability. proper unix hax0rs run their shit through an alhpanumeric filter

>>961504

We could have had the ultimate in user-developer motorcycles but we're stuck using a mainframe.

>>961855

>mainframe

>unix was developed for the PDP-11

>PDP-11 is a minicomputer, not a mainframe

here's your (You).

>>961445 (OP)

>Isn't there a better way to implement a text input and output environment?

No? UNIX and their derivatives are primarily command-line driven, so it makes sense to do this, as it allows for a more modular approach to driver development and generally makes the interface and behavior more consistent. I rather like not having to worry if my software's running on a VGA framebuffer, SSH session, X-Term, or honest-to-god VT100.

Maybe I'm dumb, but I'm yet to see a more elegant solution.

>>961874

a terminal emulator is literally more work to implement than setting up a VESA framebuffer

>install not-linux

>worry about whether it was able to setup a VESA framebuffer

>ooh it was able, what a surprise!

>continue on using superior OS that doesn't have 9 million metacharacter injection vulnerabilities

>>961456

Who is this titty monster

>>962003

Yeah usually the BIOS can even do a VESA buffer by itself. Modern TTY is a god awful POS bloated system.

>>962003

What model does *BSD use?