[Please CC me as I am a stable user and not on the -current list]
I'm running stable on a box at home and wanted to check if the -current kernel
fixed a problem with my CD-RW drive.
So I downloaded the boot floppies from current.freebsd.org, the
20010419 snap (which John B. tells me installs OK
> Weird, I installed the April 19 snap here locally on a testbox without any
> problems.
Rgr, I'll try Apr 19th and send another note with some debug info if it is
still dying.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[please CC replies; I'm not on the -current list]
I'm trying to boot a -CURRENT kernel to confirm it really does fix a problem
with my hardware (see kern/26046).
I've tried a couple of snapshots from current.freeebsd.org between 1st the 15th
April. None has booted. Each dies with an integer d
I wrote:
> when fed through an ANSI preprocessor (i.e. not "gcc -E" and not /usr/bin/cpp
> on 3.x!). This also works if (e.g.) addr is defined on the command line.
and of course I _meant_ to write "(i.e. "gcc -E" and not /usr/bin/cpp..."
gcc -E _is_ an ANSI cpp.
To Unsubscribe: send mail to
> #define addr 192.186.2.5
> #define mask 255.255.240.0
>
> #define rule(ADDR,MASK) add pass tcp from ADDR ## : ## MASK to any 25 setup
> rule(addr,mask)
This is a well-known artifact of the ANSI C rules. You need to do two levels
of macro in order to get the macro args expanded in the paste o
> I seem to remember there once was a comment in a well-known body of code,
> which
> went something like:
> "You are not supposed to understand this."
It was (IIRC) the process switching magic at the heart of fork() in V7 (and
earlier, I assume).
To Unsubscribe: send mail to majord...@freebsd
Well stone the bloody crows.
System: HP Kayak XA 440BX M/b, P-II, Quantum Fireball ex4.3a
For months I've been running with no flags on either wdc0 or wd0.
Having followed the recent discussions about DMA mode etc I looked at
LINT and added "flags 0xa0ff" to wd0. Rebuilt the system using the
lat
I've just done my first CVSup since the 3-Stable split, using RELENG_3.
This was after Matt D. committed a couple of VM fixes back to the 3-S branch.
I have also enabled 32-bit DMA on my drive at the same time (amazing
what you can learn from reading LINT - and read speed went from 3Mb/s to
12Mb/s
> What's wrong with us.unix.kbd?
This also swaps a bunch of other things - Grave<->Esc, BS<->Del, etc. It was
more confusing, so I made a new keymap.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
my vote: A version of the standard keymap with CapsLock and LeftCtl functions
swapped so the control key is under my left finger like God intended!
Greg,
home of us.iso-lock-ctl.kbd
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Now we've gone and got forked, can someone please give us examples of cvsup
files for those that want to follow 4-current and those that want to follow
3-stable.
Thanks!
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
noticed this when it tried to create lotsa devices in a read-only /dev at boot
time.
Patch:
hellcat## diff -u rc.orig rc
--- rc.orig Mon Jan 18 14:20:49 1999
+++ rc Mon Jan 18 14:20:59 1999
@@ -27,7 +27,7 @@
ccdconfig -C
fi
-if [ -n $vinum_slices ]; then
+if [ -n "$vinum_slices" ]
12 matches
Mail list logo
