buildworld has been broken for me since Sunday 20110815 at atrun

2011-08-16 Thread eculp
Is anyone else seeing this?  This is current AMD64.  I'm running the  
compile from Saturday 20110814 that I have been hammering and it has  
been rock solid.


# uname -a
FreeBSD home.encontacto.net 9.0-BETA1 FreeBSD 9.0-BETA1 #16: Sat Aug  
13 05:09:17 CDT 2011  
r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO  amd64


This morning I started with a make clean to be sure and recompile all  
just in case and the same.


=== lib/clang/include (all)
=== libexec (all)
=== libexec/atrun (all)
cc -O2 -pipe  -DATJOB_DIR=\/var/at/jobs/\   
-DLFILE=\/var/at/jobs/.lockfile\  -DLOADAVG_MX=1.5  
-DATSPOOL_DIR=\/var/at/spool\  -DVERSION=\2.9\ -DDAEMON_UID=1  
-DDAEMON_GID=1  -DDEFAULT_BATCH_QUEUE=\'E\'  -DDEFAULT_AT_QUEUE=\'c\'  
-DPERM_PATH=\/var/at/\ -I/usr/src/libexec/atrun/../../usr.bin/at  
-I/usr/src/libexec/atrun -DLOGIN_CAP -DPAM -std=gnu99  
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k  
-Wno-uninitialized -Wno-pointer-sign -c /usr/src/libexec/atrun/atrun.c
cc -O2 -pipe  -DATJOB_DIR=\/var/at/jobs/\   
-DLFILE=\/var/at/jobs/.lockfile\  -DLOADAVG_MX=1.5  
-DATSPOOL_DIR=\/var/at/spool\  -DVERSION=\2.9\ -DDAEMON_UID=1  
-DDAEMON_GID=1  -DDEFAULT_BATCH_QUEUE=\'E\'  -DDEFAULT_AT_QUEUE=\'c\'  
-DPERM_PATH=\/var/at/\ -I/usr/src/libexec/atrun/../../usr.bin/at  
-I/usr/src/libexec/atrun -DLOGIN_CAP -DPAM -std=gnu99  
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k  
-Wno-uninitialized -Wno-pointer-sign -c  
/usr/src/libexec/atrun/gloadavg.c
cc -O2 -pipe  -DATJOB_DIR=\/var/at/jobs/\   
-DLFILE=\/var/at/jobs/.lockfile\  -DLOADAVG_MX=1.5  
-DATSPOOL_DIR=\/var/at/spool\  -DVERSION=\2.9\ -DDAEMON_UID=1  
-DDAEMON_GID=1  -DDEFAULT_BATCH_QUEUE=\'E\'  -DDEFAULT_AT_QUEUE=\'c\'  
-DPERM_PATH=\/var/at/\ -I/usr/src/libexec/atrun/../../usr.bin/at  
-I/usr/src/libexec/atrun -DLOGIN_CAP -DPAM -std=gnu99  
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k  
-Wno-uninitialized -Wno-pointer-sign  -o atrun atrun.o gloadavg.o  
-lpam -lutil

/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
*** Error code 1

Stop in /usr/src/libexec/atrun.
*** Error code 1

Stop in /usr/src/libexec.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
(END)

Thanks,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: buildworld has been broken for me since Sunday 20110815 at atrun

2011-08-16 Thread eculp

Quoting Mark Felder f...@feld.me:

On Tue, 16 Aug 2011 12:29:47 -0500, Edwin L. Culp W.  
edwinlc...@gmail.com wrote:



Worked perfectly.  Maybe it would be a good idea to put the step by
step solution for other folks like me who  haven't put enough effort
to understand the 20110815: entry.



These steps are detailed in the handbook and you should be following  
them every

time you rebuild CURRENT.


Sorry, it looks like I have been doing things in the wrong order for  
years.  Thanks a lot for pointing that out.


ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: For about a week I've been trying to build a release that breaks at docproj. Just low priority break information.

2011-08-14 Thread eculp

Quoting Garrett Cooper yaneg...@gmail.com:


On Sat, Aug 13, 2011 at 9:09 AM, Garrett Cooper yaneg...@gmail.com wrote:

On Sat, Aug 13, 2011 at 8:37 AM, eculp ec...@encontacto.net wrote:

I've been building a release about once a week on current.  The last
successful build was on august 8 but don't know when this started  
but in the

last few days.

I am building on
# uname -a
FreeBSD Home.EnContacto.net 9.0-BETA1 FreeBSD 9.0-BETA1 #16: Sat Aug 13
05:09:17 CDT 2011
r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO  amd64

All builds include ports kernel updated ports, etc.  I build it with
generate-release.sh script below.

sh generate-release.sh head /local3/release


   Please try the attached patch.


This will work better.
Thanks,
-Garrett



World was broken for me on my early csup, I'm retrying and will get  
back after a successful build.


Thanks,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


For about a week I've been trying to build a release that breaks at docproj. Just low priority break information.

2011-08-13 Thread eculp
I've been building a release about once a week on current.  The last  
successful build was on august 8 but don't know when this started but  
in the last few days.


I am building on
# uname -a
FreeBSD Home.EnContacto.net 9.0-BETA1 FreeBSD 9.0-BETA1 #16: Sat Aug  
13 05:09:17 CDT 2011  
r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO  amd64


All builds include ports kernel updated ports, etc.  I build it with  
generate-release.sh script below.


sh generate-release.sh head /local3/release

The results that I get follow:

===   Generating temporary packing list
===  Checking if textproc/docproj already installed
===   docproj-1.17_4 is already installed
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of textproc/docproj
  without deleting it first, set the variable FORCE_PKG_REGISTER
  in your environment or the make install command line.
*** Error code 1

Stop in /usr/ports/textproc/docproj.
Home.EnContacto.net
/usr/src/release #
Home.EnContacto.net
/usr/src/release # portmaster textproc/docproj

=== Port directory: /usr/ports/textproc/docproj

=== This port is marked IGNORE
=== user must set WITH_JADETEX variable to 'yes' or 'no'

=== If you are sure you can build it, remove the
   IGNORE line in the Makefile and try again.

I'm not in a hurry nor do I really need it.  I can easily use what I  
have.  Just a bit of low priority information.


Thanks,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Can't map a Spanish keyboard on Current but in FreeBSD 7.4-STABLE it works fin.

2011-08-08 Thread eculp

Quoting Tom Evans tevans...@googlemail.com:


On Sat, Aug 6, 2011 at 12:07 AM, eculp ec...@encontacto.net wrote:

I'm running kde on both and 7.4 works equally well with ttys and with
kde4-4.6.5.

My FreeBSD 9.0-BETA1 works with ttys but not even close with kde4-4.6.5.

Is this me or could it be kde or Current?  There doesn't seem to be any
changes in the language files spanish.iso.acc.kbd, for example.

I've been tolerating this for the last week since setting it up with Beta1.

Thanks,

ed


Have you told hald that the keyboard has a different layout?

IE, do you have this:


$ cat /usr/local/etc/hal/fdi/policy/x11-input.fdi

?xml version=1.0 encoding=ISO-8859-1?
deviceinfo version=0.2
  device
match key=info.capabilities contains=input.keyboard
  merge key=input.x11_options.XkbLayout type=stringes/merge
/match
  /device
/deviceinfo



Works Great.  Thanks Tom.  I don't have that file on 7.4 but it works  
too.  I've seen changes to hald on the list but haven't paid enough  
attention.


Thanks again.  That makes my life soo much better.

ed


Cheers

Tom



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Can't map a Spanish keyboard on Current but in FreeBSD 7.4-STABLE it works fin.

2011-08-05 Thread eculp
I'm running kde on both and 7.4 works equally well with ttys and with  
kde4-4.6.5.


My FreeBSD 9.0-BETA1 works with ttys but not even close with kde4-4.6.5.

Is this me or could it be kde or Current?  There doesn't seem to be  
any changes in the language files spanish.iso.acc.kbd, for example.


I've been tolerating this for the last week since setting it up with Beta1.

Thanks,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.

2011-07-25 Thread eculp

Quoting Warren Block wbl...@wonkity.com:


On Mon, 25 Jul 2011, Andriy Gapon wrote:


on 25/07/2011 07:47 Warren Block said the following:
2.  The options don't always really apply.  Create when ad0 is  
highlighted leads
the user to think they can create a new device, like ad1.  But it  
will really
create another partition.  Delete on ad0 deletes all the  
partitions, not ad0.

No warning, either.


Are you sure about this one?
I have never expected that any installer would be able to create or delete
hardware (a hard disk) in my computer.


Device as in entry in /dev.

It's a little blurrier than that.  With no partitioning scheme,  
Create makes one, having the user select the type.  After that, it  
creates new partitions.


Having messed with this editor more, I can make it work and see the  
intent of the user interface.  I wish I could suggest a good way to  
make it more clear, but can't quite get my brain around it right now.


That makes two of us right now.  I gave up, accepted the automatic  
partition and everything else went as expected, I suppose.  The disk  
results are:


# df
Filesystem  1K-blocksUsed Avail Capacity  Mounted on
/dev/ada0p2 941441086 2150880 863974920 0%/
devfs   1   1 0   100%/dev

In my world from the beginning of commercial unix, I have never had a  
one partition disk.  I'm not sure if it is that bad with today's,  
controllers, drives, drivers, etc.  I hope someone chimes in with a I  
see no major problems with gpt.


