Re: bsd mirror
On Mar 16, 2004, Tim Connolly wrote: > I am setting up an internal mirror of FreeBSD and would like to > know what should be the best source/protocol for mirroring ? Also, if I > would like to stick my mirror on your list of mirrors, what do I need to do > ? This mirror will be used internally for www.theplanet.com. > > > > Thanks > > Tim > > > > > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hi, Check out the net/cvsup-mirror and sysutils/fastest_cvsup ports. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: linux-opera with anti-alias
On Sat, Mar 06, 2004 at 08:03:09PM -0500, Jud wrote: > On Sat, 6 Mar 2004 14:40:17 +0100, Peter Hollaubek <[EMAIL PROTECTED]> > wrote: > > >Has anyone succeeded to use the linux-opera port with anti-aliased fonts? > >During installation it says the WITH_XFT2 variable should be set to > >enable > >aa fonts, and it does install the additional linux packages, though the > >fonts are rendered as usual. I've also tried setting the QT_XFT variable > >with > >no effect. > > Opera uses an older method of anti-aliasing which involves use of an > XftConfig file. Though the document at the URL below describes a NetBSD > setup, it will work on FreeBSD, and Linux-Opera will be able to display > anti-aliased fonts if they are selected in fonts preferences. I find the > Bitstream Vera fonts give a very nice appearance. > > http://mail-index.netbsd.org/tech-x11/2002/12/29/.html> > > HTH, > > Jud > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks for the reply. Though the solution was not the one You've mentioned, I've found the real one on freebsdforums.org. Just for the archive: Fontconfig uses a configuration file named fonts.conf, xft loads fonts according to this file. Though the configuration was good for native application (for they have a differend version installed with the native port in /usr/X11R6/etc/fonts/fonts.conf), the emulated opera found another one like /usr/compat/etc/fonts/fonts.conf. You only have to symlink the native to the other one, and everything's OK. Maybe this should be done by the linux port automatically. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
linux-opera with anti-alias
Has anyone succeeded to use the linux-opera port with anti-aliased fonts? During installation it says the WITH_XFT2 variable should be set to enable aa fonts, and it does install the additional linux packages, though the fonts are rendered as usual. I've also tried setting the QT_XFT variable with no effect. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mutt, Postfix and port 512
On Feb 24, 2003, Kjell Midtseter wrote: > List members! > On my LAN I have a FreeBSD R4.7p4 workstation where I fetch > my mail for this list from my ISP using fetchmail, and reading > it with mutt. > After I switched from using sendmail to postfix I started getting messages on ttyv0 > like: > Feb 23 07:26:33 tina /kernel: Connection attempt to UDP 127.0.0.1:512 from > 127.0.0.1:1054 > each time a mail is arrives. > A second or three after the above message is shown, the mail pops up in mutt. > > What causes the message, and how do I eliminate it? > > Regards from Kjell > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message /etc/services: biff512/udpcomsat #used by mail system to notify users man comsat: Comsat is the server process which receives reports of incoming mail and notifies users if they have requested this service. Comsat receives mes- sages on a datagram port associated with the ``biff'' service specifica- tion (see services(5) and inetd(8)). This service is off by default, thus if log_in_vain is turned on, you will have a similar message after every mail. Sendmail/mail.local has the very same behavior unless you specify the -B flag to mail.local. fif pgp0.pgp Description: PGP signature
Re: installkernel first?
On Feb 20, 2003, [EMAIL PROTECTED] wrote: > I'm tracking 4.7 stable. > The handbook asks me to: > go to single user mode and fsck -p (etc ...) > Can't. > "/dev/ad2s1a: NO WRITE ACCESS > /dev/ad2s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY." > (Mounted RW according to fstab). > > after "make buildworld" as single user and reboot also to single user could not > "cd /usr/src" - ls shows the /usr directory containing only /usr/local and no > other directories. > I CAN find /usr/src (and a number of other useful directories ) as root or user. > > I am next supposed to "make buildkernel # make installkernel". This appeared to > work ok (I didn't monitor), but no new kernel appeared in the / directory (I > still had my 'old' one). > > The next step was to be "make installworld" but I have not done this in view of > the earlier errors. > > Can someone figure this out for me and point me in the right direction? > Thanks. > > -- > Brian > As of /usr/src/UPDATING: To update from 4.0-RELEASE or later to the most current 4.x-STABLE -- make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user) [1] make installworld mergemaster [2] reboot In single user mode only the root fs is mounted by default. So for making installworld you have to mount all the slices affected by such a process (usually all other slices like /usr, /var), and also, only the system itself boots up, nothing else is started preventing any problem caused by installing something new under a running old task in memory. If the new kernel fails you can return to the old one without risking incompatibility with the old kernel and the new world. Everything in this order has a reason :). fif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
