hi,

anyone can help me to configure redmine50 ?

Have you checked its website, redmine.org ?

Title: Overview - Redmine

yes

i try create db but :

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

and pkg check -d say me :

mysql80-server is missing a required shared library: libprotobuf.so.3.19.4

Sounds like your problem is with mysql, not redmine.

yes

but how correct it ?

i was delete sys on db of mysql

I'd reinstall mysql80-server.

try it

but the problem is same

i think can't purge conf file

I'm out of easy guesses, and that's all I know enough to suggest.

no more sggest ?

it's isn`t work i re-intall to 13.2

i don´t know how restart with clean distrib

white-wolf: this will install deps: pkg info -d mysql80-server | grep -v mysql80-server | xargs pkg install -y

The most recent versions of packages are already installed

i have a qemu guest running on arch with libvirt and dns has stopped working, im a freebsd newbie so i not sure where to draw the line in the problem betwen guest and host, heres the libvirt network config ix.io/4sn4

and my /etc/resolv.conf on the guest is "nameserver 192.168.122.1"

try with 1.1 or 0,1

you mean straight to gateway in resolv?

white-wolf: cheers it works, any idea why/how it got that way?

your box have a dns server

for more anonyme use opendns

yeah on the host libvirt starts a bunch of dnsmasq processes,

this would imply they are not working?

use NAT

well thats what i thought i did

Is there any explanation why 13.2 is delayed?

I wish to setup my laptop with freebsd 13.2

three extra RC builds... last minute changes/fixes... check cgit.freebsd.org/src/log/?h=releng/13.2. Why wait? You can install 13.2-RC6 and later update to RELEASE with freebsd-update or rebuild from src.

testing finds bugs. which is why we encourage testing

so, no testing, no bugs?

No testing, no known bugs

and unknown ones are just "undocumented features"

Good morning. I have migrated to a new disk using zfs send/recv, and ran an EFI update command from the same guide. The EFI is now bootable from the UEFI bootlist, but I still end up on the old zroot. I am guessing I need to rename the new zpool? Or is there another way? And is it simple to boot into a live USB and rename, or is it a can of worms?

What does "bectl list" show?

13.1-RELEASE_2023-03-12_160133 - - 105M 2023-03-12 16:01

default NR / 8.12G 2023-03-11 18:42

This is the guide I followed: people.freebsd.org/~dch/posts/2021-05-12-nvme-on-freebsd.html

Title: Adding a new nvme drive - Random Musings

??

zapata: I know I can install the release candidate but I wish to go directly with release so I only use stable stuff

lol, it that date again :D

Is there any integration for VS code like the docker one that works with jails

cristiioan: why not yet it, to make sure it will be stable — for your use-case, and report bugs if it isn't

morsing: did you set the new zpool as boot device?

meena: How do I do that?

Title: loader.conf(5)

vfs.root.mountfrom="zfs:/pool/fs"

meena: But /boot is on ZFS, the new pool. Catch-22?

I think this goes wrong even before the kernel is loaded.

I've run into a port that writes some files into /usr/local/etc/newsyslog.d but as far as I can see that should be /usr/local/etc/newsyslog.conf.d. I couldn't find too many references to newsyslog.d outside of a 2015 BSDCan paper referencing support for it has been added bsdcan.org/2015/schedule/attachments/327_AsiaBSDCon2015_paper.pdf. Can anyone shed some light on this before I submit a patch?

My best guess so far is at some point newsyslog.d was used and then replaced with newsyslog.conf.d

looks like it was introduced initially as newsyslog.conf.d (see b39df8fe2d85847497684b427a1b9c2908c4a576)

but it's /usr/local/etc/syslog.d for syslog itself, so someone must have confused the two

domlaut: I'm guessing /etc/newsyslog.conf history will have the answer

domlaut: also, I think it was at one time, all files, not just .conf

dvl: hey, you're actually the maintainer for the package :-)

lol

domlaut: which package?

acme.sh -- I have a patch ready, but I'm thinking whether the newsyslog.conf.d file should also be installed in share/examples as the cron.d file is

Oh yeah, that's an old one. I've also wanted to do a cron.d entry for that.

there is a cron installed, but missing a user. fixed that too

I checked mail/dta's cron file to see how they're doing it, and indeed its "* * * * * root ..."

Sorry I thought you said anvil, i got it.

acme.sh installs "* * * * * <script>" when it should be "* * * * * acme <script>"

another question is given its supposed to be running with the acme user, should the binary remain in sbin instead of bin

but I don't want the patch to break stuff, so I figured not to change that

axcient.com/blog/using-dtrace-to-fi…nd-block-sizes-of-zfs-nfs-and-iscsi ooo

Title: Using DTrace to find block sizes of ZFS, NFS and iSCSI - Axcient

anyway -- give me 10 minutes to submit it on bugzilla and we can take it from there when you've got time if that's okay

This may be a breaking change.

dvl: the cron file or the newsyslog file? contents or locations?

domlaut: newsyslog - might duplicate entries.

currently both get installed commented out, one in a wrong location (newsyslog.d)