My major problem was editing the automatic swap that was set at 4G and  
the menu would not let me change the 4G.  The experienced option would  
not accept a blank value as swap even though there was message that  
said it would.


I feel like a real idiot and am beginning to believe that it might be true.
The rest of the install was brain dead.  It was possibly a bit simpler  
than the previous.  Less decisions ;)


I had the idea the following were available in the new installer.
  1.  Raid configuration
  2.  ZFS
  3.  Regular everyday simple disk partitioning as before.

I wasn't able to find any functional option except the one mentioned above.

Now, I have to accept this single partition or upgrade sources to  
date, build a release and reinstall but I don't know if the problem  
has been fixed.  I'll probably give it a try.  It isn't that much of a  
deal.


Thanks,
ed

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.

2011-07-25 Thread eculp

Quoting Adam Vande More amvandem...@gmail.com:


On Mon, Jul 25, 2011 at 11:46 AM, eculp ec...@encontacto.net wrote:


That makes two of us right now.  I gave up, accepted the automatic
partition and everything else went as expected, I suppose.  The disk results
are:

# df
Filesystem  1K-blocksUsed Avail Capacity  Mounted on
/dev/ada0p2 941441086 2150880 863974920 0%/
devfs   1   1 0   100%/dev

In my world from the beginning of commercial unix, I have never had a one
partition disk.  I'm not sure if it is that bad with today's, controllers,
drives, drivers, etc.  I hope someone chimes in with a I see no major
problems with gpt.

My major problem was editing the automatic swap that was set at 4G and the
menu would not let me change the 4G.  The experienced option would not
accept a blank value as swap even though there was message that said it
would.

I feel like a real idiot and am beginning to believe that it might be true.
The rest of the install was brain dead.  It was possibly a bit simpler than
the previous.  Less decisions ;)

I had the idea the following were available in the new installer.
 1.  Raid configuration
 2.  ZFS
 3.  Regular everyday simple disk partitioning as before.

I wasn't able to find any functional option except the one mentioned above.

Now, I have to accept this single partition or upgrade sources to date,
build a release and reinstall but I don't know if the problem has been
fixed.  I'll probably give it a try.  It isn't that much of a deal.



Hopefully I add something of value to this thread, but as a workaround you
can use a PCBSD image and installer to install/partion plain vanilla FreeBSD
with the options you mentioned earlier in a graphical enviroment.


Thanks Adam,

I suppose that I could just pull it into this machine and execute it  
as if it were sysinstall and reconfigure from the same box without  
having to update, make release, etc.


I'm going to give that a try.

Have a great day.

ed


--
Adam Vande More



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Trying to install current from a memory stick and then a DVD and got a new and strange installer.

2011-07-24 Thread eculp
I have been hearing about a new installer but I obviously have not  
payed enough attention, I am afraid. I started running freebsd at 2.0  
and never really had a problem with understanding the installation  
program.  There is always a first time, I guess.


ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/

When booting I seem to get a screen that makes me remember installer  
screens of the 1980s.  (They were not exactly intuitive.)


I somehow got the idea that the new installer was graphic.  Maybe  
something like PCBsd that is not bad at all.  I use it on all our  
employees computers.  Actually, after seeing this, I would love to  
have the old installer back.  Is their an option for that?


Does this new ASCII installer have a how to with a bit of  
information on the flow of the installation.


Thanks,

ed

P.D. The handbook does not seem to cover the installer I am seeing  
because it is 8.2.  It shows what I would love to see.  Maybe I need  
to install 8.2 and upgrade?


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.

2011-07-24 Thread eculp

Quoting Nathan Whitehorn nwhiteh...@freebsd.org:


On 07/24/11 16:29, eculp wrote:
I have been hearing about a new installer but I obviously have not  
payed enough attention, I am afraid. I started running freebsd at  
2.0 and never really had a problem with understanding the  
installation program.  There is always a first time, I guess.


ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/

When booting I seem to get a screen that makes me remember  
installer screens of the 1980s.  (They were not exactly intuitive.)


I somehow got the idea that the new installer was graphic.  Maybe  
something like PCBsd that is not bad at all.  I use it on all our  
employees computers.  Actually, after seeing this, I would love to  
have the old installer back.  Is their an option for that?


Does this new ASCII installer have a how to with a bit of  
information on the flow of the installation.


Thanks,


Can you please describe what you didn't like about it, and what you  
would prefer be changed? Reminiscent of the 1980s is not really  
helpful, especially given that the new installer in fact looks very  
much like sysinstall, which you seemed to like.

-Nathan


I do not get a menu that I can understand or relate to any of the  
installations that I have done previously.  I will give it another try  
and try to explain what I don't understand.


Thanks,

ed

P.S. Is their no documentation on what to expect?

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


seeing pf: state key linking mismatch! with pf on up to date current but not on FreeBSD 7.4-STABLE

2011-07-03 Thread eculp
Something is strange with PF.  I get the above error using pf on  
current but not on FreeBSD stable.  The pf configuration hasn't  
changed for a couple of years on either and they are the same except  
for hardware names.


The two machines are:
9.0-CURRENT FreeBSD 9.0-CURRENT #247: Wed Jun 29 04:49:16 CDT 2011
7.4-STABLE FreeBSD 7.4-STABLE #1228: Sat Jun 25 04:42:55 CDT 2011

Anyone else seeing this?

Thanks,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: seeing pf: state key linking mismatch! with pf on up to date current but not on FreeBSD 7.4-STABLE

2011-07-03 Thread eculp

Quoting Fabian Keil freebsd-lis...@fabiankeil.de:


eculp ec...@encontacto.net wrote:


Something is strange with PF.  I get the above error using pf on
current but not on FreeBSD stable.  The pf configuration hasn't
changed for a couple of years on either and they are the same except
for hardware names.


pf has recently been updated in CURRENT.


The two machines are:
9.0-CURRENT FreeBSD 9.0-CURRENT #247: Wed Jun 29 04:49:16 CDT 2011
7.4-STABLE FreeBSD 7.4-STABLE #1228: Sat Jun 25 04:42:55 CDT 2011

Anyone else seeing this?


Yes:
http://lists.freebsd.org/pipermail/freebsd-pf/2011-June/006191.html

Fabian


Thanks, Fabian.  From what I understand, not officially fixed yet.

Have a great weekend.

ed





___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Opinion on using AMD Phenom II x6 1090t with Gigabyte 890BPA-UD3H and 8GB DDR-3 as a WebServer.

2011-06-30 Thread eculp

Quoting Dennis Glatting d...@penx.com:


On Wed, 2011-06-29 at 07:31 -0500, eculp wrote:

I just saw this box that is being promoted as a gaming machine at a
great price and am considering it as a web-server.

In addition to having no information on the CPU as a server lack of
comfort with 6 cores and memory 8GB of memory that I am having a
problem with.  I am not a gamer but I have always assumed that a
gaming machine needs the most aggressive hardware.  I have also seen
this processor with 12 GB rather than 8 which, in my ignorance sounds
better.

Any opinions and guidance are appreciated.



I have been moving away from Gigabyte however I do have a similar board:

MB GIGABYTE GA-870A-UD3 RT


This one is GA-890BPA-UD3G that also has RealTek 811D 10/100/1000 Mbit  
that I doubt will be a limitation.  I'll stick in another card anyway.  
I also like that has is sata3 and usb 3 so it seems to be up to date.




My key complaint about Gigabyte is the ReatTek Ethernet chips. Realtek
doesn't publish chip specs and therefore the drivers under FreeBSD/Linux
are so-so (i.e., they work but not performance optimized and forget
about anything but the default MTU).

On my board I hate the South Bridge chip, which is useless for RAID.

I am also unable to install VMWare ESXi, my last ditch attempt to find a
use for my board. There appears to be a hardware incompatibility while
installing (i.e., not during the probe sequence, rather after that
sequence then onto installation).

Thanks a lot for your suggestions and point of view.  I'm begining to  
think that this may be too much machine but comming down doesn't save  
much so I will probably give it a try.


ed






___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Totally confused with the /usrsrc/UPDATING for 20110424 CAM-based ATA stack

2011-05-03 Thread eculp

With this confusion I need someone to give me an idea on renumbering.

I have two disks on this old machine that I have keep current sin  
FreeBSD 6 IIRC as preparation for all the new goodies but this really  
bit me in the morning with a generic kernel and had a heck of a time  
getting it up.


I have a new kernel with the new options.
optionsATA_CAM
device ahci
device mvs
device siis

This  morning was such a shock that I am tempted to go back to the old  
kernel config that I understand still works but gonna try to bite the  
bullit.


My fstab that I assume is still necessary is:

 /dev/ad4s1bnoneswapsw  0   0
 /dev/ad4s1a/   ufs rw  1   1
 /dev/ad4s2g/backup ufs rw  2   2
 /dev/ad4s1g/home   ufs rw  2   2
 /dev/ad4s2f/releaseufs rw 
  2   2

 /dev/ad4s2d/tmpufs rw  2   2
 /dev/ad4s1e/usrufs rw  2   2
 /dev/ad4s1h/usr/local  ufs rw 
  2   2

 /dev/ad4s1f/varufs rw  2   2
 /dev/ad4s2e/var/tmpufs rw 
  2   2

 /dev/acd0  /cdrom  cd9660  ro,noauto   0   0
 /dev/acd1  /cdrom1 cd9660  ro,noauto   0   0
 /dev/cd0   /cdrom  cd9660  ro,noauto   0   0
 /dev/cd1   /cdrom  cd9660  ro,noauto   0   0
