On Sun, 17 Sep 2000 00:48:27 EST, "Peter Avalos" wrote:
> I don't know who to contact about this, so I'm hoping some people subscribed
> to this list have commit access. I found some spelling errors in passwd(1)
> manpage. I have RELENG_4 installed. Here's the output of diff -u:
Thanks. Your
}In message <[EMAIL PROTECTED]>you write:
}}Danny Braniss ([EMAIL PROTECTED]) wrote:
}}> BTW, is someone working in passing all this stuff via dhcp? im trying to co
}m
}}e}}> up with an almost zero admin diskless ws solution.
}}
}}Yes, this has been done in current for a while and was back ported
On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
> I recently ran into revelant problem with /dev/stdout, while
> working on some software under linux that expected /dev/stdout as an
> argument instead of using stdout.
>
> Using the device file breaks, if the process is suid to a non
>
> if by -stable you mean whatever i get when i do a 'cvs co
> -rRELENG_4' src/sys
> then there are some things missing.
> i386/i386/autoconf.c does not have the stuff for pxe.
> if i compile a kernel with the BOOTP_ stuff, then i can mount
> nfsroot, but
> [mount_]mfs is broken, i get '
Hello, I don't wish to jump all the way forward to -CURRENT, but would
like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0
for kqueue() and fxp PEX support).
I would like to do this via cvsup and `make world'.
My understanding is that `make world' is just buildworld followed
by i
Marc Tardif wrote:
>
> What is the FreeBSD naming convention for devices of disk slices and
> labels? Considering my system is installed on the first partition of
> /dev/wd0 (non-dedicated), these are the block-device interfaces I
> have to my disk:
>
> wd0 wd0cwd0fwd0s1 wd0s1c
Danny Braniss ([EMAIL PROTECTED]) wrote:
> if by -stable you mean whatever i get when i do a 'cvs co -rRELENG_4' src/sys
> then there are some things missing.
> i386/i386/autoconf.c does not have the stuff for pxe.
> if i compile a kernel with the BOOTP_ stuff, then i can mount nfsroot, but
Marc Tardif wrote:
>
> If I understand correctly, wd0[a-h] will be the same as wd0s3[a-h] in a
> situation where DOS is on first slice, Linux on second and FreeBSD on
> third, right? But what if the fourth slice is also FreeBSD? In such a
Right.
> case, I'll assume you meant "booted slice" inst
Hi all,
CCd to freebsd-bugs (I think it exists, doesn't it?!)
In every FreeBSD Snapshot I tested (2214, 2521, 2905) I always
got problems regarding Natd. I have a very simple /etc/rc.firewall:
/sbin/ipfw -f flush
/sbin/ipfw add divert natd all from any to any via isp0
/sbin/ipfw add
Hello:
I'm resending this mail here as nobody in -questions seems to
have a clue about what is going on.
Any ideas? Thanks for your time.
- Forwarded message from Fernando Schapachnik -
Subject: Weird locking issue with makemap, sendmail on a 4.1-R SMP.
To: [EMAIL PROTECT
On Mon, 18 Sep 2000, Christopher Stein wrote:
>
> Hello, I don't wish to jump all the way forward to -CURRENT, but would
> like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0
> for kqueue() and fxp PEX support).
>
> How do I specify 4.1 in the release field of my supfile?
>
If
On Mon, 18 Sep 2000, Christopher Stein wrote:
> I would like to do this via cvsup and `make world'.
> My understanding is that `make world' is just buildworld followed
> by installworld, each a single monolithic step. Hhmm.. it seems
> to me that some build stages will not work without
> some oth
On Tue 2000-09-19 (00:54), Daniel C. Sobral wrote:
> > Lastly, where else could I have found this information other
> > than asking on the FreeBSD mailing list?
>
> Beats me, but it _should_ be in the handbook.
A basic device naming overview, as well as some simple disk layout
information, is av
A friend asks me what will happen if more than one process trying to read
the stdin at the same time. There is no way to guarantee that any
particular keyboard input will be accepted by a particular process.
Since a system call is atomic, this makes me wonder how long it takes to
do a system cal
[ snip ]
> > Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1
> > doesn't span to the end of disk:
> > 4. If I want to use /dev/wd0s2 as a raw slice for reading
> >and writing, what are the steps to follow?
>
> None. You just use it.
>
This is what I have in fdisk (from /stand/sysins
In message <[EMAIL PROTECTED]> Takanori
Watanabe writes:
: I ported kernel part of PEACE from NetBSD.(That is in sys/compat/pecoff/*).
Cool. Way Cool.
: - It requires following changes to sys/imgact.h and kern/kern_exec.c to
: be able to change size of memory area to hold dynamic linker argum
Every message I see in the archives on these points is very simple:
"See /usr/src/UPDATING"
Unfortunately, my system has no /usr/src/UPDATING.
I have decided to go with a full net reinstall (rather than use cvsup) to
take me from 3.3 to 4.1.
I look forward to reading UPDATING when it lands on
I am experiencing problems with ptrace() under FreeBSD. I made a simple
example program to demonstrate. All it does is fork a child process to
execl() a simple "hello world" program and ptrace() it with PT_CONTINUE.
The first time around, everything is as it should be - the program is
executed
On Mon 2000-09-18 (14:42), Marc Tardif wrote:
> > > 4b. Should I then be using /dev/rwd0s2 or /dev/rwd0s2a
> > > for reading and writing (of course, this is assuming
> > > block i/o of multiples of 512 bytes)?
> >
> > Nope, using raw devices is almost always wrong, and we even got rid of
Marc Tardif wrote:
>
> This is what I have in fdisk (from /stand/sysinstall):
> Offset SizeEnd Name PType Desc Subtype Flags
> 0 63 62- 6 unused0
> 6319375651937627wd0s1 3freebsd 165 C
> 1
> > Is it possible to stop any PnP operation (checking, seting) during
> > boot?
> >
>
> Can I ask specifically what problems you're having or what you are
> trying to accomplish?
I want install 4.1 RELEASE on my old 486's, with ISA bus only and
without bios PnP support.
First has SMC EliteU
Mike Smith wrote:
>
> > ok, once i compiled a kernel with options BOOTP things got better ;-)
> > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
> > but after it re-configures the ethernet, the ethernet stops working!
> >
> > ponters anyone?
>
> You can't run dhclient (
On Tue, 19 Sep 2000, Bruce Evans wrote:
> On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
>
> > I recently ran into revelant problem with /dev/stdout, while
> > working on some software under linux that expected /dev/stdout as an
> > argument instead of using stdout.
> >
> > Using the
In message <[EMAIL PROTECTED]>you write:
}Mike Smith wrote:
}>
}> > ok, once i compiled a kernel with options BOOTP things got better ;-)
}> > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs)
}> > but after it re-configures the ethernet, the ethernet stops working!
}> >
}>
> > This is what I have in fdisk (from /stand/sysinstall):
> > Offset SizeEnd Name PType Desc Subtype Flags
> > 0 63 62- 6 unused0
> > 6319375651937627wd0s1 3freebsd 165 C
> > 1937628 1
Takanori Watanabe <[EMAIL PROTECTED]> writes:
> PEACE is Win32 API Compatible environment for (Originally) NetBSD.
> It consist of three parts:
> Kernel part to load PE format executable onto process memory space.
> Dynamic Linker to link with PE format DLL.
> Libraries to translate Win32 API cal
In article <[EMAIL PROTECTED]>,
Max Khon <[EMAIL PROTECTED]> wrote:
> hi, there!
>
> On Fri, 15 Sep 2000, John Polstra wrote:
>
> > Here is another possibility: we could call _thread_init() from
> > crt1.o. The patch (untested) is below. It calls _thread_init() if
> > and only if that symbol
Dag-Erling Smorgrav wrote:
> Takanori Watanabe <[EMAIL PROTECTED]> writes:
> > PEACE is Win32 API Compatible environment for (Originally) NetBSD.
> > It consist of three parts:
> > Kernel part to load PE format executable onto process memory space.
> > Dynamic Linker to link with PE format DLL.
>
Marc Tardif writes:
> > > This is what I have in fdisk (from /stand/sysinstall):
> > > Offset SizeEnd Name PType Desc Subtype Flags
> > > 0 63 62- 6 unused0
> > > 6319375651937627wd0s1 3freebsd
On Mon, 18 Sep 2000, Christopher Stein wrote:
> Every message I see in the archives on these points is very simple:
>
> "See /usr/src/UPDATING"
>
> Unfortunately, my system has no /usr/src/UPDATING.
Reread what I said:
> See the /usr/src/UPDATING file after updating your source and be sure to
Brian Somers <[EMAIL PROTECTED]> wrote:
> > First, the things I am definitely going to do. Christian "naddy"
> > Weisgerber has taken on the task of porting mm to openbsd.
>
> I think it would be nice to aim to keep the two scripts exactly the
> same, using `uname` when it's really necessar
On Mon, 18 Sep 2000, Piotr Sroczynski wrote:
> First has SMC EliteULTRA 8416 software selectable PnP operation
> - ethernet
The 'ed' driver doesn't support SMC cards in PnP mode. (Or rather it
doesn't support SMC cards in non shared memory mode which is what they run
in when configured via PnP.
On 18-Sep-00 Marc Tardif wrote:
>> > This is what I have in fdisk (from /stand/sysinstall):
>> > Offset SizeEnd Name PType Desc Subtype Flags
>> > 0 63 62- 6 unused0
>> > 6319375651937627wd0s1 3fre
On Mon, Sep 18, 2000 at 02:45:06PM -0400, Christopher Stein wrote:
> On Mon, 18 Sep 2000, Kris Kennaway wrote:
> > See the /usr/src/UPDATING file after updating your source and be sure to
> > follow the directions precisely.
>
> Every message I see in the archives on these points is very sim
Hi,
as part of my thesis research, I'm implementing something similar to the
POSIX idle-time CPU scheduler for other resource types, one being network
I/O. The basic idea is to substitute two-level queues for the standard
ones. I'm seeing some unexpected things (explained below), but let me first
In message <[EMAIL PROTECTED]>
Christopher Stein writes:
: Unfortunately, my system has no /usr/src/UPDATING.
Then you need to get newer sources. /usr/src here is the conventional
code for "the path to where you keep your sources."
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
Daniel C. Sobral writes:
> Marc Tardif wrote:
> > > > 4. If I want to use /dev/wd0s2 as a raw slice for reading
> > > >and writing, what are the steps to follow?
> > > You can't write several blocks near /dev/wd0s2 beginning.
> > > Use /dev/wd0 with proper address
> > >
> > That is rather risk
In message <[EMAIL PROTECTED]>, Steve Kargl wrote:
>Dag-Erling Smorgrav wrote:
>> Takanori Watanabe <[EMAIL PROTECTED]> writes:
>> > PEACE is Win32 API Compatible environment for (Originally) NetBSD.
>> > It consist of three parts:
>> > Kernel part to load PE format executable onto process memory
hi,
i am implementing a pseudo-devicer, many instaces of
this device may be
active, all have to share a resource. all instances
have to synchronize
their access to the resource. trying to implement
this, i ended up with a
less powerful version of semaphores. since the
resultant code became
littl
> 0cicuta/home/babolo(9)#dd of=/dev/wd0s2 if=/dev/zero bs=660b
> 1cicuta/home/babolo(11)#od -b /dev/wd0s2
[ snip ]
> Why I use 2.2.7 for test?
> Because of my lovely 4.1-STABLE is extremly unstable with content of
> ad0s2 (wd0s2) above and silently reboot after the first dd in the test above.
>
A
On 19-Sep-00 Mohan Krishna P wrote:
> hi,
>
> i am implementing a pseudo-devicer, many instaces of
> this device may be
> active, all have to share a resource. all instances
> have to synchronize
> their access to the resource. trying to implement
> this, i ended up with a
> less powerful versi
Hi,
i believe there are two things here that you need to consider before
you can see any queue build up in ipq:
1. you should generate packets (way) faster than the card is able
to handle them;
2. the network card itself might be able to queue multiple packets in
the "transmit ring";
42 matches
Mail list logo
