On Sat, Jul 21, 2001 at 07:17:47PM -0700, Arun Sharma wrote:
> Greetings. I'm trying to port an application to FreeBSD. I have
> a signal handler registered using signal(2). It modifies the
> data pointed to by the third argument - of type sigcontext (specifically
> sc_eip) - so that the execution
Greetings. I'm trying to port an application to FreeBSD. I have
a signal handler registered using signal(2). It modifies the
data pointed to by the third argument - of type sigcontext (specifically
sc_eip) - so that the execution would resume at a different point).
However, when execution resumes
At 9:06 PM -0700 7/20/01, David O'Brien wrote:
>The way to do this, is first install -stable.
>[...]
>
>Now install -current in the normal way.
>[...]
>
>You might be able to optimize the number of times booting from
>CDROM to change the partition type of ad0s1.
It occurs to me that it is actuall
In article <[EMAIL PROTECTED]>,
David O'Brien <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote:
> > I'm probably completely dim today so please bear with me :/
> > Thing is I want to setup a dual-boot box, running -stable & -current.
> > This box, a P2/266
On Thu, Jul 19, 2001 at 02:38:07PM -0400, Michael Sinz wrote:
> I had been meaning to ask if there was a reason why NFS mounts happened
> before NFS servers were started but life kept getting in the way :-)
If /usr was nfs mounted on a machine, then /usr needs to be mounted before
nfsd was loade
:
:In message <[EMAIL PROTECTED]>, Terry Lambert writes:
:>> FWIW, I vote that we rever to the traditional default and require
:>> -R1 or -b to avoid boot time hangs. The standard behaviour for most
:>> NFS implementations that I'm aware of would do this.
:>
:>I agree; people at work have bitched
On Sat, Jul 21, 2001 at 06:54:54PM +0200, Wilko Bulte wrote:
> This indeed fixed it. I always though Unix^WFreeBSD was supposed to allow
> you to shoot yourself in the foot. sysinstall obviously decided it needed
> to outsmart me.
Not so much out smart you, but the code that maps da0a to da0sXa i
On Fri, Jul 20, 2001 at 09:27:26PM -0700, David O'Brien wrote:
> On Thu, Jul 19, 2001 at 05:29:10PM -0400, Garance A Drosihn wrote:
> > Anyway, the above is a long-winded justification for the following
> > suggestions:
> > 1) if disklabel has already been told about '/', then it
> >
On Fri, Jul 20, 2001 at 09:06:09PM -0700, David O'Brien wrote:
> On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote:
> > I'm probably completely dim today so please bear with me :/
> > Thing is I want to setup a dual-boot box, running -stable & -current.
> > This box, a P2/266 has a 30G
Garance A Drosihn wrote:
>
[SNIP]
>
> How did you do those two installs though? David is not saying that
I don't remember very well : it may well have been done via cloning an
existing slice via dump/restore (thus no sysinstall troubles ...)
[SNIP]
>
> Where you have trouble is if you have t
In message <[EMAIL PROTECTED]>, Brian Dean writes:
>On Sat, Jul 21, 2001 at 02:47:29PM +0100, Ian Dowse wrote:
>
>> Below is a patch that makes fdisk request user confirmation before
>> making any changes to the start and end of partitions.
>
>Please allow this behaviour to be overridden by a flag
On Sat, Jul 21, 2001 at 02:47:29PM +0100, Ian Dowse wrote:
> Below is a patch that makes fdisk request user confirmation before
> making any changes to the start and end of partitions.
Please allow this behaviour to be overridden by a flag that can
specified so that scripts don't suddenly stop a
For about a year, fdisk(8) has had code that automatically adjusts
partitions to begin on a head boundary and end on a cylinder
boundary. This is fine in most situations, but the way it is
implemented makes it awkward to override, and more importantly it
is way too easy to mess up an existing par
Sat, Jul 21, 2001 at 15:07:00, lucky (Alexey Privalov) wrote about "strange with
named":
> Jul 21 13:43:17 host named[124]: denied update from [196.127.211.51].1475 for
>"host.domain"
> Jul 21 13:48:17 host named[124]: denied update from [196.127.211.51].1486 for
>"host.domain"
> Jul 21 13:5
Alexey Privalov wrote:
>
> hi all.
> i have FreeBSD 4.3-STABLE and named 8.2.3-REL.
> everyday i see following strings in my log:
>
> Jul 21 13:43:17 host named[124]: denied update from [196.127.211.51].1475 for
>"host.domain"
> Jul 21 13:48:17 host named[124]: denied update from [196.127.211.5
in kernel,
when I have
(struct tty*)cur_tty pointer
how can I know if the cur_tty is a console (ttyv) ?
or X windows ?
I'm writing a wheel support for console, but it creates problem with the X
windows.
thanks,
Amir.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
hi all.
i have FreeBSD 4.3-STABLE and named 8.2.3-REL.
everyday i see following strings in my log:
Jul 21 13:43:17 host named[124]: denied update from [196.127.211.51].1475 for
"host.domain"
Jul 21 13:48:17 host named[124]: denied update from [196.127.211.51].1486 for
"host.domain"
Jul 21 13:
David O'Brien wrote:
> On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote:
> > I'm probably completely dim today so please bear with me :/
> > Thing is I want to setup a dual-boot box, running -stable & -current.
> > This box, a P2/266 has a 30G IDE disk.
> >
> > What I did is create
> >
Ian Dowse wrote:
>
> In message <[EMAIL PROTECTED]>, Terry Lambert writes:
> >> FWIW, I vote that we rever to the traditional default and require
> >> -R1 or -b to avoid boot time hangs. The standard behaviour for most
> >> NFS implementations that I'm aware of would do this.
> >
> >I agree; peop
19 matches
Mail list logo