#
/dev/ad0s1a   /newufs rw  1   1
/dev/ad0s1g  /new/home   ufs rw  2   2
/dev/ad0s1d/new/tmpufs rw  2   2
/dev/ad0s1e/new/usrufs rw  2   2
/dev/ada01h  /new/usr/local  ufs rw  2   2
/dev/ada01f/new/varufs rw  2   2

I am totally confused on how these should now be.

Any help appreciated.

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


I want to put together a new server with 9.0 that I will use as a prototype

2011-03-15 Thread eculp
I want to put together a new server with 9.0  that I will use as a  
prototype for hardware and OS updating.  By the time I finish I'm sure  
9 will be out;) I will use them to replace my 7.4 servers.


The only doubt that I have relates to disks.  I would like to use GPT  
and ZFS for the disks and have never used either but my real concern  
is ZFS and problems that I could have due to my ignorance in choosing  
the correct configuration for installing and then maintaining once in  
production.  I like to think that I am not a total idiot and should be  
able to.  I am also concerned with ZFS life expectancy (oracle).  I'm  
assuming the GPT will be around for a while and don't see it as a  
problem.


I would appreciate any support as to any errors my logic and which ZFS  
setup is the most practical, up-time and maintenance wise.  If there  
is something better that I've missed, I would love to here it.  ZFS is  
my raid solution and I find it cool.


Thanks for any and all suggestions, slaps on the wrist, etc, etc.

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash.

2011-01-13 Thread eculp

Quoting Ariff Abdullah ar...@freebsd.org:


On Wed, 12 Jan 2011 09:53:03 -0600
eculp ec...@encontacto.net wrote:

Quoting Ariff Abdullah ar...@freebsd.org:

 On Wed, 12 Jan 2011 22:51:29 +0800
 Ariff Abdullah ar...@freebsd.org wrote:

 []

 Try disabling mtrr, machdep.disable_mtrrs=0 through
 boot prompt or /boot/loader.conf.


 Grr.. should be machdep.disable_mtrrs=1

Caught it, changed it en loader.conf, rebooted and have had youtube

running more that 10 minutes with no ill affects.


Keep in mind that disabling mtrr is a temporary measure.


Hopefully this will be announced when the problem is fixed because I  
have NO idea what mtrr value is, haven't thought about it and at my  
age, I would prefer to keep it that way ;)


Thanks,

ed




Want to clarify that this in with current i386.

9.0-CURRENT FreeBSD 9.0-CURRENT #161: Wed Jan 12 04:38:15 CST 2011

r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO  i386

Thanks again,

ed

Thanks so much for your help.

ed


 If that is the case, you probably want this:

 http://people.freebsd.org/~ariff/misc/mtrr.diff




This breakage was due to r215415 commit. Jung-uk Kim, any idea ?


--
Ariff Abdullah
FreeBSD

... Recording in stereo is obviously too advanced
and confusing for us idiot * users :P 

... Going with the standard and orthodox
is the death of intellect ..



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash.

2011-01-12 Thread eculp

Quoting Barbara barbara.xxx1...@libero.it:





For a week or so, with up to date, current, ports, etc.  everytime I
open a page that has automatic flash video my mouse freezes and I have
to manually kill X and restart.  I had worked fine for many months.
Yesterday I rebuilt all linux emulation.  All ports are up to date as
of today.  I have no idea where to look.

Anyone else seen this or know where to look.

thanks,




From what I can see, on CURRENT most of the flash objects are triggering a

X

error.
I can see it on the console where I started X, but I don't remember it now.
I'll post il later.
Anyway Xorg is still working after that.

Barbara


I think that it could be related to this message:
http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021997.html
even if I'm on i386


Thanks, Barbara.  I am on i386 also.  It sounds as though it could  
very well be but I would expect others to be seeing something similar.  
 The kernel that I am using was built and rebooted from yesterday's  
sources with hopes that the problem would just go away same with  
world and ports but no cigar.  It is still the same and I don't have  
an old enough kernel to go back to so I guess I will just have to wait  
until something changes.


Have a great day,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash.

2011-01-12 Thread eculp

Quoting Gary Jennejohn gljennj...@googlemail.com:


On Wed, 12 Jan 2011 07:09:10 -0600
eculp ec...@encontacto.net wrote:


Quoting Barbara barbara.xxx1...@libero.it:



 For a week or so, with up to date, current, ports, etc.  everytime I
 open a page that has automatic flash video my mouse freezes and I have
 to manually kill X and restart.  I had worked fine for many months.
 Yesterday I rebuilt all linux emulation.  All ports are up to date as
 of today.  I have no idea where to look.

 Anyone else seen this or know where to look.

 thanks,


 From what I can see, on CURRENT most of the flash objects are  
triggering a

 X
 error.
 I can see it on the console where I started X, but I don't  
remember it now.

 I'll post il later.
 Anyway Xorg is still working after that.

 Barbara

 I think that it could be related to this message:
  
http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021997.html

 even if I'm on i386

Thanks, Barbara.  I am on i386 also.  It sounds as though it could
very well be but I would expect others to be seeing something similar.
  The kernel that I am using was built and rebooted from yesterday's
sources with hopes that the problem would just go away same with
world and ports but no cigar.  It is still the same and I don't have
an old enough kernel to go back to so I guess I will just have to wait
until something changes.

Have a great day,



I'm running 9-current on amd64 and have experienced no problems with
flash using linux-opera, which is what I use to view flash content.
Otherwise I use linux-firefox with the flash plugin disabled.

Assuming you use firefox you could try
a) installing a flash blocker
b) installing NoScript, since it basically automatically blocks the
   execution of java scripts, etc., which might help
c) checking Tools-Add-Ons-Plugins to see whether you can disable flash
   (not sure about this, but it works with linux-firefox)

Thanks a bunch Gary.

That is great information.  I'm going to try that on my browsers.   
Flash can be a real pain in . . . . the neck.


I have it working now with Ariff's correction putting
machdep.disable_mtrrs=1
in loader.conf rebooting and all is now well.

have a great day all.

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash.

2011-01-12 Thread eculp

Quoting Ariff Abdullah ar...@freebsd.org:


On Wed, 12 Jan 2011 22:51:29 +0800
Ariff Abdullah ar...@freebsd.org wrote:



[]


Try disabling mtrr, machdep.disable_mtrrs=0 through
boot prompt or /boot/loader.conf.



Grr.. should be machdep.disable_mtrrs=1


Caught it, changed it en loader.conf, rebooted and have had youtube  
running more that 10 minutes with no ill affects.


Want to clarify that this in with current i386.

9.0-CURRENT FreeBSD 9.0-CURRENT #161: Wed Jan 12 04:38:15 CST 2011  
r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO  i386


Thanks again,

ed

Thanks so much for your help.

ed




If that is the case, you probably want this:

http://people.freebsd.org/~ariff/misc/mtrr.diff



--
Ariff Abdullah
FreeBSD

... Recording in stereo is obviously too advanced
and confusing for us idiot * users :P 

... Going with the standard and orthodox
is the death of intellect ..




___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: world build stuck in gnu for about a week for me.

2010-11-15 Thread eculp

Quoting Andreas Tobler andre...@freebsd.org:


On 14.11.10 16:40, eculp wrote:

I build world several times a week on this machine:
9.0-CURRENT FreeBSD 9.0-CURRENT #126: Mon Nov  8 07:22:49 CST 2010

Since the above build I have not been able to get past gnu.

Today it broke at gdb :


===  gnu/usr.bin/dialog (cleandir)
===  gnu/usr.bin/dialog/TESTS (cleandir)
===  gnu/usr.bin/diff (cleandir)
===  gnu/usr.bin/diff/doc (cleandir)
rm -f diff.info diff.info.gz
===  gnu/usr.bin/diff3 (cleandir)
===  gnu/usr.bin/gdb (cleandir)
===  gnu/usr.bin/gdb/doc (cleandir)
===  gnu/usr.bin/gdb/libgdb (cleandir)
Unclosed substitution for TARGET_ARCH (/ missing)


This one was fixed today:

http://svn.freebsd.org/viewvc/base?view=revisionrevision=215292

Gruss,
Andreas


Thanks, Andreas.  With a new cvsup this morning it now stops at a  
different point for me:



Making grotty.1 from  
/usr/src/gnu/usr.bin/groff/src/devices/grotty/../../../../../../contrib/groff/src/devices/grotty/grotty.man

gzip -cn grotty.1  grotty.1.gz
=== gnu/usr.bin/groff/src/preproc (all)
=== gnu/usr.bin/groff/src/preproc/eqn (all)
c++ -O2 -pipe  
-I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/preproc/eqn -I. -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/include -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/include -fstack-protector -fno-rtti -fno-exceptions -c  
eqn.cpp

y.tab.c: In function 'int yygrowstack()':
y.tab.c:703: error: invalid conversion from 'void*' to 'short int*'
y.tab.c:709: error: invalid conversion from 'void*' to 'YYSTYPE*'
*** Error code 1

Stop in /usr/src/gnu/usr.bin/groff/src/preproc/eqn.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/groff/src/preproc.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/groff/src.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/groff.
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1

