Problems building JDK 1.4
I am trying to build java/jdk14 with portupgrade, and I have run into a problem. After downloading all the necessary patches and the j2sdk binaries and src files from Sun, I ran the following: portupgrade --new java/jdk14 Things went along fine for about 2 hours, and then wham I get the following error: Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location /usr/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java/util/CurrencyData.java:1: 'class' or 'interface' expected Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location ^ /usr/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java/util/CurrencyData.java:1: unclosed character literal Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location ^ 2 errors gmake[4]: *** [.compile.classlist] Error 1 gmake[4]: Leaving directory `/usr/ports/java/jdk14/work/j2se/make/java/java' gmake[3]: *** [optimized] Error 2 gmake[3]: Leaving directory `/usr/ports/java/jdk14/work/j2se/make/java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk14/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk14/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk14. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade8248.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! java/jdk14(unknown build error) I did some searching and noticed that someone else posted the exact same problem a couple weeks ago, but unfortunately no one replied to his problem. Has anyone solved this, or know what I should do to fix the problem? Here's some more info that may be helpful: port: jdk-1.4.2p6_4 uname -mp: 5.1-RELEASE-p2 i386 Thanks for any help, Chris p.s. sorry for the long lines in the error signature.asc Description: This is a digitally signed message part
Re: Jail setup
On Fri, 2004-03-05 at 00:57, Harald Schmalzbauer wrote: ...cut... Things seem to be fine. I can see the jailed environment and everything looks fine. I log out and then try to set up the last configuations so I can ssh in and run sendmail. In the non-jail /etc/rc.conf I added the following lines: ifconfig_fxp0_alias0=10.0.0.203 netmask 255.255.255.0 This is wrong. The jail can only have one IP so netmask has to be 0x (255.255.255.255) Do you have something like this on the host? fconfig_fxp0=inet 10.0.0.202 netmask 0xff00 #host ifconfig_fxp_alias0=inet 10.0.0.203 netmask 0x#jail 1 ...cut again... Change the IP like I wrote above and everything should be fine. -Harry This all worked (thank you Harry), but now I have a slightly different problem. I can ssh to the jail, but I get the following message: Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. You can use the 'fetch' command to retrieve files over ftp or http. fetch http://www.freebsd.org/index.html will download the front page of the FreeBSD web site. I figured this had something to do with my MAKEDEV problem so after re-reading the jail manpage (thanks albi) I found the following: mount_devfs devfs /usr/jail/dev Now I can ssh to the 10.0.0.203 address without problem. This is OK, but not ideal. I am wondering if there is something I need to do to set up the devfs in the jail permanantly, or do I have to run the mount_devfs command every time I start the jail. I was planning on writing a /usr/local/etc/rc.d shell script to start the jail on boot up anyway, so adding the mount command to that isn't a big deal, I was just wondering if there was another way. Thanks, Chris signature.asc Description: This is a digitally signed message part
Jail setup
I need to set up a new mail server at a different building, so I thought I would put sendmail and its services (virus scanning etc.) in a jail to be a bit more secure. I thought that before I do this for real I would try setting up a jail on a test server and see if I can ssh to it and generally get things to work. I can't. Here's what I have set up so far. I found a couple how-tos and I am following them; one is an ONLamp article (http://www.onlamp.com/pub/a/bsd/2003/09/04/jails.html), and the other is the jails section of the AbsoluteBSD book. I am running 5.1. On the server I set up a /usr/jail directory to put the jail into. Then I ran the following from /usr/src/: # make world DESTDIR=/usr/jail # cd etc # make distribution DESTDIR=/usr/jail # cd /usr/jail/dev # sh MAKEDEV jail This is where I had my first problem, MAKEDEV doesn't exist. At first I was a bit concerned about this, then I remembered that in 5.0 and above MAKEDEV isn't necessary, it is handled by the kernel (If that isn't right someone please tell me). I didn't worry about this. Next I ran: # cd ../ # ln -sf /dev/null kernel Then I started my jail: #jail /usr/jail jail.myhost.com 10.0.0.203 /bin/sh Things seem to be fine. I can see the jailed environment and everything looks fine. I log out and then try to set up the last configuations so I can ssh in and run sendmail. In the non-jail /etc/rc.conf I added the following lines: ifconfig_fxp0_alias0=10.0.0.203 netmask 255.255.255.0 sendmail_enable=NONE inetd_flags=-wW -a 10.0.0.202 I also added ListenAddress 10.0.0.202 to /etc/ssh/sshd_config. In the jail's /etc/rc.conf (i.e. /usr/jail/etc/rc.conf) I added: portmap_enable=NO ifconfig_fxp0=inet 10.0.0.203 netmask 255.255.255.0 sendmail_enable=YES sshd_enable=YES and added ListenAddress 10.0.0.203 to /usr/jail/etc/ssh/sshd_config I then rebooted to shut all services down. When the system was back up and running I ran the commands to mount and start the jail: # mount -t procfs proc /usr/jail/proc # jail /usr/jail jail.myhost.com 10.0.0.203 /bin/sh /etc/rc Things seem to boot fine until it gets to sendmail; it seems to hang there (sshd starts fine though). Eventually sendmail times out and I get a prompt. I figure my jail is running (minus sendmail which I don't care about at the moment), and a ps -ax|grep J shows a few jailed processes running including sshd. From another system I try: % ssh 10.0.0.203 and I get nothing. I can ping 10.0.0.203 just fine (as well as 10.0.0.202). A sockstat -4 shows: root sshd 3041 3 tcp4 10.0.0.203:22 *:* root syslogd2908 4 udp4 10.0.0.203:514*:* root sshd 2650 3 tcp4 10.0.0.202:22 *:* so it seems like sshd is listening on 10.0.0.202 and 203. I can ssh to 202 without problem, I just can't get into the jail. Can anybody tell me where I screwed up, or other things to look for. Any help would be appreciated. Thanks, Chris signature.asc Description: This is a digitally signed message part
Re: Does anybody installed DVD Rom on FreeBSD 4.9?
On Wed, 2004-02-25 at 11:15, Carla Neves wrote: Hi dear FreeBSD users, I would like to install a DVD R+W on my Proliant Ml330 for backups purposes. Before I buy the DVD Rom, I would like to know if someone has done that before with success for FreeBSD 4.9. I checked on freebsd sites that there is a SW for FreeBSD 4.9, called, used for burning DVDs and it is compatible with several DVD R+W providers. Anyway, I would like to know if I need something more besides this SW, like: DVD drivers, Kernel configurations... Thanks in advance for your help CG I have used a DVD burner for saving backups for a couple months now and it works fine. The burner I have is a generic Memorex DVD+RW model. There are a couple steps that you will need to go through before being able to burn discs with your drive (at least I had to go through these steps). First you will need to add a line to your kernel conf file and recompile. The line to add is: device atapicam Next you will need to install sysutils/dvd+rw-tools. This will give you some command line dvd authoring tools, the most useful of the bunch is growisofs. The man page for growisofs is good, probably a bit too good for general backups. The basic command you need to run is: growisofs -Z /dev/cd0 -R -J path/to/directory_or_file The -R and -J aren't strictly necessary. Also the device, will more than likely not match what dmesg lists for your dvd drive. For me dmesg shows the following for my drive: acd0: DVD-R Memorex DVD+/-RW Dual-X1 at ata1-master PIO4 However the atapicam device in your recompiled kernel does some SCSI emulation (or something like that) and the cd0 device is necessary for the growisofs command (of course your drive may be cd1 or cd2 rather than 0 depending on your hardware). One final note. I have not had any luck getting growisofs to work with files over 2GB. Growisofs relies on mkisofs which has been giving me problems with large files. I eventually removed the standard version of mkisofs and replaced it with mkisofs-devel, and that will happily work on files larger than 2GB. Now when I use growisofs it goes through the whole process without any errors, but when I try to read the disc I get errors about the file being too large. If anyone has any suggestions to get around this issue I would be grateful. Hope this helps, Chris signature.asc Description: This is a digitally signed message part
Re: mkisofs vs large files
Replying to myself here in the hopes that someone who can help didn't see this the first time I posted. Any help to the below problem would be appreciated. Thanks, Chris On Wed, 2004-02-18 at 10:47, Chris Meyers wrote: I am running 5.1-RELEASE-p2 with dvd+rw-tools version 5.17.4.8.6 and mkisofs version 2.0.3_1 and I'm having some problems with mkisofs and files larger than 2GB. Basically what I am trying to do is backup some database dumps to a dvd. Everything was working fine until the dumps got larger than 2 Gigs. Now I get this message when I try to use growisofs: % growisofs -dry-run -Z /dev/cd0 -R -J bkupdir Executing 'mkisofs -R -J feb8 | builtin_dd of=/dev/pass0 obs=32k seek=0' mkisofs: Value too large to be stored in data type. File bkupdir/large-file-20040208.sql.gz is too large - ignoring Total translation table size: 0 Total rockridge attributes bytes: 169 Total directory bytes: 0 Path table size(bytes): 10 I have looked around and found some articles and emails that say the mkisofs has a 2 gig limit in some circumstances, but I have also seen articles and emails that say this shouldn't be the case on FreeBSD or when dvd+rw-tools is installed. The man page for mkisofs gives a -split-output option which I tried in hopes that it would split the file as necessary, but I got the same error. Anyone have any clues or advice? Thanks, Chris signature.asc Description: This is a digitally signed message part
Re: quick mozilla question
On Fri, 2004-02-20 at 10:29, jr315 wrote: running freeBSD 5.2 release. installed mozilla from packages. When I try to run I get the following message: sh# mozilla /libexec/ld-elf.so.1: Shared object libintl.so.5 not found /libexec/ld-elf.so.1: Shared object libintl.so.5 not found any ideas Someone here had the exact same error the other day. The problem was gettext had been updated, but the ports/packages that depended on it (pretty much everything) hadn't. So gettext updated libintl.so.5 to libintl.so.6 so mozilla and gvim and evolution and almost everything complained with the same error you are seeing. I'm not sure if this is your problem. Since you installed mozilla from packages rather than ports it may be. The package may have been built with the older version of gettext. A portupgrade mozilla may solve the problem. Chris signature.asc Description: This is a digitally signed message part
mkisofs vs large files
I am running 5.1-RELEASE-p2 with dvd+rw-tools version 5.17.4.8.6 and mkisofs version 2.0.3_1 and I'm having some problems with mkisofs and files larger than 2GB. Basically what I am trying to do is backup some database dumps to a dvd. Everything was working fine until the dumps got larger than 2 Gigs. Now I get this message when I try to use growisofs: % growisofs -dry-run -Z /dev/cd0 -R -J bkupdir Executing 'mkisofs -R -J feb8 | builtin_dd of=/dev/pass0 obs=32k seek=0' mkisofs: Value too large to be stored in data type. File bkupdir/large-file-20040208.sql.gz is too large - ignoring Total translation table size: 0 Total rockridge attributes bytes: 169 Total directory bytes: 0 Path table size(bytes): 10 I have looked around and found some articles and emails that say the mkisofs has a 2 gig limit in some circumstances, but I have also seen articles and emails that say this shouldn't be the case on FreeBSD or when dvd+rw-tools is installed. The man page for mkisofs gives a -split-output option which I tried in hopes that it would split the file as necessary, but I got the same error. Anyone have any clues or advice? Thanks, Chris signature.asc Description: This is a digitally signed message part
Re: DVD Burning
On Thu, 2003-11-20 at 15:30, Charles Swiger wrote: ... Right, but the acd device ['man 4 acd'] and the cd device ['man 4 cd'] are not the same-- that's what the CAM subsystem is for, to provide passthrough emulation for ATAPI devices so that you can send SCSI commands to them. The burncd program works with ATAPI devices directly; the programs with dvd+rw-tools need CAM. I mostly get what you are talking about here, but I'm not sure what this means in my situation. Sorry. Hmm, also you should be configuring your device to enable UltraDMA modes rather than PIO; try a sysctl hw.ata.atapi_dma=1, or equivalent in /etc/sysctl.conf or /boot/loader.conf. When I try that sysctl command I get this: # sysctl hw.ata.atapi_dma=1 sysctl: oid 'hw.ata.atapi_dma' is read only The same thing shows up at boot when I have the 'hw.ata.atapi_dma=1' part in /etc/sysctl.conf Charles, I appreciate all your help so far, and I hope that I'm not frustrating you too much. Thanks, Chris signature.asc Description: This is a digitally signed message part
Re: DVD Burning -- Got it Working!!
On Thu, 2003-11-20 at 15:30, Charles Swiger wrote: On Nov 20, 2003, at 3:52 PM, Chris Meyers wrote: On Thu, 2003-11-20 at 14:35, Charles Swiger wrote: Double-check what's going on with your devices, what does camcontrol devlist give you? Maybe try using /dev/cd0c rather than /dev/acd0c? Here's what camcontrol had to say: # camcontrol devlist -v scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) I'm guessing there should be something there between the . More than that, you should see an entry like: NEC CD-ROM DRIVE:465 1.03at scbus0 target 5 lun 0 (pass2,cd0) ...mentioning the CD/DVD device; the entry for xpt0 is simply the driver interface itself, not a reference to a particular device. I don't have a cd0 entry in /dev so trying growisofs with it give this: :-( unable to open(/dev/cd0c,O_RDONLY): No such file or directory Also dmesg show this line: acd0: DVD-R Memorex DVD+/-RW Dual-X1 at ata1-master PIO4 which pretty much shows that the drive is being recognized and put at acd0 Right, but the acd device ['man 4 acd'] and the cd device ['man 4 cd'] are not the same-- that's what the CAM subsystem is for, to provide passthrough emulation for ATAPI devices so that you can send SCSI commands to them. The burncd program works with ATAPI devices directly; the programs with dvd+rw-tools need CAM. Hmm, also you should be configuring your device to enable UltraDMA modes rather than PIO; try a sysctl hw.ata.atapi_dma=1, or equivalent in /etc/sysctl.conf or /boot/loader.conf. Ok I finally got it working. I did need to recompile my kernel and add: device atapicam Once I did that I ran: growisofs -Z /dev/acd0c -R -J bkuptest and I got an ioctl error. I then tried: growisofs -Z /dev/cd0c -R -J bkuptest and everything worked as it was supposed to. Thanks to Charles and everyone else who pitched in their 2 cents. Chris signature.asc Description: This is a digitally signed message part
DVD Burning
So I'm trying to burn daily data backups to a dvd+rw in FreeBSD 5.1 and I'm having no end of problems. The dvd drive is a Memorex IDE internal which is brand new. I've googled until my fingers were cramped and everyone seems to say Here's a bunch of extra stuff you have to do for 4.x insert kernel patching and configuring here. For 5.x you should just be able to do: # burncd -f /dev/acd0c -F format dvd+rw # burncd -f /dev/acd0c -s max dvdrw file.iso Well I can get that format command to work just fine. When I try it, I get the following: # burncd -f /dev/acd0c -F format dvd+rw formatting with blocks=2295104 type=0x26 param=0 formatting DVD - 100 % done So I know that I can talk to the writer and give it commands. I try the next command and all I get is No soup for you! like so: # burncd -f /dev/acd0c -s max dvdrw bkuptest.iso next writeable LBA 0 writing from file bkuptest.iso size 942976 KB written this track 1568 KB (0%) total 1568 KB only wrote -1 of 32768 bytes: Device busy Just so you know, I have tried the above command with -s set to 1, 4 and without it altogether. I am at a loss. Does anybody have any suggestions about what I need to do to make this work? Is there some other way to burn dvds? Do I need to do some kernel recompilation? I have installed dvd+rw-tools but haven't found any good docs, and there doesn't seem to be a man page. I will gladly RTFM if someone would be willing to point me in the direction of the FM which can help me. Thanks in advance for any help. Chris signature.asc Description: This is a digitally signed message part
Re: DVD Burning
On Thu, 2003-11-20 at 14:35, Charles Swiger wrote: On Nov 20, 2003, at 3:18 PM, Chris Meyers wrote: I did check out the docs at /usr/local/share/doc/dvd+rw-tools/index.html and they pretty much re-enforce what you said. Any other ideas?? Double-check what's going on with your devices, what does camcontrol devlist give you? Maybe try using /dev/cd0c rather than /dev/acd0c? Here's what camcontrol had to say: # camcontrol devlist -v scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) I'm guessing there should be something there between the . I don't have a cd0 entry in /dev so trying growisofs with it give this: :-( unable to open(/dev/cd0c,O_RDONLY): No such file or directory Also dmesg show this line: acd0: DVD-R Memorex DVD+/-RW Dual-X1 at ata1-master PIO4 which pretty much shows that the drive is being recognized and put at acd0 Is there any chance you could try this out under FreeBSD 4.9 or so instead of 5.x? Not much of a chance right now. I don't really have a spare system to drop down from 5.1 to 4.9. Chris signature.asc Description: This is a digitally signed message part
