/bsd/ - *BSD Discussion

Microchip still have that proprietary licence on every library, though? Fuck that.

>>29

I didn't look at that. I take it it must be pretty restrictive. I still like the retro-ness of the system.

Besides, maybe having restrictive source code licensing gives you that nice retro UNIX feel. (cricket)

>>30

I don't know what you're going on about, Anon. Not trying to be a dick.

>no LICENSE.txt

Nice, thread got deleted on /tech/. Goes to show

EDIT: Nevermind, my mistake. Was pretty sure it got deleted though.

>>31

I'm the author of Ersatz Emacs that emg is based on.

>>33

Shit is impossible to use on a Dvorak keyboard. Crtl+X+C? Fuck me, X and C are miiiiiiiiles apart.

>>32

The server is having some problems. Special pages often 404 temporarily. This causes the auto-updater to think they've been deleted.

>>36

Ah, thanks for the info Anon. I'll keep that in mind when I'm on 8ch.

>>33

Emacs is slow on older PCs, can't imagine how slow it'll be on a PIC. That said, running any OS at all on a PIC is pretty cool.

>>39

Actually, I should have made it clear that emg is a clone. It runs pretty darn well – it was designed for low memory systems.

The only lag you'll get will be from the serial connection.

Is there a reason country flags are enabled?

>>41

Not really, I went happy with the config. It'd be cool to see a board where you can't samefag easily. If a lot of people don't like it, I'll get rid of it though.

>>42

I fucking hate country flags. This isn't /int/

>>44

Tell you what, if one more person says that in the next 10 minutes I'll get rid of the flags when I wake up.

>>42

You already have IDs enabled for that, so an additional system with lots of room for false positives (I'm not >>44 but you might think so if you rely on flags) seems redundant.

>>35

>Dvorak Master Race can't into editing source code file with the keybindings.

>>50

I completely forgot about the ID tag. Country flags have been removed.

Plus Tor would sort of warrant them to be useless.

I'm thinking of rigging up a terminal for my board.

Nothing fancy, just a TFT LCD and a PS/2 keyboard. I'll connect those to an Arduino then just use the ATMega's serial port (so that way I don't have to bother writing kernel drivers.) Also, it'd be really cool to have a terminal that runs at 300 baud – fast enough to read, slow enough to be a pain.

There's a guy who put BSD 4.4 on a microchip.

https://github.com/sergev/LiteBSD

>>103

Same dude, sister project. I'll definitely get around to making a detailed tutorial/overview on LiteBSD when I have the money to buy a board.

>>104

I thought they worked on the same board… what board does the 4.4 version require? I would love to use this as a project.

>>89

Are you talking about a literal terminal machine? Like a modern VT220?

That would be fucking amazan can you imagine an e-ink display? You'd have a mobile laptop that would last for months off a single charge.

>>106

>mobile laptop

>requires serial line

uh-huh

>>105

Sadly, they don't. because of the network stack in 4.4BSD, you need to have more RAM (or something like that.)

2.11BSD = 128KB RAM

4.4BSD = 512KB RAM

There is a list of supported boards here:

https://github.com/sergev/LiteBSD/wiki

Ethernet is supported, I have no clue about the WiFire. Look at retrobsd.org. I would look into it IF I had the money.

>>106

I was thinking of starting with a LCD and a PS/2 keyboard. A very low power display would be nice, seeing as the entire dev board probably doesn't use more than 500mW (guessing. Too lazy to break out the multimeter.)

Multiple screens would be amazing, too. You could use one for coding/working and the other for man – that's basically what I do now when I code.

>>107

There are plenty of ways around that, but it would probably not be as pseudovintage, if that makes any sense.

>>108

>making /bsd/ admin look like a scrub

I'd just like to interject for a moment. What you're referring to as BSD, is in fact, BSD/Unix, or as I've recently taken to calling it, Unix plus BSD. BSD is not an operating system onto itself, but rather another paid component of a fully functioning Unix system made useful by the BSD libraries, utilities, and vital system components compromising a full OS as defined by POSIX. Many computer users run a modified version of the BSD system everyday, without realizing it. Through a peculiar turn of events, the version of BSD which is widely used today is often called "Unix," and many of its users are not aware that it is basically the BSD system, developed by Berkeley University. There really is a Unix, and these people are using it, but it is just a part of the system they use. Unix is the base OS: the software that manages computer hardware and software resources. Unix is an essential part of BSD, but useless by itself; it does not have a network stack such as the one in 4.4BSD. Unix is normally used in combination with BSD: the whole system is basically Unix with BSD added, or BSD/Unix. All of the so-called "BSD" distributions are really distributions of BSD/Unix.