Stop in /usr/src/gnu.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


world build stuck in gnu for about a week for me.

2010-11-14 Thread eculp

I build world several times a week on this machine:
9.0-CURRENT FreeBSD 9.0-CURRENT #126: Mon Nov  8 07:22:49 CST 2010

Since the above build I have not been able to get past gnu.

Today it broke at gdb :


=== gnu/usr.bin/dialog (cleandir)
=== gnu/usr.bin/dialog/TESTS (cleandir)
=== gnu/usr.bin/diff (cleandir)
=== gnu/usr.bin/diff/doc (cleandir)
rm -f diff.info diff.info.gz
=== gnu/usr.bin/diff3 (cleandir)
=== gnu/usr.bin/gdb (cleandir)
=== gnu/usr.bin/gdb/doc (cleandir)
=== gnu/usr.bin/gdb/libgdb (cleandir)
Unclosed substitution for TARGET_ARCH (/ missing)
*** Error code 2

Stop in /usr/src/gnu/usr.bin/gdb.
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1

Stop in /usr/src/gnu.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

My main concern is if it is my error or a known problem that I have  
missed.  I regularly do make check-old and delete-old.


Thanks for confirming,

ed

P.S. This isn't a problem but a concern.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: world build stuck in gnu for about a week for me.

2010-11-14 Thread eculp

Quoting Andreas Tobler andre...@freebsd.org:


On 14.11.10 16:40, eculp wrote:

I build world several times a week on this machine:
9.0-CURRENT FreeBSD 9.0-CURRENT #126: Mon Nov  8 07:22:49 CST 2010

Since the above build I have not been able to get past gnu.

Today it broke at gdb :


===  gnu/usr.bin/dialog (cleandir)
===  gnu/usr.bin/dialog/TESTS (cleandir)
===  gnu/usr.bin/diff (cleandir)
===  gnu/usr.bin/diff/doc (cleandir)
rm -f diff.info diff.info.gz
===  gnu/usr.bin/diff3 (cleandir)
===  gnu/usr.bin/gdb (cleandir)
===  gnu/usr.bin/gdb/doc (cleandir)
===  gnu/usr.bin/gdb/libgdb (cleandir)
Unclosed substitution for TARGET_ARCH (/ missing)


This one was fixed today:

http://svn.freebsd.org/viewvc/base?view=revisionrevision=215292


Thanks, I supped too early,

ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Having a problem with security/libassuan-1 when compiling gnupg.

2010-06-17 Thread eculp
Having a problem with security/libassuan-1 when compiling gnupg.  I  
did the upgrade to libassuan-2.0.0 following the instructions in  
UPDATING and this is the first problem that I have seen.


===   gnupg-2.0.14_3 depends on package: libassuan-1=1.0.5 - not found
===Verifying install for libassuan-1=1.0.5 in  
/usr/ports/security/libassua

n-1

===  libassuan-1-1.0.5 conflicts with installed package(s):
  libassuan-2.0.0

  They install files into the same place.
  Please remove them first with pkg_delete(1).
*** Error code 1

Stop in /usr/ports/security/libassuan-1.
*** Error code 1

Stop in /usr/ports/security/gnupg.

=== make failed for security/gnupg
=== Aborting update

Any suggestions will be appreciated.

TIA,

ed

Kernel:
9.0-CURRENT FreeBSD 9.0-CURRENT #6: Sun Jun  6 06:23:48 CDT 2010

Today's world.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Having a problem with security/libassuan-1 when compiling gnupg.

2010-06-17 Thread eculp

Quoting Kevin Oberman ober...@es.net:


Date: Thu, 17 Jun 2010 12:03:48 -0500
From: eculp ec...@encontacto.net
Sender: owner-freebsd-curr...@freebsd.org

Having a problem with security/libassuan-1 when compiling gnupg.  I
did the upgrade to libassuan-2.0.0 following the instructions in
UPDATING and this is the first problem that I have seen.

===   gnupg-2.0.14_3 depends on package: libassuan-1=1.0.5 - not found
===Verifying install for libassuan-1=1.0.5 in
/usr/ports/security/libassua
n-1

===  libassuan-1-1.0.5 conflicts with installed package(s):
   libassuan-2.0.0

   They install files into the same place.
   Please remove them first with pkg_delete(1).
*** Error code 1

Stop in /usr/ports/security/libassuan-1.
*** Error code 1

Stop in /usr/ports/security/gnupg.

=== make failed for security/gnupg
=== Aborting update

Any suggestions will be appreciated.


Sorry. Just re-read the message.

Since you already have libassuan-2.0.0 installed, you will probably need
to:
pkg_delete -f libassuan-2.0.0
portinstall libassuan-1
or
portmaster security/libassuan-1



Thanks a lot, Kevin.  It is now working fin as far as I can tell.  I  
was confused as to which was the prefered version for Current and was  
sure that I had seen somewhere that is was 2.x but was probably  
confused with another port.


Thanks again,

ed


--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net  Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


signal 12's everywhere on Current with update this morning.

2003-11-13 Thread eculp
I installed an older current snap, Oct 26, on a brandnew dell power edge
with a single Xeon 2.4 GHz cpu and 1G in memory.  It was running great.
I installed everything except the kitchen sink.  Then I decided it was
time to update, I've got serveral other machines weathering the storms.
Bad idea.  It doesn't hang or anything that I can get my teeth into but
it just give signal 12 core dumps on many if not most applications.  I
caught this before finishing an install on another box, yesterday morning.
One of the apps that generates signal 12 is ls so I tried pulling ls
from the other box and it no longer has a problem.  I am at a lost.
Any suggestions for where to start would be appreciated.

Thanks in advance,

ed

-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: signal 12's everywhere on Current with update this morning.

2003-11-13 Thread eculp
Mensaje citado por Ceri Davies [EMAIL PROTECTED]:

| On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote:
|  I installed an older current snap, Oct 26, on a brandnew dell power edge
|  with a single Xeon 2.4 GHz cpu and 1G in memory.  It was running great.
|  I installed everything except the kitchen sink.  Then I decided it was
|  time to update, I've got serveral other machines weathering the storms.
|  Bad idea.  It doesn't hang or anything that I can get my teeth into but
|  it just give signal 12 core dumps on many if not most applications.  I
|  caught this before finishing an install on another box, yesterday morning.
|  One of the apps that generates signal 12 is ls so I tried pulling ls
|  from the other box and it no longer has a problem.  I am at a lost.
|  Any suggestions for where to start would be appreciated.
|
| Read /usr/src/UPDATING.
|
Thanks, I missed that.  :(   Sorry for the noise.

ed

-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Unattended reboot was Re: signal 12's everywhere on Current with update this morning.

2003-11-13 Thread eculp
Mensaje citado por [EMAIL PROTECTED]:

| Mensaje citado por Ceri Davies [EMAIL PROTECTED]:
|
| | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote:
| |  I installed an older current snap, Oct 26, on a brandnew dell power edge
| |  with a single Xeon 2.4 GHz cpu and 1G in memory.  It was running great.
| |  I installed everything except the kitchen sink.  Then I decided it was
| |  time to update, I've got serveral other machines weathering the storms.
| |  Bad idea.  It doesn't hang or anything that I can get my teeth into but
| |  it just give signal 12 core dumps on many if not most applications.  I
| |  caught this before finishing an install on another box, yesterday
| morning.
| |  One of the apps that generates signal 12 is ls so I tried pulling ls
| |  from the other box and it no longer has a problem.  I am at a lost.
| |  Any suggestions for where to start would be appreciated.
| |
| | Read /usr/src/UPDATING.
| |
| Thanks, I missed that.  :(   Sorry for the noise.
|
| ed

I'm building new kernels as I write this.  My next question is:
One of the machines I'm building on is remote and was last rebuilt
just before the change.  What would be be better sequence for making
the change after a fresh cvsup ?

  1. Build and Install a new kernel
  2. build a new world
  3. Run mergemaster
  4. ReBoot (I'm not sure it will come up multiuser with a new
 kernel and a 4 day old userland.)
  5. Installworld and assess possible problems :-)

or

  1. Build and Install a new kernel
  2. make buildworld
  3. Run mergemaster
  4. make installworld; shutdown -r now # and pray :-)

Or is there a better option?

Has anyone else already done this?

Thanks,

ed


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: signal 12's everywhere on Current with update this morning.

2003-11-13 Thread eculp
Mensaje citado por Uwe Laverenz [EMAIL PROTECTED]:

| [EMAIL PROTECTED] schrieb:
|
|  Thanks, I missed that.  :(   Sorry for the noise.
|
| You're not the only one who missed that. We killed 2 machines yesterday
| evening (~11pm CET) this way. I think I did read UPDATING and I can't
| remember any warning entries?! It's there now, of course so we were just
| running cvsup a few hours too early I guess. ;)
|
| Anyway, things like this can happen if you decide to run -CURRENT. :-)

Uwe, do you have any remote machines?  I'm wondering what the correct
sequence would be to update and reboot them.

Thanks,

ed



-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.

2003-11-13 Thread eculp
Mensaje citado por Jesper Skriver [EMAIL PROTECTED]:

| On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote:

CUT