to actually set up the package, you need uncomment the cron file, add a user to it, and move newsyslog.d/acme.sh to newsyslog.conf.d/acme.sh.conf

I'm not sure if newsyslog.d can or should be clean up, or if newsyslog.conf.d/acme.sh.conf would end up overwritten. maybe go back to not installing examples but just leave them in share/examples?

domlaut: Right, good, I should be installing a conf.sample file

so that's also done

domlaut: I prefer to make it as easy as possible, and that's a sample file

so for newsyslog, two files get installed into PREFIX/etc/newsyslog.d: acme.sh and acme.sh.sample

I would expect that to only be one file, in PREFIX/etc/newsyslog.conf.d, and for it to be named acme.sh.conf.sample (as .conf is required)

and then for cron, you get a file in PREFIX/share/examples/acme.sh/acme.sh-cron.d, and the same file in PREFIX/etc/cron.d/acme.sh

Title: FreeBSD / src / b39df8fe2d85847497684b427a1b9c2908c4a576 - FreshBSD

morsing: what does ‘zpool show bootfs $pool’ show

shouldn’t set vfs mountfrom these days

dvl: alternatively the newsyslog sample should also go in PREFIX/share/examples, as the cron file does. I'm not sure what the best practice here is.

domlaut: Thanks

dvl: you want a patch then or will you take care of it? :-D

domlaut: For newsyslog, it's building now. The testport is doing a full build of all dependencies

cool, great

The only change is newsyslog.d -> newsyslog.conf.d

dvl: in that case do you think its worth mentioning in pkg-message.in that the installed file needs to end with .conf

currently it says "A newsyslog.conf sample file is installed at %%PREFIX%%/etc/newsyslog.d/acme.sh - you must modify it by at least uncommenting the line"

(you also need to rename it to something ending in .conf, acme.sh will not work)

nor will the default cron file for that matter - you'll find a (*system*) PARSE (bad username) in /var/log/cron with the default installed.

(if you just uncomment the line in etc/cron.d/acme.sh,)

Adding an upgrade message to pkg-message

Added acme to crontab file

I think the existing cronjob was meant to be installed under the acme user - so when it was also used as the cron.d entry, it failed.

domlaut: install vs upgrade pkg-message : gist.github.com/dlangille/b2e2f236f2f61f0e7b1565aedd5bf373

Title: acme.sh updates · GitHub

dvl: is it /usr/local/etc/newsyslog.conf.d/acme.sh.sample or /usr/local/etc/newsyslog.conf.d/acme.sh.conf? install says one, upgrade another :-D

(or both?)

fixing

domlaut: please reload that url

ok so you *are* installiing a commented-out .conf file instead of a .sample file. okay

domlaut: I agree, we should not install to /usr/local/etc.cron.d - that file needs local mods. and an upgrade would overwrite it. No such thing as a .sample file in that directory

domlaut: yes, it goes in as a commented out .sample file

now I'm confused

first because as of right now two files get installed (one ending with sample, another not) and the install file in the gist doesn't say it's a .sample file, but a .conf file

domlaut: Agreed. and you don't edit the .sample file.

as for the upgrade file, the old location(s) were /usr/local/etc/newsyslog.d/acme.sh and /usr/local/etc/newsyslog.d/acme.sh.sample, not /usr/local/etc/newsyslog.d/acme.sh.conf

Oh, and it says copy, no need to copy

^ ignore that. wrong file.

ok so just to confirm, two identical files are installed, one .conf, one .sample.conf

Correct

sorry .conf.sample

great

That's the function of @sample in pkg-plist

Next task, make sure cron.d file is not installed to /usr/local/etc/cron.d

great, in that case just update the upgrade file to reference that previously /usr/local/etc/newsyslog.d/acme.sh and /usr/local/etc/newsyslog.d/acme.sh.sample we installed

because it wasnt acme.sh.conf and acme.sh.conf.sample

it was missing the .conf

s/we installed/were installed

I think the upgrade message should mention "%%PREFIX%%/etc/newsyslog.d/acme.sh" and "%%PREFIX%%/etc/newsyslog.conf.d/acme.sh.conf" - not .sample. The @sample macro will always overwrite any existing acme.sh.conf.sample but will only create acme.sh.conf if it does not already exist.

yeah fair enough

as long as it doesn't reference acme.sh.conf that didn't exist previously and only exists now

OK, working on non-install to /usr/local/etc/cron.d/

So I've spent the past five minutes modifying the wrong ports tree, and wondering why my changes were not reflected in my testport...

and, why werent they? :-D

domlaut: Please reload the URL - below the pkg-message bit, the first part now has details of the install files.

dvl: seems right. I'd leave the cron file to be commented, though

so the SHELL, MAILTO and actual cron line

domlaut: Why? It gets installed only to /usr/local/share/examples/acme.sh/acme.sh-cron.d ... not to an active cron.d directory

because you don't need to think about configuring MAILTO and SHELL, those are totally optional

domlaut: I wanted to not install to cron.d because it has no concept of a sample file, everything gets run. Future pkg upgrades would overwrite that file.

I agree about not installing it

domlaut: Yes, they are optional. So you think comment out only mailto and shell?

