Re: OpenBSD Trademark Policy
On 07/12/14 09:35, Adam Thompson wrote: On 14-12-06 03:20 PM, Riley Baird wrote: Okay, I'll change the name. What I'm wondering is, which mentions of the OpenBSD name should I change? For example, you said before that the OpenBSD name may not be removed from the license headers of source files. So far, I can see that I would have to change the default motd, the installation scripts, Theo's welcome root mail and xdm. Is there anything that I have missed? You might want to ask on the BitRig mailing lists/forums/whatevers, since I believe they would have already had to tackle this. Thanks, I've looked through the Bitrig commit messages and I think that I've found what I'm looking for! If I actually get around to making the derivative, and I leave some mentions of OpenBSD where I shouldn't have, and this bothers the OpenBSD project, and someone tells me that it does, then I will be happy to correct it. :)
Re: OpenBSD Trademark Policy
On 07/12/14 09:05, Daniel Dickman wrote: On Sat, Dec 6, 2014 at 3:45 AM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: I have a few questions about OpenBSD's trademark policy. (I tried looking, but I couldn't find a document.) 1. What is OpenBSD's stance on allowing derivative distros to keep the name OpenBSD throughout the system? It's a ton of work to change the name. I'm curious why you want to create a derivative distro? Besides all kinds of subtle breakage in the base system, many ports will break/stop working properly. I agree entirely. For this reason, I think it would be best to keep system internals (e.g. uname, includes, etc.) using the name OpenBSD with only the main user-visible parts changed to a new name. As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included.
Re:
On Thu, 05 Jun 2014 22:36:37 -0600 Theo de Raadt dera...@cvs.openbsd.org wrote: There's something fairly weaselous about this all... this: didn't want to notify you. You might be right about OpenSSL maintainers (although I think you are not) - I just don't know, and can't speak for them - but at least for me (as someone who was notified via distros list) it appeared that you actually didn't want your team to be notified in a manner that would impose any restrictions on when you can commit a fix. So, believe it or not, it didn't even occur to me to put your project in a position where your folks would be asked to accept an embargo, which you didn't want. is not a technical discussion. It is about the politics being imposed up open systems. Would you like me to suggest What I'd like to suggest is that counsel not meant for all ears is worthy of none. Dhu (good call, T) -- Ne obliviscaris, vix ea nostra voco.
Re: OpenBSD Trademark Policy
On Sun, Dec 07, 2014 at 07:35:03PM +1100, Riley Baird wrote: As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. What exactly do you mean by that?
Re: OpenBSD Trademark Policy
On 12/07/14 03:35, Riley Baird wrote: As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. Doesn't really make any sense why. But either way hopefully you're not using common hardware like AMD GPUs or Intel Wifi otherwise that is pretty crippling. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: OpenBSD Trademark Policy
On 07/12/14 19:53, Kaspars Bankovskis wrote: On Sun, Dec 07, 2014 at 07:35:03PM +1100, Riley Baird wrote: As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. What exactly do you mean by that? Look in sys/dev/microcode. This is the firmware required for some devices to operate, and is loaded into the device on boot. It is clear that this was not written in assembly; rather, it has been compiled, and we are only getting the output. You could argue that this is better than hardware where the firmware is physically on the hardware, because at least the blobs we load onto the hardware can be reverse engineered, and to a certain degree you would be right. Except nobody actually reverse engineers them. ath9k for Linux has open-source firmware thanks to atheros, and this has actually been modified for various interesting applications.
Re: OpenBSD Trademark Policy
On 07/12/14 19:59, Brad Smith wrote: On 12/07/14 03:35, Riley Baird wrote: As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. Doesn't really make any sense why. But either way hopefully you're not using common hardware like AMD GPUs or Intel Wifi otherwise that is pretty crippling. I'd personally rather choose to activate a device that required binary-only firmware after realising that it doesn't work, because at least then I know what I'm getting myself into. I had Intel Wifi for a period of time on Debian, and I had to install the package for it myself. I'd always felt uneasy about it, and now whenever I buy wireless hardware for Linux, I ensure that I'll buy one that will work with the open ath9k. That being said, this should be less of a problem with OpenBSD, since a large portion of its use is in server applications, when you should really be using ethernet anyway.
Re: OpenBSD Trademark Policy
Riley Baird said:
As for why I want to create the distro, I think that OpenBSD has
excellent security, and I would like to create a version without the
binary-only microcode included.
Isn't it easier to just do
# cd /mnt/etc; tar czf firmware{.tgz,}; rm -R firmware
from bsd.rd after installer exits?
--
Dmitrij D. Czarkoff
Re: OpenBSD Trademark Policy
On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
Riley Baird said:
As for why I want to create the distro, I think that OpenBSD has
excellent security, and I would like to create a version without the
binary-only microcode included.
Isn't it easier to just do
# cd /mnt/etc; tar czf firmware{.tgz,}; rm -R firmware
from bsd.rd after installer exits?
Yes, it definitely would be. You'd also need to change the installer
script such that fw_update is not run on first boot. I've removed the
firmware from my own system already. Also, it would be nice to be able
to build the source tree without requiring the firmware files to exist.
However, remember that if someone doesn't know much about OpenBSD, they
will either: a) think that OpenBSD does not contain binary-only firmware
due to the Blob-Busters marketing or b) not know where to look to
remove it should they wish to
Re: OpenBSD Trademark Policy
Hi, Riley, On Sun, Dec 7, 2014 at 5:35 PM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: On 07/12/14 09:05, Daniel Dickman wrote: On Sat, Dec 6, 2014 at 3:45 AM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: I have a few questions about OpenBSD's trademark policy. (I tried looking, but I couldn't find a document.) 1. What is OpenBSD's stance on allowing derivative distros to keep the name OpenBSD throughout the system? It's a ton of work to change the name. I'm curious why you want to create a derivative distro? Besides all kinds of subtle breakage in the base system, many ports will break/stop working properly. I agree entirely. For this reason, I think it would be best to keep system internals (e.g. uname, includes, etc.) using the name OpenBSD with only the main user-visible parts changed to a new name. Don't think too far ahead. but do talk to a lawyer if you decide to try to publish a derivative. (I think you do understand that you have to leave the opyright notices as they are, but that's not the worst of the problems. If you have the money for an hour or two of consultation, you should find a good lawyer to talk it over with. Won't solve every problem, but it will leave you in a better position to seek solutions.) As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. The openbsd team has a pretty good track record at deciding which binary blobs can be put up with. They also have a relatively good track record with persuading companies to open up their source. Relatively. :-( I'm not sure, but I'd guess no one else in the libre/opensource community can claim a better record. -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: OpenBSD Trademark Policy
On Sun, Dec 07, 2014 at 08:29:48PM +1100, Riley Baird wrote:
On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
Riley Baird said:
As for why I want to create the distro, I think that OpenBSD has
excellent security, and I would like to create a version without the
binary-only microcode included.
Isn't it easier to just do
# cd /mnt/etc; tar czf firmware{.tgz,}; rm -R firmware
from bsd.rd after installer exits?
Yes, it definitely would be. You'd also need to change the installer
script such that fw_update is not run on first boot. I've removed the
firmware from my own system already. Also, it would be nice to be able
to build the source tree without requiring the firmware files to exist.
However, remember that if someone doesn't know much about OpenBSD, they
will either: a) think that OpenBSD does not contain binary-only firmware
due to the Blob-Busters marketing or b) not know where to look to
remove it should they wish to
The blobs we do not like are pieces of code running inside the kernel.
Code running on a device is a completely different category.
-Otto
Re: OpenBSD Trademark Policy
On 12/07/14 04:29, Riley Baird wrote: However, remember that if someone doesn't know much about OpenBSD, they will either: a) think that OpenBSD does not contain binary-only firmware due to the Blob-Busters marketing or b) not know where to look to remove it should they wish to Your interpretation of the marketing is flawed. The marketing about blobs was about device drivers in the kernel only. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: OpenBSD Trademark Policy
I have a few questions about OpenBSD's trademark policy. (I tried looking, but I couldn't find a document.) 1. What is OpenBSD's stance on allowing derivative distros to keep the name OpenBSD throughout the system? It's a ton of work to change the name. I'm curious why you want to create a derivative distro? Besides all kinds of subtle breakage in the base system, many ports will break/stop working properly. I agree entirely. For this reason, I think it would be best to keep system internals (e.g. uname, includes, etc.) using the name OpenBSD with only the main user-visible parts changed to a new name. Don't think too far ahead. but do talk to a lawyer if you decide to try to publish a derivative. (I think you do understand that you have to leave the opyright notices as they are, but that's not the worst of the problems. If you have the money for an hour or two of consultation, you should find a good lawyer to talk it over with. Won't solve every problem, but it will leave you in a better position to seek solutions.) I see your point, but I'm just wondering - if you are recommending that I get a lawyer, is that because such a distro would upset the OpenBSD community so much that someone would try to take legal action against me? I don't want to do anything that would hurt the community, so if feelings about this are that strong, then I won't do it. But really, I think that taking legal action over something like this is an overreaction. As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. The openbsd team has a pretty good track record at deciding which binary blobs can be put up with. They also have a relatively good track record with persuading companies to open up their source. Relatively. :-( I'm not sure, but I'd guess no one else in the libre/opensource community can claim a better record. Agreed. Thanks for that! (Especially, I like Theo's method of screaming at manufacturers - because surprisingly, it *actually worked*.)
Re: OpenBSD Trademark Policy
On 07/12/14 20:52, Otto Moerbeek wrote:
On Sun, Dec 07, 2014 at 08:29:48PM +1100, Riley Baird wrote:
On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
Riley Baird said:
As for why I want to create the distro, I think that OpenBSD has
excellent security, and I would like to create a version without the
binary-only microcode included.
Isn't it easier to just do
# cd /mnt/etc; tar czf firmware{.tgz,}; rm -R firmware
from bsd.rd after installer exits?
Yes, it definitely would be. You'd also need to change the installer
script such that fw_update is not run on first boot. I've removed the
firmware from my own system already. Also, it would be nice to be able
to build the source tree without requiring the firmware files to exist.
However, remember that if someone doesn't know much about OpenBSD, they
will either: a) think that OpenBSD does not contain binary-only firmware
due to the Blob-Busters marketing or b) not know where to look to
remove it should they wish to
The blobs we do not like are pieces of code running inside the kernel.
Code running on a device is a completely different category.
True, but the press releases never even mentioned the microcode, which
is kind of confusing given the normal usage of the word binary blob.
I realise that this usage may have been propagated by the FSF, and on
many, many things they are insane (e.g. OpenBSD's ports tree, the GFDL),
but given that - for better or for worse - firmware is included in the
common usage of the word, it would make sense to clarify.
Re: OpenBSD Trademark Policy
On 12/07/14 05:18, Riley Baird wrote:
On 07/12/14 20:52, Otto Moerbeek wrote:
On Sun, Dec 07, 2014 at 08:29:48PM +1100, Riley Baird wrote:
On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
Riley Baird said:
As for why I want to create the distro, I think that OpenBSD has
excellent security, and I would like to create a version without the
binary-only microcode included.
Isn't it easier to just do
# cd /mnt/etc; tar czf firmware{.tgz,}; rm -R firmware
from bsd.rd after installer exits?
Yes, it definitely would be. You'd also need to change the installer
script such that fw_update is not run on first boot. I've removed the
firmware from my own system already. Also, it would be nice to be able
to build the source tree without requiring the firmware files to exist.
However, remember that if someone doesn't know much about OpenBSD, they
will either: a) think that OpenBSD does not contain binary-only firmware
due to the Blob-Busters marketing or b) not know where to look to
remove it should they wish to
The blobs we do not like are pieces of code running inside the kernel.
Code running on a device is a completely different category.
True, but the press releases never even mentioned the microcode, which
is kind of confusing given the normal usage of the word binary blob.
Blobs are vendor-compiled binary drivers without any source code.
That couldn't be more clear what the projects meaning of blobs is.
Microcode won't be mentioned when it is already pretty clear what the
meaning is. Nothing to be confused about there at all. That is your
interpretation of the meaning and not the common use.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: OpenBSD Trademark Policy
On 07/12/14 21:32, Brad Smith wrote:
On 12/07/14 05:18, Riley Baird wrote:
On 07/12/14 20:52, Otto Moerbeek wrote:
On Sun, Dec 07, 2014 at 08:29:48PM +1100, Riley Baird wrote:
On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
Riley Baird said:
As for why I want to create the distro, I think that OpenBSD has
excellent security, and I would like to create a version without the
binary-only microcode included.
Isn't it easier to just do
# cd /mnt/etc; tar czf firmware{.tgz,}; rm -R firmware
from bsd.rd after installer exits?
Yes, it definitely would be. You'd also need to change the installer
script such that fw_update is not run on first boot. I've removed the
firmware from my own system already. Also, it would be nice to be able
to build the source tree without requiring the firmware files to exist.
However, remember that if someone doesn't know much about OpenBSD, they
will either: a) think that OpenBSD does not contain binary-only
firmware
due to the Blob-Busters marketing or b) not know where to look to
remove it should they wish to
The blobs we do not like are pieces of code running inside the kernel.
Code running on a device is a completely different category.
True, but the press releases never even mentioned the microcode, which
is kind of confusing given the normal usage of the word binary blob.
Blobs are vendor-compiled binary drivers without any source code.
That couldn't be more clear what the projects meaning of blobs is.
Microcode won't be mentioned when it is already pretty clear what the
meaning is. Nothing to be confused about there at all. That is your
interpretation of the meaning and not the common use.
Since I interpreted the meaning incorrectly, it is likely that others
did as well. In any case, I'm sure that we can all agree that ideally
the microcode would come with source. Some people are going to take that
idealism further, and decide not to use the microcode. I don't see the
harm in helping these people, whether it be through a derivative distro,
or even a question in the installation scripts. (I wrote a patch for an
installer question a couple of months ago, if you're interested.)
Re: OpenBSD Trademark Policy
On Sun, Dec 7, 2014 at 7:09 PM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: I have a few questions about OpenBSD's trademark policy. (I tried looking, but I couldn't find a document.) 1. What is OpenBSD's stance on allowing derivative distros to keep the name OpenBSD throughout the system? It's a ton of work to change the name. I'm curious why you want to create a derivative distro? Besides all kinds of subtle breakage in the base system, many ports will break/stop working properly. I agree entirely. For this reason, I think it would be best to keep system internals (e.g. uname, includes, etc.) using the name OpenBSD with only the main user-visible parts changed to a new name. Don't think too far ahead. but do talk to a lawyer if you decide to try to publish a derivative. (I think you do understand that you have to leave the opyright notices as they are, but that's not the worst of the problems. If you have the money for an hour or two of consultation, you should find a good lawyer to talk it over with. Won't solve every problem, but it will leave you in a better position to seek solutions.) I see your point, but I'm just wondering - if you are recommending that I get a lawyer, is that because such a distro would upset the OpenBSD community so much that someone would try to take legal action against me? That's not what I'm thinking about, no. (But I am not a voice for this community, either.) Intellectual property is easy to get confused by, in no small part because the current laws and practices are essentially attempting to undo several centuries of progress making laws and reality match. Sometimes you do what seems to make sense and it has the opposite effect of what you intended. I don't want to do anything that would hurt the community, so if feelings about this are that strong, then I won't do it. But really, I think that taking legal action over something like this is an overreaction. As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. The openbsd team has a pretty good track record at deciding which binary blobs can be put up with. They also have a relatively good track record with persuading companies to open up their source. Relatively. :-( I'm not sure, but I'd guess no one else in the libre/opensource community can claim a better record. Agreed. Thanks for that! (Especially, I like Theo's method of screaming at manufacturers - because surprisingly, it *actually worked*.) That's not quite the way I remember it. I would rather describe it as use of diplomacy. -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: OpenBSD Trademark Policy
On 07/12/14 21:51, Joel Rees wrote: On Sun, Dec 7, 2014 at 7:09 PM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: I have a few questions about OpenBSD's trademark policy. (I tried looking, but I couldn't find a document.) 1. What is OpenBSD's stance on allowing derivative distros to keep the name OpenBSD throughout the system? It's a ton of work to change the name. I'm curious why you want to create a derivative distro? Besides all kinds of subtle breakage in the base system, many ports will break/stop working properly. I agree entirely. For this reason, I think it would be best to keep system internals (e.g. uname, includes, etc.) using the name OpenBSD with only the main user-visible parts changed to a new name. Don't think too far ahead. but do talk to a lawyer if you decide to try to publish a derivative. (I think you do understand that you have to leave the opyright notices as they are, but that's not the worst of the problems. If you have the money for an hour or two of consultation, you should find a good lawyer to talk it over with. Won't solve every problem, but it will leave you in a better position to seek solutions.) I see your point, but I'm just wondering - if you are recommending that I get a lawyer, is that because such a distro would upset the OpenBSD community so much that someone would try to take legal action against me? That's not what I'm thinking about, no. (But I am not a voice for this community, either.) Intellectual property is easy to get confused by, in no small part because the current laws and practices are essentially attempting to undo several centuries of progress making laws and reality match. Sometimes you do what seems to make sense and it has the opposite effect of what you intended. I really can't afford a lawyer. Which is really unfortunate, because it would probably make the situation clearer. I don't want to do anything that would hurt the community, so if feelings about this are that strong, then I won't do it. But really, I think that taking legal action over something like this is an overreaction. As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. The openbsd team has a pretty good track record at deciding which binary blobs can be put up with. They also have a relatively good track record with persuading companies to open up their source. Relatively. :-( I'm not sure, but I'd guess no one else in the libre/opensource community can claim a better record. Agreed. Thanks for that! (Especially, I like Theo's method of screaming at manufacturers - because surprisingly, it *actually worked*.) That's not quite the way I remember it. I would rather describe it as use of diplomacy. I was trying to give a compliment, not an insult :) I'll save my insults for later :P This is kind of unrelated, but Torvalds gave Nvidia the finger and said Nvidia, fuck you during a speech because of binary drivers: http://www.wired.com/2012/06/torvalds-nvidia-linux/ Now, Nvidia is starting to contribute to the open-source Nouveau driver project.
Re: OpenBSD Trademark Policy
On Sun, Dec 7, 2014 at 8:31 PM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: On 07/12/14 21:51, Joel Rees wrote: On Sun, Dec 7, 2014 at 7:09 PM, Riley Baird [...] I see your point, but I'm just wondering - if you are recommending that I get a lawyer, is that because such a distro would upset the OpenBSD community so much that someone would try to take legal action against me? That's not what I'm thinking about, no. (But I am not a voice for this community, either.) Intellectual property is easy to get confused by, in no small part because the current laws and practices are essentially attempting to undo several centuries of progress making laws and reality match. Sometimes you do what seems to make sense and it has the opposite effect of what you intended. I really can't afford a lawyer. Which is really unfortunate, because it would probably make the situation clearer. Well anyway, you probably want to spend some time reading up on the subject. Wikipedia, at any particular point in time, is not a bad place to start, but it's definitely not a good place to end. You need to read actually law and case studies to start seeing what really happens, and to start forming useful opinions about what it all means and testing your ideas against the legal record. Kind of like learning to read code. [...] I would rather describe it as use of diplomacy. I was trying to give a compliment, not an insult :) I'll save my insults for later :P This is kind of unrelated, but Torvalds gave Nvidia the finger and said Nvidia, fuck you during a speech because of binary drivers: http://www.wired.com/2012/06/torvalds-nvidia-linux/ Now, Nvidia is starting to contribute to the open-source Nouveau driver project. I think we see the dramatic moments and tend to forget about the build-up and the follow-up, where the real diplomacy gets applied. That's where the work is really done, and, of course, it's not just Theo and Linus at work. Lots of people helping. -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: OpenBSD Trademark Policy
2014-12-06 9:45 GMT+01:00 Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch: I have a few questions about OpenBSD's trademark policy. (I tried looking, but I couldn't find a document.) Is OpenBSD actually a registered trademark? The USPTO doesn't list it. FreeBSD is, though. Best Martin
Re: OpenBSD Trademark Policy
Your changes to the system will be very small, and most of the time you'll be just renaming 'openbsd' to something else, and syncing back changes from upstream. If you have time for that, lucky you. But there are more useful things to do, don't you think so?
Re: segmentation fault during package build
Hi, Miod Vallat wrote: I can confirm the spurious segmentation faults or `double free' issues with an SM40 module, and I am currently investigating the issue. Fine. That means that using the SM40 instead of the SM50 won't probably help. I will try though, just to be sure. They are both cache-less modules. What I found out is that apparently crashes change from reboot to reboot ad not in the same place. 1) compile, get a crash (appears ln most often for me) 2) reissue make, it will crash in the same place 3) reboot, reissue make, it will crash somewhere else! As soon as I have enough time (might be next week though) I will try the above again and again to see if it is consistent. Also, a method for reproducing it would be nice, just randomly building ports is not the best reproducible test case. Thanks, Riccardo
Re: OpenBSD Trademark Policy
On Sun, Dec 07, 2014 at 07:35:03PM +1100, Riley Baird wrote: I agree entirely. For this reason, I think it would be best to keep system internals (e.g. uname, includes, etc.) using the name OpenBSD with only the main user-visible parts changed to a new name. As for why I want to create the distro, I think that OpenBSD has excellent security, and I would like to create a version without the binary-only microcode included. This is silly, all the firmware in /etc/firmware allows free distribution and what isn't is installed via fw_update(1). You can easily pkg_delete what you don't like. If you're worried about scary evil Microcode, then you probably shouldn't run a modern Intel or AMD machine, not including all the firmware on flash or ROM, your BIOS likely loaded CPU microcode that is almost entirely undocumented magic. Hilarious.. -Bryan.
Re: OpenBSD Trademark Policy
At 7 Dec 2014 12:42:41 + (UTC) from Kaspars Bankovskis kasp...@bankovskis.net: there are more useful things to do, don't you think so? Agree. Riley, I think you don't get the point here. The firmware blob are *not* running on the system, but on device. Why do you don't create just a script to remove these's files if you want? Why create a entire new system for this?
Re: OpenBSD Trademark Policy
Riley Baird said: However, remember that if someone doesn't know much about OpenBSD, they will either: a) think that OpenBSD does not contain binary-only firmware due to the Blob-Busters marketing or b) not know where to look to remove it should they wish to This information is easily available to anyone interested via online manual pages for affected drivers. If user is not knowledgable enough to verify whether his hardware can be used without proprietary firmware, you are doing misservice. P.S.: how are you going to cope with hardware that already contains firmware and does not require loading it at initialization time? Or is this kind of firmware OK according to your definition of free? -- Dmitrij D. Czarkoff
Proposed patch to unmute Azalia sound card on Compaq 610
Greetings,
Some days ago I installed OBSD 5.6 on my old Compaq 610 laptop (a pretty
standard CORE2 Duo 2010 machine - yes, I know that standard is a
kind of hard concept in the i386/amd64 world...), dmesg in [1].
Great hardware support, except that sound card was completely silent
(dmesg with AZALIA_DEBUG in [2], mixerctrl in [3], audioctl in [4]).
I played a bit with the parameters, trying to follow some advices
discussed on this list in the past, with no success.
Quick trials in both FreeBSD (10.1 and 11-current) and NetBSD (6.5.1)
revealed a working sound out of the box, confirming the well established
support for this model.
Long story short, I had a look at the code and ended up with the
following patch which makes my sound card working in OpenBSD too:
--- ./sys/dev/pci/azalia_codec.cFri Dec 5 21:06:18 2014
+++ ./sys/dev/pci/azalia_codec.c.patchedFri Dec 5 21:08:02 2014
@@ -182,6 +182,10 @@
break;
case 0x111d7608:
this-name = IDT 92HD75B1/2;
+ if ((this-subid 0x) == 0x103c) { /* HP */
+ this-qrks |= AZ_QRK_GPIO_UNMUTE_0;
+ }
break;
case 0x111d7674:
this-name = IDT 92HD73D1;
Of course, I don't know if this is very machine specific or instead
it could be of general interest; I'm writing here just in case someone
had the same problem or the developers consider it useful to add
that upstream.
Hope this can help
All the best
[1]
OpenBSD 5.6-stable (GENERIC.MP) #1: Fri Dec 5 21:49:07 CET 2014
r...@icarus.atlantide.net:/builds/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3195731968 (3047MB)
avail mem = 3101937664 (2958MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf284b (25 entries)
bios0: vendor Hewlett-Packard version 68PVU Ver. F.08 date 09/24/2009
bios0: Hewlett-Packard Compaq 610
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC HPET APIC MCFG TCPA SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices C0B6(S5) C10E(S3) C115(S3) C116(S3) C117(S3) C121(S3)
C123(S3) C139(S5) C2AB(S5) C13C(S5) C2AC(S5) C13D(S5) C13F(S5) C247(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz, 2194.81 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 2MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz, 1995.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu1: 2MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 2 (C0B6)
acpiprt1 at acpi0: bus 8 (C125)
acpiprt2 at acpi0: bus 16 (C139)
acpiprt3 at acpi0: bus 40 (C13C)
acpiprt4 at acpi0: bus 48 (C13D)
acpiprt5 at acpi0: bus 0 (C003)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: C27C, resource for C277
acpipwrres1 at acpi0: C289, resource for C27D
acpipwrres2 at acpi0: C2A5, resource for C2A3
acpipwrres3 at acpi0: C1CE, resource for C13E
acpipwrres4 at acpi0: C3C1, resource for C3C6
acpipwrres5 at acpi0: C3C2, resource for C3C7
acpipwrres6 at acpi0: C3C3, resource for C3C8
acpipwrres7 at acpi0: C3C4, resource for C3C9
acpipwrres8 at acpi0: C3C5, resource for C3CA
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 107 degC
acpitz2 at acpi0: critical temperature is 110 degC
acpitz3 at acpi0: critical temperature is 256 degC
acpitz4 at acpi0: critical temperature is 107 degC
acpibat0 at acpi0: C245 model Primary serial 01223 2009/10/04 type LIon oem
Hewlett-Packard
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: C2BE
acpibtn1 at acpi0: C15B
acpivideo0 at acpi0: C09E
acpivout0 at acpivideo0: C1B5
cpu0: Enhanced SpeedStep 2194 MHz: speeds: 2001, 2000, 1600, 1200, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel GME965 Host rev 0x0c
vga1 at pci0 dev 2 function 0 Intel GME965 Video rev 0x0c
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1366x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
Re: OpenBSD Trademark Policy
On 14-12-07 06:37 AM, Martin Schröder wrote: Is OpenBSD actually a registered trademark? The USPTO doesn't list it. FreeBSD is, though. The answer appears to be no, as CIPO doesn't list it, either. My guess is that keeping the lights on (literally) was a higher priority than paying the annual registration fee. I'm reasonably confident that if someone were to step up to not only fund the trademark application (looks like $500/yr /in perpetuity/ in IPO fees alone???), but find a trademark agent willing to do the work /pro bono/, and spend the time filling out the paperwork, etc. etc., etc. then it could probably happen fairly rapidly. I believe it would have to be done through the Canadian office (http://cipo.gc.ca/) since both Theo and the Foundation are based in Canada. AFAIK Canada does not yet comply with the Madrid Protocol, the Nice Agreement or the Singapore Treaty, so that registration would only be good in Canada. An international application would probably be best done through the USPTO, which incurs similar costs. Also, where do you stop? Does the logo need to be protected as well? What about the dæmon character? Or the audio track for every release? The source code is, I think, the only thing that's obvious - both the BSD license and years of jurisprudence about that license establish its situation. -- -Adam Thompson athom...@athompso.net
apmd.8 lacks of hibernation quirks info
Greetings, With OpenBSD 5.6 release, I finally have a pretty functional (and usable) hibernation function (not on all my hardware, but at least for a not-so-recent HP laptop it works!). I was digging into my scripts in order to apply some quirks before hibernating the machine, and noticed that the man page lacks some info. In particular, the code already support a specific file to be executed before entering the S4 state (/etc/apm/hibernate), even if uses the same file (/etc/apm/resume) after resuming from both S3 and S4 (if my understanding is wrong, please correct me). So: 1) a proposed patch for the man page (as per the 5.6 code): --- ./usr.sbin/apmd/apmd.8 Thu Jul 24 03:04:58 2014 +++ ./usr.sbin/apmd/apmd.8.patched Sun Dec 7 17:47:58 2014 @@ -137,14 +137,15 @@ in the requested state after running the configuration script and flushing the buffer cache. .Pp -Actions can be configured for the following five transitions: +Actions can be configured for the following six transitions: suspend, +hibernate, standby, resume, powerup, and powerdown. -The suspend and standby actions are run prior to +The suspend, hibernate and standby actions are run prior to .Nm performing any other actions (such as disk syncs) and entering the new state. @@ -159,6 +160,7 @@ Default device used to control the APM kernel driver. .Pp .It /etc/apm/suspend +.It /etc/apm/hibernate .It /etc/apm/standby .It /etc/apm/resume .It /etc/apm/powerup @@ -169,6 +171,7 @@ by examining the name by which it was called, which is one of suspend, +hibernate, standby, resume, powerup, 2) a question: why two different files for entering suspend/hibernate states, but only one for resuming? At the moment, I do not apply any quirks on resume, but having the possibility to differentiate b/w S3 and S4 wake-up could be useful in some corner cases. Thanks in advance for your time. -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: OpenBSD Trademark Policy
On Sun, 07 Dec 2014 09:37:13 -0600 Adam Thompson athom...@athompso.net wrote: On 14-12-07 06:37 AM, Martin Schröder wrote: Is OpenBSD actually a registered trademark? The USPTO doesn't list it. FreeBSD is, though. The answer appears to be no, as CIPO doesn't list it, either. My guess is that keeping the lights on (literally) was a higher priority than paying the annual registration fee. I'm reasonably confident that if someone were to step up to not only fund the trademark application (looks like $500/yr /in perpetuity/ in IPO fees alone???), but find a trademark agent willing to do the work /pro bono/, and spend the time filling out the paperwork, etc. etc., etc. then it could probably happen fairly rapidly. It's not $500/year. You need to pay a registration fee, then I think 5 or 6 years later submit an application that you're still using it, then every 10 years after that, renew. Something like that, anyway. IIRC each of these is somewhere in the $500 ballpark, but they don't happen every year. Legal fees vary according to difficulty. Obshrenkoroid would be much easier to trademark than Troubleshooters.Com (reg #s 2984611 and 2210851), which in turn is much easier to trademark than Radio. I'd imagine a resourceful person could read a bunch of trademark apps on USPTO.gov, and then do the Obshrenkoroid trademark him/herself. I'd imagine that you'd need some pretty good lawyers spending a lot of time to trademark Radio for almost any purpose. I spoze theoretically you could trademark Radio brand dog food, but it wouldn't be easy. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance
man afterboot - discouraging usage of space characters in root password
Hi all, I would like to ask what is the reason for man afterboot discouraging the usage of the space character in root passwords. Root password Change the password for the root user. (Note that throughout the documentation, the term ``superuser'' is a synonym for the root user.) Choose a password that has digits and special characters *(not space)* as well as from the upper and lower case alphabet. Is there a reason for '(not space)' being included in that passage? The passwd utility seems pretty happy taking up the space character. Was it not the case in the past? Regards, -- Adam Wolk adam.w...@koparo.com
Re: OpenBSD Trademark Policy
Adam Thompson athom...@athompso.net writes: On 14-12-07 06:37 AM, Martin Schröder wrote: Is OpenBSD actually a registered trademark? The USPTO doesn't list it. FreeBSD is, though. The answer appears to be no, as CIPO doesn't list it, either. My guess is that keeping the lights on (literally) was a higher priority than paying the annual registration fee. I'm reasonably confident that if someone were to step up to not only fund the trademark application (looks like $500/yr /in perpetuity/ in IPO fees alone???), but find a trademark agent willing to do the work /pro bono/, and spend the time filling out the paperwork, etc. etc., etc. then it could probably happen fairly rapidly. I believe it would have to be done through the Canadian office (http://cipo.gc.ca/) since both Theo and the Foundation are based in Canada. AFAIK Canada does not yet comply with the Madrid Protocol, the Nice Agreement or the Singapore Treaty, so that registration would only be good in Canada. An international application would probably be best done through the USPTO, which incurs similar costs. For the record, I get enough use out of OpenBSD that in case Mr. De Raadt (or some other appropriate person from the OpenBSD Foundation) desires me to do so, I am happy to research and shepherd the OpenBSD trademark in the US; although I am not currently familiar with USPTO regulations/procedures in general, I have considerable experience dealing with bureaucracy--formerly, I was a member of the US Army and I worked for around five years as an employee of a state government, and was specifically tasked in both instances with interpreting (and in some cases, writing) bureaucratic policy. (I work for a private company now, and am much, MUCH happier.) I am not, however, willing to pay the required fees out of my own account, without reimbursement. I have five children who must, in fact, be fed, it turns out. Carson
Re: man afterboot - discouraging usage of space characters in root password
Hi Adam, Le 07/12/2014 19:30, Adam Wolk a écrit : Hi all, I would like to ask what is the reason for man afterboot discouraging the usage of the space character in root passwords. Root password Change the password for the root user. (Note that throughout the documentation, the term ``superuser'' is a synonym for the root user.) Choose a password that has digits and special characters *(not space)* as well as from the upper and lower case alphabet. Is there a reason for '(not space)' being included in that passage? The passwd utility seems pretty happy taking up the space character. Was it not the case in the past? Regards, I think that it means that you can use it but not as a special character. I could be wrong but this is what I understood. Mxher
Re: apmd.8 lacks of hibernation quirks info
On Sun, Dec 07, 2014 at 06:05:16PM +0100, Alessandro DE LAURENZIS wrote: Greetings, With OpenBSD 5.6 release, I finally have a pretty functional (and usable) hibernation function (not on all my hardware, but at least for a not-so-recent HP laptop it works!). Which machines don't work, and how do they break? I would like to know. Please file a bug report (man sendbug). Thanks. -ml I was digging into my scripts in order to apply some quirks before hibernating the machine, and noticed that the man page lacks some info. In particular, the code already support a specific file to be executed before entering the S4 state (/etc/apm/hibernate), even if uses the same file (/etc/apm/resume) after resuming from both S3 and S4 (if my understanding is wrong, please correct me). So: 1) a proposed patch for the man page (as per the 5.6 code): --- ./usr.sbin/apmd/apmd.8Thu Jul 24 03:04:58 2014 +++ ./usr.sbin/apmd/apmd.8.patchedSun Dec 7 17:47:58 2014 @@ -137,14 +137,15 @@ in the requested state after running the configuration script and flushing the buffer cache. .Pp -Actions can be configured for the following five transitions: +Actions can be configured for the following six transitions: suspend, +hibernate, standby, resume, powerup, and powerdown. -The suspend and standby actions are run prior to +The suspend, hibernate and standby actions are run prior to .Nm performing any other actions (such as disk syncs) and entering the new state. @@ -159,6 +160,7 @@ Default device used to control the APM kernel driver. .Pp .It /etc/apm/suspend +.It /etc/apm/hibernate .It /etc/apm/standby .It /etc/apm/resume .It /etc/apm/powerup @@ -169,6 +171,7 @@ by examining the name by which it was called, which is one of suspend, +hibernate, standby, resume, powerup, 2) a question: why two different files for entering suspend/hibernate states, but only one for resuming? At the moment, I do not apply any quirks on resume, but having the possibility to differentiate b/w S3 and S4 wake-up could be useful in some corner cases. Thanks in advance for your time. -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
fatal page fault in supervisor mode
Hi list, I've got this error and I don't what it is about. Is something wrong with my hardware, like RAM? Could someone point me in right direction to resolve this error? Dec 7 11:35:33 gw /bsd: uvm_fault(0xd0a2, 0xcfc0, 0, 3) - e Dec 7 11:35:33 gw /bsd: fatal page fault (6) in supervisor mode Dec 7 11:35:33 gw /bsd: trap type 6 code 2 eip d056f4a8 cs 50 eflags 210256 cr2 cfc0 cpl 40 Dec 7 11:35:33 gw /bsd: panic: trap type 6, code=2, pc=d056f4a8 Dec 7 11:35:33 gw /bsd: Starting stack trace... Dec 7 11:35:33 gw /bsd: panic(d08d35a6,dc7deabc,d08d6f9e,dc7deabc,2) at panic+0x6a Dec 7 11:35:33 gw /bsd: panic(d08d6f9e,6,2,d056f4a8,50) at panic+0x6a Dec 7 11:35:33 gw /bsd: trap() at trap+0x38f Dec 7 11:35:33 gw /bsd: --- trap (number -809500672) --- Dec 7 11:35:33 gw /bsd: 0x2: Dec 7 11:35:33 gw /bsd: End of stack trace. Dec 7 11:35:33 gw /bsd: panic: mtx_enter: locking against myself Dec 7 11:35:33 gw /bsd: Starting stack trace... Dec 7 11:35:33 gw /bsd: panic(d08d35a6,dc7de72c,dc7de720,d020476c,c0) at panic+0x6a Dec 7 11:35:33 gw /bsd: panic(d02036a2,dc7de75c,d03ee791,d0a181a0,17) at panic+0x6a Dec 7 11:35:33 gw /bsd: mtx_enter(d0a181a0,17,d0a162c0,dc7de780,d02043fc) at mtx_enter+0x62 Dec 7 11:35:33 gw /bsd: pool_get(d0a181a0,2,d6872a18,dc7de8f8,2) at pool_get+0x31 Dec 7 11:35:33 gw /bsd: pf_test_rule(dc7de8d0,dc7de8cc,1,d1ea3900,dc8dab00) at pf_test_rule+0x1ab9 Dec 7 11:35:33 gw /bsd: pf_test(2,1,d1eba030,dc7de9d4,0) at pf_test+0xd4c Dec 7 11:35:33 gw /bsd: ipv4_input(dc8dab00,6,dc7de9ec,d0445b55,d0203776) at ipv4_input+0x20c Dec 7 11:35:33 gw /bsd: ipintr(d0203776,d1e98440,dc7dea0c,d057569f,0) at ipintr+0x73 Dec 7 11:35:33 gw /bsd: netintr(0,200292,0,0,d0202232) at netintr+0xc5 Dec 7 11:35:33 gw /bsd: softintr_dispatch(1) at softintr_dispatch+0x4f Dec 7 11:35:33 gw /bsd: Xsoftnet() at Xsoftnet+0x17 Dec 7 11:35:33 gw /bsd: --- interrupt --- Dec 7 11:35:33 gw /bsd: end(100,dc7deabc,d08d6f9e,dc7deabc,2) at 0xdc7deabc Dec 7 11:35:33 gw /bsd: panic(d08d6f9e,6,2,d056f4a8,50) at panic+0x65 Dec 7 11:35:33 gw /bsd: trap() at trap+0x38f Dec 7 11:35:33 gw /bsd: --- trap (number -809500672) --- Dec 7 11:35:33 gw /bsd: 0x2: Dec 7 11:35:33 gw /bsd: End of stack trace. Dec 7 11:35:33 gw /bsd: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 Dec 7 11:35:33 gw /bsd:    dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP Dec 7 11:35:33 gw /bsd: cpu0: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (GenuineIntel 686-class) 2 GHz Dec 7 11:35:33 gw /bsd: cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM Dec 7 11:35:33 gw /bsd: real mem = 1064431616 (1015MB) Dec 7 11:35:33 gw /bsd: avail mem = 1036947456 (988MB) Dec 7 11:35:33 gw /bsd: mainbus0 at root Dec 7 11:35:33 gw /bsd: bios0 at mainbus0: AT/286+ BIOS, date 08/12/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0x9f800 (28 entries) Dec 7 11:35:33 gw /bsd: bios0: vendor American Megatrends Inc. version 080014 date 08/12/2008 Dec 7 11:35:33 gw /bsd: bios0: ICP / iEi KINO-9652 Dec 7 11:35:33 gw /bsd: acpi0 at bios0: rev 0 Dec 7 11:35:33 gw /bsd: acpi0: sleep states S0 S1 S4 S5 Dec 7 11:35:33 gw /bsd: acpi0: tables DSDT FACP APIC MCFG OEMB ASF! SSDT Dec 7 11:35:33 gw /bsd: acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) EUSB(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) HDAC(S4) USB4(S4) USB5(S4) USBE(S4) GBEC(S4) Dec 7 11:35:33 gw /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits Dec 7 11:35:33 gw /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT compat Dec 7 11:35:33 gw /bsd: cpu0 at mainbus0: apid 0 (boot processor) Dec 7 11:35:33 gw /bsd: cpu0: apic clock running at 201MHz Dec 7 11:35:33 gw /bsd: cpu1 at mainbus0: apid 1 (application processor) Dec 7 11:35:33 gw /bsd: cpu1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (GenuineIntel 686-class) 2.02 GHz Dec 7 11:35:33 gw /bsd: cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM Dec 7 11:35:33 gw /bsd: ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins Dec 7 11:35:33 gw /bsd: acpimcfg0 at acpi0 addr 0xe000, bus 0-255 Dec 7 11:35:33 gw /bsd: acpiprt0 at acpi0: bus 0 (PCI0) Dec 7 11:35:33 gw /bsd: acpiprt1 at acpi0: bus -1 (P0P2) Dec 7 11:35:33 gw /bsd: acpiprt2 at acpi0: bus 1 (P0P1) Dec 7 11:35:33 gw /bsd: acpiprt3 at acpi0: bus 2 (P0P4) Dec 7 11:35:33 gw /bsd: acpiprt4 at acpi0: bus 3 (P0P5) Dec 7 11:35:33 gw /bsd: acpiprt5 at acpi0: bus -1 (P0P6) Dec 7 11:35:33 gw /bsd: acpiprt6 at acpi0: bus -1 (P0P7) Dec 7 11:35:33 gw /bsd: acpiprt7 at acpi0: bus -1 (P0P8) Dec 7 11:35:33 gw /bsd: acpiprt8 at acpi0: bus -1 (P0P9) Dec 7 11:35:33
Re: wsconsctl dislay.brightness stopped working after upgrade to 5.6
On Sat, Nov 15, 2014 at 02:30:26PM +0100, Frank Groeneveld wrote: I might be able to find out what change caused this regression if somebody can hint where to look. I've already crawled through most of the intel drm code, but I think this must be somewhere in the ACPI layer. Where should I look? Could somebody please give me a hint? Thanks, Frank
Re: fatal page fault in supervisor mode
On Sun, Dec 07, 2014 at 22:03, pavel pocheptsov wrote: Dec 7 11:35:33 gw /bsd: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 Honestly, this is way too old. There have been hundreds of bugs fixed since then.
Re: man afterboot - discouraging usage of space characters in root password
Am 12/07/14 um 19:30 schrieb Adam Wolk: Hi all, I would like to ask what is the reason for man afterboot discouraging the usage of the space character in root passwords. Root password Change the password for the root user. (Note that throughout the documentation, the term ``superuser'' is a synonym for the root user.) Choose a password that has digits and special characters *(not space)* as well as from the upper and lower case alphabet. Is there a reason for '(not space)' being included in that passage? The passwd utility seems pretty happy taking up the space character. Was it not the case in the past? Regards, Hi Adam, I have been asking exactly this question in June: http://marc.info/?l=openbsd-miscm=140388067802438w=2 Best, STEFAN
Re: OpenBSD Trademark Policy
I think the same, if running a command after installing it will make your system free enough, what is the need of a fork? I think that if you publish a web page with that information the OpenBSD community would not take that as an offense. I'm in the middle of leaving Debian after almost 15 years of using it, due to the systemd affair. And as you might guess it has not been easy, I have enough (personal) systems and experience invested to leave Debian only for a tantrum, but there is no easy way to install a new system and avoid systemd, and I guess this will become worse over time. Had I an one-command option to avoid or drop systemd, I might not be here. Best regards, Jorge. Luiz Roberto dos Santos arrowscr...@mail.com wrote: At 7 Dec 2014 12:42:41 + (UTC) from Kaspars Bankovskis kasp...@bankovskis.net: there are more useful things to do, don't you think so? Agree. Riley, I think you don't get the point here. The firmware blob are *not* running on the system, but on device. Why do you don't create just a script to remove these's files if you want? Why create a entire new system for this?
Re: OpenBSD Trademark Policy
After a private conversation with Theo, I've decided that I'm not going to respond to any of your emails for 4-6 days. You'll still get a response, but just not now. :)
Re: OpenBSD Trademark Policy
After a private conversation with Theo, I've decided that I'm not going to respond to any of your emails for 4-6 days. You'll still get a response, but just not now. :) Riley, you seem to take yourself far more seriously then the rest of us do.
iked CRL's
Anyone had any problems getting iked to adhere to revoked certificates? I can log in with a valid cert but can also log in using the same cert after it's been revoked using # ikectl ca vpn certificate xxx.xxx.xxx.xxx revoke . I tried restarting iked but it still behaved the same. Any suggestions would be appreciated. TIA
Re: Squid configuration
On Sat, Dec 6, 2014 at 9:20 AM, Stuart Henderson s...@spacehopper.org wrote:
On 2014-12-02, sven falempin sven.falem...@gmail.com wrote:
Hello,
I am more or less forced to test Squid.
OpenBSD test.my.domain 5.6 GENERIC.MP#333 amd64
I have two problems:
WARNING! Your cache is running out of filedescriptors
And probably have to read more about ICAP
suspending ICAP service for too many failures
My question is about the fds,
i tried to add
squid:\
:openfiles-cur=4096:\
:tc=daemon:
Follow the instructions in the pkg-readme exactly and let me know if you
still have problems. If you want to make adjustments to limits etc then
do that after trying the suggested configuration.
In your case you most likely have an invalid config, the openfiles-max
limit will probably be *lower* than your openfiles-cur. OpenBSD used to
accept this and use the higher limit, but a couple of releases ago this
was changed for posix compatibility. The example in the pkg-readme just
sets openfiles, overriding both -cur and -max.
into login.conf and did not forget to 'push' it
# cap_mkdb /etc/login.conf
# echo $?
0
You only have to run cap_mkdb if you already have a login.conf.db file.
Most people do not use these and just use the plaintext file instead.
And it checks the non space friendly syntax :-)
whith openfile
squid:\
:openfiles-cur=4096:\
:openfiles=4096:\
:tc=daemon:
I do not have to do ulimit manually before but stop at 1025, I didn't
call setrlimit
root@unicornD # su -l -c squid -s /bin/sh root -c perl /root/fds.pl
perl /rooperl /root/fds.pl
uid=515(_squid) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty),
5(operator), 20(staff), 31(guest)
ksh: ulimit: Permission denied
Error in tempfile() using template /tmp/XX: Could not create
temp file /tmp/4vncHRQHUt: No locks available at /root/fds.pl line 20.
Count:1025
setrlimit change nothing :
# cat /root/fds.pl
#!/usr/bin/perl
use warnings;
use strict;
use v5.10;
use POSIX;
use BSD::Resource;
use File::Temp qw/tempfile/;
if (defined $ARGV[0] and $ARGV[0] =~ /^\d+$/) {
setuid ($ARGV[0]);
} else {
setuid ( 515 );
}
system('id');
my $rc = setrlimit(RLIMIT_OPEN_MAX,4096,4096);
say 'ok' if ($rc);
my @fds = ();
while (0xBAD) {
my($fh, $filename) = tempfile();
last unless $fh;
push @fds, { fd=$fh,n=$filename};
}
END{
say 'Count:'.($#fds+1);
foreach my $fd (@fds) {
close $fd-{fd};
unlink $fd-{n};
}
}
It looks like it has no effect. Is this the way to go ? have I to change a
limit somewhere else ?
Best regards,
Sven
--
-
() ascii ribbon campaign - against html e-mail
/\
Re: Squid configuration
On 2014/12/07 15:57, sven falempin wrote:
On Sat, Dec 6, 2014 at 9:20 AM, Stuart Henderson s...@spacehopper.org wrote:
On 2014-12-02, sven falempin sven.falem...@gmail.com wrote:
Hello,
I am more or less forced to test Squid.
OpenBSD test.my.domain 5.6 GENERIC.MP#333 amd64
I have two problems:
WARNING! Your cache is running out of filedescriptors
And probably have to read more about ICAP
suspending ICAP service for too many failures
My question is about the fds,
i tried to add
squid:\
:openfiles-cur=4096:\
:tc=daemon:
Follow the instructions in the pkg-readme exactly and let me know if you
still have problems. If you want to make adjustments to limits etc then
do that after trying the suggested configuration.
In your case you most likely have an invalid config, the openfiles-max
limit will probably be *lower* than your openfiles-cur. OpenBSD used to
accept this and use the higher limit, but a couple of releases ago this
was changed for posix compatibility. The example in the pkg-readme just
sets openfiles, overriding both -cur and -max.
into login.conf and did not forget to 'push' it
# cap_mkdb /etc/login.conf
# echo $?
0
You only have to run cap_mkdb if you already have a login.conf.db file.
Most people do not use these and just use the plaintext file instead.
And it checks the non space friendly syntax :-)
whith openfile
squid:\
:openfiles-cur=4096:\
:openfiles=4096:\
:tc=daemon:
I do not have to do ulimit manually before but stop at 1025, I didn't
call setrlimit
root@unicornD # su -l -c squid -s /bin/sh root -c perl /root/fds.pl
perl /rooperl /root/fds.pl
uid=515(_squid) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty),
5(operator), 20(staff), 31(guest)
ksh: ulimit: Permission denied
Error in tempfile() using template /tmp/XX: Could not create
temp file /tmp/4vncHRQHUt: No locks available at /root/fds.pl line 20.
Count:1025
setrlimit change nothing :
# cat /root/fds.pl
#!/usr/bin/perl
use warnings;
use strict;
use v5.10;
use POSIX;
use BSD::Resource;
use File::Temp qw/tempfile/;
if (defined $ARGV[0] and $ARGV[0] =~ /^\d+$/) {
setuid ($ARGV[0]);
} else {
setuid ( 515 );
}
system('id');
my $rc = setrlimit(RLIMIT_OPEN_MAX,4096,4096);
say 'ok' if ($rc);
my @fds = ();
while (0xBAD) {
my($fh, $filename) = tempfile();
last unless $fh;
push @fds, { fd=$fh,n=$filename};
}
END{
say 'Count:'.($#fds+1);
foreach my $fd (@fds) {
close $fd-{fd};
unlink $fd-{n};
}
}
It looks like it has no effect. Is this the way to go ? have I to change a
limit somewhere else ?
Best regards,
Sven
--
-
() ascii ribbon campaign - against html e-mail
/\
I have no idea what you're trying to do here.
sthen@wc2-pl7:~:669$ tail -5 /etc/login.conf
squid:\
:datasize=infinity:\
:openfiles-max=1:\
:openfiles-cur=6000:\
:tc=default:
sthen@wc2-pl7:~:670$ sudo -c squid sh -c ulimit -a
time(cpu-seconds)unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 33554432
stack(kbytes)4096
lockedmem(kbytes)2029690
memory(kbytes) 6087328
nofiles(descriptors) 6000
processes128
Re: Squid configuration
On Sun, Dec 7, 2014 at 5:12 PM, Stuart Henderson s...@spacehopper.org wrote:
On 2014/12/07 15:57, sven falempin wrote:
On Sat, Dec 6, 2014 at 9:20 AM, Stuart Henderson s...@spacehopper.org
wrote:
On 2014-12-02, sven falempin sven.falem...@gmail.com wrote:
Hello,
I am more or less forced to test Squid.
OpenBSD test.my.domain 5.6 GENERIC.MP#333 amd64
I have two problems:
WARNING! Your cache is running out of filedescriptors
And probably have to read more about ICAP
suspending ICAP service for too many failures
My question is about the fds,
i tried to add
squid:\
:openfiles-cur=4096:\
:tc=daemon:
Follow the instructions in the pkg-readme exactly and let me know if you
still have problems. If you want to make adjustments to limits etc then
do that after trying the suggested configuration.
In your case you most likely have an invalid config, the openfiles-max
limit will probably be *lower* than your openfiles-cur. OpenBSD used to
accept this and use the higher limit, but a couple of releases ago this
was changed for posix compatibility. The example in the pkg-readme just
sets openfiles, overriding both -cur and -max.
into login.conf and did not forget to 'push' it
# cap_mkdb /etc/login.conf
# echo $?
0
You only have to run cap_mkdb if you already have a login.conf.db file.
Most people do not use these and just use the plaintext file instead.
And it checks the non space friendly syntax :-)
whith openfile
squid:\
:openfiles-cur=4096:\
:openfiles=4096:\
:tc=daemon:
I do not have to do ulimit manually before but stop at 1025, I didn't
call setrlimit
root@unicornD # su -l -c squid -s /bin/sh root -c perl /root/fds.pl
perl /rooperl /root/fds.pl
uid=515(_squid) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty),
5(operator), 20(staff), 31(guest)
ksh: ulimit: Permission denied
Error in tempfile() using template /tmp/XX: Could not create
temp file /tmp/4vncHRQHUt: No locks available at /root/fds.pl line 20.
Count:1025
setrlimit change nothing :
# cat /root/fds.pl
#!/usr/bin/perl
use warnings;
use strict;
use v5.10;
use POSIX;
use BSD::Resource;
use File::Temp qw/tempfile/;
if (defined $ARGV[0] and $ARGV[0] =~ /^\d+$/) {
setuid ($ARGV[0]);
} else {
setuid ( 515 );
}
system('id');
my $rc = setrlimit(RLIMIT_OPEN_MAX,4096,4096);
say 'ok' if ($rc);
my @fds = ();
while (0xBAD) {
my($fh, $filename) = tempfile();
last unless $fh;
push @fds, { fd=$fh,n=$filename};
}
END{
say 'Count:'.($#fds+1);
foreach my $fd (@fds) {
close $fd-{fd};
unlink $fd-{n};
}
}
It looks like it has no effect. Is this the way to go ? have I to change a
limit somewhere else ?
Best regards,
Sven
--
-
() ascii ribbon campaign - against html e-mail
/\
I have no idea what you're trying to do here.
opening (tempfile) files to the failure point. then cleaning the mess
END{}, I got 1025 temp file opened then it fails.
Since I run squid after a ulimit or with the class, I didn't get the
fd warnings in log, but I didn't check how many files where open,
the test with fds.pl probably fails for another reason (No locks available).
Years using other opensource kernel learn me to trust nothing , the
result is the one expected when using
my($fh, $filename) = tempfile('/tmp/X',EXLOCK = 0);
to open files.
Clearly out of the squid subject.
I am on my sslBump issue now.
Thank you for the support :-)
sthen@wc2-pl7:~:669$ tail -5 /etc/login.conf
squid:\
:datasize=infinity:\
:openfiles-max=1:\
:openfiles-cur=6000:\
:tc=default:
sthen@wc2-pl7:~:670$ sudo -c squid sh -c ulimit -a
time(cpu-seconds)unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 33554432
stack(kbytes)4096
lockedmem(kbytes)2029690
memory(kbytes) 6087328
nofiles(descriptors) 6000
processes128
--
-
() ascii ribbon campaign - against html e-mail
/\
Re: segmentation fault during package build
Hello Miod, Miod Vallat wrote: I can confirm the spurious segmentation faults or `double free' issues with an SM40 module, and I am currently investigating the issue. I swapped in the ol' SM40 instead of SM50 and after a make clean, build still failed, still in tcl. So yes, both modules are affected Something stresses ln there, just as a test I tried touch a and ln -s a b and it of course works. Riccardo
[OT] Re: OpenBSD Trademark Policy
Hi, Jorge Gabriel Lopez Paramount wrote: I'm in the middle of leaving Debian after almost 15 years of using it, due to the systemd affair. And as you might guess it has not been easy, I have enough (personal) systems and experience invested to leave Debian only for a tantrum, but there is no easy way to install a new system and avoid systemd, and I guess this will become worse over time. Had I an one-command option to avoid or drop systemd, I might not be here. me too. That systemd choice is really a pity. I will keep debian as a system to test my code on before releasing it, but my interest in it as an OS wanted. But this is becoming quite off-topic. Just to share the pain. Riccardo
Re: man afterboot - discouraging usage of space characters in root password
Hi, Stefan Wollny wrote on Sun, Dec 07, 2014 at 08:32:00PM +0100: Am 12/07/14 um 19:30 schrieb Adam Wolk: I would like to ask what is the reason for man afterboot discouraging the usage of the space character in root passwords. Root password Change the password for the root user. (Note that throughout the documentation, the term ``superuser'' is a synonym for the root user.) Choose a password that has digits and special characters *(not space)* as well as from the upper and lower case alphabet. Is there a reason for '(not space)' being included in that passage? The passwd utility seems pretty happy taking up the space character. Was it not the case in the past? I have been asking exactly this question in June: http://marc.info/?l=openbsd-miscm=140388067802438w=2 Oh well. Advice that nobody can explain the reasons for, and that several experienced people report to routinely disregard without adverse effect, is bad advice, in particular when it keeps people wondering what it's all about, so i deleted it. As long as you don't reuse one of your programs written in http://en.wikipedia.org/wiki/Whitespace_%28programming_language%29 for your password, you should be fine even if it contains a blank. Yours, Ingo
changing password after install
Hi Alexander, [ moved back to misc@, let's not discuss such a minor issue on source-changes@ ] Alexander Hall wrote on Mon, Dec 08, 2014 at 12:31:43AM +0100: On December 8, 2014 12:05:30 AM CET, Ingo Schwarze wrote: CVSROOT: /cvs Module name: src Changes by: schwa...@cvs.openbsd.org2014/12/07 16:05:30 Modified files: share/man/man8 : afterboot.8 Log message: Since rev. 1.1, we discouraged space characters in passwords but even after repeated enquiries on misc@, nobody can explain why, so tedu the two confusing words; ok tedu@. Why do we recommend changing the root password there at all? I suspect some horribly outdated historical reason, but I don't see the point of that part at all. It certainly isn't very important; if you set a good password while installing, you are already fine. Then again, i sometimes install machines in the lab where they are not exposed to the Internet right away and only later move them into production. During the install, i'm sometimes not in the mood for inventing a good password but focus on other things like network and disk configuration. The afterboot(8) manual is more useful for newbies than for developers, and newbies may regard installing as an adventure, so they may feel that effect even more strongly. Besides, you are supposed to read afterboot(8) *after* installing, and that's a good time to realize that the password you typed in while installing was a really bad idea. Having this advice at this place certainly doesn't hurt. As the page says at the very top: The idea is to create a list of items that can be checked off so that you have a warm fuzzy feeling that something obvious has not been missed. Did you set reasonable passwords? does make some sense on such a list. Yours, Ingo
Re: OpenBSD 5.6-current on ASUS Chromebox
I did not. In fact both HDMI and Displayport outputs worked fine. I also tried the system on a 2560x1440 monitor, that worked as well. I did not test audio, didn't do very much desktop stuff. Firefox and xterm work fine. I still need to spend some time on learning how to install another window manager and play with more desktop stuff. -Gene On Sun, Dec 7, 2014 at 3:15 PM, Amit Kulkarni amitk...@gmail.com wrote: Did you have to do anything special to get HDMI to work? thanks On Wed, Dec 3, 2014 at 11:42 AM, Gene gh5...@gmail.com wrote: I'm a fan of the ASUS Chromebox hardware, specifically the M004U with the Celeron 2955U processor. Comes with 2 GB of RAM, and 16GB SSD. It typically retails for $160 USD. I have a couple running Linux (HTPC and a desktop for my kids). I picked up a third one on black friday for $110 just to play with, was specifically interested in loading OpenBSD on it. 5.6-stable doesn't work because of the lack of USB 3.0 (xhci) support, but 5.6-current installed without issue. The wireless adapter wasn't detected, but the Realtek ethernet device works. I have it driving a 1920x1200 display over HDMI. It's been a long time since I've used OpenBSD as a desktop so I've got a bit to figure out, but thus far this little system is running very nicely. Just in case anyone else is interested in it I'm including dmesg output. Also, if you do try just be aware that the Chromebox has to be put into developer mode and the default BIOS will need to be replaced with coreboot. The Kodi (XBMC) wiki has a good document on doing that. http://kodi.wiki/view/ASUS_Chromebox dmesg output: OpenBSD 5.6-current (RAMDISK_CD) #584: Mon Dec 1 00:41:23 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 4215820288 (4020MB) avail mem = 4102762496 (3912MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7f69f020 (7 entries) bios0: vendor coreboot version 4.0-7445-ge0d42b6-dirty date 12/02/2014 bios0: Google Panther acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT MCFG APIC HPET SSDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) 2955U @ 1.40GHz, 1397.00 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,XSAVE, RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,ERMS,INVPCID cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus 3 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus -1 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 4G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel HD Graphics rev 0x09 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel Core 4G HD Audio rev 0x09 at pci0 dev 3 function 0 not configured xhci0 at pci0 dev 20 function 0 Intel 8 Series xHCI rev 0x04: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 Intel xHCI root hub rev 3.00/1.00 addr 1 Intel 8 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured Intel 8 Series HD Audio rev 0x04 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 Intel 8 Series PCIE rev 0xe4 pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x0c: RTL8168G/8111G (0x4c00), msi, address c4:54:44:4d:be:ab rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb1 at pci0 dev 28 function 1 Intel 8 Series PCIE rev 0xe4 pci2 at ppb1 bus 2 Atheros AR9462 rev 0x01 at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 28 function 2 Intel 8 Series PCIE rev 0xe4 pci3 at ppb2 bus 3 Intel 8 Series LPC rev 0x04 at pci0 dev 31 function 0 not configured ahci0 at pci0 dev 31 function 2 Intel 8 Series AHCI rev 0x04: msi, AHCI 1.3 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, SanDisk SSD U110, U221 SCSI3 0/direct fixed naa.5001b44bed91e41e sd0: 15272MB, 512 bytes/sector, 31277232 sectors, thin Intel 8 Series SMBus rev 0x04 at pci0 dev 31 function 3 not configured vendor Intel, unknown product 0x9c24 (class DASP subclass miscellaneous, rev 0x04) at pci0 dev 31 function 6 not configured isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo uhidev0 at uhub0 port 2 configuration 1 interface 0 Logitech USB Receiver rev 2.00/29.00 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0 wskbd0 at ukbd0: console keyboard,
OpenBSD 5.6/current on Soekris 6501-70
Hi, Anyone running OpenBSD 5.6 or current on Soekris 6501-70 who wouldn't mind sharing some through-put data for gigabit performance. Regards, MH
broken links on site
Hi, Since I don't know if the OpenBSD Project still providing support for these products, I don't make a diff, sorry. The following links are broken on http://www.openbsd.org/products.html RTMX (http://www.rtmx.com/) PowerCrypt (http://www.powercrypt.com/) Core Systems (http://www.core.dk/) InSite (http://www.core.dk/products/insite/index_en.html) Regards, L.
Re: OpenBSD 5.6/current on Soekris 6501-70
I would like to be able to run ~100-120 MB/s from one NIC to the other on this box, if possible?
Re: OpenBSD 5.6/current on Soekris 6501-70
Search the mailing list history. If you can't find that specific model Soekris you'll likely be able to find information for that NIC chipset (the Intel 82574L). -Gene On Sun, Dec 7, 2014 at 3:53 PM, Martin Hanson greencopperm...@yandex.com wrote: Hi, Anyone running OpenBSD 5.6 or current on Soekris 6501-70 who wouldn't mind sharing some through-put data for gigabit performance. Regards, MH
Re: OpenBSD 5.6/current on Soekris 6501-70
Hi Martin, On 7 December 2014 at 18:18, Martin Hanson greencopperm...@yandex.com wrote: I would like to be able to run ~100-120 MB/s from one NIC to the other on this box, if possible? Take a look a look at these threads: https://www.mail-archive.com/misc%40openbsd.org/msg133961.html https://www.mail-archive.com/misc@openbsd.org/msg134259.html And others from here: https://www.mail-archive.com/misc@openbsd.org/ I was looking at APU systems myself but now I'm leaning towards this: http://www.newegg.com/Product/Product.aspx?Item=N82E16856205007 No intel NICs but I like the price. Best, j.b. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: OpenBSD 5.6/current on Soekris 6501-70
I mentioned it one of those threads, I have the 2550L2D-MxPC and one of the NICs died after nine months of use. I might just be unlucky, but I feel its worth mentioning. -Gene On Sun, Dec 7, 2014 at 8:05 PM, jungle Boogie jungleboog...@gmail.com wrote: Hi Martin, On 7 December 2014 at 18:18, Martin Hanson greencopperm...@yandex.com wrote: I would like to be able to run ~100-120 MB/s from one NIC to the other on this box, if possible? Take a look a look at these threads: https://www.mail-archive.com/misc%40openbsd.org/msg133961.html https://www.mail-archive.com/misc@openbsd.org/msg134259.html And others from here: https://www.mail-archive.com/misc@openbsd.org/ I was looking at APU systems myself but now I'm leaning towards this: http://www.newegg.com/Product/Product.aspx?Item=N82E16856205007 No intel NICs but I like the price. Best, j.b. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: OpenBSD 5.6/current on Soekris 6501-70
I misspoke, in both cases. It died on the 14th month. -Gene On Sun, Dec 7, 2014 at 8:39 PM, Gene gh5...@gmail.com wrote: I mentioned it one of those threads, I have the 2550L2D-MxPC and one of the NICs died after nine months of use. I might just be unlucky, but I feel its worth mentioning. -Gene On Sun, Dec 7, 2014 at 8:05 PM, jungle Boogie jungleboog...@gmail.com wrote: Hi Martin, On 7 December 2014 at 18:18, Martin Hanson greencopperm...@yandex.com wrote: I would like to be able to run ~100-120 MB/s from one NIC to the other on this box, if possible? Take a look a look at these threads: https://www.mail-archive.com/misc%40openbsd.org/msg133961.html https://www.mail-archive.com/misc@openbsd.org/msg134259.html And others from here: https://www.mail-archive.com/misc@openbsd.org/ I was looking at APU systems myself but now I'm leaning towards this: http://www.newegg.com/Product/Product.aspx?Item=N82E16856205007 No intel NICs but I like the price. Best, j.b. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: OpenBSD 5.6/current on Soekris 6501-70
Hi Gene, On 7 December 2014 at 20:39, Gene gh5...@gmail.com wrote: I mentioned it one of those threads, I have the 2550L2D-MxPC and one of the NICs died after nine months of use. I might just be unlucky, but I feel its worth mentioning. I probably glossed right over that post. Would you still recommend the 2550L2D-MxPC or move on to something more? Regarding the brand 'OEM Production' that's the only unit on newegg.com with dual LAN. From a brief search the other day, this Jetaway looks appealing, too, but it is slightly more expensive and has fewer reviews: http://www.newegg.com/Product/Product.aspx?Item=N82E16856107095cm_re=mini_pc-_-56-107-095-_-Product It does have intel NICs and way more sata ports. -Gene -jb --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: broken links on site
Hahaha. When I went to powercrypt.com it sent me to a different site tried to get me to download an Adobe Flash installer, and not from Adobe's website. -Gene On Sun, Dec 7, 2014 at 6:05 PM, Luiz Roberto dos Santos arrowscr...@mail.com wrote: Hi, Since I don't know if the OpenBSD Project still providing support for these products, I don't make a diff, sorry. The following links are broken on http://www.openbsd.org/products.html RTMX (http://www.rtmx.com/) PowerCrypt (http://www.powercrypt.com/) Core Systems (http://www.core.dk/) InSite (http://www.core.dk/products/insite/index_en.html) Regards, L.
Re: fatal page fault in supervisor mode
On 07.12.2014 20:03, pavel pocheptsov wrote: Hi list, I've got this error and I don't what it is about. Is something wrong with my hardware, like RAM? Could someone point me in right direction to resolve this error? Dec 7 11:35:33 gw /bsd: uvm_fault(0xd0a2, 0xcfc0, 0, 3) - e Dec 7 11:35:33 gw /bsd: fatal page fault (6) in supervisor mode Dec 7 11:35:33 gw /bsd: trap type 6 code 2 eip d056f4a8 cs 50 eflags 210256 cr2 cfc0 cpl 40 Dec 7 11:35:33 gw /bsd: panic: trap type 6, code=2, pc=d056f4a8 Dec 7 11:35:33 gw /bsd: Starting stack trace... Dec 7 11:35:33 gw /bsd: panic(d08d35a6,dc7deabc,d08d6f9e,dc7deabc,2) at panic+0x6a Dec 7 11:35:33 gw /bsd: panic(d08d6f9e,6,2,d056f4a8,50) at panic+0x6a Dec 7 11:35:33 gw /bsd: trap() at trap+0x38f Dec 7 11:35:33 gw /bsd: --- trap (number -809500672) --- Dec 7 11:35:33 gw /bsd: 0x2: Dec 7 11:35:33 gw /bsd: End of stack trace. Dec 7 11:35:33 gw /bsd: panic: mtx_enter: locking against myself Dec 7 11:35:33 gw /bsd: Starting stack trace... Dec 7 11:35:33 gw /bsd: panic(d08d35a6,dc7de72c,dc7de720,d020476c,c0) at panic+0x6a Dec 7 11:35:33 gw /bsd: panic(d02036a2,dc7de75c,d03ee791,d0a181a0,17) at panic+0x6a Dec 7 11:35:33 gw /bsd: mtx_enter(d0a181a0,17,d0a162c0,dc7de780,d02043fc) at mtx_enter+0x62 Dec 7 11:35:33 gw /bsd: pool_get(d0a181a0,2,d6872a18,dc7de8f8,2) at pool_get+0x31 Dec 7 11:35:33 gw /bsd: pf_test_rule(dc7de8d0,dc7de8cc,1,d1ea3900,dc8dab00) at pf_test_rule+0x1ab9 Dec 7 11:35:33 gw /bsd: pf_test(2,1,d1eba030,dc7de9d4,0) at pf_test+0xd4c Dec 7 11:35:33 gw /bsd: ipv4_input(dc8dab00,6,dc7de9ec,d0445b55,d0203776) at ipv4_input+0x20c Dec 7 11:35:33 gw /bsd: ipintr(d0203776,d1e98440,dc7dea0c,d057569f,0) at ipintr+0x73 Dec 7 11:35:33 gw /bsd: netintr(0,200292,0,0,d0202232) at netintr+0xc5 Dec 7 11:35:33 gw /bsd: softintr_dispatch(1) at softintr_dispatch+0x4f Dec 7 11:35:33 gw /bsd: Xsoftnet() at Xsoftnet+0x17 Dec 7 11:35:33 gw /bsd: --- interrupt --- Dec 7 11:35:33 gw /bsd: end(100,dc7deabc,d08d6f9e,dc7deabc,2) at 0xdc7deabc Dec 7 11:35:33 gw /bsd: panic(d08d6f9e,6,2,d056f4a8,50) at panic+0x65 Dec 7 11:35:33 gw /bsd: trap() at trap+0x38f Dec 7 11:35:33 gw /bsd: --- trap (number -809500672) --- Dec 7 11:35:33 gw /bsd: 0x2: Dec 7 11:35:33 gw /bsd: End of stack trace. Dec 7 11:35:33 gw /bsd: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 http://www.openbsd.org/faq/faq5.html#Flavors Dec 7 11:35:33 gw /bsd:    dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP Dec 7 11:35:33 gw /bsd: cpu0: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (GenuineIntel 686-class) 2 GHz Dec 7 11:35:33 gw /bsd: cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM Dec 7 11:35:33 gw /bsd: real mem = 1064431616 (1015MB) Dec 7 11:35:33 gw /bsd: avail mem = 1036947456 (988MB) Dec 7 11:35:33 gw /bsd: mainbus0 at root Dec 7 11:35:33 gw /bsd: bios0 at mainbus0: AT/286+ BIOS, date 08/12/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0x9f800 (28 entries) Dec 7 11:35:33 gw /bsd: bios0: vendor American Megatrends Inc. version 080014 date 08/12/2008 Dec 7 11:35:33 gw /bsd: bios0: ICP / iEi KINO-9652 Dec 7 11:35:33 gw /bsd: acpi0 at bios0: rev 0 Dec 7 11:35:33 gw /bsd: acpi0: sleep states S0 S1 S4 S5 Dec 7 11:35:33 gw /bsd: acpi0: tables DSDT FACP APIC MCFG OEMB ASF! SSDT Dec 7 11:35:33 gw /bsd: acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) EUSB(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) HDAC(S4) USB4(S4) USB5(S4) USBE(S4) GBEC(S4) Dec 7 11:35:33 gw /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits Dec 7 11:35:33 gw /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT compat Dec 7 11:35:33 gw /bsd: cpu0 at mainbus0: apid 0 (boot processor) Dec 7 11:35:33 gw /bsd: cpu0: apic clock running at 201MHz Dec 7 11:35:33 gw /bsd: cpu1 at mainbus0: apid 1 (application processor) Dec 7 11:35:33 gw /bsd: cpu1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (GenuineIntel 686-class) 2.02 GHz Dec 7 11:35:33 gw /bsd: cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM Dec 7 11:35:33 gw /bsd: ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins Dec 7 11:35:33 gw /bsd: acpimcfg0 at acpi0 addr 0xe000, bus 0-255 Dec 7 11:35:33 gw /bsd: acpiprt0 at acpi0: bus 0 (PCI0) Dec 7 11:35:33 gw /bsd: acpiprt1 at acpi0: bus -1 (P0P2) Dec 7 11:35:33 gw /bsd: acpiprt2 at acpi0: bus 1 (P0P1) Dec 7 11:35:33 gw /bsd: acpiprt3 at acpi0: bus 2 (P0P4) Dec 7 11:35:33 gw /bsd: acpiprt4 at acpi0: bus 3 (P0P5) Dec 7 11:35:33 gw /bsd: acpiprt5 at acpi0: bus -1 (P0P6) Dec 7 11:35:33 gw /bsd: acpiprt6 at acpi0: bus -1 (P0P7) Dec 7 11:35:33 gw /bsd: acpiprt7 at
Re: DNS: how to verify glue NS records?
Thus said Alexei Malinin on Fri, 05 Dec 2014 15:49:59 +0300: - the question is - how and with what tools (dig, host, nslookup, or maybe C or Perl libs) can I verify the NS glue records in the parent zone of my ISP (zone transfers are denied)? The entries in the ADDITIONAL SECTION below are ``glue records'' for the NS records in the ANSWER SECTION. The problem you have, however, DNS resolvers are going to have to make a lot of additional DNS requests to be able to determine if the glue can be used. For the glue to be immediately trusted, it would have to be in-bailiwick (e.g. ns1.0-15.66.233.212.in-addr.arpa and ns2.0-15.66.233.212.in-addr.arpa). But, At any rate, there you have it, glue is found in the ADDITIONAL SECTION: $ dig ptr 1.0-15.66.233.212.in-addr.arpa @ns1.agtel.net ; DiG 9.4.2-P2 ptr 1.0-15.66.233.212.in-addr.arpa @ns1.agtel.net ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 37069 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 7 ;; QUESTION SECTION: ;1.0-15.66.233.212.in-addr.arpa.IN PTR ;; ANSWER SECTION: 1.0-15.66.233.212.in-addr.arpa. 43200 IN PTRdynamic-212-233-66-1.amt.ru. ;; AUTHORITY SECTION: 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns58-cloud.nic.ru. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns1.agtel.net. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns2.agtel.net. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns4-l5.nic.ru. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns8-l5.nic.ru. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns54-cloud.nic.ru. ;; ADDITIONAL SECTION: ns1.agtel.net. 600 IN A 212.111.64.132 ns2.agtel.net. 600 IN A 212.233.88.2 ns4-l5.nic.ru. 25082 IN A 91.217.20.13 ns8-l5.nic.ru. 36736 IN A 91.217.21.13 ns54-cloud.nic.ru. 19033 IN A 195.253.64.16 ns54-cloud.nic.ru. 19033 IN 2a01:5b0:4::10 ns58-cloud.nic.ru. 12582 IN A 195.253.65.16 ;; Query time: 273 msec ;; SERVER: 212.111.64.132#53(212.111.64.132) ;; WHEN: Sun Dec 7 23:03:49 2014 ;; MSG SIZE rcvd: 354 Andy -- TAI64 timestamp: 400054854018
Re: OpenBSD 5.6/current on Soekris 6501-70
On 12/07/14 21:18, Martin Hanson wrote: I would like to be able to run ~100-120 MB/s from one NIC to the other on this box, if possible? The NICs should be fine but I'd be worried that even the -70 model would be CPU limited for such throughput. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
