Dual booting FreeBSD and Linux using GRUB fails
I have an all-SCSI system with FreeBSD 6.3 on one disk and 7.0 on the other. It booted using GRUB and worked OK. I installed Mandriva Linux on the disk that had 7.0 on it (replacing 7.0) The setup now is: SCSI ID 15 73GB /dev/sda - running FreeBSD SCSI ID 14 36GB /dev/sdb - Mandriva The device names above are as reported by Mandriva when doing the install. Mandriva installed OK onto the 36GB HDD and wrote this menu.lst: Code: timeout 10 color black/cyan yellow/cyan gfxmenu (hd0,0)/boot/gfxmenu default 0 title linux kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=77a15e0a-b9f5-46ab-8236-886418dbbfd8 resume=/dev/sdb5 splash=silent vga=788 initrd (hd0,0)/boot/initrd.img title linux-nonfb kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=77a15e0a-b9f5-46ab-8236-886418dbbfd8 resume=/dev/sdb5 initrd (hd0,0)/boot/initrd.img title failsafe kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=77a15e0a-b9f5-46ab-8236-886418dbbfd8 failsafe initrd (hd0,0)/boot/initrd.img Note that it has used hd0 even though the disk is /dev/sdb (which implies the second disk). The problem is that when it boots the Adaptec SCSI BIOS searches for bootable drives from the highest SCSI ID downwards. Since the 73GB (FreeBSD) disk is id 15 it boots from that. That disk also has GRUB installed with an entry for FreeBSD which is also hd0. The FreeBSD entry works. Because the disks are seen by the SCSI BIOS as id 15 first, id 14 second, id 14 - the disk with Mandriva installed, is hd1 so I copied the Mandriva menu.lst file into the one on the FreeBSD partition and edited hd0 to hd1 (for both the lernel and initrd lines) but Mandriva won't boot, I get Error 2: Bad File or Directory type In fact, the FreeBSD GRUB seems unable to read the Linux disk - it knows it's there, but can't access anything on it. I've tried numerous things as suggested on the Mandriva forums but nothing works: grub> root (hd0,0,a) Filesystem type is ufs2, partition type is 0xa5 grub> cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/da0 (hd1) /dev/da1 grub> root (hd1,0) Filesystem type is ext2, partition type is 0x83 grub> cat /boot/grub/device.map Error 2: Bad file or directory type grub> root (hd Possible disks are: hd0 hd1 grub> root (hd1, Possible partitions are: Partition num: 0, Filesystem type is ext2fs, partition type 0x83 Partition num: 4, Filesystem type is unknown, partition type 0x82 Partition num: 5, Filesystem type is ext2fs, partition type 0x83 grub> root (hd0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'b', Filesystem type is unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'e', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'f', Filesystem type is ufs2, partition type 0xa5 Can anyone suggest how to make this work? The root of the problem is that both OSes think their disk is hd0. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Effects of CPUTYPE
On Thu, June 5, 2008 00:24, Jonathan Chen wrote: > In my personal opinion, the small gain you get is more than > overwhelmed by the big pain you get from setting CPUTYPE. Thanks Jonathan. I think I'll reinstall my 7.0 system from scratch and install the apps from packages rather than build from ports and see if that solves the problems. The thing is that the main "serious" use for this box is managing my digital photos - over 12GB of them - and it is getting increasingly difficult with the apps I choose to use becoming unreliable. I've really got to the point where I'm considering switching to Linux as I've tried Mandriva and all the apps I use that I'm having problems with on FreeBSD work just fine under Linux. I don't want to switch - I've been using FreeBSD for ~13 years (since 2.0.5) but since I ditched Windows nearly 2 years ago I need reliability. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Effects of CPUTYPE
For months now I've been having ever increasing problems with software (ports) stopping working - or not working properly; xorg, digikam, jalbum, etc. The problems are the same on 6.3-STABLE and a brand new, clean install of 7.0. Searching mailing lists and Google makes me think that a lot of these problems are specific to my system. Trying to identify why I should be having all these problems I've been looking for anything that may be specific to my machine. One thing I've come up with is the fact that I have CPUTYPE?=athlon-mp in /etc/make.conf on both 6.3 and 7.0. I understand that this optimizes compilation for that CPU but can this potentially cause problems? Is this a possible cause of strange problems? All my ports are built from source rather than from packages so are built with this option. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Bob McConnell wrote: From: Mark Ovens If anyone can tell me how to debug this to try to get to the cause so a fix can be found then I'm happy to spend the time doing so. Unless you are already familiar with the drivers and the bus itself, or want to learn more about it than anyone should ever need to know, it is not likely to be a productive use of your time. Hehe, yes, I kind of guessed the answer would be something like that. Oh well, never mind. I bought it off FleaBay and it did say Windows/Mac but I figured something as basic as a ATA->USB bridge should be OS agnostic - to be fair it is, as it sees the disk and creates devices for it, it's just that the USB interface is not standards-compliant. I fired up the Mandriva Linux Live CD and tried it. Linux found the disk, created devices for it - then did a USB reset and the devices disappeared. Might have a word at work and see if they'll swap it with the one I borrowed that does work. Thanks for your help guys. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Mark Ovens wrote: Hi Roland, I had to rebuild the kernel without umass in it first, but here's the result. Follow up: I discovered that atausb wants to attach the disk as a floppy and I don't have a FD so the module isn;t compiled into my kernel. kldload'd atapifd.ko and it now sees the disk as afd0 - but it crashes the kernel (in 6.3) just like umass did in 7.0, Fatal Trap 12. Built atausb in 7.0 and same thing. Guess I'll just have to accept that I've bought a pup - I've noticed that the USB2.0 Hi-Speed logo on the box is not the official one so I guess it just doesn't comply with the USB standards. If anyone can tell me how to debug this to try to get to the cause so a fix can be found then I'm happy to spend the time doing so. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Roland Smith wrote:
On Wed, May 28, 2008 at 08:37:55PM +0100, Mark Ovens wrote:
Roland Smith wrote:
You could try using the atausb driver instead of umass. Unfortunately it
doesn't have a manpage yet, but you have to unload umass if you want to
use atausb.
Thanks Roland, but I can't find atausb in either 6.3 or 7.0 - is it a kld
module?
Yes;
$ locate atausb
/usr/src/sys/modules/ata/atausb
/usr/src/sys/modules/ata/atausb/Makefile
(This is on 7-STABLE)
Presumably, it would not work with other usb mass storage devices like
memory sticks or phones?
It should work with all usb mass storage devices, I think. It just seems
to be tied into the ata subsystem instead of into the scsi subsystem via
atapicam.
Hi Roland,
I had to rebuild the kernel without umass in it first, but here's the
result.
It attaches the device as an ata rather than umass - but no devices are
created for the slices/partitions on the disk.
atausb0: using SCSI over Bulk-Only
ata2: on atausb0
/boot/kernel{105}# ls /dev/ata*
/dev/ata
/boot/kernel{106}# ls /dev/ad*
ls: No match.
/boot/kernel{107}# kldstat
Id Refs AddressSize Name
1 10 0xc040 4e1cb8 kernel
21 0xc08e2000 21ef8linux.ko
31 0xc0904000 65de0acpi.ko
41 0xc5898000 5000 atausb.ko
51 0xc589d000 d000 ata.ko
/boot/kernel{108}#
I've only tried it on 6.3 at the moment and atausb/Makefile didn't
exist, so I copied it from 7.0, it built and installed without error,
the module kldload'd without error, and it finds the device so I assume
it should be OK in 6.3 even though the Makefile doesn't get cvsup'd?
Regards,
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Roland Smith wrote: Yes; $ locate atausb /usr/src/sys/modules/ata/atausb /usr/src/sys/modules/ata/atausb/Makefile (This is on 7-STABLE) Ah, so it's not built by default! Presumably, it would not work with other usb mass storage devices like memory sticks or phones? It should work with all usb mass storage devices, I think. It just seems to be tied into the ata subsystem instead of into the scsi subsystem via atapicam. Great, I'll try it out and let you know how it goes. Thanks. Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Roland Smith wrote: You could try using the atausb driver instead of umass. Unfortunately it doesn't have a manpage yet, but you have to unload umass if you want to use atausb. Thanks Roland, but I can't find atausb in either 6.3 or 7.0 - is it a kld module? Presumably, it would not work with other usb mass storage devices like memory sticks or phones? Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Mark Ovens wrote:
Chuck Robey wrote:
I saw a mail yesterday about something nearly like this, from nej, except with
him, the umass device wasn't reporting anything at all, no device when he
plugged it in. I sent him a little piece of usb driver code that resets his usb
buss, just to experiment and see if that got his devices correctly detected, but
he didn't yet reply, I don't know if it worked for him. I don't have something
like that to experiment with.
With yours, you obviously have a da2 ... that only means you have a
direct-access disk devide #2 being detected. The next step is to figure oout
what kind of formatting you have. Hopefully, it's been fdisk'ed to where it has
partitions, so do this (as root): "/sbin/fdisk /dev/da2", and in fdisk, give the
'p' command, this will print out the formatting for any partitions. Likely it's
either one of the various Microsoft things, or a Linux one, or even a FreeBSD
one. Depending on what you see, you either directly give a mount command next,
to the right partition, or maybe you use bsdlable to find out what the
disk-labelling is (if it's a FreeBSD disk).
Hi Chuck,
The next line in my post after where you snipped was:
(The disk is from another FreeBSD system so is UFS2 and da2s1f is /usr
on the other system)
It contains a running FBSD 7.0 system - it's out of a spare box I was
using for testing and it mounts/reads/writes fine using the other USB
enclosure I borrowed. There's just something screwy about the enclosure
I've bought (typical eh?)
Forgot to add the output of fdisk.
/home/mark{104}# /sbin/fdisk /dev/da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=4866 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=4866 heads=255 sectors/track=63 (16065 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 78172227 (38170 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
The data for partition 3 is:
The data for partition 4 is:
/home/mark{105}#
Regards,
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: External USB disk won't mount
Chuck Robey wrote: I saw a mail yesterday about something nearly like this, from nej, except with him, the umass device wasn't reporting anything at all, no device when he plugged it in. I sent him a little piece of usb driver code that resets his usb buss, just to experiment and see if that got his devices correctly detected, but he didn't yet reply, I don't know if it worked for him. I don't have something like that to experiment with. With yours, you obviously have a da2 ... that only means you have a direct-access disk devide #2 being detected. The next step is to figure oout what kind of formatting you have. Hopefully, it's been fdisk'ed to where it has partitions, so do this (as root): "/sbin/fdisk /dev/da2", and in fdisk, give the 'p' command, this will print out the formatting for any partitions. Likely it's either one of the various Microsoft things, or a Linux one, or even a FreeBSD one. Depending on what you see, you either directly give a mount command next, to the right partition, or maybe you use bsdlable to find out what the disk-labelling is (if it's a FreeBSD disk). Hi Chuck, The next line in my post after where you snipped was: (The disk is from another FreeBSD system so is UFS2 and da2s1f is /usr on the other system) It contains a running FBSD 7.0 system - it's out of a spare box I was using for testing and it mounts/reads/writes fine using the other USB enclosure I borrowed. There's just something screwy about the enclosure I've bought (typical eh?) Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
External USB disk won't mount
Bought an external USB HD enclosure but it doesn't work under FreeBSD. Under FreeBSD-6.3-STABLE: umass0: Super Top USB 2.0 IDE DEVICE, rev 2.00/2.01, addr 2 da2 at umass-sim0 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: 38172MB (78177792 512 byte sectors: 255H 63S/T 4866C) # mount /dev/da2s1f /mnt # ls /mnt # (The disk is from another FreeBSD system so is UFS2 and da2s1f is /usr on the other system) So although it mounts, nothing is visible. After a few minutes this happens: umass0: at uhub3 port 1 (addr 2) disconnected (da2:umass-sim0:0:0:0): lost device (da2:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0 (da2:dead_sim0:0:0:0): removing device entry umass0: detached Tried it under 7.0-RELEASE and it's even worse - it crashes the kernel with Fatal Trap 12: page fault in kernel mode. (forget the exact wording of the message, but it's definitely Fatal Trap 12). So is this just a case of the device not complying with USB standards - the manufacturer just tests it under Windows and that's good enough - or is there a way to solve this? I can confirm that the disk is good as I borrowed another enclosure to try and that works as expected. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Stick memory USB
Chuck Robey wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 nej ALL wrote: Hi, I'm new on FreeBSD not on unix. I want to mount automatically an usb-stick memory into my machine ? I get some problems. Need help. You're trying with your devfs stuff to create the file, but you have to realize it's a device representing a filesystem, not just a file. What you want to read is the mount and fstab man pages, mount to find out how to mount your memory stick, and fstab to figure out how to get it to happen automatically. The devfs stuff is all mistaken, I think, you want that when you want to change permissions or make softlinks of devices, not to create them in the first place, least that's how I';'ve always used it, and I know very well that the correct line in /etc/fstab WILL automount your memory stick. Are you sure Chuck? The devfs rules stuff is to allow non-root users to mount removable media isn't it? I followed the instructions at http://gphoto.sourceforge.net/doc/manual/permissions-usb.html - the FreeBSD-specific stuff is near the bottom of the page - but I have *exactly* the same problem as the OP with my mobile phone. It is detected as da2 and da3 (phone and memory stick - mine's a SCSI system so da0 and da1 are the HDDs) but only the top-level device nodes (/dev/da[23]) are created. I can try to mount /dev/da3 until I'm blue in the face and it always fails but as soon as I attempt to mount /dev/da3s1 it fails first time but succeeds the second time because the /dev/da3s1 device node gets created on the first (failed) mount attempt. It doesn't matter whether I have an entry in /etc/fstab for /dev/da3s1 or not, it stills fails, but creates the device, on the first attempt. Maybe something has changed? The page I linked to above refers to FreeBSD 5 but I'm running 6.3-STABLE. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best nVidia card for Xorg on FreeBSD?
Manolis Kiagias wrote: Don't know about CompuViz, but if you would like to try compiz fusion, I am a bit tempted to point you to this article (maybe because I am the author :) Ah, compiz - that's what I was thinking of ;-) http://www.freebsd.org/doc/en_US.ISO8859-1/articles/compiz-fusion/ This will answer your questions on installing nvidia drivers and also getting 3D effects and compiz-fusion to work. Note that there is no nvidia-supplied (read: proprietary) driver for the 64bit version of FreeBSD. The community 'nvidia' driver works fine, although no 3D and 2D performance is somewhat limited. I've used a number of cards with FreeBSD (7300GT, 7300Go (laptop), 6600GT, 6200) and never had problems. The FX series should also work, but why not buying a newer card? You can get new entry-level nvidia cards for very little money. Well, it's down to money really but I'll take a look at the price of new cards. Thanks. Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Best nVidia card for Xorg on FreeBSD?
Currently using a Radeon 8500LE but since u/g to xorg 7.3 I've had nothing but trouble with X hanging/crashing/locking-up. From what I've read, the state of the radeon drivers leaves much to be desired and although some people seem to have trouble with nVidia cards they appear to be a better choice. So, after over a decade of brand-loyalty to ATI (when I started with FreeBSD back in the mid-90's ATI cards were the only ones I could find that would run X at better than VGA resolution) I'm going to switch to nVidia. The machine is FreeBSD-only so no issues with Windows drivers and performance etc. (I divorced the Evil Empire a couple of years ago) and my Radeon 8500 is adequate for my needs so I don't need a high-end card. I'm looking on eBay and an FX5x00 card seems to fit the bill. So, are there any particular cards that work well under Xorg/FreeBSD or, more importantly, any that don't? Any advice about the need to consider 3D issues would be welcome? I run KDE and mainly use digikam/GIMP for digital photo editing and kmplayer for viewing videos. I believe there is a 3D interface for KDE (CompuViz?) - is this worth bothering with? All help/advice gratefully received. TIA Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.org 7.3 sure is a mess...
Peter Boosten wrote: Ken Gunderson wrote: [snip] Looks like you're having a problem with your window manager, instead of Xorg. Mine (with enlightenment-devel) works like charm. None of the issues you describe anyway. Peter So how would you explain that I am seeing same type of behaviors in straight "startx" with default twm, i.e. bundled Xorg wm? Dunno. But the troubles cannot originate from the xorg ports, or everyone would see the same behaviour, right? > Maybe some other port, or hardware (maybe your video card? - just > guessing), or the driver for that particular piece of hardware. > One would expect so, but it would appear not to be the case. I'm having the same problem - if I ssh in from another box I see the Xorg process sucking >100% CPU and the state is *GIANT I'm using an ATI card but people are having the same issue with nVidia and Matrox cards. My box has run every version of Xorg since it replaced XFree86 on FreeBSD and many versions of XFree86 before that without this problem. Also, the problem seems to come and go for me as I update my ports, i.e. the box has the problem, I run ``portmaster -a'' and the problem goes away. sometime later I run ``portmaster -a'' again and the problem re-appears. Only seems to happen when X-related stuff gets updated. The other thing I've noticed is, on my box at least, that the problem always starts when I move the mouse (not every time of course) so could it be Xorg 7.3 not playing nicely with the mouse driver - or the USB driver since my mouse is a USB one? Which may explain why some people see the problem and others don't? This is really becoming a big PITA. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any software that can do X windows screen capture (with mouse cursor)
Nicholas Godson wrote: So what you are wanting is a program like Snag-It for Windows, Ksnapshot can do this I think. Haven't used it in quite a while though. KSnapshot doesn't grab the cursor either. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0 nvidia-driver woes
Darren Spruell wrote: During attempted startup and when using CTRL+ALT+BKSP to kill the server the Xorg process drives CPU usage to 100%: PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 1203 root 1 1180 28168K 23960K CPU1 1 1:21 100.00% Xorg I have exactly the same problem with an ATI card (radeonhd driver) except that the STATE of Xorg is *GIANT and recently I've seen CPU usage figure exceed 400% - yes *four* hundred!! In my search for a solution I've found someone with the same problem with a Matrox card. I've come to the conclusion that Xorg 7.3 is a crock - at least on FreeBSD - since I've never had some many problems under any previous version of Xorg, or XFree86. Is it possible to install Xorg 7.2 on FreeBSD 7.0? FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. Hmm, I see this too (although I think it is freetype on my box, not misc) - any idea what it means? Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD 7] Radeon Mobility M10/9600 + xorg 7.3 + ati/radeon driver causes complete system hang/freeze
Torgeir Hoffmann wrote: On beforehand, I appologize for sending a rather incomplete mail regarding this last week, I hope with this new information that I can find a clue on how to debug or solve this problem. I have the following problems with my xorg 7.3 installation, even after I have pkg_delete -a, and reinstalled all with packages. The system was updated with freebsd-update from 6.3-release to 7.0-release. This sounds similar to the problem I have with 7.3 and a Radeon 8500LE card. Never had this problem with any previous version of Xorg (or XFree86). when the system hangs I can ssh(1) in from another box and find that Xorg process is sucking as much as 400% - yes four *hundred* percent - CPU ? It is holding a Giant Lock - State is *GIANT I can kill the Xorg process but on the affected box I just end up with a blank black screen so have to Ctrl-Alt_Del to reboot. The problem seems to come and go as I update installed ports. If I've got the problem then updating the ports gets rid of it (sometimes) and when the system is working a port upgrade starts it off again (sometimes). It seems to be one of the X ports being updated that is the cause but I don't know which - xorg-drivers seems a likely culprit. One thing I did do was to delete the port xf86-video-radeonhd which fixed the problem once. I don't know what installed it as a dependency but it hasn't been reinstalled - although the problem still comes and goes. I've had this on 6.3 and on 7.0 (completely clean build, not an upgrade from 6.3). As I said, this has only been a problem since u/g Xorg from 7.2->7.3 and it is becoming a PITA. I wonder if it's just that Radeon cards don't work too well with FreeBSD and/or Xorg?? Perhaps it's worth swapping to nVidia? Don't know whether any of that helps? Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: So How Hard Is Moving From 6.3 To 7.0?
This post hasn't appeared on the list after almost 24 hours so I'm re-posting. Apologies if it appears twice. It seems that about 50% of the posts I make to the lists (-questions and -ports) never show up. Matthew Seaman wrote: I've been doing a bunch of 6.x -> 7.0 upgrades recently. Here's a few hints I've picked up along the way: [snip the gory details] Thanks for that Matthew, it confirms that I've made the right decision to do a completely clean install :-) Which leads me to ask if there are likely to be any issues with dual-booting 6.3-STABLE (as of ~1 month ago) and 7.0-RELEASE? I vaguely recall from way back there being issues with dual-booting multiple versions of FreeBSD. Maybe that was when trying to install both in the same slice? Mine will be installed on separate hard disks. The only thing I could think may possibly be an issue is the FreeBSD Boot Manager. The current setup uses the FBSD BM to boot FBSD and Ubuntu on separate disks - it's the Ubuntu disk that I will be zapping to install 7 - is there anything to watch out for (apart from the obvious stupidity of selecting the wrong disk to newfs ;-) ) Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: su problem
Martin Schweizer wrote: Hello If I su from user martin to root or from user martin to martin (for testing) I get this errors in /var/log/messages: [snip] May 9 11:33:08 merkur init: can't get /dev/console for controlling terminal: Operation not permitted May 9 11:33:38 merkur init: can't get /dev/console for controlling terminal: Operation not permitted [snip] I crosschecked also the permissions on /dev/console. They are correct. Any hints are welcome. IIRC you need this line in /etc/fbtab (or uncomment it if it's there but commented out) - that's what I've got and I'm sure that's why it's there; I don't get those errors. /dev/ttyv0 0600/dev/console HTH Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 80 pin SCSI hard drives.
Alfredo Finelli wrote: I have 80 pin SCSI discs mounted in hot-swappable trays on a SCSI backplane which takes care also of powering them up and of SCSI termination. This is one way of using them. I also have the same drives in a different system connected to normal SCSI LVD cable using small adaptors which have an 80 pin receptacle on one side and a 68 pin SCSI connector plus 4 pin molex power connector on the other, as well as jumpers to define SCSI id. In this second case you have to provide the required termination of the SCSI bus (e.g. using the right terminated SCSI cable). So you can confirm that using these adaptors works OK? When I bought my SCSI drive (off eBay) there were more SCA drives for sale than 68-pin but doing some research about 80->68 pin adaptors I found a lot of people saying not to use them, including Adaptec: This from Adaptec's ASK knowledgebase http://tinyurl.com/b3ofa "Although there are adapters on the market converting 80 pin to 68 pin they are not supported by Adaptec or the hard drive manufacturers. These convertors can cause loss of signal integrity that may result in connectivity issues and data loss." This put me off getting a SCA drive. Now I'm looking for a another drive and SCA ones seem to be cheaper on eBay. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Virtual CD drive for FreeBSD?
Is there such a thing as a virtual CD drive in the Ports. Something that allows you to treat an ISO image file - data or audio - as though it were a real CD in a real drive? Like Nero ImageDrive in Windows. TIA Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: System time suddenly changed after reboot.
Scott Ballantyne wrote: Running 5.3-RELEASE. After many years of using FreeBSD, and as many reboots or more, I had occasion to reboot today, and a few hours later discovered to my horror that the system time had suddenly been moved ahead to the year 2020! I did the best I could with the resulting mess, but I am curious if anyone else has seen this, or what would cause it. This is the same hardware I have been running for a couple of years now, and I haven't changed anything in the bios or system. I had that problem back with early versions of 5.x - up to 5.3 IIRC - except that it happened with 9 out of 10 reboots for me. After weeks of trying to solve the problem it turned out to be the keyboard!!1 Yes, the fscking keyboard. It's a Compaq USB and I'm guessing that there is something non-standard about it (it won't work when connected to a PS/2 port via an adaptor for instance). Don't know whether this helps you. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with local rc.d scripts in 6.0
Since src u/g 5.4->6 the *_enable variables in rc.conf for local rc.d
scripts are being ignored. For example, neither lisad (for KDE LAN
Browsing) or giftd (for giFT) are starting.
In rc.conf I have:
lisa_enable="YES" # Lisa daemon for LAN Browsing in Konqueror
giftd_enable="YES"
giftd_flags="-d -q"
giftd_user="mark"
giftd_local_dir=""
Adding 'rc_debug="YES"' to rc.conf shows:
/etc/rc: DEBUG: checkyesno: usbd_enable is set to YES.
Starting usbd.
/etc/rc: DEBUG: run_rc_command: _doit: /usr/sbin/usbd
/etc/rc: DEBUG: checkyesno: nis_yppasswdd_enable is set to NO.
/etc/rc: DEBUG: checkyesno: lisa_enable is set to NO.
/etc/rc: DEBUG: checkyesno: giftd_enable is set to NO.
cups: started scheduler.
/etc/rc: DEBUG: checkyesno: slpd_enable is set to NO.
/etc/rc: DEBUG: run_rc_command: evaluating pkgtools_start().
Note that lisa_enable and giftd_enable are NO.
I've tried moving the lines from rc.conf to rc.conf.local but it makes
no difference.
Old-style .sh scripts in /usr/local/etc/rc.d are being run from
/etc/rc.d/localpkg
In /etc/rc we have
# Now that disks are mounted, for each dir in $local_startup
# search for init scripts that use the new rc.d semantics.
#
case ${local_startup} in
[Nn][Oo] | '') ;;
*) find_local_scripts_new ;;
esac
so they are being run but the variables set in rc.conf are not being
honoured so the daemons aren't started.
Once the system is up the scripts work OK from the command line:
/home/mark{107}# /usr/local/etc/rc.d/lisa.sh start
/usr/local/etc/rc.d/lisa.sh: DEBUG: checkyesno: lisa_enable is set to YES.
Starting lisa.
/usr/local/etc/rc.d/lisa.sh: DEBUG: run_rc_command: _doit:
/usr/local/bin/lisa -q -c /usr/local/etc/lisarc
/home/mark{108}#
So the variables are now being honoured.
I've found several threads in the mailing lists about rc.d problems, but
not this particular one, and haven't been able to figure out the cause.
I wonder if I screwed up when running mergemaster(8) after the upgrade?
Any help would be appreciated.
Regards,
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkgdb format
Colin Percival wrote:
Mark Ovens wrote:
After reading this thread, I killed the upgrade, deleted INDEX-6,
INDEX-6.db, and pkgdb.db; rebuilt pkgdb.db using `pkgdb -u' and re-ran
`portupgrade -af'
It started off OK (using dbm_hash) but after a couple of hours it had
started continually rebuilding pkgdb.db.
Anyone else got any ideas?
I had exactly the same problem during portupgrading after a 5.4->6.0
base system upgrade until I did a `portupgrade -fR portupgrade`, at
which point it stopped (and has been fine ever since). I have no idea
what the problem is or why this would fix it, but you might like to
try this and see if it helps.
Thanks! That seems to have fixed it for me too - it's now using
bdb1_btree consistently :-)
As to why, I'm not sure, but here's what upgrading portupgrade the way
you suggested affects:
/home/mark{101}# portupgrade -fRn portupgrade
[snip]
---> Listing the results (+:done / -:ignored / *:skipped / !:failed)
+ databases/db4 (db4-4.0.14_1,1)
+ lang/perl5.8 (perl-5.8.7_2)
+ lang/ruby18 (ruby-1.8.2_5,1)
+ databases/ruby-bdb (ruby18-bdb4-0.5.7)
+ sysutils/portupgrade (portupgrade-20051204)
---> Packages processed: 5 done, 0 ignored, 0 skipped and 0 failed
I don't know if any of those were actually upgraded or just reinstalled
but databases/ruby-bdb looks like a candidate for being the culprit
since portupgrade uses ruby so, if ruby itself and one or more of it's
dependencies are out of sync it could explain it; i.e. if part of ruby
got upgraded but not another by `portupgrade -af' - although if that is
the case it is puzzling that when I aborted the first run, deleted the
INDEX and pkgdb files that it ran OK for a while - the ports that had
already been upgraded hadn't been downgraded
Maybe portupgrade needs to be changed to upgrade itself
upward-recursively first whenever the -a option is used?
Thanks again for your help.
Regards,
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkgdb format
Kent Stewart wrote: On Wednesday 07 December 2005 12:55 pm, eoghan wrote: Hello Ive recently upgraded to 6.0 and I decided to upgrade my ports... So I ran a: portupgrade -af Its running fine, but each time its upgrade a port I get: [Updating the pkgdb in /var/db/pkg ... Failed `Inappropriate file type or format'; rebuild needed] [Rebuilding the pkgdb in /var/db/pkg ... - 439 packages found (-0 +439) Just wondering if its to do with my upgrade to 6.0 (from 5.4) Thanks Not from my experience. You are setting the package database interface one way in one spot and using the default someplace else. Since they are incompatible, it has to rebuild the port data base. Look for the string bdb in your scripts and in pkgtools.conf. I've got the same problem running `portupgrade -af' after upgrading from 5.4 -> 6 After reading this thread, I killed the upgrade, deleted INDEX-6, INDEX-6.db, and pkgdb.db; rebuilt pkgdb.db using `pkgdb -u' and re-ran `portupgrade -af' It started off OK (using dbm_hash) but after a couple of hours it had started continually rebuilding pkgdb.db. The sequence is: Build new version of port Rebuild pkgdb.db in bdb1_btree format Backup old version of port Rebuild pkgdb.db in dbm_hash format Uninstall old version of port Rebuild pkgdb.db in bdb1_btree format Deinstall Clean Rebuild pkgdb.db in dmb_hash format It is rebuilding pkgdb.db *4 times per port* which will add several hours to the build time. The fact that Kent hasn't had this problem and that the upgrade started off correctly for me suggests that it goes wrong when a particular port gets installed. OP: Did you find a solution to this? Kent: I don't have the string bdb in pkgtools.conf, nor anywhere else I can think to look, except INDEX-6.db - but that was built when portupgrade started and things worked OK at first. Anyone else got any ideas? Regards and a Happy New Year Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please don't change Beastie to another crap logo suchasNetBSD!!!
Anthony Atkielski wrote: Linux is a great case in point. What a pity that when people finally looked at something like UNIX, it turned out to not be UNIX at all, but someone cooked up in a schoolkid's garage. History repeating itself? Microsoft began life in Bill Gates' garage didn't it? A perfect example of a product sold on hype alone, even though technically superior solutions already existed (but had no hype behind them). History repeating itself? Can I say "Microsoft"? ;-) Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0506-0, 08/02/2005 Tested on: 10/02/2005 13:44:59 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: start of daemons
[EMAIL PROTECTED] wrote: Hello, I have installed apache and spamd from source and would like for them to start on bootup. How do I do that? (there are no .sh scripts for them in /usr/local/etc/rc.d) For apache add ''apache_enable="YES"'' to /etc/rc.conf There should be apache.sh in /usr/local/etc/rc.d - the port installs it. How did you install apache? Should be a similar method for spamd. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0506-0, 08/02/2005 Tested on: 09/02/2005 19:37:36 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please don't change Beastie to another crap logo such as NetBSD!!!
Louis LeBlanc wrote: On 02/09/05 04:32 PM, Charles-André Landemaine sat at the `puter and typed: This will sign the death of FreeBSD. How could they believe such crap?! Who said beastie is evil?! This is totally non-sense, it's a logo, it's not the CD cover of a heavy-metal release...! I think the reasons are the same as NetBSD. Do extremist Republicans threaten BSD distros? The word "daemon" in greek means "server" (the person, not the hardware). This is neither good nor bad, if it has to be either one, then it's good. Uh, not to be rude, but what the hell are you talking about? I don't remember anyone talking about changing the logo. http://logo-contest.freebsd.org/announce.txt Read it and weep. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0506-0, 08/02/2005 Tested on: 09/02/2005 19:11:10 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please don't change Beastie to another crap logo such as NetBSD!!!
Charles-André Landemaine wrote: This will sign the death of FreeBSD. How could they believe such crap?! Who said beastie is evil?! This is totally non-sense, it's a logo, it's not the CD cover of a heavy-metal release...! I think the reasons are the same as NetBSD. Do extremist Republicans threaten BSD distros? The word "daemon" in greek means "server" (the person, not the hardware). This is neither good nor bad, if it has to be either one, then it's good. Oh please, wake me up, it's a nightmare!!! See the thread "The FreeBSD Project is announcing a public competition for the new logo design. " in -advocacy - I've already replied with my views on the subject, along the same lines as your comments. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0506-0, 08/02/2005 Tested on: 09/02/2005 18:48:20 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cracked out floppy install
daniel wrote: On February 7, 2005 10:40 pm, Chris Hill wrote: On Mon, 7 Feb 2005, daniel wrote: > i've been trying to install freebsd-5.3RELEASE on this old computer on > and off for days now. i downloaded the floppies, watched the thing > boot and each and every time, it'll get to the little beastie prompt > where it counts down and is *supposed* to run sysinst but instead, it > just reboots! That's just peculiar. Maybe you need more RAM? Couldn't hurt, anyway. The 16M you cite below seems a bit meager. well the handbook says freebsd5 has a minimum requirement of 8mb, so 16 should be fine. but even if it weren't, you'd think there'd be some form of useful error message instead of just rebooting. it just makes no sense. Interestingly, the Installation Notes for 4.11-R, http://www.freebsd.org/releases/4.11R/installation-i386.html state, in section 1.2 Hardware Requirements, "The sysinstall(8) installation program requires 16MB of RAM" Does sysinstall in 5.3 _really_ need half the RAM that 4.11 requires? I find that hard to believe. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0506-0, 08/02/2005 Tested on: 09/02/2005 14:51:07 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what are patches ?
Tom Huppi wrote: Almost totally unrelated, but this reminds me of a very pleasant conversation I had with on of the early FreeBSD developers. He mentioned that the FreeBSD project grew out of what was known as 'the unofficial 386BSD patch kit' or something like that name. He said that it got to the point where the patch set was indeed larger than the distribution of the OS of interest (which was, I believe, the first port of BSD Unix to the x86 architecture.) I didn't get the sense that he was joking about that. He wasn't. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-1, 02/02/2005 Tested on: 05/02/2005 03:02:12 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Within X, how can I see console messages?
Nathan Kinkade wrote: On Fri, Feb 04, 2005 at 06:13:01PM +0100, Benjamin Walkenhorst wrote: Steven Friedrich wrote: >I know I can Control-Alt-F1 to go back to the console, but is there a way >to see these messages in an xterm or something? > > xconsole When xdm starts, xconsole gets started, too, on my machine, I can't remember doing anything to get this behaviour, though. Kind regards, Benjamin Keep in mind that /dev/console may only be readable by root. You might have to change permissions on the device, or perhaps launch xconsole as the root user. There may be other ways to get around this. I just throw this into the mix as a problem that you may encounter. You uncomment this line in /etc/fbtab #/dev/ttyv0 0600/dev/console and start an xterm with '-c' IIRC Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-1, 02/02/2005 Tested on: 04/02/2005 18:13:55 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting FreeBSD-5.3 from NTLDR
Rakhesh Sasidharan wrote: On Wed, 2 Feb 2005 01:48:47 -0800, Loren M. Lang <[EMAIL PROTECTED]> wrote: Unless BootPart specifically know about how the freebsd boot loaders work and how to reconize them, I doubt that it's modifying those parameters. Now the last 66 bytes of the MBR stores the partition table of the hard drive, it's possible that BootPart might try to modify that as it's not part of the boot loader, but the boot loader uses that information. Possible. I even checked BootPart's site and forums, but didn't find any mention that it is "FreeBSD-aware" etc. All they talk about is Windows and DOS and Linux. I had a good mind to sign up on the forums and ask the author -- but wasn't too keen on signing up and so left it. I know it modifies the bootsector some way, coz when I boot using the extracted file I get a message (and a second's pause) saying that this bootsector was extracted using BootPart blah blah ... I don't know about BootPart, but the FreeBSD boot manager replaces the MBR on _both_ disks and allows booting from either. The limitation is in NTLDR because it's M$ so is only designed for booting M$ OSes and the BOOTSECT file method is designed for booting DOS and non-NT class Windows which could only boot from the first partition on the first drive anyway therefore there is no need for NTLDR to support booting from the second, third, etc. disk using a BOOTSECT file. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-1, 02/02/2005 Tested on: 02/02/2005 16:05:07 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [lorenl@alzatex.com: Re: Mounting a samba share on boot?]
Ruben de Groot wrote: On Mon, Jan 31, 2005 at 05:47:53AM -0800, Loren M. Lang typed: On Mon, Jan 31, 2005 at 12:38:53PM +, Mark Ovens wrote: > Loren M. Lang wrote: > >replacing MYWORKGROUP, SERVER, USER, secret as neccessary. Make sure > >nsmb.conf is only readable by root. Add the following line to fstab: > > > >//[EMAIL PROTECTED]/share /mnt/share smbfs rw 0 0 > > > > PMJI, but do you know if it's possible to handle a share name containing > a space when mounting smb filesystems using fstab? > > I tried > > "//[EMAIL PROTECTED]/Drive C" > '//[EMAIL PROTECTED]/Drive C' > //[EMAIL PROTECTED]/Drive\ C > > None of these worked. I know that using spaces in filenames is a Bad > Idea, but this is Windows we're talking about here ;-) A random guess might be to try: //[EMAIL PROTECTED]/Driver%20C %20 refers to the ascii character with hex value 20 which is space. It's what webservers use for getting around spaces, samba might too.` I'd be really curious to see if this works. The following seems to work for me: [EMAIL PROTECTED]:/root> mount_smbfs //odo/"Temp Dir" /mnt Password: [EMAIL PROTECTED]:/root> mount | grep smbfs //[EMAIL PROTECTED]/TEMP DIR on /mnt (smbfs) [EMAIL PROTECTED]:/root> Yes, that WFM too. The problem is if you try to add that as an entry in /etc/fstab as it cannot handle the space. I had a quick look in fstab.c and there appears to be no handling of escaped characters, which is understandable I suppose since the first field would normally be something /dev/da0s1a Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 02/02/2005 01:30:28 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache+SSL, which port?
Mark Ovens wrote: That's fixed it, thanks :-) httpd.conf from the previous version I had installed doesn't have index.php in the DirectoryIndex directive, but it does have Duh! brain fade; that should say: ...does have index.php in the DirectoryIndex directive, and it also has Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 01/02/2005 17:48:40 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache+SSL, which port?
Adi Pircalabu wrote: On Tue, 01 Feb 2005 17:12:02 + Mark Ovens <[EMAIL PROTECTED]> wrote: Should have mentioned that I tried adding that but it just caused the contents of index.php to be displayed in the browser rather than the directory listing. If I understand this correctly, your .php page was not parsed, but displayed. You should also need a directive like this: AddType application/x-httpd-php .php From what I see, /usr/ports/lang/php4/pkg-message.mod says how to complete the integration of php module. That's fixed it, thanks :-) httpd.conf from the previous version I had installed doesn't have index.php in the DirectoryIndex directive, but it does have AddType application/x-httpd-php3 .php3 AddType application/x-httpd-php3-source .php3s AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps DirectoryIndex index.php index.php3 index.html DirectoryIndex index.php3 index.html DirectoryIndex index.php index.html DirectoryIndex index.html but I'm 99% certain I didn't have to add thosehmmm, the previous version was installed from a package, the current version from the ports; maybe that's why? Thanks again for your help. Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 01/02/2005 17:41:00 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache+SSL, which port?
Adi Pircalabu wrote: On Tue, 01 Feb 2005 16:54:19 + Mark Ovens <[EMAIL PROTECTED]> wrote: Anyway, it's all working now, except that when I try to connect to squirrelmail in a browser I just get a directory listing of /usr/local/www/squirrelmail. Hi, Maybe you forgot listing index.php in DirectoryIndex directive? Should have mentioned that I tried adding that but it just caused the contents of index.php to be displayed in the browser rather than the directory listing. Also, I didn't have index.php in the DirectoryIndex directive in the previous version of apache and it worked correctly then. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 01/02/2005 17:12:03 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache+SSL, which port?
Tim Erlin wrote: Andrew L. Gould wrote: Not necessarily. I've heard lots of complaints about PHP and Apache2 not "playing nice". (Does anyone have any updates on this situation?) I've been running apache2 with squirrelmail for a while. The biggest problems were performance issues. Squirrelmail was very slow pulling mail from the disk. Not sure that apache13 would help there. I finally installed apache13-ssl after trying to portupgrade -o to apache2 and trashing everything. Anyway, it's all working now, except that when I try to connect to squirrelmail in a browser I just get a directory listing of /usr/local/www/squirrelmail. I've reinstalled squirrelmail and run the configure script. Alias in httpsd.conf is copied from the old httpd.conf: Alias /squirrelmail/ "/usr/local/www/squirrelmail/" Options Indexes FollowSymlinks MultiViews AllowOverride None Order allow,deny Allow from all Which worked before. Any idea what I've missed? Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 01/02/2005 16:54:20 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache+SSL, which port?
Charles Swiger wrote: On Jan 31, 2005, at 1:22 PM, albi wrote: Mark Ovens wrote: I want to install apache with SSL but there are two ports, www/apache13-modssl and www/apache13-ssl What is the difference, and which is the best to install? i think the apache13-ssl has SSL build in, the other uses a module for SSL Apache-1.3 does not have SSL built-in. The port www/apache13-ssl is using "Ben Laurie's SSL", whereas mod_ssl is by Ralf Engelschall. See: http://www.apache-ssl.org/#Credits http://www.modssl.org/ It is just for use on my home LAN but I want to run squirrelmail to access my mail from remote machines. there's also apache2 which, afaik, builds with SSL by default Yes, apache2 has support for SSL built-in, and will enable SSL if the system it is built on has it available (which is true for all recent FreeBSD versions). So apache2 is the way to go then? Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 31/01/2005 18:39:35 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache+SSL, which port?
I want to install apache with SSL but there are two ports, www/apache13-modssl and www/apache13-ssl What is the difference, and which is the best to install? It is just for use on my home LAN but I want to run squirrelmail to access my mail from remote machines. TIA Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 31/01/2005 18:14:43 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting FreeBSD-5.3 from NTLDR
Rakhesh Sasidharan wrote: On Mon, 31 Jan 2005 11:33:59 +, Mark Ovens <[EMAIL PROTECTED]> wrote: I rewrote that section of the FAQ years ago (around FreeBSD 3.1!!) because the previous wording was unclear and I did _exactly_ what Rakhesh has done :-( Ah! Glad to see I am not the only one. :))) Felt really goofy when I read that this goofup that I did was clearly documented in the handbook! Thankfully I had backups (I keep doing this sort of messups every now and then :p) and so I wasn't too freaked out when I discovered my entire partition table and boot sectors erased -- but it wasn't a nice sight either. The thought of re-installing everything, plus restoring from backups, yada yada yada ... thankfully I managed to find a program for recovering the partitions. Hehe! I did it the hard way; I manually recreated the partition table - 3 partitions! In fact.[roots around in drawer]..yes, still got the printout of the spreadsheet I used to calculated the start and end CHS values - don't know why, the disk was replaced ages ago :-) Caveat: Things have no doubt changed since then so it may now be possible to add FreeBSD to the NTLDR menu with FreeBSD on a different disk, but I've never investigated it as I am happy with the solution I use. Actually, I know that I can very well use GRUB or BootEasy to do this job. But I dunno, its this curiousity that has gotten over me -- to explore NTLDR a bit more, and to see why I can't boot into FreeBSD with it. If I had gotten a definitive answer that its *not* possible, then I would have given up -- but as it is, nobody has said its not possible, and added to that I can see if I extract the bootsectors using a program like BootPart then things work, and so I am highly curious why I can't get things working with conventional tools and methods like "dd" etc! Guess if I get no answers, I'll just start using BootEasy, but I'm curious why things dont work nevertheless. :)) And I'm all the more curious what changes BootPart makes to the extracted bootsectors to make them work with NTLDR. IRCC, boot0 is the MBR and boot1 is the boot sector (of the FreeBSD partition (slice)) and they only ontain info about the local disk, i.e. _relative_ info in effect, so if FreeBSD is on your second disk and you copy boot1 to C:\BOOTSECT.BSD and add an entry for it in BOOT.INI then NTLDR has know way of knowing that it refers to the second HDD and so can't boot because the info doesn't match the layout of the first HDD. Remember boot0 and boot1 are restricted to 512bytes - one sector. That is the reason as far as remember. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 31/01/2005 16:06:39 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [lorenl@alzatex.com: Re: Mounting a samba share on boot?]
Loren M. Lang wrote: On Mon, Jan 31, 2005 at 12:38:53PM +, Mark Ovens wrote: Loren M. Lang wrote: >replacing MYWORKGROUP, SERVER, USER, secret as neccessary. Make sure >nsmb.conf is only readable by root. Add the following line to fstab: > >//[EMAIL PROTECTED]/share /mnt/share smbfs rw 0 0 > PMJI, but do you know if it's possible to handle a share name containing a space when mounting smb filesystems using fstab? I tried "//[EMAIL PROTECTED]/Drive C" '//[EMAIL PROTECTED]/Drive C' //[EMAIL PROTECTED]/Drive\ C None of these worked. I know that using spaces in filenames is a Bad Idea, but this is Windows we're talking about here ;-) A random guess might be to try: //[EMAIL PROTECTED]/Driver%20C %20 refers to the ascii character with hex value 20 which is space. It's what webservers use for getting around spaces, samba might too.` I'd be really curious to see if this works. Nope: //[EMAIL PROTECTED]/Drive%20C/smb2smbfs rw,noauto 0 0 postbag# mount /smb2 Password: smbfs: unable to open connection: syserr = No such file or directory Using \x20 produced the same result. The other three that I mentioned all produce: postbag# mount /smb2 fstab: /etc/fstab:17: Inappropriate file type or format fstab: /etc/fstab:17: Inappropriate file type or format mount: /smb2: unknown special file or file system Which suggests that it's interpreting the space as a delimiter and ignoring the escapes. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0505-0, 31/01/2005 Tested on: 31/01/2005 15:41:20 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port update problem - deleted all the ports
Mark Ovens wrote: Also are you sure that you want your ports tree in /var/db? /usr would be more usual. *default base=/usr Duh! Ignore that, /var/db is fine (although I use /usr/sup) I was confusing base and prefix. Sorry, 'bout that. Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0504-4, 28/01/2005 Tested on: 31/01/2005 13:47:53 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port update problem - deleted all the ports
saravanan ganapathy wrote: Hai , I am using 5.3 release and included tag=RELENG_5_3 to my ports-supfile and when I tried to update ports using " cvsup -g -L 2 /root/ports-supfile", it deleted almost all the ports and finally it says ... ... ... Delete ports/x11-wm/yawm/Makefile Delete ports/x11-wm/yawm/distinfo Delete ports/x11-wm/yawm/pkg-descr Shutting down connection to server Finished successfully My ports-supfile looks as *default host=cvsup10.us.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5_3 *default delete use-rel-suffix ports-all What is the problem? The ports tree doesn't have tags so you should edit the above to *default release=cvs tag=. Note the '.'!! Also are you sure that you want your ports tree in /var/db? /usr would be more usual. *default base=/usr HTH Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0504-4, 28/01/2005 Tested on: 31/01/2005 13:40:22 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [lorenl@alzatex.com: Re: Mounting a samba share on boot?]
Loren M. Lang wrote: replacing MYWORKGROUP, SERVER, USER, secret as neccessary. Make sure nsmb.conf is only readable by root. Add the following line to fstab: //[EMAIL PROTECTED]/share /mnt/share smbfs rw 0 0 PMJI, but do you know if it's possible to handle a share name containing a space when mounting smb filesystems using fstab? I tried "//[EMAIL PROTECTED]/Drive C" '//[EMAIL PROTECTED]/Drive C' //[EMAIL PROTECTED]/Drive\ C None of these worked. I know that using spaces in filenames is a Bad Idea, but this is Windows we're talking about here ;-) If it is not possible then perhaps a PR is needed to get this addressed? In my case I renamed the share on the Windows box (which broke a few shortcuts) but this may not always be possible - in a corporate environment for example. Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0504-4, 28/01/2005 Tested on: 31/01/2005 12:38:54 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting FreeBSD-5.3 from NTLDR
Loren M. Lang wrote: On Mon, Jan 31, 2005 at 02:16:25PM +0400, Rakhesh Sasidharan wrote: Thanks for that link! I had read that part of the handbook a long time ago, and that's how my ideas of boot0 and boot1 and etc etc had gotten clear. Glad to see it once again -- in the context of my question! :)) So what I understand now is -- copying boot0 over to c:\bootsect.bsd will *not* work. Which explains why my MBR got messed up when I tried booting FreeBSD this way. :( But I'm still confused. How do I install boot0 using sysinstall? As far as I remm, sysinstall gives three options -- (a) leave the MBR untouched, (b) put a standard MBR, and (c) install BootEasy. My understanding is that option (b) copies boot0 to the MBR, and this that is what I had chosen while installing FreeBSD. How does one copy boot0 to a file using sysinstall?? I think option b is actually /boot/mbr and BootEasy refers to /boot/boot0. They are two different boot loaders, mbr being a very simple one with no configuration. I think fdisk -B is used to install /boot/mbr to the mbr of a harddisk and boot0cfg is used to install BootEasy. I rewrote that section of the FAQ years ago (around FreeBSD 3.1!!) because the previous wording was unclear and I did _exactly_ what Rakhesh has done :-( At that time it was not possible to add FreeBSD to the NTLDR menu if FreeBSD was on a _different disk_ so you had to either use the FreeBSD boot menu or put the FreeBSD root partition on the same disk as NT (which usually required a BIOS that could boot beyond the first 1024 cylinders) or use the FreeBSD boot manager (which used /boot/boot0). This is what I have done ever since. As I only have a single user set up in XP it doesn't show the NTLDR menu so you don't have to go through two boot menus, just the FreeBSD F1/F5 choice. Caveat: Things have no doubt changed since then so it may now be possible to add FreeBSD to the NTLDR menu with FreeBSD on a different disk, but I've never investigated it as I am happy with the solution I use. HTH Regards, Mark On Mon, 31 Jan 2005 08:44:23 +, Mark Ovens <[EMAIL PROTECTED]> wrote: > Rakhesh Sasidharan wrote: > >> No, boot0 is just a normal file that is 512 bytes long. There is > >> nothing special about it. In it is a bootloader program that can be > >> used to boot FreeBSD, and if you run it during boot, it will read the > >> partition table and look for all OSes. I think it will modify the > >> partition table, though, marking the last OS you booted into, but that's > >> the program running doing that, the file itself is harmless. > > > > Ok. I must have used some other command then, which resulted in my > > first disk MBR getting over-written ... strange. :-/ > > > > By the way, does the fact that NTLDR is on my first disk, while > > FreeBSD (and hence its MBR boot0) is on my second disk complicate > > matters? I mean, you mention boot0 will modify my partition table to > > reflect which OS was booted last -- will it by any chance modify the > > partition table on the first disk and hence mess it? > > > > > > Yes and yes, > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER > > Regards, > > Mark > > --- > avast! Antivirus: Outbound message clean. > Virus Database (VPS): 0504-4, 28/01/2005 > Tested on: 31/01/2005 08:44:24 > avast! - copyright (c) 2000-2004 ALWIL Software. > http://www.avast.com > > -- -- Rakhesh [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0504-4, 28/01/2005 Tested on: 31/01/2005 11:34:00 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting FreeBSD-5.3 from NTLDR
Rakhesh Sasidharan wrote: No, boot0 is just a normal file that is 512 bytes long. There is nothing special about it. In it is a bootloader program that can be used to boot FreeBSD, and if you run it during boot, it will read the partition table and look for all OSes. I think it will modify the partition table, though, marking the last OS you booted into, but that's the program running doing that, the file itself is harmless. Ok. I must have used some other command then, which resulted in my first disk MBR getting over-written ... strange. :-/ By the way, does the fact that NTLDR is on my first disk, while FreeBSD (and hence its MBR boot0) is on my second disk complicate matters? I mean, you mention boot0 will modify my partition table to reflect which OS was booted last -- will it by any chance modify the partition table on the first disk and hence mess it? Yes and yes, http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0504-4, 28/01/2005 Tested on: 31/01/2005 08:44:24 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Daily run output message
On 22/01/2005 19:01 Paul Schmehl stood on a soap-box and preached to the unwashed masses: --On Saturday, January 22, 2005 5:46 PM + Mark Ovens <[EMAIL PROTECTED]> wrote: I see this in the daily run output on a 4.10-R box: Removing stale entries from sendmail host status cache: purgestat: no mapping in /etc/mail/mailer.conf What is the mapping that is missing? The machine is running postfix, not sendmail BTW. Read the pkg-message file in the Postfix port. Also, you will want to disable some Sendmail-specific daily maintenance routines in your /etc/periodic.conf file: daily_clean_hoststat_enable="NO" daily_status_mail_rejects_enable="NO" daily_status_include_submit_mailq="NO" daily_submit_queuerun="NO" I'd read the port message and put those lines in /etc/periodic.conf but I had to create the file but mis-typed periodic.comf Duh! :-[ Thanks for all the replies. Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0503-2, 21/01/2005 Tested on: 22/01/2005 20:08:55 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Daily run output message
On 22/01/2005 17:58 Jorn Argelo stood on a soap-box and preached to the unwashed masses: On Sat, 22 Jan 2005 17:46:32 +, Mark Ovens wrote I see this in the daily run output on a 4.10-R box: Removing stale entries from sendmail host status cache: purgestat: no mapping in /etc/mail/mailer.conf What is the mapping that is missing? The machine is running postfix, not sendmail BTW. Mine looks like this, and I'm also running Postfix. # # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail # sendmail/usr/local/sbin/sendmail send-mail /usr/local/sbin/sendmail mailq /usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail Perhaps you're missing something? No, same as yours. Thanks for the suggestion though. I take it that you don't see the same message? Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0503-2, 21/01/2005 Tested on: 22/01/2005 18:07:41 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Daily run output message
I see this in the daily run output on a 4.10-R box: Removing stale entries from sendmail host status cache: purgestat: no mapping in /etc/mail/mailer.conf What is the mapping that is missing? The machine is running postfix, not sendmail BTW. TIA Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0503-2, 21/01/2005 Tested on: 22/01/2005 17:46:33 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: chmod: Operation not permitted
Gardner Bell wrote:
After rebuilding world last night I can no longer chmod some system
binaries that I don't need. When attemtping to do so I get a permission denied.
[EMAIL PROTECTED] chmod 000 /bin/rcp
chmod: /bin/rcp: Operation not permitted.
[EMAIL PROTECTED] chmod 000 /bin/rlogin
chmod: /bin/rlogin: Operation not permitted
The only binaries this seems to be happening with are the ones used
for remote operations. Ie: rcp, rlogin, rsh, opieinfo, etc. I
All those have schg flag set on my RELENG_5 system (also, rlogin and rcp
are in /usr/bin, not /bin).
/home/mark{83}# ls -lo /bin/r* /usr/bin/r*
-r-sr-xr-x 1 root wheel schg 18388 13 Jan 09:50 /bin/rcp
-r-xr-xr-x 1 root wheel - 3668 13 Jan 09:50 /bin/realpath
-r-xr-xr-x 2 root wheel - 48832 13 Jan 09:50 /bin/red
-r-xr-xr-x 1 root wheel - 55748 13 Jan 09:51 /usr/bin/rlog
-r-sr-xr-x 1 root wheel schg 10804 13 Jan 09:52 /usr/bin/rlogin
-r-xr-xr-x 1 root wheel - 82296 13 Jan 09:52 /usr/bin/rpcgen
-r-xr-xr-x 1 root wheel - 30888 13 Jan 09:52 /usr/bin/rpcinfo
-r-xr-xr-x 1 root wheel - 9964 13 Jan 09:52 /usr/bin/rs
-r-sr-xr-x 1 root wheel schg 8800 13 Jan 09:52 /usr/bin/rsh
-r-xr-xr-x 1 root wheel - 6464 13 Jan 09:52 /usr/bin/rup
-r-xr-xr-x 1 root wheel - 7260 13 Jan 09:52 /usr/bin/ruptime
-r-xr-xr-x 1 root wheel - 6776 13 Jan 09:52 /usr/bin/rusers
-r-xr-xr-x 1 root wheel - 6500 13 Jan 09:52 /usr/bin/rwall
-r-xr-xr-x 1 root wheel - 6256 13 Jan 09:52 /usr/bin/rwho
/home/mark{84}#
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tab to Auto-Complete + ....
Warren wrote:
On Tue, 18 Jan 2005 10:03 pm, Daniel Bye wrote:
On Tue, Jan 18, 2005 at 11:52:16AM +, Mark Ovens wrote:
> It does support command history and editing, though not auto-complete.
>
> ''set -E'' or ''set -V'' at the prompt (or put either - they are
> mutually exclusive - in ~/.profile) will enable command history with
> Emacs or vi style command editing respectively.
Live and learn! Thanks for that.
Dan
I changed the shell type using: chsh -s /bin/csh
re-logged in as it prompts and still no go with anything .. so i just simply
installed putty and used it to connect to each machine.
Thanks for all the help.
Put some or all of these in ~/.cshrc
# size of history buffer
set history = 100
# enable auto-complete
set filec
# stop it beeping
set nobeep
# ignore *.o files for file completion
set fignore = '.o'
# '%' prompt for normal user; '#' for root/su
set promptchars="%#"
# /path/to/cwd{cmd number}%
set prompt="%/{!}%# "
# List matches when autocompleting
set autolist=true
# enable spelling correction
set correct=all
# Useful key bindins
bindkey "^W" backward-delete-word
bindkey -k up history-search-backward
bindkey -k down history-search-forward
bindkey "^?" backward-delete-char
bindkey "\e[3~" delete-char
bindkey "\e[1~" beginning-of-line
bindkey "\e[4~" end-of-line
See csh(1) for loads of additional options!
HTH
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tab to Auto-Complete + ....
Daniel Bye wrote: On Tue, Jan 18, 2005 at 08:30:52PM +1000, Warren wrote: What is need for me to add/do in order for the pressing of Tab to autcomplete a name to work? It works fine in root .. also when i press the up or down arrow keys it dosent bring up the previous command issued ... im using FreeBSD5.3-STABLE What shell are you using? I guess you haven't installed any shells from ports yet, and are using the system default, /bin/sh, which doesn't support autocomplete or command history. It does support command history and editing, though not auto-complete. ''set -E'' or ''set -V'' at the prompt (or put either - they are mutually exclusive - in ~/.profile) will enable command history with Emacs or vi style command editing respectively. Regards, Mark The root shell is csh, which does have such things. So, either set your user's shell to be /bin/tcsh, or install one of the several shells in ports. HTH Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ctrl+Shift not working in KDE
KDE 3.3.2 Any key combination that includes Ctrl+Shift doesn't work, e.g. Ctrl+Shift+C to MArk All Read in Thunderbird or Ctrl+Shift+D to Uncomment a line in KWrite. It is the combination that is ignored; Ctrl+ and Shift+ work as expected. I've looked at all the keyboard stuff in Regional 7 Accessibility but can't find anything. Anyone got any ideas? TIA Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LAN Browsing not working in KDE 3.3
LAN Browsing in Konqueror (Services tab in Navigation panel) was working fine in the previous version I was running (3.2.x IIRC) using the lisa daemon. In 3.3.0 however, when I select LAN Browsing I get an error "Protocol not supported: lan". ISTR reading somewhere that lisa had been replaced by something else for providing this functionality but I can't find it now. lisa definitely isn't installed on my system. I can't find any info on docs.kde.org on how to set up LAN Browsing but the lisa documentation is still listed under kdenetwork in 3.3. Samba is running and I can browse my FreeBSD box in Network Neighbourhood on Windows boxes. Can someone point me in the right direction please? TIA Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Mon November 29 2004 12:54, Mark Ovens wrote: > # make buildkernel && installkernel Duh! typo. That should read # make buildkernel && make installkernel Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Sun November 28 2004 21:03, Trey Sizemore wrote: > Mark Ovens wrote: > >On Sun November 28 2004 19:35, Trey Sizemore wrote: > >>Mark Ovens wrote: > >>>On Sun November 28 2004 18:28, Trey Sizemore wrote: > >>>>Hmmm...not sure why mine's not working then. Is your mouse the > >>>> wireless version? Mine says Microsoft Wireless Mouse 2.0 (it's kind > >>>> of a light purple color ). > >>> > >>>Yes, same as mine. > >>> > >>>You did change ''moused_port'' in /etc/rc.conf to /dev/psm0 when you > >>>connected it to the PS/2 port, didn't you? > >> > >>I'll have to check...I'm doing a portupgrade right now, so I'll have to > >>check when that finishes. > > > >I've just applied the patch in PR kern/70607 and it works just fine - > > although I've not tested the tilt wheel because, as I said, I don't use > > it so I'm not sure how to set it up in FreeBSD. > > When you say it works fine, do you mean you've attached the mouse via > USB? Yes :-) > I'm new to FreeBSD, so how do I apply this patch to get the mouse > to work? > The patch needs a slight mod - removal of a field in a struct - from the one posted (see comments about the 'dt' field in the PR). I can e-mail you a modified version - is your re-mail address valid? Save the patch to a file, e.g. /tmp/pr70607_patch then, as root: # cd /usr/src # patch -Clp0 < /tmp/pr70607_patch [that's a lower case L and a zero] The -C just simulates what would happen without actually changing anything - just to check that the patch will apply cleanly. Make sure all the hunks succeed, you should see this: Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- sys/dev/usb/usbhid.h.orig Mon Sep 20 00:59:48 2004 |+++ sys/dev/usb/usbhid.h Mon Sep 20 02:14:40 2004 -- Patching file sys/dev/usb/usbhid.h using Plan A... Hunk #1 succeeded at 123. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |--- sys/dev/usb/ums.c.orig Mon Nov 29 12:37:13 2004 |+++ sys/dev/usb/ums.c Sun Nov 28 20:12:30 2004 -- Patching file sys/dev/usb/ums.c using Plan A... Hunk #1 succeeded at 104. Hunk #2 succeeded at 114. Hunk #3 succeeded at 140. Hunk #4 succeeded at 269. Hunk #5 succeeded at 277. Hunk #6 succeeded at 290. Hunk #7 succeeded at 408. Hunk #8 succeeded at 425. Hunk #9 succeeded at 466. Hunk #10 succeeded at 484. Hunk #11 succeeded at 503. Hunk #12 succeeded at 550. Hunk #13 succeeded at 807. done If they all succeed then do it for real: # patch -lp0 < /tmp/pr70607_patch [again a lower case L and a zero] The rebuild and install your kernel # make buildkernel && installkernel edit /etc/rc.conf to change moused_port to /dev/ums0, shutdown, connect the mouse to the USB port, restart and enjoy: Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Mon November 29 2004 02:32, Robert Huff wrote: > Trey Sizemore writes: > > OK...making some progress now. I have these entries (except I'm > > using /dev/psm0 for the time being) and now the mouse is jumping > > to the upper left corner of the screen and flickering menus > > mysteriously. Moving the mouse only causes the flickering. I > > used another PS/2 connected mouse (wired this time -> MS Optical > > USB) and it gave the exact same behavior). > > This sounds very like a known problem some time ago involving > the ACPI code, I don't remember what the outcome was, but you > should check the archives of the questions@ and current@ lists for > more info. > ISTR that this can happen if the protocol is set incorrectly Trey, do you have moused_type set to "auto" in rc.conf? Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Sun November 28 2004 22:22, Trey Sizemore wrote: > Mark Ovens wrote: > >On Sun November 28 2004 18:28, Trey Sizemore wrote: > >>Hmmm...not sure why mine's not working then. Is your mouse the wireless > >>version? Mine says Microsoft Wireless Mouse 2.0 (it's kind of a light > >>purple color ). > > > >Yes, same as mine. > > > >You did change ''moused_port'' in /etc/rc.conf to /dev/psm0 when you > > connected it to the PS/2 port, didn't you? > > Actually, the only entries I have in /etc/rc.conf are: > ifconfig_vr0="DHCP" > linux_enable="YES" > usbd_enable="YES" > > What does this line look like? Here's what I have: moused_enable="yes" # Run the mouse daemon. moused_type="auto" # See man page for rc.conf(5) for available settings. moused_port="/dev/ums0" # Set to your mouse port. moused_flags="" # Any additional flags to moused. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Sun November 28 2004 19:35, Trey Sizemore wrote: > Mark Ovens wrote: > >On Sun November 28 2004 18:28, Trey Sizemore wrote: > >>Hmmm...not sure why mine's not working then. Is your mouse the wireless > >>version? Mine says Microsoft Wireless Mouse 2.0 (it's kind of a light > >>purple color ). > > > >Yes, same as mine. > > > >You did change ''moused_port'' in /etc/rc.conf to /dev/psm0 when you > > connected it to the PS/2 port, didn't you? > > I'll have to check...I'm doing a portupgrade right now, so I'll have to > check when that finishes. > I've just applied the patch in PR kern/70607 and it works just fine - although I've not tested the tilt wheel because, as I said, I don't use it so I'm not sure how to set it up in FreeBSD. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Sun November 28 2004 18:28, Trey Sizemore wrote: > > Hmmm...not sure why mine's not working then. Is your mouse the wireless > version? Mine says Microsoft Wireless Mouse 2.0 (it's kind of a light > purple color ). > Yes, same as mine. You did change ''moused_port'' in /etc/rc.conf to /dev/psm0 when you connected it to the PS/2 port, didn't you? Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
On Sat November 27 2004 22:26, Trey Sizemore wrote: > Mark Ovens wrote: > > Trey Sizemore wrote: > >> I've just installed FreeBSD 5.3 on my desktop machine (P4 2.8GHz with > >> 512MB RAM) and cannot get my mouse pointer to move in KDE. It is a > >> Microsoft Wireless Optical 2.0 mouse (USB) and I have the following > >> section in my /etc/X11/xorg.conf file: > >> > >> Driver "mouse" > >> Option "Protocol" "Auto" > >> Option "Device" "/dev/sysmouse" > >> Option "Buttons" "7" > >> Option "ZAxisMapping" "4 5" > >> > >> I have installed FreeBSD from the disc 1 ISO file and installed > >> everything by default. I have not done a kernel recomple at this point. > >> > >> Is this an issue with my xorg.conf file or a USB issue that requires > >> a kernel recompile? I did not see anything helpful in the Using X11 > >> in the manual. > > > > They don't work :-( I have to run mine on PS/2 via an adaptor. There > > is a patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/70607 to > > fix this. I tried the first version of the patch; the mouse worked but > > there were other problems. There have been several modifications done > > to the patch since then that I haven't tried. > > I've just tried mine by using the PS/2 adaptor and it's not working here > either. The light on the 'base station' doesn't stay on. Is your > xorg.conf different than mine? > Slightly: Identifier "Mouse1" Driver "mouse" Option "Protocol""sysmouse" Option "Device" "/dev/sysmouse" Option"Buttons" "5" Option"ZAxisMapping" "4 5" I don't use the tiltwheel - it annoys me - hence Buttons set to 5 Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what does "rm //" delete?
Oliver Fuchs wrote: Hi, I had a directory which contained the following: ls showed me simple this: "?" with 0 bytes ls -axl showed me nothing So I tried to delete the directory but could not succeed with "rm -R" because the "directory is not empty". I changed to the directory and tried to delete everything inside with "rm *" but also did not succeed. It seemed that the file had no name. So than I did a mistake and wanted to delete the file with no name with the operation: rm -R // This was a big mistake which I noticed soon enough (some files in /bin were deleted). I could repair the damage but what I want to know is what exactly is rm -R // deleting. It seems that it is deleting everything? It is, you're recursively deleting / - multiple '/' are treated as one; try cd //usr//bin To delete the rogue file try rm -i * in the directory the file is in, answering 'n' for all other files. If that fails, try copying everything you need in the directory it is in to somewhere else then recursively deleting the directory rm -rf /path/to/dir/with/rogue/file HTH Mark Thanx in advance Oliver --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0448-1, 26/11/2004 Tested on: 28/11/2004 12:58:15 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse support
Trey Sizemore wrote: I've just installed FreeBSD 5.3 on my desktop machine (P4 2.8GHz with 512MB RAM) and cannot get my mouse pointer to move in KDE. It is a Microsoft Wireless Optical 2.0 mouse (USB) and I have the following section in my /etc/X11/xorg.conf file: Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/sysmouse" Option "Buttons" "7" Option "ZAxisMapping" "4 5" I have installed FreeBSD from the disc 1 ISO file and installed everything by default. I have not done a kernel recomple at this point. Is this an issue with my xorg.conf file or a USB issue that requires a kernel recompile? I did not see anything helpful in the Using X11 in the manual. They don't work :-( I have to run mine on PS/2 via an adaptor. There is a patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/70607 to fix this. I tried the first version of the patch; the mouse worked but there were other problems. There have been several modifications done to the patch since then that I haven't tried. HTH Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0448-1, 26/11/2004 Tested on: 27/11/2004 21:45:44 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Postfix/fetchmail problem
I've set up postfix, fetchmail, and courier-imap on a FreeBSD box (4.10) and got it working - for one account. When I added a second account it goes wrong; all mail gets sent to the user that fetchmail is running as. My .fetchmailrc contains poll pop.myisp.com protocol POP3 user mark with pass "xx" is user mark here user maureen with pass "yy" is user maureen here which matches one of the examples in fetchmail(1), which also says, "It's possible to specify more than one user per server (this is only likely to be useful when running fetchmail in daemon mode as root)." so I'm running fetchmail in daemon mode as root and all mail from both accounts gets sent to root. This suggests that my postfix config is wrong but I can't figure out why. Surely the ''is user here'' in ~/.fetchmailrc should pass mail off to postfix as ? Can someone point me in the right direction please? Thanks. Regards, Mark --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0447-0, 15/11/2004 Tested on: 19/11/2004 09:27:20 avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCSI Shock Advice !
Graham Bentley wrote: Hi All, When I was about to install the new drive which was sitting on top of the system box I tilted the box to move the disc access LED lead onto the SCSI card. My nice new SCSI disc slid off and hit the MDF worktop - Agh ! I reckon the drop height was about 14" ~ do you think this would have exceed the G Force limit and invalidated my warranty / casued any damage ? The reason for asking is that I never really got up close and personal with a SCSI disc before and it does make some odd noises? Currently there is a frequent one every so often - its two freequencies that last about a second or two each. What model is it? A 36LZX or 73LZX? If so they do make an awful screeching noise. When I got mine (off eBay) I thought the bearings were on their way out, but searching Hitachi's website (Hitachi now own IBM's HD division) threw up this http://www.hitachigst.com/hdd/support/qcheck.htm#a4 Mine makes this noise a lot more frequently than once per minute that they state and it's extremely annoying. My Seagate OTOH is almost silent except when it's doing some serious thrashing. HTH Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5: KDE upgrade Catch-22
Michael Nottebrock wrote: On Friday 17 September 2004 21:14, Mark Ovens wrote: Hmmm, if I delete XFree86-libraries then X won't run, and without libXinerama.so.1 KDE won't run :-/ Anyone have a solution to this conundrum please? Yes: Update all of XFree86 to the latest version in ports (4.4). XFree86-libraries does contain libXinerama.so.1. The real conundrum is how you ended up with a system like this. I can make a few guesses: You upgraded KDE via packages Running ''portupgrade -PPRa'' I guess. I had been having problems caused by the compiler changes and read in this list, or -questions, an answer to a question about the same problem where the advice was to u/g all your ports via packages (or uninstall them all and rebuild from ports). portupgrade(1) skipped XFree86. - that KDE has been built against xorg (which is the default X distribution for 5.3 and contains libXinerama.so.1, while XFree86-4.3 only contains a libXinerama.a). Are you saying the KDE packages are built against xorg? I guess that explains all the dependencies on xorg that I kept having to delete using ''pkgdb -F''. Is that the real reason KDE won't run? Would switching to xorg be the best solution in the long run then (now is the time for me to do it if it is)? I guess that would mean rebuilding all my X apps that weren't installed from packages. Thanks for the quick and detailed reply. Regards, Mark Or maybe you compiled KDE yourself - against Xorg or XFree86-4.4 and then downgraded to XFree86-4.3? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quick and simple ssh(1) question
Erik Trulsson wrote: On Mon, Sep 13, 2004 at 10:15:47PM +0100, Mark Ovens wrote: Is it correct that you can't ssh(1) between two machines on the same LAN (using NAT) _via the Internet?_ What do you mean 'via the Internet'? If both machines are on the same LAN any connections between them will never go outside the LAN, and thus never go near the Internet. Strange question I know, but I need to be able to access one of my machines, postie, remotely. I've got sshd(8) running and can ssh(1) to it from a local machine using it's local hostname. However, since I only have a single 'net connection here I tried to test connecting remotely by ssh(1)'ing to my router's 'net-facing hostname but I get ssh: connect to host port 22: Connection refused Port 22 is forwarded to postie on the router. Most likely your router is configured to only forward connections that come from the outside. As I said, it was only a test and I was hoping that by using the router's external hostname it would "simulate" an external connection, obviously it doesn't. Does it work to access 'postie' via ssh from some machine that is *actually* on the outside? If it does, then it is the configuration of your router which is not doing what you want it to. I don't have access to one until I get to work tomorrow which was why I was trying to simulate it - whilst I have the target machine in front of me. Thanks for the reply. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quick and simple ssh(1) question
Chuck Swiger wrote: Mark Ovens wrote: Is it correct that you can't ssh(1) between two machines on the same LAN (using NAT) _via the Internet?_ Strange question I know, but I need to be able to access one of my machines, postie, remotely. I've got sshd(8) running and can ssh(1) to it from a local machine using it's local hostname. However, since I only have a single 'net connection here I tried to test connecting remotely by ssh(1)'ing to my router's 'net-facing hostname but I get ssh: connect to host port 22: Connection refused Port 22 is forwarded to postie on the router. Given time and sufficient determination, you ought to be able to make this work, but it's a real pain-- [snip detailed info] I think that answers my question - it won't work the way I'm trying it. As I said, this was just an attempt to test connecting from outside; guess I'll have to wait until I get to work tomorrow and try it from there (which is where I really want to connect from), it's just that if it doesn't work I'll have to wait until I get home to change things - a bit of a pain. Thanks for the answer. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Quick and simple ssh(1) question
Is it correct that you can't ssh(1) between two machines on the same LAN (using NAT) _via the Internet?_ Strange question I know, but I need to be able to access one of my machines, postie, remotely. I've got sshd(8) running and can ssh(1) to it from a local machine using it's local hostname. However, since I only have a single 'net connection here I tried to test connecting remotely by ssh(1)'ing to my router's 'net-facing hostname but I get ssh: connect to host port 22: Connection refused Port 22 is forwarded to postie on the router. It kind of make sense to me that this won't work but I'd like to confirm that this is the case and it's not my sshd(8) configuration that's wrong. Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Epson C66 doesn't work with Epson drivers (print/pips-sc65_66s port)
I originally posted this in -ports but despite some suggestions it is still a problem. Hopefully someone here may be able to shed some light? I'm (now) running FreeBSD postie 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I got my Epson C66 Photo up and running using CUPS, ESP Ghostscript, and the gimp-print drivers (using C64 since C66 isn't listed explicitly). It all works and I exported it through Samba and printed successfully from a Windows box :-) Then I found that the Epson KOWA drivers were in the ports - print/pips-sc65_66s - so installed them as they are better drivers, changed the configuration in CUPS as per readme-sc65_66s-cups but the printer wouldn't work. I deleted the printer and re-added it from scratch but still it won't work. When I click Print Test Page in CUPS the printer head "shuffles" which shows there is some communication with the printer but it just shows "Processing..." for a while then the job appears under Completed Jobs with a status of "aborted". I've set CUPS to log at debug2 level but that doesn't show anything useful (to me anyway): D [06/Sep/2004:20:08:51 +0100] [Job 32] cups->ppd = 0x83f5400 D [06/Sep/2004:20:08:51 +0100] [Job 32] cups->ppd->flip_duplex = 0 D [06/Sep/2004:20:08:51 +0100] [Job 32] width = 827, height = 1039 D [06/Sep/2004:20:08:51 +0100] [Job 32] PageSize = [ 612 792 ], HWResolution = [ 100 100 ] D [06/Sep/2004:20:08:51 +0100] [Job 32] HWMargins = [ 8.400 35.400 8.400 8.400 ] D [06/Sep/2004:20:08:51 +0100] [Job 32] matrix = [ 1.389 0.000 0.000 -1.389 -11.667 1088.333 ] d [06/Sep/2004:20:08:51 +0100] PID 689 exited with no errors. d [06/Sep/2004:20:08:51 +0100] PID 690 exited with no errors. D [06/Sep/2004:20:08:51 +0100] UpdateJob: job 32, file 0 is complete. d [06/Sep/2004:20:08:51 +0100] UpdateJob: Removing fd 9 from InputSet... D [06/Sep/2004:20:08:51 +0100] CancelJob: id = 32 D [06/Sep/2004:20:08:51 +0100] StopJob: id = 32, force = 0 D [06/Sep/2004:20:08:51 +0100] StopJob: printer state is 3 d [06/Sep/2004:20:08:51 +0100] StopJob: Freeing status buffer... d [06/Sep/2004:20:08:51 +0100] SaveJob: Closing file 7... d [06/Sep/2004:20:08:51 +0100] SaveJob: Closing file 7... The ekpstm program (Status Monitor) shows a "Communication Error" and the pips-sc65_66s program shows "Cannot communicate with a printer" on the Utility tab. Can anyone offer any help/advice on this please? BTW, the port appears to be missing a build dependency for autoconf253 - my build stopped part way through as it couldn't find /usr/local/bin/autoconf253. Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Package version problem with portupgrade(1)
kstewart wrote: His PACKAGESITE environment variable is set to a wrong location. I think that he needs to set it using something like setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/All Thanks Kent, but it didn't work. Setting it made it search in ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/All. I eventually found that it's PKG_SITES that needs setting (and you don't include 'All') after trawling through pkgtools.conf. Unfortunately it's not documented in the portupgrade manpage. Anyway, I've got it all working now - thanks for the push in the right direction, and thanks Phil too for the input. Regards, Mark or his favorite mirror, as all one line. and then run portupgrade -PPa. It defaults to the 4.9 release packages and they never change. I have only used PACKAGESITE once and that was to update KDE. The sites were so busy that my computer would build it almost as fast as I could download it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Package version problem with portupgrade(1)
kstewart wrote: Well, png is up to png-1.2.5_8 and if you did a recent cvsup and recreated your INDEXs, that is what you should be seeing. OK, portupgrade(1) _is_ looking for 1.2.5_8 but it is trying to get it from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.9-release/All where the version of png is 1.2.5_2, so how to resolve the conflict? Seems to me that portupgrade(1) needs to be getting the packages from packages-4-stable/All instead? Staying behind is a good way to end up with a security black hole :). Precisely. A cvsup of ports-all and a portsdb -uU should be a good way to keep your system current. Will that change where portupgrade(1) tries to get the packages from? Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Package version problem with portupgrade(1)
FreeBSD postie 4.9-RELEASE FreeBSD 4.9-RELEASE #1: Sun Mar 21 19:46:39 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/POSTIE i386 I'm trying to upgrade cups-base on this system, using packages (as the machine doesn't really have enough grunt for building ports), with portupgrade, but it is trying to get the wrong version: postie# portupgrade -RPPv cups-base ---> Session started at: Wed, 01 Sep 2004 17:27:46 +0100 ---> Checking the availability of the latest package of 'graphics/png' ---> Fetching the package(s) for 'png-1.2.5_8' (graphics/png) ---> Fetching png-1.2.5_8 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/ ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/png-1.2.5_8.tgz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1.2.5_8.tgz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1.2.5_8.tgz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1.2.5_8.tgz The actual file in ports/i386/packages-4.9-release/All/ is png-1.2.5_2 I'm guessing that this is caused because my ports tree was cvsup'd and so is more up to date than the packages built for 4.9-RELEASE. Thing is, how to deal with it? I could set $PKG_SITES in pkgtools.conf to use packages-4.9-release/Latest but the files there have no version number at all, e.g. png.tgz What's the best solution here - before I go and screw my system ;-) Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Logging router errors using syslog
Martin Hasenbein wrote: On 26 Aug 2004 (15:30:52) [1093527052], Mark Ovens wrote: Hi Mark, Thanks, yes, I was. I've changed it and restarted without ''-s'' but it still doesn't appear to be logging anything - I configured the router to log everything so the file should grow quite quickly. Do you have any other idea(s)? are you running some kind of firewall, like ipfilter or ipfw? No, I'm not. If so, did you open Port 514/UDP? What happens, if you change this line in /etc/syslog.conf local2 /var/log/router/zyxel to local2.*/var/log/router/zyxel and restart? It is actually local2.*, it was a typo in my original post, sorry. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Logging router errors using syslog
Martin Hasenbein wrote: On 26 Aug 2004 (13:55:35) [1093521335], Mark Ovens wrote: Hi Mark, The router has been set up to log to the local2 facility and I've added these lines to the end of /etc/syslog.conf: !* +P650R-31 local2 /var/log/router/zyxel Can anyuone suggest why this is not working? how did you start syslogd? If it was started from /etc/rc.conf without modifying the flags for syslogd, it won't work. The default-flag for syslogd is syslogd_flags="-s" From the man-page: -s Operate in secure mode. Do not log messages from remote machines. If specified twice, no network socket will be opened at all, which also disables logging to remote machines. You have to disable this option and restart syslogd. Thanks, yes, I was. I've changed it and restarted without ''-s'' but it still doesn't appear to be logging anything - I configured the router to log everything so the file should grow quite quickly. Do you have any other idea(s)? Regards, Mark Ciao, -Martin. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Logging router errors using syslog
FreeBSD 4.9-RELEASE My ADSL router/modem, Zyxel P650R-31, supports error logging to a remote *nix host using syslog but I can't get it to work. The router has been set up to log to the local2 facility and I've added these lines to the end of /etc/syslog.conf: !* +P650R-31 local2 /var/log/router/zyxel and created the log file and restarted syslogd (kill -HUP) - the machine has also since been rebooted. There is an entry in /etc/hosts for the router. I originally made both router/ and router/zyxel 644 root/wheel but have also tried changing the perms to 777 and changing the group to network. Can anyuone suggest why this is not working? Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Top posting solution
Chris wrote: Paul Schmehl wrote: --On Tuesday, August 10, 2004 05:45:58 PM -0400 JJB <[EMAIL PROTECTED]> wrote: Over the years I have seen many posts on this list where Unix hard liners complain about people posting their replies to the top of the email messages on this list. The fact of life is all the Unix mail clients adhere to the Unix email format of posting the reply to the bottom of the email while indenting with a quote character. Not true. Pine doesn't. Mulberry doesn't. I don't believe Evolution does. I'm pretty sure the Firefox solution (don't recall the name) doesn't. Thunderbird gives you the option And of course OE/Outlook users could just learn to hit Ctrl-End before they start typing :-) Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: backspace and delete keys behavior
Ion-Mihai Tetcu wrote: On Fri, 30 Jul 2004 14:30:59 +0100 Mark Ovens <[EMAIL PROTECTED]> wrote: Peter Ryan wrote: > I've got the same thing on the 2 machines i am experimenting > with. I am new and thought it was a standard feature :) > > I also defined a standard US 101 keyboard. > > Makes me think there is a setting or choice at installation that > deals with this, rather than having to patch something. > Add keysym Delete = 0x04 to ~/.xmodmaprc and add xmodmap ~/.xmodmaprc to ~/.xinitrc To implement this in a running X session type this in an xterm xmodmap -e "keysym Delete = 0x04" Actually, this is probably a better solution for the OP as it is global whereas my previous suggestion is xterm specific. The only problem is that if you keep the delete key pressed to long it exits the terminal. At least when xmodmap typed under kde's konsole; it acts this way both in for konsole and xterm. Only if the cursor is in the first character position after the prompt of course. Not sure what the solution is since Ctrl-D is delete char to the right of the cursor and EOT, which exits the shell. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: backspace and delete keys behavior
Peter Ryan wrote: I've got the same thing on the 2 machines i am experimenting with. I am new and thought it was a standard feature :) I also defined a standard US 101 keyboard. Makes me think there is a setting or choice at installation that deals with this, rather than having to patch something. Add keysym Delete = 0x04 to ~/.xmodmaprc and add xmodmap ~/.xmodmaprc to ~/.xinitrc To implement this in a running X session type this in an xterm xmodmap -e "keysym Delete = 0x04" Actually, this is probably a better solution for the OP as it is global whereas my previous suggestion is xterm specific. HTH Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: backspace and delete keys behavior
Mariano Guadagnini wrote: Hi guys, I am new to Freebsd (after years of linux) and, althought system installation and configuration was quite seamlessly, I've an issue with the delete key of my keyboard (101 keys us layout): In xterm, the backspace key works ok, but when I press del, it prints the "~" character, instead of deleting . I have read it has something to do with keyboard layout config, but I couldn't find out how to fix it. So, any ideas? Thanks, (and forgive my poor english) Add this to ~/.Xdefaults XTerm*vt100.translations: #override \n\ Delete: string(0x04) \n which maps Ctrl-D to the DEL key, then run % xrdb < ~/.Xdefaults to implement it (in the current X session). Note that this won't change the behaviour in the current xterm, but will in any new ones you open. HTH Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KDE vs Gnome
Chris wrote: Sandbox Video Productions wrote: IF i install both gnome & kde. how do i choose which one i want to start up. It seem that it only starts the GUI that was installed last. __ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Depends. 1. Are you using KDM? If so, you make your choice at the login menu. 2. If not above, edit .xinitrc and comment out one IE: exec startkde #gnome-session #exec startxfce4 #exec startfluxbox In the above example, KDE starts after entering startx #exec startkde gnome-session #exec startxfce4 #exec startfluxbox In the above example, Gnome starts ater entering startx Even easier, if you want to avoid editing ~/.xinitrc everytime you want to change between the two, you could add a case statement in ~/.xinitrc to handle args to startx(1): case "$1" in -k) exec startkde ;; -g) gnome-session ;; *) exec startkde ;; esac The '*' case being the default if there are no args. For this to work you have to hack /usr/X11R6/bin/startx and change the line defaultclient=/usr/X11R6/bin/xterm to defaultclient="" because if you specify any (client) args then startx(1) just starts X and an xterm - no window manager. The last time I used multiple WMs was in XFree86 3.x and I'm certain I didn't have to hack startx so it looks like the behaviour has changed, or it maybe that it was just so long ago that I've forgotten :-) See startx(1) and xinit(1) for details of the default startup behaviour. HTH Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: Re: Random Freeze]
Paul Mather wrote: Mark, When you do, look for PREEMPTION. That should speed up the search. :-) Yes, I searched the mailing lsts and found it, deleted #define PREEMPTION from sys/i38i6/include/param.h, rebuilt my kernel and the machine has been up for 13 hours now :-) Only thing is the screensaver hangs after ~5 minutes (that had me worried the first time it happened), but that's not really important. Seriously, though, -CURRENT has been going through some major instability the last fortnight or so. One thesis is that the pre-emption code added has either introduced or uncovered some obscure bugs. The net effect has been random freezes---most often reported is when under load or doing something (e.g., rendering a complicated page) using Mozilla, or when using XMMS. The two apps I probably use the most! One suggestion, until the culprit has been found, is to rebuild without PREEMPTION (undef it in /usr/src/sys/i386/include/param.h). That has certainly stopped the freezes in my case. Me too. If you're running -CURRENT, it is advisable to subscribe to the freebsd-current mailing list---if nothing else but to be apprised of ongoing problems like this, or to get a heads-up about possible future instability caused by major repository/functionality changes. (For example, today there was a heads-up about the GCC 3.4 import being done [which seems to have broken things temporarily].) I have done now. I'm only running -CURRENT because this is a dual CPU box and when I built it back in December what I was readin on the lists suggested that 5-STABLE was only a few months away and, since SMP support in 5.x is superior to 4.x, I figured upgrading 5-CURRENT->5-STABLE would be easier than 4-STABLE->%-STABLE. As soon as we get a 5-STABLE that's what I'll run. Thanks for your input. Regards, Mark Cheers, Paul. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(SOLVED) Console in X
Mark Ovens wrote: If I put this in ~/.xinitrc exec startkde > /dev/console 2>&1 to redirect messages to the console in order to read them in xconsole, X starts and immediately exits with the error: /home/mark/.xinitrc: cannot create /dev/console: permission denied I've uncommented this line in /etc/fbtab: /dev/ttyv0 0600/dev/console Duh! Seems you have to reboot for the changes to /etc/fbtab to take effect. It's been that long since I set it up that I'd forgotten. Sorry for the noise folks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Console in X
If I put this in ~/.xinitrc
exec startkde > /dev/console 2>&1
to redirect messages to the console in order to read them in xconsole, X
starts and immediately exits with the error:
/home/mark/.xinitrc: cannot create /dev/console: permission denied
I've uncommented this line in /etc/fbtab:
/dev/ttyv0 0600/dev/console
and dev/console exists:
/home/mark{12}% ls -l /dev/con*
crw--- 1 root wheel0, 0 28 Jul 16:55 /dev/console
crw--- 1 root wheel 234, 255 28 Jul 11:29 /dev/consolectl
This used to work in 4.x and XFree86 4.1 but now I'm running -CURRENT
and XFree86 4.3.0.
Has something changed, or have I missed something?
Thanks.
Regards,
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random Freeze
Karol Kwiatkowski wrote: Mark Ovens wrote: I'm seeing the same problem on my dual Athlon box. The freezes are totally random AFAICT, sometimes when the machine is just idling. I've not used any CPU-specific make options but may try setting some to see if it makes a difference. One thing though, I only have cpu I686_CPU set, not I486_CPU and I586_CPU as well, maybe that could be a problem? AFAIK, that's a proper setting for Athlons. What I recommend is you shouldn't play with make options before setting up a stable system (sorry if that's too obvious). I'm running -CURRENT and the build I did on 8 April didn't have this problem but it started with the next build I did a couple of weeks ago. I've cvsup'd and rebuilt a couple of times since, the last on 25 July, but the problem persists. I don't have much experience with CURRENT (and with SMP) but if you didn't change the config files it looks like something in the code (this is possible in CURRENT, right?). Only thing I can think of is reading freebsd-current and searching the archives. Not much from me, sorry. I've noticed something; it only seems to freeze when I'm in X. I had the machine up for over 30 hours at the command line yesterday whilst I upgraded some ports, including KDE (which was why I did it from the command line). I rebooted it when I'd finished. I've never had it stay up anywhere near that long since the 8 April build. Some conflict between XFree86 (4.3.0) and -CURRENT/5.2.1-RELEASE? Also, my machine dual-boots with XP and that stays up for days at a time so, in my case at least, I doubt it's hardware, plus I've run memtest86 and it was OK. Thanks for the input. I'm going to subscribe to freebsd-current and search the archives. Regards, Mark Regards, Karol ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random Freeze
Karol Kwiatkowski wrote: Joseph Peterson wrote: Unfortunately that is not the solution to my problem, I've run memtest86 on my laptop several times and found no problems... any other thoughts? =) -joe Just a thought: Have you build your world and / or kernel from source? If that's the case double check processor-specific make options like CPUTYPE, CFLAGS, COPTFLAGS, etc. (they can be used from command line and from /etc/make.conf) Good luck! Karol I'm seeing the same problem on my dual Athlon box. The freezes are totally random AFAICT, sometimes when the machine is just idling. I've not used any CPU-specific make options but may try setting some to see if it makes a difference. One thing though, I only have cpu I686_CPU set, not I486_CPU and I586_CPU as well, maybe that could be a problem? I'm running -CURRENT and the build I did on 8 April didn't have this problem but it started with the next build I did a couple of weeks ago. I've cvsup'd and rebuilt a couple of times since, the last on 25 July, but the problem persists. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade(1) kde fails
Kent Stewart wrote: Kdelibs has the new files and when you try to update kdebase later, it messes up the install. That is why you have to delete kdebase first. If the files had been moved from kdelibs into kdebase, it wouldn't have mattered. Ah, I see. OK, I'll give it a spin. Thanks for the help Kent. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3COM NIC Card???
Hakim Singhji wrote: Hello All, I recently purchased a pair of 3Com 3C905CTXM EtherLink XL PCI TX Network adapter PCI 100 Mbps NIC Cards and I wanted to know if they are compatible with FreeBSD 4.10 (stable). Could someone please give me some feedback on this thanks. Yes, http://www.freebsd.org/releases/4.10R/hardware-i386.html#ETHERNET Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions regarding /etc/make.conf
Henrik W Lund wrote: Greetings! No, nothing you put into make.conf will affect already installed software. This file is for setting build-time options, and as such will only affect subsequent software builds. And yes, rebuilding and reinstalling a package you already have qualifies as a "subsequent build". As for valid CPUTYPE values, have you checked out the manpage? man make.conf I'm pretty sure I've seen it in there somewhere. /usr/share/examples/etc/make.conf is where it is described. HTH Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade(1) kde fails
Kent Stewart wrote:
Hi Mark,
On a 2nd read, I thought I was kind of sharp.
No problem. I saw the message:
===> kdelibs-3.2.3_1 conflicts with installed package(s):
kdebase-3.1.2
They install files into the same place.
Please remove them first with pkg_delete(1).
*** Error code 1
but it seemed misleading because I thought that portupgrade(1)
pkg_delete-ed the old version (after first backing up the files) -
obviously not.
What you have is a similar
problem to the old problem with XFree86-server and -libraries. You
update -libraries, which contain the new files, and then you delete
them when you update -server. Then, nothing would update because files
were missing.
There were a number of comments on -questions or -ports when this first
happened.
Yes, I'd searched the mailing lists (for KDE problems, not XFree86) but
didn't find anything that seemd relevant, although after your reply some
of them make sense now.
You might get by just deleting kdebase.
Delete kde-libs surely?
Is this a limitation/shortcoming/bug of portupgrade(1)? Is the whole
point of it ot that it handles, often complex, dependencies for you?
Thanks for the reply.
Regards,
Mark
Kent
On Monday 26 July 2004 05:40 am, Kent Stewart wrote:
On Monday 26 July 2004 05:20 am, Mark Ovens wrote:
> I'm trying to upgrade kde (the meta-port), 3.1.2->3.2.3_1 using
> portupgrade(1) but it fails trying to install kdelibs.
>
> Can anyone shed any light on what's wrong?
>
> FreeBSD redshift 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Sun Jul 25
> 19:19:46 BST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REDSHIFT
> i386
>
> /home/mark{106}# pkg_info | grep kde
>
> kde-3.1.2 The "meta-port" for KDE
> kdebase-3.1.2 This package provides the basic applications
> for the KDE sy
> kdegames-3.1.2 Games for the KDE integrated X11 desktop
> kdegraphics-3.1.2 Graphics utilities for the KDE3 integrated X11
> desktop kdelibs-3.1.2 This is the base set of libraries
> needed by KDE programs kdemultimedia-3.1.2 Multimedia utilities for
> the KDE integrated X11 desktop kdenetwork-3.1.2Network-related
> programs and modules for KDE kdesdk-3.1.4KDE Software
> Development Kit kdeutils-3.1.2 Utilities for the KDE
> integrated X11 desktop xmms-kde-3.0.0 Integrates XMMS into the
> KDE3 Panel
> /home/mark{107}#
>
> /home/mark{107}# portupgrade -Rv kde-3.1.2
>
> [snip successful build of dependencies and kdelibs]
>
> pkg_delete: unable to completely remove directory
> '/usr/local/share/servicetypes'
>
> [snip lots of similar lines]
>
> pkg_delete: unable to completely remove directory
> '/usr/local/include/kate' rmdir: /usr/local/include/arts: Directory
> not empty
> pkg_delete: couldn't entirely delete package (perhaps the packing
> list is incorrectly specified?)
> [Updating the pkgdb in /var/db/pkg ... - 148
> packages found (-1 +0) (...) done]
> ---> Uninstallation of kdelibs-3.1.2 ended at: Mon, 26 Jul 2004
> 13:12:26 +0100 (consumed 00:00:28)
> ---> Installation of x11/kdelibs3 started at: Mon, 26 Jul 2004
> 13:12:26 +0100
> ---> Installing the new version via the port
> ===> Installing for kdelibs-3.2.3_1
>
> ===> kdelibs-3.2.3_1 conflicts with installed package(s):
>kdebase-3.1.2
>
>They install files into the same place.
>Please remove them first with pkg_delete(1).
> *** Error code 1
It told you what to do right here. You can't directly upgrade to the
next level because of the file shift.
Kent
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade(1) kde fails
I'm trying to upgrade kde (the meta-port), 3.1.2->3.2.3_1 using
portupgrade(1) but it fails trying to install kdelibs.
Can anyone shed any light on what's wrong?
FreeBSD redshift 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Sun Jul 25 19:19:46
BST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REDSHIFT i386
/home/mark{106}# pkg_info | grep kde
kde-3.1.2 The "meta-port" for KDE
kdebase-3.1.2 This package provides the basic applications for the
KDE sy
kdegames-3.1.2 Games for the KDE integrated X11 desktop
kdegraphics-3.1.2 Graphics utilities for the KDE3 integrated X11 desktop
kdelibs-3.1.2 This is the base set of libraries needed by KDE programs
kdemultimedia-3.1.2 Multimedia utilities for the KDE integrated X11 desktop
kdenetwork-3.1.2Network-related programs and modules for KDE
kdesdk-3.1.4KDE Software Development Kit
kdeutils-3.1.2 Utilities for the KDE integrated X11 desktop
xmms-kde-3.0.0 Integrates XMMS into the KDE3 Panel
/home/mark{107}#
/home/mark{107}# portupgrade -Rv kde-3.1.2
[snip successful build of dependencies and kdelibs]
pkg_delete: unable to completely remove directory
'/usr/local/share/servicetypes'
[snip lots of similar lines]
pkg_delete: unable to completely remove directory '/usr/local/include/kate'
rmdir: /usr/local/include/arts: Directory not empty
pkg_delete: couldn't entirely delete package (perhaps the packing list is
incorrectly specified?)
[Updating the pkgdb in /var/db/pkg ... - 148
packages found (-1 +0) (...) done]
---> Uninstallation of kdelibs-3.1.2 ended at: Mon, 26 Jul 2004
13:12:26 +0100 (consumed 00:00:28)
---> Installation of x11/kdelibs3 started at: Mon, 26 Jul 2004 13:12:26
+0100
---> Installing the new version via the port
===> Installing for kdelibs-3.2.3_1
===> kdelibs-3.2.3_1 conflicts with installed package(s):
kdebase-3.1.2
They install files into the same place.
Please remove them first with pkg_delete(1).
*** Error code 1
Stop in /usr/ports/x11/kdelibs3.
*** Error code 1
Stop in /usr/ports/x11/kdelibs3.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade681.35 make reinstall
---> Updating dependency info
---> Modifying /var/db/pkg/digikam-0.5.1/+CONTENTS
---> Modifying /var/db/pkg/kde-3.1.2/+CONTENTS
---> Modifying /var/db/pkg/kdebase-3.1.2/+CONTENTS
---> Modifying /var/db/pkg/kdegames-3.1.2/+CONTENTS
---> Modifying /var/db/pkg/kdegraphics-3.1.2/+CONTENTS
egrep: /var/db/pkg/kdelibs-3.1.2/+CONTENTS: No such file or directory
---> Modifying /var/db/pkg/kdemultimedia-3.1.2/+CONTENTS
---> Modifying /var/db/pkg/kdenetwork-3.1.2/+CONTENTS
---> Modifying /var/db/pkg/kdesdk-3.1.4/+CONTENTS
---> Modifying /var/db/pkg/kdeutils-3.1.2/+CONTENTS
---> Modifying /var/db/pkg/koffice-1.2.1_1,1/+CONTENTS
---> Modifying /var/db/pkg/xmms-kde-3.0.0/+CONTENTS
---> Restoring the old version
** Fix the installation problem and try again.
---> Installation of x11/kdelibs3 ended at: Mon, 26 Jul 2004 13:12:58
+0100 (consumed 00:00:32)
---> Upgrade of x11/kdelibs3 ended at: Mon, 26 Jul 2004 13:12:58 +0100
(consumed 00:52:53)
[Updating the pkgdb in /var/db/pkg ... - 149
packages found (-0 +1) . done]
---> Skipping 'editors/koffice-kde3' (koffice-1.2.1_1,1) because a
requisite package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to
force)
---> Skipping 'games/kdegames3' (kdegames-3.1.2) because a requisite
package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to force)
---> Skipping 'net/kdenetwork3' (kdenetwork-3.1.2) because a requisite
package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to force)
---> Skipping 'graphics/kdegraphics3' (kdegraphics-3.1.2) because a
requisite package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to
force)
---> Skipping 'x11/kdebase3' (kdebase-3.1.2) because a requisite
package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to force)
---> Skipping 'misc/kdeutils3' (kdeutils-3.1.2) because a requisite
package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to force)
---> Skipping 'multimedia/kdemultimedia3' (kdemultimedia-3.1.2) because
a requisite package 'kdelibs-3.1.2' (x11/kdelibs3) failed (specify -k to
force)
---> Skipping 'x11/kde3' (kde-3.1.2) because a requisite package
'kdeutils-3.1.2' (misc/kdeutils3) failed (specify -k to force)
---> Listing the results (+:done / -:ignored / *:skipped / !:failed)
- graphics/png (png-1.2.5_6)
- lang/python (python-2.3.4_1)
- textproc/expat2 (expat-1.95.7)
- converters/libiconv (libiconv-1.9.2)
- devel/gettext (gettext-0.13.1_1)
- devel/libgnugetopt (libgnugetopt-1.2)
- lang/perl5 (perl-5.6.1_15)
- devel/imake-4 (imake-4.3.0_2)
- audio/libogg (libogg-1.1,3)
- audio/libvorbis (libvorbis-1.0.1,3)
- devel/pcre (pcre-4.5)
- graphics/jpeg (jpeg-6b_3)
- print/freetype2 (freetype2-2.1.7_3)
- graphics/tiff (tiff-3.6.1_1)
- graphics/lcms (lcms-
Re: mount_msdosfs anomaly
Malcolm Kay wrote: On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote: Here is the output of fdisk when ran from FBSD: frankie# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=155061 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=155061 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 11 (0x0b),(DOS or Windows 95 with 32 bit FAT) start 63, size 10249407 (5004 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 637/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 10249470, size 40949685 (19994 Meg), flag 80 (active) beg: cyl 638/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 51199155, size 5863725 (2863 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: sysid 5 (0x05),(Extended DOS) start 57062880, size 99233505 (48453 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 frankie# As you can see, I still have 98SE on partition 1 and partition 3 shows as fat32. Slackware was re-installed and is working on P-8 with linux-swap 0n P-9. Is this weird that I cannot mount ad0s3? Does someone out there know the significance of "sysid 12" versus "sysid 11"? According to the fdisk output sysid 11 is DOS or Windows 95 with 32 bit FAT and sysid 12 is DOS or Windows 95 with 32 bit FAT (LBA) The difference is LBA although I thought that if you needed to use LBA then the _whole disk_ was LBA but since slice 3 is visible in Win98 I guess it's correct (probably just a case of FreeBSD reporting _accurately_ what's on the disk). It's a few years since I messed with FAT so I may not have remembered this correctly, but originally DOS could only support a single _active_ primary partition (which is why extended was invented). Somewhere in the Win9x line that changed; the OS still had to be on the first primary partition but other primary partitions were visible in the OS. The OP says that Win98 can see /dev/ados3 and write to it but, if you look at the fdisk output only slice 1 is flagged 'active'. The last time I had a machine with multiple OSes (Win98, W2K, and FreeBSD) I used BootMagic that comes with PartitionMagic which had a config option to choose which partitions/slices each OS could see. With FreeBSD the default setting hid _all_ the FAT & NTFS slices (I got the same problem you have) so I had to change the settings. The first one or two bytes in each entry in the partition table determine whether the partition is 'active' (i.e. the one that is booted from) but also whether the partition is visible or hidden. When you choose an OS from BM's menu it edits the PT "on the fly" (which will set the BIOS boot sector anit-virus alarm off if it's enabled) and then continues the boot process. IIRC Win9x can see adso3 (in this case) by simply ignoring the visible flag, i.e. a kludge, in typical MS fashion. As to how to resolve it, if you are really brave you can edit the partition table flags directly but the changes may not hold (I have a feeling that Win98 may "fix" them next time you boot Win98) or install a boot manager like BM that allows you to set the visibility. If you run this # dd if=/dev/ad0 of=/tmp/foo bs=512 count=1 # hd /tmp/foo > /tmp/foo.hd and post the last 6 lines of foo.hd it will help identify which byte is set wrong; I've a load of notes here about partition tables so I'll dig them out. HTH Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntfs mount
J. W. Ballantine wrote: The last four lines are not even close: fa eb 5c 53 42 4d 33 2e 37 2e 31 00 02 01 01 00 |..\SBM3.7.1.| 0010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 |[EMAIL PROTECTED]| 0020 00 00 00 00 00 00 29 00 00 00 00 53 4d 41 52 54 |..)SMART| 0030 20 42 54 4d 47 52 46 41 54 31 32 20 20 20 eb 1f | BTMGRFAT12 ..| 0040 53 42 4d 4c 01 03 2c 01 00 00 00 00 00 00 00 00 |SBML..,.| OK, SBM has replaced the MBR (to be expected) but I think we need to see what it looks like booted to Windows. As per my other post I suspect that the first 2 partitions will then appear as type 7. I've sent you a ZIP containing a copy of DSKPROBE.EXE. Regards, Mark 01b0 4d 4b 20 42 61 64 21 0d 0a 00 00 00 00 00 00 01 |MK Bad!.| 01c0 01 00 2d fe ff ff 3f 00 00 00 39 b1 d4 01 00 ff |..-...?...9.| 01d0 ff ff 2d fe ff ff 78 b1 d4 01 3b 8b 38 01 80 ff |..-...x...;.8...| 01e0 ff ff a5 fe ff ff b3 3c 0d 03 fc 47 bb 00 00 ff |...<...G| 01f0 ff ff a5 fe ff ff af 84 c8 03 51 ce df 00 55 aa |..Q...U.| 0200 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntfs mount
Bart Silverstrim wrote: On May 7, 2004, at 1:40 PM, Mark Ovens wrote: J. W. Ballantine wrote: It a Dell, but given the configuration, i do not believe it came pre-installed from the factory. I would have thought that a Dell would have had *an* OS pre-installed. Not always. I am running FBSD 4.9 on a couple Dell 2650's ordered just for the purpose of installing FreeBSD on them for some of our server use...you can specify *no operating system* and they ship you the system and rails with nothing but the hard drives configured for RAID on the PERC controller. No fuss, no muss :-) That's good to know :-) Does it only apply to servers, or can you get desktop machines /sans/ OS? Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" . ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntfs mount
Mark Ovens wrote: Not come across Smart Boot Manager but I wonder if it creates a small partition to run from; the OS/2 Boot Manager, which was also shipped with older versions of Partition Magic, did but, like "recovery" partitions it didn't get a drive letter. Ah! I've just thought of something. My old machine had Boot Magic installed - the boot manager that came with later versions of Partition Magic and didn't need a dedicated partition. One of it's features let you choose which partitions each OS could see. I never looked into _how_ it did it but I'm now wondering if it worked by setting the partition type id flag to 45 (unknown) in the partition table; I do remember that I had to disable the BIOS boot sector anti-virus feature as it went off everytime I booted. Now, it may be that this is how Smart Boot Manager works. You could confirm it by viewing the MBR when booted into Windows, you can get a copy of dd(1) and hd(1) for windows from cygwin.com or you can use DSKPROBE.EXE which is in the NT4 Resource Kit (if you can find a copy - e-mail me if you can't) and see if the partition type for the first two partitions is now set to 7 (NTFS), and maybe the FreeBSD partitions are now 45? Regards, Parish ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntfs mount
J. W. Ballantine wrote: The full fdisk output is: *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=4865 heads=255 sectors/track=63 (16065 blks/cyl) [snip] I take it that the partition sizees reported are correct? It a Dell, but given the configuration, i do not believe it came pre-installed from the factory. I would have thought that a Dell would have had *an* OS pre-installed. Only the first partition is bootable, I had two to separate the "standard" install from the non-standard (ie the programs I use). The multi-os boot manager is Smart Boot Manager, but that doesn't change any partiton ids. Not come across Smart Boot Manager but I wonder if it creates a small partition to run from; the OS/2 Boot Manager, which was also shipped with older versions of Partition Magic, did but, like "recovery" partitions it didn't get a drive letter. Try running: # dd if=/dev/ad0 of=/tmp/foo bs=512 count=1 # hd /tmp/foo > /tmp/foo.hd This copies the first sector of the disk to a file and hd(1) does a hexdump of the binary file. Open /tmp/foo.hd in an editor and look at the last 4 lines, they should look similar to: 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01 01c0 01 00 a5 7f ff 10 3f 00 00 00 41 97 60 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa 0200 (there will be the ASCII to the right of each line but I've not included it to prevent wrapping in the e-mail) The partition type is the third hex number in the last 4 lines; the example above is 'a5' (FreeBSD) and the disk has only one partition which is why the other 3 lines are all zeros. Post the file /tmp/foo.hd here as other stuff may yield clues. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntfs mount
J. W. Ballantine wrote:
Seems our friends in redmond have done something strange with the
fs type. both w2k partitions on the disk show a type of 45
Hmm, it's not a brand-name PC that came with Windows pre-installed is
it? If so there may be a hidden "recovery/diagnostics" partition that is
confusing fdisk.
Do you have anything like OnTrack Disk Manager installed to get round
disk size limitations in the BIOS? Unlikely with a machine that runs
W2K, but I do know someone that installed in on a P-III machine when he
built it, using an old 6.5Gbyte disk, "because it came with the disk"?
Since you have 2 Windows partitions, you haven't installed any form of
multi-OS boot manager have you? You wouldn't need it with W2K but you
may have had if you had 2 different versions of Win9x on there once over?
Can you post the whole output of `fdisk ad0', it may just give someone a
clue?
and both freebsd show 165.
Which is correct.
Regards,
Mark
Thanks
Jim
-- In Response to your message -
Date: Thu, 06 May 2004 20:40:45 +0100
To: "J. W. Ballantine" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
From: Mark Ovens <[EMAIL PROTECTED]>
Subject: Re: ntfs mount
J. W. Ballantine wrote:
> when I do a properties under w2k it says file system is ntfs,
> fdisk on bsd show partition 1 is sysid 45,(unknown)
>
Hmm, should be sysid 7. I can't remember if the NTFS driver is built
into the kernel (by default) or it's a kld module under 4.x, I'm running
-CURRENT, but I'm sure I never had to do anything special for NTFS
support in 4.x and the Handbook and FAQ only mention mount_ntfs.
FWIW, here's what I get (single partition, C:, on the first drive). Note
mine is 'da0', not 'ad0', as it's SCSI not IDE:
/home/mark{38}# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8924 heads=255 sectors/track=63 (16065 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 143347932 (69994 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
The data for partition 3 is:
The data for partition 4 is:
/home/mark{39}#
> -- In Response to your message -
>
>> Date: Thu, 06 May 2004 20:01:24 +0100
>> To: "J. W. Ballantine" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
rg
>> From: Mark Ovens <[EMAIL PROTECTED]>
>> Subject: Re: ntfs mount
>>
>> J. W. Ballantine wrote:
>> >
>> > yes, there is only one hard disk.
>> >
>>
>> What does the output from `fdisk ad0' show?
>>
>> Regards,
>>
>> Mark
>>
>
>
>
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntfs mount
J. W. Ballantine wrote:
when I do a properties under w2k it says file system is ntfs,
fdisk on bsd show partition 1 is sysid 45,(unknown)
Hmm, should be sysid 7. I can't remember if the NTFS driver is built
into the kernel (by default) or it's a kld module under 4.x, I'm running
-CURRENT, but I'm sure I never had to do anything special for NTFS
support in 4.x and the Handbook and FAQ only mention mount_ntfs.
FWIW, here's what I get (single partition, C:, on the first drive). Note
mine is 'da0', not 'ad0', as it's SCSI not IDE:
/home/mark{38}# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8924 heads=255 sectors/track=63 (16065 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 143347932 (69994 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
The data for partition 3 is:
The data for partition 4 is:
/home/mark{39}#
-- In Response to your message -
Date: Thu, 06 May 2004 20:01:24 +0100
To: "J. W. Ballantine" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
From: Mark Ovens <[EMAIL PROTECTED]>
Subject: Re: ntfs mount
J. W. Ballantine wrote:
>
> yes, there is only one hard disk.
>
What does the output from `fdisk ad0' show?
Regards,
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
