> > Well, this BTX thing is amazing: all this effort, (btxld, run-time
> > library crt0.o, loader, etc.) seems to just to provide a 32-bit
> > protected and possibly paging-enabled environment to start the
> > kernel/loader(and to confuse a new-comer like me.) What are the
> > other gains? Where
>
> Dear Friends
>
> I'm incorporating the Real Time Protocol RTP (rfc 1889) to
> FreeBSD 4.0 kernel.
>
> Months ago, I compiled successfully the RTP Library API developed
> by Lucent into the FreeBSD kernel with the right logical and technical
> adjustments for the BSD kernel of course (cop
> > I need to MFC changes in ida driver, which start backround
> > firmware processing on Integrated SmartArray controllers
> > (this allows automatic on-line rebuild of failed drives).
> >
> > I am going to do it in next few days. I understood that I shall
> > avoid all changes for interrupt-ent
This sounds great; nothing else I can think of. Compaq are happy about
this. 8)
> I need to MFC changes in ida driver, which start backround
> firmware processing on Integrated SmartArray controllers
> (this allows automatic on-line rebuild of failed drives).
>
> I am going to do it in next f
> 3) Steal an idea from Linux (gasp!), and have module dependencies. ie,
>load ipfw.ko and then before we load up natd, we check to see if
>ipdivert.ko is loaded and load it. Alternatively, loading ipdivert.ko
>(before loading ipfw.ko), will automagically load ipfw.ko since ipfw is
>
>
> Does anyone have a reference to the values of "type" field in the Intel
> BIOS physical system RAM mapping?
>
> I am curious why we are using only entries of type "0x01".
This table (from Ralf Brown's Interrupt List) is self-explanatory:
Values for System Memory Map address type:
01hm
> >hi,
> >In FreeBSD i want to compile the module "dev" which should reflect the
> >kernel also, without compiling the kenel completely.
You can't do this.
> > and also i want to
> >include one more directory in "/usr/src/sys/dev" . so to compile that
> >directory files shall i have to made ch
> > We support ATAPI devices and has been for a long time (also CD burners)...
>
> I believe I forgot to do a group reply on my previous reply
> to Søren.
>
> OK, it seems a misunderstanding of the term ATAPI.
> The author of cdrecord, Joerg Schilling, told me - I will translate:
>
> Citation:
>In fact there are other considerations as well, namely the power supply,
> which is typically not all that beefy in 1U systems. For both of these
> reasons and others, our current 1U offering, although using an MP motherboard
> ,
> can only be ordered with one CPU. We've recently improved the
> > In the "default" case, it should attempt to obtain a DHCP lease,
> > and, failing that, ask the user to give it settings, or let
> > them do IPv4 stateless autoconfiguration. Ad Hoc networking
> > should always "just work".
>
> If anyone is taking a vote, I disagree. I do not want any system
For those of you that have too much time on your hands.
http://people.freebsd.org/~msmith/subr_figlet.diff
You'll need to load a font before booting;
load -t figlet_font .flf
Now, for the complication; it's wrapping lines at a single character. If
someone wants to work out why, I'd love
> On Wed, Jul 04, 2001 at 20:18:51 -0400, Kevin Hui wrote:
> > Then the question is whether the kernel is copying data between userspace
> > and kernelspace or whether it just DMAs the data straight in/out of the
> > user program's address space. In Linux raw-io, given that it is a block
> > devi
> Mike Smith([EMAIL PROTECTED])@2001.07.02 23:01:42 +:
> >=20
> > Be aware that ftpd is likely to be replaced in the near future, as=20
> > there's a strong desire to converge on the LukeM FTP tools.
>
> no matter how nice lukemftpd looks (i got it running on
pport proprietary
FAA protocols and equipment obsolete to the rest of the world, I want to
have as clean a kernel as possible to start from.
BTW, after 2 weeks, I LOVE this OS!
Mike Smith
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Be aware that ftpd is likely to be replaced in the near future, as
there's a strong desire to converge on the LukeM FTP tools.
> --BOKacYhQ+x31HxR3
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Mon, Jul 02, 2001 at 11:55:14PM -0400, Mike Wiacek wrote:
> > I
>
> Many pcmcia cards that I use have user-updateable firmware - basically a
> flash region of some kind that you can update with newer firmwares.
>
> When I want to update these items, I generally stick them in a windows
> machine and get the new firmware from the manufacturer and use whateve
> > So it looks like we have prior art by around 6 years, which would
> > invalidate the patent iff it was the same thing.
>
> Does it mean that the algorithm is free to use by everyone or free to use
> only in freebsd? I would like to implemet these page table back pointers
> too and I'm scared
> hahahahahahaaThe patent was filed in 1996. In the 90's the patent
> office starting granting patents for everything under the sun without
> doing real prior art searches. I'm sure even just going to the candy
> store these days is patented by someone...
Every time I tease
> Hi
>
> Go to http://www.uspto.gov/patft/, search for patent number 5873127, and
> you will find the description of mapping page table entries into virtual
> memory via one page directory entry pointing to the page directory itself
> - exactly what FreeBSD does with PTDPTDI and APTDPTDI entries
> One big area we need to clean up is PNPBIOS devices. They should be
> probed *FIRST* before anything else (which is hard because the isa bus
> gets attached late on pci systems).
This isn't actually such a problem; the space in which PNPBIOS devices
tend to have their resources allocated is p
> Tell me: at what point are you willing to trust the data?
>
> Is "the card plus the motherboard" my machine, or is it
> just "the motherboard"?
>
> The cards support offloading the checksum to hardware;
> you are saying that it is never reasonable to do this.
No, that's not what's being said.
> Since some strings are non-constant (the are allocated) - I believe
> the `const' qualifier in the structure declaration is incorrect.
'const' just means "I will not be modifying this"; it's a way for a
function prototype to constrain the function's implementation.
--
... every activity me
> >I don't think it would be much of a practical problem for anyone since
> >the old behvior can be emulated with the new md pretty easily, but
> >you're right that it isn't appropriate to break compatibility in
> >-stable. It's probably possible to retrofit the old behavior into the
> >new code,
I appear to have missed some of this thread. Dang.
> : > > - Some dummy driver which grabs the resource. The dummy driver would
> : > >need to be unloaded when the actual driver needs the resources.
> : >
> : > This sounds attractive, but it's hard to find the dummy driver when
> : > y
> | You manually set the correct I/O port in the hints file and then you
>
> Sorry if i misunderstand, but isn't the hints file only for -current? I was
> under the impression it was only to simplify driver development.
>
> Since my goal is to clean up the driver under the newbus system, how wo
> Some time ago, you corresponded with a gentleman from Japan (Katsushi
> Kobayashi <[EMAIL PROTECTED]>) about his firewire code. I've also
> noted a more recent query from a Wind River employee, which gives me
> hope that they might have interest in pursuing it.
I don't think that Bill Paul (the
> | You manually set the correct I/O port in the hints file and then you
> | don't have to check for each port between 0x200 and 0x3a0.
> |
> | Just bus_alloc_resource once and test for the card.
>
> So without having the card for testing, i should just wrap the port access
> calls into bus_xxx
> | Typically, probe routines these days are invoked with a single set of I/O
> | parameters to probe (and even this is only ISA devices).
> |
> | It's pretty rare to need to bit-bang to find a device these days anyway;
> | you should probably be looking for PnP data or similar. This is what
>
> The newbus routines use a certain amount of overhead, but once done, you
> forget about it. In some device drivers, the probe methods often need to
> try a variety of hardware ports. In the past, inb/outb was used, along with
> an often hardcoded port address.
>
> Does it make sense to cal
> Currently on FreeBSD, resources are either free, allocated or activated.
> As I understand it, they mean approximately the following:
> - Free: unused.
> - Allocated: Resource reserved for use by device X.
> - Activated: Resource actively used by device X.
>
> This leaves somewhat of a gap
> You might also consider to get this article from http://www.ddj.com/:
>
> Dr. Dobb's Journal March 1998 - Benchmarking and Software
> Testing, Tracing BSD System Calls, by Sean Eric Fagan
>
> AFAIR, in this article is explained what steps were necessary to make a
> ptrace() for FreeBSD
> Doug> Don't use nqnfs. It sucks.
>
> Ummm... I'm using a fstab line of:
>
> raid:/usr /raid nfs rw,-3,-s,-q,-b,-i 0 0
>
> ... which should invoke nfsv3?
Read the mount_nfs manpage:
-q Use the leasing extensions to the NFS Version 3 protocol to main-
> Hi all,
>
> We have a quite disapointing problem with a mylex 170 card, which causes
> a system crash every 6 hours.
> This card is installed in a VA Linux 2240 with 4 18GB drives, configured
> in a single RAID 5 pack, running a FreeBSD 4.2-stable system.
There are known problems with the 'mly
>
> Hello! I'm running FreeBSD 4.3 and have encountered a mystery of some
> missing files. Using "find" and "quota" to find the same files, I get
> different results. For example:
...
> So "find" is reporting 2435 files, but "quota" is reporting 2537. Where
> could the difference be hiding?
/tm
> > Date: Mon, 28 May 2001 19:01:37 -0500 (CDT)
> > From: David Scheidt <[EMAIL PROTECTED]>
>
> [ snip ]
>
> > If you're really interested in database performance, remember "Spindles
> > is good." Spreading your IO load over as many seperate disks, on as
> > many independent IO channels as prac
> > > SMAP type=01 base= len= 0009f800
> > > SMAP type=02 base= 0009f800 len= 0800
> > > SMAP type=02 base= 000e8400 len= 00017c00
> > > SMAP type=01 base= 0010 len= 13ef
> > > SMAP type=03 base= 13ff
> Valentin Nechayev wrote:
> >
> > Sun, May 20, 2001 at 19:53:29, barry (Barry Lustig) wrote about "Boot time memory
>issue":
> >
> > Do verbose boot (`boot -v') with large SC_HISTORY_SIZE (1000 at least,
> > 2000 at most), and after boot check for "SMAP ..." lines at the very
> > beginning of
> Hello all,
>
>
> I have been discussing on IRC with a blind people who can't use BSD
> because ``brltty'', the software used to render the console tty with
> braille displays, doesn't appear to work on BSD. I have been
> experiencing troubles while trying to compile it and moreover, it
> Any user who can log on at a vty can remap any key to reboot the
> machine (try remapping "t" to reboot to annoy your firends ;-).
> The sysctl can only be enabeled by root, so I think it would be
> useful. A more useful sysctl might be one that prevented the
> remapping of the keyboard unless y
> I thought it would be useful to have a sysctl for disabling the
> keyboard reboot sequence. This functionality is currently
> available through the SC_DISABLE_REBOOT config option, but it's
> convenient to have this capability available at runtime, too.
Just edit the keymap.
--
... every act
You don't have to change anything; IRQ sharing is allowed by PCI (and in
fact, unless you change the slot the card is in, you can't change one
without changing the other).
> Thanks for the reply. I first tried to change the IRQ from the BIOS. I saw
> that the IRQ of both the cards changes tog
> I'm sure this probably reeks of cluelessness, but I'm wondering how I can
> find each bus in the system, and if it's PCI/ISA/whatever, so that I could
> say "1 PCI bus, 1 ISA bus in system", etc. without having to probe the
> system directly, since I want to make what I'm working on portable.
S
> Daniel Lang wrote:
> > > > What I did:
> > > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf
> > > > set options CONSPEED=38400 in KERNEL
> > > > compiled and installed kernel and new bootstrap (with disklabel).
> > > > changed /etc/ttys to use std.38400 as argument to getty.
>
> "Me, too."
> The bootstraps works with 38400, (both boot2 and loader),
> but as soon as the kernel boots, it switches back to 9600.
You forgot to edit /etc/ttys to set the getty that runs on your console
port to 38400 as well.
--
... every activity meets with opposition, everyone who acts has his
rivals
>
> The software I am using in Linux (cajun - cajun.sourceforge.net)
> requires a serial display to work. What the linux driver does is emulate
> the serial display, and provides a /dev/lcd.
>
> As I am not a perl coder, I cannot modify Cajun to use the app you
> wrote, And as I am not a C coder,
> Hi Patrick,
>
>
> I didn't really explain much about the LCD+Driver...
> Basically its a parallel port display that uses the generic Hitachi
> HD44780
> chipset. What the driver for linux does is provide a /dev/lcd
> that you can address the same as you would /dev/cuaaX for a serial
> matrix o
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : > Just wondered, is there an equivelant function to ISA_PNP_PROBE that works
> : > with PCI (for example PCI_PNP_PROBE), anyone know?
> :
> : There isn't one. Go look at a PCI driver to see why.
>
&g
> Hi All
>
> Just wondered, is there an equivelant function to ISA_PNP_PROBE that works
> with PCI (for example PCI_PNP_PROBE), anyone know?
There isn't one. Go look at a PCI driver to see why.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opp
We discussed this a while back; it has some interesting (and in some
cases) undesirable side-effects. FFS tries to balance directories across
CGs in order to balance the use of CGs for file allocation. The approach
being advocated here will tend to use CGs one at a time, resulting in
poor d
> Query: I've noticed that if I use up too much stack space, the freebsd
> kernel (4.2) seems to crash very easily. Specially, if I create an
> array of size N within a function, once the function gets invoked,
> my machine just reboots. How do I find out how much stack space I've
> got? I'm assu
> so in your oppinion it would be more preferable to either
> a) attempt the dlopen(3) on each entry in the path, and give the value of dlerror(3)
>to stderr for each one
> or
> b) attempt the dlopen(3) on each entry in the path and not give any error
>information because most items would
> Sorry ... didn't think anyone was interested, and it's off topic, but
> here it is in a nutshell:
>
> The client I'm working with is moving from a Novell server to a FreeBSD
> server using Samba. They're very unhappy with Samba's behaviour in only
> 1 respect: on the Novell server, files/direct
> in a project I'm currently working on I use the access(2) call when
> going through a path for plugins to load. For each : delim on the path
> it does an access(2) to see if there is a file there, and then it
> uses dlopen(3) to open the file as a share object, and responds
> appropriatly to an
> I am developing a KLD and I am having problems getting a page fault. I am
> using a set "library" (basically a set of third party object files I build
> and then link in). This libarary requires its own chunk of memory that it
> manages and needs to be passed a pointer to that memory (and the
> > > > >It seems that only 256 bpf devices are supported. How painful would
> > > > >it be to increase that number...I assume its an 8bit varable
> > > > >somewhere?
> > > > >Are there other caveats?
> > > >
> > > >It's pretty trivial. Send a patch when you are done.
> > >
> > > I was hoping
> >I was hoping to get some useful insight before I looked into it..or if
> >there was a sound reason for not expanding them. Im hopeful someone
> >brighter will answer.
>
> Well, if anybody but you had answered I would have fixed it right away,
> but since it would probably help you if I did s
> > > You mention that I should consider software RAID if I only need level
> > 1. How much processing overhead is there? My system will be running
> > with a single 1.2GHz Athlon CPU.
> >
> > Software RAID like Vinum has proven to be faster then HW
> >RAID. Mainly because of HW Raid c
> On Fri, 23 Mar 2001, Daniel C. Sobral wrote:
>
> > Let me just pipe in a bit. Compromise seems just like the kind of thing
> > marketing or legal would want to do. The problem is that _we_ cannot
> > compromise because one cannot write a "half-way there" driver. It's a
> > technical impossibili
> > Ioctls allow user processes to make function calls within a device
> > driver; they are a mechanism for exporting functionality from a device
> > driver out into userspace.
>
> I know that, of course.
This wasn't clear from your example.
> > You don't call them from other device drivers,
> > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into
> > > sent-mail), I beg your pardon :)
> >
> > Your FreeBSD sample involved making an ioctl call, so it must have been
> > from userspace.
>
> Is anything wrong with using ioctl calls from device driver?
Perhaps a mo
> > > > Mm, so what's it doing in userspace? 8)
> > >
> > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into
> > > sent-mail), I beg your pardon :)
> >
> > Your FreeBSD sample involved making an ioctl call, so it must have been
> > from userspace.
>
> Is anything wrong w
I appear to have missed the original version of this message. Oops.
> Alexey
>
> > static inline unsigned long
> > get_kvirt_address(unsigned long address)
> > {
> > }
>
> This function returns 0 if a virtual address is not mapped.
If you're looking at using t
> > Because dinking with PCI configuration space is usually the wrong thing
> > to do from userland.
>
> So what about pciconf(8)?
It's a special case.
> > > This code is used, actually, in char device driver.
> >
> > Mm, so what's it doing in userspace? 8)
>
> Did I say I'm doing it from us
> The fpc core team is currently working on unicode support for Free
> Pascal, a pascal compiler that runs on FreeBSD/i386, and I would
> like to ask your opinion about what encoding to choose for the
> default multibyte string type. (Delphi's WideString), choices are UTF-
> 8 , -16 or UCS4.
> > It is a possible solution for me to be able to use cdparanoia and cdrdao
> > with my ATAPI CD drive. An alternative solution would be to implement
> > an atapi-cd ioctl to send a raw command to an ATAPI device, and make
> > libscg use that.
>
> Exactly, I coule dream up an API for that shovin
> > SCSI is way of encapsulating scanner commands so that you can transport
> > them to the scanner. So is USB. The command set your scanner uses is
> > probably the same as the SCSI command set, but this is not what a CAM
> > transport would give you - it would only give you the layers benea
> Le 2001-03-21, Mike Smith écrivait :
>
> > > Has anyone implemented/thought of implementing:
> > > - a CAM transport for ATAPI devices;
> > Yes. It's not a lot of work.
>
> Ah, interesting! Do you know if any source code is publicly available?
No
> > > Hey, that's not fair :-) I'd like to know how to do things the rigth way.
> >
> > You'll need to tell us what it is that you're actually doing, then, since
> > it's hard to guess from a tiny snippet like that. 8)
>
> Well, but if you didn't know, how could you tell that I'm doing somethi
> I'm trying to write a module which should be a child of the smbus.
The smbus probe/attach is broken; you're going to have to fix it before
this code will work properly. 8(
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not
> > > Under linux, PCI stuff is generally done thru set of pci* functions, while
> > > under FreeBSD there are ioctls provided by pci driver. I've been doing
> > > some code migration from linux to FreeBSD, and got thru most of it, except
> > > for things like this one:
> >
> > You are probably
> Hi hackers,
>
> Has anyone implemented/thought of implementing:
> - a CAM transport for ATAPI devices;
Yes. It's not a lot of work.
> - a CAM transport for USB scanners;
No; this wouldn't make much sense, since most USB scanners aren't SCSI
devices.
> - the Linux SCSI generic device
> > :total avail mem
> >
> > Do you mean physical memory, in which case the value of hw.physmem will
> > tellyou.
>
> Phys mem + swap, which I think I can calc pretty easily now
> that I have swap. -sc
That's not actually a useful number either. 8)
Bear in mind, for example, that progr
> Hello there,
>
> Under linux, PCI stuff is generally done thru set of pci* functions, while
> under FreeBSD there are ioctls provided by pci driver. I've been doing
> some code migration from linux to FreeBSD, and got thru most of it, except
> for things like this one:
You are probably doing
> Hi,
>
> i'm trying to do some programming on freebsd and i can't
> find 'asm/io.h'. this must be for security reasons.
>
> so how do i talk to the parallel port?
See /usr/share/examples/ppi, and the ppi(4) manpage.
--
... every activity meets with opposition, everyone who acts has his
riv
> THANKS! and compliments on your name. It was a quick and simple port
> to see if people were interested. I've sent it to the author/maintainer
> Dan Hollis but I haven't gotten a response yet. He has an email list
> on Yahoo/Groups and there is occasional traffic so it isn't dead code.
>
> Ye
> Turning PNP on into the BIOS and recompiling the Kernel with options PNPBIOS
> brings the problem back:
>
> fxp0: could not map memory !
Turn "PnP OS" off in your BIOS. We're not ready to deal with this yet.
DES unfortunately doesn't really understand the issues here.
> Rafael Tonin
>
>
> Out of idle curiousity, has the NIH syndrome died down enough that it might
> hypothetically be possible for the three major *BSD camps to cooperate on this
> kind of thing?
No, I'm afraid it hasn't.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunate
> Okay, maybe I'm missing something...
>
> 1. Has anyone tried one of these new Intel parts with BSD/OS?
> 2. Do any of the people involved with this have source licenses to BSD/OS?
>
> I am quite sure BSDi hasn't been swamped with "help, my Intel card isn't
> working" requests. I'm also quit
>
> I think its been mentioned several times in this and other threads that
> intel has a driver for LINUX that is effective documentation on the board,
> and the code is public (although you may have to stick an intel copyright
> in the code also).
It hasn't been mentioned in this thread tha
>
> On Fri, 9 Mar 2001, Mike Smith wrote:
>
> > Joe; it looks like you have some funny ideas about something that's not
> > actually very relevant. I assume that you have already gone and bought
> > Monster Cable(tm) SCSI cables, and that you have the spec
Joe; it looks like you have some funny ideas about something that's not
actually very relevant. I assume that you have already gone and bought
Monster Cable(tm) SCSI cables, and that you have the special
oxygen-free-copper SCSI controller PCBs, because none of this is going to
mean anything
> What board is this?
If this is the board I think it is, it's a Supermicro P6DLE dual Slot-1
motherboard with an integrated Intel 82559 (no external PHY).
(I had this board for some time before I gave it to David, it was
originally donated to FTL by Bob Willcox.)
> Sam
>
> - Origin
> > > Ive spoken with Mr Johnson several times. hes the biggest reason that BSDI
> > > is what it is. Amazing that hes still there. He has no concept of what the
> > > market wants. First he wanted to challenge microsoft (at similar prices)
> > > for the server market now he wants to be redhat. fu
> maybe commercial vendors would be willing to fund some freebsd projects if
> there was a positive relationship.
They do, and there is. I'm continually irritated that we can't work out
a better relationship with you/ETinc, since I think it'd be to our mutual
benefit. You're just one of thos
>
> The point here seems very simple. The intel NICs are on a large number of
> MBs and the eepro100 is the most popular card on the market. So why is
> there vitually no maintainer for arguably the most important driver in the
> freebsd tree when there are maintainers for scads of obscure, mu
> In message <[EMAIL PROTECTED]>, Dennis writes:
> >I really dont care to ask this on the list, but DG doesnt answer my private
> >emails, so I have little choice.
>
> Yup. None at all. I mean, you're getting something for free, and the
> people giving it away don't seem to be able to build th
> In message <[EMAIL PROTECTED]>, Mike Smith writes:
> >How would it *not* be atomic?
>
> Well, imagine a hypothetical broken system in which two simultaneous calls
> to mkdir, on some hypothetical broken filesystem, can each think that it
> "succeeded". A
> In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes
> :
> >is mkdir(3) guaranteed to be atomic?
>
> Yes.
Um. mkdir(2) is atomic. Note that mkdir(1) with the -p argument is
*not* atomic.
> >Are there filesystem type cases where this might not be the case
> >(NFS being my main co
>
>
> To follow up on myself, it seems to work on older Asus P2B-LS
> motherboards (onboard fxp). But only after you shutdown FreeBSD via
> 'shutdown -p now'. I don't suppose anybody knows which machines
> support this well?
The machine *should* support WOL from a cold power-on. However, I d
> I'm trying to convert a PCI network interface device driver to a KLD module.
> However, the driver is depending on a pseudo-device and the pseudo-device is
> in turn dependent on the device driver. How do I specify dependencies
> between KLD modules and what type of module shall they be?
With a
> > > I am trying to convert my PCI device driver into a KLD.
> > >
> > > So far I have done the following:
> > > 1. Built the kernel without the static linked device driver.
> > > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx.
> > > 3. Did "make all install" in /sys/modules d
> >You can't boot from the parallel-port drives, but that's a feature of the
> >PC not expecting to be able to boot from a printer rather than a FreeBSD
> >issue.
> >
> >I've personally booted FreeBSD from the old, old ATA Zip drives, the
> >ATAPI ones and of course the SCSI drives, in both whole-
>
> Is it true that freebsd can't boot from a zip drive?
No.
You can't boot from the parallel-port drives, but that's a feature of the
PC not expecting to be able to boot from a printer rather than a FreeBSD
issue.
I've personally booted FreeBSD from the old, old ATA Zip drives, the
ATAPI o
> Hi
>
> I am trying to convert my PCI device driver into a KLD.
>
> So far I have done the following:
> 1. Built the kernel without the static linked device driver.
> 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx.
> 3. Did "make all install" in /sys/modules directory.
> 4.
>
> I have about 10 min to make decision on OS of this boxi hate linux but
> I may have no choicei have to get this up as an nfs server by the end
> of the day.
Solaris. Forget Linux for NFS service.
--
... every activity meets with opposition, everyone who acts has his
rivals and unf
>
> WHo would I contact for support for freebsd for that driver?
Emulex, as they don't offer source or documentation for the hardware.
You may want to look at a Qlogic-based controller instead.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opp
> I've just finished scouring Cisco's documentation, and it doesn't look
> like FEC is anything beyond plain old trunking (with the option of
> autoconfiguration on some hardware). As long as you configure the
> appropriate ports on the switch on the other end as "SA-Trunk", or
> "Trunk", you sho
> Unless the network is lying to me again, Lyndon Nerenberg said:
> > Another company to look at is Yottayotta (www.yottayotta.com).
>
> Yeah, and they have a theme song...
>
> http://www.yottayotta.com/images/YottaYotta_Song.mp3
>
> Or is that a reason *NOT* to look at their product?
H
>
> when it comes to ibm, as far as i understand you have to hook up their
> filers to rs/6000(aix) or s/370 or s/390 systems since they are "only"
> fibrechannel or ficon attached raid subsystems, so the client platform
> is responsible for handling all the filesystem stuff.
Hrrm. The last box
> I have been poking around my kernel for quite some time now, and I have
> been doing it with various text editors and programs of that nature. It
> suddenly occured to me that there might be a better way to go about
> this. So I ask you, are there any programs that make reading and editing
> the
101 - 200 of 900 matches
Mail list logo
