Re: Recognition Of Linux LVMs
Greg Thomas wrote: > > storage (and I wonder, parenthetically, why FreeBSD and NetBSD are > > willing to support ZFS, but OpenBSD is not). Why continue to wonder? Why not just sit down and figure out that they surrendered their ideals? I make vegeterian meals all the time, with a big slab of beef on the other half of the plate.
Re: Recognition Of My Wireless Network Device
Unfortunately, no OpenBSD driver for the Broadcom BCM4313 exists. The bwfm driver support Broadcom "FullMAC" chips but the BCM4313 is a "SoftMAC" chip and would need a different driver. There is a driver for this chip in Linux (brcmsmac) so it might be possible for someone to write an OpenBSD driver but this is no small undertaking. Your best bet may be to replace the onboard wireless with a card that is supported by OpenBSD. - todd
Re: Recognition Of My Wireless Network Device
On Mon, Aug 7, 2023 at 2:02 PM Jay F. Shachter wrote: > > It does not. The "ifconfig -a" command reports an awareness of lo0, > em0 (my Ethernet device), enc0, and pflog0. And nothing else. How do > I get OpenBSD to recognize my Broadcom BCM4313 wireless network device? > Did you Google "BCM4313 OpenBSD" The results aren't very encouraging.
Recognition Of My Wireless Network Device
Esteemed Colleagues: How do I get OpenBSD to recognize my wireless network device? When I install OpenBSD on my computer, the second-to-last thing the installer says, is that I have a multiprocessor machine, so it will use bsd_mp instead of bsd. Then there is a very long pause -- so long that you are nearly certain that the installer is hung, and you will have to power-cycle. Then the installer reports that fw_update has obtained intel and inteldrm, and congratulates me on a successful installation. When I reboot and log in for the first time, fw_update reports that it has just obtained uvideo and vmm (why it did not do this at the end of the installation, when it obtained intel and inteldrm, is never explained). At this point, after two opportunities to obtain the firmware that it needs, I would expect that my computer's operating system would recognize my computer's wireless network device (which, according to the output of "pciconf -v", is a Broadcom BCM4313, Vendor ID: 14e4, Product ID: 4727). It does not. The "ifconfig -a" command reports an awareness of lo0, em0 (my Ethernet device), enc0, and pflog0. And nothing else. How do I get OpenBSD to recognize my Broadcom BCM4313 wireless network device? If your answer to this question is something alone the lines of "read the fabulous manual" please be aware that I have tried to read the fabulous manual, and I do not see where the fabulous manual provides an answer to this question. If you do direct me to the fabulous manual, please be so kind as to tell me where the fabulous manual answers the question. As always, thank you in advance for any and all replies. Jay F. Shachter 6424 North Whipple Street Chicago IL 60645-4111 (1-773)7613784 landline (1-410)9964737 GoogleVoice j...@m5.chicago.il.us http://m5.chicago.il.us "Quidquid latine dictum sit, altum videtur"
Re: Recognition Of Linux LVMs
On Mon, Aug 7, 2023 at 12:20 PM Jay F. Shachter wrote: > > > > > As the primary author of OpenBSD's current fdisk/disklabel/etc. I > > was intrigued by your recent email to misc@ [I]f you want > > disklabel(8) to say "Linux LVM" for sd0l you would need at a minimum > > a patch to /usr/src/sys/sys/disklabel.h to add an FS_LINUXLVM define > > and the string "Linux LVM" to the immediately following > > fstypenames[] array > > > > Please forgive me for being unclear. > > I was not asking whether my Linux volume group could be recognized by > the OpenBSD "disklabel" program as a Linux volume group, and correctly > identified as such. That would certainly be nice, and a welcome > improvement to the disklabel program, but it was not what I was > asking. I was asking whether Linux logical volumes can be recognized > as disk devices by the OpenBSD kernel, in the way that they can be > recognized in NetBSD, and in FreeBSD. Thus, if I have a multiboot > computer, on which Linux, FreeBSD, and NetBSD have been installed, and > if, on the Linux system, I create a volume group named "vgname", and I > then create within that volume group a logical volume named "lvname", > then, on the NetBSD system, I can access this logical volume by using > the exact same names that are used on Linux: either /dev/vgname/lvname, > or /dev/mapper/vgname-lvname. On FreeBSD the device name is slightly > different, on FreeBSD you say /dev/linux_lvm/vgname-lvname, but in > either case the logical volume is visible. My question for this > mailing list was: Are Linux logical volumes visible, or can they be > made visible, on an OpenBSD system? > > I have already remarked that my Solaris, Linux, FreeBSD, and NetBSD > systems can share disk storage (e.g., the /home/jay directory) by > means of a ZFS pool, but that OpenBSD cannot, because OpenBSD does not > support ZFS, and that, therefore, installing an OpenBSD system on the > same hardware will require some duplication of otherwise shared disk > storage (and I wonder, parenthetically, why FreeBSD and NetBSD are > willing to support ZFS, but OpenBSD is not). > Stuart already told you this: "Not likely to happen. Even if there was an implementation written, patents are involved (use is granted via the CDDL but that's not an acceptable license for OpenBSD)."
Re: Recognition Of Linux LVMs
> On Aug 7, 2023, at 12:20 PM, Jay F. Shachter wrote: > > Can OpenBSD be made to see Linux logical volumes? As I’ve often said at work, anything is possible with computers!
Recognition Of Linux LVMs
> > As the primary author of OpenBSD's current fdisk/disklabel/etc. I > was intrigued by your recent email to misc@ [I]f you want > disklabel(8) to say "Linux LVM" for sd0l you would need at a minimum > a patch to /usr/src/sys/sys/disklabel.h to add an FS_LINUXLVM define > and the string "Linux LVM" to the immediately following > fstypenames[] array > Please forgive me for being unclear. I was not asking whether my Linux volume group could be recognized by the OpenBSD "disklabel" program as a Linux volume group, and correctly identified as such. That would certainly be nice, and a welcome improvement to the disklabel program, but it was not what I was asking. I was asking whether Linux logical volumes can be recognized as disk devices by the OpenBSD kernel, in the way that they can be recognized in NetBSD, and in FreeBSD. Thus, if I have a multiboot computer, on which Linux, FreeBSD, and NetBSD have been installed, and if, on the Linux system, I create a volume group named "vgname", and I then create within that volume group a logical volume named "lvname", then, on the NetBSD system, I can access this logical volume by using the exact same names that are used on Linux: either /dev/vgname/lvname, or /dev/mapper/vgname-lvname. On FreeBSD the device name is slightly different, on FreeBSD you say /dev/linux_lvm/vgname-lvname, but in either case the logical volume is visible. My question for this mailing list was: Are Linux logical volumes visible, or can they be made visible, on an OpenBSD system? I have already remarked that my Solaris, Linux, FreeBSD, and NetBSD systems can share disk storage (e.g., the /home/jay directory) by means of a ZFS pool, but that OpenBSD cannot, because OpenBSD does not support ZFS, and that, therefore, installing an OpenBSD system on the same hardware will require some duplication of otherwise shared disk storage (and I wonder, parenthetically, why FreeBSD and NetBSD are willing to support ZFS, but OpenBSD is not). But if OpenBSD can see Linux volume groups, and the logical volumes that are carved out of them, then there can be shared disk storage among Linux, FreeBSD, NetBSD, and OpenBSD, and that would reduce somewhat the extent to which an OpenBSD system requires that disk storage be duplicated. Can OpenBSD be made to see Linux logical volumes? As always, thank you in advance for any and all replies. Jay F. Shachter 6424 North Whipple Street Chicago IL 60645-4111 (1-773)7613784 landline (1-410)9964737 GoogleVoice j...@m5.chicago.il.us http://m5.chicago.il.us "Quidquid latine dictum sit, altum videtur"
Re: Shotwell
On Sun Jul 30, 2023 at 03:06:26PM -0600, Raymond, David wrote: > Hello, > > I am trying to import photos using Shotwell over a usb connection with > the file transfer option. When I connect my phone to the usb port with > Shotwell running and select this option, Shotwell recognizes the phone > but says that there are no photos to transfer. The transfer works on > Arch Linux. > > Am I missing something? Some kind of permissions? The phone is a > Pixel 7 and I am running openbsd 7.3 stable. I had the problem with > 7.2 as well, but things worked before (I think with an earlier pixel > phone). > > -- > David J. Raymond > david.raym...@nmt.edu > http://kestrel.nmt.edu/~raymond > I'm not a Shotwell user but it works with libgphoto. You may wish to read /usr/local/share/doc/pkg-readmes/libgphoto Rafael
