From owner-freebsd-questions Wed May 17 13:44:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from home.se (smtp1.home.se [195.66.45.70]) by hub.freebsd.org (Postfix) with ESMTP id 0847F37BD25 for ; Wed, 17 May 2000 13:44:17 -0700 (PDT) (envelope-from nash@home.se) Received: from divan (nat.studenthem.gu.se [193.10.163.20]) by home.se (8.8.8/8.8.7) with SMTP id WAA10198 for ; Wed, 17 May 2000 22:44:15 +0200 (CEST) Message-ID: <001401bfc040$ef8bcde0$1a0a120a@hemmet.chalmers.se> From: "Nash J." To: Subject: Writing a Database-driver... program! Date: Wed, 17 May 2000 22:45:40 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01BFC051.A01F8F10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0011_01BFC051.A01F8F10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'm planning on writing a driver for a very large and slow Storage = Media, but don't know how to interface the directory listings to the = FreeBSD OS. I wonder if someone can point me in the right direction, on = how to start writing this software? The driver I'm trying to write is one that will implore (for now) the = SCSI bus, where the data comes in from the large Storage Device, and = also one of the serial buses (com ports); to stear a rather complicated = PIC-regulated device. My problem is that, I need to get an enormous list = of files and directories, into my FreeBSD server's file system, so that = the server sees the _extra_files_ as if they were mounted onto the = existing set of drives; so as to be able to add " an enormous new drive = in the /etc/fstab file". The reason why I want to use a serial port in conjunction with the = SCSI-2 interface is mainly because I know very little about the = SCSI-protocol's serious stuff, AND, that this Storage Device is so large = (around the Tera Byte region), that I doubt the SCSI-2 interface = supports such a large addressing scheme. I'm almost sure this qualifies as a form of database programming, but so = far I've only done minor programming of such nature. Unfortunately, when = it comes to the interfacing between the device I'm making, and the = FreeBSD OS, I don't even know where to start. I'm plannig on writing it in C-language (in case you'd like to know). My field of expertise is not very much of a software nature, so please = be kind with the complication of your reply - if any :-)) . Thank you in advance, Nader S. ------=_NextPart_000_0011_01BFC051.A01F8F10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

I'm planning on writing a driver for a = very large=20 and slow Storage Media, but don't know how to interface the directory = listings=20 to the FreeBSD OS. I wonder if someone can point me in the right = direction,=20 on how to start writing this software?

The driver I'm trying to write is = one that=20 will implore (for now) the SCSI bus, where the data comes in from the = large=20 Storage Device, and also one of the serial buses (com ports); to stear a = rather=20 complicated PIC-regulated device. My problem is that, I need to get = an=20 enormous list of files and directories, into my FreeBSD server's = file=20 system, so that the server sees the _extra_files_ as if they were = mounted=20 onto the existing set of drives; so as to be able to add " an = enormous new=20 drive in the /etc/fstab file".

The reason why I want to use a serial = port in=20 conjunction with the SCSI-2 interface is mainly because I know very = little about=20 the SCSI-protocol's serious stuff, AND, that this Storage Device is so = large=20 (around the Tera Byte region), that I doubt the SCSI-2 interface = supports such a=20 large addressing scheme.

I'm almost sure this qualifies as a = form of=20 database programming, but so far I've only done minor programming of = such=20 nature. Unfortunately, when it comes to the interfacing between the = device I'm=20 making, and the FreeBSD OS, I don't even know where to = start.

I'm plannig on writing it in C-language = (in case=20 you'd like to know).

My field of expertise is not very much = of a=20 software nature, so please be kind with the complication of your reply - = if any=20 :-)) .

Thank you in advance,

Nader S.

------=_NextPart_000_0011_01BFC051.A01F8F10-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message