|  I'm building new kernels as I write this.  My next question is:
|  One of the machines I'm building on is remote and was last rebuilt
|  just before the change.  What would be be better sequence for making
|  the change after a fresh cvsup ?
| 
|1. Build and Install a new kernel
|2. build a new world
|3. Run mergemaster
|4. ReBoot (I'm not sure it will come up multiuser with a new
|   kernel and a 4 day old userland.)
|5. Installworld and assess possible problems :-)
|
| I upgraded a ancient -current last night, I did
|
| 1) cvsup
| 2) build and install new kernel
| 3) reboot
| 4) build and isntall new world
| 5) mergemaster
| 6) reboot

Jesper,  Thanks.  I'm already finishing a buildworld but I'm going to
reboot after before installworld, I've already installed the kernel.
I was afraid it would't go multiuser so I could finish with a ssh.

Thanks for confirming that it will, or should :-)

ed
|
| /Jesper
|


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: signal 12's everywhere on Current with update this morning.

2003-11-13 Thread eculp
Mensaje citado por Uwe Laverenz [EMAIL PROTECTED]:

| [EMAIL PROTECTED] schrieb:
|
|  Uwe, do you have any remote machines?  I'm wondering what the correct
|  sequence would be to update and reboot them.
|
| I would suggest to do it this way:
|
| 1. make buildworld
| 2. make kernel KERNCONF=YOURCONF

Uwe, I just inverted the first two but I can always build another
kernel, just in case.

| 3. *reboot* (with new kernel and old userland)

This is the step that I wasn't sure about.  It has to come up in
multiuser so I can access it with ssh.  I don't have a console
access on this machine.

| 4. make installworld
| 5. mergemaster
| 6. *reboot*

Fantastic,  thanks for the confirmation that it will come up with the
old userland.

ed
|
| cu,
| Uwe
|
|
| ___
| [EMAIL PROTECTED] mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-current
| To unsubscribe, send any mail to [EMAIL PROTECTED]
|


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.

2003-11-13 Thread eculp
Mensaje citado por Eric Anderson [EMAIL PROTECTED]:

| I'm not having any luck - I'm started to feel like I'm missing something
| here :)

You're getting signal 11's.  That could indicate memory problems.
I get signal 12's with the changes to the statfs structure.  I assume
that you rebooted after the bombed installworld, didn't you?  If
not that just might be the solution, if you did the problem could be
else where.

ed

|
| I cvsup'd yesterday afternoon, and did my usual make buildworld, kernel,
| install kernel, single user mode, then make installworld - except it
| bombed on the installworld.  I ignored the message moved on.  So, this
| morning, I cvsup'ed again, and started over.
|
| Here's what I get when doing a make buildworld:
| --
|   stage 1.1: legacy release compatibility shims
| --
| snip
| === tools/build
| /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build
| cd /usr/src/tools/build; make buildincludes; make installincludes
| rm -f .depend
| mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include
| /usr/src/tools/build/dummy.c
| cc -O -pipe  -I/usr/obj/usr/src/i386/legacy/usr/include -c
| /usr/src/tools/build/dummy.c
| building static egacy library
| ranlib libegacy.a
| sh /usr/src/tools/install.sh -C -o root -g wheel -m 444   libegacy.a
| /usr/obj/usr/src/i386/legacy/usr/lib
| *** Signal 11
|
| Stop in /usr/src/tools/build.
| *** Error code 1
|
| Stop in /usr/src.
| *** Error code 1
|
| I've tried rm'ing the /usr/obj subdirs, and even moving /usr/src out of
| the way and re cvsuping the whole tree, still no luck..
|
| How am I being stupid here?
|
| Eric
|
|
|
| --
| --
| Eric AndersonSystems Administrator  Centaur Technology
| All generalizations are false, including this one.
| --
|
|
| ___
| [EMAIL PROTECTED] mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-current
| To unsubscribe, send any mail to [EMAIL PROTECTED]
|


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
I'm having problems with current buildworld in gnu now on two different
machines in current(today).  The latest is the following:

rm: tar: is a directory
*** Error code 1

Stop in /usr/src/gnu/usr.bin/tar.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/tar.
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1

I'm begining to wonder if I'm getting a complete checkout with cvsup
of the gnu tree.

Thanks for any suggestions,

ed


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
Mensaje citado por Ruslan Ermilov [EMAIL PROTECTED]:

| On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote:
|  I'm having problems with current buildworld in gnu now on two different
|  machines in current(today).  The latest is the following:
| 
|  rm: tar: is a directory
|  *** Error code 1
| 
|  Stop in /usr/src/gnu/usr.bin/tar.
|  *** Error code 1
| 
|  Stop in /usr/src/gnu/usr.bin/tar.
|  *** Error code 1
| 
|  Stop in /usr/src/gnu/usr.bin.
|  *** Error code 1
| 
|  I'm begining to wonder if I'm getting a complete checkout with cvsup
|  of the gnu tree.
| 
| ``rm -rf /usr/obj/usr/src/gnu/usr.bin/tar'' and try again.

Ruslan

That didn't seem to work.  I've erased the /usr/obj/usr tree several
times and even gnu but without luck.  After resuping getting the
error doing a rm -rf /usr/obj/usr/src/gnu/usr.bin/tar and then
another make buildworld, I continue to get:

=== gnu/usr.bin/tar
rm -f tar addext.o argmatch.o backupfile.o basename.o dirname.o error.o
exclude.o full-write.o getdate.o getline.o getopt.o getopt1.o getstr.o hash.o
human.o mktime.o modechange.o prepargs.o print-copyr.o quotearg.o safe-read.o
save-cwd.o savedir.o unicodeio.o xgetcwd.o xmalloc.o xstrdup.o xstrtoul.o
xstrtoumax.o buffer.o compare.o create.o delete.o extract.o incremen.o list.o
mangle.o misc.o names.o rtapelib.o tar.o update.o tar.1.gz tar.1.cat.gz
rm: tar: is a directory
*** Error code 1

I've actually got two different machines doing the same thing.  At least
I'm consistent :-(

Thanks for your help,

ed


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
Mensaje citado por Jean-Marc Zucconi [EMAIL PROTECTED]:

|  eculp  writes:
|
|   Mensaje citado por Ruslan Ermilov [EMAIL PROTECTED]:
|   | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote:
|   |  I'm having problems with current buildworld in gnu now on two
| different
|   |  machines in current(today).  The latest is the following:
|   | 
|   |  rm: tar: is a directory
|   |  *** Error code 1
|   | 
|   |  Stop in /usr/src/gnu/usr.bin/tar.
|   |  *** Error code 1
|   | 
|   |  Stop in /usr/src/gnu/usr.bin/tar.
|   |  *** Error code 1
|   | 
|   |  Stop in /usr/src/gnu/usr.bin.
|   |  *** Error code 1
|   | 
|   |  I'm begining to wonder if I'm getting a complete checkout with cvsup
|   |  of the gnu tree.
|   | 
|   | ``rm -rf /usr/obj/usr/src/gnu/usr.bin/tar'' and try again.
|
|   Ruslan
|
|   That didn't seem to work.  I've erased the /usr/obj/usr tree several
|   times and even gnu but without luck.  After resuping getting the
|   error doing a rm -rf /usr/obj/usr/src/gnu/usr.bin/tar and then
|   another make buildworld, I continue to get:
|
| Try 'cvs update -PdA'
|
Jean-Marc,

I haven't tried it yet but I think that is the problem.  I just found a
/usr/src/gnu/usr.bin/tar/tar/attic that I suspect as causing problem and that
I'm assuming that the -P would take care of.  I'm trying yet another
make buildworld and it seems to have passed the problem but I am not
declaring victory yet :-) but I feel that this or the -PdA will solve
the problem.

Thanks for the suggestion,

ed


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
Mensaje citado por M. Warner Losh [EMAIL PROTECTED]:

| cvs update -PAd
|
| Pruning is very important.

Warner,

It hadn't even dawned on me but, after several days of suffering with this
problem, I couldn't agree more.  I am converted, believe me.  I will be doing
that more often.  I've become too entrenched with cvsup, I'm afraid.

Thanks very much,

ed

-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


I could have caused error in gnu on current buildworld.

