this already locally?
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> gr...@freebsd.org
On Thu, Jan 08, 2009 at 10:44:20PM -0500, Daniel Eischen wrote:
> On Thu, 8 Jan 2009, Brian Fundakowski Feldman wrote:
>
>> It appears that the post-fork hooks for malloc(3) are somewhat broken such
>> that
>> when a threaded program forks, and then its child att
On Thu, Jan 08, 2009 at 11:09:16PM -0800, Julian Elischer wrote:
> Brian Fundakowski Feldman wrote:
>> On Thu, Jan 08, 2009 at 10:44:20PM -0500, Daniel Eischen wrote:
>>> On Thu, 8 Jan 2009, Brian Fundakowski Feldman wrote:
>>>
>>>> It appears that the pos
On Fri, Jan 09, 2009 at 07:42:32PM +0200, Kostik Belousov wrote:
> On Fri, Jan 09, 2009 at 11:34:26AM -0500, Brian Fundakowski Feldman wrote:
> > On Thu, Jan 08, 2009 at 11:09:16PM -0800, Julian Elischer wrote:
> > > Brian Fundakowski Feldman wrote:
> > >> On Thu, Ja
On Fri, Jan 09, 2009 at 09:39:08AM -0800, Julian Elischer wrote:
> Brian Fundakowski Feldman wrote:
>> On Thu, Jan 08, 2009 at 11:09:16PM -0800, Julian Elischer wrote:
>>> Brian Fundakowski Feldman wrote:
>>>> On Thu, Jan 08, 2009 at 10:44:20PM -0500, Daniel Eischen w
On Fri, Jan 16, 2009 at 02:36:06PM -0800, Jason Evans wrote:
> Brian Fundakowski Feldman wrote:
> > Could you, and anyone else who would care to, check this out? It's a
> regression
>> fix but it also makes the code a little bit clearer. Thanks!
>>
>> Index
On Mon, Jan 19, 2009 at 07:41:35PM -0500, Brian Fundakowski Feldman wrote:
> On Fri, Jan 16, 2009 at 02:36:06PM -0800, Jason Evans wrote:
> > Brian Fundakowski Feldman wrote:
> > > Could you, and anyone else who would care to, check this out? It's a
> > regression
&
> So after a fork(), there is no need to reallocate anything,
> it can just be reinitialized if necessary.
In this case it's not a matter of locks needing to be again initialized
-- the mutexes are fine -- they just need to be relinquished,
m
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
gr...@freebsd.org _ __ ___ | _ ) __| \
Fr
eeping the ints that SHOULD be ints), which I am pretty sure I've
done properly. I've also removed bogus casts, added new ones, and generally
cleaned up the code into a more maintainable lump.
I suppose by learning the code and doing the cleanups/fixes, I've designated
mysel
On Fri, 18 Jun 1999, Ruslan Ermilov wrote:
> On Fri, Jun 18, 1999 at 12:24:16PM -0400, Brian Fundakowski Feldman wrote:
> > Hello, I'm Brian Feldman, a new committer to the FreeBSD source tree! Some
> > of
> > the things I'll be working on are:
> > - mai
I also want new-IPFW to be modular. This would mean that, for instance,
DUMMYNET would be just one plug-in to IPFW. More would be created in an
extensible manner, rather than the current hack to do DUMMYNET.
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
gr...@freebsd.org
On Fri, 18 Jun 1999, Nicolai Petri wrote:
> On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote:
> > On Fri, 18 Jun 1999, Ruslan Ermilov wrote:
> >
> > > Let's join our efforts in this area!
> > > IPFW code is very ugly...
> >
> > implementatio
How do you feel about (after getting it fixed in -CURRENT) helping with
converting ipfw(8) to just a front-end to ipf? I think it's worth discussing
whether it's actually worth it to rewrite IPFW or just work on improving
ipfilter. (discussion moved to -hackers)
Brian Fundakows
On Sat, 19 Jun 1999, Darren Reed wrote:
> In some email I received from Brian Fundakowski Feldman, sie wrote:
> > How do you feel about (after getting it fixed in -CURRENT) helping with
> > converting ipfw(8) to just a front-end to ipf? I think it's worth discussing
>
achieve the effect you want;
take a look at e.g. mprotect(), you should be able to do much the same
thing with kernel_map instead.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTE
t, or kqueue file descriptor) to wait
upon at any given time. Since kqueues are pollable, what happens is
that the kqueue along with every other fd being polled/selected are all
polled by a single poll(2) system call. Yes, your kqueue is being used,
but it has an indirection of another poll(2) system
On Wed, Feb 09, 2005 at 06:39:52PM +0300, Dmitry Agaphonov wrote:
> On Wed, 9 Feb 2005 09:49:24 -0500
> Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
>
> BFF> Since you're using user threads, not kernel threads, the kernel can only
> BFF> have one &
lling to make a port and help with all needed setup information -
> a 5-10 minutes job if someone has the time for it.
Have you tried valgrind in any of its modes yet?
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''&
On Sun, Feb 13, 2005 at 05:51:11PM +0200, Peter Pentchev wrote:
> On Sun, Feb 13, 2005 at 10:03:30AM -0500, Brian Fundakowski Feldman wrote:
> > On Thu, Feb 10, 2005 at 10:55:58PM +0200, Ion-Mihai Tetcu wrote:
> > > Hi,
> > >
> > >
> > > One of my
On Sun, Feb 13, 2005 at 06:47:52PM +0200, Ion-Mihai Tetcu wrote:
> On Sun, 13 Feb 2005 18:26:16 +0200
> Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote:
>
> > On Sun, 13 Feb 2005 10:03:30 -0500
> > Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
> >
> &g
7;t want to
trust the same code to both tasks, and possibly optimize more because
it can do that?
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''
with: --show-reachable=yes
>
> The amount of memory leaked seems constant regardless of how many
> times getaddrinfo() is called, so it's probably from reading
> resolv.conf.
It looks like the memory leaked scales with the number of times that
the mtime of the configura
ware .. FreeBSD-USB#2 -> Device
>
> The advantage would be then to possible use scripts to debug protocol in order
> to port drivers to freebsd.
>
>
> Ref: ftp://download.intel.com/design/chipsets/e7500/datashts/29073303.pdf
Wouldn't being able to do that violate t
tten upon power loss. Dealing with many in-order writes
being lost (in order), upon power loss, is something the filesystems
are already written to assume, and the fsync(2) semantics are designed
to work with.
--
Brian Fundakowski Feldman \'[ FreeBSD ]'
s about that?
>
> If no such a parser exists is there any practical reason why ?
Ethereal uses TLV...
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<>
ng
unique binary identifiers, for example, pids.
The VM map algorithms are the same as ever, though. They use linear
traversal along with a cached reference to the last lookup. There
are certainly some workloads that should benefit from this, s
r 5.x and
6.x both, then, too.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own.
rd fare, unless you're developing code as a kernel
module, and manage to keep out bugs that would cause instability during
the development process... that can definitely cut down development
time.
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''&
readdirsize; /* Size of a readdir rpc */
int nm_readahead; /* Num. of blocks to readahead */
+ int nm_wcommitsize; /* Max size of commit for write */
int nm_acdirmin;/* Directory attr cache min lifetime */
int nm_acdirma
On Fri, Apr 15, 2005 at 03:21:08PM +0200, Marc Olzheim wrote:
> On Fri, Apr 15, 2005 at 01:08:21AM -0400, Brian Fundakowski Feldman wrote:
> > I'll spare a lengthy write-up because I think the patch documents it well
> > enough. It certainly appears to fix things here w
test on your hard drives
and view their statistics and error logs. I don't know why it doesn't
currently do much on SCSI, but ports/sysutils/smartmontools works
great for ATA.
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''''
On Tue, Apr 19, 2005 at 03:32:27PM +0200, Marc Olzheim wrote:
> On Mon, Apr 18, 2005 at 10:33:21PM +0200, Marc Olzheim wrote:
> > On Mon, Apr 18, 2005 at 04:22:13PM -0400, Brian Fundakowski Feldman wrote:
> > > > > http://green.homeunix.org/~green/nfs_client.deadlock.patc
On Tue, Apr 19, 2005 at 06:09:00PM +0200, Marc Olzheim wrote:
> On Tue, Apr 19, 2005 at 06:02:58PM +0200, Marc Olzheim wrote:
> > On Tue, Apr 19, 2005 at 11:18:00AM -0400, Brian Fundakowski Feldman wrote:
> > > Does this work for you?
> >
> > ...
> >
> &g
On Tue, Apr 19, 2005 at 12:16:16PM -0400, Brian Fundakowski Feldman wrote:
> On Tue, Apr 19, 2005 at 06:09:00PM +0200, Marc Olzheim wrote:
> > On Tue, Apr 19, 2005 at 06:02:58PM +0200, Marc Olzheim wrote:
> > > On Tue, Apr 19, 2005 at 11:18:00AM -0400, Brian Fundakowski Feldman w
On Wed, Apr 20, 2005 at 04:04:09PM +0200, Marc Olzheim wrote:
> On Tue, Apr 19, 2005 at 04:47:23PM -0400, Brian Fundakowski Feldman wrote:
> > This compiles.
>
> It does and it seems to work. The NFS performance drops considerably
> though, from 8/9 MByte/s to 3/4 on se
On Wed, Apr 20, 2005 at 04:38:42PM +0200, Marc Olzheim wrote:
> On Wed, Apr 20, 2005 at 10:24:48AM -0400, Brian Fundakowski Feldman wrote:
> > > It does and it seems to work. The NFS performance drops considerably
> > > though, from 8/9 MByte/s to 3/4 on sequenti
On Wed, Apr 20, 2005 at 05:35:28PM +0200, Marc Olzheim wrote:
> On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundakowski Feldman wrote:
> > Reads should be totally unaffected...
>
> The server was misbehaving. Fixed. :-)
>
> > > Btw.: I'm not sure write(),writ
On Wed, Apr 20, 2005 at 07:12:20PM +0200, Jilles Tjoelker wrote:
> On Wed, Apr 20, 2005 at 11:52:33AM -0400, Brian Fundakowski Feldman wrote:
> > On Wed, Apr 20, 2005 at 05:35:28PM +0200, Marc Olzheim wrote:
> > > On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundako
fs_bio.c::nfs_write()? IO_UNIT is
set for all write calls which means "atomic", and nfs_rslock() and
O_APPEND appear to at least attempt this. Please take a detailed look
at the current system and the changes... it's far less clear-cut than
POLA dictates.
--
Brian Fundako
it's acceptable to interleave multiple
writers that are doing O_APPEND? At best, to do what you're asking,
they could be kept from being interleaved from the context of one
specific NFS client host...
--
Brian Fundakowski Feldman \'[ FreeBSD ]''&#
uld be kept from being interleaved from the context of one
> > specific NFS client host...
>
> As far as POSIX goes, the standard says that applications are expected
> to handle serialization. It makes no exception for O_APPEND.
Then let's fix IO_UNI
ing much
like:
db> show disk/ad0s1b
struct cdev *=0xc2f0
db> w dumpdev
In this case, you would presumably be able to do this by booting into
DDB early and setting "break execve" to stop right before init is
executed. Of course, this method wouldn't be partic
gt;If you want do to it the hard way: clri(8)
> >
> >:-)
> >
>
> Thanks! I'll use clri for this. It would still be a nice
> feature in rm, after all, i dont think it's that hard to
> make.
Way overkill. find . -mindepth 1 -maxdepth 1 -inum
--
Brian Fund
SD ad0s1e 268435456 512 i 4 o 1610612736 ty 7
2 BSD ad0s1d 268435456 512 i 3 o 1342177280 ty 7
2 BSD ad0s1c 164694749184 512 i 2 o 0 ty 0
2 BSD ad0s1b 1073741824 512 i 1 o 0 ty 1
2 BSD ad0s1a 268435456 512 i 0 o 1073741824 ty 7
--
Brian Fundakowski Feldman \'[ FreeBSD
y
truthful about the fact that it doesn't sleep at all -- it calls those
routines which can. They can both be documented to require no locks
to be held when being called, except for M_NOWAIT specifically in the
one-page-or-less allocation case.
--
Brian Fundakowski Feldman
On Fri, May 20, 2005 at 10:39:12AM -0600, Scott Long wrote:
> Brian Fundakowski Feldman wrote:
>
> >On Fri, May 20, 2005 at 01:40:35PM +0200, Hans Petter Selasky wrote:
> >
> >>Hi,
> >>
> >>I just hit some problems with the new "contigmalloc()&qu
e is largely not productionable
on FreeBSD thanks to a locking versus IPL model being used in the
kernel versus the if_bridge(4) code having been structured for IPL.
I very much like this far more featureful and cleaner bridging
implementation; it would benefit from implementing a locking strateg
On Wed, Jun 01, 2005 at 11:58:49AM +1200, Andrew Thompson wrote:
> On Tue, May 31, 2005 at 07:48:16PM -0400, Brian Fundakowski Feldman wrote:
> > On Tue, May 31, 2005 at 11:25:54AM +1200, Andrew Thompson wrote:
> > > Hi,
> > >
> > > I am looking for tester
is happening
> inside the kernel when NMI is delivered .
>
> Please provide me some inputs.
Look for "NMI" references in src/sys/i386/i386/trap.c.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''
as a superset of xterm (see the tc=
directive). I have a lot of X resources defined, and here is one that
could help you guys:
XTerm*termName: xterm-color
Happy to help :)
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--
ntage here is that it's wired memory and can't get swapped
out like mount_mfs can.
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
a seperate code base)?
This avoids certain MFS problems, yes. Please see vnconfig(8) =)
> -MB
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTE
rary standard.
>
> try this link :
>
> http://www.opengroup.org/onlinepubs/7908799/
Thanks, but manpages only go so far...
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send m
re doing things with threads, you'd be using the
pthread_mutex_t routines, of course ;)
> In lock_create the lock is aligned to CACHE_LINE_SIZE. Why is that
> important?
I'm thinking it's to keep things in one line of the data cache so as
to not impact performance more than necessar
/* socket used for communications */
+ int connected; /* is the socket connected */
+ int vc; /* is the socket a virtual circuit? */
+ int af; /* address family of socket */
+
or it's hard to guess what might be "wrong".
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
&
to enable it.
For anyone that normally runs into failed allocations hot-plugging
hardware, please try this and see if it helps out.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED
. How to do
> that ?
Take a look at src/sys/compat/linprocfs; I think it has everything you
are looking for.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''
On Tue, Jun 15, 2004 at 03:57:09PM -0400, Brian Fundakowski Feldman wrote:
> The patch, which applies to 5-CURRENT, can be found here:
> <http://green.homeunix.org/~green/contigmalloc2.patch>
> The default is to use the old contigmalloc(). You can set the
> sysctl
On Fri, Jun 18, 2004 at 04:21:27PM -0500, Alan Cox wrote:
> On Fri, Jun 18, 2004 at 04:51:15PM -0400, Brian Fundakowski Feldman wrote:
> > On Tue, Jun 15, 2004 at 03:57:09PM -0400, Brian Fundakowski Feldman wrote:
> > > The patch, which applies to 5-CURRENT, can be found h
.c:1010
> #27 0xc061b21d in Xint0x80_syscall () at {standard input}:136
What queue is the buffer on that the system is panicking? (What was
the panic message, or alternately, "p *bp" from the bundirty or brelse
frame in gdb leading up to the panic.
--
Brian Fundakowski Feld
vfrom all over the place.
>
>
> it is actually pretty simple. man pcap. this is a wrapper around bpf
> which lets you do it in a couple lines of C code.
Just change the sendto/recvfrom calls to write/read. It's not a lot of
work, the xsuppli
gher
level in your application. BSD and System V IPC mechanisms already are
very good building blocks here for system-scoped locks.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
nefit much from being implemented
in the kernel unless they conform to a portable API. I certainly always
have my own various kernel modifications that I find useful, but aren't
very standard :)
--
at some
point.
I've been running something like this one for some time on -CURRENT with
zero problems (may be a bit stale, especially if not removing the VM
parts): <http://green.homeunix.org/~green/kqueue%2bvm.patch>
--
Brian Fundakowski Feldman \'[ FreeBS
SB drivers in FreeBSD, and if it can be done with ugen(4)/libusb, you'll
safe yourself a lot of time and pain.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAI
suspect it to be an alignment problem, it's easy to test. Look for
the bus_dma_tag_create() calls -- all of them use PAGE_SIZE (4096+) or
ETHER_ALIGN (2). Did you try changing the ETHER_ALIGNS to 8?
--
Brian Fundakowski Feldman \'[ FreeBSD ]&#x
ds a lot like "Well, there's no point in doing something better
> since nobody else is doing it.". strlcpy() and friends are an example of
> non-standard stuff that just Makes Sense(tm).
If you're trying to create a new "standard", I think -standards o
of TRUE.
Comments?
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own. \,
On Fri, Jul 16, 2004 at 08:32:05PM -0400, Brian Fundakowski Feldman wrote:
> Anyone VM-y enough to be up to the task: please take a look at this
> current vm_contig.c code and the crash that I have.
>
> This crash is not common -- this is the first time I've seen it --
> but t
hing to a maintainer that indent has.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own.
shes so far.
Andreas, are you using the nvidia driver too?
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are
; similar behaviour with other ports that try to use glib's threading
> functions.
>
> I CC-ed glib20 port-maintainer ([EMAIL PROTECTED]) in the hope this
> (or appropriate alternative) fix makes it in time for 5.3-RELEASE.
FWIW, I had to fix a similar problem in mozilla/NS
> limited. For example 'lsusb' in linux can show much more info. What do you
> > think about that too?
> >
> >
> > Thanks in advance for any info and/or flames :)
>
> I seem to recall a problem with ugen that it doesn't discove
'csh' (ie, the last from CSRG)??
> THERE IS NO STANDARD 'csh'. POSIX doesn't even try to standardize it.
>
> 'csh' is an interactive shell, not a programming language. Anyone trying
> to write "portable" scripts in 'csh' should kno
ries. Some stuff sometimes pops up in lost+found. Some
> stuff can vanish (not 100% positive on that). But most worringly, is
> that some files come back corrupted (ie berkley db files that db won't
> read).
Long strings of NUL bytes? Missing data? Spam (from the same file,
or from
it would be a GEOM module, though.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own.
, z->zalloc);
+ item = (void *)kmem_alloc(kernel_map, nbytes);
+ if (item != NULL) {
+ atomic_add_int(&zone_kern_pages, z->zalloc);
} else {
- item = (void *) kmem_alloc(kernel
I keep getting these panics on my SMP box (no backtrace or DDB or crash
dump of course, because panic() == hang to FreeBSD these days):
panic: receive: m == 0 so->so_rcv.sb_cc == 52
>From what I can tell, all sorts of socket-related calls are "MP-safe"
and yet never even come close to locking the s
hould be a "bus" where pccard, usb,
and SCSI cards would go (instead of "storage"). Currently, we
don't have way too many modules, so I'm happy with what's here now.
I definitely think there's room for improvement in how /modules
is organized, but remember that the fo
;[EMAIL PROTECTED]>
> |A closed mouth gathers no feet.
> `--
>
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
f argument
for nasm instead.
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
5-100%, it's considerably easier.)
>
The _REALLY_ obvious solution to this is to find the real path on exec()
and store the pointer in proc. How is this full of "overhead" and
"impractical"?
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[E
what you really want are the semantics of a
symbolic link and not the semantics of a hard link. Is it just me,
or does it seem as if the pathname of the executable being stored as
a virtual symlink in procfs as "file" would solve these security
problems?
--
Brian Fun
.
As you can see, the second time it worked. CVSup also seems to do this on
the same symmbol every time it happens, so when that occurs I'll make sure
to report it.
Thanks John, and anyone else who may have an idea what's going on.
--
Brian Fundakowski Feldman \ Free
re not using fseek() like your should be using
for FILE * IO. Don't mix FILE *fp and int fd operations callously.
>
> By the way, I also find out if you copy a file with holes into another
> file, the holes in the first file will be replaced with 0s in the second
> file, taking
___
> Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTE
They weren't. They were made in the development
branch, HEAD, 4.0.
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
o PIO mode
Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done
(rc continues here)
So ad1 runs in PIO, and mount may or may not have successfully gotten
ad1 mount entries up.
>
> What am I missing?
>
Something possibly close to what I am :/ That 71626 seems strange.
n
is, why aren't you using X11?
>
> I peeked at the source and there are various syscons related ioctl() calls.
> Any reason that /dev/io and /dev/mem wasn't used instead?
That's simple. We're not trying to move to making things MORE platform-
specific.
>
> Than
rth Planet. Sci, Nagoya Univ. |The power to serve! |
> Nagoya, 464-8602, Japan| http://www.FreeBSD.org/ |
> |http://www.jp.FreeBSD.org/|
> FreeBSD(98) 3.3R-Rev. 01 available! +==+
--
Brian Fundakowski Feld
d `135ds15'.
>
> Those are the SCO Unix/Xenix compatable names. SCO (and SYSV/386) uses those
> instead of "fdN.1440" etc.
>
> 48 = 48 tracks per inch = 5.25" disk,
> 96 = 96 tracks per inch = 5.25" disk,
> 135 = 135 tracks per inch = 3.5"
now review, (fix WRT mono) and commit these diffs? It's very
important to be done. I originally got these diffs from W. Gerald Hicks.
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
reeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat
> Feb 19 09:56:01 CET 2000
> [EMAIL PROTECTED]:/usr/src/sys/compile/cichlids i386
> -r-xr-xr-x 1 root wheel 143360 10 Feb 22:58 /boot/loader*
>
> Alex
>
> --
> I need a new ~/.sig.
>
>
> To Unsub
inglen
pushl stringaddr
pushl $0x1
call write
which would result in %eax containing the return value.
For what it's worth, you can find all of the syscall calling conventions
in src/lib/libc, and you can find where the calling conventions are
"defined" by looking at src/sys/i386/i
rg/~green/read_cd.tar.gz
MD5 (read_cd.tar.gz) = 7881ea5ef1428ced7533b1cb2a3afbb1
> Thanks for any reply
HTH
> RP
> [EMAIL PROTECTED]
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe
27;ll
give it a check and post it.
> ---
> Daniel O'Connor software and network engineer
> for Genesis Software - http://www.gsoft.com.au
> "The nice thing about standards is that there
> are so many of them to choose from."
> -- Andrew Tanenbaum
t no data was received or acknowledged. According to jlemon,
whose diagnosis makes sense, the problem is that for whatever reason
the kernel is not returning to user mode. That explains why sshd
doesn't work, telnetd doesn't work, XFree86 and apps don't respond.
The question
s as much as I do; I'll just convince him
to keep running the latest -CURRENT and get the serial console working.
> thanks,
> --
> -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
> "I have the heart of a child; I keep it in a
1 - 100 of 115 matches
Mail list logo
