grenzland.club is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Search results for tag #unix

random stranger »
@kyonshi@dice.camp

spent my evening installing KiwiIRC for our little network. It's a web chat portal, giving access to our little network (the GrenzlandNet? Did we agree on that name?)

Anyway, spent most of the time trying to validate the json file used for configuration, and then a bit more time trying to make it play nice with caddy. Still not sure if it actually does. But if it does it should be reachable under chat.wilderland.ovh/

    The Psychotic Network Ferret » 🤖
    @nuintari@mastodon.bsd.cafe

    I really didn't get the appeal of tiling window managers at first, but then I discovered ion(defunct, now replaced with notion), which adds in stackable panes. Each window pane can contain more than one child window. A simple mouse click or Mod4+Tab shifts between them.

    Beyond that, its just some basic controls. Mod4+F1 opens a web browser, F2 is a terminal, F3 is a run dialogue, F4 is an SSH session, stuff like that.

    The thing I really like about notion is that opening a new program does not cause your existing layout to change. You draw the layout first, and have a series of empty panes that you can populate with applications. You can even drag windows between panes. I really dislike how most tiling window managers are always dynamic, all the time. You open a new thing, and BAM, all of sudden everything else has moved and shifted in size. I'm a very position oriented person. I like to put things in a particular spot, and leave them there, so I can find them later.

    I really dislike modern desktop environments. They are slow, obtrusive, and waste entirely too much screen real estate on useless things like toolbars. I want the user interface to be as simple as possible, and to stay the hell out of my way.

    So, this is my (#FreeBSD specifically) workstation. Four monitors. I generally keep the web browsers and other large GUI applications to the full screen panes on the left, and use the right for my terminal windows and smaller applications. But I _always_ have an xterm open in every single pane. I can never find a terminal fast enough when I am angry|stressed|tired|etc. 😜

    So, this is how and why I do things the way I do on a computer. I'm hoping so of y'all will post screenshots of your own, and talk about what works for you. Because we are all different, we all have different ways of thinking, needs, and desires. And to quote Chris Boden, "That's pretty cool!"

    Oh, if someone submits a better , I will totally use it.

    Screenshot of my FreeBSD workstation. Four monitors, with windows handled by the tiling+paneing window manager "notion." Various terminal windows are shown with applications such as cbonsai, fastfetch, cpufetch, and fortune. Several SSH sessions are also shown.

    Alt...Screenshot of my FreeBSD workstation. Four monitors, with windows handled by the tiling+paneing window manager "notion." Various terminal windows are shown with applications such as cbonsai, fastfetch, cpufetch, and fortune. Several SSH sessions are also shown.

      SDF.ORG boosted

      ICM »
      @icm@mastodon.sdf.org

      Cidney boosted

      random stranger »
      @kyonshi@dice.camp

      version... dunno... 12?

      German, he/him, 40s, living in Poland (#lodz). I work in IT and do some geeky computer stuff on the side (#usenet, , , )

      My main hobby are (#osr , , ) and similar (#minipainting, ) but I also do writing and reading (#fantasy, ) and .

      I will be complaining about , , lack of , and the general state of the world

      I do get weirdly obsessed with topics. But don't we all?

        SDF.ORG boosted

        ICM »
        @icm@mastodon.sdf.org

        Misspiggy’s decwriter is accepting logins to the decsystem-570 running version 7. You can connect yourself at connect.sdf.org

          random stranger »
          @kyonshi@dice.camp

          ok, working on I am not quite sure if I even have the right repositories. According to what I read online the hipster-encumbered repository should have all kinds of different things, not just 63 packages.

          I feel like I am missing something here.

            random stranger »
            @kyonshi@dice.camp

            today I am trying OpenIndiana on the side (an distribution). First problem: they give both an ISO and a .usb file for download. Turns out using the ISO to create a USB medium does NOT work, because it's missing the right drivers.

            hmmm...

              Tomáš »
              @prahou@merveilles.town

              my memory of drawterm is fading 4

              It is december 1994.

theo de raadt is forced to leave the netbsd project.

people around the world report seeing an apparation of a shape covered in spikes resembling a fish.

it will not be seen again for another 5 years.

in new jersey plan 9 replaces unix in bell labs.

my memory of drawterm is fading.

              Alt...It is december 1994. theo de raadt is forced to leave the netbsd project. people around the world report seeing an apparation of a shape covered in spikes resembling a fish. it will not be seen again for another 5 years. in new jersey plan 9 replaces unix in bell labs. my memory of drawterm is fading.

                Michael Engel »
                @me_@sueden.social

                Sean Haas' talk about the Unix Wars mentions Bill Plauger and Idris history!

                youtube.com/watch?v=RjtxpvXT5cA

                  random stranger »
                  @kyonshi@dice.camp

                  experimenting with today. (courtesy of @ptribble ), a variation of illumos.

                  it doesn't hold back as to what it is. it tells me from the get go that is starting

                    screwlisp »
                    @screwlisp@gamerplus.org

                    on again ! toobnix.org/w/gXLXQqxf5MYg1NDF anonradio one is replay

                    On the hour!

                    Hopefully joined by @kentpitman and @ramin_hal9001

                    Viz the I am hoping to talk about the thing viz @cwebber gamerplus.org/@cwebber@social.

                    the wonderful @nosrednayduj clued me into discussions and the paper on failure chai.uni-hamburg.de/~moeller/s

                    ALSO our @dougmerritt and and and

                    Chat in as always!

                    The lispy Gopher climate Moon unix_surrealism banne. The green lisp alien with many beautiful eyes looks down from a color monitor at the grizzled gopher in a grayscale dystopian world beneath a broken moon.

                    Alt...The lispy Gopher climate Moon unix_surrealism banne. The green lisp alien with many beautiful eyes looks down from a color monitor at the grizzled gopher in a grayscale dystopian world beneath a broken moon.

                      Michael Engel »
                      @me_@sueden.social

                      It’s vintage computer repair meeting time at the Nürnberg FabLab again! Amazingly, the Sun 3/50 board works out of the box, while my trusty old 3/60 throws a memory path data test error, bits 26 and 21 at address 0x400 are stuck at 1…

                      The working Sun 3/50 board

                      Alt...The working Sun 3/50 board

                      Memory data path self test error at the first address (0x400), the value read back is 0x04200001 instead of simply 1…

                      Alt...Memory data path self test error at the first address (0x400), the value read back is 0x04200001 instead of simply 1…

                        random stranger »
                        @kyonshi@dice.camp

                        ok, after a bit of trial and error I got pkgsrc installed on my LFS system. built a small package and it works.

                        pkgsrc by default installs to a seperate /usr/pkg/bin directory.

                        I wonder if I shouldn't just change that to /usr/bin or if that's too stupid an idea.

                          Arnaud Gomes boosted

                          The Psychotic Network Ferret » 🤖
                          @nuintari@mastodon.bsd.cafe

                          pet peeve.

                          When I see people do: sudo su

                          It's sudo -s or sudo -i you dingbats!

                            Jan Schaumann »
                            @jschauma@mstdn.social

                            Advanced Programming in the Environment

                            In this class, we use as our reference platform. In addition to our shared shell server, here are some ways you can install NetBSD:

                            - put it on e.g., your laptop: netbsd.org/docs/guide/en/chap-

                            - use VirtualBox: stevens.netmeister.org/631/vir

                            - use UTM: stevens.netmeister.org/631/utm/ (Video instructions: youtu.be/hCqfmuG5Acc )

                            - use or create an AWS image: stevens.netmeister.org/615/net

                            - create your own NetBSD : netmeister.org/blog/netbsd-on-

                              Jan Schaumann »
                              @jschauma@mstdn.social

                              Advanced Programming the Environment

                              Week 1: UNIX History

                              We cover the early days at Bell Labs, USL vs BSDi, the birth of the BSDs and , and how we got from Ken Thompson playing "Space Travel" on a PDP-7 to Unix running on your phone, fridge, and TV.

                              youtu.be/3H7SQWTR6Dw

                              Scroll along through it all here: levenez.com/unix/unix.pdf

                                Jan Schaumann »
                                @jschauma@mstdn.social

                                Advanced Programming in the Environment

                                Week 1, Unix Basics

                                We write our first trivial program, which promptly segfaults and gives us a chance to explain function forward declarations and maneuvering man pages and set our default compiler flags ("-Wall -Werror -Wextra"), then proceed to write the most trivial versions of cat(1), ls(1), and even a rudimentary shell including a signal handler.

                                youtu.be/w3spRzZ8bSA

                                Slides: stevens.netmeister.org/631/01-

                                  Jan Schaumann »
                                  @jschauma@mstdn.social

                                  Advanced Programming in the Environment

                                  Week 2: File Descriptors

                                  To introduce the concept of file descriptors, let's start with a simple question: how many file descriptors can a unix process open? Finding the answer helps us introduce a few different limits that may apply across the system, for a given user, or just a process.

                                  As a fun exercise, try setting "ulimit -n 0" in your shell and see what happens. Can you explain why?

                                  youtu.be/h5A1OQjuCqk

                                  Presentation slides showing an illustration of file descriptors connected from the terminal to a single program as well as to two programs in a pipe.

Additional bullet points:
A file descriptor (or file handle) is a small, non-negative integer which identifies a file to the kernel.

Traditionally, stdin, stdout and stderr are 0, 1 and 2, respectively, but relying on magic numbers is bad practice. Use STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO instead.

                                  Alt...Presentation slides showing an illustration of file descriptors connected from the terminal to a single program as well as to two programs in a pipe. Additional bullet points: A file descriptor (or file handle) is a small, non-negative integer which identifies a file to the kernel. Traditionally, stdin, stdout and stderr are 0, 1 and 2, respectively, but relying on magic numbers is bad practice. Use STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO instead.

                                    Jan Schaumann »
                                    @jschauma@mstdn.social

                                    Advanced Programming in the Environment

                                    Week 2: open(2) and close(2)

                                    Having introduced the concept of file descriptors, let's look at what happens when we try to create a file, "create" an existing file, open an existing file, truncate a file, and look at the various other flags we can pass to open(2). We also note the perhaps surprising number of ways in which open(2) can fail and take a look at openat(2) and TOCTOU defenses.

                                    youtu.be/QnL4eYpb5Iw

                                      Jan Schaumann »
                                      @jschauma@mstdn.social

                                      Advanced Programming in the Environment

                                      Week 2: read(2)/write(2)/lseek(2)

                                      In this video lecture, we will go into the details of the read(2), write(2), and lseek(2). We'll also do a few weird things with file descriptors, and take a look at how we can ensure I/O efficiency when making these system calls.

                                      youtu.be/EUUPw8MOV_A

                                        Jan Schaumann »
                                        @jschauma@mstdn.social

                                        Advanced Programming in the Environment

                                        Week 2: File Sharing

                                        In this final video lecture segment for our week 2 materials, we take a look at what it means when multiple processes access the same files and what the implications of that are on the syscalls we know. We conclude with a look at /dev/fd on different operating systems, including , , and .

                                        youtu.be/CAbUtc86ULw

                                          Jan Schaumann »
                                          @jschauma@mstdn.social

                                          Advanced Programming in the Environment

                                          Week 3: stat(2) intro

                                          In this video lecture, we meet our new best friend, the 'struct stat'. We'll cover the stat(2) system calls and begin discussing each of the fields in the struct, often by example of the ls(1) and stat(1) commands. In this way, we begin learning more about how the Unix File System is implemented.

                                          (Note that the output of stat(1) on is different from that on .)

                                          youtu.be/veFwXrEHPsk

                                          $ ls -l file
-rw-r--r-- 1 jschauma wheel 1048576 Sep 10 20:04 file

"-rw-r-r-" from st_mode
1 st_nlink
"jschauma" from st_uid
"wheel" from st_gid
1048576 st_size
Sep 10 20:04  from st_mtime
file not from stat at all

                                          Alt...$ ls -l file -rw-r--r-- 1 jschauma wheel 1048576 Sep 10 20:04 file "-rw-r-r-" from st_mode 1 st_nlink "jschauma" from st_uid "wheel" from st_gid 1048576 st_size Sep 10 20:04 from st_mtime file not from stat at all

                                          The stat(1) utility displays information about the file pointed to by file.

$ stat -r file
16 3 0100644 1 1000 0 -1 1048576 1599768274 1599768274 1599768274 0 4096 2056 0 file

The default format displays the st_dev, st_ino, st_mode, st_nlink, st_uid,
st_gid, st_rdev, st_size, st_atime, st_mtime, st_ctime, st_birthtime,
st_blksize, st_blocks, and st_flags fields, in that order.

                                          Alt...The stat(1) utility displays information about the file pointed to by file. $ stat -r file 16 3 0100644 1 1000 0 -1 1048576 1599768274 1599768274 1599768274 0 4096 2056 0 file The default format displays the st_dev, st_ino, st_mode, st_nlink, st_uid, st_gid, st_rdev, st_size, st_atime, st_mtime, st_ctime, st_birthtime, st_blksize, st_blocks, and st_flags fields, in that order.

                                            Jan Schaumann »
                                            @jschauma@mstdn.social

                                            Advanced Programming in the Environment

                                            Week 3: UIDs and GIDs

                                            In this video lecture, we'll learn a little bit more about file ownership and the user IDs of a process (real, effective, saved) by looking at the seteuid(2) and setuid(2) system calls and experimenting with setting the setuid bits and observe the file access we gain.

                                            youtu.be/YlcF3ncTQpo

                                              Jan Schaumann »
                                              @jschauma@mstdn.social

                                              Advanced Programming in the Environment

                                              Week 3: struct stat st_mode

                                              In this video segment, we're looking at how the traditional permissions defined in the `struct stat st_mode` are applied. You want to pay particular attention to the permissions on directories and the order in which they are checked. One thing that often surprises newcomers is that to delete a file, Unix does not care about the permissions on the _file_, only on the directory it's in.

                                              youtu.be/vS6abFjN3ZY

                                              The st_mode also encodes the file access permissions (S_IRUSR, S_IWUSR,
S_IXUSR, S_IRGRP, S_IWGRP, S_IXGRP, S_IROTH, S_IWOTH, S_IXOTH). Uses of
the permissions are summarized as follows:
• To open a file, need execute permission on each directory component of the path.
• To open a file with O_RDONLY or O_RDWR, need read permission.
• To open a file with O_WRONLY or O_RDWR, need write permission.
• To use O_TRUNC, must have write permission.
• To create a new file, must have write+execute permission for the directory.
• To delete a file, need write+execute on directory, file doesn’t matter.
• To execute a file (via exec family), need execute permission.

                                              Alt...The st_mode also encodes the file access permissions (S_IRUSR, S_IWUSR, S_IXUSR, S_IRGRP, S_IWGRP, S_IXGRP, S_IROTH, S_IWOTH, S_IXOTH). Uses of the permissions are summarized as follows: • To open a file, need execute permission on each directory component of the path. • To open a file with O_RDONLY or O_RDWR, need read permission. • To open a file with O_WRONLY or O_RDWR, need write permission. • To use O_TRUNC, must have write permission. • To create a new file, must have write+execute permission for the directory. • To delete a file, need write+execute on directory, file doesn’t matter. • To execute a file (via exec family), need execute permission.

                                              Which permission set to use is determined (in order listed):
1. If effective-uid == 0, grant access
2. If effective-uid == st_uid
2.1. if appropriate user permission bit is set, grant access;
2.2. else, deny access
3. If effective-gid == st_gid
3.1.if appropriate group permission bit is set, grant access
3.2. else, deny access
4. If appropriate other permission bit is set, grant access, else deny access

                                              Alt...Which permission set to use is determined (in order listed): 1. If effective-uid == 0, grant access 2. If effective-uid == st_uid 2.1. if appropriate user permission bit is set, grant access; 2.2. else, deny access 3. If effective-gid == st_gid 3.1.if appropriate group permission bit is set, grant access 3.2. else, deny access 4. If appropriate other permission bit is set, grant access, else deny access

                                                Jan Schaumann »
                                                @jschauma@mstdn.social

                                                Advanced Programming in the Environment

                                                Week 3: chmod(2) and chown(2)

                                                Having seen a lot of examples in our previous videos of creating files, changing their ownership, changing their permissions, we now focus on the system calls that are used to implement the chmod(1) and chown(8) commands.

                                                youtu.be/5MJmCanZDyk

                                                  Jan Schaumann »
                                                  @jschauma@mstdn.social

                                                  Advanced Programming in the Environment

                                                  Week 3: umask(2)

                                                  In this video lecture, we'll take a look at what file ownership and permissions are applied when we create a new file. In the process, we'll learn about the concept of a process's "umask", and look at how the 'umask' shell built-in is implemented.

                                                  youtu.be/bRAR2bv2HSM

                                                    Jan Schaumann »
                                                    @jschauma@mstdn.social

                                                    Advanced Programming in the Environment

                                                    Week 3 (and 4, kind of): Union Mounts and Whiteout Files

                                                    One of the file types we've encountered are those of type S_IFWHT, so called "whiteout" files. But what the hell is that?? Let's illustrate! We describe the concept of union mounts and see what happens when a file in the upper layer is removed while the same file still exists in the lower layer: a whiteout file is created to cover up the lower file.

                                                    youtu.be/MkFExG9jhEE

                                                      Jan Schaumann »
                                                      @jschauma@mstdn.social

                                                      Advanced Programming in the Environment

                                                      Week 3: recap

                                                      Slides from tonight's class, summarizing the last few videos and adding a few more bits (haha, get it?) about how the umask works.

                                                      stevens.netmeister.org/631/03-

                                                        Jan Schaumann »
                                                        @jschauma@mstdn.social

                                                        Advanced Programming in the Environment

                                                        Week 4: The Unix Filesystem

                                                        This week, we'll take a closer look at the Unix Filesystem (UFS). In our first video segment, we visualize how the filesystem structures the disk and organizes files and directories. We illustrate how directory entries are created and moved around.

                                                        youtu.be/kY4JAXYyByQ

                                                          Jan Schaumann »
                                                          @jschauma@mstdn.social

                                                          Advanced Programming in the Environment

                                                          Week 4: Links

                                                          In this video lecture, we'll take a look at the system calls used to create, remove, and rename both hard- and symbolic links. We'll compare expected output against trivial implementations of the ln(1) and mv(1) commands.

                                                          youtu.be/0l8o2goJ1kc

                                                            Jan Schaumann »
                                                            @jschauma@mstdn.social

                                                            Advanced Programming in the Environment

                                                            Week 4: Directories

                                                            In this video, we take a look at how directories are created and removed, as well as how to move around the filesystem hierarchy. We also learn how directory permissions are applied, why the 'cd' command must be a shell builtin in order to work, what happens when you remove a directory you're currently in, and we revisit our simple ls(1) clone from week 1, using opendir(2) and readdir(2) to list files.

                                                            youtu.be/xZ7dNXZ58G8

                                                              Jan Schaumann »
                                                              @jschauma@mstdn.social

                                                              Advanced Programming in the Environment

                                                              Week 4: Directory Size

                                                              Let's dive deep into the structure of the directory on a traditional Unix File System and see how its size is independent of the file sizes of its entries, but dependent on the filename lengths. We'll also use hexdump(1) to cheat a bit and look at the actual directory structure on disk.

                                                              youtu.be/gY0SE-71LZA

                                                                Jan Schaumann »
                                                                @jschauma@mstdn.social

                                                                Advanced Programming in the Environment

                                                                Week 4: /etc/passwd

                                                                In this short video, we try to answer the awkward question "Mommy, where do UIDs come from?". We look at the /etc/passwd user database and identify the various fields before we look at how things can get weird.

                                                                youtu.be/fv16TWDnLYM

                                                                  Jan Schaumann »
                                                                  @jschauma@mstdn.social

                                                                  Advanced Programming in the Environment

                                                                  Week 4: getpwuid(2) and /etc/groups

                                                                  After having discussed all the account fields in /etc/passwd, we now look at the library functions used to look up that information. We learn about how primary and supplementary groups are handled as well as how the hashed passwords are stored outside of the world readable /etc/passwd file.

                                                                  youtu.be/aomkx6_aWpc

                                                                    Jan Schaumann »
                                                                    @jschauma@mstdn.social

                                                                    Advanced Programming in the Environment

                                                                    Week 4: atime, mtime, ctime

                                                                    In this video lecture, we start looking a little bit closer into what our systems think of "time", something that experts most accurately describe as a big ball of wibbly, wobbly, timey, wimey... stuff. In short, analyze how the atime, mtime, and ctimes of a file connect.

                                                                    youtu.be/ffYEEj5vnlw

                                                                      Jan Schaumann »
                                                                      @jschauma@mstdn.social

                                                                      Advanced Programming in the Environment

                                                                      Week 4: time(3) is an illusion

                                                                      Having revisited the atime, mtime, and time in our last video segment, we now have to come to terms with time(3) itself. We'll discuss managing the data structures and handling arbitrary concepts such as leap seconds, timezones, and (ugh) Daylight Savings Time. It gets silly real quick.

                                                                      youtu.be/3N2aH1vUacQ

                                                                      For a lot more time based shenanigans, see also:

                                                                      netmeister.org/blog/epoch.html

                                                                        Jan Schaumann »
                                                                        @jschauma@mstdn.social

                                                                        Advanced Programming in the Environment

                                                                        Week 5: The Unix Development Environment

                                                                        This week, we're looking at the Unix system as an effective Integrated Development Environment. This introduction outlines the different tools we will cover in subsequent videos. (You may notice it is a bit dated already in it's references to AI from back in 2020. Good thing we don't allow the use AI in this class, so you've got nothing to worry about.)

                                                                        youtu.be/QYwYLR3UD2w

                                                                          Jan Schaumann »
                                                                          @jschauma@mstdn.social

                                                                          Advanced Programming in the Environment

                                                                          Week 5: The Editor

                                                                          In this video lecture, we look at the required feature for a full-fledged programmer's editor and illustrate some of the core functionality by example of . This includes basic motion commands, setting and moving to markers, using folds, and the integration with build tools, such as the compiler, debugger, and 'make', all of which we will cover in the next videos.

                                                                          youtu.be/DdaJ87G9Kes

                                                                            Jan Schaumann »
                                                                            @jschauma@mstdn.social

                                                                            Advanced Programming in the Environment

                                                                            Week 5: ed(1) is the standard text editor

                                                                            What? You thought we could skip ed(1)? No way! It's the standard text editor. ed man! !man ed

                                                                            But understanding ed(1) also helps us understand other tools like vi(1), sed(1), and ultimately even things like diff(1) and patch(1) better.

                                                                            youtu.be/mRZsV7aMK0I

                                                                              Brennan Kenneth Brown »
                                                                              @brennan@social.lol

                                                                              Y⃒̸̷̝̜̙ͥͥͥngmar »
                                                                              @yngmar@social.tchncs.de

                                                                              @eniko This is the revenge of the lamers that showed up on IRCnet in the 90s and got kicked for asking how to run a bot 😆

                                                                                SDF boosted

                                                                                ICM »
                                                                                @icm@mastodon.sdf.org

                                                                                Back to top - More...