polyduekes
well, i mean it's cut and clear that tarfs and ext2fs weren't affected in that patch but sure :)
polyduekes
yeah, the version of kernel in freebsd-version is still p2
Jekyll
You installed the "update"?
Jekyll
Output of freebsd-version -kru ?
B
can anyone explain what does it mean by updating to p2
Maybe you had some missing files ? Or old ones ?
polyduekes
Maybe you had some missing files ? Or old ones ?
there were no missing files or old, my src is upto date with the 14.2 branch
Jekyll
Would you mind sharing the checksum of /boot/kernel/kernel ?
polyduekes
Would you mind sharing the checksum of /boot/kernel/kernel ?
why? because it won't match for obvious reasons
Jekyll
Just curious if yours is the same as mine.
polyduekes
Just curious if yours is the same as mine.
d92232fdeec355858cd33787a2e92d48976d440a20605727ae3012db8c1288e5 sha256sum it won't be the same but there you go
Jekyll
d92232fdeec355858cd33787a2e92d48976d440a20605727ae3012db8c1288e5 sha256sum it won't be the same but there you go
Now I wonder what version are you on. I check 2 different machines, both upgraded to 14.2-RELEASE-p2 but from different versions, they share the same kernel binary.
Pouria
Now I wonder what version are you on. I check 2 different machines, both upgraded to 14.2-RELEASE-p2 but from different versions, they share the same kernel binary.
did you build from source? because if you didn't, it's normal to have same checksum on different machines.
Andreas
I have made a script that uses ffmpeg to split a movie up into many smaller parts, using I-frames as the split points.. I can then encode these parts using different computers.. the problem is that sometimes, and it seems completely random... there is no I-frame.. so the audio plays along as intended, but the screen freezes for some seconds.. is anyone good with ffmpeg here, please?
Mahdi
Hi friends, How's it going? Last night, my computer running FreeBSD turned on at 3:30 AM in a rather curious way. Two hours later, when I woke up, I noticed the sound of the computer's fan. Now, after checking the /var/log/messages file, I can't find anything about the reason why the computer turned on. In the BIOS, neither link-up or Wake-on-LAN (WoL) active. How can I determine the reason my computer turned on in FreeBSD? For instance, whether it turned on due to the power button or something else? When I woke up and tried to log in, it seemed like the keyboard driver wasn't working, and I couldn't type anything. I ended up unplugging the computer. Thank you!
Mahdi
Could power fluctuations or something similar cause the computer to turn on? Or perhaps I had enabled the feature in the BIOS to turn on the computer using the keyboard with a password, which wasn’t working anyway.
Mahdi
Yes, I didn't sleep much, so maybe my brain hasn't bootsed up yeyt
Pouria
Not related to your problem, but I'm currently experiencing a similar issue. Last week, I was doing my regular upgrades, and after installing the kernel, my laptop doesn't power off anymore. The command 'init 0' works, but it seems like I have an ACPI issue that doesn't initiate the power-off request for my laptop. P.S: I'm on CURRENT.
Krond
Not related to all of that, but when I'm turning off Windows on my book it just reboots instead of powering off. Though I haven't seen it's powering up by itself I think this might be related to vendor/firmware/bios settings… a lot of things could happen. And as we have no logs about why host was powered up it's really hard to tell what heppened.
Maxim
first, why would anyone "turn off" their computer in the current year? is it, like, 1998 or something? second, how's "my computer weirdly turned on" FreeBSD-related?
polyduekes
btw i have a similar keyboard driver related issue, i need to try debugging that
polyduekes
the keyboard randomly stops taking input even though the indication lights on keyboard tell me that it is connected, ti make it work again,i have to unplug and replug it
Pouria
btw i have a similar keyboard driver related issue, i need to try debugging that
I had similar issue before, and this quirk helped me: usbconfig -d 0.{} add_quirk UQ_KBD_BOOTPROTO. you can test your keyboard inputs with xinput if the problem only occurs in Xorg or use usbdump if it also happens in console.
Maxim
If FreeBSD supported hibernate, then I'd say that .
my ThinkPad is running FreeBSD, and it's sleeping rn
B
S3 and S4 are different .
Maxim
yes, and? mine can spend up to several days in S3
nami
Anybody here runs audio/mixxx or qtracktor or lmms on FreeBSD?
nami
Gold:
nami
https://people.freebsd.org/~wpaul/daemonette/s114.jpg
Pouria
https://people.freebsd.org/~wpaul/daemonette/s114.jpg
That's good, but @freebsd_offtopics would be more appropriate for that 👍
nami
https://mixxx.org/ Works well on FreeBSD A higher kernel frequency of 2000 - 3000Hz seems to give better performance
Andrei Drusian
https://mixxx.org/ Works well on FreeBSD A higher kernel frequency of 2000 - 3000Hz seems to give better performance
Uoww I also do DJing. I still have a USB stick with Windows on my laptop just to use Pioneer's rekordbox. You can try it to see if it works with my equipment.
polyduekes
huge update coming soon(i still wish for security updates to get merged asap rather then waiting for new quarterly)
Monad
Hi
Artel
Hi
hello
Chad
Hi
welcome!
polyduekes
it's nice to see there are people working on podman and oci container images support for freebsd, super useful
polyduekes
sigh, nvm, looks like there is still need to be a lot of work done
polyduekes
https://cgit.freebsd.org/ports/tree/sysutils/podman/pkg-message hmm, am i doing something wrong?
polyduekes
nvm, the proper command is podman run --rm --os=linux docker.io/library/alpine cat /etc/os-release | head -1 someone should change that in https://cgit.freebsd.org/ports/plain/sysutils/podman/pkg-message
polyduekes
also by "Edit /etc/pf.conf and set v4egress_if, v6egress_if variables to your network interface(s)s" they mean network interfaces like re0 for ethernet etc right?
polyduekes
sigh, now what am i doing wrong :/
B
I don't understand the need for Podman when jails exist .
B
convenience
Jails have that too .
che
sigh, now what am i doing wrong :/
What about next command: podman run --rm docker.io/dougrabson/hello if doesn't work then I think that: sudo sysrc linux_enable=YES sudo service linux start sudo podman run --rm --os=linux docker.io/library/alpine cat /etc/os-release | head -1 NAME="Alpine Linux" For more information and examples by https://podman.io/docs/installation
polyduekes
Jails have that too .
no one is gonna spend all the time porting containers to jails whenever they need one and already exists as an oci image and oci is much more supported and well regarded, additionally, if someone knows the working of podman they would be quite reluctant to let their skills go to waste and learn about jails while everyone else is having breeze time with podman and oci images, it's just more time saving
polyduekes
figuring out how jails work when you can instead pull up an oci image in seconds is more convenient
polyduekes
That's just your lack of skills, in other words skill issue .
it's not lack of skills, it's called saving time, you can't expect a worker in a production environment to waste time on learning jails, while the competitor is going through faster, it's unproductive
polyduekes
and oci images are very much the standard in cloud industries
B
It's much simpler for me to run a jail off a tar file rather that podman docker insanity . It is really time saving for me . It is native to my OS and time tested so there are a ton of info on it too .
polyduekes
"insanity" heh, enjoy you dreams
B
Thanks jails are really a dream, enjoy your YAML files also .
Jay
sigh, now what am i doing wrong :/
You are assuming you are on linux
polyduekes
You are assuming you are on linux
yes, i need to specify —os=linux everytime, got it now
polyduekes
https://github.com/AlchemillaHQ/Sylve seems nice
Pouria
? ofc oci images are there, but how does that relate to what i said about porting to jails?
I am here to help. You mentioned the term OCI, which refers to the Open Container Initiative. It is not a tool but rather a specification for container images. There is a working group focused on FreeBSD Jails within the OCI framework. The issue you are facing is not the inability to use OCI images on FreeBSD, but rather the challenge of using a Linux-specific image format on FreeBSD. While it is possible to make it work, you may find yourself on a solo mission, as there are already OCI images available for FreeBSD. Others may prefer to use the native tools that are better suited for their needs. Based on the latest FreeBSD reports, I would like to inform you that there are two other tools available that support OCI and have their own centralized repositories. You may find your specific image on AppJail or Pot to help resolve your issue. Regarding Podman, it is designed specifically with Linux in mind, and using it on FreeBSD may not yield the best results. Others in this chat have indicated that it is not the right tool for your requirements in a FreeBSD environment. You are correct about the importance of saving time, which is one of the reasons why full OS virtualization exists on FreeBSD. If you are more familiar with a specific tool and image that only works on Linux, it may be worth considering a switch to Linux. If you prefer a homogeneous environment, you could run Linux on top of FreeBSD. However, the recommended solution is to use the native tools for OS-level virtualization on FreeBSD and to seek your image on AppJail, Pot, or other applications, or even contribute to building one.
Pouria
And also wanted to remind the group to review the FreeBSD Code of Conduct for their language and tone: https://www.freebsd.org/internal/code-of-conduct/ We're a community. This is NOT a religious war.
polyduekes
I am here to help. You mentioned the term OCI, which refers to the Open Container Initiative. It is not a tool but rather a specification for container images. There is a working group focused on FreeBSD Jails within the OCI framework. The issue you are facing is not the inability to use OCI images on FreeBSD, but rather the challenge of using a Linux-specific image format on FreeBSD. While it is possible to make it work, you may find yourself on a solo mission, as there are already OCI images available for FreeBSD. Others may prefer to use the native tools that are better suited for their needs. Based on the latest FreeBSD reports, I would like to inform you that there are two other tools available that support OCI and have their own centralized repositories. You may find your specific image on AppJail or Pot to help resolve your issue. Regarding Podman, it is designed specifically with Linux in mind, and using it on FreeBSD may not yield the best results. Others in this chat have indicated that it is not the right tool for your requirements in a FreeBSD environment. You are correct about the importance of saving time, which is one of the reasons why full OS virtualization exists on FreeBSD. If you are more familiar with a specific tool and image that only works on Linux, it may be worth considering a switch to Linux. If you prefer a homogeneous environment, you could run Linux on top of FreeBSD. However, the recommended solution is to use the native tools for OS-level virtualization on FreeBSD and to seek your image on AppJail, Pot, or other applications, or even contribute to building one.
yeah, i think i told that i solved that before here
polyduekes
I am here to help. You mentioned the term OCI, which refers to the Open Container Initiative. It is not a tool but rather a specification for container images. There is a working group focused on FreeBSD Jails within the OCI framework. The issue you are facing is not the inability to use OCI images on FreeBSD, but rather the challenge of using a Linux-specific image format on FreeBSD. While it is possible to make it work, you may find yourself on a solo mission, as there are already OCI images available for FreeBSD. Others may prefer to use the native tools that are better suited for their needs. Based on the latest FreeBSD reports, I would like to inform you that there are two other tools available that support OCI and have their own centralized repositories. You may find your specific image on AppJail or Pot to help resolve your issue. Regarding Podman, it is designed specifically with Linux in mind, and using it on FreeBSD may not yield the best results. Others in this chat have indicated that it is not the right tool for your requirements in a FreeBSD environment. You are correct about the importance of saving time, which is one of the reasons why full OS virtualization exists on FreeBSD. If you are more familiar with a specific tool and image that only works on Linux, it may be worth considering a switch to Linux. If you prefer a homogeneous environment, you could run Linux on top of FreeBSD. However, the recommended solution is to use the native tools for OS-level virtualization on FreeBSD and to seek your image on AppJail, Pot, or other applications, or even contribute to building one.
it's not, others lot have also ran linux oci containers with podman on freebsd before
Pouria
I didn't read messages deep enough. Happy to hear that
polyduekes
I am here to help. You mentioned the term OCI, which refers to the Open Container Initiative. It is not a tool but rather a specification for container images. There is a working group focused on FreeBSD Jails within the OCI framework. The issue you are facing is not the inability to use OCI images on FreeBSD, but rather the challenge of using a Linux-specific image format on FreeBSD. While it is possible to make it work, you may find yourself on a solo mission, as there are already OCI images available for FreeBSD. Others may prefer to use the native tools that are better suited for their needs. Based on the latest FreeBSD reports, I would like to inform you that there are two other tools available that support OCI and have their own centralized repositories. You may find your specific image on AppJail or Pot to help resolve your issue. Regarding Podman, it is designed specifically with Linux in mind, and using it on FreeBSD may not yield the best results. Others in this chat have indicated that it is not the right tool for your requirements in a FreeBSD environment. You are correct about the importance of saving time, which is one of the reasons why full OS virtualization exists on FreeBSD. If you are more familiar with a specific tool and image that only works on Linux, it may be worth considering a switch to Linux. If you prefer a homogeneous environment, you could run Linux on top of FreeBSD. However, the recommended solution is to use the native tools for OS-level virtualization on FreeBSD and to seek your image on AppJail, Pot, or other applications, or even contribute to building one.
there is no native image for python oci image, only Linux and windows ones so i can't have native either way
polyduekes
I am here to help. You mentioned the term OCI, which refers to the Open Container Initiative. It is not a tool but rather a specification for container images. There is a working group focused on FreeBSD Jails within the OCI framework. The issue you are facing is not the inability to use OCI images on FreeBSD, but rather the challenge of using a Linux-specific image format on FreeBSD. While it is possible to make it work, you may find yourself on a solo mission, as there are already OCI images available for FreeBSD. Others may prefer to use the native tools that are better suited for their needs. Based on the latest FreeBSD reports, I would like to inform you that there are two other tools available that support OCI and have their own centralized repositories. You may find your specific image on AppJail or Pot to help resolve your issue. Regarding Podman, it is designed specifically with Linux in mind, and using it on FreeBSD may not yield the best results. Others in this chat have indicated that it is not the right tool for your requirements in a FreeBSD environment. You are correct about the importance of saving time, which is one of the reasons why full OS virtualization exists on FreeBSD. If you are more familiar with a specific tool and image that only works on Linux, it may be worth considering a switch to Linux. If you prefer a homogeneous environment, you could run Linux on top of FreeBSD. However, the recommended solution is to use the native tools for OS-level virtualization on FreeBSD and to seek your image on AppJail, Pot, or other applications, or even contribute to building one.
well not really, podman is a cross platform tool that does things the docker way, as i like to say
Pouria
there is no native image for python oci image, only Linux and windows ones so i can't have native either way
AFAIK, there's no Windows container. There are only linux containers over hyper-v (WSL) on windows so still Linux specific.
Artel
there is "Windows Containers" that cook their own non-OCI thing
polyduekes
also there is nothing wrong with podman or lacking in any way as i get the feeling some here are trying to communicate to me
Pouria
Ok, on which application these windows containers could run?
polyduekes
there is "Windows Containers" that cook their own non-OCI thing
you can also run oci images with podman on windows without any linuxism or wsl :)