This question pertains to Tuxedo laptops (and possibly Clevo, Uniwill, or Tongfang laptops, which Tuxedo systems appear to be based on). Tuxedo provides official support for Windows and Linux, but I'm particularly interested in BSD. For reference, my specific laptop model is the Tuxedo Gemini 15 Gen 2. The issue I'm experiencing is that the fans are controlled by the embedded controller (EC), which by default does not spin the fans adequately. Updating the EC firmware hasn't resolved the problem. As a result, the laptop runs hot, and I'm concerned that prolonged operation under these conditions may degrade the hardware. - The EC does not have pre-programmed fan profiles that the software selects. - The driver writes a desired fan speed directly as an 8-bit integer (255 being full speed and 0 being off). - On Linux, a daemon communicates with the driver via IOCTL, and the driver communicates with the EC through ACPI. What options are available to enable proper fan control on BSD operating systems (specifically OpenBSD or FreeBSD) without having to write my own driver?

I have a MacBook Retina 12" (2017) machine that unfortunately has developed an error with the power system that shows up in Apple Diagnostics and result in the machine being severely throttled down under MacOS 12 which is the latest the machine can run. I have given up upon trying to get MacOS not throttle anyway. I have tried to install Ubuntu 25.04 which works well with an external USB keyboard and mouse, but the out of the box experience is not working well with the builtin trackpad and keyboard, and I could not locate any easy instructions to fix it. Some poking around indicated that the devices were present, but apparently not wired up correctly. Question is: Is there any version of Linux or a *BSD variant, that works well without any non-trivial post-install tinkering for this particular machine?

In Solaris, I believe that you can assign privileges to users, and in Linux you can assign capabilities to executable files. Does some or all BSD flavors have privileges or capabilities, or something of this nature? Or do they follow the "all or nothing" approach where the root user have full privileges while the other users have very few privileges?

