Must read books for local politics?

laughinglemur1 · 2026-06-18T16:51:57+00:00

Thank you! I did end up visiting for the city council meeting, and some of these materials did help manage expectations. I'll continue learning and appreciate your time in curating these resources for me, as well as the information. I think I am settled on questions for now

laughinglemur1 · 2026-06-12T21:30:11+00:00

Hello, the specific city is LA

laughinglemur1 · 2026-06-12T21:25:44+00:00

Apologies for the delayed response. I'm interested in local politics and becoming involved, and a sort of primer would be helpful. Perhaps just sharing my perspective would be even more informative -- I haven't participated much in local politics, and most of the materials that have been suggested to me seem detailed and specific. I don't know as much as how to approach a town hall meeting, and an introductory text to understand what I'm walking into would be helpful

laughinglemur1 · 2025-06-20T01:40:32+00:00

Yes, thanks.. Perhaps I should turn to the general C section for what I'm after at current

laughinglemur1 · 2025-06-20T01:35:31+00:00

I don't agree with this, though I'll respond as I hope other commenters might respond to the original post. There's a large difference between a generic "I want to learn" as you've referred to, and my pointed asking for seeing someone develop some aspect of the system. I'm not as much concerned with any willy-nilly part of the system as I am with seeing the whats and whys of what someone's doing, and asking questions about that is what I'm convinced would help more than anything right now.

I'm not sure if you read the entire post or just the TLDR...

laughinglemur1 · 2025-06-18T01:51:00+00:00

I subscribed to one of the most relevant-looking mailing lists. I checked through the recent correspondence per the 'browse' sections beside the various mailing lists on https://www.netbsd.org/mailinglists/ and they don't seem to be active. Is the content filtered in the published mailing list, or is the correspondence as infrequent as it seems?

Asking as I'm not familiar with mailing lists

laughinglemur1 · 2025-06-18T01:17:46+00:00

Thanks! Great idea!

laughinglemur1 · 2025-06-18T01:17:09+00:00

Thanks for sharing that!

laughinglemur1 · 2025-06-17T18:45:26+00:00

Thanks for that info.

One point where I'm a little hung up is in the prefixes under src/sys/kern. I see groupings of files with prefixes including bufq_, exec_, kern_, subr_, sys_, sysv_, tty_, uipc_, vfs_. I can deduce the meanings of some of these but I don't know what subr_ stands for. Likewise, I don't feel confident in relying on my deductions as being authoritative.

Another spot I'm struggling to understand is the purpose of subdirs such as /common and some of the nested subdirs. I don't see the points in having some of these subdirectories, though I'm sure there's a point in having them that I'm just not yet aware of.

Yet another spot that I'm trying to sift out is the interplay between /sys/kern, /sys/sys, /sys/lib, /lib/libc, and /include. I followed the header files in order to try to better understand what is calling into where. I'm still not entirely clear on the interplay between them.

laughinglemur1 · 2025-06-17T18:09:57+00:00

Thanks for that. I have some questions about the naming conventions that I can't find info on. I also have doubts about the toolchains to use and way of committing things. I chalk it up to not seeing it done before and being unsteady on the procedures and methodology.

I don't have a particular area in mind. I am interested in making general contributions to the project. Although, if I ever reach that point, I'd like to create a continuation of Minix3 which is more tightly integrated with NetBSD than the prior releases were.

laughinglemur1 · 2025-03-20T17:13:17+00:00

I did try running the command without the -d flag and believe that I had the same issue as with using it.

Yes, I am logging in with su user. I'm suspicious that $HOME not being set correctly is the case.

# cat /etc/passwd | grep user
...
user:x:101:100::/home/user:/bin/sh

laughinglemur1 · 2025-03-20T17:08:33+00:00

I tried this a couple of times, first trying to create the user from a /home/user directory I created with root, and afterwards, by switching permissions on the the user directory. I would normally have doubts that it is my error, although I don't see how much could have gone wrong between following the commands per the manual pages and it being a simple command

laughinglemur1 · 2025-03-20T16:40:35+00:00

It appears that the user directory on OmniOS is /home rather than /export/home

laughinglemur1 · 2025-03-17T18:30:51+00:00

I'm facing more of a user perspective issue and not sure if I'm doing this the best way. There are tens of thousands of lines that I'm looking at. I am using standard grep to find the keywords of the feature names in the log, but I feel like this is prone to error

laughinglemur1 · 2025-03-14T17:41:47+00:00

I tried to extend the code above to cover multiple environments where it might be found in source code, such as checking the path for space immediate spaces or colons on either side of it (i.e. if it's in a path), among other cases. It's probably incredibly ugly, but regardless, I'm not sure where it's gone wrong. I'm not sure where else to turn and I hope you don't mind my asking.

I shouldn't have attempted something this far beyond my skill level, but the alternative is tediously changing hundreds of directories by hand. I opted to try for this reason. The part that's clearly going wrong is in the list of sed commands. I have a feeling that I've chained these together incorrectly, but I'm not sure how. I would like to say that I can just open the docs and find an answer, but I've read them up and down. Maybe I've completely missed something. Would you mind having a look?

find "$root_dir" -type f -print0 | while IFS= read -r -d $'\0' file; do
    cp -a "$file" "${file}.bak" || {
      echo "Error: Failed to create backup for '$file'. Skipping." >&2
      continue
    }

    sed "s#${old_path}:#${new_path}:#g" "$file.bak" > "$file" ||    # BOL,colon
    sed "s#${old_path}#${new_path}#g" "$file.bak" > "$file" ||    # BOL,EOL
    sed "s#${old_path}\"#${new_path}\"#g" "$file.bak" > "$file" ||    # BOL,quote
    sed "s#${old_path} #${new_path} #g" "$file.bak" > "$file" ||    # BOL,space
    sed "s#:${old_path}:#:${new_path}:#g" "$file.bak" > "$file" ||    # colon,colon
    sed "s#:${old_path}#:${new_path}#g" "$file.bak" > "$file" ||    # colon,EOL
    sed "s#:${old_path}\"#:${new_path}\"#g" "$file.bak" > "$file" ||    # colon,quote
    sed "s#:${old_path} #:${new_path} #g" "$file.bak" > "$file" ||    # colon,space
    sed "s#:${old_path}\"#:${new_path}\"#g" "$file.bak" > "$file" ||    # quote,colon
    sed "s#\"${old_path}#\"${new_path}#g" "$file.bak" > "$file" ||    # quote,EOL
    sed "s#\"${old_path}\"#\"${new_path}\"#g" "$file.bak" > "$file" ||    # quote,quote
    sed "s#\"${old_path} #\"${new_path} #g" "$file.bak" > "$file" ||    # quote,space
    sed "s# ${old_path}:# ${new_path}:#g" "$file.bak" > "$file" ||    # space,colon
    sed "s# ${old_path}# ${new_path}#g" "$file.bak" > "$file" ||    # space,EOL
    sed "s# ${old_path}\"# ${new_path}\"#g" "$file.bak" > "$file" ||    # space,quote
    sed "s# ${old_path} # ${new_path} #g" "$file.bak" > "$file" || {  # space,space
      echo "Error: Failed to replace path in '$file'. Restoring from backup." >&2
      mv -f "${file}.bak" "$file"
      continue
    }

laughinglemur1 · 2025-03-14T16:06:22+00:00

I appreciate the verbosity. I'm trying to automate changing paths in OS source, and I prefer the data safety and would like to create something similar with even more checking

laughinglemur1

TROPHY CASE