In message <[EMAIL PROTECTED]> "Jacques A. Vidrine" writes:
: On Wed, Feb 21, 2001 at 08:53:57AM -0700, Warner Losh wrote:
: > The standard requires that (void *) &foo == (void *) &foo->s
:
: Thanks, that is what I was trying to track down but couldn't find
In message <[EMAIL PROTECTED]> "Jacques A. Vidrine" writes:
: Likewise if the first member were a more complex data type, but
: nevertheless the same between the different structures.
:
: It seems safe to me, but I can't explain why :-)
It is obfuscated 'C', but it is safe. The standard require
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: On Thu, Feb 22, 2001 at 10:32:13AM -0500, Justin McKnight wrote:
: > I cant figure out to get freebsd 4.2 to recognize
: > and enable my 3com cardbus card?
:
: FreeBSD currently doesn't support cardbus cards.
FreeBSD -stable doesn't sup
In message <[EMAIL PROTECTED]> Peter Seebach writes:
: In message <9631.983048712@critter>, Poul-Henning Kamp writes:
: >No it is not and it never was.
:
: The C committee believes it is.
I do not believe you. Such a "believe" does not appear to be embodied
in the C-99 standard.
The standard (
In message <[EMAIL PROTECTED]> Peter Seebach writes:
: >I searched through the standard extensively to see if "allocates
: >space" is defined and couldn't find anything other than 'the poitner
: >can be used to access the space allocated.'
:
: EXACTLY!
:
: If it can't actually be used, then some
In message <[EMAIL PROTECTED]> Peter Seebach writes:
: In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes:
: >OTOH, the *only* way to get non-overcommit to FreeBSD is for someone who
: >*wants* that feature to sit down and code it. It won't happen otherwise.
:
: So, out of idle curiousity:
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: What I can't understand is the reference to missing support for large
: file sizes - as far as I know, that's one of FreeBSD's strengths! Anybody
: care to guess what they mean here?
It is crap. FreeBSD's API supports up to 2^63 byte fil
In message <[EMAIL PROTECTED]> Michael Lucas writes:
: Is the Handbook correct, or are unified diffs preferred? I'll be
: happy to fix my article and submit a PR to correct the Handbook if
: this is the case.
diff -c or diff -u is 1000% better than palin diff. That's what is
ment by "context" i
In message <[EMAIL PROTECTED]> Jonathan
Lemon writes:
: You can't find the answers to any of these in the datasheets. The
: datasheets may provide a tiny bit of information, and hint at how things
: actually operate, but there is not sufficient information to develop a
: driver from them.
Their
In message <[EMAIL PROTECTED]> Dima Dorfman writes:
: Right now, if you try to detach an md device that's currently mounted,
: you will get a panic (maybe not immedietely, but it will come, esp. if
: you ever try to use that mountpoint again). I'm pretty sure this is a
: known problem, with the s
In message <5663.984480931@critter> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, Dima Dorfman write
: s:
: >Hello -hackers
: >
: >Right now, if you try to detach an md device that's currently mounted,
: >you will get a panic (maybe not immedietely, but it will come, esp.
:
: This
In message <8773.984501263@critter> Poul-Henning Kamp writes:
: >We should then fix the rest of the system to deal with disks that
: >disappear without notice.
:
: That was the point yes :-)
Cool. When this happens, the forgetful ata flash ejectors of the
world will be happy :-)
Warner
To Uns
In message <[EMAIL PROTECTED]> Soren Schmidt writes:
: This all needed the patch to subr_disk.c that I made earlier today,
: but now we can actually do it, however some of the cleanup action
: should be done by the higher levels and not by the device driver...
Most of the crashes I've seen are in
In message <[EMAIL PROTECTED]> Soren Schmidt writes:
: It seems Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> Soren Schmidt writes:
: > : This all needed the patch to subr_disk.c that I made earlier today,
: > : but now we can actually do it, however some
In message <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> "Matt Simerson"
writes:
: I have found that there IS a variety of reasons NOT to do it that way. The
: most obvious is that you might not have console access, thus making it
: pretty hard to access the machine while it's in single
In message <[EMAIL PROTECTED]> Robert
Watson writes:
: On Fri, 23 Mar 2001, Warner Losh wrote:
:
: > You'll also get better milage out of make -j N (say 3 or 4) and doing
: > things sequentially. It is safer and runs just as fast.
:
: Dunno if it was a temporary compile
In message <[EMAIL PROTECTED]> Maxime Henrion writes:
: Here is a patch to select the modules you want and don't want.
: The patch is for /usr/src/sys/modules/Makefile from RELENG_4.
My patch is even simpler:
Index: Makefile
===
RCS
In message <[EMAIL PROTECTED]> Peter Pentchev writes:
: See -arch for a detailed discussion :)
Right. I just did. I still think mine is *MUCH* simpler and easier
to deal with.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Marc W writes:
: Excellent, I will look for that. However, in the meantime, on
: older systems (3.x, 4.x, etc ...), is the below assertion correct?
I ran mail over NFS for a while, as well as using a mail program that
didn't do locking to sort my mail. In both
In message <[EMAIL PROTECTED]> Luigi Rizzo writes:
: [Charset iso-8859-1 unsupported, filtering to ASCII...]
: > I currently have a Sharp pc ax20 laptop with an inbuilt rtl8139 nic. It works
:
: i have an AX10, similar design i suppose, and it works fast and fine for me
: at 10megs. Are you sure
In message <[EMAIL PROTECTED]> "Pedro F. Giffuni" writes:
: They don't have FreeBSD boxes. I understand the tool will eventually
: be available but the authors don't want to be bothered about it right
: now.
I think they may have had problems using openbsd's config on the
FreeBSD kernel.
Warner
In message <[EMAIL PROTECTED]> Arjan Knepper writes:
: Could anyone make recommandations on the STL to use with C++. I'm using
: the build in gcc 2.95.2 on -stable and build in gcc 2.95.3 on -current.
:
: What is preffered the build-in STL (/usr/include/g++) or STLport?
We use the builtin stl an
In message <[EMAIL PROTECTED]> Ceri Storey writes:
: but these two command lines give me different results, eg:
: cds220# head -c 32 /dev/ad0c | hd
: so they are not equivalent?
ad0 is the whole device. ad0c is the whole slice. These can be the
same, but are often different. /dev/ad0 is the ri
In message <[EMAIL PROTECTED]> Bill Moran writes:
: I'm a little confused here, if access() is such a serious security
: problem that it should _never_ be used, do we now have a major problem
: with a large amount of software in the base system?
Access(2) can be raced. If you say access("fred")
In message <[EMAIL PROTECTED]> Rick Bradley writes:
: If the program is running with more privileges than the user this
: is a truck-sized hole (or at least SUV-sized).
Wouldn't that be SUSV2-sized hole?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in
In message <[EMAIL PROTECTED]> Paul
Herman writes:
: Shouldn't the stat(2) manpage then also carry the same warning that
: access(2) has (apparently dating back to 4.4BSD-Lite)? ...or maybe
: even a suggestion to use fstat(2) instead...
No. stat can be used safely. In fact, it can even be use
In message <[EMAIL PROTECTED]> David Malone writes:
: Don't you need fstat to do this? (In which case you may as well just
: open the file and fstat it anyway).
There are times when you are traversing the tree that you need to stat
before and after you open.
Warner
To Unsubscribe: send mail to
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: On Sun, Apr 01, 2001 at 10:55:23AM +1000, Greg Black wrote:
: > Many years ago I implemented a new interface that I called
: > eaccess() which replicated the work of access, but tested
: > against the effective uid and gid. I'd like to see
In message <[EMAIL PROTECTED]> Andrew Hesford writes:
: Hrm... I'm sorry then. I have no idea why the Handbook asks you to zero
: out the device, it consumes a lot of time and really isn't necessary. I
: wonder if that could be the source of your problem.
The handbook should say that only the fir
In message <[EMAIL PROTECTED]> Andrew Hesford writes:
: On Sat, Apr 07, 2001 at 07:26:30PM -0600, Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> Andrew Hesford writes:
: > : Hrm... I'm sorry then. I have no idea why the Handbook asks you to zero
: > : out the de
In message <[EMAIL PROTECTED]> Luigi Rizzo writes:
: > In message <[EMAIL PROTECTED]> Andrew Hesford writes:
: > : Hrm... I'm sorry then. I have no idea why the Handbook asks you to zero
: > : out the device, it consumes a lot of time and really isn't necessary. I
: > : wonder if that could be the
In message <[EMAIL PROTECTED]> "Brian W.
Buchanan" writes:
: Do PCI PCMCIA adapters work in 4.3?
No.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Warner Losh writes:
: In message <[EMAIL PROTECTED]> "Brian
:W. Buchanan" writes:
: : Do PCI PCMCIA adapters work in 4.3?
:
: No.
I should amplify a little here.
The pci cards that plug into a desktop route interrupts over the pci
bus.
In message <[EMAIL PROTECTED]> "Vladimir B. Grebenschikov" writes:
: May be it need to create some makefile variable like KERNEL_MODULES,
: that can be defined in /etc/make.conf to limit list of modules
: to build/install, it is not very good idea to spend a lot of
: CPU time building modules, t
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: On Mon, Apr 16, 2001 at 09:51:20AM +0400, Vladimir B. Grebenschikov wrote:
: > I have idea about modules build/install process:
:
: Warner (imp) was to commit this fuctionality to 5-current (and back port
: to releng_4 after 4.3-RELEASE).
In message <[EMAIL PROTECTED]> Coleman Kane writes:
: It would also be nice to be able to update third-party modules (like those =
: in
: ports, x11, etc...) after a kernel recompile. Perhaps some way of setting t=
: hese
: up into /usr/local?
I do this all the time at work with 4.2-BETA. But yo
In message <[EMAIL PROTECTED]> David Miller
writes:
: Anyone know of a way to get a low cost port of some kind to to simple
: state change detection? The specific purpose is to time external events
: which are triggered by breaking an LED light beam. Millisecond resolution
: would be fine.
:
:
In message <60546.987709317@critter> Poul-Henning Kamp writes:
: Use the pps driver and you get microsecond jitter with nanosecond
: resolution.
While I usually see microsecond jitter, I have seen it as high as a
few milliseconds when the interrupt load on the machine was high and
the cpu was slo
In message <60866.987710568@critter> Poul-Henning Kamp writes:
: The BIOS misuse of SMM mode can give you jitter in the 1msec range
: and there is not much you can do about it. I found out when I
: clocked a motherboard with a 14.318 derived from a Rb, and timed
: 1Hz pulses derived from a Cs.
In message <66167.987742147@critter> Poul-Henning Kamp writes:
: Then the disk is probably running in PIO mode which thrashes your
: interrrupts.
That's likely right. This was a real low end machine, designed to be
smalffl and cheap.
: >The pentium systems were much better about this.
:
: Prob
In message <[EMAIL PROTECTED]> Lists Account
writes:
: I just was wondering if anyone out there knew of any drivers that support
: the pccard PCI -> PCMCIA bridge adapter, also made by pccard (see
: www.pccard.co.uk), similar to the ISA -> PCMICIA bridge adapter that is
: currently supported unde
In message <[EMAIL PROTECTED]> Peter Pentchev writes:
: I think there was talk on -mobile about this recently, with someone
: (I can't remember who, but Warner Losch comes to mind) saying that
: this cannot be done in 4.x-stable at the moment, and it shall not
: be done in 4.x-stable ever. It's s
In message <[EMAIL PROTECTED]> Brandon Fosdick writes:
: A search of the archives revealed that PCI adapters for orinoco cards
: don't work yet. So I guess there's no hope of getting the MiniPCI card
: working either?
Nope.
: Does it work in -current?
Nope.
I'm working on it.
Warner
To Unsub
In message Rich Morin writes:
: I am quite willing to write a first cut at the client code, but I
: think I need to get some buy-in from the folks who are generating
: the advisories. Specifically, I need version characterization data
: in a form which ca
In message <[EMAIL PROTECTED]> Lists Account
writes:
: Just to say, I seem to have fbsd recognizing my pci cardbus bridge in
: 4.3-RELEASE however, it doesnt pick up the orinoco card plugged into
: there, is this because of bugs mentioned on the list so far or is this for
: another reason?
The 4
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.
Actually, I think he's asking for a convenience functi
In message <[EMAIL PROTECTED]> Lists Account
writes:
: Any suggestions?
Be patient.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> Peter Pentchev writes:
: Yes, I had the same problem with my PCMCIA->PCI bridge. I solved it with
: the following patch, which adds a new option to pccardd: -S maxslot.
: Then, add -S 1 to pccardd_flags in your /etc/rc.conf, and you're all set.
On current, without
In message <[EMAIL PROTECTED]> Jos Backus writes:
: dbtool.h:99: declaration of `__sF' as array of references
: void stdin(const Config& config); <-=== line 99
stdin is #defined to be __sF[0].
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bo
In message <[EMAIL PROTECTED]> Peter Seebach writes:
: In message <[EMAIL PROTECTED]>, Jos Backus writes:
: >Yeah, I am just puzzled as to how this can build at all on other platforms
: >(Linux?), unless they don't define this variable.
:
: Many of them probably have it as an external object, not
In message <[EMAIL PROTECTED]> Doug Ambrisko writes:
: Any generic PCMCIA IDE based thing should work. I might stop using an
Other than flash, I have 5 different PCMCIA IDE based things, and they
all work.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hacker
In message <[EMAIL PROTECTED]> Kevin Day writes:
: I tried sending this from my work account, but our new exchange server isn't
: exactly sending mail correctly... Excuse the duplicate post if you see it.
: :)
It sounds like the PCI card that you are trying to read from is
generating the pci faul
In message <[EMAIL PROTECTED]> Kevin Day writes:
: The PCI target itself isn't doing anything like that, but it's possible that
: the PCI-PCI bridge we're going through might be. In any case, getting the
: NMI isn't really all that bad, it's stopping the chipset from getting hung
: on a infinite r
In message <[EMAIL PROTECTED]> "David Mr. Hackers O'Brien" writes:
: I went thru this last month -- bsd.*.mk assumes /usr/src and the base
: compilers. Peroid. People didn't want to accept that, but you are
: giving more proof of it. If you want to change the assumptions of about
: the base sys
I have a cdrom that defies logic:
1:14am harmony:/cdrom[51]> df /cdrom
Filesystem 1024-blocks UsedAvail Capacity Mounted on
/dev/acd0a 54 540 100%/cdrom
1:14am harmony:/cdrom[52]> du /cdrom
325460 /cdrom/chujiten/data
146 /cdrom/chujiten/gaiji
325608
In message <[EMAIL PROTECTED]> Andrew Gallatin writes:
: If anybody else feels like testing this, please do so. Is there
: some interest an MFC?
If this fixes the problem where sometimes the system would hang when
writing to MFS, there'd be a large interest. However, there'd be
little interest
In message Garance A Drosihn writes:
: Well, the most suspect directory is /cdrom/chujiten/data
:
: What is in that directory? Might it be some large database-type
: file(s) which have large holes in it(them)?
Japanese/English dictionary. Yes, it really i
In message <[EMAIL PROTECTED]> Josef Karthauser writes:
: I was thinking about doing this, but several people have objected to
: an MFC on the basis that lots of people already use md on -stable, and
: the new md is a slightly different animal.
My objection is based on the notion of removing MFS
In message <[EMAIL PROTECTED]> Doug White
writes:
: Two things mainly cause du-vs-df sizing problems:
: . hardlinks
: . sparse files
No. DU uses the actual number of blocks in file. Hardlinks aren't an
issue here because I did a df on the mountpoint.
Warner
To Unsubscribe: send mail to [EMAI
In message <[EMAIL PROTECTED]> Jon Parise writes:
: 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 runti
In message <[EMAIL PROTECTED]> Jon Parise writes:
: In addition, I prefer my approach here because it's a single,
: known toggle that doesn't involve messing with other parts of the
: system. I might just want to disable keyboard rebooting
: temporarily. This seems like the most intuitive way to
In message <[EMAIL PROTECTED]> Jason Andresen writes:
: If only FreeBSD could boot from those funky M-Systems flash disks.
We boot FreeBSD off of M-Systems flash disks all the time. Don't know
what the problem is with your boxes.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
In message <[EMAIL PROTECTED]> Alexander Langer
writes:
: Thus spake SJ ([EMAIL PROTECTED]):
:
: Hi!
:
: > 1. "ioconf.c" contains struct config_resource and
: > config_device definitions for declarations in
: > "config" file. But I noticed that for some devices
: > e.g. device
In message <[EMAIL PROTECTED]> j mckitrick writes:
: I'd like to finalize the newbus work by changing inb()/outb() calls to
: bus_space_write calls. Is there a device where this has been partially done
: already? I'd like to see the old and new styles, then i would fix the
: vpo/imm zip driver f
In message <[EMAIL PROTECTED]> SJ writes:
: But still the name "private" confuses me...according
: to
: me it should have been "bus_public.c". Any comments?
Yes. You aren't allowed to use anything that's inside of
bus_private.h in your driver. That's why it is called private. Only
certain part
In message <[EMAIL PROTECTED]> j mckitrick writes:
: Any devices using the ppbus will end up sharing the hardware port. If i want
: to access this resource info, should i store it in my local driver's softc
: structure, or extract it from the parent device (ppbus)?
There should be a method for g
In message <[EMAIL PROTECTED]> j mckitrick writes:
: Well, all of the resources have already been allocated when the ppc device
: has been attached. The hardware port and interrupt have already been
: reserved and stored in the softc data structure for ppc. All devices
: attached to ppc, like pp
In message <[EMAIL PROTECTED]> j mckitrick writes:
: In the probe routines, the values of the hardware ports are changing from
: one chipset to the next. Throughout the ppc driver, the regular macros are
: used to access the parallel port control registers, but in the probe routine
: it reverts t
In message <[EMAIL PROTECTED]> j mckitrick writes:
: I will newbussify all macros, and any inb/outb calls i find that are not
: inside a probe function.
:
: How is that?
Ummm, including inb/outb that are in the probe would be better. This
would allow us to write a pcmcia attachment to the ppc
buildworld uses the boot blocks installed on the system to build
sysinstall, rather than the ones that are build tree.
.if ${MACHINE} == "i386"
file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
echo "size_t boot0_size = sizeof(boot0);" >> makedevs.tmp
file2c
In message <70325.991758797@critter> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
: >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote:
: >> Is there any reason not to MFC the new md(4) functionality
: >
: >Zero reason not to.
:
: Others see it di
In message <[EMAIL PROTECTED]> j mckitrick writes:
: 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 hardco
In message Nick Hibma writes:
: > > - 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 dum
In message <[EMAIL PROTECTED]> j mckitrick writes:
: How would you recommending fixing this, taken from the ex driver?
By deleting it.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> j mckitrick writes:
: | 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.
Hints will be in -stable
In message <[EMAIL PROTECTED]> Warner Losh writes:
: In message <[EMAIL PROTECTED]> j mckitrick writes:
: : How would you recommending fixing this, taken from the ex driver?
:
: By deleting it.
Let me expand a little. The reason I advocate deleting it is because
there are too many
In message <[EMAIL PROTECTED]> "Matthew N.
Dodd" writes:
: Except that the 'ex' driver uses a non-destructive probe.
I just know that I've had some hardware start working by deleting ex
from the kernel. I'll see if I was wise enough to document said
hardware...
Warner
To Unsubscribe: send mai
In message <[EMAIL PROTECTED]> Mike Smith writes:
: Actually, I do recall discussion over 'wd' being end-of-lifed in 4.x. I
: suspect that it would make sense to EOL 'mfs' in a similar fashion. I
: don't think there's a lot of good sense in pulling it out at an arbitrary
: point, though, any
In message <[EMAIL PROTECTED]> j mckitrick writes:
: Okay, there is something i'm not understanding here. In the ed driver,
: there are many possible cards, which each have different i/o ports, correct?
Not really. The ed driver is the most twisted driver in the tree when
it comes to probe.
:
In message <[EMAIL PROTECTED]> John Baldwin writes:
: Of course, this begs the question of why you are free'ing a const. :)
Sometimes that's the only handle that you have on the object :-). I
sometimes think that changing free to be const void * is the right
answer, but that has its own set prob
I have the need to read a whole pile of DEC Rainbow 100 floppies. I
can do it on the DEC Rainbow, but that's a huge pita since it isn't
networked. I'd like to either connect a RX-50 drive to my machine, or
use a 1.2M 5.25" floppy drive that I can scrounge easily enough to do
the deed.
80 trac
In message <[EMAIL PROTECTED]> Mark Hittinger writes:
: I'd actually recommend trying to use kermit to get the data out via the
: serial port first :-) There is a rainbow kermit out there.
Not an option. I have about 100 floppies to transfer. I know I could
set this up, but 9600 baud is just t
In message <[EMAIL PROTECTED]> James Housley writes:
: Mark Hittinger wrote:
: >
: > MSDOS world only and not CPM. I'd bet there are utilities on simtel20 that
: > would read a CPM format floppy in 40 track format. I formatted them on the
:
: A quick search returned 10 matches with this one lo
[[ Lots of details on how to do this deed, or at least the format
of the Rainbow disk, follow. Hit 'n' or 'd' if you don't care ]]
In message <[EMAIL PROTECTED]> Ian Dowse writes:
: The fdcontrol program allows most of the paramaters to be set to
: match the disks, but unfortunately it cannot
In message
<[EMAIL PROTECTED]> Doug
Rabson writes:
: Actually, the ex driver does have an identify method. The issue is that
: the identify method uses 'unallocated' ports to do its search. It ought to
: allocate them, do its tests and release them for the real probe but it
: gets messy due to th
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > 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
In message <[EMAIL PROTECTED]> Peter Wemm writes:
: If you built the
: entire system with NOSHARED=NO, then /bin/ls, /bin/sh etc will be dynamically
: linked and the patches will probably work. However, you had better have
: /usr on your root (/) file system or you wont be able to boot. Linux's
In message <[EMAIL PROTECTED]> Mark Santcroos writes:
: What is the difference between the present rc scheme and the NetBSD one?
The NetBSD rc scheme, in a nutshell, put each thing into its own file
and does order dependencies automatically. Ours is one big monolithic
beast that kinda can do ext
In message <[EMAIL PROTECTED]> Mark Santcroos writes:
: Can it be called SysV style? Or not seperated in that way?
: (I must say, the big ugly rc thing is the only thing I don't like about
: FreeBSD, I'm very much in favor of the SysV style init. But thats another
: war ;)
It specifically isn't S
In message <[EMAIL PROTECTED]> Doug Barton writes:
: reason is that when you say "System V" anything, people have immediate
: negative reactions that are based purely on emotion.
S01My S02reactions S03to S04system S05V S06is S07not S08based
S09purely S10on S11a S12pruely S13emotional S14reaction.
In message <[EMAIL PROTECTED]> Matt Dillon writes:
: I kinda like our scheme... at least I like the single monolithic
: /etc/rc.conf file. It makes maintaining and installing machines
: utterly trivial whereas having a billion little files each with
: one or two options in them m
In message <[EMAIL PROTECTED]> Sergey Babkin writes:
: Or a drawback. Encoding the order in the names makes changing
: the order or disabling some files easy, without any neccessity to
: edit the contents of the files.
:
: Though I haven't seen the NetBSD approach, maybe it actually is better.
In message <[EMAIL PROTECTED]> void writes:
: On Mon, Jun 11, 2001 at 05:56:45PM -0600, Warner Losh wrote:
: >
: > With the netbsd approach, you remove the file, and all things taht
: > depend on it fail. as it should be :-)
:
: I'm pretty sure you turn it off in rc.conf,
In message <[EMAIL PROTECTED]> Dave Hayes writes:
: I agree completely. One of the points that should be kept in mind
: (IMO) is that the SysV RC style dominates Linux...a fact I've used to
: convince people that FreeBSD administration is easier, faster,
: better...etc.
But the NetBSD style is e
In message <[EMAIL PROTECTED]> Andrew Hesford writes:
: New "modules"? Isn't that just the same as /usr/local/etc/rc.d/ ? I side
: with Mr. Dillon, I hope things stay the way they are.
No. It isn't. Our current /usr/local/etc/rc.d is a *SUBSET* of what
the NetBSD system provides. Right now it
In message <[EMAIL PROTECTED]> Matt Dillon writes:
: What I really hate is the SysV/Linux/Solaris style of rc.d configuration
: directories where you create/maintain softlinks in specially named
: directories (named after the run level) to a master set of
: startup files. Blech.
In message <30671.992330850@critter> Poul-Henning Kamp writes:
: Well, the application date is what counts, and that's mar1992, but I'm
: pretty sure that Bill Jolitz had them beat to that date already...
I'm pretty sure that VMS 3.x used a similar technique. I have my old
VMS internals docs fro
In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
: The patent system is broken and we need to focus our energies on
: reforming it, not on trying to bend ourselves into impossible shapes
: to conform to the damage it's done.
Exactly. My thoughts are to hell with them. The patent sighted is
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: I've contacted Luke Mewburn (the guy behind the new NetBSD rc system)
: and he's keen to chat to FreeBSD-heads after his talk at USENIX (FREENIX
: track). I can't make it, but I'd encourage interested parties from the
: FreeBSD community to c
In message <[EMAIL PROTECTED]> Doug Barton writes:
: > in fact, the require keyword isn't sufficient in it's own. there
: > should be pre_require and post_require keywords since nfsd needs to
: > start mountd before to start nfsd then rpc.statd and rpc.lockd have to
: > be started after nfsd.
:
:
401 - 500 of 2062 matches
Mail list logo