subscribe me please =)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
I've put an initial version of my hack for debugging FreeBSD user threads
with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be
appreciated.
--
Doug Rabson Mail: d...@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
The binary is now available by anonymous ftp at ftp.genericwindows.com in
the pub directory. If you have problems, please email me directly.
Carlos C. Tapang
http://www.genericwindows.com
-Original Message-
From: Max Khon
To: Carlos C. Tapang
Cc: Jordan K. Hubbard ; freebsd-current@FreeB
As Wilko Bulte wrote ...
> As Doug Rabson wrote ...
> > On Mon, 10 May 1999, Wilko Bulte wrote:
> >
> > > >
> > > > Yeah. That must be why my 164lx won't netboot.
> > >
> > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit
> > > only) worked just dandy.
> >
> > That remi
Doug Rabson wrote:
> I've put an initial version of my hack for debugging FreeBSD user threads
> with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be
> appreciated.
Is the uniqueid really necessary when the address of the thread structure
is already unique within the process
I don't have time just now to attend this particular detail, which
manifests itself by swapinfo/pstat -p showing "/dev/(null)" for
device name.
The problem in short is that libkvm:kvm_getswapinfo.c has it's
fingers in the kernels memory and pulls out a dev_t without knowing
how to (and it shouldn
On Wed, 12 May 1999, John Birrell wrote:
> Doug Rabson wrote:
> > I've put an initial version of my hack for debugging FreeBSD user threads
> > with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be
> > appreciated.
>
> Is the uniqueid really necessary when the address of the
Doug Rabson wrote:
> I didn't want to use the address since it might cause confusion if a
> thread was freed and then the memory was re-allocated to create a new
> thread.
Good reason.
> I thought about the versioning but I don't think it will be a problem in
> practice since both uthread and gdb
Mike Smith writes:
>> I switched to the new config(8) today, where the ``config kernel root on..''
>> line is no longer tolerated in the config file.
>>
>> I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't
>> necessary before.
>>
>> I know I can probably put something int
On Wed, 12 May 1999, John Birrell wrote:
> Doug Rabson wrote:
> > I didn't want to use the address since it might cause confusion if a
> > thread was freed and then the memory was re-allocated to create a new
> > thread.
>
> Good reason.
>
> > I thought about the versioning but I don't think it
Doug Rabson wrote:
> Other gdb thread debugging systems tend to export a set of variables from
> the thread library which describe the important offsets in the thread
> structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset
> etc.
>
> If you think there will be a real problem, I co
Poul-Henning Kamp writes:
>In message <199905111939.vaa02...@peedub.muc.de>, Gary Jennejohn writes:
>>I switched to the new config(8) today, where the ``config kernel root on..''
>>line is no longer tolerated in the config file.
>>
>>I now have to ``boot -r'' to avoid a `can't mount root' panic. Th
On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote:
>
> I don't have time just now to attend this particular detail, which
> manifests itself by swapinfo/pstat -p showing "/dev/(null)" for
> device name.
>
> The problem in short is that libkvm:kvm_getswapinfo.c has it's
> fingers in t
In message <19990512033344.e21...@phc.igs.net>, Robert Garrett writes:
>On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote:
>>
>> I don't have time just now to attend this particular detail, which
>> manifests itself by swapinfo/pstat -p showing "/dev/(null)" for
>> device name.
>>
>>
On Tue, 11 May 1999 21:39:42 +0200, Gary Jennejohn wrote:
> I switched to the new config(8) today, where the ``config kernel root on..''
> line is no longer tolerated in the config file.
As a workaround, try the following, taken directly from LINT
options ROOTDEVNAME=\"da0s2e\"
Ciao,
On Wed, 12 May 1999 at 10:38:41 +0200, Poul-Henning Kamp wrote:
> In message <19990512033344.e21...@phc.igs.net>, Robert Garrett writes:
> >On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote:
> >>
> >> I don't have time just now to attend this particular detail, which
> >> manifests it
On Wed, 12 May 1999, John Birrell wrote:
> Doug Rabson wrote:
> > Other gdb thread debugging systems tend to export a set of variables from
> > the thread library which describe the important offsets in the thread
> > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset
> > etc.
In message <19990512034529.a5...@phc.igs.net>, Robert Garrett writes:
>> There is a dev_t passed out to pstat -s in a datastructure.
>
>Right and thats where it comes from kvm_proc.c is responsible for
>dealing with pstat at least the way I read that file
pstat >-s< is what we're talking about ri
Hi,
On Tue, 11 May 1999, Luigi Rizzo wrote:
> Hi,
> maybe i am the last one in the world to know, but were you guys aware
> of this:
>
> http://research.microsoft.com/programs/NTSrcLicInfo.htm
>
> Microsoft makes Windows NT source code available to universities
> and other "not-for-prof
Doug Rabson wrote:
> That would work. I think I only need uniqueid, sig_saved,
> saved_sigcontext, saved_jmpbuf, state and nxt. If those guys were lumped
> up at the start of struct pthread (possibly in another struct so that gdb
> doesn't need to know sizeof(struct pthread)) and marked appropriate
running FreeBSD 4.0-CURRENT i have encountered the following
problems:
1. something is wrong with psm0 driver. my Genius NewScroll PS/2 mouse works
well, but in random moment when i touch the mouse kernel starts to write to the
system log the following.
Apr 29 11:55:58 camel /kernel: psmintr:
On Wed, 12 May 1999, John Birrell wrote:
> Doug Rabson wrote:
> > That would work. I think I only need uniqueid, sig_saved,
> > saved_sigcontext, saved_jmpbuf, state and nxt. If those guys were lumped
> > up at the start of struct pthread (possibly in another struct so that gdb
> > doesn't need to
NOTE: Please Cc: s...@sra.co.jp, I am not subscribing this mailing
list, because I am a NetBSD user. :-)
> > It depends on old-config, so poor mechanism. newconfig already
> > implimented best match probe/attach.
>
> And a very useful mechanism it is. Which is why I implemented priority
Doug Rabson wrote:
> Ok, I'll see about updating my patch along these lines and I'll post up
> another one in a day or two.
One more thing... the states are subject to change, probably with new
states being added. It is important to check that the state number is
within the range that gdb was comp
On Wed, 12 May 1999, John Birrell wrote:
> Doug Rabson wrote:
> > Ok, I'll see about updating my patch along these lines and I'll post up
> > another one in a day or two.
>
> One more thing... the states are subject to change, probably with new
> states being added. It is important to check that
Doug Rabson wrote:
> I think the only state which I need to know about is PS_DEAD. If we marked
> dead threads in the public struct it might simplify things.
You use PS_RUNNING too. We could just tie down those two as PS_DEAD = 0
and PS_RUNNING = 1.
--
John Birrell - j...@cimlogic.com.au; j...@f
On Wed, 12 May 1999, Noriyuki Soda wrote:
> NOTE: Please Cc: s...@sra.co.jp, I am not subscribing this mailing
> list, because I am a NetBSD user. :-)
>
> > > It depends on old-config, so poor mechanism. newconfig already
> > > implimented best match probe/attach.
> >
> > And a very useful
> > BTW, there are many fundamental design flaws in new-bus, so I don't
> > think new-bus is comparable with newconfig, yet, even if priority
> > probe is implemented. For example:
>
> I'm not going to reply to these points as I suspect it will lead to a
> pointless flame thread. I would prefer to
(he asked :)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Tue, May 11, 1999 at 08:23:15PM +0200, Poul-Henning Kamp wrote:
>
> Isn't it more appropriate to ask where he didn't learn to read ? :-)
>
Ok. ok. thanks for the abuse :)
> >
> >> > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES).
> >
So we're agreed that this is co
On 12-May-99 Ilya Naumov wrote:
>
> running FreeBSD 4.0-CURRENT i have encountered the following
> problems:
>
> 1. something is wrong with psm0 driver. my Genius NewScroll PS/2
> mouse works
> well, but in random moment when i touch the mouse kernel starts to
> write to the
> system log the fo
Hrmmm have any commits been made on this one yet? The reason Im asking is
that as of about 2am my time last night I cvsupped to 4.0-CURRENT and I
cant build, it dies on libkvm.
It claims the error exists in /usr/src/sys/sys/vnode.h, exact error
message as follows:
In file included from /usr/src/
John Birrell wrote:
> Doug Rabson wrote:
> > Other gdb thread debugging systems tend to export a set of variables from
> > the thread library which describe the important offsets in the thread
> > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset
> > etc.
>
> > If you think the
Yes, I fixed that a few hours ago.
In message , v
ortexia writes:
>Hrmmm have any commits been made on this one yet? The reason Im asking is
>that as of about 2am my time last night I cvsupped to 4.0-CURRENT and I
>cant build, it dies on libkvm.
>
>It claims the error exists in /usr/src/sys/sys/
Daniel Eischen wrote:
> Why don't we make a libc_r_db and provide the necessary interfaces to
> gdb from that instead of having gdb know about uthread internals?
It would still mean that gdb would be linked to the uthread internals
which may not match the version of libc_r that the 3rd party progr
Andrzej Bialecki wrote:
> On Sat, 8 May 1999, Peter Wemm wrote:
>
>> It's interesting that the ANSI emulation in loader(8) is good enough to
>> do full-screen displays. It still seems to make sense to move
>> userconfig-like functionality into the pre-kernel stages including
>> moving config(8)'
John Birrell wrote:
> Daniel Eischen wrote:
> > Why don't we make a libc_r_db and provide the necessary interfaces to
> > gdb from that instead of having gdb know about uthread internals?
>
> It would still mean that gdb would be linked to the uthread internals
> which may not match the version of
We , 12 may 1999, Steve O'Hara-Smith wrote:
> > 1. something is wrong with psm0 driver. my Genius NewScroll PS/2
> > mouse works
> > well, but in random moment when i touch the mouse kernel starts to
> > write to the
> > system log the following.
> >
> > Apr 29 11:55:58 camel /kernel: psmintr:
I'm currently running into a problem, that when I start my system,
it spontaneously reboots when starting X. Has anyone else run into
this?
--
Geoff Rehmet, The Internet Solution - Infrastructure
tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800
email: geo...@is.co.za
URL: http
On 12-May-99 Ustimenko Semen wrote:
>
> Are we going to get this license? I am interested in NTFS
> source code a lot...
>
> P.S. What's happening with MS?
>
They have got a virus. I think they're calling it Open Source...
They're fighting really hard to get rid of it, but these things can h
Hi,
Does anyone else experience problems with the current kernel release
and vinum?
I've compiled a new kernel along with a make world today. After rebooting
vinum did not start: "/dev/vinum/Control: invalid operation..."
Any suggestions?
regards,
Christian
To Unsubscribe: send mail to ma
I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing
me some pains. If I boot with flags 0x80ff, everything works fine:
wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
wdc0: unit 0 (wd0): , 32-bit, multi-block-16
wd0: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at
> On Wed, 12 May 1999 09:35:36 -0400,
"Rick Whitesel" said:
> In general I believe that dynamic configuration of the system is
> extremely useful to both the development community and the user
> community. The development community has a much easier time if they
> can load / unload dr
Hi:
While I confess to not having the whole picture here, I do, of course,
have an opinion. In general I believe that dynamic configuration of the
system is extremely useful to both the development community and the user
community. The development community has a much easier time if they can lo
I just got a 18GB "22GXP" model from IBM and saw the same thing
on my -stable box.
>start_init: trying /sbin/init
>wd0: DMA failure, DMA status 5
>wd0: DMA failure, DMA status 5
>wd0: DMA failure, DMA status 5
>wd0: DMA failure, DMA status 5
--
Poul-Henning Kamp FreeBSD coreteam memb
It seems Dag-Erling Smorgrav wrote:
> I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing
> me some pains. If I boot with flags 0x80ff, everything works fine:
Hmm, I have one of those, it works wonderfully with my ata driver...
So try to use that instead, it should work then...
-
At 02:35 PM 5/12/99 +0200, Geoff Rehmet wrote:
I'm currently running into a problem, that when I start my system,
it spontaneously reboots when starting X. Has anyone else run into
this?
I had the same thing happen last night, after building a new kernel and
rebooting.
I had to go back to a ke
In message <199905121351.paa51...@freebsd.dk>, Soren Schmidt writes:
>It seems Dag-Erling Smorgrav wrote:
>> I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing
>> me some pains. If I boot with flags 0x80ff, everything works fine:
>
>Hmm, I have one of those, it works wonderfully w
Soren Schmidt writes:
> Hmm, I have one of those, it works wonderfully with my ata driver...
> So try to use that instead, it should work then...
I'll try that.
OBTW, the following comment in LINT is a little weird:
# You only need one "controller ata0" for it to find all
# PCI devices on moder
Poul-Henning Kamp writes:
> Try disabling "ultra DMA" in the BIOS, that seems to have worked for
> me on my IBM-DJNA-371800 drive.
Thanks, I'll try that if the ata driver doesn't work.
DES
--
Dag-Erling Smorgrav - d...@yes.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscrib
On Wed, 12 May 1999, Daniel Eischen wrote:
> John Birrell wrote:
> > Daniel Eischen wrote:
> > > Why don't we make a libc_r_db and provide the necessary interfaces to
> > > gdb from that instead of having gdb know about uthread internals?
> >
> > It would still mean that gdb would be linked to the
On Wed, 12 May 1999, John Birrell wrote:
> Doug Rabson wrote:
> > I think the only state which I need to know about is PS_DEAD. If we marked
> > dead threads in the public struct it might simplify things.
>
> You use PS_RUNNING too. We could just tie down those two as PS_DEAD = 0
> and PS_RUNNING
After make world this morning I received this panic :
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x14
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0155ca4
stack pointer = 0x10:0xc6864d64
frame pointer = 0x10:0xc6864d78
code segment = base
At 12/05/99, Manfred Antar wrote:
>At 02:35 PM 5/12/99 +0200, Geoff Rehmet wrote:
>>I'm currently running into a problem, that when I start my system,
>>it spontaneously reboots when starting X. Has anyone else run into
>>this?
>I had the same thing happen last night, after building a new kernel a
In 4.0-current sometimes the box will froze again after the :
"Waiting 3 seconds for SCSI devices to settle"
then nothing happens.
It was a thing happened also in early 1999, before the branch in
4.0-current and 3.1 stable, if I remember well.
Any others experience such behaviour ?
Here is again
Hi:
Since newconfig appears technically superior, what are the issues that
are hindering its acceptance?
Rick Whitesel
- Original Message -
From: Noriyuki Soda
To: Rick Whitesel
Cc: Noriyuki Soda ;
Sent: Wednesday, May 12, 1999 9:41 AM
Subject: Re: cvs commit: src/sys/pci pcisuppor
> After make world this morning I received this panic :
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x14
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc0155ca4
> stack pointer = 0x10:0xc6864d64
> frame pointer = 0x10:0xc6864d78
> co
Tomer Weller wrote:
> i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure this in
> FreeBSD or Linux (or if i even can), im on 4.0-CURRENT.
> ==
> Tomer Weller
> s...@i.am
> well...@netvision.net.il
> "Drugs are good, and if you do'em
> p
At 12/05/99, you wrote:
>>
>Could you show us the symbols around the faulting instruction at 0xc0155ca4?
>It would be even better if you have a crash dump and the gdb backtrace.
Pardon, but I am not be able to figure by myself what you asked to me...
If you can explain me step by step in a newbi
In message <003001be9c88$2669b620$d3e4b...@xyplex.com>, "Rick Whitesel" writes
:
>Hi:
>Since newconfig appears technically superior, what are the issues that
>are hindering its acceptance?
That we want to have no "config" at all.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@f
I'm trying to plug some of the holes not checking for mbuf shortage.
In particular, there are the following unchecked calls to MGET and
friends in /sys/kern/uipc_socket.c:sosend() (see patches below).
Would anyone mind if I commit these? I won't be able to commit
these before next Sunday evening,
> ahc0: irq 14 at device 6.0 on pci0
> ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
> [...]
> Waiting 3 seconds for SCSI devices to settle
> sa0 at ahc0 bus 0 target 6 lun 0
> sa0: Removable Sequential Access SCSI-2 device
> sa0: 3.300MB/s transfers
> changing root device to da0s1a
>
From: Poul-Henning Kamp
Subject: Re: cvs commit: src/sys/pci pcisupport.c
Date: Wed, 12 May 1999 17:17:49 +0200
Message-ID: <5598.926522...@critter.freebsd.dk>
phk> In message <003001be9c88$2669b620$d3e4b...@xyplex.com>, "Rick Whitesel"
writes
phk> :
phk> >Hi:
phk> >Since newconfig appears
Pierre Beyssac wrote:
> Another big problem is that there's a check in m_retry and friends
> that panics when falling short of mbufs! I really believe this does
> more harm than good, because it prevents correct calling code
> (checking for NULL mbuf pointers) from exiting gracefully with
> ENO
>phk> >Since newconfig appears technically superior, what are the issues
>that
>phk> >are hindering its acceptance?
>phk>
>phk> That we want to have no "config" at all.
>
>That is too short an answer.
No, it is complete and to the point.
>What is the definition of "config"?
config
Luoqi Chen writes :
I'm trying to get a crash dump myself, but the kernel I have
right now, is screwing up my keyboard, and I cannot even log
in!
I will try again.
Geoff.
> > After make world this morning I received this panic :
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault vi
At least put DDB in your kernel, type "trace" when it
panics and tell us what it says.
In message <19990512154854.78032.qm...@rucus.ru.ac.za>, "Geoff Rehmet" writes:
>Luoqi Chen writes :
>
>I'm trying to get a crash dump myself, but the kernel I have
>right now, is screwing up my keyboard, and I
Only one problem with that - screen and keyboard are not responding when
it panics. I'm hoping that I will be able to get a dump which I can
look at post mortem.
I'm going to try again though. The kernel I have at the moment is
totally messing up my keyboard, and I cannot even get a single user
On Wed, May 12, 1999 at 05:43:27PM +0200, Stefan Bethke wrote:
> I've discussed this with Garett back in September. The reason is quite
> simple: unless all cases of not checking for a NULL pointer returned are
> fixed (or instrumented with a panic), it is better to fail with a panic
> than with s
On Wed, 12 May 1999, Stefan Bethke wrote:
> Any pointer on Forth literature/web pages would be appreciated, especially
> if it's not the ANSI standard (I've looked at it, and it is that: a
> standard, not a reference manual or a tutorial). My Forth knowledge is
> rather rusty, I realised... last
From: Poul-Henning Kamp
Subject: Re: cvs commit: src/sys/pci pcisupport.c
Date: Wed, 12 May 1999 17:45:45 +0200
Message-ID: <5756.926523...@critter.freebsd.dk>
phk>
phk> >phk> >Since newconfig appears technically superior, what are the
issues that
phk> >phk> >are hindering its acceptance?
> On Wed, 12 May 1999 17:45:45 +0200,
Poul-Henning Kamp said:
>> What is the definition of "config"?
> config(8)
>> Why do you want to remove it?
> Why should we, as a 3rd millenium OS need a static config tool ?
For example,
- To specify the drivers which is linked statica
At 12/05/99, you wrote:
>
>At least put DDB in your kernel, type "trace" when it
>panics and tell us what it says.
Ok... it's a bit long ... (Tell me there isn't a command to write the trace
output on a disk :-)
After the panic make by "screen" ...
>trace
Stopped at ttyflush+0x48: movl 0x14(%eax)
At 12/05/99, you wrote:
>Ok, what I'd like you to do is, run this command,
> nm -n /kernel | more
>the output is the list of symbols in the kernel sorted by their addresses
>(the left-most column), page through the output, find symbols around the
>address 0xc0155ca4, and send me those symbol
< said:
> Another big problem is that there's a check in m_retry and friends
> that panics when falling short of mbufs! I really believe this does
> more harm than good, because it prevents correct calling code
> (checking for NULL mbuf pointers) from exiting gracefully with
> ENOBUFS...
I think
> > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure
> > this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT.
..snip..
> Have you tried /usr/ports/graphics/sane?
It doesn't build under 4.0-CURRENT.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To U
Hello Geoff,
Wednesday, May 12, 1999, 4:35:54 PM, you wrote:
GR> I'm currently running into a problem, that when I start my system,
GR> it spontaneously reboots when starting X. Has anyone else run into
GR> this?
yes, i'm experiencing the same problem with today's (May, 12) kernels.
Best rega
Joe Abley writes:
> (he asked :)
As I understand it, 3.2 is simply a release tag on the already existing
branch called RELENG_3 (aka 3.1-stable). So there will be no additional
branch for 3.2, just a release tag: RELENG_3_2_0 or somesuch.
-Archie
_
Pierre Beyssac writes:
> if (resid >= MINCLSIZE) {
> MCLGET(m, M_WAIT);
> + if (m == 0) {
> + error = ENOBUFS;
> + goto release;
> +
I bought two of the cards in order to decide whether or not I wanted
to use them in my research group's PII cluster. Right now, they're
plugged into a 233MHz Pentium Pro and a 400Mhz K6-2 (using an
Aladdin V-based board). I did a bunch of NFS testing over the
gigabit link last week and didn't see
Well, I did some reading through rfc821, and an email address is defined
as follows:
::= "@"
::= |
::= | "."
^^^ !
::= |
::= """ """
::= "\" | "\" | |
::= | "\"
::= any one of the 128 ASCII characters, but not any or
::= any one of the 128 ASCII characters (no exce
On Wed, May 12, 1999 at 10:28:45AM -0700, David O'Brien wrote:
> > > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure
> > > this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT.
> ..snip..
>
> > Have you tried /usr/ports/graphics/sane?
>
> It doesn't build under 4.0
>Date: Wed, 12 May 1999 14:15:12 -0400 (EDT)
>From: Bob K
>People on -current: Just to recap, adduser (and rmuser) disallow .'s in
>usernames on FreeBSD-stable; passwd(5) cites that some mailers have
>problems with dots in usernames. However, they are becoming more common,
>and are a legal part
Wilko Bulte wrote:
> PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> Writing Makefile for DynaLoader
> ==> Your Makefile has been rebuilt. <==
> ==> Please rerun the make command. <==
> false
> false: not found
> *** Error code 1
I periodically see this one reported, and It is always repaired
b
Bob K wrote:
> Well, I did some reading through rfc821, and an email address is defined
> as follows:
Email addresses != Usernames. What this suggests to me is that having
an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.ca
On Wed, 12 May 1999, David Wolfskill wrote:
> >Date: Wed, 12 May 1999 14:15:12 -0400 (EDT)
> >From: Bob K
>
> >People on -current: Just to recap, adduser (and rmuser) disallow .'s in
> >usernames on FreeBSD-stable; passwd(5) cites that some mailers have
> >problems with dots in usernames. Howe
In the last episode (May 12), Mark Murray said:
> Bob K wrote:
> > Well, I did some reading through rfc821, and an email address is
> > defined as follows:
>
> Email addresses != Usernames. What this suggests to me is that having
> an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK.
On Wed, 12 May 1999, Mark Murray wrote:
> Bob K wrote:
> > Well, I did some reading through rfc821, and an email address is defined
> > as follows:
>
> Email addresses != Usernames. What this suggests to me is that having
> an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK.
Sigh.
NAKAGAWA Yoshihisa writes:
> > mechanism was unacceptable -- else we would have used it years ago.
> It is not formal core decision.
On whose authority do you say that? Garrett is a core team member.
> > Our policy in all areas has been that we'd rather do the Right Thing
> > than follow the cro
I also am experiencing a kernel panic whenever I start X using today's
kernel. Thanks
Kenneth Culver
Computer Science Major at the University of Maryland, College Park.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
My personal opinion is that static configuration is a subset of dynamic
configuration.
The eventual aim is to have a kernel which is a very sparse skelaton,
with very few services and drivers loaded (in fact possibly none).
At boot time, the needed drivers and services are loaded and configured
(
i tried it, i belive it's only for SCSI scanners, my UMAX 1220P is for the
parallel port.
On Wed, 12 May 1999, Edwin Culp wrote:
> Have you tried /usr/ports/graphics/sane?
>
> ed
--
==
Tomer Weller
s...@i.am
well...@netvision.net.il
"Drugs are good, and if
Ustimenko Semen wrote:
>
> Hi,
>
> On Tue, 11 May 1999, Luigi Rizzo wrote:
>
> > Hi,
> > maybe i am the last one in the world to know, but were you guys aware
> > of this:
> >
> > http://research.microsoft.com/programs/NTSrcLicInfo.htm
> >
> > Microsoft makes Windows NT source code available
As Gianmarco Giovannelli wrote ...
>
> In 4.0-current sometimes the box will froze again after the :
> "Waiting 3 seconds for SCSI devices to settle"
> then nothing happens.
> It was a thing happened also in early 1999, before the branch in
> 4.0-current and 3.1 stable, if I remember well.
>
> An
As e...@habatech.no wrote ...
>
> On 12-May-99 Ustimenko Semen wrote:
> >
> > Are we going to get this license? I am interested in NTFS
> > source code a lot...
> >
> > P.S. What's happening with MS?
> >
> They have got a virus. I think they're calling it Open Source...
Na... it's called US
:I think we need to think a bit more about the right semantics before
:making such a change. M_WAIT is supposed to mean `I am in process
:context and don't mind sleeping in order to get an mbuf, but there is
:too much locking going on inside the network stack to be able to
:safely sleep without se
/usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catal
og -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sg
ml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/
sgml/freebsd.dsl -t sgml handbook.sgml
/usr/local/bin/ja
> Wilko Bulte wrote:
> > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> > Writing Makefile for DynaLoader
> > ==> Your Makefile has been rebuilt. <==
> > ==> Please rerun the make command. <==
> > false
> > false: not found
> > *** Error code 1
>
> I periodically see this one reported, and It
Maybe whoever committed the supposedly innocuous dev_t changes should
back it out.
Just a thought.
-Matt
Matthew Dillon
:
:It looks like something has come unstuck
1 - 100 of 164 matches
Mail list logo