2003-10-31 Thread eculp
A few days ago I lost some files in /usr/src/gnu and erased /usr/src/gnu/*
cvsuped to recover the files and now my build world stops in

sh /usr/src/tools/install.sh -s -o root -g wheel -m 555   strfile
/usr/obj/usr/src/i386/legacy/usr/games
=== gnu/usr.bin/gperf
make: don't know how to make bsd.README. Stop
*** Error code 2

Did I miss something in my cvsup or is there a problem.

Thanks,

ed

-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Release seems to be broken or maybe I missed a change.

2003-08-20 Thread eculp
With cvsup early this morning.  Make release generated

install -o root -g wheel -m 444 rtld.1.gz  /usr/share/man/man1
/usr/share/man/man1/ld-elf.so.1.1.gz - /usr/share/man/man1/rtld.1.gz
/usr/share/man/man1/ld.so.1.gz - /usr/share/man/man1/rtld.1.gz
/usr/libexec/ld-elf.so.1 - /libexec/ld-elf.so.1
ln: /usr/libexec/ld-elf.so.1: Operation not permitted
*** Error code 1

Stop in /usr/src/libexec/rtld-elf.
*** Error code 1

Stop in /usr/src/libexec.
*** Error code 1

Stop in /usr/src.
*** Error code 1

I seem to remember something similar in make world a few days back,

ed

-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Weird reboots from bootmgr or loader

2003-08-14 Thread eculp
Mensaje citado por Florian Smeets [EMAIL PROTECTED]:

| quote who=Lukas Ertl
|  On Tue, 5 Aug 2003, John-Mark Gurney wrote:
| 
|  Are you running -current w/ a kernel from the last 24 hrs?  (After
|  phk's mass swap check in?)  If so, make sure your swap isn't at the
|  start of your disk.  If it is, phk was nice enough to only blow away
|  your boot blocks instead of your disk label too. :)  Swap currently
|  uses all but the first page (4k on i386).
| 
|  Argl, YES, swap _is_ the first partition:
|
| Yes same here!
|
| 
|  Does that mean I have to rearranged or never build world again?
|
| Yeah good question, what can we do ?

I've got the same or a similar problem on my laptop with a new world and
kernel from yesterday.  I can't even boot into freebsd, only windows:-(.
With F3 for FreeBSD it immediately reboots with no visible message.
Windows is the first partition in this case.  Anyone else seeing this?
Maybe I'm just lucky and have another problem ;-)

Thanks for any suggestions,

ed
--


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Bootstrap: Machine keeps booting ? (boot0/mbr) ?

2003-08-06 Thread eculp
Mensaje citado por Stephan van Beerschoten [EMAIL PROTECTED]:

| I just finished installing this brand new -CURRENT box. I haven't been
| on -CURRENt for a while, and thought about having a peek at 5.x.
|
| After installing the machine, it boots up fine for a while, but then
| something strange happends.
| I have not yet been able to determine WHY it happends, much less do I
| know WHAT exactly happends. I hope you can help.
| The only thing I did was to update my 5.1 install to the latest
| -CURRENT. I assume the make world somehow also does something to update
| the bootloader, or is this where I went wrong ?
| Please read on:
|
| I installed the Bootloader for my dualboot machine, and when it comes up
| during boot:
|
| F1 ??
| F2 FreeBSD
|
| and I press F2, it autmatically reboots again. Please note it DID work
| yesterday, but somehow my laptops keeps booting on my now. (-CURRENT ?
| why?)
|
| I am dualbooting with WinXP, and I initially grabbed the first 512bytes
| from /dev/ad0s2c and dumped them on the XP disk, using the NTLoader to
| boot FreeBSD for me. This too worked untill _something_ happened and
| selecting FreeBSD caused the machine to spontaniously reboot too.
|
| Since this happends even before any real kernels are loaded, I cannot
| produce any debug output, so any hints on resolving this issue would be
| greatly appreciated.
|
| Please copy me in on any replies, as I am not yet on -current. I will
| once this problem is fixed :)
|
Stephan,

I have exactly the same problem.  I'm assuming that this was caused by
the changes committed by PHK.  See the [HEADSDOWN] swap_pager.c calming down
and the Weird reboots from bootmgr or loader threads.  He is looking at
it now and will probably be committing a fix.

ed


-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Linux emulation busted

2003-03-24 Thread eculp
Mensaje citado por M. Warner Losh [EMAIL PROTECTED]:

| I had a working Linux world on my laptop.  I upgraded my kernel and
| acroread4 stopped working.  Now all I get is:
| 
| Exited with error code: 0x400e0009.
| 
| after a whole lot of disk access when I try to run it.  This worked on
| a December kernel for sure.  I'm pretty sure it was working as late as
| a January 15th kernel.  It hasn't worked on a March 1st and subsequent
| kernels.  I'm not sure where it broke inbetween.  Has anybody else
| seen this?

Warner,

Both acroread4 and 5 work for me with Mar 21 and Mar 18 kernels with today's
world.  Acroread5 works on another machine with a Mar 10 kernel and today's 
world don't seem to have 4 here.

Hope that helps,

ed

-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: mirrored root fs?

2003-01-07 Thread eculp
Quoting Soeren Schmidt [EMAIL PROTECTED]:

 | It seems Soeren Schmidt wrote:
 | 
 |  It should work on 4.7 forward, but its been a while since I played with
 | it.
 |  Another thing is that its a pain to make a mirror on an already running
 |  system (which is often wanted), so I plan to add an option to atacontrol
 |  to tell where to get the master from, and then do an automatic rebuild
 |  during the create phase ie:
 | 
 |  atacontrol create RAID1 ad0 ad2 source ad0
 | 
 |  This will create a mirror using ad0 and ad2, and start a rebuild to
 |  build the master with data from ad0. This way you can do a normal
 |  install, add a second (identical or bigger) disk, and make a
 |  mirror out of those. You just have to change your fstab before
 |  rebooting (ad0 - ar0) in order to boot...
 | 
 | For those that are brave enough to play with this I just created the
 | following small change to ata-raid.c. Now it will always rebuild the
 | array on creation, using the first disk as the master image. This
 | allows you to turn any set of ATA disks into a mirror on the fly..
 | Remember to rename you filesystems in fstab before booting :)
 | 
 | Index: ata-raid.c
 | ===
 | RCS file: /home/ncvs/src/sys/dev/ata/ata-raid.c,v
 | retrieving revision 1.50
 | diff -u -r1.50 ata-raid.c
 | --- ata-raid.c  2 Oct 2002 07:44:17 -   1.50
 | +++ ata-raid.c  7 Jan 2003 10:02:50 -
 | @@ -374,7 +374,14 @@
 |  rdp-flags |= AR_F_READY;
 | 
 |  ar_table[array] = rdp;
 | +
 | +/* kick off rebuild here */
 | +if (setup-type == 2) {
 | +   rdp-disks[1].flags = ~AR_DF_ONLINE;
 | +   rdp-disks[1].flags |= AR_DF_SPARE;
 | +}
 |  ar_attach_raid(rdp, 1);
 | +ata_raid_rebuild(array);
 |  setup-unit = array;
 |  return 0;
 |  }

Søren,

This is a real temptation.  Let me be sure that I'm understanding 
correctly.  I have an old machine, but running today's current, with only 
one disk, ad0. Could I do the following?

  o- Add ad2
  o- run atacontrol create RAID1 ad0 ad2 source ad0
  o- change ad0s1a to ar0s1a through ad0s1f to ar0s1f in fstab
  o- reboot and enjoy my new mirror.

If ar0 were to die, I would just take it out connect ar2 and boot as ?
I could then do the same with a new mirror, I suppose?

If I'm understanding correctly, I could use any disk  ad0 as the mirror.
Is that correct?  

One last question, what prompted you to preceed the patch with 
For those that are brave enough to play with this, where could
it come back and bit me? :-)

Thanks,

ed


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: mirrored root fs?

2003-01-07 Thread eculp
Quoting Soeren Schmidt [EMAIL PROTECTED]:


 | Doing stuff to your root filesystems is always dangerous, so you
 | have been warned :)
 | 

Thanks, Søren.  Indeed I have:-)  I'll give it a try over the coming 
weekend after backing up everything:).  Will this patch be committed to 
the tree, before then?

This is really great news.  I sometimes feel like I live under a
rock, I didn't realize that atacontrol raid was working so well.  
Do you know of any documentation on setting it up on a new system
install, especially atacontrol RAID1+0?  

I haven't used vinum because of the root partition limitations and 
the complexity of the first configuration although I have been on the
verge several times.  BTW, is this an integration of vinum?  To not 
have to be limited to hw raid by having similar flexibility and ease 
of use with software raid will be/is, IMO, fantastic.

Thanks,

ed


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: mirrored root fs?

2003-01-07 Thread eculp
Quoting Soeren Schmidt [EMAIL PROTECTED]:

 | man atacontrol :)

I did that but it sounded too easy :)  

 | 
 | However if you want to use RAID1+0 and you want to be able to
 | boot from it you *need* a RAID capable controller BIOS, there is
 | no way to make a stock BIOS boot from a RAID0...
 | If you need it on install you probably also need at RAID capable
 | controller, if you define the RAID BIOS there, it will show up
 | in sysinstall..

The solution that pops into my mind is to have a small ad0 for boot 
and / partition. and ad1,ad2,ad3 as raid0+1 or ad1 and 2 as raid1
raid1 should solve my problem.  Would either of these be configurable 
on sysinstall to have the /var and /usr partitions on the raid disks?
If not that should be easy enough after a minimal install and reboot
on ad0.

 | 
 |  I haven't used vinum because of the root partition limitations and
 |  the complexity of the first configuration although I have been on the
 |  verge several times.  BTW, is this an integration of vinum?  To not
 |  have to be limited to hw raid by having similar flexibility and ease
 |  of use with software raid will be/is, IMO, fantastic.
 | 
 | No, the RAID part of the ATA driver has nothing to do with vinum.
 | Vinum has several limitations that make it useless in this context.
 | Mainly that the RAID config layout on disk need to be of different
 | formats depending on what controller BIOS we have, and there is no
 | place to put all the extra volume stuff that vinum needs.
 | The ATA RAID code is very generic instead, with backends that converts
 | the internal RAID info to/from the needed info on disk depending
 | on controller type.

Thanks for the clarification, Søren.  Please forgive my basic, uninitiated
questions.  I really should probably have been paying more attention as 
these features were being added.

ed


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



pcm0:play:0: play interrupt timeout, channel dead

