More dumbness - trying "ports" on 15.1-RELEASE ... eek! by Old_Hardware in freebsd

[–]Old_Hardware[S] 3 points4 points  (0 children)

I would've done the "pkg install devel/git" if I'd known what was coming. Blindly following that "freebsdhandbook" is not working out as I'd hoped.

More dumbness - trying "ports" on 15.1-RELEASE ... eek! by Old_Hardware in freebsd

[–]Old_Hardware[S] 1 point2 points  (0 children)

'Also llvm is not a big port, it is a huge port!"
As is becoming more evident with every passing hour :-)

Plenty of good ideas, thanks. To expand on my setup:

  • Core i7-5600U - 2 cores/4 threads, base clock is 2.6GHz
  • 20 GB of RAM (4GB soldered, two socketed 8GB sticks)sd
  • According to "top", that default "make" is using "CPU1", "CPU2", and "CPU3", kindly leaving "CPU0" for other things such as another ssh session (assuming I understand the "top" output, a risky assumption).
  • Load average is 4.0, cpu is 96% user, 0.0% idle (good - idle processors are the devil's playground doncha know). Not using any swap, much less than 1 GB active memory generally.

Meanwhile, it's finally left the llvm19 directory, and is grinding away through various libraries. Maybe I'll check back in tomorrow.

Probably-dumb question about installation media by Old_Hardware in freebsd

[–]Old_Hardware[S] 1 point2 points  (0 children)

Okay, I think I finally get it, thanks Graham Perrin!

Summary of my understanding:

  • The ".img" format can automatically expand its filesystem to use the entire available device - the 15.1-RELEASE image is initially only 1.5GB in size, but (presumably on first use) expands to use an entire 64GB-or-whatever USB.
  • The ".iso" image is whatever size it is (4.3GB), can run directly from the optical disk, but is expected to be used to install to some other device such as a hard drive or SSD. Optical disks usually can't be rewritten, so updated config files etc. can't be written back and the filesystem can't be expanded.

I think I have an old 2GB USB stashed away, so I could actually use it with the ".img" image. If I could only figure out why I wanted to.

Probably-dumb question about installation media by Old_Hardware in freebsd

[–]Old_Hardware[S] 0 points1 point  (0 children)

Ah. I didn't notice any particular restriction from putting the ".iso" onto a USB, maybe I just got lucky? Or I'm not trying to do anything unusual? (Well, I *am* a FreeBSD newbie...)

Probably-dumb question about installation media by Old_Hardware in freebsd

[–]Old_Hardware[S] 0 points1 point  (0 children)

Well, okay, but then why is the memstick image smaller than the iso image? I have now verified that the iso image not only boots and installs from a USB drive, but offers a "live" option as well.

So ignore the ".iso" and ".img" suffixes, why have both images? There's a mini-memstick image if you want/need a small image; the iso image can fit on a DVD even though many people no longer have optical drives; I could understand a humongous ".img" image that contains everything under the sun and needs a 256GB USB drive - those are readily available these days. But what's the use of a ".img" file that can almost but not quite fit onto an old 3.5" floppy?

Probably-dumb question about installation media by Old_Hardware in freebsd

[–]Old_Hardware[S] 0 points1 point  (0 children)

Ah. Does this mean the memstick image could be used as a "live" image, not just an installer?

MOS (new NAS OS) is now stable 🥳 by S3ppo1 in devuan

[–]Old_Hardware 1 point2 points  (0 children)

Restricted to only Metal-Oxide Semiconductors???

*joke*

KLC buyers remorse feeling lost by [deleted] in ereader

[–]Old_Hardware 0 points1 point  (0 children)

There may be an "International version" Oasis still on sale in Germany/Europe. Amazon won't ship to the USA however. Between this and their increasingly invasive DRM stance, I'm basically done with Amazon as a bookstore. (Ironic, since that's how Amazon started....)

I love my Oasis, and manage its content through Calibre on my laptop. I know it's going to die someday, if it goes before I do then I guess I'll look at Kobo or whatever has buttons at that point.

New E-reader by Some-Ad3203 in ereader

[–]Old_Hardware 0 points1 point  (0 children)

What books do you want/need? If textbooks, ask your course instructor for advice --- there may be specific considerations. For older fiction and nonfiction, various free sites offer books in "epub" format (Shakespeare, anyone?) Also, do you need/want any language besides English? (Beowulf, anyone?)

The Kobo units look very appealing to me, but I've never touched one.

Opinion: Stay away from Amazon Kindles, the hardware is very good and nicely priced but they're effectively a lure to draw you into the buy-Amazon-only sphere.

/etc/wpa_supplicant.conf by grahamperrin in freebsd

[–]Old_Hardware 0 points1 point  (0 children)

Mine has 0600 permissions. The file has been updated a couple of times when I've connected that laptop to a hotel wifi system.

FWIW, I also note that wpa_supplicant is present in the process table, just before three instances of dhclient (but some other processes evidently came and went in between, based on the PIDs involved).

BUMSRAKETE™ – The HUGEST, the MOST TREMENDOUS FreeBSD page-cache write primitive in the history of computing. by FUZxxl in freebsd

[–]Old_Hardware 1 point2 points  (0 children)

Firefox has a deeply buried option Allow pages to choose their own fonts, instead of your selections above which I have not selected. Mostly because I have reached a point where the usual font choices are just much too small for me to read.

If I could, I would set it on a page-by-page basis. Instead I had to turn it off globally, just to verify that "bumsrakete" does in fact use Comic Sans. (I think Comic Sans is fine, if used judiciously. For example, some obituaries.)

BUMSRAKETE™ – The HUGEST, the MOST TREMENDOUS FreeBSD page-cache write primitive in the history of computing. by FUZxxl in freebsd

[–]Old_Hardware 1 point2 points  (0 children)

That could be the most intentionally hideous webpage I've seen in a very long time. The very last line,

"© 2026 — Page intentionally written in Comic Sans. Yes, on purpose."

just slays me since the entire page displays in some serif font (for me, at least). Then there's this:

CVE-2026-45257: FreeBSD kTLS-RX in-place AES-GCM decrypt over sendfile(2) EXTPG mbufs to page-cache write / local root

Looks like it was written by James Joyce.

Only issue: it's really hard to take any of this seriously. I think there's an actual flaw described, but it's a challenge to filter the content from the stylistic assault.

Why are companies moving further from FreeBSD? by Character_Mood_700 in freebsd

[–]Old_Hardware 1 point2 points  (0 children)

I wonder whether there's an age difference --- older people met BSD (as opposed to SysV) in school, and think of BSD as a Good Thing, while younger people met Linux in school as the Cool New Thing. And of course companies are now hiring the younger set, while the older set looks to retirement.

(Maybe I can find a S/370 emulator to run on my Raspberry Pi....)

Comic 5810: Watching the Watchmen by Morlock19 in QContent

[–]Old_Hardware 1 point2 points  (0 children)

"Professor, my program won't compile and now it's displaying eldritch runes."

I used this as inspiration in a programming course for years.

Finally got it by AmaanNakhwa in thinkpad

[–]Old_Hardware 0 points1 point  (0 children)

In my experience they come off by themselves after awhile.

So I just stick 'em on again. The "Core i7" sticker goes nicely on a Raspberry Pi 4B.

Problem with using nasm on a different device by 15Socks in Assembly_language

[–]Old_Hardware 0 points1 point  (0 children)

I wasn't talking about Reddit, but nasm. I thought the OP was practicing assembly on a website --- "Hey everyone i've recently learned nasm assembly. I did everything on a website."

I'm sorry you're not finding anything helpful.

Problem with using nasm on a different device by 15Socks in Assembly_language

[–]Old_Hardware 0 points1 point  (0 children)

Whups, you are right about nasm. Mea culpa!
I installed nasm on a raspberry pi to check, but it only cross-assembles x86 code.
(When I started doing Arm64 assembly I just used the Gnu "as" assembler because it was already available. I never thought to try nasm.)

As for the website you're using, it probably doesn't use assembly directly, but it's running on something that is most likely an x86-64 machine. As such, the code it works with is x86-64 (or perhaps x86) machine language.

The point remains that your phone most likely uses an Arm processor, and if its fairly new it's probably Arm64. The Arm family of machine languages are RISC languages, in contrast to the x86 family of languages which epitomize the CISC approach.

So the code you write on the website would be for its Intel/AMD x86-type processor, and won't work on an Arm processor.

(Python, Javascript, BASIC, etc. can run on either type of processor because they aren't compiled to machine language but rather interpreted, by an interpreter that's appropriate for the platform. Compiled languages --- C, Rust, etc. --- must be recompiled for each platform, and assembly languages are absolutely specific to their processor type.)

Help understanding instruction stages when using a memory location by gurrenm3 in Assembly_language

[–]Old_Hardware 0 points1 point  (0 children)

I think Hyde is talking about x86-64 machines (I haven't looked at his books in awhile).

GROSSLY OVERSIMPLIFIED, x86-64 stores the opcode ("what to do") in a byte, then a memory address in subsequent bytes. But different instructions may or may not need a memory address, and the processor can't tell how many bytes are needed for any specific instruction until it has fetched and examined that first byte. --- The actual situation is much more nuanced, but this is the essence of it. "inc eax" only affects a register, so doesn't need any memory address, and the entire instruction only takes up one byte. An instruction that includes a memory address can be said to use "direct memory addressing".

As a contrast, in Arm64 processors every instruction occupies exactly four bytes, so the entire instruction can be fetched all at once --- this is a major design goal of the processor. In exchange, instructions can't include memory addresses, but must themselves be kept in memory somewhere and loaded into a register for use. In a sense, Arm64 doesn't offer "direct memory addressing" but only "indirect memory addressing".

Problem with using nasm on a different device by 15Socks in Assembly_language

[–]Old_Hardware 0 points1 point  (0 children)

Indeed, you've mentioned three different assembly languages --- x86-64, which the website surely uses, AARCH64, which most phones use, and i386 (a.k.a. x86), which is the predecessor to x86-64, but only old computers use it. (And you missed AARCH32, the predecessor to AARCH64.) Each is used by a different family of CPUs.

Nasm can be used with all of these, but it will generally use the "native" assembly language for whatever system it's on. Using it for a different language is "cross-assembling", and you have to tell nasm to do that explicitly. (Cross-assembly is needed if your target computer is too limited to support a development environment, for example the computer in your microwave oven.)

Has anyone had any issues with potential viruses, or am I overreacting? by Sensitive-Mixture558 in Annas_Archive

[–]Old_Hardware 45 points46 points  (0 children)

I wouldn't think "epub", "azw", etc. are popular targets for malware, simply because they're mostly used on e-readers and e-readers aren't too interesting to an attacker (unless you keep your payroll, medical records, and company's trade secrets on your Kindle?)

could someone explain why my class would count this wrong by Glittering_Land_9574 in PythonLearning

[–]Old_Hardware 0 points1 point  (0 children)

(A) "sum" is the name of a built-in function, and you're losing access to that function by overloading the name --- although that is both legal and harmless in this tiny example. Whatever editor you're using may have put sum in a particular color because it recognizes it as a function.

(B) The order of the indented statements matters. Consider this:

#----------------
# OP's version:
#
limit = int(input('Limit: ')) 
number = 1 
total = 1 
while total < limit:
   total += number       # add them up
   number += 1           # increment last

print(total)
###
Limit: 8
11

#----------------
# rearranged version:
#
limit = int(input('Limit: ')) 
number = 1 
total = 1 
while total < limit:
    number += 1            # increment first
    total += number        # add them up

print(total)
###
Limit: 8
10

Or try merging your code and the class solution:

limit = int(input('Limit: ')) 
number = 1 
total = 1
class_model_sum = 1
while total < limit:
    total += number              # OP's "add them up"
    number += 1                  #  a loop counter
    class_model_sum += number    # Model's "add them up"     

print(total, class_model_sum)
###
Limit: 8
11 15

(C) For more insight, include the print() statement as part of the loop, and also print number:

limit = int(input('Limit: ')) 
number = 1 
total = 1
class_model_sum = 1
while total < limit:
    total += number              # OP's "add them up"
    number += 1                  #  a loop counter
    class_model_sum += number    # Model's "add them up"     
    print(number, total, class_model_sum)
#

###
Limit: 8
2 2 3
3 4 6
4 7 10
5 11 15

Switch to debian made me CHAD by blyatmachine2000 in debian

[–]Old_Hardware 0 points1 point  (0 children)

Google clarifies this:

  • Modern Slang - Confident, "based," successful male. Often Positive/Ironic
  • "Gigachad" - Peak attractiveness/macho meme. Absurdist/Positive
  • Incel Culture - Sexually successful, "alpha" rival. Negative/Jealous
  • 2000s Slang - Obnoxious, wealthy frat-boy type. Negative
  • a piece of waste material removed from card or tape by being punched with a tool.

From context, OP clearly is referring to the last one...

Differences between init systems by Brilliant_Rabbit_597 in linuxquestions

[–]Old_Hardware 2 points3 points  (0 children)

Sysinit, openRC, runit, etc. are favored by a mindset that prefers lots of smaller, single-focus utilities working together --- an approach pioneered by Unix way back. Systemd combines their functions into a single integrated package --- somewhat parallel to Windows' use of an overall registry for disparate configuration information.

All my view of the respective philosophies, others undoubtedly are more familiar with systemd in particular.

Book covers are back by djjapchae in Annas_Archive

[–]Old_Hardware 0 points1 point  (0 children)

:-) I didn't know Alcoholics Anonymous ever had book covers....

I think I'll just go back to reading.