Hi, Garrett.
No, that patch did not work.
because
+ tzsetup $${optC} -r; \
run current installed tzsetup which use libdialog.so
you must use just compiled one
/usr/obj/usr/src/usr.sbin/tzsetup/tzsetup
PS. I have 9-0Current 201101 upgrading to 9-0Beta2 20110925
I even try by hand setup ENV an
2011/9/26 Коньков Евгений :
> Hi
>
> For me patch do not working
>
> because tzsetup uses old tzsetup
>
> I use this:
>
>> --- share/zoneinfo/Makefile (revision 224989)
>> +++ share/zoneinfo/Makefile (working copy)
>> @@ -72,7 +72,8 @@
>> optC="-C ${DESTDIR}"
Hi
For me patch do not working
because tzsetup uses old tzsetup
I use this:
> --- share/zoneinfo/Makefile (revision 224989)
> +++ share/zoneinfo/Makefile (working copy)
> @@ -72,7 +72,8 @@
>optC="-C ${DESTDIR}"; \
>fi; \
>
On Fri, Sep 9, 2011 at 11:21 AM, Garrett Cooper wrote:
> On Fri, Sep 9, 2011 at 11:17 AM, Kevin Oberman wrote:
>> Last night I upgraded my laptop from 8-stable (Sept. 7) to head. I
>> almost worked, but I
>> did hit an issue during the installworld phase. The problem was when the
>> make in
>> /
On Fri, Sep 9, 2011 at 11:17 AM, Kevin Oberman wrote:
> Last night I upgraded my laptop from 8-stable (Sept. 7) to head. I
> almost worked, but I
> did hit an issue during the installworld phase. The problem was when the make
> in
> /usr/src/share/zoneinfo tried to run tzsetup that dialog failed
Last night I upgraded my laptop from 8-stable (Sept. 7) to head. I
almost worked, but I
did hit an issue during the installworld phase. The problem was when the make in
/usr/src/share/zoneinfo tried to run tzsetup that dialog failed to run
with the error:
/tmp/install.xtvA5ik4/libdialog.so.7: Undef
Hi,
I am interested in using the SCTP protocol implementation ( http://www.sctp.org )
on -CURRENT. Currently it works on -STABLE, and is integrated with the
current KAME snapshots ( http://www.kame.net ).
Has anyone ported networking code from -STABLE to -CURRENT?
What is involved? Right now
Thus spake Juli Mallett <[EMAIL PROTECTED]>:
> * De: Giorgos Keramidas <[EMAIL PROTECTED]> [ Data: 2003-01-31 ]
> [ Subjecte: Re: Seat-belt for source upgrades from stable to current ]
> > On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote:
> >
* De: Giorgos Keramidas <[EMAIL PROTECTED]> [ Data: 2003-01-31 ]
[ Subjecte: Re: Seat-belt for source upgrades from stable to current ]
> On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote:
> > Thus spake Mike Makonnen <[EMAIL PROTECTED]>:
> &g
Thus spake Giorgos Keramidas <[EMAIL PROTECTED]>:
> On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote:
> > Thus spake Mike Makonnen <[EMAIL PROTECTED]>:
> > > Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on
> > > the repository remotely, so you don't need
On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote:
> Thus spake Mike Makonnen <[EMAIL PROTECTED]>:
> > Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on
> > the repository remotely, so you don't need to have the files checked out localy.
>
> That's a pretty
Thus spake Ruslan Ermilov <[EMAIL PROTECTED]>:
> On Thu, Jan 30, 2003 at 09:58:15PM -0800, David Schultz wrote:
> > I don't know about Steve, but cvsup is the wrong answer for me
> > because it's a mirroring tool and not a version control tool.
> > Among the things I would like to do are:
> >
> >
On Friday 31 January 2003 00:58, David Schultz wrote:
> Thus spake Christopher Vance <[EMAIL PROTECTED]>:
> > On Thu, Jan 30, 2003 at 09:07:11PM -0800, Steve Kargl wrote:
> > : On Thu, Jan 30, 2003 at 08:05:06PM -0800, David Schultz wrote:
> > : > Thus spake Steve Kargl <[EMAIL PROTECTED]>:
> > : >
>Date: Thu, 30 Jan 2003 21:58:15 -0800
>From: David Schultz <[EMAIL PROTECTED]>
>I asked the question in hopes that there would be some neat
>feature of cvsup that mocked up some CVS metadata for me, but
>since nobody has mentioned any such thing, I guess I'm out of
>luck. Mirroring the entire re
On Thu, Jan 30, 2003 at 09:58:15PM -0800, David Schultz wrote:
> Thus spake Christopher Vance <[EMAIL PROTECTED]>:
> > On Thu, Jan 30, 2003 at 09:07:11PM -0800, Steve Kargl wrote:
> > : On Thu, Jan 30, 2003 at 08:05:06PM -0800, David Schultz wrote:
> > : > Thus spake Steve Kargl <[EMAIL PROTECTED]>
On Thu, Jan 30, 2003 at 11:33:16PM -0500, Mike Makonnen wrote:
> On Thu, 30 Jan 2003 20:05:06 -0800
> David Schultz <[EMAIL PROTECTED]> wrote:
>
> >
> > That's a great answer...to a different question. ;-)
> >
>
> Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on
On Wed, Jan 29, 2003 at 10:35:40PM -0500, Garance A Drosihn wrote:
> At 9:18 PM +0200 1/29/03, Sheldon Hearn wrote:
> >Can anyone think of a good way to implement an installworld /
> >installkernel seat-belt for source upgrades from stable to current?
> >
> >What I
Thus spake Christopher Vance <[EMAIL PROTECTED]>:
> On Thu, Jan 30, 2003 at 09:07:11PM -0800, Steve Kargl wrote:
> : On Thu, Jan 30, 2003 at 08:05:06PM -0800, David Schultz wrote:
> : > Thus spake Steve Kargl <[EMAIL PROTECTED]>:
> : > > On Thu, Jan 30, 2003 at 07:09:16PM -0800, David Schultz wrote
Thus spake Mike Makonnen <[EMAIL PROTECTED]>:
> Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on
> the repository remotely, so you don't need to have the files checked out localy.
That's a pretty good solution, and I use those occasionally. It
would be a perfect so
On Thu, Jan 30, 2003 at 09:07:11PM -0800, Steve Kargl wrote:
: On Thu, Jan 30, 2003 at 08:05:06PM -0800, David Schultz wrote:
: > Thus spake Steve Kargl <[EMAIL PROTECTED]>:
: > > On Thu, Jan 30, 2003 at 07:09:16PM -0800, David Schultz wrote:
: > > > OT: Is there a good way to get the CVS metadata
On Thu, Jan 30, 2003 at 08:05:06PM -0800, David Schultz wrote:
> Thus spake Steve Kargl <[EMAIL PROTECTED]>:
> > On Thu, Jan 30, 2003 at 07:09:16PM -0800, David Schultz wrote:
> > > OT: Is there a good way to get the CVS metadata in /usr/src and
> > > /usr/ports without transferring the entire sour
On Thu, 30 Jan 2003 20:05:06 -0800
David Schultz <[EMAIL PROTECTED]> wrote:
>
> That's a great answer...to a different question. ;-)
>
Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on
the repository remotely, so you don't need to have the files checked out local
Thus spake Steve Kargl <[EMAIL PROTECTED]>:
> On Thu, Jan 30, 2003 at 07:09:16PM -0800, David Schultz wrote:
> > OT: Is there a good way to get the CVS metadata in /usr/src and
> > /usr/ports without transferring the entire source tree over the
> > network? On some machines, I'd like to be able to
On Thu, Jan 30, 2003 at 07:09:16PM -0800, David Schultz wrote:
> Thus spake Christopher Vance <[EMAIL PROTECTED]>:
> > On Wed, Jan 29, 2003 at 10:35:40PM -0500, Garance A Drosihn wrote:
> > : How about requiring the user to touch some file in / or /boot which
> > : indicates the branch-tag that's a
Thus spake Christopher Vance <[EMAIL PROTECTED]>:
> On Wed, Jan 29, 2003 at 10:35:40PM -0500, Garance A Drosihn wrote:
> : How about requiring the user to touch some file in / or /boot which
> : indicates the branch-tag that's acceptable for installworlds? Then
> : you just need to propagate the t
On Wed, Jan 29, 2003 at 10:35:40PM -0500, Garance A Drosihn wrote:
: How about requiring the user to touch some file in / or /boot which
: indicates the branch-tag that's acceptable for installworlds? Then
: you just need to propagate the tag from the 'cvs co' stage to some
: file under /usr/src (
On 2003-01-29 21:55, Steve Kargl <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 30, 2003 at 12:47:13AM -0500, Garance A Drosihn wrote:
> > At 8:59 PM -0800 1/29/03, Steve Kargl wrote:
> > >You don't need a special file to indicate what version of
> > >FreeBSD you have. uname -r tells you.
> >
> > Actual
At 9:55 PM -0800 1/29/03, Steve Kargl wrote:
I don't run 4.x, so I do know. ;-)
I suspect on a 4.x system, you'll get "4.x-"
where is either FreeBSD or STABLE. To distinguish
between 4.x and 5.x, all we need the first character.
So, uname -r shows 4.7-FreeBSD for the security branch?
On Thu, Jan 30, 2003 at 12:47:13AM -0500, Garance A Drosihn wrote:
> At 8:59 PM -0800 1/29/03, Steve Kargl wrote:
> >
> >You don't need a special file to indicate what version of
> >FreeBSD you have. uname -r tells you.
> >
>
> Actually, one thing I don't know is how this would work when it
> com
At 8:59 PM -0800 1/29/03, Steve Kargl wrote:
You don't need a special file to indicate what version of
FreeBSD you have. uname -r tells you.
Actually, one thing I don't know is how this would work when it
comes to RELENG_4 vs RELENG_4_0 (since I don't run RELENG_4_0).
What does uname show for
At 8:59 PM -0800 1/29/03, Steve Kargl wrote:
On Wed, Jan 29, 2003 at 11:21:39PM -0500, Garance A Drosihn wrote:
At 8:05 PM -0800 1/29/03, Steve Kargl wrote:
>uname(1) works on both 4.7 and 5.0. This seems
>like a trivial problem to fix.
If you use something fixed like uname, then what does
On Wed, Jan 29, 2003 at 11:21:39PM -0500, Garance A Drosihn wrote:
> At 8:05 PM -0800 1/29/03, Steve Kargl wrote:
>
> >uname(1) works on both 4.7 and 5.0. This seems
> >like a trivial problem to fix.
>
> If you use something fixed like uname, then what does one do once
> they *DO* want to switch
At 8:05 PM -0800 1/29/03, Steve Kargl wrote:
On Wed, Jan 29, 2003, Garance A Drosihn wrote:
> How about requiring the user to touch some file in / or /boot which
indicates the branch-tag that's acceptable for installworlds? Then
you just need to propagate the tag from the 'cvs co' stage to so
On Wed, Jan 29, 2003 at 10:35:40PM -0500, Garance A Drosihn wrote:
> At 9:18 PM +0200 1/29/03, Sheldon Hearn wrote:
> >Can anyone think of a good way to implement an installworld /
> >installkernel seat-belt for source upgrades from stable to current?
> >
> >What I
At 9:18 PM +0200 1/29/03, Sheldon Hearn wrote:
Can anyone think of a good way to implement an installworld /
installkernel seat-belt for source upgrades from stable to current?
What I'm looking for is a way for installworld and installkernel
in the current source to look for some signatu
On Wed, Jan 29, 2003 at 09:18:22PM +0200, Sheldon Hearn wrote:
> Hi folks,
>
> Can anyone think of a good way to implement an installworld /
> installkernel seat-belt for source upgrades from stable to current?
>
> What I'm looking for is a way for installworld and install
Hi folks,
Can anyone think of a good way to implement an installworld /
installkernel seat-belt for source upgrades from stable to current?
What I'm looking for is a way for installworld and installkernel in the
current source to look for some signature in the target filesystem that
sug
On Sat, 2002-11-02 at 17:58, Conrad Sabatier wrote:
> > Now, my system was installed around 4.4, so I "should not" need to
> > update my boot blocks. Correct?
>
> Mmm, perhaps not. :-)
Eh, at this rate, I might as well...
> Myself, I played it ultra-safe and followed the upgrade instructions
On 03-Nov-2002 Ned Wolpert wrote:
> On Sat, 2002-11-02 at 17:20, Conrad Sabatier wrote:
>> Read the UPDATING file very carefully. You'll see that one of the steps
>> in upgrading from 4.x to 5.0 is updating the boot blocks.
>
> Yes, there are several entries. 2615 is the most interesting:
>
On Sat, 2002-11-02 at 17:20, Conrad Sabatier wrote:
> Read the UPDATING file very carefully. You'll see that one of the steps in
> upgrading from 4.x to 5.0 is updating the boot blocks.
Yes, there are several entries. 2615 is the most interesting:
In addition, you'll need to update
On 02-Nov-2002 Ned Wolpert wrote:
> Folks-
>
> I've ran into problem upgrading to -current from RELENG_4 after the
> 'make installkernel' process. One the kernel was installed, I rebooted.
> However, the old 4.7 kernel was loaded instead of the new -current
> kernel. I read from the archive a
Folks-
I've ran into problem upgrading to -current from RELENG_4 after the
'make installkernel' process. One the kernel was installed, I rebooted.
However, the old 4.7 kernel was loaded instead of the new -current
kernel. I read from the archive about how the old /modules directory
can cause p
to 'TGTS' in the main Makefile , and now
cd /usr/src; make buildworld
breaks a little later with:
make: don't know how to make incsinstall. Stop
Is anyone else able to upgrade from stable to current ?
As usual any thoughts on this are welcome.
Hans Lambermont
--
http://la
Ruslan Ermilov wrote:
> On Wed, May 15, 2002 at 03:32:45PM +0200, Hans Lambermont wrote:
> > I get a persistent Signal 12 when upgrading from -stable to -current :
> >
> Signal 12 indicates a non-existent system call. This means that
> your running world is incompatible w
On Wed, May 15, 2002 at 03:32:45PM +0200, Hans Lambermont wrote:
> Hi list,
>
> I get a persistent Signal 12 when upgrading from -stable to -current :
>
Signal 12 indicates a non-existent system call. This means that
your running world is incompatible with your kernel. Fix this
Hi list,
I get a persistent Signal 12 when upgrading from -stable to -current :
>>> stage 4: populating /usr/obj/usr/src/i386/usr/include
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386
OBJFORMAT_
This is a note for someone upgrading from 4.4 stable to current 5.0
comes right out of my experience in doing so the file
/usr/src/UPGRADE doesnt detail the following step
I didnt see ne 1 post this before may be it will help
some newbie like myself and perhaps somebody will add
it to the
This is a note for someone upgrading from 4.4 stable to current 5.0
comes right out of my experience in doing so the file
/usr/src/UPGRADE doesnt detail the following step
I didnt see ne 1 post this before may be it will help
some newbie like myself and perhaps somebody will add
it to the
r/run/nologin, or similar. (Just make sure
> you open plenty of shells for yourself first. :)
>
> I hope this is useful,
>
> Doug
I just wanted to let you know that I used this procedure on a very recent
3.4-STABLE to -CURRENT upgrade and it worked flawlessly. The whole
proced
Nik Clayton wrote:
> That, at least, was not the case with an upgrade I attempted a few days
> ago. On booting with kernel.GENERIC (from -current) it hung mounting the
> disks. Trying to go back to kernel.stable didn't work, because I'd had
> to update the /dev entries for -current, and they wo
On Tue, Mar 07, 2000 at 04:49:06PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Brooks Davis writes:
> : You don't need to update /dev though. As long as you don't change
> : anything else, a 4.0 kernel will work just fine with a 3.x /dev and
> : userland (other then top and friends
In message <[EMAIL PROTECTED]> Brooks Davis writes:
: You don't need to update /dev though. As long as you don't change
: anything else, a 4.0 kernel will work just fine with a 3.x /dev and
: userland (other then top and friends). You can delay updating /dev
: until later as the ata code will de
On Tue, Mar 07, 2000 at 07:14:42PM +, Nik Clayton wrote:
> On Tue, Mar 07, 2000 at 10:19:57AM -0800, Brooks Davis wrote:
> > On Tue, Mar 07, 2000 at 11:01:09AM +, Nik Clayton wrote:
> > > To which the response has been nil. At this point, you're either all
> > > struck dumb by the stagger
On Tue, Mar 07, 2000 at 10:19:57AM -0800, Brooks Davis wrote:
> On Tue, Mar 07, 2000 at 11:01:09AM +, Nik Clayton wrote:
> > To which the response has been nil. At this point, you're either all
> > struck dumb by the staggering simplicity and elegance of this approach,
> > or you're sat there
On Tue, Mar 07, 2000 at 09:20:01AM -0800, Steve Kargl wrote:
> Nik Clayton wrote:
> >> 5. Mount all the fixed disk partitions, and then (assuming they're all
> >> mounted under /mnt/root)
> >>
> >> cd /mnt/root/usr/src && make DESTDIR=/mnt/root
> >>
> >> 7. Build and install
On Tue, Mar 07, 2000 at 11:01:09AM +, Nik Clayton wrote:
> Quoting the whole thing deliberately:
>
> On Sun, Mar 05, 2000 at 08:24:35PM +, Nik Clayton wrote:
[snip]
>
> To which the response has been nil. At this point, you're either all
> struck dumb by the staggering simplicity and el
Nik Clayton wrote:
>> 5. Mount all the fixed disk partitions, and then (assuming they're all
>> mounted under /mnt/root)
>>
>> cd /mnt/root/usr/src && make DESTDIR=/mnt/root
>>
>>
>> 7. Build and install a new kernel
>>
>
> Come on then, which is it?
>
Okay, here's some
Quoting the whole thing deliberately:
On Sun, Mar 05, 2000 at 08:24:35PM +, Nik Clayton wrote:
> I had an abortive -stable to -current upgrade late last week, despite
> following the directions in UPGRADING, the two kernels I built (one
> custom, one GENERIC) both froze on me d
Hi guys,
I had an abortive -stable to -current upgrade late last week, despite
following the directions in UPGRADING, the two kernels I built (one
custom, one GENERIC) both froze on me during the reboot process.
I'm a little wary of doing it again like that, because it does take
some ti
At 23:38 13/1/2000 -0800, Lamont Lucas wrote:
>Hi, I've been trying unsuccessfully for two days to upgrade to -current on
>one of my machines at home, and was hoping there might be some suggestions
>from the group I could try.
>
>This is the consistant error off of today's -current tree:
>
>cc -O
On Thu, Jan 13, 2000 at 11:38:29PM -0800, Lamont Lucas wrote:
> This is the consistant error off of today's -current tree:
>
> cc -O -pipe -elf -Wall -fkeep-inline-functions
> -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/csu/i386-elf/crt1.c -o
> crt1.o
> cc: Internal compiler error: progr
Hi, I've been trying unsuccessfully for two days to upgrade to -current on
one of my machines at home, and was hoping there might be some suggestions
from the group I could try.
This is the consistant error off of today's -current tree:
cc -O -pipe -elf -Wall -fkeep-inline-functions
-I/usr/obj/
Doug White wrote:
> On Fri, 29 Oct 1999, Ben Rosengart wrote:
> > On Fri, 29 Oct 1999, Doug White wrote:
> > > I still hate the way the signal change was handled.
> > How would you have done it differently? As I understand it, the pain
> > was more or less inevitable.
>
> Perhaps, but there must
On Fri, 29 Oct 1999, Doug White wrote:
> On Fri, 29 Oct 1999, Ben Rosengart wrote:
>
> > On Fri, 29 Oct 1999, Doug White wrote:
> >
> > > I still hate the way the signal change was handled.
> >
> > How would you have done it differently? As I understand it, the pain
> > was more or less inev
On Fri, 29 Oct 1999, Ben Rosengart wrote:
> On Fri, 29 Oct 1999, Doug White wrote:
>
> > I still hate the way the signal change was handled.
>
> How would you have done it differently? As I understand it, the pain
> was more or less inevitable.
Perhaps, but there must be a way to keep gcc fr
On Fri, 29 Oct 1999, Doug White wrote:
> I still hate the way the signal change was handled.
How would you have done it differently? As I understand it, the pain
was more or less inevitable.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send
On Thu, 28 Oct 1999, Randy Bush wrote:
> trying to take a system from stable to current.
> o cvsup current
> o try makeworld but get
Bzzt! Read /usr/src/UPDATING. You need a new kernel first.
I still hate the way the signal change was handled.
Doug White|
On Thu, 28 Oct 1999, Randy Bush wrote:
> o so build -current binary for config
> o update kernel config file to -current
> o config a -current kernel
> o make a -current kernel
> o install -current kernel
> o reboot
> o crash in init after configuring network, but was too fast to c
trying to take a system from stable to current.
o cvsup current
o try makeworld but get
cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC
-I/usr/obj/usr/src/tmp/usr/include -DL_ashrsi3 -o
69 matches
Mail list logo
