Re: pkg/port dependency tool (enclosed)
On Mon, Apr 23, 2001 at 12:54:52PM -0400, Walter Campbell wrote: > On Mon, 23 Apr 2001, Jeff Kletsky wrote: > > to dependencies, and am offering back to the project a Perl script that > > provides output that can be run through dot(1) (available in the port > > graphics/graphviz) to produce a dependency graph. > > graphviz depends on X11. What I had to do was take an older version > of graphviz, strip out the X stuff, and only build the two tools I > need, dot and neato. If a FreeBSD port is available to do that and > that alone, without requiring X, I will be incredibly happy, and > willing to upgrade my (slightly buggy) graphviz installation. I was talking to the at&t people recently, and all the patches the current freebsd port applies in order to make the build work on freebsd have now been rolled into their CVS repository; so, if you check out a current set of sources (see www.graphviz.org for details) you should get something that compiles smoothly on freebsd. I meant to ask them whether they might like to roll another release with those patches in so that I could update the freebsd port, but I forgot. I will do that. Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sdl breakage? (was Re: pkg/port dependency tool (enclosed))
On Mon, Apr 23, 2001 at 10:48:23AM -0500, Mike Meyer wrote: > Very cool idea, but the graphviz port doesn't build on 4.3-STABLE, > failing with > > ===> Applying FreeBSD patches for graphviz-1.7c > aclocal: /usr/opt/share/aclocal/sdl11.m4: 11: duplicated macro `AM_PATH_SDL' > *** Error code 1 > > :-(. what i did to fix this, was to edit .../aclocal/sdl.m4 , and rename `AM_PATH_SDL' `__AM_PATH_SDL' or such like. -- Ceri Storey <[EMAIL PROTECTED]> http://pkl.net/~cez/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stable breaks acroread port
Mike Meyer wrote: > > Kenneth Ingham <[EMAIL PROTECTED]> types: > > I was running acroread fine from the ports for months: > > acroread4-4.05 View, distribute and print PDF documents > > I've been running it for quite some time. In fact, I'm running it now > to view and print PDF documents. My system was updated on the > yesterday - the 22nd. It was also updated the 15th, and I probably > used it at least once in the interim. > > > On 4/13, I upgraded to 4.2-STABLE, and this broke acroread. I > > upgraded again 4/18 (this time 4.3-RC), hoping it would solve the > > problem, but no go. I noticed that the port did not change either > > time. > > Upgrading the system won't update the port, unless you're updating the > ports tree at the same time. > > > The problem is that acroread dies with the following (wonderfully > > helpful, thanks Adobe) error message: > > Exited with error code: 0x400e0009. > > > > It's not Linux emulation that is broken, because other Linux programs > > still run fine (e.g. StarOffice, Netscape, etc). > > > > Any ideas? > > Did you change anything else while doing the update? Kernel, maybe? > Did you reinstall acroread at some point? > Same problem... did a build/installworld on several machines yesterday and it hangs on all on the splash screen. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
REGISTRE EL SUYO
Si tiene una empresa en marcha, un proyecto o una idea registre su dominio en Internet AHORA, tal vez mañana sea demasiado tarde. Proteja su nombre en Internet. Si tiene ya dominio y ha de renovarlo proximamente transfiera el dominio por solo 20$ lo tendra un año renovado (esta operacion no afecta al hospedaje, solo al registrador del dominio) Si conoce a alguien en esta situacion y no sabe que regalarle regalele un dominio, es original y quedara bien. Vea toda la informacion referente al registro de dominios en http://www.brand.es.vg REGALE UN DOMINIO O REGISTRE EL SUYO Otros servicios: hospedaje, redireccion de dominio, ...etc ¿HAS DE RENOVAR EL REGISTRO DE TU DOMINIO? PRECIO ESPECIAL POR TRANSFERENCIA DE DOMINIO (20$ AÑO) PRECIO DE HOSTING IMBATIBLE ---REMOVE-- SI NO QUIERE RECIBIR MAS MENSAJES DESDE ESTA DIRECCION VAYA AL LINK INDICADO Y SERA DADO DE BAJA INMEDIATAMENTE. DICHO LINK ES UN SERVICIO INDEPENDIENTE DEL ENVIO DE ESTE EMAIL -- dar de baja de la lista de distribucion - remove distribution list http://borrame.anexos.com RemovingNet. Cuentas gratuitas para el control de bajas. Free accounts for the control of "unsubscribes" RemovingNet nada tiene que ver con este email ni con su contenido RemovingNet nothing has to do with this email nor with contained his IF YOU DON'T WANT TO RECEIVE MORE MESSAGES FROM US, PLEASE CLICK ON THE LINK BELOW. http://borrame.anexos.com YOUR EMAIL ADDRESS WILL BE REMOVED FROM OUR DATA BASE IMMEDIATELY. REMOVING.NET IS AN INDEPENDENT SERVICE ---REMOVE-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
vinum configuration
After upgrading to 4.3 from 4.2 my vinum configuration seems to have stopped working. this is my vinum.conf file: drive vinumdrive0 device /dev/ad2c drive vinumdrive1 device /dev/ad3c volume vimum0 plex name vinum0.p0 org concat sd name vinum0.p0.s0 drive vinumdrive0 size 0 sd name vinum0.p0.s1 drive vinumdrive1 size 0 After trying numerous times to read the drives: # vinum read /dev/ad2c /dev/ad3c Apr 23 13:41:07 slumber /kernel: vinum: no drives found I've even got as far as to redo the configurtion: vinum create -f /etc/vinum.conf but i get: 1: drive vinumdrive0 device /dev/ad2c ** 1 Can't initialize drive vinumdrive0: Inappropriate ioctl for device 2: drive vinumdrive1 device /dev/ad3c ** 2 Can't initialize drive vinumdrive1: Inappropriate ioctl for device Both drives are there and seem fine, only other odd behavior is.. su-2.03# disklabel /dev/ad3c # /dev/ad3c: type: ESDI disk: ad3s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 59597 sectors/unit: 60074721 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 600747210 vinum# (Cyl.0 - 59597*) Warning, partition c is not marked as unused! Warning, An incorrect partition c may cause problems for standard system utilities This error message appears on both drives. I dont recall seeing this msg before when I setup vinum, but I also dont think its a bad drive when both started doing it at the same time. Am i doing something wrong? I've had this working fine for about a year now and never had problems upgrading, this 4.3 release seems to have broke it but I cant say I know why. I apologize if there is not enough information, i'll be glad to include any additional information needed. Thanks. -- Shawn Ostapuk Senior UNIX System Administrator Inficad Communications PGP signature
RE: vinum configuration
Partition c represents the whole harddisk and should be used for any file system. Using disklabel create a partition a with fstype vinum and change your vinum.conf to use /dev/ad2a and /dev/ad3a For me it is still working in 4.2-STABLE I got last week Vinesh > -Original Message- > From: Shawn Ostapuk [SMTP:[EMAIL PROTECTED]] > Sent: Monday, April 23, 2001 3:47 PM > To: [EMAIL PROTECTED] > Subject: vinum configuration > > After upgrading to 4.3 from 4.2 my vinum configuration seems > to have stopped working. > > > this is my vinum.conf file: > > drive vinumdrive0 device /dev/ad2c > drive vinumdrive1 device /dev/ad3c > volume vimum0 > plex name vinum0.p0 org concat >sd name vinum0.p0.s0 drive vinumdrive0 size 0 >sd name vinum0.p0.s1 drive vinumdrive1 size 0 > > > > After trying numerous times to read the drives: > > # vinum read /dev/ad2c /dev/ad3c > Apr 23 13:41:07 slumber /kernel: vinum: no drives found > > > I've even got as far as to redo the configurtion: > > vinum create -f /etc/vinum.conf > > but i get: > > >1: drive vinumdrive0 device /dev/ad2c > ** 1 Can't initialize drive vinumdrive0: Inappropriate ioctl for device >2: drive vinumdrive1 device /dev/ad3c > ** 2 Can't initialize drive vinumdrive1: Inappropriate ioctl for device > > > Both drives are there and seem fine, only other odd behavior is.. > > su-2.03# disklabel /dev/ad3c > # /dev/ad3c: > type: ESDI > disk: ad3s1 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 16 > sectors/cylinder: 1008 > cylinders: 59597 > sectors/unit: 60074721 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0# milliseconds > drivedata: 0 > > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > c: 600747210 vinum # (Cyl.0 - > 59597*) > Warning, partition c is not marked as unused! > Warning, An incorrect partition c may cause problems for standard system > utilities > > > This error message appears on both drives. I dont recall seeing this msg > before when > I setup vinum, but I also dont think its a bad drive when both started > doing it at > the same time. > > > Am i doing something wrong? I've had this working fine for about a year > now and never had > problems upgrading, this 4.3 release seems to have broke it but I cant say > I know why. > > I apologize if there is not enough information, i'll be glad to include > any additional > information needed. Thanks. > -- > > Shawn Ostapuk > Senior UNIX System Administrator > Inficad Communications To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: slight perl IO::Socket weirdness after cvsup & buildworld 4.3RC1 -> RC5
On Fri, Apr 20, 2001 at 09:22:19AM -0400, Jay Sachs wrote: > Everything was fine under RC1, and two days ago I successfully upgraded > again from RC1 -> RC5. > Poking around in /usr/libdata/perl, I noticed the following: > > thelonius% cd /usr/libdata/perl/5.00503/mach/IO > thelonius% ls -la Socket* > -r--r--r-- 1 root wheel 16948 May 2 1999 Socket.pm > > Socket: > total 15 > drwxr-xr-x 2 root wheel 512 Mar 16 16:58 ./ > drwxr-xr-x 3 root wheel 512 Apr 19 14:44 ../ > -r--r--r-- 1 root wheel 9570 May 20 1998 INET.pm > -r--r--r-- 1 root wheel 3015 Mar 18 1998 UNIX.pm > > Unfortunately I don't know what it looked like before, but this is > definitely different than my 4.2-STABLE box at home, where the Socket > subdirectory and related files do NOT exist. > > Any clues on this one? Yes. You have installed IO-1.20 on the machine in question. You did that using CPAN, instead of using FreeBSD port devel/p5-IO, which DTRT. Your 4.2-STABLE machine does not have this problem because you have not installed IO-1.20 on it. FreeBSD 4.X, including 4.3, does not have the files you mention in the base system. Cheers, +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
addition to /usr/src/sys/pci
Everytime I cvsup and recompile my kernel I have to remember to add lines to /usr/src/sys/pci referring to my Tekram dc390 and dc395 devices. How can I make this reference permanent? Thanks in advannce, Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sdl breakage? (was Re: pkg/port dependency tool (enclosed))
Ceri Storey <[EMAIL PROTECTED]> types: > On Mon, Apr 23, 2001 at 10:48:23AM -0500, Mike Meyer wrote: > > Very cool idea, but the graphviz port doesn't build on 4.3-STABLE, > > failing with > > > > ===> Applying FreeBSD patches for graphviz-1.7c > > aclocal: /usr/opt/share/aclocal/sdl11.m4: 11: duplicated macro `AM_PATH_SDL' > > *** Error code 1 > > > > :-(. > what i did to fix this, was to edit .../aclocal/sdl.m4 , and rename `AM_PATH_SDL' >`__AM_PATH_SDL' or such like. Well, that solved that problem. Now it's dieing because it can't find the freetype.h include file. Probably because the thing moved going from XFree86-3 to XFree86-4. It seems you need to include freetype/freetype.h. Maybe I'll just try grabbing the sources from AT&T. Thanx, http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: addition to /usr/src/sys/pci
* s <[EMAIL PROTECTED]> [010423 13:58] wrote: > Everytime I cvsup and recompile my kernel I have to remember to > add lines to /usr/src/sys/pci referring to my Tekram dc390 and > dc395 devices. How can I make this reference permanent? Send us the change you're making and it'll most likely wind up in the sources. :) Use the 'diff' utility with the '-u' option to make the diff file we'll need. -- -Alfred Perlstein - [[EMAIL PROTECTED]] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
dumpdev for twed ?
Hi,
Does the twe device support dumpon ? Or is it just
/dev/{ad,da}?s?b standard swap areas ?
---Mike
Mike Tancsa, tel +1 519 651 3400
Network Administration, [EMAIL PROTECTED]
Sentex Communications www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
/boot/boot0 or boot1 bad?
I did a binary upgrade from 3.5 to 4.3-RELEASE using floppies and ftp. The upgrade went fine, but I had a bad idea, and decided to upgrade my sources via cvsup. Here is my present situation/problem: When booting from HD, I use a boot manager (Win98, OS/2, FreeBSD), and go to FreeBSD. About 1 second after clicking FreeBSD, there appears a single line of about 14 characters of gibberish at the bottom left of my monitor. It doesn't lock-up the keyboard, but I can't get anything to happen either. The Num Lock, Caps Lock, and Scroll Lock keys all work. Anyway, I hit C-A-D, and reboot with the kern.flp disk. As soon as the "baton" shows, I hit the space bar and type "0:ad(0,a)kernel" and FreeBSD boots from the HD just fine. Everything is mounted, all programs run, I can log in as a normal user and root. Everything is there and looks/runs great. If I understand correctly, /boot/boot0 and /boot/boot1 are the first files "read". Did I damage one of those files or perhaps a different partition on my FreeBSD slice is being pointed to to boot? Can it be repaired? No, I don't have a back-up... no room to spare :( BTW- /etc/fstab and ls -l /dev |grep ad0 show the same devices (if that helps) TIA, Mike __ I use: FreeBSD 4.2, L-M 7.2, OS/2 Warp3&4, Amiga 4000 ICQ #54186124 BP40MM May God bless you abundantly __ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
top and ps broken
I was running 4.1 for a while, I updated all my sources using cvs, and did a make world. after I did this, top and ps stopped working. This is what I get now: %top kvm_open: proc size mismatch (37728 total, 1056 chunks) top: Out of memory. ps: proc size mismatch (28296 total, 1056 chunks) Does anyone know what this means? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: top and ps broken
On Mon, Apr 23, 2001 at 07:41:31PM -0400, Roy Shimmyo wrote: > I was running 4.1 for a while, I updated all my sources using cvs, and did > a make world. after I did this, top and ps stopped working. This is what I > get now: > > %top > kvm_open: proc size mismatch (37728 total, 1056 chunks) > top: Out of memory. > > ps: proc size mismatch (28296 total, 1056 chunks) > > Does anyone know what this means? It means your kernel and userland are out of sync. Did you compile a new kernel in conjunction with the make world? See /usr/src/UPDATING for the latest instructions on keeping your system up to date. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