I have an old laptop which I am trying to install OpenStep 4.2 with Patch 3 pack (Which supports over 8GB and has a VESA driver) on to a 2003 laptop which is a 32-bit pentium 4 with 512MB RAM and a ICH4M IDE adapter hard drive controller which is backwards compatible with the PIIX4 controller driver (I've hex edited the PCI identifier strings for PIIX4 and changed them to my ICH4M which works). I had to use Virtual Box to create a hard disk image as my laptop does not have floppy disks to read drivers before reading of the CD-ROM. I managed to create 2.88MB bootable image on VirtualBox and then boot the floppy image of one of the GRUB frameworks that allows booting of disk images or .iso's (I forgot what one it was). This still could not detect the writeable DVD drive and boot the OpenStep CD-ROM. The Open Step Virtual Box image is a 512MB flat image and I've managed to **/bin/dd** to my 40GB hard drive with C/H/S 16,383/16/63 which from research is LBA and the driver uses IDE command **IDENTIFY** to read the hard drive size. **The question is how do I manually edit the MBR so that it shows up as one 512MB partition on the HDD?** Currently at the moment nothing is showing up. I have access to Lubuntu which when you use the Partition Manage it just shows a empty drive. The Open Step image kind of works at the moment the IDE driver is having trouble as it does not detect my DVD-ROM drive (Which is ok for now). But I want to be able to create a DOS/FAT partition on the drive so I can transfer files between another OS that I want to install on the HDD. No Nextstep, Openstep tags. --- In Response to user Marcus Müller who posted comments. I have used the page you mentioned to create a bootable CD which is how I managed to make a custom 2.88MB disk image that I can boot of USB using the GRUB floppy disk image booter. The main problem seems to be the EIDE.config driver (V3.337 which supports PIIX IDE hardware, the ICH4M is backwards compatible with PIIX IDE hardware as per ICH4M IDE documentation manual) seems to keep showing a error.

`
PCI bus support enabled
PnP: Plug and Play support enabled
PnP: Plug and Play BIOS present
PnP: read port 0x0, max csn 0
ISA/EISA bus support enabled
ISA bus
DriverKit version 420
BusLogic Board not found at port 0x330
Registering: PS2Controller
Registering: PCKeyboard0
Registering: PCMCIA0
PCI bus support enabled
Registering: PCI0
Registering: EISA0
hc0: device detected at port 0x1f0 irq 14
hc0: drive 0, type 55, using geometry from INT table.
hc0: WARNING: using disk geomtry for drive 0.
hc0: Checking for ATA drive 0...
hc0: drive 0, type 55, using geometry from INT table.
hc0: WARNING: using BIOS geometry for drive 0.
hc0: Resetting drives..
Registering: hc0
hd0: 1024 cylinders, 255 heads, 63 spt
hd0: using single sector transfers.
Registering: hd0
hc0: ATA command 20 failed. Retrying...	; 0x20 READ_SECTORS
hc0: ATA Command: error=0x1 secCnt=0x1 secNum=0x1 cyl=0xeb14 drhd=0xe0 status=0x0
hc0: Resetting drives..
hc0: ATA command 20 failed. Retrying...
hc0: ATA Command: error=0x1 secCnt=0x1 secNum=0x1 cyl=0xeb14 drhd=0xe0 status=0x0
hc0: Resetting drives..
hc0: ATA command 20 failed. Retrying...
hc0: ATA Command: error=0x1 secCnt=0x1 secNum=0x1 cyl=0xeb14 drhd=0xe0 status=0x0
hc0: Resetting drives..

` So I'm wondering if this conflicting error with HD image as the image I created on Virtual Box says the HD is only 512MB but the HD is saying to the controller it's 60GB. So I was wanting help with writing to the MBR that the first partition will only be the first 512MB of the HDD and that the rest is available. The EIDE/ATAPI driver can not detect my DVD ROM so can't read the CD otherwise I would install of the CD-ROM.

This is on TrueNAS 13.0U6.3 (FreeBSD 13.1-RELEASE-p9) I had a disk in my ZFS pool die. I replaced it, but I updated TrueNAS (Core) first - I think I was on U6.0 or U6.1 before the update. When I try to replace the dead disk in my pool with the fresh one, what comes up to replace the dead disk with is multipath/disk1. $ gmultipath list shows this:

Type: AUTOMATIC
Mode: Active/Passive
UUID: 472fbec0-b03b-11ef-9225-eb3c2b011256
State: OPTIMAL
Providers:
1. Name: multipath/disk1
   Mediasize: 2000398933504 (1.8T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da3
   Mediasize: 2000398934016 (1.8T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da7
   Mediasize: 2000398934016 (1.8T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

I know I didn't explicitly create a multipath disk. I've done a bit of research on it and I don't think it was enabled before - so I'd like to disable/delete it if it's possible to do so safely. From what I can tell, the multipath device disk1 just contains da3 and da7, neither of which are in my zpool right now (but either of which I'd like to use to replace the now-dead disk). $ sudo gmultipath remove da3 multipath/disk1 just results in gmultipath: Device da3 not found. I've tried da7 in place of da3, and disk1 in place of multipath/disk1, with the same result. Both da3 and da7 show up in /dev. What am I doing wrong? $ gmultipath status

Name   Status  Components
multipath/disk1  OPTIMAL  da3 (ACTIVE)
                          da7 (PASSIVE)

$ glabel status

Name  Status  Components
gptid/ba57595c-ee74-11ec-b51b-399e00f59ed1     N/A  da1p2
gptid/d0b76aad-bfbd-11ec-996d-4d60e9b1c6c6     N/A  da0p1
gptid/ba4d8354-ee74-11ec-b51b-399e00f59ed1     N/A  da6p2
gptid/ba1ee75b-ee74-11ec-b51b-399e00f59ed1     N/A  da4p2
gptid/ba11edb8-ee74-11ec-b51b-399e00f59ed1     N/A  da2p2
gptid/8968c667-48aa-11ef-b8e7-f5ee91c5a64b     N/A  da5p2
gptid/ba05228b-ee74-11ec-b51b-399e00f59ed1     N/A  da8p2
gptid/b9bc5150-ee74-11ec-b51b-399e00f59ed1     N/A  da9p2
gptid/b9cf5ec0-ee74-11ec-b51b-399e00f59ed1     N/A  da1p1

In GNU tar (i.e. gtar), the --exclude option with a glob only matches the subdirectories, but not the directory itself. For example, --exclude test-tar/a/b/* would exclude anything inside of b, but not b itself. However, bsdtar is excluding the directory itself as well. My question is how do I make bsdtar act the same as GNU in this regard? Here is an example script the demonstrates the problem: #!/usr/bin/env bash echo -e "\nGiven an archive that looks like this:" bsdtar -tf test.tgz echo -e "\nExtract the archive excluding test-tar/a/b/* using gtar" rm -rf test-tar gtar -xzf test.tgz --exclude 'test-tar/a/b/*' file test-tar/a/b file test-tar/a/b/B.txt echo -e "\nExtract the archive excluding test-tar/a/b/* using bsdtar" rm -rf test-tar bsdtar -xzf test.tgz --exclude 'test-tar/a/b/*' file test-tar/a/b file test-tar/a/b/B.txt This outputs: Given an archive that looks like this: test-tar/ test-tar/a/ test-tar/a/A.txt test-tar/a/b/ test-tar/a/b/B.txt Extract the archive excluding test-tar/a/b/* using gtar test-tar/a/b: directory test-tar/a/b/B.txt: cannot open `test-tar/a/b/B.txt' (No such file or directory) Extract the archive excluding test-tar/a/b/* using bsdtar test-tar/a/b: cannot open `test-tar/a/b' (No such file or directory) test-tar/a/b/B.txt: cannot open `test-tar/a/b/B.txt' (No such file or directory) My versions are tar (GNU tar) 1.29 and bsdtar 3.3.2.

I am trying to build an ARM64 version of the FreeBSD kernel that has Realtek wireless drivers enabled.  I absolutely have to customize the kernel options, as some of the drivers do not allow boot time enabling. 0. I am on WSL 2 using Ubuntu to attempt to make/build the files. 1. First I cloned the repository.

https://github.com/freebsd/freebsd-src.git 

2. Next I cd’ed into the directory called freebsd-src…. 3. Then I attempted to make just the base version doing this:

make buildkernel=GENERIC

Then I get this error:

Makefile:122: *** missing separator.  Stop.

I have read other posts that mention it being an indention issue / expecting tabs but getting spaces, but the directory does not (in my view) have the correct files to change the ruleset.  It also does not have any configure / autoconf files.  What could fix my issue?

In FreeBSD you get access to a geli-encrypted partition by: geli attach -k /root/ada1.key /dev/ada1 Which then opens a password prompt. Is there a way to get the password displayed while it is entered?

BSD cp:

-a    Archive mode.  Same as -RpP options. Preserves structure and
           attributes of files but not directory structure.

     -P    No symbolic links are followed.  This is the default if the -R
           option is specified.

     -R    If source_file designates a directory, cp copies the directory and
           the entire subtree connected at that point.  If the source_file
           ends in a /, the contents of the directory are copied rather than
           the directory itself.  This option also causes symbolic links to be
           copied, rather than indirected through, and for cp to create
           special files rather than copying them as normal files.  Created
           directories have the same mode as the corresponding source
           directory, unmodified by the process' umask.

     -p    Cause cp to preserve the following attributes of each source file
           in the copy: modification time, access time, file flags, file mode,
           user ID, and group ID, as allowed by permissions.  Access Control
           Lists (ACLs) and Extended Attributes (EAs), including resource
           forks, will also be preserved.

           If the user ID and group ID cannot be preserved, no error message
           is displayed and the exit value is not altered.

           If the source file has its set-user-ID bit on and the user ID
           cannot be preserved, the set-user-ID bit is not preserved in the
           copy's permissions.  If the source file has its set-group-ID bit on
           and the group ID cannot be preserved, the set-group-ID bit is not
           preserved in the copy's permissions.  If the source file has both
           its set-user-ID and set-group-ID bits on, and either the user ID or
           group ID cannot be preserved, neither the set-user-ID nor set-
           group-ID bits are preserved in the copy's permissions.

GNU cp:

-a, --archive
              same as -dR --preserve=all

       -d     same as --no-dereference --preserve=links

       -P, --no-dereference
              never follow symbolic links in SOURCE

       -R, -r, --recursive
              copy directories recursively

       --preserve[=ATTR_LIST]
              preserve the specified attributes

- Is there a difference between BSD and GNU cp -a in practice? - Is there a way to cp non-recursively if the -a option is already used, that is, to overwrite its -R part?

What might be a reason that BSD cp and find don't "like" a trailing slash for directory names?

|     |            cp            |            mv            |
|-----|--------------------------|--------------------------|
|     | # to copy dir1/ contents |                          |
|     | cp -a dir1/* dir2/       | # to move dir1/ contents |
| GNU |                          | mv dir1/* dir2/          |
|     | # to copy dir1/ itself   |                          |
|     | cp -a dir1/ dir2/        | # to move dir1/ itself   |
|-----|--------------------------| mv dir1/ dir2/           |
|     | # to copy dir1/ contents | # mv dir1 dir2/ works    |
|     | cp -a dir1/ dir2/        | # same, but I don't      |
| BSD |                          | # consider this syntax   |
|     | # to copy dir1/ itself   | # really correct[^1]     |
|     | cp -a dir dir2/          |                          |

A similar issue with BSD find. It adds a trailing slash after the source path automatically, and so, if, for the sake of consistency\[\^1\], you already added it manually, as in find ./ -type f, the first / will be replaced with // instead. Though it doesn't break anything (at least, until you need to parse it), it looks ugly:

.//file1
.//file2
.//dir1/file3
.//dir2/file4

\[\^1\]: Because the root directory in Unix and Unix-like operating systems is /, I consider a trailing / to be not an excessive or optional but instead a mandatory (though its omission is often forgiven by the tools we use) part of directory names, and so I always refer to them like /usr/bin/ and not /usr/bin (and to refer to their contents, /usr/bin/*).

I downloaded GhostBSD Live CD but it is asking for an input and a password on boot. Live CDs usually don't need those. I could not find an answer in the GhostBSD Handbook.

I'm creating a CLI utility which is aimed at *nix OS:es. Let's call it 'Super CLI Project'. Looking at the latest POSIX Issue 7, 2018 edition - https://pubs.opengroup.org/onlinepubs/9699919799/ - Utility Conventions - The section shows an example with underscores like this -> utility_name[-a]... which I could interpret as that my util should be named super_cli_project, by convention (with underscores as separator). However, POSIX does not say this explicitly. A quick 'ls' in my /usr/bin/ shows that most utils in my OS (Ubuntu) that consists of several words uses a hyphen instead of an underscore. That implies that my util should be named 'super-cli-project' instead. So, what is really the preferred naming convention here? Note: There are a few discussions regarding FILENAMES in general for this topic - but not for the naming conventions of *nix CLI utils themselves.

Some folders on macOS have custom icons that are stored in a file named Icon?, where the ? is actually a CR character, and only prints as "?" in most cases (in Terminal and Finder). But when printing such a file name in hex in Terminal, you'll get:

$ ls -l1 Icon* | xxd
00000000: 4963 6f6e 0d0a         Icon..

The 0d is the CR at the end of the name, and the 0a is the LF that's printed by ls at the end of each line. Now, I like to find such files, using find. I'd think that this would be the way: find -E . -iregex '.*/Icon\x0d' Nor does: find -E . -iregex '.*/Icon\r' However, this won't find it. But this finds it (using . as a whildcard char): find -E . -iregex '.*/Icon.' But something is wrong with looking for hex chars in general, because this doesn't work either: find -E . -iregex ".*/\x49con." \x49 is the code for I, so this should work. So, if you want to try this yourself, take _any_ file and try to find it using the find command with the -regex option and specifying at least one character in hex, e.g. looking for the file named 'a' with the regex \x61 or whatever is correct. Can you accomplish it? Note, on SO, where I had asked first, someone suggester to use this form: find -E . -iregex $'.*/Icon\r' That does indeed work, but it's not really what I want, because I use construct this command in a program where I let the user enter a regex pattern and then apply a regex function to check if a file name matches the pattern. I like to use the very same pattern when invoking the find command, and therefore I'd prefer it if I could use the very same pattern in both places. Using the $'…' wrapping might change the interpretation of regex patterns (not sure if that'll actually cause problems), so I rather would like to figure out why I cannot use the \x.. notation in the command, because according to man find and man re_format this should work.

I know about Linux terminal. I can also issue many advanced commands over terminal. But one simple concept is not clear to me. What is terminal and how does it work? I know about hardware which consists of CPU, RAM, HARD DISK and so on. I know about kernel which is basically the core of the operating system. I know about software which sits on the top of kernel. And I know about users. And I know that user uses either terminal or GUI to give instructions to the software.(or kernel?) Now please explain these concepts of terminal and shell. **Graphical explanation and simple non-technical words are preferable.**

Unix iMac shell terminal sed -i 's/original/new/g' maths.tx Message returned: sed: -i may not be used with stdin

It is well known that OpenBSD disables hyper-threading by default . However, htop shows 16 CPUs: 8 online and 8 offline, which takes extra space on the screen and is not very informative. Moreover, sysctl also sees 16 logical CPUs. This doesn't make sense to me: with hyperthreading disabled, it's an 8-core 8-thread processor, so I should see 8 physical/logical CPUs.

$ sysctl hw
hw.machine=amd64
hw.model=AMD Ryzen 7 5800H with Radeon Graphics
hw.ncpu=16
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=sd0:6d1abdce154d2fc8
hw.diskcount=1
hw.sensors.cpu0.frequency0=3900000000.00 Hz
hw.sensors.cpu2.frequency0=3900000000.00 Hz
hw.sensors.cpu4.frequency0=3900000000.00 Hz
hw.sensors.cpu6.frequency0=3900000000.00 Hz
hw.sensors.cpu8.frequency0=3900000000.00 Hz
hw.sensors.cpu10.frequency0=3900000000.00 Hz
hw.sensors.cpu12.frequency0=3900000000.00 Hz
hw.sensors.cpu14.frequency0=3900000000.00 Hz
hw.sensors.ksmn0.temp0=83.12 degC (Tctl)
hw.sensors.it0.temp0=83.00 degC
hw.sensors.it0.temp1=49.00 degC
hw.sensors.it0.temp2=200.00 degC
hw.sensors.it0.fan0=0 RPM
hw.sensors.it0.fan1=3835 RPM
hw.sensors.it0.fan2=2986 RPM
hw.sensors.it0.volt0=1.74 VDC (VCORE_A)
hw.sensors.it0.volt1=1.62 VDC (VCORE_B)
hw.sensors.it0.volt2=2.67 VDC (+3.3V)
hw.sensors.it0.volt3=3.71 VDC (+5V)
hw.sensors.it0.volt4=10.69 VDC (+12V)
hw.sensors.it0.volt5=-3.24 VDC (-12V)
hw.sensors.it0.volt6=0.57 VDC (-5V)
hw.sensors.it0.volt7=3.68 VDC (+5VSB)
hw.sensors.it0.volt8=2.16 VDC (VBAT)
hw.cpuspeed=3200
hw.setperf=100
hw.vendor=AZW
hw.product=SER
hw.version=Default string
hw.serialno=A58003LH80340
hw.uuid=00020003-0004-0005-0006-000700080009
hw.physmem=13840232448
hw.usermem=13840216064
hw.ncpufound=16
hw.allowpowerdown=1
hw.perfpolicy=manual
hw.smt=0
hw.ncpuonline=8
hw.power=1
hw.ucomnames=

How do I disable logical processors, so that each "CPU" is a physical processor?

On old 43BSD... netstat -f unix Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr 801ca38c dgram 0 0 8008b5c0 0 0 0 /dev/log 801cc10c stream 0 0 8008e690 0 0 0 /dev/printer Address #socket address type #type: stream or dgram Inode #Inode? Conn #sockets connections Refs #? Nextref #? Addr #socket file Anyone know what does it mean "Refs" and "Nextref". As I know Refs is referred to routing, but in sockets there is no routing as I know.

Is there any way to install docker on FreeBSD? I tried following the official freeBSD handbook but from what i have found the version of docker on FreeBSD is broken (i read that on docker page). i wonder if there is way to install it using older version or something.

I'm trying to play a very old [Star Trek BSD game](https://manpages.debian.org/unstable/bsdgames/trek.6.en.html) . It recognises characters that I type, but I occasionally make an error and want to use the arrow keys to correct it. This always fails. The pressing the left arrow on my keyboard makes me type ^[[D and the other arrow keys are similar. I believe that many old packages behave like this. What are the idiomatic solutions to this problem? Are them some old-school keyboard shortcuts that I have not thought to try? Or must I resort to manually modifying the game myself? It certainly seems to not expect Vi movements.

I'm trying to work out whether or not, or rather to what extend, xattrs are supported in FreeBSD using ZFS. I've read some conflicting information. 1. zfs get xattr lists it as on (default) for /, /usr and /var, but as off (temporary) for all other datasets, including children of those mentioned above. 2. Running zfs set xattr=on zroot/usr/home I get the message > property 'xattr' not supported on FreeBSD: permission denied. 3. This agrees with [the zfs man page](https://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+10.2-RELEASE&arch=default&format=html) : > The xattr property is currently not supported on FreeBSD. 4. setextattr, getextattr and lsextattr seem to work well enough. 5. I also managed to save and restore a device file node using rsync --fake-super, and could see its data using lsextattr and getextattr. 6. Wikipedia has some discussion in the [xattr talk page](https://en.wikipedia.org/wiki/Talk:Extended_file_attributes#FreeBSD) . Apparently there once was a claim that ZFS supports xattr since FreeBSD 8, but that was removed later on, with reference to the manpage (see 3.). Currently I get the impression that extended attributes on zfs work in practice, but that the xattr property which would control their use does not work as it would in other zfs distributions. But I'd like to hear that confirmed (or corrected) before I trust large amounts of backup data to an rsync --fake-super running on such a machine. I'd rather not lose all my metadata due to known xattr problems. If it matters, this is a *very* fresh FreeBSD 10.2 install I just set up, with ZFS set up by the installer.