On Thu, Jul 17, 2003 at 01:01:11PM -0400, Robert Watson wrote:
+> Most system functionality that relied on procfs has been rewritten to rely
+> on other mechanisms. In general, I advise against running procfs--it's
+> interesting, but conceptually it's very risky. If you look at the history
+> of
Pawel Jakub Dawidek wrote:
> +> trussRelies on the event model of procfs; there have been some
> +> initial patches and discussion of migrating truss to ptrace() but
> +> I don't think we have anything very usable yet. I'd be happy to
> +> be
(Cc'ed to phk@ as to main GEOM and DEVFS developer; see corresponding
questions below.)
Hi,
I need to downgrade a remote FreeBSD system from 5.1-release to 4.8-release
remotely without any local help (except possible hitting Reset).
Don't ask why the collocation provider is too ugly and too far f
Hi,
Valentin Nechayev wrote on Fri, Jul 18, 2003 at 12:12:48PM +0300:
[..]
> I need to downgrade a remote FreeBSD system from 5.1-release to 4.8-release
> remotely without any local help (except possible hitting Reset).
> Don't ask why the collocation provider is too ugly and too far from me; it's
On Fri, Jul 18, 2003 at 12:12:48PM +0300, Valentin Nechayev typed:
>
> 8. Disable all processes except sshd and run the following (saying generally):
>
>for D in /bin /sbin /etc /boot /usr/bin /usr/sbin /usr/lib /usr/libexec \
> /usr/libdata /usr/share /usr/local /var/db
>do
>
In message <[EMAIL PROTECTED]>, Valentin Nechayev writes:
>(Cc'ed to phk@ as to main GEOM and DEVFS developer; see corresponding
>questions below.)
I'm on vacation right now, and sort of semi offline (you know, the
undocumented ACPI S-1 "wife mandated offline state" :-)
In addition to what you al
On Fri, Jul 18, 2003 at 12:12:48PM +0300, Valentin Nechayev wrote:
This is really hard task...
+>for D in /bin /sbin /etc /boot /usr/bin /usr/sbin /usr/lib /usr/libexec \
+> /usr/libdata /usr/share /usr/local /var/db
+>do
+>mv ${D} ${D}5
+>mv ${D}4 {D}
+>do
Given that uma_zalloc() has the same flags as malloc(9) shouldn't it check
these flags like malloc(9) does? I would think we could copy the #ifdef
INVARIANTS section at the beginning of malloc(9) to uma_zalloc_arg().
I just found a large number of calls in the ATM code that have just
M_ZERO or ev
In message <[EMAIL PROTECTED]>, Harti Brandt write
s:
>
>Given that uma_zalloc() has the same flags as malloc(9) shouldn't it check
>these flags like malloc(9) does? I would think we could copy the #ifdef
>INVARIANTS section at the beginning of malloc(9) to uma_zalloc_arg().
>
>I just found a large
Fri, Jul 18, 2003 at 12:44:33, nick wrote about "Re: complicated downgrade":
> +>do
> +>mv ${D} ${D}5
> +>mv ${D}4 {D}
> +>done
> Here is a race:)
> # mv /bin /bin5
> # mv /bin4 /bin
> mv: Command not found.
PATH=/bin4:/bin:/bin5/...
I used the same
hi, there!
On Wednesday 09 July 2003 00:30, Dan Nelson wrote:
DN> > pos = telldir(dirp);
DN> > ent = readdir(dirp);
DN> > seekdir(dirp, pos);
DN> > printf("First telldir:%d\nSecond telldir:%d\n", pos, telldir(dirp));
DN> I don't think there's any pstandard that says that telldir h
- Julian Elischer's Original Message -
> It is teh nextthing to look at..
> The ptrace interface doesn't extend to coverthreads at all.
> We willneed to design somewhole new system..
> One posibility is the benedict arnold thread(*), that
> talks with the debugger and controlls teh other th
John wrote:
- Julian Elischer's Original Message -
It is teh nextthing to look at..
The ptrace interface doesn't extend to coverthreads at all.
We willneed to design somewhole new system..
One posibility is the benedict arnold thread(*), that
talks with the debugger and controlls teh ot
Hi,
I updated a system of us for testing the the compiler and I run into
following problem:
cc -c -O -pipe -march=pentium4 -Wall \
-Wredundant-decls -Wnested-externs -Wstrict-prototypes \
-Wmissing-prototypes -Wpointer-arith -Winline \
-Wcast-qual-fformat-extensions -std=c99 -nostdi
On Fri, 18 Jul 2003, Valentin Nechayev wrote:
> (Cc'ed to phk@ as to main GEOM and DEVFS developer; see corresponding
> questions below.)
>
> Hi,
>
> I need to downgrade a remote FreeBSD system from 5.1-release to 4.8-release
> remotely without any local help (except possible hitting Reset).
> Don
Hi All,
I began to import some code from Darwin msdosfs. Here
is my first patch about the dirty flag. I patched the
msdosfs kernel module and fsck_msdos to enable the
flag. Can someone test it and checked in? Must I
submit a PR?
>From my own option, the new features of Darwin's
msdosfs are dirty
Hi all,
as far as I know new stuff should be first committed to -current and, if
it turns out stable enough, MFCed to -stable. I would like to commit a
driver to -stable that will not be in -current. The driver is for ProSum's
ProATM card. I have recently committed a full busdma driver to current
Hi all,
it seems there is a problem with the zone allocator in SMP systems.
I have a zone, that has an upper limit on items that resolves to an
upper limit of pages of 1. It turns out, that allocations from this
zone get stuck from time to time. It seems to me, that the following
happens:
- on
On Fri, Jul 18, 2003 at 07:05:58PM +0200, Harti Brandt wrote:
>
> Hi all,
>
> it seems there is a problem with the zone allocator in SMP systems.
>
> I have a zone, that has an upper limit on items that resolves to an
> upper limit of pages of 1. It turns out, that allocations from this
> zone
On Fri, Jul 18, 2003 at 06:19:46PM +0200, Harti Brandt wrote:
>
> Hi all,
>
> as far as I know new stuff should be first committed to -current and, if
> it turns out stable enough, MFCed to -stable. I would like to commit a
> driver to -stable that will not be in -current. The driver is for ProS
On Fri, Jul 18, 2003 at 01:45:34AM -0700, Terry Lambert wrote:
+> > +> trussRelies on the event model of procfs; there have been some
+> > +> initial patches and discussion of migrating truss to ptrace() but
+> > +> I don't think we have anything very usabl
In the last episode (Jul 18), Pawel Jakub Dawidek said:
> On Fri, Jul 18, 2003 at 01:45:34AM -0700, Terry Lambert wrote:
> +> > +> truss Relies on the event model of procfs; there have been
> +> > +>some initial patches and discussion of migrating truss
> +> > +>to ptrace() but I d
In the last episode (Jul 18), Alexey Neyman said:
> hi, there!
>
> On Wednesday 09 July 2003 00:30, Dan Nelson wrote:
> DN> > pos = telldir(dirp);
> DN> > ent = readdir(dirp);
> DN> > seekdir(dirp, pos);
> DN> > printf("First telldir:%d\nSecond telldir:%d\n", pos, telldir(dirp));
>
I asked this in -questions, but got no response; sorry for the repost.
I have a device driver that needs to make requests for data from a
userland daemon. What's the preferred method for doing this in 4.8R and
5.1R? I'm assuming the answer is Unix-domain sockets...
Thanks,
Marc.
--
Marc Rami
On 2003.07.18 13:28:27 +, Bosko Milekic wrote:
[CUT]
> wait for someone from the TRB (is there a list of who's part of this
> group somewhere, anyway?) and/or -core to respond before you take
There is a list with the TRB members at
http://www.freebsd.org/internal/staff.html .
--
Simon L
On 18-Jul-2003 Terry Lambert wrote:
> Pawel Jakub Dawidek wrote:
>> +> trussRelies on the event model of procfs; there have been some
>> +> initial patches and discussion of migrating truss to ptrace() but
>> +> I don't think we have anything very usable y
On Fri, 18 Jul 2003, Marc Ramirez wrote:
> I asked this in -questions, but got no response; sorry for the repost.
>
> I have a device driver that needs to make requests for data from a
> userland daemon. What's the preferred method for doing this in 4.8R and
> 5.1R? I'm assuming the answer is Un
On Fri, 18 Jul 2003, Daniel Eischen wrote:
> On Fri, 18 Jul 2003, Marc Ramirez wrote:
> > I asked this in -questions, but got no response; sorry for the repost.
> >
> > I have a device driver that needs to make requests for data from a
> > userland daemon. What's the preferred method for doing th
On Fri, 18 Jul 2003, Marc Ramirez wrote:
> On Fri, 18 Jul 2003, Daniel Eischen wrote:
>
> > On Fri, 18 Jul 2003, Marc Ramirez wrote:
> > > I asked this in -questions, but got no response; sorry for the repost.
> > >
> > > I have a device driver that needs to make requests for data from a
> > >
On Fri, 18 Jul 2003, Julian Elischer wrote:
>
>
> On Fri, 18 Jul 2003, Marc Ramirez wrote:
>
> > On Fri, 18 Jul 2003, Daniel Eischen wrote:
> >
> > > On Fri, 18 Jul 2003, Marc Ramirez wrote:
> > > > I asked this in -questions, but got no response; sorry for the repost.
> > > >
> > > > I have a dev
On Friday 18 July 2003 06:28, Bosko Milekic wrote:
> On Fri, Jul 18, 2003 at 06:19:46PM +0200, Harti Brandt wrote:
> > Hi all,
> >
> > as far as I know new stuff should be first committed to -current
> > and, if it turns out stable enough, MFCed to -stable. I would like
> > to commit a driver to -s
Dear scsi experts,
currently I'm discussing a problem I experience with
Thomas' atapicam(4) driver. To simplify discussions and
channel opinions and current discoveries, I've opened a PR
about the matter.
Please have a look at
kern/54616
and tell us your opinions.
Many thanks!
Daniel
--
IRC
I can not make my MTA work.
To: [EMAIL PROTECTED]
From: Jun Su <[EMAIL PROTECTED]>
Reply-To: Jun Su <[EMAIL PROTECTED]>
Cc:
X-send-pr-version: 3.113
X-GNATS-Notify:
>Submitter-Id: current-users
>Originator:Jun Su
>Organization: none
>Confidential: no
>
Valentin Nechayev wrote:
> I need to downgrade a remote FreeBSD system from 5.1-release to 4.8-release
> remotely without any local help (except possible hitting Reset).
> Don't ask why the collocation provider is too ugly and too far from me; it's
> given and unchangeable. This system never was 4.
Jun Su wrote:
> I began to import some code from Darwin msdosfs. Here
> is my first patch about the dirty flag. I patched the
> msdosfs kernel module and fsck_msdos to enable the
> flag. Can someone test it and checked in? Must I
> submit a PR?
>
> From my own option, the new features of Darwin's
Marc Ramirez wrote:
> I asked this in -questions, but got no response; sorry for the repost.
>
> I have a device driver that needs to make requests for data from a
> userland daemon. What's the preferred method for doing this in 4.8R and
> 5.1R? I'm assuming the answer is Unix-domain sockets...
John Baldwin wrote:
> Since ktrace logs all syscall entries and exits, it should seem that
> a kdump after the process had exited would show which syscall returned
> EAGAIN quite easily.
This works if the process exits after the EAGAIN; that would only
work for the specific error that people are s
37 matches
Mail list logo