Re: HEADS UP: /bin and /sbin are now dynamically linked
David O'Brien wrote: On Sun, Nov 23, 2003 at 06:00:36PM -0800, Tim Kientzle wrote: Scenarios that require /rescue are ones in which /bin and /sbin are unusable, which is almost always going to imply a trashed file in /bin, /sbin, or /lib. Thus, most /rescue scenarios are going to involve locating a good copy of a trashed file to replace a damaged local copy. NO. /rescue was allowed in the system to handle the case of a trashed file in /lib[exec]. To allow a sysadmin to recover a system from the same type of mishaps they could before we went to a dynamic /. Ie, let's do things the same way we did in 1994? Other things have changed since then, hard drives and typical root partitions are much bigger, and Tim estimated the total bloat from this as 64k. Maybe earlier, pre-/rescue, you couldn't recover from damaged files in the root partition without a CD/floppy/NFS, it doesn't mean you should not have that capability in /rescue. For a *lot* of people today (like home users), an up-to-date FreeBSD CD or floppy or a second machine to create the disk on may not be handy (and forget about NFS), but a network connection may still be available. This applies equally if the trashed file is in /lib[exec]. I don't understand this argument of we have never been able to do this, therefore we shouldn't do this now even if we are able to. Rahul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble building XFree86-4-Clients.
[moving to -ports, I'm not sure it's a -current issue] Alastair G. Hogge wrote: On Saturday, 22 March 2003 22:17, Daniel O'Connor wrote: On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote: I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect the 4.3.0 clients port. I've tried completely removing and building it manuly thru make install but I get the same. -DMITSHM -DXFT -DXRENDER -c do_text.c do_text.c:403:25: X11/Xft/Xft.h: No such file or directory Tried making sure Xft and fontconfig are up to date? Both were updated with portupgrade. I was bitten by this too, as reported here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=369839+0+current/freebsd-ports and someone posted a follow-up reporting the same issue. I think this happened with the Xft2-Xft rename -- the upgrade clobbered the original libxft and xft.h from XFree86-4-libs v 4.2, but they were still in the +CONTENTS of XFree86-4-libs, and then the portupgrade of XFree86-4-libs to 4.3 removed both these files. This should be fixed. Already files aren't deleted if their original checksums don't match, unfortunately I think this is overruled with pkg_delete -f ... perhaps one needs an option which forces deleting if there are dependencies, but doesn't delete if there's a checksum mismatch? - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATAPI CDROM drive not found
Fred Souza wrote: I've just noticed that recent -CURRENT kernels (from at least 2 days to now, but I suspect it might be a little longer) do not find my ATAPI CDROM drive. This happened to me today, but it turned out that the drive wasn't recognized after a reboot if there was an audio CD already in the drive (ie, acd0 didn't show up in dmesg at all). If I rebooted with an empty drive, all was well. Anyone else notice this? - Rahul I'll send dmesg etc if relevant; my drive is acd0: LG DVD-ROM DRN-8080B/3.10 DVD-ROM drive at ata1 as master acd0: 512KB buffer, UDMA33 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Synaptics touchpad support
Paul A. Mayer said on Feb 10, 2003 at 11:01:45: Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. Yes, this was noted back then. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2003/freebsd-hackers/20030112.freebsd-hackers I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Well, without doing anything, you should be able to see some activity from the up button: in my case, it worked by default as a middle button, while the down button did nothing but showed up in xev, for example. Basically, left=1, up=2 right=3 ,down=4. What I really wanted was for up to mean up, down to mean down, and I was happy to emulate middle with simultaneous left-right as before. The following does it for me: I run moused with the options -m 5=4 -m 4=2 -a 0.5 (the -a is because this driver scales the speed up a bit too much for my liking). And in my XF86Config I have Option Emulate3Buttons Option Buttons 5 I *don't* have the Option ZAxisMapping 4 5 which the howto's for wheel mice will tell you to insert -- seems it's there by default. And if I insert it, curiously, it stops working... - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Synaptics touchpad support
Terry Lambert said on Feb 10, 2003 at 04:07:25: You actually lose the tap/tap-tap click and doubleclick button emulation with the new driver, and, as you note, the pressure sensitivity. Both of these issues were noted when the driver was posted for review. It semed the consensus at the time that until at least the tap/tap-tap was brought back (via software emulation), the driver would not be replaced, only optioned. You can check the list archives for details, I think. I don't think there was a consensus, by anyone in the know. I don't think any committer responded in the whole thread. Personally, at the time I was ambivalent, but now I'm happy it's gone... Perhaps it can indeed be reimplemented in userspace software. R To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC 3.2.2 import -- questions
Craig Rodrigues wrote: There is a long thread on the GCC mailing list right now complaining about compile-time speed regressions from 2.95.x, with many complaints coming from Apple: I don't think the original poster was talking about compile-time speed. The running speed of applications is vastly improved under gcc 3.2.x, sometimes by 30% over gcc 2.95.x, in my experience. To the OP -- any speed improvement from gcc 3.2.1 to 3.2.2 would probably be marginal. If some particular port really bothers you with its slow performance, try recompiling (though it's unlikely to help), otherwise don't bother. - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Synaptics touchpad support
Lest this disappear, like so much else, into the black hole that is GNATS, can some laptop user take a look at this? It works great for me, I can now scroll using the up and down touchpad buttons which were useless decorations earlier. Thanks to Marcin Dalecki. PR kern/48116 http://www.freebsd.org/cgi/query-pr.cgi?pr=48116 - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I've just had a massive file system crash
David Schultz wrote: I still can't figure out why the problem would trash your entire home directory, though. Even if the disk reordered writes and failed to write some sectors, directory entries that were not being actively modified shouldn't have become corrupted, as far as I know. Something similar happened to me in 4-STABLE several months ago. After a panic/crash (caused by an unstable USB audio driver) the automatic fsck failed. This happened twice; the second time my filesystem was totally messed up, and after fsck did its thing, several files were missing, including files in /usr/bin and /usr/sbin that had not been touched for many weeks (ie since the last installworld). The damage wasn't as extensive as Greg reports, and my home directory was spared, but I had to reinstall the base system to get things working smoothly again. I then turned off write caching on the IDE drive. Afterwards I had several such crashes (caused by the same driver) but never again had filesystem damage -- automatic fsck always worked. Nevertheless, as you say, it's strange files which had not been touched went missing. - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Losing time on apm -Z (despite pmtimer)
I have acpi disabled and apm enabled in /boot/device.hints
because acpi didn't do standby properly: apm -Z wouldn't turn off the
screen backlight, and on reawakening the screen would be messed up.
(acpiconf -s {2,3} didn't work either.) With acpi, the following
problem doesn't exist. It also didn't exist on 4-STABLE.
When I put the laptop into standby (apm -Z) -- suspend doesn't work --
the clock stays where it was before standby, when reawakened. (eg, if
standby'd at 10:20 and reawakened at 11:00, it still shows 10:20).
I have device pmtimer in my kernel config, and
hint.pmtimer.0.at=isa
in /device/hints. dmesg shows
pmtimer0 on isa0
This is -CURRENT cvsupped and built Jan 21, 2003.
Any ideas? Any more information I can give?
Thanks,
Rahul
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Performance problems with 5.0-RELEASE
Kenneth Culver wrote: I hope someone could bring light to what's going on. Alltho I'm not whining, I knew what I was getting myself into when I installed 5.0, it would be nice get things solved, for FreeBSD's sake already. Did you by any chance build your own kernel? If so did you leave things like this in: options INVARIANTS #Enable calls of extra sanity options INVARIANT_SUPPORT #Extra sanity checks of internal options WITNESS #Enable checks to detect deadlocks options WITNESS_SKIPSPIN#Don't run witness on spinlocks I'd like to add that even with these removed, I was experiencing terrible performance in building ports, etc (anything involving heavy filesystem activity or memory usage). Setting up an /etc/malloc.conf fixed this (this is also briefly noted in UPDATING). Specifically I use (don't know whether it's optimal, but it works): # ls -l /etc/malloc.conf lrwxr-xr-x 1 root wheel 4 Jan 23 11:52 /etc/malloc.conf - HR I didn't need to do this in 4-STABLE, however. Given that this gives really vast performance improvement with 5-CURRENT (in my experience) should something like this be in -RELEASE too? - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
malloc.conf (was Re: Performance problems with 5.0-RELEASE)
Dan Nelson wrote: # ls -l /etc/malloc.conf lrwxr-xr-x 1 root wheel 4 Jan 23 11:52 /etc/malloc.conf - HR H and should only make a difference if you are low on memory. Yes. R is on by default in 5.0 anyway, due to A and J being on by default. That's not what the malloc(3) man page suggests -- R seems to have nothing to do with A or J. Perhaps, however, the improvement I see is due to turning off A and J (implicitly, ie by not specifying them)? - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BitTorrent Mirror of 5.0
Hunter Peress wrote: We're in debian (and hence knoppix), and gentoo. Both of these packages have come from users of BitTorrent. Other packages like a ports style one will currently also have to come from users. I tried porting it some days ago, I got stuck because the wxpython port wouldn't compile (on 5.0-current). See PR ports/46985. I tried it again yesterday, and it still broke, but at a different place. - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Paul A. Mayer wrote: I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. Hm, didn't know about this port.. but it still doesn't include a mount program, and I still can't mount the partition even after installing the port. I don't want to fsck it and risk screwing it up: it's a real linux system (ie, a dual-boot machine) and the linux continues to boot perfectly nicely. But here's what I get with an e2fsck -n : # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes Not a problem for me (it's likely to be mounted read-only anyway, and I can always boot into linux to fix it if it's dirty) - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
[EMAIL PROTECTED] wrote: # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? Can you send us the output of sysctl -b kern.geom.conftxt please ? 0 DISK ad0 10056130560 512 hd 16 sc 63 1 MBR ad0s2 2928199680 512 i 1 o 7123092480 ty 131 1 MBR ad0s1 7123060224 512 i 0 o 32256 ty 165 2 BSD ad0s1e 6816876032 512 i 4 o 306184192 2 BSD ad0s1c 7123060224 512 i 2 o 0 2 BSD ad0s1b 201326592 512 i 1 o 104857600 2 BSD ad0s1a 104857600 512 i 0 o 0 - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
[EMAIL PROTECTED] said on Jan 6, 2003 at 00:14:15: I'm not an EXT2 specialist, and I don't really intend to become one, so I hope somebody else can help you out... As posted earlier, there seems to be funny stuff on my ufs disklabel too: # disklabel -r /dev/ad0s1 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 204800 634.2BSD0 0 0 # (Cyl.0*- 12*) b: 393216 204863 swap# (Cyl. 12*- 37*) c: 13912227 63unused0 0 # (Cyl.0*- 865*) e: 13314211 5980794.2BSD0 0 0 # (Cyl. 37*- 865*) Warning, partition c doesn't start at 0! Warning, partition c doesn't cover the whole unit! Warning, An incorrect partition c may cause problems for standard system utilities Should I worry about that? As for the ext2fs partition: I can probably live with it. But it may bite more people after the -RELEASE Not sure whether this information is relevant, but the ext2 partition was originally a UFS partition. A few months ago I changed it to ext2 with freebsd 4.x's fdisk and then newfs'd with the linux mke2fs binary under linux emulation (FreeBSD 4.x, again). I then wrote a gentoo bootstrap filesystem to it and was able to boot it via grub. It's worked fine since then (I haven't messed with it again under freebsd, and it's mostly been mounted read-only). - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Unable to mount ext2fs partition
I decided to bump my laptop up to 5.0-CURRENT today. All seems to have gone well and all my old binaries work fine, it looks very nice. However, I can no longer mount my linux partition: when I try, I get # mount -t ext2fs /dev/ad0s2 /mnt ext2fs: /dev/ad0s2: No such file or directory Did something change when I install new bootblocks, and how do I fix it? Below, output from fdisk and disklabel. I don't remember anything unusual before the upgrade. Thanks, Rahul --- # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 13912227 (6793 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 865/ head 254/ sector 63 The data for partition 2 is: sysid 131 (0x83),(Linux native) start 13912290, size 5719140 (2792 Meg), flag 0 beg: cyl 866/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED # disklabel -r /dev/ad0s2 # /dev/ad0s2: type: ESDI disk: ad0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 356 sectors/unit: 5719140 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: 5719140 13912290unused0 0 # (Cyl. 866 - 1221) e: 5719140 139122904.2BSD 1024 819216 # (Cyl. 866 - 1221) partition c: offset past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities partition e: offset past end of unit partition e: partition extends past end of unit To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
However, I can no longer mount my linux partition: when I try, I get # mount -t ext2fs /dev/ad0s2 /mnt ext2fs: /dev/ad0s2: No such file or directory Here's the ata/geom related parts of the dmesg output: - Rahul atapci0: VIA 82C686 ATA66 controller port 0x1420-0x142f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x1420 ata0: mask=03 ostat0=50 ostat2=00 ata0-slave: ATAPI 00 00 ata0-master: ATAPI 00 00 ata0: mask=03 stat0=50 stat1=50 ata0-master: ATA 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x1428 ata1: mask=03 ostat0=50 ostat2=01 ata1-master: ATAPI 14 eb ata1-slave: ATAPI 00 00 ata1: mask=03 stat0=00 stat1=01 ata1-slave: ATA 24 a5 ata1: devices=06 ata1: at 0x170 irq 15 on atapci0 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it ad0: success setting UDMA4 on VIA chip GEOM: new disk ad0 ar: FreeBSD check1 failed ad0: TOSHIBA MK1517GAP/A1.04 H ATA-5 disk at ata0-master ad0: 9590MB (19640880 sectors), 19485 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=5 cblid=1 ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting UDMA2 on VIA chip acd0: LG DVD-ROM DRN-8080B/3.10 DVD-ROM drive at ata1 as master acd0: 512KB buffer, UDMA33 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc GEOM: Configure ad0s1, start 32256 length 7123060224 end 7123092479 GEOM: Configure ad0s2, start 7123092480 length 2928199680 end 10051292159 GEOM: Add ad0s1 hot[0] start 512 length 276 end 787 GEOM: Configure ad0s1a, start 0 length 104857600 end 104857599 GEOM: Configure ad0s1b, start 104857600 length 201326592 end 306184191 GEOM: Configure ad0s1c, start 0 length 7123060224 end 7123060223 GEOM: Configure ad0s1e, start 306184192 length 6816876032 end 7123060223 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Craig Rodrigues said on Jan 4, 2003 at 22:41:50: You truncated too much stuff, can you repost the whole dmesg output, not just the parts you think are relevant. OK, here it is at the bottom. Also, what do you get when you do the following: file - /dev/ad0s1a standard input: x86 boot sector, system, BSD disklabel file - /dev/ad0s1b standard input: Unix Fast File system (little-endian), last mounted on /usr2, last written at Fri Jan 11 13:34:17 2002, clean flag 1, number of blocks 6853713, number of data blocks 6642013, number of cylinder groups 210, block size 8192, fragment size 1024, minimum percentage of free blocks 8, rotational delay 0ms, disk rotational speed 60rps, TIME optimization file - /dev/ad0s1c standard input: x86 boot sector, system, BSD disklabel file - /dev/ad0s1e standard input: Unix Fast File system (little-endian), last mounted on /usr, last written at Sat Jan 4 22:46:06 2003, clean flag 0, number of blocks 6657105, number of data blocks 6451453, number of cylinder groups 204, block size 8192, fragment size 1024, minimum percentage of free blocks 8, rotational delay 0ms, disk rotational speed 60rps, TIME optimization And for file - /dev/ad0s2, it gives standard input: x86 boot sector, BSD disklabel HTH - Rahul --- Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Jan 4 13:49:25 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLUERONDO_CURRENT Preloaded elf kernel /boot/kernel/kernel at 0xc054. Preloaded elf module /boot/kernel/acpi.ko at 0xc05400a8. Calibrating clock(s) ... TSC clock: 799980311 Hz, i8254 clock: 1193294 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 799914775 Hz CPU: Pentium III/Pentium III Xeon/Celeron (799.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 129957888 (123 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00567000 - 0x07be7fff, 124260352 bytes (30337 pages) avail memory = 120438784 (114 MB) bios32: Found BIOS32 Service Directory header at 0xc00f74f0 bios32: Entry = 0xfd720 (c00fd720) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd720+0x11e pnpbios: Found PnP BIOS data at 0xc00f7540 pnpbios: Entry = f:a2f9 Rev = 1.0 pnpbios: OEM ID 1500110e Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06011106) Using $PIR table, 5 entries at 0xc00fdf70 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded09A 0x02 11 embedded09B 0x03 9 embedded0 11A 0x05 11 embedded07A 0x01 9 embedded07B 0x02 11 embedded07C 0x03 9 embedded07D 0x05 11 embedded01A 0x01 9 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 1, max = 6, width = 6 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 3, width = 3 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 acpi_acad0: AC adapter on acpi0 acpi_cmbat0: Control method Battery on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.PCI0.PIB_.LNKA irq 9: [ 9 11 12] low,level,sharable 0.1.0 \\_SB_.PCI0.PIB_.LNKA irq 9: [ 9 11 12] low,level,sharable 0.7.0 \\_SB_.PCI0.PIB_.LNKB irq 11: [ 9 11 12] low,level,sharable 0.7.1 \\_SB_.PCI0.PIB_.LNKC irq 9: [ 9 11 12] low,level,sharable 0.7.2 \\_SB_.PCI0.PIB_.LNKD irq 11: [ 9 11 12] low,level,sharable 0.7.3 \\_SB_.PCI0.PIB_.LNKD irq 11: [
Re: [Discuss] FreeBSD 5.0 Version of CrossOver Office. (fwd)
I sent the following to the Codeweavers (http://www.codeweavers.com) crossover discussion list, in response to a couple of mails about FreeBSD 5.0. However, I'm not totally sure it's the right answer -- if not, perhaps one of the developers can send a better answer? (One needs to be subscribed to the list to post.) I think crossover is useful/important to many users, so a correct and useful answer to the codeweavers people is highly desirable. Thanks, Rahul - Forwarded message from Rahul Siddharthan [EMAIL PROTECTED] - Date: Fri, 22 Nov 2002 23:48:00 -0500 From: Rahul Siddharthan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Discuss] FreeBSD 5.0 Version of CrossOver Office. Jeremy White said on Nov 22, 2002 at 08:02:15: A question for you: if we get a working binary build under FreeBSD 4.7, will that run out of the box on FreeBSD 5.0, or will we have to recompile (in other words, do I have to rip out the extra FreeBSD 4.7 development box we just put in, or will it suffice grin). If you're targeting FreeBSD, please target 4.7 for now. 5.0 is a really major upgrade, and will take at least a few months to stabilize; most people will be running 4.x for the near future. I'm not totally sure if a 4.x binary will work on 5.x (I'm not a developer) but if 4.x binaries don't work on 5.x, I think the developers will try to get them working; but a 5.x binary will not work on a 4.x machine at all and will be useless for most FreeBSD users for at least the next few months. Thanks - Rahul ___ discuss mailing list [EMAIL PROTECTED] http://crossover.codeweavers.com/mailman/listinfo/discuss - End forwarded message - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: problems with Ghostscript5/55/6
Ghostscript55: It will build and install. When I run "gs", I get: bash-2.03# gs /usr/local/share/ghostscript/5.50/examples/tiger.ps Aladdin Ghostscript 5.50 (1998-9-16) Copyright (C) 1998 Aladdin Enterprises, Menlo Park, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. showpage, press return to continue GS snip bash-2.03# gs /usr/local/share/ghostscript/6.01/examples/tiger.ps Aladdin Ghostscript 6.01 (2000-03-17) Copyright (C) 2000 Aladdin Enterprises, Menlo Park, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /invalidfileaccess in --.outputpage-- snip Try gs -sDEVICE=x11 /usr/local/share/ghostscript/6.01/examples/tiger.ps gs --help will give you available options. For viewing stuff on the screen, install a front-end such as gv -- there's no point in messing with gs directly. Rahul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
