FreeBSD 8.0 and KDE Fonts
On 8.0 with KDE 4.3.1 package installed I have problems with Firefox fonts. Though I installed URW and freetype fonts according to handbook and declared them on xorg.conf, Firefox 3.5.4 cant display some pages properly,ie text is not displayed. So that must be a problem with fonts, because those pages are displayed (well) with Konqueror. What would be the resolution? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Source code of cal
[3D"cid:image001.gif@01C81245.257B2550"] Dear all on Free = BSD: &nbs= p;I want to get a source code of cal (calendar tool), where can I get = it? Thanks smime.p7s Description: S/MIME cryptographic signature Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Computer wakes, keyboard sleeps on
On 15/05/2007, at 8:48 PM, Tom Judge wrote: Never you mind wrote: The keyboard stays asleep after everything else has woken up. How do I begin troubleshooting this problem? I use a KVM switch to share the KVM between two machines. The other machine runs Windows, everything works as it should there. Malcolm Does the KVM you are using have keyboard and mouse emulation for when the system is not active on the KVM. yes, I think it does but I'm not sure I can find the documentation for the device now to confirm its behaviour. Most systems only enable the keyboard if the system detects it on boot, it could be the same when waking from a sleep state. Watching the boot process I see that there is a keyboard error but the keyboard then works once the system is running. That does seem odd. I'll try removing the KVM and see what happens. malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Computer wakes, keyboard sleeps on
The keyboard stays asleep after everything else has woken up. How do I begin troubleshooting this problem? I use a KVM switch to share the KVM between two machines. The other machine runs Windows, everything works as it should there. Malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mounting an FTP space ?
On 02/03/2007, at 2:58 AM, John Nielsen wrote: On Thursday 01 March 2007 01:37, Never you mind wrote: On my Mac from the Finder I can select "Connect to server", give it the details of an ftp location and it will connect and display the ftp space as a drive on the desktop. Can I obtain the same sort of functionality using freeBSD and xfce desktop manager? I haven't used it, but the sysutils/fusefs-curlftpfs should allow you to mount an ftp location as a virtual filesystem. The desktop icon thing you'll have to work out on your own, but it shouldn't be too difficult (a shortcut to your chosen mountpoint should suffice). I've just made an error during installation. At the dialog I selected BOTH c-ares and IPV6. That caused an error: curl-7.16.0_1 does not support both c-ares and IPv6 - disable one of them. OK. I thought I'd simply run "make install clean" again and at the dialog I would make my selection. However, I do not get to the dialog. My choices have been saved somewhere and are being re-used. I need to clean up from my first effort. What do I need to do to wipe the slate clean? malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mounting an FTP space ?
On 02/03/2007, at 2:58 AM, John Nielsen wrote: On Thursday 01 March 2007 01:37, Never you mind wrote: On my Mac from the Finder I can select "Connect to server", give it the details of an ftp location and it will connect and display the ftp space as a drive on the desktop. Can I obtain the same sort of functionality using freeBSD and xfce desktop manager? I haven't used it, but the sysutils/fusefs-curlftpfs should allow you to mount an ftp location as a virtual filesystem. The desktop icon thing you'll have to work out on your own, but it shouldn't be too difficult (a shortcut to your chosen mountpoint should suffice). thanks John, That sounds like what I want. I have previously used KDE as the desktop manager and it included graphical tools which managed this job. However, I'm learning to like xfce and looking at what I can do to make it work for me. malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mounting an FTP space ?
On my Mac from the Finder I can select "Connect to server", give it the details of an ftp location and it will connect and display the ftp space as a drive on the desktop. Can I obtain the same sort of functionality using freeBSD and xfce desktop manager? Malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adding a KVM, what should I be aware of?
I got a x86 running 4.7 and 5.0 on one port, mouse works fine, and an Alpha 1000a on the other port running RH... I was given a funky keyboard that supported a whole bunch of crummy commands for opening URL's and what not. This made both unices get all stupid when switching between the two, no alt-f1 switching etc. I put my old fuji keyboard on and now it's back up to working m&k on both ports. Just a pair of bits. :) On Wed, 26 Mar 2003, Dragoncrest wrote: > I'm looking at adding a new KVM switch in the coming weeks. I'm also > going to be installing Freebsd 5.0 on one of my new workstations. Just > wondering what I should be aware of before installing the system and > putting it on the KVM. I know some people have mentioned issues with that > before, so I wanted to be ready and aware of any and all issues so I could > nail them as they show up so I'm not ripping my hair out trying to solve > issues relating to my KVM switch. Thanks! > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel i810e graphic
Windows 3.11. Are you using that now? No probably not. Does 9X, 2000, or any other new M$ breed work? That would be interesting. Sometimes old hardware is sure nice to have around as a spare, but at $200.00 for a decent monitor that includes all horiz/vert timings I'd say maybe it's time to move on. As a side, I consider having the opportunity to modify my monitor's scan rates quite a bonus and something as the owner of the hardware/software should be allowed to do. Not rely on some companies 'default should work for everyone' profile. I am using 815e and had similar difficulties to the ones you talked about. After a few weeks of research I figured it out and am happy with the results. Was I frustrated? Yes at the time. Is it FreeBSD/developers fault or even XFree86? Nope. Notta. I know that much more now and in fact have two video cards in my box supporting two monitors off of the same X... All learned while working on figuring out my 815e problems. My 2 cents. R. On Sun, 9 Mar 2003, Miroslaw J. Wiechowski wrote: > Just one more observation... > > Somehow the old Windows 3.11 worked very well with my monitor > in all avaliable resolutions 640x480, 800x600 and 1024x768. > > I didn't have to know anything about timings, clocks, vertical > synchronisations, modelines etc. > > Regards > mjw > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: hacking attempts?
On Tue, 4 Mar 2003, Kevin Kinsey, DaleCo, S.P. wrote: > > him/her/it access to your sshd daemon. NOTE: It is 'normally not a > good > > idea' to do this, but if you don't want to rebuild with a firewall > > configured kernel it will suffice. > > > And the reason it's not a "good idea"? I've always > assumed it was because you didn't want to be > on vacation, at a friends house, or suddenly have > your ISP switch subnets on you and lock you out > of your box... > > Absolutely nothing wrong with denying the > supposed "cracker's" IP; AAMOF, go over > to ARIN or APNIC or such and ditch entire > Class A nets that you'll never touch...I'll never > be in SE Asia, for example... > > I use a dual strategy here. One machine only > trusts a second; on the second box I deny > the known bad guyz and let most others try... > ...Needless to say, the really important stuff > is on the first box... > I was only quoting the default hosts.allow line for sshd which states: # Wrapping sshd(8) is not normally a good idea... This is no reason not to use it since in the man for sshd it states: /etc/hosts.allow, /etc/hosts.deny Access controls that should be enforced by tcp-wrappers are defined here. Further details are described in hosts_access(5). R. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: hacking attempts?
ipfw: getsockopt(blaah) Is your kernel configured for firewall work? Check LINT for options. As well you should be able to use tcpwrappers, look in /etc/hosts.allow. You could add a deny for this 'persons' ip addy denying him/her/it access to your sshd daemon. NOTE: It is 'normally not a good idea' to do this, but if you don't want to rebuild with a firewall configured kernel it will suffice. Hope this helps. R. On Tue, 4 Mar 2003, Phillip Smith (mailing list) wrote: > > I found this in my logs and I'm wondering if this is a hacking attempt? > Should I be concerned? > > Also, if/when I see these, I'd like to add them to a blocked list using > /sbin/ipfw, but get the following message when trying this command: > > # /sbin/ipfw add 1 deny all from 151.204.100.88:255.255.255.255 to any > ipfw: getsockopt(IP_FW_ADD): Protocol not available > > > freedom.domain.com login failures: > Mar 2 11:38:33 freedom sshd[47912]: Failed none for illegal user test > from 64.21.10.2 > port 36747 ssh2 > Mar 2 11:38:33 freedom sshd[47912]: Failed publickey for illegal user > test from > 64.21.10.2 port 36747 ssh2 > Mar 2 11:38:34 freedom sshd[47912]: Failed keyboard-interactive for > illegal user test > from 64.21.10.2 port 36747 ssh2 > Mar 2 11:38:34 freedom sshd[47912]: Failed password for illegal user > test from > 64.21.10.2 port 36747 ssh2 > Mar 2 11:38:34 freedom sshd[47912]: Failed password for illegal user > test from > 64.21.10.2 port 36747 ssh2 > Mar 2 11:38:37 freedom sshd[47913]: Failed none for illegal user oracle > from 64.21.10.2 > port 36984 ssh2 > Mar 2 11:38:38 freedom sshd[47913]: Failed publickey for illegal user > oracle from > 64.21.10.2 port 36984 ssh2 > Mar 2 11:38:38 freedom sshd[47913]: Failed keyboard-interactive for > illegal user oracle > from 64.21.10.2 port 36984 ssh2 > Mar 2 11:38:38 freedom sshd[47913]: Failed password for illegal user > oracle from > 64.21.10.2 port 36984 ssh2 > Mar 2 11:38:38 freedom sshd[47913]: Failed password for illegal user > oracle from > 64.21.10.2 port 36984 ssh2 > Mar 2 11:38:41 freedom sshd[47914]: Failed none for illegal user guest > from 64.21.10.2 > port 37171 ssh2 > Mar 2 11:38:41 freedom sshd[47914]: Failed publickey for illegal user > guest from > 64.21.10.2 port 37171 ssh2 > Mar 2 11:38:41 freedom sshd[47914]: Failed keyboard-interactive for > illegal user guest > from 64.21.10.2 port 37171 ssh2 > Mar 2 11:38:41 freedom sshd[47914]: Failed password for illegal user > guest from > 64.21.10.2 port 37171 ssh2 > Mar 2 11:38:41 freedom sshd[47914]: Failed password for illegal user > guest from > 64.21.10.2 port 37171 ssh2 > Mar 2 11:38:44 freedom sshd[47915]: Failed password for ROOT from > 64.21.10.2 port 37187 > ssh2 > Mar 2 11:38:45 freedom sshd[47915]: Failed password for ROOT from > 64.21.10.2 port 37187 > ssh2 > Mar 2 11:38:48 freedom sshd[47916]: Failed password for nobody from > 64.21.10.2 port > 37211 ssh2 > Mar 2 11:38:48 freedom sshd[47916]: Failed password for nobody from > 64.21.10.2 port > 37211 ssh2 > Mar 2 11:38:52 freedom sshd[47917]: Failed password for games from > 64.21.10.2 port > 37215 ssh2 > Mar 2 11:38:52 freedom sshd[47917]: Failed password for games from > 64.21.10.2 port > 37215 ssh2 > Mar 2 11:38:56 freedom sshd[47918]: Failed none for illegal user user > from 64.21.10.2 > port 37217 ssh2 > Mar 2 11:38:56 freedom sshd[47918]: Failed publickey for illegal user > user from > 64.21.10.2 port 37217 ssh2 > Mar 2 11:38:56 freedom sshd[47918]: Failed keyboard-interactive for > illegal user user > from 64.21.10.2 port 37217 ssh2 > Mar 2 11:38:56 freedom sshd[47918]: Failed password for illegal user > user from > 64.21.10.2 port 37217 ssh2 > Mar 2 11:38:56 freedom sshd[47918]: Failed password for illegal user > user from > 64.21.10.2 port 37217 ssh2 > Mar 2 11:38:59 freedom sshd[47919]: Failed password for ROOT from > 64.21.10.2 port 37218 > ssh2 > Mar 2 11:38:59 freedom sshd[47919]: Failed password for ROOT from > 64.21.10.2 port 37218 > > > -- > Phillip > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Alpha and Unaligned access errors.
Just a note, I used to run a 1000a on DU 4.0 up to 5.0 and had those as well. It had to do with a library I was compiling against and usually didn't cause any damage that I was aware of. R. On Fri, 14 Feb 2003, Kris Kennaway wrote: > On Fri, Feb 14, 2003 at 10:54:40AM -0600, Eric Six wrote: > > > Messages whenever I do a ipfw -* commands. I know I can add a > > unaligned_print="NO" to rc.conf to stop these errors, but what I am > > wondering is: Is this normal or is this a sign of a software problem with > > ipfw? > > It's a code problem which no-one has bothered to fixed. > > Kris > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Off-topic question.
--daxbert That was my first thought to that my ISP was using a proxy of sorts. A friend of mine using "the other" (there are only two highspeed w.i.l) isp got the same message. Now there is a chance that the site we were hitting was using a proxy and we snagged it both when they were experience problems. Just wondering what software/hardware was stdout'ing the message in the format it's in. R. On Thu, 13 Feb 2003, Daxbert wrote: > > Don't know if you have been seeing more and more of these messages in your > > surfing: > > > > SERVER_RESPONSE_RESET > > > > It's a message on a white screen with little else. > > > > Searching web, cisco (I thought it was a router issue...), > > httpd.apache.org, etc didn't turn up any good results. > > > > Not important, me and me friends were trying to figure out where it is > > coming from. > > Are you by chance using a web proxy? or does your ISP use > a transparent web proxy? > > --daxbert > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Off-topic question.
Don't know if you have been seeing more and more of these messages in your surfing: SERVER_RESPONSE_RESET It's a message on a white screen with little else. Searching web, cisco (I thought it was a router issue...), httpd.apache.org, etc didn't turn up any good results. Not important, me and me friends were trying to figure out where it is coming from. R. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
I did have an instance where my screen had this annoying green square on it, I tried soo many things until I kicked the box in desperation. [ kick = reboot ] It was gone when I restarted. I don't know if this will help or not, just thought I'd throw what happened to me into the mix. R. On Tue, 11 Feb 2003, Darren Spruell wrote: > Andrew Lankford wrote: > > To my knowledge, DRI extensions have never worked with i810 on FreeBSD. > > Whenever I felt tinkering with the config to see I could enable DRI, it > > wouldn't take, but I don't think it ever mucked up my screen. My video monitor > > did have some trouble with the DDC option (on my stable partition, just after > > I had upgraded the bios), but DDC seems to work ok now. If you do get it > > working, I would stay with a DefaultDepth of 16 instead of 24, as > > a setting of 24 tends to slow demanding apps down without noticeably improving > > picture quality. Notice also that the HorizSync and VertRefresh values are > > a tiny bit different on mine as well. > > > > Anyway, here's my XF86Config: > [...] > > Aargh. I tried both the changes you suggested, as well as adjusting only > the relevant parts of your config and trying it.. same result in both > cases. I even pulled a Red Hat 7.3 XFree86-4 config off of a working X > station and adjusted paths, etc. Same stupid staticy crap with the white > square ;) > > Anyway. I hate getting whooped by something this stupid, but I'm at > wit's end. Any other suggestions? If not, I found another huddy OEM > Gateway box with a different video card. I've got half a mind to try X > out on it. > > -- > Darren Spruell > Sento IS Department > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
My i815e wouldn't run until I did the following: NoDDC as an option. Configured horiz & vert according to monitor specs. Added agp into kernel configuration. Compiled new agp enabled kernel and installed it. NOTE: For a test I loaded the agp module and then ran X. NOTE2: I also took the generic XF86Config and edited by hand so I didn't have to use -configure. I don't know if this will help any but that's what I did. You might want to check your /dev/agpgart as well to make sure it exists. R. On Mon, 10 Feb 2003, Darren Spruell wrote: > Continuing on from my previous posting below, I have scoured some docs > to make some changes to the XF86Config: > > * Added Option "DPMS" to Monitor section (by suggestion of list member) > * Added Option "NoDDC" to Device section (by suggestion of list member) > * Changed Device section to now read as follows, from i810 man page... > (in short, was using the vga driver, changed to the i810 driver.) > > > Section "Device" > ### Available Driver options are:- > ### Values: : integer, : float, : "True"/"False", > ### : "String", : " Hz/kHz/MHz" > ### [arg]: arg optional > #Option "ShadowFB" # [] > #Option "VGAClocks" # [] > #VideoRam16 > Option "NoDDC" > Identifier "Intel i810" > Driver "i810" > VendorName "Intel" > BoardName "i810-dc100" > BusID "PCI:0:1:0" > EndSection > > The problem now is that when I run "XFree86 -xf86config > ./XF86Config.new", it looks like the X display is coming up but all it > shows me is a 1 inch by 1 inch white square surrounded by a screen of > staticy purplish, bluish, and greenish lines.. and stays. Desktop never > displays. > > The log file shows lines like this, with the following error: > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > drmOpenDevice: minor is 1 > drmOpenDevice: node name is /dev/dri/card1 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > [...] > drmOpenDevice: minor is 13 > drmOpenDevice: node name is /dev/dri/card13 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > drmOpenDevice: minor is 14 > drmOpenDevice: node name is /dev/dri/card14 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > drmOpenDevice: Open failed > (II) I810(0): [drm] drmOpen failed > (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. > > > Any other suggestions? > > > DS > > > > +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: > > | Date: Mon, 10 Feb 2003 11:07:22 -0700 > > | From: Darren Spruell <[EMAIL PROTECTED]> > > | Subject: X problems on i810 | AddScreen/ScreenInit failed > > | > > | Greetz, > > | > > | I'm trying to configure v4.7 to run X but am having a hard time getting > > | the server to start. > > | > > | I've followed the config instructions at > > | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html > > | by doing the following steps: > > | > > | Run XFree86 -configure > > | to create the default XF86Config.new > > | Run XFree86 -xf86config ./XF86Config.new > > | to ensure that it works w/my hardware > > | Edit it to taste, to change specifics for HorizSync, VertRefresh, and > > | the Display subsection under "Screen". > > | > > | However, running 'XFree86 -xf86config ./XF86Config.new' after changing > > | my config does not work. The output error is: > > | > > | == > > | (==) VGA(0): Write-combining range (0xa,0x1) was already clear > > | > > | Fatal server error: > > | AddScreen/ScreenInit failed for driver 0 > > | == > > | > > | I followed through the part in the Advanced Configuration section about > > | adding in support for agpgart and created the device node and added the > > | following to /boot/loader.conf: > > | agp_load="YES" > > | > > | dmesg now shows: > > | Preloaded elf module "agp.ko" at 0xc051a09c. > > | agp0: mem > > | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at de
