jdk14 without X libraries?
I'm building /usr/ports/jdk14 on my 5.4-RELEASE i386, and it's using a lot of X.org stuff to do the build. I'm already using the -DMINIMAL flag, but I'd like a way to turn off all the graphical stuff. Does anyone here know how to do this? Thanks, Steve Brown ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Serial console capable BIOSes?
Does anyone have recommendations for motherboards (P3 or P4) with good BIOS serial console support that plays nicely with FreeBSD running a serial console on the same port? Basically, I'd like to monitor the pre-BSD boot process and the BSD boot process from a terminal window on another machine. Thanks, Steve B [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linux move to FreeBSD
That is way I here your problem but could not clearly see the problem with any Os's. How about you install BSD and just clear the conf file which shows Beastie at startup. Asking people to do something to easily remedy a situation of their own accord? Are you crazy? Steve B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dovecat-0.99.14 SSL option not present?
I am trying to get dovecat running on a FreeBSD-5.2.1 system with a nightly-updated ports tree. I am running into the problem that dovecat 0.99.14 is not compatible with GNUTLS at the moment, as document on this list previous to my joining: # make config will allow you to redo your config choices and select SSL rather than GNUTLS, support for which is broken in Dovecot itself ATM, thus in the port also. However, when I run the config, I don't have the option to select SSL. My options are: GNUTLS, SASL2, VPOPMAIL, LDAP, PGSQL, and MYSQL. Any suggestions? Thanks, Steve B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Did not use port_upgrade
Do I need to make deinstall all of these ports and start all over? I'd appreciate someone correcting me if I'm wrong; I think you should just be able to upgrade your ports tree (directions in the Handbook) and then the ports will compile with the latest versions. Steve B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Geli questions.. ponderings..
The idea: I'd like to use geli to encrypt *everything* on the disk. So if someone (a competitor maybe) removes the disk from the machine, he can't gain any data off of it easily. I know nothing is 100%, but why make the process easy for him? It seems like there is a more basic problem here than automating key downloading. If the end-user can boot up the box, then they have an opportunity to interfere with the boot process. The code providing instructions to fetch a remote key would have to be in the clear, in which case the competitor could just use that code to get the remote key (since it would do so automatically on boot, I assume you're not requiring the client to call you for key authorization every time?) and then access the disk. The problem is wanting to automate the decryption process, I think. Steve B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
devfs creates unwanted devices in jail after ruleset applied
I am running a DNS server in a jail and have setup a devfs mount in the jail to have null and random devices. The setup works fine, but once I log out then log back in the pty and tty devices of my login get created in the jail. Which, of course, I don't want to happen. To clarify, I'm not talking about logging into the jail, this occurs when logging on to the system. The jail is stripped down, not anywhere close to a virtual server. I do the following to create the jail'd devfs at startup: mount_devfs devfs JAILDIR/dev devfs -m JAILDER/dev rule -s 35 add hide devfs -m JAILDIR/dev rule -s 35 add path null unhide devfs -m JAILDIR/dev rule -s 35 add path random unhide devfs -m JAILDIR/dev rule -s 35 applyset This works great - I get a dev directory setup with just null and random. But the second anyone logs into the system, whammo all the sudden pty and tty devices appear inside the jail's /dev directory. If anyone would care to unclueless me I would appreciate it. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 6.1
I `ve got a question about freebsd 6.1. I try to install 6.1 on a celeron 1300 but it will not install. When i try to install freebsd 5.5 on the same machine i don`1t have any trouble. What could be the reason? Any additional information such as how are you trying to install (CD? FTP?), where does it fail, what happens when it fails, error messages, etc. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devfs creates unwanted devices in jail after ruleset applied
If no one has any ideas, suggestions on perhaps a better place to pose this question? Steve On Sat, 18 Nov 2006 10:52:55 -0500, Steve Brown [EMAIL PROTECTED] said: I am running a DNS server in a jail and have setup a devfs mount in the jail to have null and random devices. The setup works fine, but once I log out then log back in the pty and tty devices of my login get created in the jail. Which, of course, I don't want to happen. To clarify, I'm not talking about logging into the jail, this occurs when logging on to the system. The jail is stripped down, not anywhere close to a virtual server. I do the following to create the jail'd devfs at startup: mount_devfs devfs JAILDIR/dev devfs -m JAILDER/dev rule -s 35 add hide devfs -m JAILDIR/dev rule -s 35 add path null unhide devfs -m JAILDIR/dev rule -s 35 add path random unhide devfs -m JAILDIR/dev rule -s 35 applyset This works great - I get a dev directory setup with just null and random. But the second anyone logs into the system, whammo all the sudden pty and tty devices appear inside the jail's /dev directory. If anyone would care to unclueless me I would appreciate it. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