2003-01-02 Thread eculp
Since sometime around Christmas I noticed that sound no longer worked
wiith my new kernels from new worlds.  I can go back to a pre-Christmas
kernel and it works fine.  I thought I might have done something or that
it would work itself out.  I haven't found what I might have done wrong
and it hasn't worked itself out so I wonder if there is anyone else having
issues with maestro3 or similar sound problems?  Are there any ideas for
what I might do to get it working again?

TIA for any help or suggestions,

ed

P.S. General Information.  I don't know what else to send.

My kernel configuration file is Generic with unused drivers commented out.
From todays dmesg with a new world and kernel from yesterday I get:

FreeBSD 5.0-CURRENT #34: Wed Jan  1 06:32:26 PST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIII850
Preloaded elf kernel /boot/kernel/kernel at 0xc042b000.
Preloaded elf module /boot/kernel/snd_maestro3.ko at 0xc042b0bc.
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc042b170.
Preloaded elf module /boot/kernel/acpi.ko at 0xc042b21c.

and

pci0: simple comms at device 9.1 (no driver attached)
pcm0: ESS Technology Allegro-1 port 0x1800-0x18ff irq 5 at device 10.0 on pci0

Then trying to play an mp3 I get
pcm0:play:0: play interrupt timeout, channel dead

/root # kldstat
Id Refs AddressSize Name
 1   12 0xc010 2c42a8   kernel
 21 0xc03c5000 83cc snd_maestro3.ko
 32 0xc03ce000 19a88snd_pcm.ko
 41 0xc03e8000 41f3cacpi.ko
 51 0xc135a000 5000 linprocfs.ko
 61 0xc27d4000 15000linux.ko

-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pcm0:play:0: play interrupt timeout, channel dead

2003-01-02 Thread eculp
Quoting Eric Hodel [EMAIL PROTECTED]:

 | [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
 | 
 |  Since sometime around Christmas I noticed that sound no longer worked
 |  wiith my new kernels from new worlds.  I can go back to a pre-Christmas
 |  kernel and it works fine.  I thought I might have done something or that
 |  it would work itself out.  I haven't found what I might have done wrong
 |  and it hasn't worked itself out so I wonder if there is anyone else having
 |  issues with maestro3 or similar sound problems?  Are there any ideas for
 |  what I might do to get it working again?
 | 
 |  Then trying to play an mp3 I get
 |  pcm0:play:0: play interrupt timeout, channel dead
 | 
 | I get this on -STABLE if I'm playing an mp3, suspend the laptop, then
 | resume it.  If I kill and restart mpg123, it starts playing fine again.
 | I think it has an es1868 in it.
 Eric,

Thanks.  I'm running Current as of cvsup-ed as of a 90 minutes ago.  I also have
a new kernel, clean libraries, includes and system binaries.  With an old -
December 20 kernel - I can play anything that I've tried.  With kernel's since
about December 26 or 27, I can't.  I noticed it first while testing mplayer 
with quicktime.  I was getting a hang with any video that had audio, without
audio it worked great.  Then I started trying mp3, au, etc.

Thanks, again for you observations and help,

ed

-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pcm0:play:0: play interrupt timeout, channel dead

2003-01-02 Thread eculp
Quoting Vladimir [EMAIL PROTECTED]:

 | On Thu, Jan 02, 2003 at 07:47:33AM -0800, [EMAIL PROTECTED] wrote:
 |  Since sometime around Christmas I noticed that sound no longer worked
 |  wiith my new kernels from new worlds.  I can go back to a pre-Christmas
 |  kernel and it works fine.  I thought I might have done something or that
 |  it would work itself out.  I haven't found what I might have done wrong
 |  and it hasn't worked itself out so I wonder if there is anyone else having
 |  issues with maestro3 or similar sound problems?  Are there any ideas for
 |  what I might do to get it working again?
 | 
 |  TIA for any help or suggestions,
 | 
 |  ed
 | 
 | 
 | Try to disable acpi : add following line to /boot/loader.conf
 | hint.acpi.0.disabled=1
 | I have the same problem with sound. Turning off acpi helps.
 | 
Vladimir,

I hadn't thought to try that and it was definitely worth a try.
Unfortunately, it didn't solve the problem.  I thought that it 
might.  It works great with an older, just before Christmas, kernel
and current build.

I am surprised that no one else is seeing it.

Thanks again,

ed
 

-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pcm0:play:0: play interrupt timeout, channel dead

2003-01-02 Thread eculp
Quoting Christian Brueffer [EMAIL PROTECTED]:


 | 
 | Hi,
 | 
 | I'm seeing the same on two boxen here.  The errors seem to have been
 | introduced during the latest pcm locking changes in mid-december.
 | 
 | A src/dev/sound from the beginning of december works fine.

Christian,

Thanks.  At least I'm not alone,  Misery loves company, they say.  I only
have one older kernel and it works fine. [cvsup/world/kernel Dec. 20,2002
+- 4am pst]  Now all we need is a fix :-)

Thanks again,

ed



-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: [PATCH] note the __sF change in src/UPDATING

2002-11-08 Thread eculp
Quoting Brooks Davis [EMAIL PROTECTED]:

 | On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
 |  I'd love for there to be a way to know which binaries use __sF.
 | 
 | The following script run on your bin, sbin, lib, and libexec directories
 | does a pretty decent job of finding files that contain refrences to __sF
 | and listing the ports that use them (depend on portupgrade).
 | 
 | -- Brooks
 | 
 | 
 | #!/bin/sh
 | 
 | sym=__sF
 | 
 | for file in $*; do
 |  if [ -n `nm ${file} 21 | egrep  ${sym}$` ]; then
 |  echo ${file} `pkg_which $file`
 |  fi
 | done
 |

FWIW, while playing with the script I found libc_p.a from today's build.

ed

BTW, I did remove the $ from $*.  I thought it was running too fast :-)



-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Kernel build with cvsup from about 6am pst.

2002-10-28 Thread eculp
This could well be an operator error since I built kernels on two other
machines with cvsup's of about 1 1/2 hours earlier.  I thought I would send
it just in case, while I do a little more investigation.

ed

cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions
-ansi  -nostd
inc -I-  -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica
-I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common 
-mno-align-
long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  vers.c
linking kernel
udbp.o: In function `udbp_attach':
udbp.o(.text+0x36f): undefined reference to `ng_newtype'
udbp.o(.text+0x39c): undefined reference to `ng_make_node_common'
udbp.o(.text+0x3d7): undefined reference to `ng_name_node'
udbp.o(.text+0x411): undefined reference to `dumpnode'
udbp.o(.text+0x42e): undefined reference to `ng_unref_node'
udbp.o(.text+0x478): undefined reference to `dumpnode'
udbp.o: In function `udbp_detach':
udbp.o(.text+0x593): undefined reference to `ng_rmnode_self'
udbp.o(.text+0x5c3): undefined reference to `dumpnode'
udbp.o(.text+0x60e): undefined reference to `dumpnode'
udbp.o(.text+0x62b): undefined reference to `ng_unref_node'
udbp.o: In function `udbp_in_transfer_cb':
udbp.o(.text+0x70b): undefined reference to `ng_package_data'
udbp.o(.text+0x721): undefined reference to `ng_address_hook'
udbp.o(.text+0x73e): undefined reference to `ng_snd_item'
udbp.o: In function `ng_udbp_newhook':
udbp.o(.text+0x972): undefined reference to `dumpnode'
udbp.o(.text+0x9cc): undefined reference to `dumphook'
udbp.o: In function `ng_udbp_rcvmsg':
udbp.o(.text+0xa3b): undefined reference to `dumpnode'
udbp.o(.text+0xab1): undefined reference to `M_NETGRAPH_MSG'
udbp.o(.text+0xb9c): undefined reference to `ng_address_ID'
udbp.o(.text+0xbb9): undefined reference to `ng_snd_item'
udbp.o(.text+0xbdd): undefined reference to `dumpitem'
udbp.o(.text+0xc00): undefined reference to `ng_free_item'
udbp.o(.text+0xc0c): undefined reference to `M_NETGRAPH_MSG'
udbp.o: In function `ng_udbp_rcvdata':
udbp.o(.text+0xc56): undefined reference to `dumphook'
udbp.o(.text+0xc94): undefined reference to `dumpnode'
udbp.o(.text+0xd15): undefined reference to `dumpitem'
udbp.o(.text+0xd38): undefined reference to `ng_free_item'
udbp.o(.text+0xe46): undefined reference to `M_NETGRAPH_META'
udbp.o: In function `ng_udbp_rmnode':
udbp.o(.text+0xe97): undefined reference to `dumpnode'
udbp.o(.text+0x1026): undefined reference to `dumpnode'
udbp.o(.text+0x1043): undefined reference to `ng_unref_node'
udbp.o(.text+0x1053): undefined reference to `ng_make_node_common'
udbp.o(.text+0x1084): undefined reference to `ng_name_node'
udbp.o(.text+0x10be): undefined reference to `dumpnode'
udbp.o(.text+0x10e1): undefined reference to `ng_unref_node'
udbp.o(.text+0x1124): undefined reference to `dumpnode'
udbp.o: In function `ng_udbp_connect':
udbp.o(.text+0x117f): undefined reference to `dumphook'
udbp.o(.text+0x11ba): undefined reference to `dumphook'
udbp.o: In function `ng_udbp_disconnect':
udbp.o(.text+0x120e): undefined reference to `dumphook'
udbp.o(.text+0x124c): undefined reference to `dumpnode'
udbp.o(.text+0x1296): undefined reference to `dumphook'
udbp.o(.text+0x12d4): undefined reference to `dumpnode'
udbp.o(.text+0x131e): undefined reference to `dumphook'
udbp.o(.text+0x135c): undefined reference to `dumpnode'
udbp.o(.text+0x13a9): undefined reference to `dumphook'
udbp.o(.text+0x13c2): undefined reference to `ng_rmnode_self'
udbp.o(.rodata+0x24): undefined reference to `ng_parse_int32_type'
udbp.o(.rodata+0x30): undefined reference to `ng_parse_int32_type'
udbp.o(.rodata+0x44): undefined reference to `ng_parse_struct_type'
udbp.o(.rodata+0xa0): undefined reference to `ng_parse_int32_type'
*** Error code 1



