Re: READ_BIG timed out errors on acd0
Sorry for the delay... I had memory issues I had to resolve first. I'm now ready to revisit this issue. Predrag Punosevac wrote: I will also mention something which is probably stupid. But you know that in FreeBSD you must have a wire between DVD/CD rom and audio card to be able to listen to CDs. Can you listen to the CDs? I have no clue if you could rip CD without that wire. The CD-audio cable is not used or needed for ripping which is also known as DAE = digital audio extraction. Garrett Cooper wrote: Try cd0, not acd0, or create appropriate links via /etc/devfs.conf. Sound Juicer doesn't allow you to pick between the two. It identifies the drive by name, not by its /dev entry, and it only gives me the one option. Everyone else: here's my original post for reference. I'm trying to doing a fresh buildworld with the latest -STABLE but it doesn't seem stable and isn't building as the tree currently is, so I might have to wait on that. I'm hoping there's a multimedia guru who can help walk me through a series of sensible troubleshooting steps in order to get to the bottom of this, because multimedia isn't my forte and I'm sort of flying by the seat of my pants here. Scott I. Remick wrote: Hello... I'm using 6.2-STABLE from Aug 8th. Trying to get a CD ripping program to work on this new box. Have used Grip in the past, also trying Sound Juicer but both are having issues... I think it's something to do with the drive. Here's what I get in /var/log/messages: Aug 29 00:30:52 desktop kernel: acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request Aug 29 00:31:28 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:05 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 0x5 back And so on and so forth. The drive is a Samsung SH-S183L DVD+RW connected via SATA: acd0: DVDR TSSTcorpCD/DVDW SH-S183L/SB01 at ata3-master SATA150 # atacontrol mode acd0 current mode = SATA150 I think the freezes I get with Grip and Sound Juicer are related to these errors. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports tree is already up to date.
On Mon, 01 Oct 2007 18:07:50 +0200, Zbigniew Szalbot wrote: Hard to believe that as I have not fetched the updates for the last 2 (or 3) days and there are always a few new or updated ones. Coincidence or the portsnap server is wrong? You're not the only one. I just hopped on here to check to see if there was any mention of a ports freeze that I missed. Figure 6.3 is just around the corner...maybe? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nVidia driver with Xorg 7.3?
Anyone tried the current nVidia-driver with the new X.org 7.3? I heard that there was a general (non-FreeBSD-specific) incompatibility, but just saw that 7.3 was now in the ports system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Predrag Punosevac wrote: How about if you read first page from Chapter 18 from the Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html There are several rock solid command line programs for burning CDs and DVDs. Burn cd is the simplest one. cdrecord is the second one. Except I am not trying to burn a CD. I am trying to rip (extract CD audio tracks into a file). Both burncd and cdrecord are for burning (writing) CDs, which is not the issue. Now, the dd command mentioned on that page... that I am familiar with, and already had tried. Through me for a loop at first since I thought it was outputting a .wav file, but once I realized it was just a raw PCM file I was able to play it fine. So it works. cdda2wav seems to extract a wav file fine, with no errors. File is playable. cdparanoia also creates a playable wav file just fine. Forgive me for saying this but before we declare something is wrong with hardware lets check if the thing can record from the command line when you are supper user. This way we will check if something is wrong with hardware or with configuration files i.e. permissions , links etc. If you can rip CD from the command line hardware is OK. It's not that I thought I had bad hardware, but I figured I might need some config/settings tweaks, especially since it's an SATA drive. Anyhow, sorry for the confusion... don't mean to seem dense. Just didn't seem like we were on the same page (burning vs. ripping). Hopefully the command-line results give you an idea of where to look next. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Garrett Cooper wrote: The big assumption is that the CD that you're ripping from doesn't have copyright protection on it. That kind of a CD will show that particular set of behavior in FreeBSD. I'm pretty sure I'm safe... the CD I'm testing with at the moment is from 1990. :) It happened with another old CD too, but I thought it was due to some scratches on that one so I tried another. I'm not trying to encourage anything illegal. I did that with a lot of Japanese CDs I own just because I prefer MP3/MP4 formatted tracks on my iPod / PC. I prefer Ogg Vorbis, and I'd rather not have to scour the internet for songs that I already have the CDs for and could just rip/encode myself (in better-quality than what I'd find too). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Predrag Punosevac wrote: Why don't you mount your cd as su - password mount-t cd9660 /dev/acd0 /mnt You should see you disk mounted and songs like files that you can transfer to hard disk. Of course you can convert them latter to some format you like best. # mount -t cd9660 /dev/acd0 /mnt mount_cd9660: /dev/acd0: Invalid argument device scbus device cd device pass Yes, all 3 of those are already in my kernel. device atapicam I also have this. Verified by the following dmesg output: cd0 at ata3 bus 0 target 0 lun 0 cd0: TSSTcorp CD/DVDW SH-S183L SB01 Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: cd present [3281952 x 2048 byte records] Finally, if you are running GNOME 2.16 or later, you must have HAL running Yep: [EMAIL PROTECTED] /data/home/scott]# ps -ax | grep hald 893 ?? Ss 0:59.80 /usr/local/sbin/hald 894 ?? I 0:00.02 hald-runner 904 ?? S 2:22.76 hald-addon-storage: /dev/da0 (hald-addon-storage) 907 ?? S 2:20.78 hald-addon-storage: /dev/da1 (hald-addon-storage) 910 ?? S 2:20.42 hald-addon-storage: /dev/da2 (hald-addon-storage) 913 ?? S 2:20.95 hald-addon-storage: /dev/da3 (hald-addon-storage) 918 ?? S 3:29.59 hald-addon-storage: /dev/cd0 (hald-addon-storage) To figure out which CD/DVD drive you will be using, run the following command as root: # camcontrol devlist Generic USB SD Reader 1.00 at scbus0 target 0 lun 0 (pass0,da0) Generic USB CF Reader 1.01 at scbus0 target 0 lun 1 (pass1,da1) Generic USB SM Reader 1.02 at scbus0 target 0 lun 2 (pass2,da2) Generic USB MS Reader 1.03 at scbus0 target 0 lun 3 (pass3,da3) TSSTcorp CD/DVDW SH-S183L SB01 at scbus5 target 0 lun 0 (cd0,pass4) The devices in parentheses at the end are important. You must make sure the /dev entries for those devices are writable by the users that will be using nautilus-cd-burner, totem, goobox, or sound-juicer. Hmm well I didn't realize that Sound Juicer used /dev/cd0, I figured it used acd0 (which had suitable permissions). I granted write permissions across the board for /dev/cd0 but that didn't fix it. In addition to those devices, /dev/xpt* must also be writable to your nautilus-cd-burner, totem, goobox, and sound-juicer users. The following /etc/devfs.conf configuration will achieve the desired results given the above devlist: permcd0 0666 permxpt00666 permpass0 0666 Those I also didn't have set, but granting permissions still doesn't allow Sound Juicer to work. Basically the symptoms are that Sound Juicer detects the drive (as CD/DVDW SH-S183L) but never displays a track list. Grip loads up but seems to freeze for several moments at a time... sometimes Grip will display a track list for the duration of one freeze only to have it vanish and say no disc after the next freeze. And periodically I see messages like these in my /var/log/messages: Aug 29 17:42:10 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 17:43:59 desktop last message repeated 3 times Aug 29 17:43:59 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 0x5 back ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Podcast management software?
On Mon, 27 Aug 2007 23:53:37 +0200, Nikola Lecic wrote: Does any of these programs look good enough? Actually I had already looked into those before I posted. Neither castget nor podcatcher support any retention settings like the other software I listed. Castpodder hasn't seen development in a year and the website is gone, so it appears abandoned. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
READ_BIG timed out errors on acd0
Hello... I'm using 6.2-STABLE from Aug 8th. Trying to get a CD ripping program to work on this new box. Have used Grip in the past, also trying Sound Juicer but both are having issues... I think it's something to do with the drive. Here's what I get in /var/log/messages: Aug 29 00:30:52 desktop kernel: acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request Aug 29 00:31:28 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:05 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 0x5 back And so on and so forth. The drive is a Samsung SH-S183L DVD+RW connected via SATA: acd0: DVDR TSSTcorpCD/DVDW SH-S183L/SB01 at ata3-master SATA150 # atacontrol mode acd0 current mode = SATA150 I think the freezes I get with Grip and Sound Juicer are related to these errors. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Podcast management software?
I think I must be the only one using FreeBSD who wants to listen to podcasts. :) I'm having trouble finding decent podcast downloading/management software to use on my FreeBSD desktop. Although a number of media player/ management programs (Exaile, Rhythmbox, Amarok, BMPx) have podcast- capabilities, they are limited and seem tacked-on as an afterthought. Missing is something along the lines of IcePodder, jPodder, Juice Reciever, etc. Because I want to keep my podcast directory current so it's ready to be synced with my media player at pretty much any time, even a command-line program (run via cron) would suffice. I fear not editing text configuration files. I just need SOMETHING that has the basic features I need. Not even castget nor podcatcher have more than download what's new features. What I need is to be able to manage my already-downloaded podcasts, so that I can choose things like only keep the last X number of podcasts and only keep podcasts from the last X days/weeks. Seems simple, right? Does anyone know of any program in the ports that can do this? If there's one out there not in ports, is there someone willing to add it? Thanks ever so much! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird 2.0
On Tue, 24 Apr 2007 10:12:06 -0700, FreeBSD WickerBill wrote: I portupgraded thunderbird today (6.1 p11, KDE 3.5.6_2) and while it's semi-functional, it does seg fault as it checks the pop server. ... These problems were fixed by uninstalling all broken extensions and removing the theme I was using and installing the default theme. Hmm, I don't even get that far. TB 2.0 just immediately seg faults for me (after coming up and showing itself, apparently as it's checking but it's not semi-functional for me at all). Didn't have much time to look into it this morning before work but I do have a number of extensions so maybe my problem is similar to yours (I use IMAP though). I assume TB has a safemode switch similar to Firefox's... I'll have to look into it tonight or tomorrow. Anyone else seeing TB 2.0 crash on startup? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot route mail through an internal Exch5.5 SMTP server
I am at my wits end with this... help please! FreeBSD 6.1-RELEASE Sendmail 8.13.6 (base) I'm trying to accomplish what should be simple: 1) all outgoing From: email addresses should be stamped @ourdomain.com and not @server.corpdomain.com 2) All emails should be routed through the corp SMTP server (runs MS Exchange 5.5.2658.3). Users use Outlook clients to connect to the corp Exchange system and this SMTP server is our only gateway into it. I'm a bit rusty on my Sendmail and .mc stuff (I really haven't done much with managing email flow, sendmail or other MTAs) so I tried to brush up online as best I can, but I don't remember it being this hard in the past. At this point, here are the things I've put in my .mc file (I'm sure at least some is redundant or not needed/applicable, but this is the result of trying more and more ideas): define(`SMART_HOST', `internal.corp.smtp') define(`LOCAL_RELAY', `internal.corp.smtp') FEATURE(masquerade_envelope) FEATURE(always_add_domain) FEATURE(`masquerade_entire_domain') FEATURE(`allmasquerade') MAILER(local) MAILER(smtp) MASQUERADE_AS(`ourdomain.com.') MASQUERADE_DOMAIN(`outdomain.com.') (and did the required make install in /etc/mail to apply it) resolv.conf has the corp DNS servers in it. I can use ping and host on internal.corp.smtp and it resolves to the proper IP address. I also tried putting them into /etc/hosts along with entries for the versions of the name with the ending dot. 10.xxx.xxx.xxxinternal.corp.smtp internal 10.xxx.xxx.xxxinternal.corp.smtp. 10.xxx.xxx.xxxinternal. I've even done up mailertable (plus the hash) with the following line: .ourdomain.com smtp:internal.corp.smtp This was the result of some stuff I read on the web regarding the error. Anyways, here is the problem that persists after all that: Sep 14 15:25:04 bugzilla sm-mta[67919]: k8EJOhhB067917: to=[EMAIL PROTECTED], delay=00:00:21, xdelay=00:00:20, mailer=relay, pri=30985, relay=internal.corp.smtp., dsn=4.0.0, stat=Deferred: Name server: internal.corp.smtp.: host name lookup failure First of all, not sure why it's adding the trailing dot, but hence my additions to the /etc/hosts file. Secondly: how can it not resolve? bugzilla# host internal.corp.smtp internal.corp.smtp has address 10.xxx.xxx.xxx bugzilla# host internal.corp.smtp. internal.corp.smtp has address 10.xxx.xxx.xxx my /etc/nsswitch.conf file: group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis shells: files And not that it applies here... but I can telnet to the SMTP server on port 25, type out a session manually and send an email that way. So ultimately it can work. I just don't get this quirky name-resolution problem. I searched on Google and came up with tons of stuff on this, lots of people asking about it but not a lot of answers... I've tried the ones I've found, but a lot of discussions fell dead without the problem being solved. I'm hoping a fellow FreeBSD user (who knows more than me) might help guide me to a solution. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Flash 7 and Firefox 1.5.0.2
On Mon, 1 May 2006 10:44:42 -0400, John Nielsen wrote: 1) I apply the rtld_dlsym_hack.diff patch after every time I update my sources and before I build / install world. Will this still be necessary in 6.1? Or has the patch already been included? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cheap FreeBSD hosting?
On Fri, 24 Mar 2006 07:53:50 -0900, Peter Giessel wrote: $8/month for what you were getting was a steal. I agree. I was otherwise happy. However this buyout is going to be bad, I fear. And the OS change makes me feel hypocritical since I have Powered by FreeBSD all over my pages and actively promote it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cheap FreeBSD hosting?
On Sat, 25 Mar 2006 22:44:36 -0800, Sam Nilsson wrote: iweb.ca a canadian company has good deals on dedicated servers. mine has been up since i got it which makes 129 days now. there have been no network interruptions that i've been aware of in that time. i don't know how their shared hosting plans work though... Thanks for the lead, but looks like I'd have to pay 5X as much per month ($40) for half the space on their shared hosting. :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cheap FreeBSD hosting?
On Fri, 24 Mar 2006 13:48:21 -0500, RJ wrote: http://www.layeredtech.com/layer1.php?g=13 Those are for dedicated servers where the cheapest is $65/month. I guess I don't see how that is a suitable-replacement for my needs and budget...? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cheap FreeBSD hosting?
On Mon, 27 Mar 2006 11:38:37 -0800, Tim Traver wrote: Not exactly sure what your needs are, but we have a shared hosting system that uses FreeBSD as its back end, and we offer competitive features and prices, with a really cool control panel... Our main package for domains is only $12.99/mo and you get 750MB of disk, 15GB of transfer per month, and all the other features that you would expect from a high end web hosting company. Hey Tim... my needs are the reverse: lots of storage, low bandwidth. I'm already at 2.5GB and slowly growing, but average 200-300MB/month transfer. Unfortunately I don't see a plan on your site that fits my needs, but thanks for the heads-up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cheap FreeBSD hosting?
Well it seems my perfect FreeBSD webhost, which had great service, great features, and a great support community has been sold-out to a large webhost consolidation company with a reputation for ruining every company they buy. They'll also be switching from FreeBSD to Linux. Since I desire to eat my own dogfood and continue to have my sites and pages Powered by FreeBSD I am back in the market looking for a new webhost. Currently I pay about $8/month for 12GB of storage, 300GB of bandwidth/month, and 5 MySQL databases. I need at least 4 databases (preferably more), and currently average 200-300MB/month transfer (although I peaked last year one month at 6GB for the month, but that's rare). I currently use 2.5GB but my space needs will gradually increase. I'd like to find a comparable plan at a webhost that uses FreeBSD servers. Pair is out of my league. I've had bad previous experience with iPowerWeb. Any others? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC forwarding over sshd issue
I'm having a weird problem that surfaces sometimes and I am having trouble pinning down the cause. What I do is use VNC to remote-control my home FreeBSD box remotely. Most of the time, this works fine. My home router forwards the external port to my FreeBSD (6.0R) box. I use PuTTY as a Windows ssh client, and have a saved session that does the VNC port-forwarding (local port 7000 forwards over ssh to remote port 5900). I run Gnome (2.12.2) and vino as my VNC server and connect to my home desktop. Sshd is OpenSSH 2.6.1, PuTTY 0.53b, TightVNC 1.2.9 But every now and then (like right now), the VNC side of things fails. I can still connect via SSH just fine. The PuTTY logs show the port is successfully being forwarded with no error: 2006-02-17 09:38:58 Local port 7000 forwarding to localhost:5900 But when I try to launch a VNC client on the remote PC (in this case, TightVNC) I get a Connection closed error. The PuTTY logs show: 2006-02-17 09:52:42 Opening forwarded connection to localhost:5900 2006-02-17 09:52:42 Forwarded port closed On the FreeBSD box, no log files seem to get changed after the attempt. In particular, I check messages and auth.log but doing a listing sorted by time, I see nothing logged. What I DO know is if I went home and restarted the FreeBSD box, it'd work. I've tried -HUP on both sshd and vino-server to no avail. I cannot find any docs for vino-server to determine additional params I could pass it for more-detailed logging. Enabling additional debugging info on sshd with the -d option seems to not be an option remotely since it prevents it from going into daemon mode and it'll only handle one connection, and I can't make the problem surface on-request in order to test it while at home. The problem is particularly annoying because I can't MAKE it happen. It just sometimes does, with no settings changes, and will work again after rebooting the FreeBSD system, again with no settings changes. SSH never stops working... it's always the VNC-port-forwarding side of things. Any suggestions? Somewhere else to look for info? Some way to get more debug info from sshd or vino-server? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
serial console for dummies?
Hello... I'm trying to set up a serial console for watching console error messages while in X, but am having a real hard time getting my head around the concepts of what I need to do (and don't need to). I've seen http://www.freebsd.org/doc/handbook/serialconsole-setup.html but I'm not clear about how much of that applies to what I want to do, since it talks about setting it up for a headless system (no keyboard or monitor) and actually instructs you to remove the keyboard. I've also searched the mailing list archives but I've read a lot of conflicting info, much of which for different uses of the serial console than what I want to use it for, and I've now read back so far that I can't even be certain that the suggestions apply to FreeBSD 6.0. Ugh So is there someone who can give me a hand-held walk-through of just what I need to do to make this work? I'm running FreeBSD 6.0-RELEASE and live in X (Gnome) all the time. My intention here is to be able to see console messages (Errors) so when something dies (like X locking, which happens sometimes) I have a chance to see what the heck happened. I have an old 486 laptop I intend to use as the dumb terminal, as well as the necessary null modem cable. I just need to know what to configure on my FreeBSD box so that console errors are mirrored to the serial port. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serial console for dummies?
On Sun, 29 Jan 2006 10:21:23 +, Robert Slade wrote: I can't help you directly, but have you looked at the error logs? they should give you a clue, especially Xorg.log Last few times I remember looking, there was nothing logged. This lead me to believe that the lockup happened too fast for the output to the logfile to be saved to disk. Hence my desire for a capture on a separate terminal (which presumably might make it). Another thought is to connect via a network connection and SSH into the machine that will give you a console. Unfortunately the laptop I have for this use has no network connection, and it would also require getting FreeBSD working on this ancient (486) thing, which is probably about as much fun as giving yourself a root canal. I have questions about the condition of the HDD anyways (I was going to use a boot floppy, running DOS and a terminal app). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serial console for dummies?
On Sun, 29 Jan 2006 10:01:54 -0500, Ken Stevenson wrote: I was trying to accomplish the same thing a couple weeks ago and somebody recommended the following: touch /var/log/console.log Edit /etc/syslog.conf and uncomment the line that begins with console.info. Reboot (you might be able to just restart syslogd). Interesting. I will try that, but I think I'll be running into the same problem before where the HALT occurs before anything can be written to disk, so nothing gets logged. I think I'd still like to figure out how to set up a serial console too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serial console for dummies?
On Sun, 29 Jan 2006 12:32:46 -0500, Michael P. Soulier wrote: Can't you just run xconsole? Doesn't help me if xconsole is hidden by another window at the time of the halt. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: flash plugin in 6.0
On Thu, 22 Dec 2005 20:43:26 -0900, Beecher Rintoul wrote: Try starting firefox from a terminal and see if you get plugin errors before it starts. I was working on that port locally to fix the paths. I uninstalled everything and did an install with the fixed port and none of the plugins worked. I uninstalled again and reinstalled with the stock port and still nothing. Startup shows errors on all the linux plugins. I think something else has changed, but I'm not sure what. Even my fixes don't work anymore. Finally got time to look into this again tonight. I was getting errors, and the first round suggested that I needed to change libmap.conf from: [/usr/X11R6/lib/linux-flashplugin7/libflashplayer.so] to: [/usr/X11R6/lib/browser_plugins/libflashplayer.so] After that, about:plugins was showing Flash 7, but Firefox would crash when I loaded a site with flash. I then applied rtld_dlsym_hack.diff and now it appears to be working. For the time being. Heh. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: flash plugin in 6.0
I had Flash6 working but have need to try Flash7 (I know it might crash, but some sites I use require at least Flash7). But I can't get it to work at all. I uninstalled linuxpluginwrapper and linux-flashplugin6 before I started. I've tried Beecher's instructions and about:plugins still doesn't show any Flash. This is using Firefox 1.5 on FreeBSD 6.0R. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Weird nice behavior
I'm seeing something strange/annoying tonight... maybe someone could help explain why it's happening. FreeBSD 5.4-RELEASE I'm trying to do a large local rsync in the background, while listening to streaming audio via RealPlayer and do other stuff. I have the rsync running at nice level 20 (nice -20) which I've confirmed via ps: 1001 77010 1452 0 116 20 45056 44332 select SN+ p10:30.89 rsync -av - 1001 77011 77010 295 139 20 45048 44232 - RN+ p1 20:17.12 rsync -av - 1001 77548 77011 0 116 20 45200 44460 select SN+ p10:12.06 rsync -av - RealPlayer is running at normal nice (0): 1001 80675 80650 16 98 0 30004 12516 select S p20:22.69 /usr/local/lib/RealPlayer/realplay.bin 1001 80688 80675 0 96 0 30004 12516 select S p20:00.01 /usr/local/lib/RealPlayer/realplay.bin 1001 80689 80688 0 20 0 30004 12516 pause S p20:02.67 /usr/local/lib/RealPlayer/realplay.bin 1001 80692 80675 24 -8 0 13844 6772 piperd I p20:00.00 /usr/local/lib/RealPlayer/realplay.bin 1001 80693 80675 24 -8 0 13844 6772 piperd I p20:00.00 /usr/local/lib/RealPlayer/realplay.bin 1001 80694 80688 24 20 0 30004 12516 pause I p20:00.00 /usr/local/lib/RealPlayer/realplay.bin 1001 80695 80688 0 20 0 30004 12516 pause S p20:01.34 /usr/local/lib/RealPlayer/realplay.bin 1001 80696 80688 0 8 0 30004 12516 nanslp S p20:01.13 /usr/local/lib/RealPlayer/realplay.bin 1001 80765 80688 0 8 0 30004 12516 nanslp S p20:01.10 /usr/local/lib/RealPlayer/realplay.bin Not sure why it spawns so many processes, but whatever... Anyway, what's happening is despite rsync being nice 20, RealPlayer is incredibly choppy. Even if I'm not doing anything else on the system. Now here's the weirder part: if I DO do something, such as just scrolling a window, the audio stream stops being choppy. It's as if it takes some OTHER application claiming CPU cycles to get rsync to properly play nice and release up time, at which point RealPlayer gets the cycles it deserves. But for some reason, rsync with just RealPlayer on its own will not play nice and give up time to RealPlayer like it should since RealPlayer is running at 0 and rsync is running at 20. Can someone explain this behavior, and offer suggestions to fix it? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 file system troubles
On Wed, 26 Jan 2005 05:50:02 -0700 (MST), Terry R. Friedrichsen wrote: Is anybody besides *me* having file system corruption problems with FreeBSD 5.3? I've looked around on several of the mailing lists and found no men- tion of this. Not the same problem as you, but I've been getting frequent ffs panics with 5.3 that I never got with 5.2.1. I didn't know the actual error at first because I'm in X most of the time and they wouldn't appear there (system would simply lock up). It wasn't until I started trying to update some ports from console only that I caught the error. It only seems to happen during periods of intense disk activity (writes?). I have the actual error written down at home. It always causes an fsck mess upon starting up again, which makes me nervous. There's certain tasks I simply cannot do anymore because they're write-intensive and I know they'll trigger the panic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Man pages take forever on slow machine?
--- Ramiro Aceves [EMAIL PROTECTED] wrote: My pentium 100 MHz with 16 MB RAM runs smoothly with FreeBSD 4.10 , it even runs fvwm under X. I am not able to run 5.3 install, as I only have 16MB, I was suspecting that I need more memory for the install proccess. The reason I wanted 5.3 was so that, if my dad gets hooked and wants to progress, he doesn't have to unlearn the 4.x way of things after just learning it. Unfortunately this old system is the only spare one we had lying around. Now, I can understand needing more than 16MB to install. I can understand that there'd be a lot of swapping. I can understand it's going to be a lot slower than what I'm used to. But what I don't understand is how I could wake up this morning and it's STILL working on that man page. That seems to suggest not just proportional slowness, but that there's something horribly wrong. Truth is, even when it was churning, there wasn't a ton of hard drive access, which lead me to believe that it wasn't a RAM/VM/swapping issue. And now I don't even notice the hard drive light flashing. And even if it WAS swapping... I'd expect FreeBSD to multitask enough so that I could log in under another VTTY and run top and vmstat and such to figure out what was going on. Or at least being able to use CTRL-C to abort (which won't work). Maybe people think I'm masochistic here... but I struggle through these things to learn. Yeah I could just say Sorry, dad... you need to spend $100 and pick up a faster used system but that'd just turn him off the whole idea and keep it from happening anytime soon, and I wouldn't have learned anything more about FreeBSD. My nose tells me there's something wrong here above and beyond my system just being 1/4th the speed of a 450MHz Pentium or the hard drive being twice as slow... and I'd like to either figured it out so I can fix it, or learn precisely what it is for the future. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mpeg4ip require ipv6?
I still can't get mpeg4ip upgraded from 1.0 to 1.1: cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/include -I/usr/X11R6/include -DDEBU G -I../.. -O -pipe -W -Wall -Wwrite-strings -Wbad-function-cast -Wmissing-protot ypes -Wmissing-declarations -Werror -MT net_udp.lo -MD -MP -MF .deps/net_udp.Tpo -c net_udp.c -fPIC -DPIC -o .libs/net_udp.o net_udp.c: In function `udp_init6': net_udp.c:612: error: `IPV6_ADD_MEMBERSHIP' undeclared (first use in this functi on) cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/include -I/usr/X11R6/include -DDEBUG -I../.. -O -pipe -W -Wall -Wwrite-strings -Wbad-function-cast -Wmissing-prototypes -Wmissing-declarations -Werror -MT net_udp.lo -MD -MP -MF .deps/net_udp.Tpo -c net_udp.c -fPIC -DPIC -o .libs/net_udp.o net_udp.c: In function `udp_init6': net_udp.c:612: error: `IPV6_ADD_MEMBERSHIP' undeclared (first use in this function) net_udp.c:612: error: (Each undeclared identifier is reported only once net_udp.c:612: error: for each function it appears in.) net_udp.c: In function `udp_exit6': net_udp.c:654: error: `IPV6_DROP_MEMBERSHIP' undeclared (first use in this function) gmake[5]: *** [net_udp.lo] Error 1 gmake[5]: Leaving directory `/usr/ports/multimedia/mpeg4ip/work/mpeg4ip-1.1/lib/rtp' gmake[4]: *** [all-recursive] Error 1 gmake[4]: Leaving directory `/usr/ports/multimedia/mpeg4ip/work/mpeg4ip-1.1/lib/rtp' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/usr/ports/multimedia/mpeg4ip/work/mpeg4ip-1.1/lib/rtp' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/multimedia/mpeg4ip/work/mpeg4ip-1.1/lib' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/multimedia/mpeg4ip/work/mpeg4ip-1.1' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/multimedia/mpeg4ip. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade99436.25 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! multimedia/mpeg4ip (mpeg4ip-1.0) (compiler error) --- Packages processed: 0 done, 25 ignored, 0 skipped and 1 failed From that I'm suspecting that mpeg4ip might REQUIRE IPV6 support? Is that true? Why would this be the case? I have it commented out of my kernel. Could I be setting myself up for other problems by not using IPV6? Any insight appreciated... thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Man pages take forever on slow machine?
Ok so I got over my hurdle getting FreeBSD 5.3 installed on this old Presario (it ended up being RAM... needed more than 16MB to get through install, borrowed some and then could then back off to default 16MB after 5.3 was on). I thought I was on a roll until I accidentally tried to bring up a man page. It has been on Formatting page, please wait... ever since. I didn't pay attention to when, but I think it was at least an hour ago. Yes, an HOUR. And I still don't have my man page. Yes this isn't the fastest machine (I think it's a Pentium 133MHz, 16MB RAM) but really... I ran FreeBSD 2.2.2 as a webserver on a 486 66MHz back in the day. I'd expect this to be slow, but... 1+ hours for a man page? It's worse than that, though. I can't CTRL-C out. I get lots of ^C^C^C^C but it won't stop. I can use ALT-F2 and ALT-F3 to load up additional VTTYs but they are unresponsive... I type and nothing appears. Maybe if I come back a LONG while later I see some of my keystrokes. I was trying to do a good deed by recycling some old hardware my dad had and give him a FreeBSD server to learn with. But this is bizarre. Asking for a man page has brought this system to its knees. C'mon... it ran Windows 95. I think we can do better than this? It's not even going to be GUI. Any advice? Thanks in-advance... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hang on install of 5.3 on old Presario
I'm trying to breathe some life into some old hardware by giving it a task of a server. I've burnt the full 5.3 ISO to CD. I can get it to read the CD fine and start to boot. I get as far as the Welcome to FreeBSD menu (with the ASCII daemon). No matter what option I choose, the bar then spins for a moment and then the computer hangs. I've tried upgrading the BIOS to the latest offered from Compaq's website (although it's dated 1998). I've turned off PnP, and all unneeded ports (including serial, parallel, USB). I've tried both the DOS and Other setting for the HDD geometry. I've turned off all power-saving. Nothing seems to work. I've also tried using the 3 floppies... same problem. This is a Compaq Presario 4505 which won't be GUI. I'm trying to get my dad into FreeBSD, Apache, PHP, and so on. This was a machine he came up with for me to set up for him so he can screw around. It should work, since I've used a 486 as a web server before. Any ideas? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Restarting vino remotely
So I had to restart my home box the other day then realized while away that I forgot to launch vino-session, so I am unable to VNC to my local desktop. This seems to work me into a corner, as while I can still ssh into the computer, I cannot start vino-session from the remote ssh session because of DISPLAY issues. It insists on running from the local desktop. I've been researching since yesterday and haven't found any suggestions that work. Some posts mention xhost +localhost but when I try that I get: X connection to localhost:10.0 broken (explicit kill or server shutdown). I've also tried setting the DISPLAY variable to localhost:0 and localhost:0.0 as well as using the --display= command line parameter of vino-session to no avail. This isn't a critical issue but kinda inconvenient and bound to happen again. So I figured I'd ask the list: faced with a situation like this, what's the best way to bootstrap your way back into being able to VNC into your local desktop (localhost:0)? Thanks! = Fix most Windows problems here: http://vtbsd.net/winhelp/ Sick of ads/pop-ups/spam in AIM/Yahoo/MSN? http://www.jabber.org/ Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restarting vino remotely
--- Matthew Seaman [EMAIL PROTECTED] wrote: That means your ssh(1) session isn't doing X11 forwarding. ssh has he capability to pose as an X server, usually on localhost:10.0 and transparently forwards all X session traffic over an encrypted tunnel back to your desktop display, but only if you enable it. Hmm, well actually it IS enabled in the client I'm using but I'm not understanding why I'd need it. I'm using PuTTY, and under the session config in Connection - SSH - Tunnels the option for Enable X11 forwarding is checked with the X display location set to localhost:0. However, this is leftover from my days of experimenting with Cygwin (which I did have working but decided was too much of a pain). What I do these days is forward port 5900 over SSH for the sake of VNC and so the X11 forwarding isn't necessary. Secondly, you're telling X windows to display on the screen of the remote machine, which won't be a whole lot of use to you. Well my goal here is to restart vino-session, which is command-line and simply needs to spawn into the background, so I don't need to see it. And it seems to ONLY run from the screen of the host system, so (on the contrary) getting vino-session to run on its screen seems to be precisely what I'd want. I feel like I'm misunderstanding something fundamental here, or else I'm not communicating my situation very well. Instead, read about the '-X' and '-Y' options in ssh(1) and the equivalent 'ForwardX11' directive in ssh_config(5). Well I'm not using FreeBSD's ssh as I mentioned, I looked at -X though and saw it was just for the X11 forwarding that I already said I've got enabled in the SSH client I AM using (PuTTY) and I see no mention of -Y in the ssh man page to see what the equivalent PuTTY option might be. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to NOT load AGP?
Background: My computer likes to lock up sometimes in XFree86. This last time it was while doing an rsync between an internal drive and an external USB drive. But other times it's been random. Regardless, forced to do a reset, it then won't start XFree86. Sometimes unloading, rebuilding, and reinstalling the nvidia driver helps, sometimes not. Sometimes it takes several tries. When it hangs, it might hang on the nvidia splash screen, a white screen, or (like right now) still in terminal mode after startx before it even switches to graphical. This time I can't get it to go back into XFree86 no matter how many times I rebuild the nvidia driver, so I'm looking elsewhere. I even tried portupgrade -f XFree86* but no go. All along I've been using the FreeBSD AGP. I'm thinking maybe I need to try nvidia's (some people swear one way, some the other... if only there was consensus!). So I try rebuilding my kernel w/o device agp. Except the kernel build bombs at a weird point. Unable to find any reference to other people failing there, I suspect a corrupt /usr/src (perhaps due to one of my many lockups). So I rm -R and re-cvsup it. Then the build works. I also made sure that agp_load=YES was commented out of my /boot/loader.conf file. Well, upon rebooting I still see agp loading, confirmed w/ kldstat. So I try uncommenting the line but changing it to NO. Reboot, same thing. I do some more research, and try adding hint.agp.0.disabled=1 to my /boot/device.hints file. Reboot, but AGP is still loading. Argh. I can't even use kldunload to remove it. Ok, I appeal for help now. What's the proper way to keep AGP from loading so that I can test my nvidia driver using the nvidia AGP and see if that's even the sources of my XFree86 lockup problems? I need my desktop back. I'm on FreeBSD 5.2.1. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Package database corruption... need assistance
Hello. A friend of mine is running 5.1-REL and has somehow managed to get some serious corruption on her package database. It's more than I've come across before so I wanted to find out the easiest way to clean this up. The way things stand now, she gets lots of stale dependency errors when doing an pkgdb -F. Such as: Stale dependency: AbiWord2-gnome-2.0.3 - libIDL-0.8.2 (devel/libIDL): libvorbis-1.0.1,3 (score:18%) ? ([y]es/[n]o/[a]ll) [no] Which suggests that libIDL isn't installed... but according to ls /var/db/pkg it actually is. I had her try going into /usr/ports/devel/libIDL to do a make clean install but we get this: === Checking if devel/glib20 already installed pkg_info: /var/db/pkg/XFree86-fontCyrillic-4.3.0/+CONTENTS: No such file or directory *** Error code 1 Stop in /usr/ports/devel/glib20. *** Error code 1 Stop in /usr/ports/devel/libIDL. She has the folder /var/db/pkg/XFree86-fontCyrillic-4.3.0/ with some files (+COMMENT,+DESC,+MTREE_DIRS,+REQUIRED_BY) but not +CONTENTS. Presumably a lot of her other stale-dependency errors (and there are many from pkgdb -F) are also corrupted /var/db/pkg folders. What's the easiest way of fixing this? Do each of the problem programs need to be make deinstall and make clean reinstall? That's a lot. :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CMS on FreeBSD
I'm thinking about setting up a FreeBSD-based CMS/intranet and wanted to know what other people were doing. I have a tiny bit of experience with PHP-Nuke because my webhost uses it. Although I have no real complaints about it, I am not wedded to it. PHP-Nuke is in ports and was recently upgraded to 6.9 after stagnating at 6.0 for a long time. This makes me concerned that if I invested in it, and the need for an update came, I might be SOL for a while due to lack of a maintainer. As it is right now, it is marked FORBIDDEN due to a vulnerability with versions below 7.1. Also, there seems to be a lot of hatred towards PHP-Nuke. I don't claim to understand it, but I can accept they might know something I don't. I do know that PHP is rather easy for me to work with, as I've tweaked many pages on my hosted site. I am also not turned away by the fact that PHP-Nuke depends on MySQL as I have used it with Bugzilla and it doesn't scare me. Looking at other options, there comes Postnuke. Seems a pretty-popular close-relation to PHP-Nuke, however the version in ports seems 2+ years old. So there is the maintainership issue again. And a lot of people hate BOTH *Nukes, for perhaps good reasons I don't totally grasp, so there's that too. Diverging a bit, I noticed Drupal. Currently in ports but broken. Most promising seems Plone, which is based upon Zope. But it seems to be tremendously different from *nuke. The ports version is current and appears to work, but poking around the Plone site I wasn't able to get a feel for whether it truly can provide all the stuff I'm looking for. These are things such as: - Discussion forums - 3rd-party themes (I'm not looking to develop my own themes... I'm looking to get this up fast. Instead I'm looking for an established community of Plone-theme creators who like to create custom themes available for download, so I can pick one that appeals to me) - Polls - a variety of other modules/blocks (strength of the *nukes, but couldn't find a similar following for Plone). I'm also concerned about Plone using its own webserver. I feel very good using Apache as I've a lot of experience with it, and I like the idea of delegating components to groups with that strength. I also don't know Python, but could try and learn if Plone was worth it. This would be for an intranet site for about 100 employees. Looking to replace the mass-mailed MS Word newsletter, as well as provide a place to centrally discuss topics without having to try and hold meetings (and leaving things unaddressed because you're unable to pull a meeting together), give people a classifieds board, etc. What are other people doing for CMS on FreeBSD? Just how different is Plone from the *Nukes? Are there fundamental differences I need to understand? Can I do everything I want to with Plone without having to become a Python expert, code my own modules, etc? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CMS on FreeBSD
On Fri, 19 Mar 2004 14:05:45 -0600, Dan Rue wrote: Umm.. I don't know what other people think about this - but I really never run any PHP stuff from ports. It is easier, imo, to just download the tgz and unzip it to the directory you want it in. Since there's no compiling, usually very little setup, it's just _easier_ and gives you more control if you just do it yourself. Of course, the cruddy thing about that is updating. Therefore, the reason why I think the cms' in ports are old is because most people don't port install them - it's just not worth it. Ahh, I see. That would explain a lot, then. Makes sense. As far as which cms to use, I'm currently undecided as well. My boss really likes drupal, and forces me to use it :) Drupal looks really nice. Do you have any thoughts on Drupal vs. Mambo? Check out opensourcecms.com - they showcase dozens of php cms' and let you try them out. Beat ya to it... I already stumbled across it just a short while ago and am currently playing around. :) Hmmm it occurred to me that one module/component I'd really be interested in is some sort of organized (hierarchy) knowledgebase that is also searchable. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Try $ hd /dev/...| grep -A 5 02 00 00 00 0c 00 04 01 2e 00 00 00 02 00 00 00 Well that definitely produced something: bash-2.05b# hd /dev/ad2s1e | grep -A 5 02 00 00 00 0c 00 04 01 2e 00 00 00 02 00 00 002d 02 00 00 00 0c 00 04 01 2e 00 00 00 02 00 00 00 || 002d0010 0c 00 04 02 2e 2a 00 00 00 a0 09 00 10 00 04 00 |.*..| 002d0020 70 69 63 73 00 10 6a c0 00 f8 40 00 14 00 04 08 |[EMAIL PROTECTED]| 002d0030 6f 68 64 5b 6e 70 66 73 00 00 00 00 03 00 00 00 |ohd[npfs| 002d0040 14 00 08 0a 58 42 38 32 43 6b 6e 62 69 63 00 d9 |XB82Cknbic..| 002d0050 00 00 63 00 0c 00 04 03 65 70 63 00 00 58 63 00 |..c.epc..Xc.| -- 002f4000 02 00 00 00 0c 00 04 01 2e 00 00 00 02 00 00 00 || 002f4010 0c 00 04 02 2e 2e 00 00 00 a0 09 00 10 00 04 04 || 002f4020 70 69 63 73 00 14 6a c4 00 f8 40 00 14 00 04 08 |[EMAIL PROTECTED]| 002f4030 6f 6c 64 5f 6e 74 66 73 00 00 00 00 03 00 00 00 |old_ntfs| 002f4040 14 00 08 0a 58 46 38 36 43 6f 6e 66 69 67 00 d9 |XF86Config..| 002f4050 00 00 63 00 0c 00 04 03 65 74 63 00 00 58 63 00 |..c.etc..Xc.| That second one seems to be more intact. pics and old_ntfs and X were directories off /data (there were others). The first match would appear to be slightly corrupted (that etc might have been a backup I made of /etc at some point in case of / failure). It's still churning away but I'm going to assume that it's found all it's going going to and send this email now. For what it's worth, FedEx is estimating Monday the 23rd as delivery of the spare 80GB. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Here you should have answered `y' (it doesn't ask you to change anything yet). Let's try that again, shall we? Sorry, ok I went through it again, saying Y to all the Continue? prompts but N to all the ones that talked about changing things. The final result was huge, so instead of posting it here I'll host it on my site: http://vtbsd.net/fschk.txt Well, after all fsck doesn't seem mad (`erase everything and mark fs clean'). But if you are really are paranoid, as you should be, you should copy the whole contents of the harddrive, maybe to a remote machine, by dd (over NFS, perhaps). Perhaps the `sparse' dd option would help save a bit of space (by creating `holes' in the file where there were NUL's on the harddrive). I have ordered an additional 80GB drive for this very purpose (along w/ an external USB enclosure but we don't have to get that working yet). I will let you know when it arrives. If the next step you want to do is going to make changes, I'm happy to wait until the 2nd drive is here and we can do the dd. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Sorry, you were recovering an 80G disk, and now you say the 80G has 4.9 on it. Did you erase anything? Is this a remote machine? No, it was not the drive that had the OS on it. It was originally mounted as /data on a system that had FreeBSD 5.1 installed on a separate drive. We determined the 80GB was UFS1. You wanted to try troubleshooting using FreeBSD 4.9, so I obtained a spare system which I installed FreeBSD 4.9-RELEASE on. I then moved the 80GB from the 5.1 system (which is actually 5.2 now) and installed it into the 4.9 system on the 2nd controller. So now 4.9 is installed on a 20GB on /dev/ad0, and our problem 80GB is /dev/ad2. You can boot 4.9, right? Examine the output of disklabel ...s1 and ...s1c to make heart feel better. bash-2.05b# disklabel /dev/ad2s1 # /dev/ad2s1: type: ESDI disk: ad6s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 9731 sectors/unit: 156344517 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: 1563445170unused0 0# (Cyl.0 - 9731*) e: 15634451704.2BSD 2048 1638489 # (Cyl.0 - 9731*) bash-2.05b# disklabel /dev/ad2s1c # /dev/ad2s1c: type: ESDI disk: ad6s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 9731 sectors/unit: 156344517 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: 1563445170unused0 0# (Cyl.0 - 9731*) e: 15634451704.2BSD 2048 1638489 # (Cyl.0 - 9731*) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Well, as it's UFS1 as we've figured out, the next logical thing would be to try mounting /dev/ad2s1c r/o, and if that fails, try fscking it. bash-2.05b# mount -r /dev/ad2s1c /data mount: /dev/ad2s1c on /data: incorrect super block bash-2.05b# fsck /dev/ad2s1c ** /dev/ad2s1c BAD SUPER BLOCK: MAGIC NUMBER WRONG /dev/ad2s1c: NOT LABELED AS A BSD FILE SYSTEM (unused) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: And /dev/ad2s1e? bash-2.05b# mount -r /dev/ad2s1e /data mount: /dev/ad2s1e on /data: incorrect super block bash-2.05b# fsck /dev/ad2s1e ** /dev/ad2s1e BAD SUPER BLOCK: MAGIC NUMBER WRONG LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes 416 BAD I=2 412 BAD I=3 424 BAD I=4 414 BAD I=4 417 BAD I=5 INCORRECT BLOCK COUNT I=4257794 (8928 should be 9952) CORRECT? [yn] Hmmm that looks more promising, although I'm not sure exactly what it's trying to warn me about, or how bad things are from that, so I'm going to leave it there for now. :) And if I remember correctly, even though fsck has used an alternate superblock to perform the repair process, it hasn't actually replaced the master superblock with the alternate one, so I'd still need to fix that manually somehow... correct? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Try using fsck -n (answer `no'), and recording what else comes up. That won't work, because it answers no to the first question of looking for alternate superblocks, then aborts immediately. So I'm just going to manually say no to all questions after yes to the first: bash-2.05b# fsck /dev/ad2s1e ** /dev/ad2s1e BAD SUPER BLOCK: MAGIC NUMBER WRONG LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes 416 BAD I=2 412 BAD I=3 424 BAD I=4 414 BAD I=4 417 BAD I=5 INCORRECT BLOCK COUNT I=4257794 (8928 should be 9952) CORRECT? [yn] n 17227776 DUP I=4257795 1722 DUP I=4257795 17227778 DUP I=4257795 17227779 DUP I=4257795 17227780 DUP I=4257795 17227781 DUP I=4257795 17227782 DUP I=4257795 17227783 DUP I=4257795 17227784 DUP I=4257795 17227785 DUP I=4257795 17227786 DUP I=4257795 EXCESSIVE DUP BLKS I=4257795 CONTINUE? [yn] n UPDATE STANDARD SUPERBLOCK? [yn] n * FILE SYSTEM MARKED DIRTY * If you know what fsdb(8) is, it might be helpful (still with the -r (read-only) option, and the -d option as well). I don't, but I'm learning it intensively at the moment:). I don't, and the man page sufficiently put the fear of the almighty in me as far as it goes Use this tool with extreme caution--you can damage an FFS file system beyond what fsck(8) can repair. It's also a bit out of my league as far as understanding how to make use of it. so I'd still need to fix that manually somehow... correct? Yes, by means of dd. Hmm although that last fsck question UPDATE STANDARD SUPERBLOCK? [yn] seemed interesting. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
Hello, gentlemen. For those of you still interested in this little adventure, I now have the 80GB drive mounted on the 2nd IDE controller in its own dedicated FreeBSD 4.9-RELEASE system. ad0: 19092MB WDC WD200BB-75AUA1 [38792/16/63] at ata0-master UDMA100 ad2: 76345MB MAXTOR 6L080J4 [155114/16/63] at ata1-master UDMA33 I'm ready to proceed if you're still willing, if not I understand! :) (If anyone else new to this problem and would like to help, you can use google or the archives, or I can catch you up if you'd like) Many thanks already to all who have helped so far. = Scott I. Remick --==-- Jabber IM: [EMAIL PROTECTED] Save the internet - Use a Mozilla-based browser: http://vtbsd.net/mozilla/ Jabber - Ad-free, and because MSN and AIM just plain suck: http://www.jabber.org/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. http://vtbsd.net/freebsd/ Out with Eisner, bring back Disney: http://www.savedisney.com/ A: Because it reverses the logical flow of conversation. Q: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenOffice 1.1 port
On Fri, 30 Jan 2004 09:48:04 -0800, Derrick Ryalls wrote: Install the prebuild binary instead (saves a ton of time too): http://projects.imp.ch/openoffice/ Except then you don't get anti-aliased fonts :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgraded 5.1 - 5.2, now VNC over SSH fails w/ TCP_NODELAY
On Tue, 20 Jan 2004 11:42:28 -0500, Scott I. Remick wrote: Well crap, everything was going so well. I upgraded from 5.1 to 5.2 using cvsup, recompiled (nearly) all my ports (some KDE stuff is still complaining, but that shouldn't be relevant here). I have openssh installed via ports: su-2.05b# pkg_info | grep ssh openssh-3.6.1_5 OpenBSD's secure shell client and server (remote login prog And my /etc/rc.conf contains: sshd_enable=YES sshd_program=/usr/local/sbin/sshd Under 5.1, I'd SSH in (via PuTTY), then use port-forwarding to forward localhost:7001 to remote:5901. I could then run VNC, connect to localhost:7001, and tunnel my VNC session over SSH. Since upgrading to 5.2 (nothing else has changed), while I can still SSH in, attempting to tunnel VNC fails and I get the following error in my PuTTY log: 2004-01-20 11:34:21 Opening forwarded connection to localhost:5901 2004-01-20 11:34:22 Forwarded connection refused by server On the FreeBSD box, I see: Jan 20 11:33:57 scott sshd[78580]: error: getsockopt TCP_NODELAY: Connection reset by peer This is using the same configs, profiles, etc. Nothing has changed except the upgrade of the FreeBSD box from 5.1 to 5.2. Any thoughts? Sorry to reply to my own post, but I'm still stuck and had more info to offer. I've also tried adding the following line to my rc.conf: sshd_flags=-f /usr/local/etc/ssh/sshd_config And in that sshd_config file, I added the following lines: GatewayPorts yes Although I'm not sure this applies. It's definitely using that config: su-2.05b# ps -ax | grep sshd 426 ?? Is 0:00.07 /usr/local/sbin/sshd -f /usr/local/etc/ssh/sshd_config 1807 ?? Is 0:00.03 sshd: scott [priv] (sshd) 1809 ?? R 0:00.07 sshd: [EMAIL PROTECTED] (sshd) vncserver is definitely running: su-2.05b# ps -ax | grep vnc 1798 p0- S 0:00.23 Xvnc :1 -desktop X -httpd /usr/X11R6/share/tightvnc/classes -auth /home/scott Also: su-2.05b# strobe -b 5900 -e 6000 localhost strobe 1.05 (c) 1995-1999 Julian Assange [EMAIL PROTECTED]. localhost 5901 unassigned unknown - RFB 003.003\n I've also confirmed that I can VNC in using another PC on the local network. But none of this has helped and I still get the error when I try to tunnel VNC over ssh. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgraded 5.1 - 5.2, now VNC over SSH fails w/ TCP_NODELAY
Well crap, everything was going so well. I upgraded from 5.1 to 5.2 using cvsup, recompiled (nearly) all my ports (some KDE stuff is still complaining, but that shouldn't be relevant here). I have openssh installed via ports: su-2.05b# pkg_info | grep ssh openssh-3.6.1_5 OpenBSD's secure shell client and server (remote login prog And my /etc/rc.conf contains: sshd_enable=YES sshd_program=/usr/local/sbin/sshd Under 5.1, I'd SSH in (via PuTTY), then use port-forwarding to forward localhost:7001 to remote:5901. I could then run VNC, connect to localhost:7001, and tunnel my VNC session over SSH. Since upgrading to 5.2 (nothing else has changed), while I can still SSH in, attempting to tunnel VNC fails and I get the following error in my PuTTY log: 2004-01-20 11:34:21 Opening forwarded connection to localhost:5901 2004-01-20 11:34:22 Forwarded connection refused by server On the FreeBSD box, I see: Jan 20 11:33:57 scott sshd[78580]: error: getsockopt TCP_NODELAY: Connection reset by peer This is using the same configs, profiles, etc. Nothing has changed except the upgrade of the FreeBSD box from 5.1 to 5.2. Any thoughts? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems using portupgrade to recompile all ports
So I'm upgrading my 5.1R desktop to 5.2R. Used cvsup, followed the instructions in UPGRADING, did a custom kernel, etc etc. That part went fine, no probs. I noticed some of my daemons (from ports) seemed a bit annoyed though upon booting up 5.2. I tried using portupgrade -Rf on them individually, and then all was well. I decided then that it'd be best to do everything (-Raf) to play it safe. I've done this before. So it finally finished last night, but not really... about 132 ports were failed/skipped. My problem is figuring out the most efficient way to deal with it from here. LAST time I did a portupgrade -Raf I had a much smaller number failed/skipped, and what I did was work out the dependency tree for the remaining ones by hand using pkg_info -R and -r, figure out the order, and do a portupgrade -f on each in the proper order. This was to avoid rebuilding stuff already built on the first -Raf pass, and multiple times over (since I was taking care of each remaining one individually). Seems to me that if 50 of those 132 are X apps and I do a portupgrade -Rf on each, I'll be rebuilding XFree86 50 times. Hence the need to work out the install order by-hand based upon dependencies and only use -f. But I don't see that as practical this time around with so many left to do. So... my ultimate question is: how do you pros handle situations like this? Is there a trick I'm missing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NEWBIE QUESTION
On Thu, 15 Jan 2004 15:47:08 +, Donald Turnbull wrote: I'm a newbie to your OS, Does Free BSD have the KDE and Gnome GUI already installed? Already installed? No. A large number people want to run FreeBSD on their servers, and having a GUI on a server isn't usually a good or desired thing. Another large number of people want a GUI but don't want KDE or Gnome, so forcing this onto them would also be a disservice. FreeBSD is partially about choice. The same as it promotes OS choice in a world dominated by Windows, it also allows and encourages choice in its components, notably the window manager or (in the case of Gnome and KDE) the desktop environment. Or the use of one altogether, as in the case for servers. HOWEVER... it is insanely easy to install, with one command, via ports. The ports tree is your friend, and perhaps one of FreeBSD's most notable advantages over all other OSes. There are over 10,000 items in the ports tree that are no more than a make clean install away. You can take a vanilla FreeBSD install, install Gnome and have it install all it's bazillion dependencies (and XFree86 and all ITS dependencies) all in one swoop with a single command. Do you have plans in making the installation more user friendly in the future? It really isn't all that bad now. I'm guessing you'd prefer a GUI installer, but there are a number of reasons this would Bad Idea and make more people unhappy than the current system (again, take the case of servers, or the ability of the current installer to work on pretty much anything). The biggest problem people have with the FreeBSD installer is that it is different than what they're used to. Don't condemn it because you haven't learned the (valid) reasons for its differences, and how to make use of it. I've spent most my computing life with Windows, but I can blow through a FreeBSD install within 3-5 mins. Do THAT with Windows. ;-) Welcome to FreeBSD... hope your stay is a long one! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems using portupgrade to recompile all ports
On Thu, 15 Jan 2004 16:02:44 + (GMT), Jan Grant wrote: On Thu, 15 Jan 2004, Scott I. Remick wrote: So I'm upgrading my 5.1R desktop to 5.2R. Used cvsup, followed the instructions in UPGRADING, did a custom kernel, etc etc. That part went fine, no probs. I noticed some of my daemons (from ports) seemed a bit annoyed though upon booting up 5.2. I tried using portupgrade -Rf on them individually, and then all was well. I decided then that it'd be best to do everything (-Raf) to play it safe. I've done this before. So it finally finished last night, but not really... about 132 ports were failed/skipped. My problem is figuring out the most efficient way to deal with it from here. LAST time I did a portupgrade -Raf I had a much smaller number failed/skipped, and what I did was work out the dependency tree for the remaining ones by hand using pkg_info -R and -r, figure out the order, and do a portupgrade -f on each in the proper order. This was to avoid rebuilding stuff already built on the first -Raf pass, and multiple times over (since I was taking care of each remaining one individually). Seems to me that if 50 of those 132 are X apps and I do a portupgrade -Rf on each, I'll be rebuilding XFree86 50 times. Hence the need to work out the install order by-hand based upon dependencies and only use -f. But I don't see that as practical this time around with so many left to do. So... my ultimate question is: how do you pros handle situations like this? Is there a trick I'm missing? Do you know why the failure happened? The most frequent cause of this when I've encountered the problem is that a distfile could not be fetched. I tend to try to avoid that these days by prefetching the distfiles prior to a build (ie, while I'm around to sort out problems manually rather than overnight). Various reasons. I could post the full list at the end if you'd like (I saved it). Most are skipped (*) due to dependencies on the ones that failed (!). For the failed ones, I got assorted errors: unknown build error, install error, checksum mismatch, linker error, new compiler error, missing header. The ones marked ! failed isn't so large I couldn't investigate/fix each individually, but I'm trying to figure out the best way to deal with the full list of failed/skipped so that once I fix the reason for the failures, I can JUST rebuild those in the failed/skipped list and in the proper order, instead of having to rebuild my entire (400+) ports list again w/ -Raf, most of which compiled fine under 5.2. Hopefully I'm making sense... :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems using portupgrade to recompile all ports
On Thu, 15 Jan 2004 17:12:27 +, Matthew Seaman wrote: Work out what went wrong, fix it and then just run: # portupgrade -af '2004-01-15' which does a forced update of all packages installed before the given date. (Note: -R and -r are unnecessary with -a). Rinse, repeat. Until all your ports are up to date. Excellent! That should do EXACTLY what I needed. Thank you so much. Usually ports problems are either inability to download the required distfiles or a temporary SNAFU by the port maintainer/committer. In most cases it suffices to wait a few hours or days, re-cvsup the ports tree and start the portupgrade job again. Yeah that was my plan... I'm well-familiar with ports-tree hiccups. I have plenty of other things to do to pass the time while I sort this out (like install 4.9 on a separate drive to try and fix a UFS1 volume I cannot access due to a bad superblock. Or play with my new Palm Tungsten T3 once it arrives) One question: it's not clear from man pkg_glob whether I can combine the date format '2004-01-15' with a package name, so that I only update the dependencies of a SPECIFIC package that are older than that date (using -f instead of -af of course). Is there a syntax to do that? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems using portupgrade to recompile all ports
On Thu, 15 Jan 2004 17:38:41 +, Matthew Seaman wrote: portupgrade -rfx '=2004-01-15' foo will force re-install 'foo' and everything that depends on package 'foo', except those packages installed on or after the given date. Well, actually I want -R and not -r, but anyways.. almost, but not quite: su-2.05b# portupgrade -Rfx '=2004-01-14' docbook-xsl ** All the packages matching 'docbook-xsl' were excluded. ** No such package 'docbook-xsl' is installed. So -x is picking up the package name too. Don't want that. So I try: portupgrade -Rf docbook-xsl -x '=2004-01-14' And that seems to work. I've used it with a bunch of my originally-failed ports and making progress. A lot of them are failing with local modification time does not match remote but I delete the file from /usr/ports/distfiles and all is well. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I mean trying to mount it, to fsck it, using dd|hd to find the superblock, etc. I just want to be *really* sure we know what we are doing. Well, I don't have experience making bootable FreeBSD floppies... it might be more useful for me to grab a small spare HDD and install 4.9 on it. Should I do that and get back to you once I'm ready? While we are on that, do you have an empty disk to copy this disk's contents to? I'm not sure, but maybe I have an idea... I could probably come up with something. Would it have to be installed in the machine, or just available on the network? Unfortunately I don't remember how much data was used on that drive so I don't know what my goal is. :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Malcolm Kay [EMAIL PROTECTED] wrote: Beware; if you write a disklabel (or presumably bsdlabel; I have no experience with 5.x) to ad6 you create a dangerously dedicated disk, i.e. a disk without slices. Ok. I am not saying that's what I want to do, I only mentioned it because the man page for disklabel/bsdlabel uses the entire disk (/dev/da0) as an example. man disklabel brings up bsdlabel, which is why I mention bsdlabel instead. http://www.freebsd.org/cgi/man.cgi?query=bsdlabel Are you saying that the disklabels reported for ad6s1 and ad6s1c are different? This is correct. Your surprise suggests that it was good I mentioned that, eh? :) Glad I haven't done anything yet. In summary, ad6s1 returns an offset of 0 and no error. ad6s1c returns an offset of 63 and the rest of the info is identical except for the following error tagged on at the end: partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition e: partition extends past end of unit Under FreeBSD 4.x ad6s1 and ad6s1c would normally be aliases referencing the entire slice. Maybe 5.x is different! I'm now very confused. I'm not sure... maybe Sergey wants to pipe in here on this point? What is reported by fdisk? Ah, I'm at work now. Can't do that from here... I'll let you know later. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: And maybe prefix that by a $ bsdlabel -R /dev/ad6s1c dislabel.ad6s1c.new which would just check your new layout for errors, without writing anything, and print your file out as disklabel understands it. So you're saying, run it as user and not root for the sake of testing it in a read-only setting? Would that be better than using -n? From the man page: The -n stops the bsdlabel program right before the disk would have been modified, and displays the result instead of writing it. And lastly... your talk about offsets. The man page for bsdlabel describes using it on the whole disk (ad6) and not a slice or partition. If I run it It can't be fdisk that you are reading about? Nope. man bsdlabel mentions: disk represents the disk in question, and may be in the form da0 or /dev/da0. It will display the partition layout. But I see now all the later examples mention da0s1 so maybe I misunderstood. And the `new' one seems to be correct for a 80G drive (+- a couple of megabytes)? Have you touched anything? Now, mount might work. Haven't changed anything yet. Which one are you calling the new one? Mount would be done on the partion (ad6s1c) which gives errors with bsdlabel and has an offset of 63, not the whole slice (ad6s1) which has an offset of 0 and doesn't give errors (with bsdlabel). Uhum. disklabel said that the offset was 63 in your previous posting, didn't it? 63 for ad6s1c, 0 for ad6s1. This is what's got Malcolm confused. What does # ls -l /dev/ad6s1 /dev/ad6s1c say? Any differences? I have none. su-2.05b# ls -l /dev/ad6s1 /dev/ad6s1c crw-r- 1 root operator4, 20 Dec 29 08:11 /dev/ad6s1 crw-r- 1 root operator4, 21 Dec 29 08:11 /dev/ad6s1c And to recap: su-2.05b# bsdlabel /dev/ad6s1 # /dev/ad6s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 1563445170unused0 0 # raw part, don't edit e: 15634451704.2BSD 2048 1638489 su-2.05b# bsdlabel /dev/ad6s1c # /dev/ad6s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 156344517 63unused0 0 # raw part, don't edit e: 156344517 634.2BSD 2048 1638489 partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition e: partition extends past end of unit ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Sorry that was to be $ bsdlabel -R -n /dev/ad6s1c dislabel.ad6s1c.new :( No worries... I figured it out :) Indeed it's not like in 4.x, where they were the same. And what about # ls -l /dev/ad6s1a /dev/ad6s1b (these minor numbers don't seem to be in order). Neither exists. Just so you know: My motherboard (Asus A7V133) has 2 integrated IDE controllers. Besides the native VIA controller there is a Promise ATA100. The following are the relevant snippets from dmesg: atapci0: VIA 82C686B UDMA100 controller port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: Promise PDC20265 UDMA100 controller port 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 mem 0xd400-0xd401 irq 10 at device 17.0 on pci0 ata2: at 0x9400 on atapci1 ata3: at 0x8800 on atapci1 ad4: 19595MB MAXTOR 6L020L1 [39813/16/63] at ata2-master UDMA100 ad6: 76345MB MAXTOR 6L080J4 [155114/16/63] at ata3-master UDMA100 acd0: CDROM CRD-8400B at ata0-master PIO4 Mounting root from ufs:/dev/ad4s1a cd0 at ata0 bus 0 target 0 lun 0 cd0: LG CD-ROM CRD-8400B 1.03 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [279440 x 2048 byte records] (yes, I use atapicam) and ls /dev/ad*: crw-r- 1 root operator4, 10 Dec 29 08:11 /dev/ad4 crw-r- 1 root operator4, 12 Dec 29 08:11 /dev/ad4s1 crw-r- 1 root operator4, 14 Dec 29 03:11 /dev/ad4s1a crw-r- 1 root operator4, 15 Dec 29 08:11 /dev/ad4s1b crw-r- 1 root operator4, 16 Dec 29 08:11 /dev/ad4s1c crw-r- 1 root operator4, 17 Dec 29 03:11 /dev/ad4s1d crw-r- 1 root operator4, 18 Dec 29 03:11 /dev/ad4s1e crw-r- 1 root operator4, 19 Dec 29 03:11 /dev/ad4s1f crw-r- 1 root operator4, 13 Dec 29 08:11 /dev/ad6 crw-r- 1 root operator4, 20 Dec 29 08:11 /dev/ad6s1 crw-r- 1 root operator4, 21 Dec 29 08:11 /dev/ad6s1c crw-r- 1 root operator4, 22 Dec 29 08:11 /dev/ad6s1e Let me know if you come up with any suggestions on what I should try next. Thanks ever so much! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I'm in the process of downloading the floppies... ok cool And what about ad4? Does disklabel show different values for the slice and the `c' partition? Hmm not only are they different as w/ ad6, but I get the same error on the c partition: su-2.05b# bsdlabel /dev/ad4s1 # /dev/ad4s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 102400004.2BSD 2048 16384 64008 b: 2097152 1024000 swap c: 401314410unused0 0 # raw part, don't edit d: 524288 31211524.2BSD 2048 16384 32776 e: 1024000 36454404.2BSD 2048 16384 64008 f: 35462001 46694404.2BSD 2048 16384 28552 su-2.05b# bsdlabel /dev/ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1024000 634.2BSD 2048 16384 64008 b: 2097152 1024063 swap c: 40131441 63unused0 0 # raw part, don't edit d: 524288 31212154.2BSD 2048 16384 32776 e: 1024000 36455034.2BSD 2048 16384 64008 f: 35462001 46695034.2BSD 2048 16384 28552 partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition f: partition extends past end of unit The plot thickens... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I can't find a zero-bad floppy in this place! It's all the holidays! That's what AOL disks (vs. discs) used to be good for. :) With `c', they're all offset by 63(why?). But still, you can mount the partitions on the ad4s1, so the disklabel should be ok... Yeah. Starts to suggest what we were thinking was a evidence related to the problem is really unrelated and normal behavior (is disklabel/bsdlabel only meant to be run on slices and not bsd-partitions?). Are we looking in the wrong place? What about that potentially good superblock we found a while ago? (the skip 16 one that contained /data in it) Should we be saving that somewhere while we can? (how?) Anyone out there know 5.x file-system dirtiness like the back of their hand? C'mon, you know you wanna join the fun. :) Where's my time machine so I can go back and back up this drive... ah well I'm learning a ton. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I think you already have a copy (the data at offset 32 seems to be it). If you want, do a # dd if=/dev/ad6s1 skip=16 count=16 of=/some/file ok, done. Is there a way to use fsck_ufs -b now to fix this? Or is that premature? And if I remember correctly, that doesn't actually APPLY the alternate superblock... it just allows fsck to run while utilizing an alternate one. So we need to use some sort of dd command to copy it to the proper location, correct? Please tell me everything what you tried to use to mount/fsck the drive (and the results, of course). Well, my memory is sketchy so I don't know how much use it'd be. But I was saving a file to /data (ad6) when the system hung. Then it rebooted on its own. Of course fsck ran on bootup but it gave up and told me I had to run it manually. When I did (I don't remember any parameters I specifically used, if any) I got: /dev/ad6s1c Cannot find file system superblock /dev/ad6s1c: NOT LABELED AS A BSD FILE SYSTEM I remember there being some of the other common message for little things that you just tell it to go ahead and fix. But the above error was a brick wall and would keep me from going multi-user. Ultimately I had to comment-out the line in fstab: #/dev/ad6s1c/data ufs rw 2 2 So I could at least boot. And that's the way I've been ever since. Trying to mount it now gives: su-2.05b# mount -r /dev/ad6s1c /data mount: /dev/ad6s1c on /data: incorrect super block And so we stand. Try booting from a 4.x floppy and doing it all over again... The FS is UFS1, isn't it? Ummm... doing what all over again? Wipe the disk and redo the partitions? I hope we're not quite there yet. How does using 4.x give me an advantage over 5.1? I'm not clear on that part. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Jerry McAllister [EMAIL PROTECTED] wrote: (is disklabel/bsdlabel only meant to be run on slices and not bsd-partitions?). You have it backwards in this question. Disklabel is meant to run only on bsd partitions and not slices. Slices (1-4) are the major divisions of the disk and partitions (a-h) are divisions within slices. Fdisk is what creates slices. Ok, well the reason I thought it might be the other way is because if you run disklabel (bsdlabel) on a slice (such as /dev/ad4s1 on my machine, which is working, or /dev/ad0s1 on another machine I have access to) it works fine (and reports an offset of 0), but if you run it on the partition (/dev/ad0s1c) you get an offset of 63 and errors like: partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition f: partition extends past end of unit So why does disklabel/bsdlabel produce errors when run on the partition even when the disk is fine, if it is meant to be run on partitions and not slices? Trying to learn... thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Malcolm Kay [EMAIL PROTECTED] wrote: This is true. That partition is labeled as unused. I believe you should be trying to mount /dev/ad6s1e. su-2.05b# mount -r /dev/ad6s1e /data mount: /dev/ad6s1e on /data: incorrect super block #/dev/ad6s1c/data ufs rw 2 2 Certainly wrong in 4.x, I suspect also wrong in 5.x. Yikes, well that's the way it had been for about a year. How come it worked? I must have made an inexperienced mistake early on, but it WAS working. Can this be fixed? Do you have a line mounting ad4s1c for the other disk? No, that's the only one using the c partition. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
Sorry for the delay... holidays had me busy. Hopefully you're still around and interested in picking up where we left off. I think we're definitely onto something... --- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: su-2.05b# hd /dev/ad6s1 | grep 54 19 01 00 1620 54 19 01 00 74 10 68 81 23 00 00 e8 d5 03 00 00 |T...t.h.#...| These: 2550 01 00 00 00 00 00 00 00 00 00 00 00 54 19 01 00 |T...| 4550 01 00 00 00 00 00 00 00 00 00 00 00 54 19 01 00 |T...| 002e6550 01 00 00 00 00 00 00 00 00 00 00 00 54 19 01 00 DON'T look like false positives. They're just what you were supposed to get. Let's have a look at # dd if=/dev/ad6s1 skip=16 |hd su-2.05b# dd if=/dev/ad6s1 skip=16 |hd 00 04 00 04 00 04 00 04 08 04 00 04 10 04 00 04 || 0010 18 04 00 04 98 05 00 00 00 00 00 00 ff ff ff ff || 0020 9e 8d cd 3f 31 6c 54 06 d5 15 4b 06 ad 05 00 04 |...?1lT...K.| 0030 00 44 00 04 00 0c 00 04 08 04 00 04 08 04 00 04 |.D..| 0040 00 04 00 04 3c 04 00 00 00 c0 ff ff 00 fc ff ff |...| 0050 0e 04 00 04 0b 04 00 00 07 00 00 00 00 10 00 00 || 0060 03 00 00 00 02 00 00 00 00 08 00 00 00 fc ff ff || 0070 0a 04 00 04 00 14 00 04 80 04 00 04 04 04 00 04 || 0080 00 04 00 04 00 14 00 04 01 04 00 04 00 04 00 04 || 0090 00 ec 01 3f f2 6d 8d 6c 98 05 00 00 00 20 00 00 |...?.m.l. ..| 00a0 00 40 00 00 01 00 00 00 00 10 00 00 00 10 00 00 |[EMAIL PROTECTED]| 00b0 1b 95 00 04 59 04 00 04 00 5c 00 04 00 64 01 04 |Y\...d..| 00c0 34 0c 00 00 1e 25 31 04 b9 8c 92 04 1b 1f 00 04 |4%1.| 00d0 00 04 00 86 2f 64 61 74 61 04 00 04 00 04 00 04 |/data...| 00e0 00 04 00 04 00 04 00 04 00 04 00 04 00 04 00 04 || # dd if=/dev/ad6s1 skip=32 |hd su-2.05b# dd if=/dev/ad6s1 skip=32 |hd 00 00 00 00 00 00 00 00 08 00 00 00 10 00 00 00 || 0010 18 00 00 00 98 05 00 00 00 04 00 00 ff ff ff ff || 0020 00 ec 01 3f 31 68 54 02 d5 15 4b 02 ad 01 00 00 |...?1hT...K.| 0030 00 40 00 00 00 08 00 00 08 00 00 00 08 00 00 00 |[EMAIL PROTECTED]| 0040 00 00 00 00 3c 00 00 00 00 c0 ff ff 00 f8 ff ff |...| 0050 0e 00 00 00 0b 00 00 00 07 00 00 00 00 10 00 00 || 0060 03 00 00 00 02 00 00 00 00 08 00 00 00 fc ff ff || 0070 0a 00 00 00 00 10 00 00 80 00 00 00 04 00 00 00 || 0080 00 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 || 0090 00 ec 01 3f f2 6d 8d 6c 98 05 00 00 00 20 00 00 |...?.m.l. ..| 00a0 00 40 00 00 01 00 00 00 00 10 00 00 00 10 00 00 |[EMAIL PROTECTED]| 00b0 1b 95 00 00 59 00 00 00 00 58 00 00 00 64 01 00 |YX...d..| 00c0 01 00 00 00 b9 62 49 00 fd 77 93 00 0c 00 00 00 |.bI..w..| 00d0 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || I see /data in that first one, so I'm getting hopeful ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I wonder whether editing the label and setting both offsets to 0 might solve the problem. It definitely seems like that, as the actual offset of the partition is 0, as dd shows. Ok, sounds like a plan. Not that I know what I'm doing. Should I use something like the following command to save my current disklabel? bsdlabel /dev/ad6s1c disklabel.ad6s1c.backup Then do I just edit a copy of that textfile, change the offsets to 0, then write it back like this? bsdlabel -R /dev/ad6s1c dislabel.ad6s1c.new And lastly... your talk about offsets. The man page for bsdlabel describes using it on the whole disk (ad6) and not a slice or partition. If I run it on ad6, I get: bsdlabel: /dev/ad6: no valid label found If I run it on the slice ad6s1 I get: # /dev/ad6s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 1563445170unused0 0 # raw part, don't edit e: 15634451704.2BSD 2048 1638489 And there I see the offset of 0 you might be talking about...? Are we looking at the proper label? Just want to make sure before I mess things up. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kazaa client
On Tue, 23 Dec 2003 04:08:55 +0200, Anton Alin-Adrian wrote: Thanks. Seems I am going to develop a GTK UI for fasttrack ;P Hmm maybe as an easier start, someone can add giFToxic to the FreeBSD ports collection? http://giftoxic.sourceforge.net/ Porting is currently outside my own abilities. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Straightening out perl
Maybe this belongs in the -ports list... I dunno. Anyways, saw a few messages recently that prompted me to check my perl situation: su-2.05b# pkg_info | grep perl- perl-5.6.1_15 Practical Extraction and Report Language perl-5.8.2_2Practical Extraction and Report Language And wouldn't you know, everything that depends on perl depends on 5.6 currently. Yet it seems I should be ditching 5.6 and using 5.8.2, from what I read. So I'm wondering how to best straighten this out. As things stand now, use.perl port sticks me with 5.6. And I can't use portupgrade to fix this because alas, both versions are installed from ports (ports/perl5 and ports/perl5.8) and are considered separate and individually up-to-date. One option would be to do a pkg_delete -f on 5.6 then use portdb -F to fix the dependencies. Not sure if that's enough or if I need to rebuild. And if I need to rebuild the dependencies, how could I easily handle the list in one-pass? Right now it all depends on 5.6 which I'd be deleting. I could whack 5.6, repoint all dependencies to 5.8, then tell it to forcibly rebuild everything that depends on 5.8... but I don't know if this is the right thing to do. Or maybe I'm wrong and I should be keeping 5.6 because 5.8.2 will destroy things horribly and cause much breakage and woe. Eh. Advice? This seems to be a FAQ but searching/reading through the last several months of messages didn't reveal a definitive answer. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad root shell
On Sat, 20 Dec 2003 09:44:17 -0800, Mark McConnell wrote: An error in a pw* script inserted a non-existent shell into the password database, effectively locking out root. I used a fixit disk to correct the problem, using this procedure: Unless I'm missing something, seems like the long way to do this. Last time I did this to myself, I did the following: 1) Log in as a user who can su to root. 2) Use su -m to su to root without changing your current shell 3) As root, use chpass -s to change your shell to a working one. Of course, this won't work if your only account is root or you don't have anyone else in the wheel group, so maybe it doesn't apply to you. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xfree86 install on 5.1
On Thu, 18 Dec 2003 11:18:30 -0500, Chris Neustrup wrote: I recently upgraded from 5.0 to 5.1 on my thinkpad. When this worked OK, I tried to upgrade to the newest XFree86 4.30.x It filed due to patch mismatches. As I tried other earlier flavors of 4.X it never worked cleanly. Does anyone have a suggestion to get a stable 3.X X server running again? All things considered, I think it'd be much more worth your while to determine the reason for your XFree86 4.x problems. When you tried to install X, did you work from an updated ports tree? Also note that 5.2 is due out next month. There's always the chance that, if your problems are actually related to bugs, that they will be fixed in the next release. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Increase space for /var/db/
On Wed, 17 Dec 2003 08:04:58 -0800, samy lancher wrote: I have a 4.5 FreeBSD server with mysql database. only 250MB was allocated to /var/db. Our database is increasing so fast that now i need to expand the memory for /var/db. I guess one way to do is to install a new hard drive and then mount it to /var/db. But i would like to know if there is any other way to solve that problem. Is making a soft link a good idea. i have 70GB in /usr/ so i would like to map /var/db/ to some location in /usr/. Please let me know if anyone has any suggestions. First time I had to do this I did the link suggestion that other people have posted. But you have another cleaner option w/ MySQL. There is a my.cnf file where you can set a DATADIR variable (I think that's what it's called) to set the path for the database files. Then you can point that to /usr/mysql or whatever. Just read up on my.cnf and how it's used for more info. It either goes in /etc or /usr/local/etc I think. The reason I'm vague is that I don't do it that way myself. I use the /usr/local/etc/rc.d/ scripts (which I don't think were used in 4.5?) so I have an option right within the mysql-server.sh script there for setting the datadir (DB_DIR). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Increase space for /var/db/
On Wed, 17 Dec 2003 14:32:50 -0800, samy lancher wrote: thanks for the response. you are right, for 4.5 freebsd there is no reference of DB_DIR in mysql-server.sh. I looked for my.cnf in /etc and /usr/local/etc, but i did not find it in those folders. i feel that this file does not exist in my system. any suggestions? The file doesn't exist by default I don't believe. You have to create it if you want MySQL to use it. If you do a search on my.cnf on the MySQL website you'll come up with lots of documentation on the syntax of its contents. Good luck! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adelphia at home and NAT...
On Wed, 10 Dec 2003 18:42:39 -0500, Alex ander Sendzimir wrote: I chose Adelphia for my high speed internet service here in lovely Vermont. Same here! By the way, let me point you to a site I just started, http://www.vtbsd.net/ while we're at it. :) Feel free to stop by and hang out sometime... would love to drum up a community. I would like to be able to ssh into my home machine from a remote internet site or someone else's computer. I've tried a couple of things I thought might work and no such lunch. I understand Adelphia might be using NAT to route packets to my home machine. If this is true, does it mean I'm can't ssh remotely? How, if possible, can I get through. There is a company in Boston that advertises a package that does dynamic DNS for home computers. I haven't looked into how it works, though. There's gotta be a way! What I did to simplify things was pick up a DSL/cable router. I can recommend Netgear... I started with an RP614 but then upgraded recently to a WGR614. The router will receive a DHCP address from the cable modem. Your FreeBSD system will then receive a different DHCP address from the router, by default in the 192.168.0.nnn range. Netgear routers support interfacing with dyndns.org so you don't have to worry about knowing what IP address your router has this day. So you set up an account w/ dyndns (free) then config the router appropriately. All that's left is to open port 22 (or a different one if you want to use a non-standard port) on the router to point to your FreeBSD box. I'd recommend narrowing the DHCP range that the router picks from and leaving a range for static assignment. Then have your FreeBSD system use a static IP. That way you don't have to worry about the IP on the FreEBSD box accidentally changing for whatever reason and you not being able to ssh in. I've been doing this for a while now, and also tunnel VNC over the ssh connection. Works great! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports + cpan question
--- Michael Sig Birkmose [EMAIL PROTECTED] wrote: However lately I have also used Perl CPAN to install some perl modules. When I get a list of the packages I need to upgrade (portversion -l \) these packages also shows up - why? I recently went through this, and although no expert, here's what I learned: Somehow the portupgrade suite can detect stuff installed via CPAN. They appear prefixed with bsdpan-. However, because it wasn't installed in the normal manner, portupgrade can't manage upgrades, so they are all marked as held. Each has an equivalent in the official ports tree... prefixed w/ p5- and maybe named a tad different (but close enough that you can figure it out). If you uninstall the CPAN versions and install the p5- versions, this seems to make portupgrade happy. That's all I know. Someone may correct me and/or elaborate. I ran into this w/ f-prot and eventually sorted everything out so I didn't get tons of errors everytime I ran portupgrade. Hope this helps! = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://vtbsd.net/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. http://vtbsd.net/freebsd/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to make printer print faster?
On Tue, 9 Dec 2003 12:29:15 -0600, Charles Howse wrote: With all due respect, do you know for a fact that your suggestion works? I have a HP1100, configured with apsfilter, and I have tried that very same thing, and it only prints at 600 dpi. Does anyone know the correct driver for the HP1100 LaserJet? I've been using ljet4. I have a Laserjet 1012 and I can only get 600dpi. I use the hpijs driver w/ CUPS. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I wonder what did destroy it. Of course, system crashes can do wonders, but... Well, I was trying to save a file to that drive when my system spontaneously rebooted for no apparent reason. In fact, there should be a way, because a valid superblock copy has a correct checksum. Perhaps I'll hack up a program to do that taking information from the /usr/src/sys/ufs/... There's also a magic number for a superblock, mentioned in fs.h (in 4.8 it's 0x011954). I see: #define FS_UFS1_MAGIC 0x011954/* UFS1 fast filesystem magic number */ #define FS_UFS2_MAGIC 0x19540119 /* UFS2 fast filesystem magic number */ And I remember this drive was UFS2, because I was wondering if I should be concerned that this drive was UFS2 and the system drive was UFS1 (/, /var, /usr). However, the following command turns up no results after several mins: su-2.05b# hd /dev/ad6s1 | grep 19 01 54 19 Yet this won't work unless the bytes all line up on the same line. If they're split across lines in the hd output, there'll be no match. Even though your command is for UFS1, I get several matches, but they must be false-positives as I know I used UFS2: su-2.05b# hd /dev/ad6s1 | grep 54 19 01 00 1620 54 19 01 00 74 10 68 81 23 00 00 e8 d5 03 00 00 |T...t.h.#...| 2550 01 00 00 00 00 00 00 00 00 00 00 00 54 19 01 00 |T...| 4550 01 00 00 00 00 00 00 00 00 00 00 00 54 19 01 00 |T...| 002e6550 01 00 00 00 00 00 00 00 00 00 00 00 54 19 01 00 |T...| 00548740 51 19 01 00 52 19 01 00 53 19 01 00 54 19 01 00 |Q...R...S...T...| 00549740 51 19 01 00 52 19 01 00 53 19 01 00 54 19 01 00 |Q...R...S...T...| Unless somehow I am confused...? Any other ideas for finding an intact superblock off this drive and repairing it? Anyone? = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://vtbsd.net/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. http://vtbsd.net/freebsd/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: Oh yes there are... what's surprising? If you are sure that the problem is with the superblock, pick any you wish. The actual number of superblock copies depends on the disk size and the parameters you give to newfs. [...] It's about THE superblock, not a superblock copy. There can be only one superblock. There may be many copies. But if you dd them to the superblock, that'll be fine. Ahh ok, I've learned something new. Guess I misinterpreted the information I found online. I'm not complaining: this is GOOD news. :) BTW, what's the output of ``disklabel -r /dev/ad6s1c'' ? su-2.05b# disklabel -r /dev/ad6s1c # /dev/ad6s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 156344517 63unused0 0 # raw part, don't edit e: 156344517 634.2BSD 2048 1638489 partition c: partition extends past end of unit disklabel: partition c doesn't start at 0! disklabel: An incorrect partition c may cause problems for standard system utilities partition e: partition extends past end of unit That doesn't look good. By the way, the past posts I've read suggest that even if I use fsck_ffs -b to run fsck with a diff superblock (say, the one at 160) that it doesn't actually fix the master copy, and that I still need to use dd to fix the original. The command I've seen used is: dd if=/dev/ad6s1c skip=32 of=/dev/ad6s1c seek=16 bs=512 count=16 1) Do I just replace the 32 of skip=32 with 160 (or whichever superblock makes fsck_ffs -b happy)? 2) I've also read that the size and location of the original superblock can vary. Do I have to modify the seek/bs/count values to account for this? And if so, how do I find the proper values? Nothing done yet... don't wanna screw this up. Thanks everyone! = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://vtbsd.net/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. http://vtbsd.net/freebsd/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: If you want to be more sure, try dd'ing your (suspectedly damaged) superblock and some of its (suspectedly OK) copies into different files: # dd if=/dev/ad6s1e skip=... bs=512 count=16 of=somefile As /usr/src/sys/ufs/ffs/fs.h suggests, for THE superblock skip should be 16 if you have UFS1 or 128 or 512 if you have UFS2 (if my maths is correct). These commands shouldn't do anything harmful to /dev/ad6s1e. Either I'm doing something wrong, or things aren't good. Given: su-2.05b# newfs -N /dev/ad6s1e /dev/ad6s1e: 76340.1MB (156344516 sectors) block size 16384, fragment size 2048 using 416 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, ... 152046368, 152422720, 152799072, 153175424, 153551776, 153928128, 154304480, 154680832, 155057184, 155433536, 155809888, 156186240 I take 6 superblock copies (3 from beginning, 3 from end): su-2.05b# dd if=/dev/ad6s1e skip=160 bs=512 count=16 of=sb1 16+0 records in 16+0 records out 8192 bytes transferred in 0.026774 secs (305969 bytes/sec) su-2.05b# dd if=/dev/ad6s1e skip=376512 bs=512 count=16 of=sb2 16+0 records in 16+0 records out 8192 bytes transferred in 0.008415 secs (973502 bytes/sec) su-2.05b# dd if=/dev/ad6s1e skip=752864 bs=512 count=16 of=sb3 16+0 records in 16+0 records out 8192 bytes transferred in 0.006808 secs (1203283 bytes/sec) su-2.05b# dd if=/dev/ad6s1e skip=155433536 bs=512 count=16 of=sb4 16+0 records in 16+0 records out 8192 bytes transferred in 0.023173 secs (353513 bytes/sec) su-2.05b# dd if=/dev/ad6s1e skip=155809888 bs=512 count=16 of=sb5 16+0 records in 16+0 records out 8192 bytes transferred in 0.011078 secs (739484 bytes/sec) su-2.05b# dd if=/dev/ad6s1e skip=156186240 bs=512 count=16 of=sb6 16+0 records in 16+0 records out 8192 bytes transferred in 0.010837 secs (755932 bytes/sec) None of these are the same: su-2.05b# cmp sb1 sb2 sb1 sb2 differ: char 1, line 1 su-2.05b# cmp sb1 sb3 sb1 sb3 differ: char 1, line 1 su-2.05b# cmp sb2 sb3 sb2 sb3 differ: char 1, line 1 I don't include sb4-6 here because they're all null: su-2.05b# hexdump -C sb4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 2000 su-2.05b# hexdump -C sb5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 2000 su-2.05b# hexdump -C sb6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 2000 I am suspecting there is something wrong in my syntax for fetching the superblocks. I see that the SB size is always 8192 bytes regardless so it should be 512*16 as in the dd command. And I checked that the #s output by newfs -N were block positions and not raw byte permissions. However newfs -N is saying that it is reporting the positions using a blocksize of 16384. In which case, 160 would mean 160 * 16384 = 2621440 (byte pos). To translate to the 512-byte blocks, this means the skip should be 5120 (and 12048384 and 24091648 respectively for the 2nd 3rd sb positions). However, when I grab 8192-byte chunks using these skip settings w/ dd, they don't match up either. I was hoping I was onto something. :( Yet you say using the same # output by newfs -N as the skip for dd worked for you... hmm. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote: I've got a (probably bad) idea. If you say that the partition was mounted as /data, then you could do a # hd /dev/ad6s1 |grep /data It should come up soon (the superblock should be close to the beginning of the drive, right?). This way you can at least figure out where your superblock lies (rounding the address of `/data' to 8K). Considering the above discussion, you can calculate the *correct* address of the `e' partition by subtracting 8K or 64K or 256K. See if it matches the one in the disklabel. Of course, this is all possible only if your superblock isn't screwed enough to NOT contain `/data'. Been running about a minute so far... nada. So I guess your assumption is correct: the 1st superblock is destroyed (as fsck suggested when it barfed). Just a minute. Are you sure that the filesystem was newfs'd with the default parameters? If it were for me to newfs it, I would probably choose larger blockfragment sizes, as I would probably be storing large files. The superblock copy positions depend on the block/frag size. If you specify parameters different from those used for actually newfs'ing it the very first time, newfs -N will give you *incorrect* copy addresses! Well, specifying custom block/frag sizes is a bit out of my customization forte at the moment, and certainly at the time this drive went in. I'm 99% positive I used sysinstall to set it up. I remember some quirks about the sysinstall method, and also deciding that the by-hand method was unnecessarily complicated for my needs. This has taught me that, should I ever choose to do that, that writing down these custom values is CRITICAL. Is there any way to positively identify a superblock location (say, using hd | grep ) using known information? Just a random thought. Although I'm treating this as a learning experience, I also REALLY REALLY don't want to loose all that data. I do appreciate the help you've been giving me. Thanks again. I'm choosing to remain optimistic. I used to salvage lots of data from DOS/Windows partitions (still do) so learning the tricks of the trade in my new OS of choice is important to me. (PS: already pricing out external USB hard drive enclosures for making backups of this drive in the future) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot find file system superblock error - how to recover?
Running 5.1-REL on a system w/ 2 drives. Was saving a file to 2nd drive (mounts as /data) and system suddenly froze then rebooted. Never good. Fsck barfed on startup telling me I had to run it manually. The error I'm stuck with is: /dev/ad6s1c Cannot find file system superblock /dev/ad6s1c: NOT LABELED AS A BSD FILE SYSTEM Searching on this error hasn't been very productive. Some people talk about a LOOK FOR ALTERNATE SUPERBLOCKS? question that I'm not getting when I run fsck. There's also mention of an undocumented -b option to fsck for fixing this. Then there's some scary manual method using dd: dd if=/dev/ad6s1c skip=32 of=/dev/ad6s1c seek=16 bs=512 count=16 But before I do that I definitely want confirmation. Please tell me there's hope for this drive...this Windows PC makes me feel dirty. Thanks in advance. :) = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://vtbsd.net/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. http://vtbsd.net/freebsd/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot find file system superblock error - how to recover?
--- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: FSCK_FFS(8) NAME fsck_ffs, fsck_ufs -- file system consistency check and interactive repair SYNOPSIS fsck_ffs [-BFpfny] [-b block#] [-c level] [-m mode] filesystem ... -b Use the block specified immediately after the flag as the super block for the file system. Block 32 is usually an alternate super block. Ah, somehow never knew about fsck_ffs. Now I do :-) Does it matter that /dev/ad6s1c is UFS2 and not UFS1? Try doing a newfs -N and see if using some of the alternatives super-blocks in fsck_ufs will help. Note that the alternate superblock is no longer always at 32, it depends on the size of the file system. Whoa, something doesn't seem right. I do: su-2.05b# newfs -N /dev/ad6s1c /dev/ad6s1c: 76340.1MB (156344516 sectors) block size 16384, fragment size 2048 using 416 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792, 6398144, 6774496, 7150848, 7527200, 7903552, 8279904, 8656256, 9032608, 9408960, 9785312, 10161664, 10538016, 10914368, 11290720, 11667072, 12043424, 12419776, 12796128, 13172480, 13548832, 13925184, 14301536, 14677888, 15054240, 15430592, 15806944, 16183296, 16559648, 16936000, 17312352, 17688704, 18065056, 18441408, 18817760, 19194112, 19570464, 19946816, 20323168, 20699520, 21075872, 21452224, 21828576, 22204928, 22581280, 22957632, 2984, 23710336, 24086688, 24463040, 24839392, 25215744, 25592096, 25968448, 26344800, 26721152, 27097504, 27473856, 27850208, And this actually continues for quite a bit. There aren't really that many copies of the superblock on the drive, right? * Depending on the architecture and the media, the superblock may * reside in any one of four places. Yeah, a lot more than four... Haven't tried anything yet. Awaiting expert advice first... Thanks! = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://vtbsd.net/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. http://vtbsd.net/freebsd/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vncserver, rc.local, and blackbox problem
Ok, for today's edition of Show Scott What Stupid Thing He Missed... Trying to set up a dedicated VNC/ethereal server, so I'm trying to have vncserver run from rc.local (using su to run it as a user and not root). Ran into some path issues to make vncserver happy, which I resolved, but for some reason blackbox won't run and it doesn't _seem_ to be paths. Strangely enough, ethereal (which is loaded from the same ~/.vnx/xstartup file as blackbox) DOES launch (I just have no wm). So I know that file is being used. And if I launch vncserver manually as the user. both blackbox and ethereal launch fine. (for those of you wondering, I don't use fluxbox because of cosmetic quirks, or openbox because it doesn't play nice over vnc) Anyhow, my /etc/rc.local file is: PATH=$PATH:/usr/X11R6/bin:/usr/local/bin HOME=/home/ben su ben -c /usr/local/bin/vncserver -depth 8 -geometry 1024x768 And /home/ben/.vnc/xstartup is currently: #!/bin/sh #PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/b in:/usr/X11R6/bin:/home/ben/bin HOME=/home/ben [ -r $HOME/.Xresources ] xrdb $HOME/.Xresources xsetroot -solid grey #xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop #twm /usr/X11R6/bin/ethereal /usr/X11R6/bin/blackbox (note the commented-out path declaration... that was my attempt to see if making the path match what it is when ben is just logged in would make blackbox happy, which it didn't). The :1.log file only offers a vague clue. When I normally start vncserver manually as ben, it looks like this: 21/10/03 15:28:53 Xvnc version 3.3.7 - built Oct 21 2003 11:01:44 21/10/03 15:28:53 Copyright (C) 2002-2003 RealVNC Ltd. 21/10/03 15:28:53 Copyright (C) 1994-2000 ATT Laboratories Cambridge. 21/10/03 15:28:53 All Rights Reserved. 21/10/03 15:28:53 See http://www.realvnc.com for information on VNC 21/10/03 15:28:53 Desktop name 'X' (aaa.bbb.ccc.com:1) 21/10/03 15:28:53 Protocol version supported 3.3 21/10/03 15:28:53 Listening for VNC connections on TCP port 5901 21/10/03 15:28:53 Listening for HTTP connections on TCP port 5801 21/10/03 15:28:53 URL http://aaa.bbb.ccc.com:5801 BScreen::BScreen: managing screen 0 using visual 0x22, depth 16 But when I try and start vncserver from bootup, it looks like this: 21/10/03 15:32:22 Xvnc version 3.3.7 - built Oct 21 2003 11:01:44 21/10/03 15:32:22 Copyright (C) 2002-2003 RealVNC Ltd. 21/10/03 15:32:22 Copyright (C) 1994-2000 ATT Laboratories Cambridge. 21/10/03 15:32:22 All Rights Reserved. 21/10/03 15:32:22 See http://www.realvnc.com for information on VNC 21/10/03 15:32:22 Desktop name 'X' (aaa.bbb.ccc.com:1) 21/10/03 15:32:22 Protocol version supported 3.3 21/10/03 15:32:22 Listening for VNC connections on TCP port 5901 21/10/03 15:32:22 Listening for HTTP connections on TCP port 5801 21/10/03 15:32:22 URL http://aaa.bbb.ccc.com:5801 BScreen::BScreen: managing screen 0 using visual 0x22, depth 8 21/10/03 15:32:32 Xvnc version 3.3.7 - built Oct 21 2003 11:01:44 21/10/03 15:32:32 Copyright (C) 2002-2003 RealVNC Ltd. 21/10/03 15:32:32 Copyright (C) 1994-2000 ATT Laboratories Cambridge. 21/10/03 15:32:32 All Rights Reserved. 21/10/03 15:32:32 See http://www.realvnc.com for information on VNC 21/10/03 15:32:32 Desktop name 'X' (aaa.bbb.ccc.com:1) 21/10/03 15:32:32 Protocol version supported 3.3 X connection to :1.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :1.0 broken (explicit kill or server shutdown). It's almost as if it's getting called twice (???) and there's some sort of collision. And/or maybe that broken connection is blackbox dying somehow. Any advice? Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
fonts question
I understand a lot of things, but fonts sometimes confuse me. This is one of those times. I'm using FreeBSD 5.1-RELEASE and XFree86 4.3.0. Most of the time, my fonts are beautiful and anti-aliased. However, I noticed some web pages some text wouldn't be. I narrowed down one site to it listing Lucida in the fonts pref list, which I have as a PCF font. It seems that PCF fonts are bitmap fonts... so that explains why it's not anti-aliased. An example would be: font face=Tahoma, Lucida, Helvetica size=+2bThis text isn't anti-aliased!/b/font (One quick solution here would be a way in Firebird to never use PCF fonts when rendering pages... if someone knows the answer, please let me know. This would be Question #1). I use gnome (2.4), so I pulled up my font list to discover that Lucida was a PCF font. I also saw that I had LucidaBright and LucidaTypewriter, also PCF fonts. It occurred to me that maybe I could get the TTF Lucida Sans font and put it on here. If so, Question #2 is: is there a way to have X always substitute a font... in this case, Lucida Sans for any call for Lucida? I would assume flat out turning off PCF fonts would be a Bad Idea. The plot thickens though. I launch OpenOffice 1.1 and guess what? I see Lucidasans, Lucidabright, and Lucidatypewriter as VECTOR FONTS! Truly they are working, as I tried applying them to some sample text and made the point size huge. Yet these same fonts don't appear in AbiWord. So question #3 is: What gives? Where's this Lucidasans vector font coming from? How can I make it available to other apps, like Firebird and AbiWord? And how can I make it get used before the PCF Lucida? I know the page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-fonts.html ...but it doesn't go this deep. Any insight or help appreciated... thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fonts question
On Tue, 14 Oct 2003 04:20:53 -0400, Joe Marcus Clarke wrote: I know the page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-fonts.html ...but it doesn't go this deep. Actually, the Anti-Aliasing section at the bottom does. Hey Marcus... thanks for jumping in. I didn't miss that section, but I can't see how it helps me here. Maybe you can let me know what I'm missing. Going through those instructions: I don't have a ~/.fonts/ directory, and I've looked through /usr/X11R6/lib/X11/fonts/ for *[Ll][Uu][Cc]* as well as examined all the font descriptions in the various font.dir files and found no non-PCF Lucida font mentioned. Tweaking which fonts are anti-aliased seems not the answer as what I read says that bitmap fonts like PCF cannot be anti-aliased. So the editing of fonts-conf to control this isn't applicable. (note: that site talks about editing that file, yet when you open it, it says at the very top to NOT edit it). Running fc-cache -f does not make these vector Lucida fonts visible to AbiWord. Changing the point size at which fonts are anti-aliased, or the spacing, isn't applicable to my problems. And finally, I already have bitstream-vera installed. If the answer to my problem (or any of my 3 questions) is indeed on that web page, then I guess I'm being dense, but I'm not seeing it. Sorry :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openoffice
On Thu, 9 Oct 2003 09:38:24 -0500, Aaron Sloan wrote: I'm trying to build openoffice or openoffice-devel from ports. CVS, portupgrade etc...completed. says there is a checksum mismatch with the OO source and stop 4.8 stable. It has been broken for about a week and a half. First off, I'd recommend openoffice-devel as it currently conatins OO 1.1 release which is mighty-fine and compiles just great on my FreeBSD 5.1-RELEASE system. Download the file manually from http://www.ibiblio.org/pub/packages/openoffice/stable/1.1.0/ and drop it into /usr/ports/distfiles/openoffice1.1/ There were questions about this posted to the list last week. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Screen size
On Thu, 9 Oct 2003 10:23:08 -0500, Talbot wrote: I recently installed FreeBSD 4.5 with desk top KDE using a CD that came with the book, FreeBSD Unleashed, by Michael Urban and Brian Tiemann. Everything seemed to go fine until I execute startx. The desktop environment on my screen seems to be at least four times as big as it should be, displaying only the top left portion of the desktop. The strange part of this problem is that the install program displays all of the display option screens in the correct size and font. Any advice to get me going will be appreciated. I dunno if it will help, but I do all my X configs by-hand. I've never had good luck with the GUI configuration tools or the text-mode utilities. I just dive in and edit the file by-hand and it works every time. You can scroll down to the relevant portion of this speed-through I did up a while back (which is probably due for a new version when I get time): http://www.vtbsd.net/ipw-web/portal/cms/modules.php?name=Contentpa=showpag epid=5 Good luck! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error
On Fri, 5 Sep 2003 11:58:16 +0100 (BST), Jan Grant wrote: Loks like the VNC srever isn't listening at that location. Is it running? Yep: -bash-2.05b$ ps PID TT STAT TIME COMMAND 60273 p0- S 0:00.49 Xvnc :1 -desktop X -httpd /usr/local/share/vnc/classes 60277 p0- S 0:00.20 /usr/X11R6/bin/blackbox 61709 p0 Is 0:00.03 bash 80005 p1 Is 0:00.02 bash 96020 p2 Ss 0:00.01 -bash (bash) 96025 p2 R+ 0:00.00 ps 490 v0 I 0:00.01 -bash (bash) 61622 v0 I+ 0:00.01 /bin/sh /usr/X11R6/bin/startx 61634 v0 I+ 0:00.01 xinit /home/scott/.xinitrc -- -nolisten tcp 61640 v0 I 0:00.00 sh /home/scott/.xinitrc 61641 v0 I 0:01.31 /usr/X11R6/bin/gnome-session 61644 v0 S 0:01.62 /usr/X11R6/libexec/gconfd-2 13 Blackbox is the wm being started from ~/.vnc/xstartup since I normally use gnome. And I'm forwarding the ports in PuTTY: 2003-09-05 09:02:56 Local port 7001 forwarding to localhost:5901 2003-09-05 09:02:56 Local port 7002 forwarding to localhost:5902 2003-09-05 09:02:56 Local port 7003 forwarding to localhost:5903 (the same port-forwarding that worked for me before). On the Windows system, I then VNC to localhost:7001 which triggers that error on the VNC box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error
On Fri, 5 Sep 2003 14:51:08 +0100 (BST), Jan Grant wrote: I'd still recommend double-checking with sockstat on the BSD box, (and netstat -an on the windows box, but I don't think that's the problem). Sure... you help me, I help you help me. :) -bash-2.05b$ sockstat -l | grep vnc scottXvnc 60273 0 tcp4 *:6001*:* scottXvnc 60273 1 stream /tmp/.X11-unix/X1 scottXvnc 60273 3 tcp4 *:5901*:* scottXvnc 60273 4 tcp4 *:5801*:* So it IS listening on 5901. Also: su-2.05b# strobe -b 5900 -e 5910 localhost strobe 1.05 (c) 1995-1999 Julian Assange [EMAIL PROTECTED]. localhost 5901 unassigned unknown - RFB 003.003\n Amongst other things, netstat -ab reports on the Windows machine: TCP127.0.0.1:7001 0.0.0.0:0 LISTENING TCP127.0.0.1:7002 0.0.0.0:0 LISTENING TCP127.0.0.1:7003 0.0.0.0:0 LISTENING ...which makes sense, since I'm getting through enough to trigger the error on the FreeBSD system. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error
On Fri, 5 Sep 2003 16:03:21 +0100 (BST), Jan Grant wrote: OK, two other things (increasingly bizarre) occur to me; after that, I'm stumped: 1. tcp wrappers or similar on your vnc? On the FreeBSD system? No. Well, not that I know of. I have not configured to use tcp wrappers w/ VNC so if it's happening, it's doing so without me having asked it to. 2. The localhost is (as I recall) resolved on the putty side and the IP to connect to sent to the sshd. Does localhost resolve to anything other than 127.0.0.1 on your windows machine? Nope: C:\ping localhost Pinging SCOTT [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time10ms TTL=128 Reply from 127.0.0.1: bytes=32 time10ms TTL=128 Reply from 127.0.0.1: bytes=32 time10ms TTL=128 Of course, now that I think about it, plugging another workstation in at home and seeing if I can VNC to the FreeBSD system on the local LAN would be rather enlightening. Why haven't I done this already? Duh. Will have to try it later... Incidentally, I'm not the first to have this problem: http://groups.google.com/groups?selm=20030129114855.D5796-10_geri.cc.fe r.hr%40ns.sol.netoe=UTF-8output=gplain I tried emailing him but haven't heard back. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC ssh tunneling problem: getsockopt TCP_NODELAY error
Figured I'd start with my FreeBSD friends first before bugging the VNC community. I used to have VNC tunneling over ssh just fine, but then had to redo my system drive. I used FreeBSD 5.1 before and still do now, however it's not working. I'm using the same PuTTY system so the config is the same as from before when it worked. So something is different at the FreeBSD end. The PuTTY log shows: 2003-09-04 11:26:28 Opening forwarded connection to localhost:5901 2003-09-04 11:26:28 Forwarded connection refused by server And /var/log/messages shows: Sep 4 11:26:28 scott sshd[37213]: error: getsockopt TCP_NODELAY: Connection reset by peer Maybe I'm just dumb and missed something I configured before, but I can't figure out what. Can someone offer insight? Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC ssh tunneling problem: getsockopt TCP_NODELAY error
On Thu, 4 Sep 2003 11:31:56 -0500, Andrew L. Gould wrote: Is PuTTY expecting the server's key from the previous installation? Just a guess. Nope, that happens earlier in the process. I can ssh to my PC just fine, and already dealt with the message about the server's key having changed. Shouldn't be any special new key for tunnelling a protocol over an already-established ssh session (right?). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: preferred raid controller
On Thu, 4 Sep 2003 10:46:51 +0100, George Barnett wrote: I'm building a syslog server with some regular scsi disk shelves hanging off the back and I'm looking for a recommenedation on a raid controller. I currently have a (old) dpt smartcache iv, but it doesn't seem to have much in the way of management tools (I found it in a cupboard somewhere :). I dont need speed, but I'm after reliability and control (monitoring tools would be great too). What are the current favourites out there? I've heard 3Ware controllers work well w/ FreeBSD and are very good. I have no personal experience with them though. http://www.3ware.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
search replace on multiple files
Hello... I'm trying to figure out a way to pull off the following: I have a subdir with many different sorts of text files (some nested in additional subdirs, so recursion would be necessary) that need to have a search replace done on them. What's a quick way to script a global search replace on many/all text files in nested subirs? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mucked up partitions, can't boot [REPOST]
[orig question included again at end] --- Mike Meyer [EMAIL PROTECTED] wrote: You really should split swap up in that kind of situation. I.e. - put var and half of swap on da1, and tmp and the rest of swap on da2. The kernel will interleave swap usage across both spindles for better performance if you do that. Good tip, thanks... I didn't know that. Well, you didn't describe a problem, and you didn't ask a question. It's hard to provide guidance without some indication of where you are and are trying to go. Sorry, guess my problem/question didn't communicate well. Upon boot, I get: Invalid partition Invalid partition No /boot/loader FreeBSD/i386 boot Default: 0:ad(0,a)/kernel Boot: Invalid partition No /kernel FreeBSD/i386 boot Default: 0:ad(0,a)/kernel Boot: The rest of my email then applies, so I'm including it here for anyone new jumping in: Doing another experimental 5.0-REL install where I mucked things up due to partitioning by-hand. This is now becoming a learning experience on fixit et al, so although this is just for fun I'd like to carry it through the hard way vs just reinstalling. Anyhow, this system has 4 SCSI disks da0 through da3. I put / on da0, swap on da1, split da2 50/50 with /var and /tmp, then /usr is on da3. For each disk I chose A during slice setup to use entire disk but then partitioned manually once that screen came up. I think what I originally forgot to do was set da0 active as I normally have always just chosen A during partition setup. This system is old and can't boot off CD, but I do have the kern, mfsroot, and fixit floppies. I already tried fdisk -a da0 as well as disklabel -w B da0 but that only made me go from error 1 lba on boot to invalid partition. I confess to not being familiar with these tools... this is my first need to use them. In /dev, I have da0, da0c, da1, da1s1, da1s1b, da1s1c, da2, da2s1, da2s1c, da2s1d, da2s1e, da3, da3s1, da3s1c, da3s1d If I do an fdisk da0 partitions 1-3 are UNUSED and everything is on partition 4, but fdisk da1 through da3 it's partition 1 that has data, and partitions 2-4 are UNUSED. All used partitions are flag 80 (active) according to fdisk (I can't see how to make a partition UN-active, only active). Anyone willing to help me learn and guide me from here? Thanks = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://home.adelphia.net/~sremick/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Mucked up partitions, can't boot
Doing another experimental 5.0-REL install where I mucked things up due to partitioning by-hand. This is now becoming a learning experience on fixit et al, so although this is just for fun I'd like to carry it through the hard way vs just reinstalling. Anyhow, this system has 4 SCSI disks da0 through da3. I put / on da0, swap on da1, split da2 50/50 with /var and /tmp, then /usr is on da3. For each disk I chose A during slice setup to use entire disk but then partitioned manually once that screen came up. I think what I originally forgot to do was set da0 active as I normally have always just chosen A during partition setup. This system is old and can't boot off CD, but I do have the kern, mfsroot, and fixit floppies. I already tried fdisk -a da0 as well as disklabel -w B da0 but that only made me go from error 1 lba on boot to invalid partition. I confess to not being familiar with these tools... this is my first need to use them. In /dev, I have da0, da0c, da1, da1s1, da1s1b, da1s1c, da2, da2s1, da2s1c, da2s1d, da2s1e, da3, da3s1, da3s1c, da3s1d If I do an fdisk da0 partitions 1-3 are UNUSED and everything is on partition 4, but fdisk da1 through da3 it's partition 1 that has data, and partitions 2-4 are UNUSED. All used partitions are flag 80 (active) according to fdisk (I can't see how to make a partition UN-active, only active). Anyone willing to help me learn and guide me from here? Thanks = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use a Mozilla-based browser: http://home.adelphia.net/~sremick/mozilla/ FreeBSD: Because making unix user-friendly is easier than debugging Windows. Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
(still) Having trouble compiling OO
Ok, STILL trying to get OpenOffice to compile on this one machine (4.7-REL, cvsup'ed ports). Following another suggestion, I removed gcc 3.1, pruned all my /usr/ports/*/*/work files, cvsup'ed ports, and tried again. Now I'm getting a new sort of error/msg that I've never seen before and I'm not sure how to proceed. Due to the fact that the compile takes SOOO long to get to this point, I'm leaving it there until I can get some insight. Here's the tail end: COPY: ../unxfbsd.pro/inc/internal/ftdriver.h - /usr/ports/editors/openoffice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/inc/freetype/internal/ftdriver.h COPY: ../unxfbsd.pro/inc/internal/ftobjs.h - /usr/ports/editors/openoffice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/inc/freetype/internal/ftobjs.h COPY: ../unxfbsd.pro/lib/libfreetype.so.7 - /usr/ports/editors/openoffice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/lib/libfreetype.so.7 COPY: ../unxfbsd.pro/lib/libfreetype.a - /usr/ports/editors/openoffice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/lib/libfreetype.a Statistics: Files copied: 49 Files unchanged/not matching: 5 = Building project stlport = /usr/ports/editors/openoffice/work/oo_1.0.1_src/stlport - cd ./unxfbsd.pro/misc/build cat ../../../STLport-4.5.patch | patch -p2 touch so_patched Hmm... Looks like a new-style context diff to me... The text leading up to this was: -- |*** misc/STLport-4.5/src/fstream.cpp Tue Sep 4 19:10:12 2001 |--- misc/build/STLport-4.5/src/fstream.cpp Fri Jan 11 17:22:40 2002 -- Patching file STLport-4.5/src/fstream.cpp using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
OO compile fails
Not sure what to make of this. OO compile (from ports) churns for quite a while on my 4.7-REL box, then dies: -- Making: ../../unxfbsd.pro/slo/sifile.obj g++31 -w -c -I. -I. -I../inc -I../../inc -I../../unx/inc -I../../unxfbsd.pro/inc -I. -I/usr/p orts/editors/openoffice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/inc/stl -I/usr/ports/editors /openoffice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/inc/external -I/usr/ports/editors/openof fice/work/oo_1.0.1_src/solver/641/unxfbsd.pro/inc -I/usr/ports/editors/openoffice/work/oo_1.0 .1_src/solenv/unxfbsd/inc -I/usr/ports/editors/openoffice/work/oo_1.0.1_src/solenv/inc -I/usr /ports/editors/openoffice/work/oo_1.0.1_src/res -I/usr/include -I/usr/ports/editors/openoffic e/work/oo_1.0.1_src/solver/641/unxfbsd.pro/inc/stl -I/usr/ports/editors/openoffice/work/oo_1. 0.1_src/solenv/inc/Xp31 -I/usr/local/jdk1.3.1/include -I/usr/local/jdk1.3.1/include/freebsd - I/usr/local/jdk1.3.1/include/green_threads/include -I/usr/X11R6/include -I/lib/gcc-lib/i386-p ortbld-freebsd4.7/3.1.1/include -I/usr/include -I. -I../../res -I. -I/usr/ports/editors/o penoffice/work/oo_1.0.1_src/solenv/unxfbsdi/usr/include -I/usr/X11R6/include -O -pipe -fno- for-scope -fpermissive -fno-exceptions -fPIC -DFREEBSD -DUNX -DVCL -DGCC -DC300 -DINTEL -DC VER=C300 -D_USE_NAMESPACE -D_USE_NAMESPACE=1 -DX86 -DNEW_SOLAR -DSTLPORT_VERSION=400 -DOSVERS ION=47 -D_THREAD_SAFE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3 -DSUPD=641 -DBUILD=7663 -DPRODUCT -DNDEBUG -DPRODUCT_FULL -DOPTIMIZE -DEXCEPTIONS_OFF -DCUI -DSOLAR_JAVA -DSRC641 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxfbsd.pro/slo/sifile.o /usr/ports/editors/openoffice/work /oo_1.0.1_src/setup2/source/compiler/sifile.cxx /usr/ports/editors/openoffice/work/oo_1.0.1_src/setup2/source/compiler/sifile.cxx: In member function `virtual BOOL SiFile::WriteTo(SiDatabase) const': /usr/ports/editors/openoffice/work/oo_1.0.1_src/setup2/source/compiler/sifile.cxx:723: intern al error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. dmake: Error code 1, while making '../../unxfbsd.pro/slo/sifile.obj' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /usr/ports/editors/openoffice/work/oo_1.0.1_src/setu p2/source/compiler dmake: Error code 1, while making 'build_all' ---* TG_SLO.MK *--- *** Error code 255 = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: New install won't boot off A7V133
In article ashllk$28g0$[EMAIL PROTECTED], you say... On Mon, Dec 02, 2002 at 08:19:36PM -0800, Scott I. Remick wrote: I just got in an ATA133 30GB drive that I am going to dedicat to FreeBSD on my main system (an Asus A7V133). I took off the existing 20GB (Win2000), put the 30GB in its place (primary master). I boot from a 4.7-REL CD I made, install goes fine... it detects the controllers, drive, I partition the whole thing for FreeBSD, setting the auto defaults, etc etc. Everything goes swell. Then I'm done, I reboot, take out the CD... and it just sits there when it should be booting from the drive. I can't tell you the solution, but by pure chance I too have been fiddling with installs on a A7V133 system with a 30GB drive. I am convinced there is a bug in the BIOS because it doesn't honour the boot order you set in the BIOS sometimes. I did a quick experiemental install of 5.0 just to see. It all went fine, and did indeed boot. However it then refused to boot anything other than the HD, Despite the boot order being FD, CD, HD. I got around this by rather drastic means,,,but if it happens again I shall be..mmm..pissed off :) Although this is not what you are seeing, it is a bit of a co-incidence. Cliff, Just to confirm: you get beyond the POST, to the hardware info screen, where you should normally start seeing the boot process, correct? Mine just sits there at that point. A few things I haven't done yet that I intend on are installing MS-DOS to the drive, as well as using a different drive, in order to determine whether it is FreeBSD or the specific hard drive. What brand drive is yours, out of curiosity? Mine is an IBM DeskStar. What BIOS version are you using? I know there's a 1010 beta out for this board, but I'm hesitant to try it until I've done some other things (as I use this computer for Win2K also). It is interesting that 5.0 boots for you... if it were truly a problem with the A7V133's BIOS I'd expect 5.0 to not boot also. Anyhow, I will be troubleshooting this some more tonight. Maybe others will pipe in throughout the course of today with more ideas. = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
XFree86-4-libraries broken?
Just installed 4.7-REL, cvsup'ed ports and tried to make x11/XFree86-4. It's dying on XFree86-4-libraries though. The end is something like this: In file included from arc.cc:42: /usr/include/stdio.h: In function 'int __sputc(int, FILE *)': /usr/include/stdio.h:363 Internal compiler error (Sorry if that's not exact... it's not a screenshot, as it's from this computer and I had to swap the Win2K HDD in so I could boot and email this out.) I noticed there was a patch added today to make xfree86-4-libraries build on ia64, so I'm cc'ing the maintainer too... but was wondering if anyone else noticed this or had an idea? = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
New install won't boot off A7V133
I just got in an ATA133 30GB drive that I am going to dedicat to FreeBSD on my main system (an Asus A7V133). I took off the existing 20GB (Win2000), put the 30GB in its place (primary master). I boot from a 4.7-REL CD I made, install goes fine... it detects the controllers, drive, I partition the whole thing for FreeBSD, setting the auto defaults, etc etc. Everything goes swell. Then I'm done, I reboot, take out the CD... and it just sits there when it should be booting from the drive. The A7V133 has two integraded IDE controllers. One is a Promise ATA100 one. I've tried both the integrated Promise controller, and the non-promise one (doing a full, clean install on each). So it's not specific to the Promise controller. I have BIOS 1009 for this (the latest). Have it set to non-PnP OS (it detects my PCI NIC just fine), have played around with boot orders, even taken the CD-ROM drive off. Kind of bumming, as this was going to be my big exciting install (after playing around with installs on 3 other systems to polish my skills). Anyone up tonight who can offer some suggestions? = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
prefetching port dependencies
Quick question: I'm getting interested in using portupgrade -FR to prefetch a port's source and its dependencies (and maybe even run the fetching in a 2nd session while other parts are compiling). But I can only get it to work on stuff that is already installed. It works great then. Is there an equivalent means to prefetch dependencies for a port that ISN'T installed yet? For example, I hadn't installed mozilla yet on this box but when I ran: portupgrade -FR mozilla-devel I got an error that there was no such package installed. Sorry if this is a newbie question. [I tried to research this but case-insensitivity (-fr is diff than -FR) in search engines was making it useless.] = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86, Anti-aliasing, Truetype, Freetype
a few more specifics here *might* be somewhat helpful. Well, bear with me... if I knew exactly what specific info you needed to solve the problem, I'd probably already know the answer myself. ;) Extra info happily provided as-requested... you mention mozilla, so are you getting not-so-purdy fonts just in mozilla, just in gtk apps, just in openoffice, or all-around? This is a new setup, and until I nail this I've been trying to keep the number of installed apps to a minimum. Currently the only two X apps I've installed are OpenOffice and Mozilla. I do not get ANY anti-aliasing in Mozilla. I DO get AA and Truetype fonts in OO but they look poor. While the same TT font from Windows looks great. I've heard XFree86 TT fonts can looks just as good, so that's what I'm pursuing. If we needed to test something, I could certainly install some other program. are you actually selecting the truetype fonts to be used on said apps? this is relatively important, because while you may be using truetype fonts, anti-aliasing may not actually be working for you. Yes... I have tried choosing one of the TTF fonts that only appeared once I added the Fontpath line in XF86Config which pointed to the TTF folder. I have done this in both OO and Moz. In Moz I can see the font visibly change to a non-AA version of it. In OO it is AA but the quality of the AA job is poor. for instance, to have anti-aliased fonts with gtk12 ports, you need to install and configure gdkxft. Please excuse my ignorance here, but are Moz or OO gtk apps? concerning openoffice, though, it doesn't handle microsoft-based fonts very well, from what i've noticed, even on windows systems. it seems to me that this is a problem with openoffice (at least when dealing with the .doc format voodoo), not your configuration. Well, for what its worth, I have OO on my Windows system as well. I am looking at the exact same text in the exact same font in the same point size on each in OO Writer. On the Windows system, it looks clean and even. On the X system, the letters are thicker in uneven ways.. almost like an artificial bolding job gone bad (no, I don't have bold selected on either). It might be worth getting The Gimp installed so I can do some comparison screenshots and put them online. What's the significance of the fact that TT fonts don't appear when I have the line in XftConfig but not XF86Config like the handbook says I should do? Is this the sign of a problem which is playing a role here? = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
XFree86, Anti-aliasing, Truetype, Freetype
I'm close but not quite there yet, so I need some more help... FreeBSD 4.7-REL, Xfree86 4.2.0, Enlightenment 0.16.5, OpenOffice 1.0.1, recent Mozilla nightly, Freetype 1.3.1, Freetype2 2.1.2 I have Truetype fonts working, and they're even anti-aliased in OO, but they look like crap (certainly not like on a Windoze system). My TTF fonts are in /usr/X11R6/lib/X11/fonts/TTF but I can only get them to appear if I have the following line in XF86Config: FontPath /usr/X11R6/lib/X11/fonts/TTF According to the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-fonts.html#ANTIALIAS ...I should be able to comment out this line if I have the following line in XftConfig: dir /usr/X11R6/lib/X11/fonts/TTF But TrueType fonts don't appear if I do. So I'm thinking maybe my bad anti-aliasing is a result of something wrong here? I don't get anti-aliasing at all in Mozilla, but that's probably a whole 'nother problem... = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
gnome2 from ports fails (won't install)
Trying to make install gnome2 from ports (cvsup'ed nightly), and am failing with the following. I looked for those files (tree.h, etc) and they are all in /usr/local/include/libxml2/libxml/ so is this an include problem? Anything I can do to fix the port so it will make? In file included from ../bonobo/bonobo-ui-private.h:18, from bonobo-dock-item.c:47: ../bonobo/bonobo-ui-node-private.h:5: libxml/tree.h: No such file or directory ../bonobo/bonobo-ui-node-private.h:6: libxml/parser.h: No such file or directory ../bonobo/bonobo-ui-node-private.h:7: libxml/xmlmemory.h: No such file or directory In file included from ../bonobo/bonobo-ui-private.h:18, from bonobo-dock-item.c:47: ../bonobo/bonobo-ui-node-private.h:23: syntax error before `xmlChar' ../bonobo/bonobo-ui-node-private.h:30: syntax error before `xmlChar' gmake[2]: *** [bonobo-dock-item.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/libbonoboui/work/libbonoboui-2.0.3.2/bonobo' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/libbonoboui/work/libbonoboui-2.0.3.2' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Stop in /usr/ports/x11-toolkits/libbonoboui. *** Error code 1 Stop in /usr/ports/x11-toolkits/libgnomeui. *** Error code 1 Stop in /usr/ports/x11/gnomedesktop. *** Error code 1 Stop in /usr/ports/x11/gnomepanel. *** Error code 1 Stop in /usr/ports/x11/gnomeapplets2. *** Error code 1 Stop in /usr/ports/x11/gnome2. = Scott I. Remick --==-- ICQ: 450152 Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/ Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel est invisible pour les yeux. __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
