destination path needs to end in . lol. so cp -RpP /tmp/foo/ /home/foo/.

so weird

guess it makes sense but the trailing / should convert how symlink is treated into a dir

if we can touch /home/foo/bar.txt, should be able to cp into it

hi

Is there something like `ldd` that also shows dynamically called linked dependencies? - Like `dlopen` style?

is there anyway to see the -px (x being the version) subreleases...

are they announced anywhere I mean*

I think polyex has found a minor bug in the cp handling of -R. It can be workedaround by using "cp -R src/ dst/." instead of "dst/" pushing even further through the symlink to the "." pointed to.

Normally using foo/ forces foo to be a directory and implies "foo/." but that seems to be getting snarled up there with cp -R for some reason.

now you've got me thinking about grep optimization. Sigh.

I've been known to troll people into action in the past, so don't feel bad

taking /dev/random and the pattern [1234567890]+1234567890, FreeBSD is slightly faster than the l4w (also the l4w is 2950x vs freebsd on 1900x).

... but l4w might be getting in it's own way. I'll have to bench this on some equivalent VMs or something.

1.3G/s (freebsd) vs. 1.1G/s (kali linux on l4w). And the linux had the faster processor.

zBeeble: and you're definitely testing /usr/bin/grep and don't accidentally have gnugrep from ports installed?

I will check. I don't usually istall gnu grep.

Maybe the pattern isn't involved enough to trigger?

I'm certainly not giving up because _one_ test was good. I have several reasons to believe that it is slow.

(I was just idly poking at things while I fixed up the pspp poudriere mess)

to be fair /dev/random also isn't necessarily representative of the kinds of workloads grep typically operates under

usually we're talking reasonably-sized lines that we need to search, /dev/random may have random \n scattered around enough that it's not obvious

nope ... not gnugrep.

true, true. I'll think about testing it with the pspp log ... see how well that goes.

hi.. i got stuck when i did "pkg search nginx"

how to fix?

I have cerated jail with iocage but when I try to use pkg -j it says jail ... not found. any tip ?

or is bettre to use ioncage pkg ?

iocage not ioncage ... :)

Gurar: if you use the same 'JID' as listed in the 'iocage list' for 'pkg -j X ...' ?

yes

Im using name not jid

ups

is possible to use name instead of jid ?

yes. Use 'jls -N' to get name rather than jid

iocage apparently prefixes the jailname with 'ioc-'.

what do you suggests to use iocage pkg or use pkg directly ?

I'd use pkg directly. 'iocage pkg' has (atleast for me) had some issues with the output.

norrland thanks!

al1r4d: what's the output? Can you post the command and the output in dpaste.org ?

Title: dpaste

after following the handbook on freebsd upgrade minor version i get freebsd-version -kru 14.1-RELEASE 14.1-RELEASE 14.1-RELEASE-p1 how come -kr doesnt show patch level? i have restarted and run last freebsd-update install but still same

Puzfire: patch level can differ for patchsets that only change the userland or libraries, since unames values are derived from sysctls, which are only updated when the kernel binary changes.

freebsd-version -kur will tell you the kernel, userland, and running versions respectively

so all upgrade is done correctly even so : # freebsd-version -kur

14.1-RELEASE

14.1-RELEASE

14.1-RELEASE-p1

uname -a -> 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64

if 14.1p1 is the newest patch set, then yes

ye just did update :) wasnt sure as old upgrade on 14.0 did look different ;)

so was unsure

so now i can venture into the jails, now im sure host is done correct. need to document it so i can remember

Im creating jails with iocage but I can access internet from jails so I cant even install pkg's etc. Im creating jail like this iocage create -n postgresql ip4_addr="192.168.2.20" -r 14.1-RELEASE

inside a jail can we create our own zfs datasets separate from those of the jail's host?

yes

Gurar: have you read iocage.readthedocs.io/en/latest/networking.html ?

Title: Networking — iocage 1.2 documentation

norrland: thank you. But looks like my problem was solved

i am super happy about the sys/fs/p9fs commit in CURRENT (and the "MFC after: 3 months" note) :)

Title: systemd 256.1: Now slightly less likely to delete /home • The Register

thank you freebsd ;]

i get to keep my homedir

haha yikes

dch do you know how to create zfs datasets inside a jail?

good evning! I thinking of trying to install FreeBSD on a macbook air mid 2012, and wondering is it something special I need to think off? or can I just download the image to an usb and install it?

polyex: yes, there are really just a couple of things you need to do

zfs create -o canmount=off -o mountpoint=none zroot/jailed # make a containing dataset to keep things tidy and clean, not strictly required, but very helpful

zfs create -o mountpoint=/home/jenkins -o jailed=on zroot/jailed/jenkins # create the dataset that will *in future* be jailed. it needs mountpoint to be relative to the jail chroot

zfs jail jenkins zroot/jailed/jenkins # do this just after jail creation & before startup, which mounts the dataset inside the jail