-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 5.0-20021027-CURRENT.iso cdrom will not mount

2002-10-28 Thread eculp
Quoting John [EMAIL PROTECTED]:

 | - Makoto Matsushita's Original Message -
 | 
 |  jwdThe iso(s) boot correctly and sysinstall works fine. The disks
 |  jwd are formated and newfs'd correctly. However, when sysinstall
 |  jwd tries to mount the cdrom, the following error is received:
 | 
 |  jwd Error mounting /dev/acd0c on /dist: Operation not supported by device
 | (19).
 | 
 |  Which type of machine did you try?  I've heard exactly the same error
 |  on the VMware's virtual machine.
 | 
 |Abit kr7a motherboard, asus cd (plus two others which didn't
 | work). This machine boots a 4.7 iso with no problems.
 | 
 |How many other people are testing the 5.0 sysinstall booted
 | from a cd and running a local (cd/dvd) install? Try booting and
 | installing from the iso at usw2.freebsd.org and see if it works
 | for you.

I'd love to but usw2.freebsd.org seems to be restricted.  I've got 
the same problem that I can't mount any release built last week.  I 
suppose I should go to a pre GEOM kernel for an install or what would
be a better solution?

Thanks,

ed

 | 
 | Thanks,
 | -John
 | 
 |  -- -
 |  Makoto `MAR' Matsushita
 | 
 | To Unsubscribe: send mail to [EMAIL PROTECTED]
 | with unsubscribe freebsd-current in the body of the message
 | 


-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)

2002-10-27 Thread eculp
Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]:

 | Quoting Nate Lawson [EMAIL PROTECTED]:
 | 
 | SNAP
 | 
 |  |
 |  | I checked again and my commit had missed the burncd speed conversion.  I
 |  | just committed it -- rev 1.28 burncd.c.  Sorry about this.  CVSUP,
 | rebuild
 |  | burncd, and let me know if there are further problems.
 |  |

Nate, Thanks again.  Burncd now works as expected with -s.  BTW, the -s now
seems to be required and no longer optional.

ed

-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



burncd: ioctl(CDRIOCWRITESPEED): Input/output error

2002-10-26 Thread eculp
With current from yesterday, I get the following error when trying to
burn a cd.  I haven't burned one for probably a month or maybe more.
If I remove the -s, the results are the same.

Does anyone have a suggestion, fix or work around?

 # burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate
burncd: ioctl(CDRIOCWRITESPEED): Input/output error

Thanks,

ed

-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: you need to install a new kernel before an installworld.

2002-10-26 Thread eculp
Quoting Tim Kientzle [EMAIL PROTECTED]:

 | Peter Wemm wrote:
 | 
 |  'make installworld' without ... a new kernel would be rather messy.
 | 
 |  ... a reminder of the sequence is probably in order:
 |   buildworld
 |   buildkernel
 |   installkernel
 |   reboot
 |   installworld
 |   reboot
 | 
 | 
 | This _does_not_work_ because 'installkernel' does
 | not update the bootblocks.  It should.  Otherwise,
 | 'installkernel' is not filling it's contract: it is
 | not ensuring that the next boot uses the new kernel.
 | 
It has worked for me this morning.  I seem to have successfully
installed and rebooted 3 vastly different machines.  Laptop,
desktop and a scsi, raid10, server, with no noticable problems.

Now you've made me very nervious ;-)

ed

 | An alternative: have installkernel link the new kernel
 | file back to the old location, at least until 5.1.
 | That way, either old or new boot blocks would boot
 | the new kernel.  (This may be the better approach
 | all around; it leaves the downgrade option available
 | for a little bit longer.)
 | 
 | Tim Kientzle
 | 
 | 
 | 
 | 
 | To Unsubscribe: send mail to [EMAIL PROTECTED]
 | with unsubscribe freebsd-current in the body of the message
 | 


-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)

2002-10-26 Thread eculp
Quoting Nate Lawson [EMAIL PROTECTED]:

 | On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote:
 |  With current from yesterday, I get the following error when trying to
 |  burn a cd.  I haven't burned one for probably a month or maybe more.
 |  If I remove the -s, the results are the same.
 | 
 |  Does anyone have a suggestion, fix or work around?
 | 
 |   # burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate
 |  burncd: ioctl(CDRIOCWRITESPEED): Input/output error
 | 
 |  Thanks,
 | 
 |  ed
 | 
 | I've changed the subject since I guess a HEADSUP may be necessary.
 | 
 | Try rebuilding burncd.  The CDRIOC*SPEED api was changed to allow the user
 | application to send raw KB/s values whereas before the ioctl took in
 | speeds in multiples of a 1X CDROM (1 = 177KB/s, 2 = 354KB/s, ...)  This
 | was necessary to allow the user app to specify a speed of CDR_MAX_SPEED,
 | which means the drive should choose its highest speed.

Nate,

Thanks, for the input.  I've still got a problem that I'm going to check.
My version was cvsuped and built this morning following Peter's 
instructions in his HEADS UP email.  That is when I saw the problem.  
I was going to burn releases that I had made this past week
just in case :-)

/root # ls -l `which burncd`
-r-xr-xr-x  1 root  wheel  18228 Oct 26 11:11 /usr/sbin/burncd

/var/tmp # uname -a
FreeBSD worldinternet.org 5.0-CURRENT FreeBSD 5.0-CURRENT #31: Sat Oct 26
07:12:23 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIII850N  i386
worldinternet.org:

Thanks,

ed


 | 
 | The new versions of cdcontrol and burncd do the translation the kernel
 | used to do so you can still specify flags the same as you always have
 | (i.e. -s 1 like you are doing).
 | 
 | -Nate
 | 
 | 
 | To Unsubscribe: send mail to [EMAIL PROTECTED]
 | with unsubscribe freebsd-current in the body of the message
 | 


-- 


-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)

2002-10-26 Thread eculp
Quoting Nate Lawson [EMAIL PROTECTED]:

SNAP

 | 
 | I checked again and my commit had missed the burncd speed conversion.  I
 | just committed it -- rev 1.28 burncd.c.  Sorry about this.  CVSUP, rebuild
 | burncd, and let me know if there are further problems.
 | 
Thanks, Nate.  Please ignore my previous email.  I hadn't seen this one.
I'm cvsuping now.  I'll let you know if it doesn't work, tomorrow.

Thanks again,

ed

-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: loader problem

2002-10-07 Thread eculp

Quoting Lars Eggert [EMAIL PROTECTED]:

 | Hi,
 | 
 | after an installworld with last night's sources, my machine resets in
 | the the loader. It prints the BTX loader line, and then immediately
 | resets. I restored the old /boot/loader (from 10/2), which lets me boot
 | again.
 | 
 | Any ideas?
 | 
I just had the same thing happen.

ed

-

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



compile errors after yesterdays cvsup and makeworld.

2002-02-21 Thread eculp

I sure missed something, I'm sorry.  I still have the problem with
buildworld.  What should I do to fix it?  

# /usr/bin/cc -print-search-dirs
install: /usr/libexec/(null)
programs: /usr/libexec/elf/
libraries: /usr/lib/

Thanks,

ed

Quoting Edwin Culp [EMAIL PROTECTED]:

 David,
 
 I see it's already fixed so I'll assume that you no longer need the 
 compiler output.  I'm sorry that I didn't answer before but I just
 checked my email and went to some meetings and am just getting back.
 
 Thanks for your help,
 
 ed
 
 Quoting David O'Brien [EMAIL PROTECTED]:
 
  On Wed, Feb 20, 2002 at 05:53:59AM -0800, Edwin Culp wrote:
   On my daily build, my kernels are broken as per log:
   
   === wi
   cd /usr/obj/usr/src/sys/PIII850N; 
  MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm 
   make -
   f /usr/src/sys/dev/aic7xxx/aicasm/Makefile
   Warning: Object directory not changed from original
  /usr/obj/usr/src/sys/PIII850N
   cc -O -pipe  -I/usr/include -I.-c aicasm_gram.c
   cc: installation problem, cannot exec `cpp0': No such file or directory
   cc: installation problem, cannot exec `cc1': No such file or directory
   *** Error code 1
  
  
  I need to see the output of ``/usr/bin/cc -print-search-dirs'' from the
  problematic compiler.
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message
  
 
 
 -- 
 To announce that there must be no criticism of the president,
 or that we are to stand by the president, right or wrong, is not
 only unpatriotic and servile, but is morally treasonable to
 the American public.  - Theodore Roosevelt
 
 
 
 ---
 




-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message