> I've noticed that bsd.rd wants to download the install base packages
> from /pub/OpenBSD/6.1/i386. Is this an error or some sort of alias for
> the path to the snapshots of the install base? bsd.rd seems to find the
> install base packages alright.
That is normal during last weeks of the snap
Hi @misc,
I've noticed that bsd.rd wants to download the install base packages
from /pub/OpenBSD/6.1/i386. Is this an error or some sort of alias for
the path to the snapshots of the install base? bsd.rd seems to find the
install base packages alright. pkg_add has trouble finding the
applicat
On Wed, March 29, 2017 6:49 pm, Ryan Freeman wrote:
> On Wed, Mar 29, 2017 at 05:00:44PM -0500, Jordon wrote:
>> > On Mar 29, 2017, at 4:51 AM, Luke Small wrote:
>> >
>> > I thought I read that there is an arm7 based mobile device, but I
>> can't
>> > find anything about it.
>> >
>>
>> I???m reall
Maybe this helps, ioctls are at the bottom
http://man.openbsd.org/man4/scsi.4
Am Mittwoch, 29. März 2017 schrieb Markus Rosjat :
> Hi there,
> On a linux system I have the sg diver and sg.h in place to pass a cdb to
the ioctl . Is SG3 also present on OpenBSD if not what header do I need on
open b
> > > diff -u -p -r1.988 install.sub
> > > --- distrib/miniroot/install.sub 13 Mar 2017 17:08:31 - 1.988
> > > +++ distrib/miniroot/install.sub 30 Mar 2017 10:44:01 -
> > > @@ -264,13 +264,7 @@ diskinfo() {
> > > local _d
> > >
> > > for _d; do
> > > - make_dev $_d
> >
On Mar 07 12:13:11, s...@spacehopper.org wrote:
> I would definitely just go for two separate USB-RS232 adapters in
> this scenario.
On Mar 03 09:24:48, inform...@gmx.net wrote:
> I use an old USB to serial adapter from HP which attaches as uftdi(4).
> There are some other compatible chips listed
On Thu, Mar 30, 2017 at 07:21:22AM -0400, Jiri B wrote:
> On Thu, Mar 30, 2017 at 12:59:00PM +0200, Bruno Flueckiger wrote:
> > I see your point with the installer. Default labels make the disks
> > indistinguishable. The following diff prints the raw infos from dmesg
> > rather than the current li
On Thu, Mar 30, 2017 at 12:59:00PM +0200, Bruno Flueckiger wrote:
> I see your point with the installer. Default labels make the disks
> indistinguishable. The following diff prints the raw infos from dmesg
> rather than the current list of disks:
>
> Index: distrib/miniroot/install.sub
>
On Thu, Mar 30, 2017 at 04:53:51AM -0400, Jiri B wrote:
> On Thu, Mar 30, 2017 at 10:25:18AM +0200, Bruno Flueckiger wrote:
> > > how to query scsi id or wwn for a scsi disk in OpenBSD? I'd like to get
> > > this
> > > info and extend installer to provide more info about disks (because
> > > curr
On Thu, Mar 30, 2017 at 10:25:18AM +0200, Bruno Flueckiger wrote:
> > how to query scsi id or wwn for a scsi disk in OpenBSD? I'd like to get this
> > info and extend installer to provide more info about disks (because
> > currently
> > it's imposible to distinguish between scsi disks if they are
On Thu, Mar 30, 2017 at 04:04:51AM -0400, Jiri B wrote:
> Hi,
>
> how to query scsi id or wwn for a scsi disk in OpenBSD? I'd like to get this
> info and extend installer to provide more info about disks (because currently
> it's imposible to distinguish between scsi disks if they are same size an
Hi,
how to query scsi id or wwn for a scsi disk in OpenBSD? I'd like to get this
info and extend installer to provide more info about disks (because currently
it's imposible to distinguish between scsi disks if they are same size and
originate from same iscsi target and passed to OpenBSD via qemu-
12 matches
Mail list logo