if you use jail.conf then it looks a bit like this: git.sr.ht/~dch/ansible-jails/tree/m…plates/instance.conf.j2.default#L28

Title: ~dch/ansible-jails (main): templates/instance.conf.j2.default - sourcehut git

dch ah. what i was doing was i had my zfs clone -o jailed=on -o volmode=dev zroot/jails/templates... zroot/jails/jail/testjail. but that didn't work

polyex: ok yeah you can probably "jail" block devices but I don't think that would be secure

why not? jc

nwe: i've never tried an air, but my learnings from attempting on a macbook pro is that apple hardware leaves a bit to be desired.

nwe: i got 14.0 running "okay", but convenient features such as resume after suspend and sound is where i'm currently stuck.

nwe: for network i needed to go with wifibox, which runs an alpine in a bhyve and load some binary-blob linux-only drivers.

|cos|: thanks for the heads up :) Ihmm wifibox, whats that?

nwe: a virtual machine running a minimal linux, just for the linux wifi-drivers. or in abstract terms, a pragmatic solution.

nwe: i used a usb wifi-adapter while installing, just to get to the phase where i could replace it with wifibox.

|cos|: okey, regarding the sound is it because lack of driver support?

sound works with headphones. i read people managing to get speaker sound by fiddling. i wrote down the link, let me find it.

Hi, I'm trying to capture packets using WireShark on FreeBSD 14.0. The issue I'm seeing right now is only incoming packets are captured. This happens with and without firewall enabled.

nwe: forums.freebsd.org/threads/no-audio-on-my-system.57473

Title: No Audio on my system | The FreeBSD Forums

nwe: the second page has stuff like `hint.hdac.1.cad0.nid18.config="as=1 seq=0"`. let me know if you get it working, especially if you truely understand it. (:

|cos|: I will first create a backup, and when I have time to install it and get it to work I will reach out to you!

nwe: backup seems like a great idea, actually

unfortunately macOS is probably the only thing one can run if wanting to use a macbook as ones daily driver. not having suspend-resume gets old quite quickly...

|cos|: the sad thing is that I cant upgrade that macbook..

nwe: i understand, and believe it will become a neat freebsd machine. just want you to be fully prepared on what to expect.

nwe: Have you looked at OpenCore Legacy Patcher? dortania.github.io/OpenCore-Legacy-Patcher/BUILD.html

Title: Building and installing OpenCore | OpenCore Legacy Patcher

mariuss: nope, didn't know it exists :P

dch why it insecure to jail block device?

Well, this is odd. I'm working with a client's systems where /etc/rc.conf has multiple ifconfig*alias* lines. However, when the booting system hits one line, it just hangs. Any thoughts on what sort of thing triggers this?

paste 3 lines. the line above it, the line that halts, and the next line

ifconfig_genet0_alias0="inet fqdn.domain0.net netmask 255.255.255.255"

ifconfig_genet0_alias1="inet fqdn.domain1.com netmask 255.255.255.255"

ifconfig_genet0_alias2="inet fqdn.domain2.net netmask 255.255.255.255"

shouldn't gqdn.domainx.x be ips not domains?

Actual names substituted....

All fqdns exist in /etc/hosts

change to ips and try

Did that for fqdn.domain1.com, and got it working. Just trying to figure out why just the one won't work.

in bsdinstall's installerconfig i set some env vars. but bsdinstall is ambiguous on the format. quotes or no? like nonInteractive="YES" but ZFSBOOT_VDEV_TYPE=stripe. wtf?

man bsdinstall is ambiguous*

In many circumstances, quotes are optional.

If your data includes things like spaces or single quotes, wrapping it in double quotes disambiguates it. Otherwise, if your data is a simple alpha-numeric string the quotes do nothing.

ty

Wrapping in double quotes is a best common practice. It allows including spaces in data while also allowing variable expansion. From this, no quotes or switching to single quotes, or adding backslash escapes cover the uncommon exceptions.

just always wrapping env var values in double quotes even when not needed?

will wrapping value in double quotes ALWAYS be valid no matter what or are there more rules?

Yes. It comes from historical development of the shell, back they'd resolved the requirements.

is there such a thing as export FOO=1 is different from export FOO="1"?

Yes. In test comparisons, the former is numerical, while the latter is a string.

so what if i "double quote everything" but then the prog using the env var expects numerical 1 instead of string "1"?

Given shells are loose with respect to types, there exists options for pushing for the opposite during specific tests.

i just passed wrong type

Possibly. That's an uncommon case though.

Shells are loose on types, so that's an easy override.

man that sucks

the ambiguity is really stressful

It can be. Fortunately that's rare.

I think I've run into "1" vs. 1 something like a half-dozen times since I got started on Unix.

looking at github.com/freebsd/freebsd-src/commits/releng/14.1 looks like some updates since it came out. have those gone through any other release for vetting or are they new code?

Title: Commits · freebsd/freebsd-src · GitHub