that would work too, absolutely

OK, I think we're ready to commit

woohoo! thanks dvl, hope this'll help future newcomers using acme

done

dch: I don't have that option, did you mean zpool?

Title: CrystalBSD: "We have some exciting news to share with you! We …" - Fosstodon

hello folks, anybody have any luck running the gamecube dolphin-emu emulator?

You can still bypass root password of a system with single user mode or booting from a live cd in freebsd, right?

telgareith: sure, but it's true for anything that doesn't have FDE, that you can bypass its authentication if you have physical access

Anyone who has the timetable for when the FreeBSD foundation is ready to launch the new IIS driven site?

heh

xtile: freebsdfoundation.org/about-us/about-the-foundation

Title: About the Foundation | FreeBSD Foundation

I do know about the foundation.

A little.

Not very much, admittedly.

Wow - booted from a live USB stick, renamed zroot to zold and the new zpool to zroot. Booted up but the ative zpool is now zold. /boot/efi is mounted on the new disk though. So clearly, the EFI image, or kernel, or something else, points physically to the old disk, not the zpool name.

I think I just have to re-install, not worth messing with a migration.

morsing: why?

=)

what have happened XD

drobban: It imports/mounts the old zpool, no matter what I do.

morsing: im no expert in zfs, but it sounds like a broken conf to me.

drobban: But where?

so nobody has issues with dolphin? just me?

since that's not what you asked the first time around, you might wanna describe the issue you're having.

well im just not getting anything to render, it just an empty window when i run anything

that'll give someone who has a clue a chance to help, as opposed to just asking for someone :)

sorry, kernel crash

gzar: got a crashdump?

sadly no, still cant get my kernel to do that, working on it

morsing: well... Lets assume that knowing the answer to that question is one of the things to why Im no expert in ZFS =D just started using freebsd and zfs a month or so ago =)

morsing: any thing is certain, the system wont do shit without instructions.

github.com/freebsd/drm-kmod/blob/72…bf4/drivers/gpu/drm/linux_fb.c#L227 nice april 1 code :)

Title: drm-kmod/linux_fb.c at 727cf70f4ec5bd7a17b32a1ac605e4689e2d5bf4 · freebsd/drm-kmod · GitHub

yuripv: hmm?

meena: "fb_bpp not set, setting to 8\n" followed by fb_info->fbio.fb_bpp = 32;

ah, cute

i love when the comments (or in this case debug output) and the code disagree

Hello, the quarterly VScode package version for FreeBSD 13 is 1.70.2_3 and there is no version available for latest. However even if the quarterly VScode package version for FreeBSD 12 is the same, the latest VSCode package version for FreeBSD 12 is 1.76.2.

How to know why ? Is there any problem encountered in building VSCode 1.76.2 for FreeBSD 13 ?

Appears it's because of electron19 being blacklisted.

where/how did you find this information ?

freshports?

yes but where in freshports ?

I can't find this info

anyway, the electron thing was fixed today? or yesterday?

FreeBSD secret ssshhhh

so it should be back real soon now

After 25 years on Slackware II migrated recently to FReeBSD. I really would like to be as autonomous as I am with Slackware (and Linux in general)

doug713705[m]: I'm not sure if freshports know it but look at poudriere dashboard at pkg-status.freebsd.org

So many thing to learn but 'I'm not as young as I was

Title: 270565 – electron* ports are blacklisted from the build

skered, meena Thanks

doug713705[m]: I'd recommend getting poudriere-devel and hope you can pull down binary deps and minimize your rebuild of vscode.

I'm not enough confident to mix package source and, for now, I prefer to stick to binary package from pkg only

Assuming you can build it locally.

Yeah, it can be a little tricky handling multiple pkg sources.

I'm using FreeBSD for only 5 months and still have some WTF moments (even if the migration from Slackware was pretty smooth)

How old is 1.70? 1.77 is the latest?

I'm waiting for 13.2 to migrate my laptop. So my desktop is my sandbox

~1 year it appears.

1.70 is pretty old, august 2022

which is old for vscode

and some plugins won't install on 1.70. Our world is crazy. Everything is fastly deprecated / removed

I like the idea of using it thru a brower. I know eclipse had... Chi? And maybe there was another third-party that did the same.. I see MS has a MS provided one now (long time?).

Does the web insterface need electron?

Might be a possible method if not?

I don't like this idea. The all in a browser thing in general

Yeah, less features and plugins. Oh well.

and updates forced to you, etc.

It's also an easy way to facilitate usage of proprietary software (i.e: Please use our "free as in free beer but not in free as free speech" online software).

I'm not absolutely against proprietary software but I tend to avoid them when I can.

Some time ago I realized error my ways of ZFS pools renamed "seemingly" without me knowing. The error was of "zpool import -f one other" thinking that would force-import pools named "one" & "other".

(Needless to write that renamed "one" to "other")

Is anyone watchig|attending Asia BSD Con, 2023.asiabsdcon.org/program.html.en ?

Title: AsiaBSDCon 2023 - Conference Program

parv, i was planning on going to BSDCan until i heard they were enforcing a masking mandate