Cannot create custom FreeBSD 7.0 install CD for serial console
I've been trying to create a modified FreeBSD 7.0 install CD that will allow me to do installations entirely via the serial console on a headless system. Lots of digging on the Internet, reading the handbook, and I've gotten nowhere fast. The following process was my best hope, but it still isn't making a serial console install possible... In a shell on another older FreeBSD system, after downloading the Disc 1 install ISO: # cd /data # mdconfig -a -t vnode -f /data/7.0-RELEASE-i386-disc1.iso -u 1 # mount -t cd9660 /dev/md1 /mnt # mkdir headlessISO # tar -C /mnt -pcf - . | tar -C /data/headlessISO -pxvf - # umount /mnt # mdconfig -d -u 1 Next I verified that the following line appears in /data/headlessISO/boot/device.hints, ensuring that COM1 (sio0) may be used for console purposes: hint.sio.0.flags="0x10" Then I created a boot.config file for the root of what will be the new CD ISO: # echo "-Dh -S115200" > /data/headlessISO/boot.config I would have preferred to use "-P" in place of the above "-Dh", but I'm using an Intel S3210SHLC motherboard and either it or some bug in FreeBSD 7.0 always causes a keyboard to be detected, even when there isn't one (solutions/explanations for that would be appreciated too). Next step was to build the new ISO as follows: # mkisofs -R -J -ldots -no-emul-boot -b boot/cdboot -o /data/7.0-RELEASE-i386-disc1-headless.iso /data/headlessISO Since the old FreeBSD system has no CD writer, I transfer the new ISO to a Windoze box and burn a CD with Nero. End result is a bootable install CD that acts as if I never customized it at all. I've configured the motherboard BIOS to enable console redirection to COM1 and that works fine... until the FreeBSD boot process, whereupon everything reverts to internal console only. As a variation on the above procedure, I replaced the step in which I create boot.config with one in which I create /data/headlessISO/boot/loader.conf.local containing the following lines: boot_multicons="YES" boot_serial="YES" comconsole_speed="115200" console="comconsole,vidconsole" That, unfortunately, gets the same result. So, what am I doing wrong? Note that the creation of boot.config and some mods to the ttyd0 line in /etc/ttys appears to work fine for enabling serial console operation on this same motherboard *after* FreeBSD 7.0 has been installed to the hard drive using the internal console - it just won't work for creating an install CD. I assume I don't need any variation of the /etc/ttys mod for the custom install CD, true? FWIW, I've also taken the resultant ISOs I've created and fed them to UNetbootin (http://unetbootin.sourceforge.net/) in order to create a bootable USB flash thumb drive installer instead of a CD. This is even less successful because once control appears to go from BIOS to the installer, the screen goes blank and I'm left with nothing but an eternal blinking cursor. Am I up against another Intel S3210SHLC motherboard problem or does UNetbootin not actually live up to it's claims for FreeBSD 7.0? Anyone know? Is there anyone out there who might have experience with FreeBSD 7.0 on the Intel S3210SHLC motherboard? Is this a problematic motherboard with known problems? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot create custom FreeBSD 7.0 install CD for serial console
Jeremy Chadwick wrote: On Wed, Oct 01, 2008 at 02:41:03AM -0700, Carl wrote: I've been trying to create a modified FreeBSD 7.0 install CD that will allow me to do installations entirely via the serial console on a headless system. Lots of digging on the Internet, reading the handbook, and I've gotten nowhere fast. Try this: http://jdc.parodius.com/freebsd/pxeboot_serial_install.html I was already aware of that solution, but it's not for me. There are times when I need to do the install and setting up a DHCP server et al is not viable. Installing FreeBSD via the network has no benefits for me and I will not be trying to install remotely. All I need is to be able to do a simple install using the local serial console because a keyboard and monitor is not practical in the situation. Can anyone tell me where the mistake is in my process? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Intel S3210SHLC motherboard and FreeBSD 7.0
Does anyone have any direct experience running FreeBSD on the Intel S3210SHLC motherboard? If so, what problems have you run into? I'm trying to use FreeBSD 7.0, but I don't know yet if the problems are specific to 7.0 or not. The DVD reader/writer is an LG GH20NS10 SATA drive. Motherboard BIOS is release 45, BMC is release 31, and FRUSDR is 13. As per another thread I started, creating a serial console installation CD is just not working for me, although I'm still pursuing it. I managed to install FreeBSD 7.0 using the standard installer CD (aka internal console), but any deviation from that seems impossible. Creating a bootable USB flash thumb drive doesn't work either, despite having enabled such functionality in BIOS. In fact, getting this motherboard to boot from a USB thumb drive doesn't seem to work whether it contains FreeBSD or something else entirely. I've had a couple of incidents where pressing the reset button actually powers down the server for 5 seconds or so before automatically powering back up. Not a big deal, but doesn't instill confidence in this motherboard. Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel S3210SHLC motherboard and FreeBSD 7.0
Jeremy Chadwick wrote: On Fri, Oct 03, 2008 at 01:37:56AM -0700, Jeremy Chadwick wrote: 2) BIOS: Thermal monitoring I should be more precise: I'm referring to things like fan speed auto-slowdown or PWM. These boards often offer numerous methods of throttling fans and other features. I *did* make some BIOS setting changes within the time frame of the unexpected reset-equals-power-cycle events, but I didn't notice whether there was a correlation. As regards getting USB flash thumb drives to boot, a new thumb drive, lots of reading and experimenting with obscure applications, and I've successfully got Damn Small Linux to boot with the aid of UNetbootin. FreeBSD 7.0 still won't boot, but I appear to have stumbled over a UNetbootin bug that FreeBSD probably can't be blamed for: https://bugs.launchpad.net/unetbootin/+bug/272219 That unfortunately leaves me still wondering whether the motherboard and/or that SATA DVD drive are compatible with FreeBSD 7.0 or not. Can anyone point me to instructions on how to create a FreeBSD 7.0 install USB thumb drive without the aid of UNetbootin? I've found bits and pieces on the 'net, but nothing complete. Surprising, actually, when you think about it. No one else out there with experience combining the Intel S3210SHLC motherboard and FreeBSD? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot create custom FreeBSD 7.0 install CD for serial console
On Thu Oct 2 06:59:47 UTC 2008 Jonathan McKeown wrote: On a system running 6.2-RELEASE, with a 6.2-RELEASE Disc 1 in the CD drive but not mounted: mkdir serialcd tar xvfC /dev/acd0 serialcd These two commands created a directory tree in serialcd containing most of the contents of the CD. There was a ``tar ignoring out-of-order file'' error, and when I mounted the CD and ran diff -qr /cdrom serialcd it reported that RELNOTES.TXT differed - in fact the version in the serialcd directory turned out to have zero length. [I suspect you could probably do this comparison quicker with mtree, and I never did bother to fix it or find out why it was happening] Thanks, Jonathan. So I've redone the process again. I'm working from the original ISO image instead of a physical CD copy of it, so I utilize step 4 from Jeremy Chadwick's document (http://jdc.parodius.com/freebsd/pxeboot_serial_install.html) to make the initial directory tree. There are no tar error messages. I edited serialcd/boot/loader.conf to include the line console="comconsole" I did exactly that, although I also tried adding the following lines instead on a separate attempt: boot_multicons="NO" boot_serial="YES" comconsole_speed="115200" console="comconsole" I then ran mkisofs -J -r -b boot/cdboot -no-emul-boot -o serialcd.iso serialcd and got an ISO image, serial.iso, which is about 600MB. Your switches are a little different from my original procedure, so this time I used yours. The only drawback with this method is that the serial console only cuts in just before the boot menu. I suspect that if you wanted to have a serial console for every stage of the boot you would need to mess about with the ramdisk image on the CD. So creating a boot.config in the root of the CD image cannot be used the way it is for a hard drive installation in order to solve that problem? Anyway, I didn't create a boot.config this time, so I should have ended up with a 7.0 equivalent of your 6.2 serialcd.iso, which I then burned and tried. End result? Abject failure again. All boot stages still use the internal console. Just after "Loading /boot/defaults/loader.conf" appears, there is a *very* long pause added as compared with the unmodified install CD. Eventually it resumes. Don't know why that's happening. Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cannot install from existing UFS thumb drive with sysinstall
I've crafted a USB flash thumb drive containing a bootable UFS partition containing the contents of 7.0-RELEASE-i386-disc1.iso. It boots properly and sysinstall runs as expected, so I'm all set to install FreeBSD to a system that has no optical drive. Just as "fbsd2" in the following thread, I ran into the problem of being unable to specify the USB thumb drive as the installation media: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00369.html [ http://tinyurl.com/4o7pkl ] I was not deterred though because I knew from Reid Linnemann's response that I just needed to select "Install from an existing filesystem". I also understood that I'd need to go to the Fixit menu first and launch the Emergency Holographic Shell (EHS) first in order to mount the thumb drive's UFS partition. Unfortunately, the final response in the above thread appears to indicate that "fbsd2" might not have understood what he was seeing and it seems no one followed up with an explanation or solution. The problem is that the EHS, exactly as advertised, has a very small set of commands. While it does include 'mount_nfs', it does not appear to include anything for mounting a local UFS filesystem, which strikes me as being a strange thing to leave out. So, can anyone tell me how I can mount my thumb drive's UFS partition from within sysinstall? Linnemann countering the "fbsd2" assertion that this is a show stopper now looks to me to have been a little hasty, but I need to believe I'm missing something here. If there really isn't a way to mount the thumb drive's filesystem, is there a way to custom the ISO content such that either 1) the EHS can have 'mount' added to it, or 2) the thumb drive's filesystem can be automatically mounted upon sysinstall startup? Yes, I realize anything's possible if I were willing to build a whole new custom ISO from the ground up, but that's more dramatic than I'm ready for. I know virtually nothing about NFS, so excuse what is probably a stupid question... is it possible to use sysinstall's NFS capabilities to mount a local UFS filesystem somehow? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot install from existing UFS thumb drive with sysinstall
FBSD1 wrote: There is a outstanding PR on sysinstall from usb flash drive which is now over a year old. The sysinstall install program needs to be updated to use usb drives as the source of the install media. You could always edit the sysinstall program source code and make a patch to allow usb sysinstall media. Other than that you are S.O.L. I use this script to build my bootable 1GB USB flash drive [ ... ] Should I assume you've tried the fdisk/disk label method of mounting your flash drive in sysinstall and that it does not actually work either? I've been using FreeBSD for well over a decade and it seems that sysinstall development was all but abandoned a very long time ago. FWIW, the reason I didn't use your script was that in my case I'm actually creating multiple partitions on an 8GB thumb drive and using syslinux such that I can boot any one of several live disk images. FreeBSD seems to be the one distribution that hasn't clued in that USB flash devices are ubiquitous. For my hardware, it also looks like FreeBSD may be having problems with SATA DVD drives too. Since the motherboard has no IDE controller, USB flash drives may be my only hope unless I want to move to another OS. Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gjournal: journaled slices vs. journaled partitions
My goal is to build a 2-disk server configured with gmirror and gjournal for maximum reliability. There will never be a second operating system on the system, but I prefer not to freak out any non-FreeBSD repair tools that might be used, so I will use compatibility instead of dangerously dedicated mode. This means I need one slice, but see no reason for more. Inside that one slice will be the usual array of partitions (ie. /, swap, /var, /tmp, /usr, /data). Now, I think gmirror allows me to mirror the entire drive rather than forcing me to do per-slice or even per-partition mirroring. I'm looking for the simplest in-field replacement procedure when one of the drives dies and I imagine a whole drive mirror achieves this. Am I right? gjournal, OTOH, has me really confused. The man page for gjournal(8) specifically does not recommend that small partitions be journaled. I assume that's because the journal provider rivals the partition in size and is therefore overhead heavy. It seems to me, though, that if I can journal the slice as a whole instead of per-partition journaling, that there will essentially then be only one journal provider for the combination of all partitions (ie. slice) and that the aforementioned overhead becomes minor. Having smaller partitions included in journaling seems like a good thing to me. So how do I achieve per-slice journaling instead of per-partition? Every time I read up on someone else's gjournal implementation, it seems to end with adding .journal entries to /etc/fstab. Am I trying to achieve the impossible or ill-advised here? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gjournal: journaled slices vs. journaled partitions
Laszlo Nagy wrote: So how do I achieve per-slice journaling instead of per-partition? The docs only says this: "gjournal only supports UFS2". It does not specifically say that you cannot have per-slice journaling. However, since you could have other filesystems on your slice, I bet that slice based journaling is not supported. I thought I read somewhere that because gjournal is block based and not really part of the filesystem, that it could easily be extended for any other filesystem. My imagination said that gjournal was probably therefore only temporarily limited to a slice full of UFS partitions. Anyone know for sure? Another tricky question: why would you journal a SWAP partition? Well, I don't really want to, but how big does a partition like /var have to be before it's no longer ill-advised to journal it individually? A fair bit of writing can occur in /var and the scenario my server will occupy has me concerned about inglorious shutdowns. What are the actual reasons for why journaling a small partition is considered a bad idea? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gjournal: journaled slices vs. journaled partitions
Volodymyr Kostyrko wrote: I have some setups were gjournal was put on device rather the on partition, i.e.: [umgah] ~> gmirror status NameStatus Components mirror/umgah0 COMPLETE ad0 ad1 [umgah] ~> gjournal status Name Status Components mirror/umgah0.journal N/A mirror/umgah0 [umgah] ~> glabel status Name Status Components ufs/umgah0root N/A mirror/umgah0.journala label/umgah0swap N/A mirror/umgah0.journalb ufs/umgah0usr N/A mirror/umgah0.journald ufs/umgah0var N/A mirror/umgah0.journale Does the above suggest that you've ended up with individual journal providers for each partition anyway? If so, where are they and have you really achieved anything functionally different? Are they at the end of their individually associated partitions or all together somewhere else? Has the ill-advised journaled small partition issue been successfully overcome through what you've done? [umgah] ~> mount /dev/ufs/umgah0root on / (ufs, asynchronous, local, noatime, gjournal) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, asynchronous, local) /dev/ufs/umgah0var on /var (ufs, asynchronous, local, noatime, gjournal) /dev/ufs/umgah0usr on /usr (ufs, asynchronous, local, noatime, gjournal) devfs on /var/named/dev (devfs, local) And yes, mirror autosynchronization is turned off, gjournal takes care of that too. It's not stated in manual, but gjournal is typically transparent for any type of access, just in case of UFS file system is marked as journaled so any metadata writes can be distinguished from data writes. Without that gjournal does literally nothing. And what does this mean for your swap partition? Laszlo Nagy wrote earlier: Another tricky question: why would you journal a SWAP partition? Volodymyr, does your assertion that gjournal does nothing when a file system is not UFS mean that there is no penalty with regard to your swap partition despite the existence of "mirror/umgah0.journalb"? Any chance you'd like to share your command sequence for constructing your gmirror'd and gjournal'd filesystem, Volodymyr? :-) Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
re: Setting up gmirror
Wojciech Puchar wrote: > Andrew Falanga wrote: Identical drive models so their sizes are the same. Is this the command, from gmirror(8), the one I'll want to use? Create a mirror on disk with valid data (note that the last sector of the disk will be overwritten). Add another disk to this mirror, so it will be synchronized with existing disk: gmirror label -v -b round-robin data da0 add -s like -s 1048576 to prevent splitting one request on 2 disks. I thought the -s option was only applicable when using "-b split" for the balancing algorithm. Does "round-robin" not mean simply alternating between the two disks without ever splitting requests? What are the considerations in choosing between "load", "prefer", "round-robin", and "split" balance algorithms? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Setting up gmirror
Wojciech Puchar wrote: disk will be overwritten). Add another disk to this mirror, so it will be synchronized with existing disk: gmirror label -v -b round-robin data da0 add -s like -s 1048576 to prevent splitting one request on 2 disks. I thought the -s option was only applicable when using "-b split" for the balancing algorithm. Does "round-robin" not mean simply alternating between the two disks without ever splitting requests? no. it means for example with -s 65536 and 1MB request - it will split this request on 2 disks So there is no difference between "split" and "round-robin" algorithms then? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gmirror + subset of partitions gjournal'd, autosync setting?
I've built a GEOM mirror on a single slice of a single disk and am about to insert the second disk. Of the partitions in the mirror, I made only a few of them gjournal'd. I've seen it recommended that one disable autosynchronization for the mirror if using journaled filesystems. 1. Is that recommendation a must or a nice-to-have? What are the actual consequences of not taking that advice? 2. In a case like mine, the non-journaled partitions need autosychronization enabled to benefit from being mirrored, right? 3. Exactly how would I disable autosynchronization for the journaled partitions in the mirror, but not for the rest? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror slice insertion, "FAILURE - READ_DMA status=51"
Jeremy Chadwick said: ad6: FAILURE - READ_DMA status=51 error=40 LBA=134802751 Are you sure you don't have a bad hard disk? This looks to be like a classic block/sector failure. I hadn't realized that a bad block would manifest itself with a message about DMA. Seems like such semantics would be a little obscure to most users, apparently including me. So you're saying that the *exact* same READ_DMA error, at the *exact* same LBA, is reported on ad4? If so, that's very bizarre. No, perhaps I wasn't clear enough. Both instances were on ad6, so far. Can you please provide the output from the following commands? See end of message. Let me know if you then want more (in- or out-of-band). Having now installed smartmontools, you can see below that I ran it for both ad4 and ad6. Sure enough, ad6 has logged 2 READ DMA errors - does that make this a definitive bad disk then? Should I not be worried about ad4 too? Those Raw_Read_Error_Rate and Seek_Error_Rate numbers should be zero or very close to it, shouldn't they? I don't know how to interpret what I'm seeing in that output, so I'd appreciate any insight. Should I be returning both disks for warranty claims (they're both very recently purchased)? Wojciech Puchar said: boot from some kind of live CD, then make another mirror (single disk now) on other drive, then do dd if=/dev/ad6s1 of=/dev/mirror/newmirror bs=2k conv=noerror,sync i intentionally did bs=2k instead of larger, to minimize amount of lost data. then change your system to boot from newmirror, take out /dev/ad6 and have it replaced on warranty (or buy new), put new ad6, insert it to the mirror. I think you're describing a method to help me save as much data from ad6 as possible. Fortunately, this is all about constructing a new system, so there's no data yet to lose. Is there anything I should know about this model of hard disk with regards to being known for problems? Also, is there a good test I can perform to hopefully flush out any problems before I put this thing into service? Carl / K0802647 Additional Information # vmstat -i interrupt total rate irq1: atkbd0 4 0 irq4: sio0125724 16 irq19: uhci3 5 0 irq21: uhci1+ 478364 63 irq23: uhci2 ehci1 1 0 cpu0: timer 14517071 1923 irq256: em0 109568 14 cpu1: timer 14514956 1922 Total 29745693 3940 # atacontrol list | grep -v "no device present" ATA channel 0: ATA channel 1: ATA channel 2: Master: ad4 Serial ATA II ATA channel 3: Master: ad6 Serial ATA II ATA channel 4: Master: acd0 Serial ATA v1.0 ATA channel 5: ATA channel 6: ATA channel 7: # atacontrol cap ad4 Protocol Serial ATA II device model ST31000340AS serial number xxxH firmware revision SD15 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 1953525168 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management no no 0/0x00 254/0xFE # atacontrol cap ad6 Protocol Serial ATA II device model ST31000340AS serial number xxxA firmware revision SD15 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 1953525168 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management no no 0/0x00 254/0xFE # smartctl -a /dev/ad4 smartctl version 5.38 [i386-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home p
Re: gmirror slice insertion, "FAILURE - READ_DMA status=51"
Jeremy Chadwick wrote:
Seagate chooses to encode some raw data for some SMART attributes in a
custom format. The format is not publicly documented. This is why you
have to go off of the adjusted values shown in VALUE/WORST/THRESH.
"How am I supposed to know all of this?!" You aren't -- it comes with
experience.
And yet my failing drive's VALUE numbers are still all above their
THRESH values, despite it being bad enough to cripple the system. One
might argue those threshold values leave something to be desired.
Is there anything I should know about this model of hard disk with
regards to being known for problems? Also, is there a good test I can
perform to hopefully flush out any problems before I put this thing into
service?
I'm confused: what gives you the impression there's a problem with
*this model* of hard disk? I've seen no evidence presented that
indicates such. What makes you ask that question?
I don't have such an impression, thus far. In fact, Seagate drives have
always been good to me prior to this. It's only a precautionary question
because it's better to ask now than after I've committed a lot of real
data and time to it and put it all into service.
Let's take a look at the SMART data.
# smartctl -a /dev/ad4
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
...
198 Offline_Uncorrectable 0x0010 100 100 000Old_age Offline
- 0
...
To get an update on Attribute 198, you'd need to run a short offline
test ("smartctl -t short /dev/ad4"). You can safely do this while
the disk is in use; don't let the word "offline" make you think the
disk disappears. You can watch the status using smartctl -a, and
once its finished, you can compare the old value to the new. I'm
willing to bet it remains zero.
I ran that test on both drives. ad6 failed immediately at 90% with a
"read failure" - not surprising. ad4 completed without error and no
change in it's values, just as you predicted.
# smartctl -a /dev/ad6
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
...
5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always
- 2
...
10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always
- 1
...
187 Reported_Uncorrect 0x0032 098 098 000Old_age Always
- 2
...
197 Current_Pending_Sector 0x0012 100 100 000Old_age Always
- 2
198 Offline_Uncorrectable 0x0010 100 100 000Old_age Offline
- 2
...
>
And here we see the core of the problem. :-)
Advice is simple: replace this hard disk.
Hope this helps.
It definitely did, Jeremy. Your explanations were most helpful. Thanks!
Carl / K0802647
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror + subset of partitions gjournal'd, autosync setting?
Carl wrote: I've built a GEOM mirror on a single slice of a single disk and am about to insert the second disk. Of the partitions in the mirror, I made only a few of them gjournal'd. I've seen it recommended that one disable autosynchronization for the mirror if using journaled filesystems. 1. Is that recommendation a must or a nice-to-have? What are the actual consequences of not taking that advice? 2. In a case like mine, the non-journaled partitions need autosychronization enabled to benefit from being mirrored, right? 3. Exactly how would I disable autosynchronization for the journaled partitions in the mirror, but not for the rest? Can no one help me with this question? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
building a port with very long list of build options
Let's say I want to build a port for which I need to specify a huge number of build options (eg. ghostscript). In my case I am cross-compiling on an amd64 host for what will be a NanoBSD i386 target, but I don't think that's important here. The scenario precludes using the familiar configuration menu. The problem is that the desired list of options far exceeds what would be sane to specify on the 'make' command line. In fact, it apparently even exceeds what typical text editors tolerate when trying to enter the line in a shell script. What is the recommended solution? Given that I do not want to customize the port's Makefile, I was hoping 'make' would support a command line option that would let me simply point to a separate file containing the list of variables to add, one per line. It's not apparent to me that that exists. Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: building a port with very long list of build options
On 2011-04-21 8:52 PM, Polytropon wrote: This has been possible and common in the past. For example, the many options for the mplayer and mencoder ports could be specified in a file, so changing of a port's file was not needed. I'm not fully sure this option is still present, but at least on v7 it worked. Create a file Makefile.local in the port's directory and specify all your options as desired. This file will be sourced when you issue a "make" command and will override settings of the regular Makefile (e. g. if you want different CFLAGS for _this_ port). The file is to be in the known syntax, NAME=value. Does that solution allow for locating Makefile.local outside the ports tree so as not to contaminate builds for other targets using the same ports tree? On 2011-04-21 9:11 PM, Mehmet Erol Sanliturk wrote: If you read the make manual page , you will see the following option : ... *-f* *makefile* Specify a makefile to read instead of the default one. ... which is used as make -f your_own_make_file_name This form will override the Makefile present in the current directory and will use the specified make file with name your_own_make_file_name . Yes, I did see that, but I interpreted that to mean my make file *replaces* the original, in which case I would need to populate my make file not only with the list of build options I want but also a copy of everything in the original make file. If I'm correct, that doesn't seem to me to be a good idea from a maintenance perspective. I was hoping for something like the -f option that somehow inserted rather than replaced. Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: building a port with very long list of build options
On 2011-04-22 4:13 AM, Manolis Kiagias wrote: On 04/22/2011 10:33 AM, Manolis Kiagias wrote: On 04/22/2011 10:08 AM, Carl wrote: This form will override the Makefile present in the current directory and will use the specified make file with name your_own_make_file_name . make -f your_own_make_file_name Yes, I did see that, but I interpreted that to mean my make file *replaces* the original, in which case I would need to populate my make file not only with the list of build options I want but also a copy of everything in the original make file. If I'm correct, that doesn't seem to me to be a good idea from a maintenance perspective. I was hoping for something like the -f option that somehow inserted rather than replaced. Carl / K0802647 Assuming you have already selected some options during make config, you could try adding your own to the file /var/db/ports//options ___ A probably more elegant way is to use the ports-mgmt/portconf port. This allows per port settings to be applied, which are honored by make, portupgrade and the other tools. Just install and use /usr/local/etc/ports.conf to add your options: Here is the sample supplied with the portconf: editors/openoffice.org-2: WITH_CCACHE|LOCALIZED_LANG=it print/ghostscript-* print/lpr-wrapper: A4 sysutils/fusefs-kmod*: !KERNCONF | !NOPORTDOCS www/firefox-i18n: WITHOUT_SWITCHER | FIREFOX_I18N=fr it x11/fakeport: CONFIGURE_ARGS=--with-modules="aaa bbb ccc" ports-mgmt/portconf certainly does look to be a very appealing solution in general, but am I wrong in thinking that it provides me with no way to address my original problem? How do I use it when I've got an exceptionally long list of options for a particular port? As for manually customizing /var/db/ports//options, the port builds in question are done in a clean chroot using a batch process, so "make config" doesn't happen and /var/db/ports//options never exists. Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FTP server at freebsd.isc.org is broken
During an unattended, non-interactive build of many ports this evening I ran into what I think indicates that the FTP server at freebsd.isc.org is broken. Here is what I believe to be evidence, performed from a FreeBSD 8.2 server at one site: site1# fetch -vvp ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/GD-Arrow-0.01.tar.gz scheme: [ftp] user: [] password: [] host: [ftp.freebsd.org] port: [0] document: [/pub/FreeBSD/ports/distfiles/GD-Arrow-0.01.tar.gz] ---> ftp.freebsd.org:21 looking up ftp.freebsd.org connecting to ftp.freebsd.org:21 <<< 220 Welcome to freebsd.isc.org. >>> USER anonymous <<< 331 Please specify the password. >>> PASS ag...@rose.agile.lan <<< 500 OOPS: cannot change directory:/home/ftp fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/GD-Arrow-0.01.tar.gz: Syntax error, command unrecognized # echo $FTP_PASSIVE_MODE YES site1# ftp freebsd.isc.org Trying 204.152.184.73... Connected to freebsd.isc.org. 220 Welcome to freebsd.isc.org. Name (freebsd.isc.org:agile): anonymous 331 Please specify the password. Password: 500 OOPS: cannot change directory:/home/ftp ftp: Login failed. ftp> bye 500 OOPS: priv_sock_get_cmd There's no reason that I know of for anything on my end to be referencing /home/ftp. I get this on a Windoze system from a second site (different LAN, different WAN address, same city, same ISP): C:\>ftp freebsd.isc.org Connected to freebsd.isc.org. 220 Welcome to freebsd.isc.org. User (freebsd.isc.org:(none)): anonymous 331 Please specify the password. Password: 500 OOPS: cannot change directory:/home/ftp 500 OOPS: priv_sock_get_cmd Connection closed by remote host. And I found this blog entry dated today in which the author is seeing the same problem: http://salihsblog.blogspot.com/2011/05/freebsd-pkgadd-error-syntax-error.html (http://tinyurl.com/42g7dv5) When problems like this arise, shouldn't the FreeBSD port building mechanisms take advantage of the redundant FreeBSD mirrors to roll over to another working server? I use portmaster for port building and it terminates with this sort of output when this scenario arises: => Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/gd-2.0.35.tar.bz2 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/gd-2.0.35.tar.bz2: Syntax error, command unrecognized => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles// and try again. *** Error code 1 Stop in /usr/ports/graphics/gd. What is the recommended way to enable portmaster to be more resilient against such failures? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
wildcards don't work in sh shell for FAT32 filesystem
Why do pathnames containing a wildcard work in the tcsh shell regardless of the target filesystem, but do not work in the sh shell if the target filesystem is FAT32? The following sequence begins in the tcsh shell by mounting a FAT32 partition from a USB thumb drive. /tmp is in a UFS2 partition. There are no files with "fish" in their names in either location. This is happening in FreeBSD 7.0-RELEASE. Why do the last four commands not have the same result? tcsh# mount_msdosfs /dev/da0s1 /mnt tcsh# rm -f /tmp/fish* rm: No match. tcsh# rm -f /tmp/*fish rm: No match. tcsh# rm -f /mnt/fish* rm: No match. tcsh# rm -f /mnt/*fish rm: No match. tcsh# sh sh# rm -f /tmp/fish* sh# rm -f /tmp/*fish sh# rm -f /mnt/fish* rm: /mnt/fish*: Invalid argument sh# rm -f /mnt/*fish rm: /mnt/*fish: Invalid argument FWIW, the context of this discovery was trying to use the grub-install script from the GRUB port to install its boot loader on a FAT32 thumb drive. The script aborts when it attempts something like "rm -f /mnt/boot/grub/*stage1_5" Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 7.1 distribution DVD
I've downloaded 7.1-RELEASE-i386-dvd1.iso and created a bootable USB thumb drive with it. It boots up and launches sysinstall as expected. However, when I try to launch the liveFS from the Fixit menu, it will only look on /dev/acd0. What do I need to modify so that it will look for the liveFS on the thumb drive? Alternatively, since I'm using Grub as a multiboot manager, how would I alter the FreeBSD boot configuration such that it boots the liveFS directly instead of the primitive sysinstall-only boot option? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
(no subject)
___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
a problem setting screen resolution with Xorg-6.9.0
Fellow FreeBSDers, I originally sent this to FreeBSD-X11, but this may be a more appropriate venue. I have recently installed FreeBSD 6.1 on a Pentium III box, using an NVidia GeForce 2 GTS card and a CTX PL9 monitor. Running "X -configure" as root generates the file xorg.conf.new, and then running "X -config xorg.conf.new", pulls up a generic X screen with a resolution of 1600x1200. I go in and modify the xorg.conf.new file to make the default resolution 1280x1024, and rerun "X -config xorg.conf.new", but the resolution is still 1600x1200. This is a wonderful resolution, but it makes everything rather small, and the icons are difficult to see. I am obviously setting something wrong, but I do not know what it is. Might anyone have any suggestions. I really would rather have the resolution be 1280x1024. Thanks for your help! Carl The following is the file xorg.conf.new: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/TTF/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "record" Load "xtrap" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" #DisplaySize 360 270 # mm Identifier "Monitor0" VendorName "CTX" ModelName"3700" ### Comment all HorizSync and VertSync values to use DDC: HorizSync30.0 - 95.0 VertRefresh 50.0 - 160.0 Option "DPMS" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "SWcursor" # [] #Option "HWcursor" # [] #Option "NoAccel" # [] #Option "ShadowFB" # [] #Option "UseFBDev" # [] #Option "Rotate"# [] #Option "VideoKey" # #Option "FlatPanel" # [] #Option "FPDither" # [] #Option "CrtcNumber"# #Option "FPScale" # [] #Option "FPTweak" # Identifier "Card0" Driver "nv" VendorName "nVidia Corporation" BoardName "NV15 [GeForce2 GTS/Pro]" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" EndSubSection EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: JavaNNS installation issues under FreeBSD
<[EMAIL PROTECTED]> wrote: > Hi everybody, > I'm getting problems to install the JavaNNS 1.1 in FreeBSD 4.9. > I tried to install via ports and the package JavaNNS-LinuxIntel.tar.gz > but with both i get the same error, that they could'nt find the > libSNNS_jkr.so. > It asks the path to put the library(/usr/home/marcio/jnns) and the > library is created in the directory, but JavaNNS can't still find the > library file. Does anyone can help me with some idea? > > Below are the output: [ snip ] Which JDK or JRE are you using? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: JavaNNS installation issues under FreeBSD
That's the problem. You are asking a FreeBSD executable (the Java VM) to use a Linux shared library (libSNNS_jkr.so). This can't be done. You need to use a Linux Java VM (from a Linux JDK or JRE) instead. I have JavaNNS 1.1 running on FreeBSD 4.8-R with linux-sun-jdk13. If you feel like trying one of the jdk14's, be sure to read the port pkg-message and pkg-descr files before you decide. <[EMAIL PROTECTED]> wrote: > > I'm using diablo-jre-1.3.1.0 from www.freebsdfoundation.org > > Carl Mascott wrote: > > > >Which JDK or JRE are you using? > > > > > > > ><[EMAIL PROTECTED]> wrote: > > > > > > > >>Hi everybody, > >>I'm getting problems to install the JavaNNS 1.1 in FreeBSD 4.9. > >>I tried to install via ports and the package JavaNNS-LinuxIntel.tar.gz > >>but with both i get the same error, that they could'nt find the > >>libSNNS_jkr.so. > >>It asks the path to put the library(/usr/home/marcio/jnns) and the > >>library is created in the directory, but JavaNNS can't still find the > >>library file. Does anyone can help me with some idea? > >> > >>Below are the output: > >> > >> > >[ snip ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot install from existing UFS thumb drive with sysinstall
Is there no one out there that can help? I've dug into NFS a little more and that does not appear to support mounting a local filesystem under sysinstall. In the following thread, Richard Tobin makes an assertion that suggests that I might be able to mount my thumb drive's existing UFS partition in the disk labelling step. http://unix.derkeiler.com/Newsgroups/comp.unix.bsd.freebsd.misc/2004-10/0920.html [ http://tinyurl.com/3mknq7 ] The first problem I ran into was that there is no way to add a second drive (ie. target drive is SATA hard disk, thumb drive is install drive) to the disk labelling step. The only way that that can be achieved is by first adding it to the fdisk partitioning step. I'm willing to believe that *maybe* there's no risk to my thumb drive in rewriting it's disk label if I'm very careful not to newfs it. But nothing about the fdisk partition editor gives me a sense that it will hold off of rewriting my thumb drive's slice table even though I'm not trying to change anything. It just seems perverse to have to reslice and relabel just to mount an existing filesystem. If the only way one can mount a local filesystem in sysinstall is using the disk label editor, can someone explain to me the actual consequences and risks of this procedure? I did not proceed to Write or Commit in this little experiment yet because of the unknown risks. I have to say that I cannot believe how horribly unfriendly sysinstall is for anyone wanting to use a USB thumb drive as an install medium. In fact, it's looking totally unusable. Clearly sysinstall is utilizing 'mount' functionality for it's own purposes. Surely there's some way for me to access it too?!? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gmirror slice insertion, "FAILURE - READ_DMA status=51"
I'm setting up a dual-disk server and am trying to bring it up with gmirror and gjournal. One slice per disk, the goal being to create a single mirror from said slices with some of the partitions journaled. Installed FreeBSD-7.0RELEASE to ad4, then used technique from here to create single-disk mirror/gm0 on ad6: http://people.freebsd.org/~rse/mirror/ Modified ad4s1a /boot.config to pass control to boot stage 3 on ad6. So far, so good. Began Ralf's procedure for inserting ad4s1 into mirror/gm0. The synchronization began and reached 6% when this little horror appeared: ad6: FAILURE - READ_DMA status=51 error=40 LBA=134802751 GEOM_MIRROR: Request failed (error=5). ad6s1[READ(offset=69018976256, length=131072)] GEOM_MIRROR: Synchronization request failed (error=5). mirror/gm0[READ(offset=69018976256, length=131072)] After that, nothing. System unresponsive. Perhaps needless to say, the system also becomes unbootable because the whole point here was to nuke ad4 as part of inserting it into mirror/gm0. I reinstalled FB7 to ad4, redid the /boot.config modification to make ad6/gm0 bootable again and retried the insertion of ad4 into gm0. Exact same error messages at exactly the same point with same consequences. Now, I see that other folks are having unexplained DMA problems too, albeit in different contexts. What should I be concluding here? Those other folks don't seem to be concluding it's bad drives. If there were bad sectors, I'd get different error messages, yes? FWIW, I'm using gjournal on 3 partitions in mirror/gm0. Here's my server's parts list: - Intel S3210SHLC Motherboard. - Kingston KVR800D2E5/2GI 2GB DRAM (x2). - Intel BX80570E3110 Dual-Core Xeon E3110, 3 Ghz 6MB L2 Cache, LGA775. - Seagate ST31000340AS Barracuda 7200.11, 1TB, SATA (x2). - LG GH20NS10 Internal Super-Multi SecurDisc 20X SATA DVD Rewriter. - Antec 4U22EPS650XR case (NeoPower 650W PSU). Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Write attempt to file in ZFS snapshot dir causes panic
I'm new to FreeBSD. Been experimenting with 8.0-RC1 and zfs in a VM. Really haven't even installed it yet, just getting familiar with zfs usage from the fixit environment. I experienced some strange behavior and was wondering if this would warrant a bug report: 1. load zfs from bootloader prompt and then boot. 2. enter fixit environment. 3. import zpool (in this case a 2 disk vmware mirror named sodpool) 4. cd to previously created snapshot at sodpool/test/myfs/.zfs/snapshot/one 5. attempting to create a new file here results in: Fixit# echo hello > hello.txt cannot create hello.txt: Read-only file system 6. That seems like the desired response. Next, attempt to modify a file that already exists in the snapshot: Fixit# echo hello >> test.txt panic: dirtying snapshot! I know I'm not supposed to be modifying a snapshot file, but a panic doesn't seem like the best response to this situation. I'm using DVD iso named 8.0-RC1-amd64-dvd1.iso This bug report has the same panic but the scenario is different: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/138764 Is there someplace else I should check for existing issues? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS: Strange performance issues
Chris, Don't know, but, I will paste in a portion of the ZFS admin guide from SUN: Because these statistics are cumulative since boot, bandwidth might appear low if the pool is relatively idle. You can request a more accurate view of current bandwidth usage by specifying an interval. For example: # zpool iostat tank 2 Later it says about the -v option: You can use the same set of options (interval and count) when examining virtual device statistics. http://dlc.sun.com/pdf/819-5461/819-5461.pdf Page 95 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Write attempt to file in ZFS snapshot dir causes panic
Thanks for testing it out krad. I went ahead and submitted the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=139806 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Migrating from Linux (keeping partitions at install time)
Frank Shute writes: > On Sat, Nov 07, 2009 at 05:35:58PM -0500, Jerry McAllister wrote: >> > [snip] >> >> Not so sure I did anything for your most important question - if ext2 s ext3 >> is a problem, but I hope the rest is helpful. >> > > No, it's not a problem Jerry. ext3 is basically ext2 + journal, so you > can mount it at as ext2 from within FreeBSD (or Linux). > > The journal sorts itself out when you boot Linux and it mounts the > filesystem as ext3. I haven't been able to mount some ext3 filesystems. When I experimented, it appears that most new ext3 filesystems default to 256 byte inodes. When I created a filesystem with 128 byte inodes then FreeBSD could mount it just fine. I didn't try ext2, but I think the inode is independent of ext2 or ext3. This is for FreeBSD 7.1-RELEASE, so maybe things have changed for 7.2 or 8.0. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Migrating from Linux (keeping partitions at install time)
Ruben de Groot writes: > On Sat, Nov 07, 2009 at 10:18:21PM -0800, Carl Johnson typed: >> Frank Shute writes: >> >> > On Sat, Nov 07, 2009 at 05:35:58PM -0500, Jerry McAllister wrote: >> >> >> > [snip] >> >> >> >> Not so sure I did anything for your most important question - if ext2 s >> >> ext3 >> >> is a problem, but I hope the rest is helpful. >> >> >> > >> > No, it's not a problem Jerry. ext3 is basically ext2 + journal, so you >> > can mount it at as ext2 from within FreeBSD (or Linux). >> > >> > The journal sorts itself out when you boot Linux and it mounts the >> > filesystem as ext3. >> >> I haven't been able to mount some ext3 filesystems. When I >> experimented, it appears that most new ext3 filesystems default to 256 >> byte inodes. When I created a filesystem with 128 byte inodes then >> FreeBSD could mount it just fine. I didn't try ext2, but I think the >> inode is independent of ext2 or ext3. This is for FreeBSD >> 7.1-RELEASE, so maybe things have changed for 7.2 or 8.0. > > This has been patched: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/124621 Thanks for the information, but I notice that it was put into stable *very* recently, so I hope it gets into 8.0-RELEASE. I wasn't too worried about it since the workaround was obvious once I identified the problem. I actually prefer to use Reiserfs, but it appears that nobody is working on rw access for it. Like the original poster, I am a Debian user who is experimenting with it, but from VirtualBox for now. I will probably try setting up dual boot when 8.0 comes out. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: slow clock on FreeBSD 7.2 on vmware
Robert Fitzpatrick writes: > On 12/12/2009 12:59 PM, andrew clarke wrote: >> On Sat 2009-12-12 12:06:18 UTC-0500, Robert Fitzpatrick (rob...@webtent.com) >> wrote: >> >> >>> pgsql# cat /boot/loader.conf >>> kern.ipc.semmni=32 >>> kern.ipc.semmns=512 >>> hint.apic.0.disabled=1 >>> >> According to the loader.conf man page these should all be in the format: >> >> kern.ipc.semmni="32" >> kern.ipc.semmns="512" >> hint.apic.0.disabled="1" >> >> I don't know if this matters. >> >> I'm not sure hint.apic.0.disabled is valid for 7.2. sysctl -a doesn't >> list this variable on my machine. Maybe it's only available on some >> machines. >> >> >>> The only way I'm able to keep the clock up to date is to sync with >>> an Internet time server regularly. Anyone have an idea how fix this >>> issue? >>> >> Can you use ntpd? >> >> Regards >> Andrew >> > > I'm pulling from a time server now every hour, keeps it from getting > behind too much. Perhaps that is what I'll end up doing, loading the > ntp server, I guess that would keep it up to date better? Thanks. If it is consistently off by a certain amount, then you might want to look into /usr/sbin/ntptime to set a frequency offset. If it works, then you can put it into somewhere like /etc/rc.local. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IMAP and SMTP-AUTH with sendmail on FreeBSD 7
; by psbl.surriel.com DNSBL see:
http://psbl.surriel.com/listing?ip="; $&{client_addr} ""', `')dnl
FEATURE(dnsbl,`sbl-xbl.spamhaus.org', `"550 5.7.1 ACCESS DENIED to <"$&f"> from
server " $&{client_addr} " by sbl-xbl.spamhaus.org DNSBL
(http://www.spamhaus.org/xbl)"', `')dnl
FEATURE(dnsbl,`dnsbl.njabl.org', `"550 5.7.1 ACCESS DENIED to <"$&f"> from
server " $&{client_addr} " by njabl.org DNSBL (http://njabl.org)"', `')dnl
FEATURE(dnsbl,`list.dsbl.org',`"550 5.7.1 ACCESS DENIED to <"$&f"> from server:
" $&{client_addr} " see: http://www.dsbl.org with this reference:
http://www.dsbl.org/listing?"; $&{client_addr} ""')dnl
FEATURE(dnsbl,`bl.spamcop.net', `"550 5.7.1 ACCESS DENIED to <"$&f"> from
server: " $&{client_addr} " see: http://spamcop.net/fom-serve/cache/297.html
with this reference: http://www.spamcop.net/w3m?action=blcheck&ip=";
$&{client_addr} ""')dnl
GENERICS_DOMAIN_FILE(`/etc/mail/generics-domains')dnl
define(`confMILTER_MACROS_HELO', confMILTER_MACROS_HELO`, {verify}')dnl
INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamav/clmilter.sock, F=T,
T=S:4m;R:4m')
INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spamass-milter.sock, F=,
T=C:15m;S:4m;R:4m;E:10m')
MAILER(local)dnl
MAILER(smtp)dnl
LOCAL_CONFIG
# dynamic relay authorization control map
Kdrac btree -o /usr/local/etc/dracd
LOCAL_RULESETS
SLocal_check_rcpt
# allow recent POP/IMAP mail clients to relay
R$* $: $&{client_addr}
R$+ $: $(drac $1 $: ? $)
R? $@ ?
R$+ $@ $#OK
End mc file
Thanks in advance for any help!
Carl
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: One or Four?
Erich Dollansky writes: > Hi, > > On Sunday 19 February 2012 04:34:17 Jerry McAllister wrote: >> On Sat, Feb 18, 2012 at 12:07:30PM +0100, Damien Fleuriot wrote: >> >> > >> >> So, Polytropon's three choice pattern is good. Or, I could even >> suggest just two choices. >> > yes, three options is ok. > >> [ ] all in one + swap >>Create one partition containing all subtrees >>plus one swap partition. >> >> [ ] user-defined >>Make your own partitioning selection manually. >>(Both number and size of partitions) >>with a reasonable way to specify partitions and sizes. >>The old Sysinstall way is not bad, but if it obsolete, >>then something as easy that fits the new GPT based system. >> > A normal user will use the first option here and get screwed when the > file system got affected by a power failure. The second option is not > an option for a general user. What will happen in the case of a power failure? I just see an fsck when that happens, and I have been running unix and linux for about 20 years. I have always had multiple partitions in the past, but for 9.0 I went with the single partition. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: VBox network boot
Warren Block writes: > On Tue, 28 Feb 2012, Da Rock wrote: > >> I'm starting to believe this dog won't hunt (in fact is dead, >> bloated, and full of worms...); but has anyone got a solution for >> network booting in VBox on FBSD host? > > To PXE-boot a VM guest, set networking to to Bridged and use the > PCnet-PCI II (Am79C970A) adapter type. If the host is FreeBSD, the > vboxnet kernel module has to be loaded. Please emphasize that the PCnet-PCI II card emulation is necessary. I was trying the Intel emulation and making no progress. I then noticed your page and tried the PCnet-PCI II card and it started working. I would guess that means their Intel card emulation is incomplete. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: VBox network boot
Warren Block writes: > On Tue, 28 Feb 2012, Carl Johnson wrote: > >> Warren Block writes: >> >>> On Tue, 28 Feb 2012, Da Rock wrote: >>> >>>> I'm starting to believe this dog won't hunt (in fact is dead, >>>> bloated, and full of worms...); but has anyone got a solution for >>>> network booting in VBox on FBSD host? >>> >>> To PXE-boot a VM guest, set networking to to Bridged and use the >>> PCnet-PCI II (Am79C970A) adapter type. If the host is FreeBSD, the >>> vboxnet kernel module has to be loaded. >> >> Please emphasize that the PCnet-PCI II card emulation is necessary. > > Updated in the PXE article, thanks. Thank you, that makes it perfectly clear. I had initially ignored that suggestion, thinking that it wasn't important! -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: libc regex word-boundary support fallen-off?
RW writes: > I've noticed for some time that claws-mail and less (which I think use > libc's regex(3)) don't support word boundaries in searches. I might be > delusional, but I think I've used \b in the past in both of those > applications in FreeBSD. > > According to regex(3) it's an implementation POSIX.2, so the feature > needn't be supported, but at the bottom of the page it says > "word-boundary matching is a bit of a kludge", so presumably it has > been. > > Does anyone know what's going on? > > > I switched from i386 to amd64 last year so it might be something to do > with that. I'm currently using 8.2p6. The only way I have found to do it is [[:<:]] and [[:>:]]. That is very awkward, so I't love to hear of a shorter way. I found them in the re_format(7) manpage. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: find date of last boot
Fbsd8 writes: > dmesg command does not show date of last boot. > > Are there some other commands to find date of last boot? In addition to the other responses: sysctl kern.boottime -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ROOT on ZFS with MBR partitions
How long are you waiting? What are you booting from? On Sat, Feb 26, 2011 at 7:54 PM, Slawomir Wojtczak wrote: > > Anything interesting happening during your install? > > I would say no, everything seems smooth until I try to boot it. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Purchased Binaries
Doug Hardie writes: > I have a client who has purchased some software. I don't know > anything much about it yet other than it claims to run on Debian and > CentOS. I suspect its binaries. I will have access to things like > the developer, name etc. on Monday. However, thats when he needs to > know if I can make it run on FreeBSD. I am not convinced I want to run > production software on the Linux compatibility suite. No good reason > other than it sounds like its adding a lot more opportunities for > breakage. This has to be an always up application. I have virtually > no knowledge of CentOS other than it was installed on one server when > I got it. Any chance those binaries might work on FreeBSD? I am > planning on starting with FreeBSD 8.2 since its just out and working > fine on one of my servers, but could use an earlier version if > required to make this stuff run. One addition to the points that others have made is that the Linux compatibility layer appears to be 32 bits only, even for 64 bit versions of FreeBSD. At least that is true for Release 8.1. If the software is 64 bit linux, then it won't work. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel causes "GEOM: ada1: media size does not match label" messages
Maxim Khitrov writes: > On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov wrote: >> Hi all, >> >> Executing the following commands on any valid storage device seems to >> cause "media size does not match label" kernel messages (FreeBSD 8.2 >> amd64). I understand why they happen - glabel metadata occupies the >> last sector, so bsdlabel sees a device that is 1 sector smaller than >> what the kernel sees. The question is whether there is some simple way >> of suppressing these messages, since they come up every time the >> system is booted or the partition is mounted/unmounted: >> >> # glabel label vol0 ada1 >> # bsdlabel -w /dev/label/vol0 >> GEOM: ada1: media size does not match label. >> # newfs /dev/label/vol0a >> # mount /dev/label/vol0a /mnt >> GEOM: ada1: media size does not match label. >> # umount /mnt >> GEOM: ada1: media size does not match label. >> >> As you can see, I'm not using MBR or GPT partitioning schemes. I try >> to avoid those unless I plan on sharing the media with another OS. >> Even if using gpart would get rid of these errors (not sure, since >> then you'll just have a partition whose size doesn't match), I would >> still prefer to find some other way to suppress them. >> >> - Max I am not an expert, but that looks correct as you have it, so I would expect some other problem. You are using vol0 as the partition for newfs and its size should be correctly sized to allow for the last sector of ada1 being used by glabel. I have heard comments that there problems in what some call 'dangerously dedicated' partitions, so you might want to create a single slice covering the whole disk and partition that. If you just want volume names for a filesystem, you might want to try the -L option for either newfs or tunefs. The last example of the glabel manpage shows using a ufs label to contrast it with glabel. I use ufs labels for all of my filesystems and just use glabel for swap, and I suspect that swapon wouldn't catch the type of problem that you are seeing. > Heh... In the process of searching for a solution to this, I decided > to see what would happen if I used bsdlabel on ada1 rather than vol0 > (in my example above), and created a 1-sector partition at the very > end of the disk. So the layout would be something like this: > > # /dev/ada1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a:**4.2BSD > c:*0unused > h:1*unused > > The 'c' partition now covers the entire disk, which stops the kernel > from complaining about media size not matching the label. At the same > time, the 'h' partition will protect the last sector, which contains > glabel metadata. > > The problem now is that the label is technically invalid for the vol0 > device, which is what I'll be mounting. Indeed, bsdlabel complains > when I run it for /dev/label/vol0: > > # /dev/label/vol0: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 3907029151 164.2BSD0 0 0 > c: 39070291680unused0 0 > h:1 3907029167unused0 0 > partition c: partition extends past end of unit > bsdlabel: partition c doesn't cover the whole unit! > bsdlabel: An incorrect partition c may cause problems for standard > system utilities > partition h: partition extends past end of unit > > I don't care about partition 'h'; it is there only to stop the > preceding partition from covering the last sector. Are there any real > issues with the 'c' partition being 1 sector too big for the vol0 > device (but just the right size for ada1)? > > This is a bit of a hack, but I'll take it if it stops the kernel from > complaining and doesn't create any new problems. I don't see where adding an extra partition at the end does anything to protect the earlier partition. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Squeezebox Server 7.6 failed to load: YAML::Syck
I'm running FreeBSD 8.2-RC3 and use Squeezebox Server (v7.5.1, r30836, Tue Jun 1 07:00:00 MDT 2010). Squeezebox Server 7.6 has experimental native support for UPnP media renderers (of which I have many) and I wanted to try it out. I downloaded the latest tarball and when I run slimserver.pl I get the following error: The following modules failed to load: YAML::Syck *** NOTE: If you're running some unsupported Linux/Unix platform, please use the buildme.sh script located here: http://svn.slimdevices.com/repos/slim/7.6/trunk/vendor/CPAN/ If 7.6 is outdated by the time you read this, Replace "7.6" with the major version You should never need to do this if you're on Windows or Mac OSX. If the installers don't work for you, ask for help and/or report a bug. of Squeezebox Server you are running. *** Exiting.. --- The version of Perl seems to be OK: sodserve# perl -v This is perl, v5.10.1 (*) built for amd64-freebsd When I install /usr/ports/textproc/p5-YAML-Syck it's supposedly already installed: ===> Installing for p5-YAML-Syck-1.17 ===> p5-YAML-Syck-1.17 depends on file: /usr/local/bin/perl5.10.1 - found ===> Generating temporary packing list ===> Checking if textproc/p5-YAML-Syck already installed ===> p5-YAML-Syck-1.17 is already installed cpan install gives me: YAML::Syck is up to date (1.17) I'm not really sure what else to check. Can someone point me in the right direction? Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mountroot
2011/6/29 Warren Block > On Wed, 29 Jun 2011, Dick Hoogendijk wrote: > > Op 29-6-2011 21:19, Trond Endrestøl schreef: >> >>> On Wed, 29 Jun 2011 21:18+0200, Dick Hoogendijk wrote: >>> >>> Op 29-6-2011 21:15, Trond Endrestøl schreef: > On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: > > I'm a little desperade. I installed a mirrored ZFS freebsd system in >> a VM the other day and all went well. Now I did the same procedure >> on a real systrem with two drives and I can't get the system to boot >> properly. Everytime it halts at the mountroot prompt. If I manually >> put zfs:zroot at the prompt the system boots to the login screen. I >> checked the /etc/rc.conf and the /boot/loader.conf for syntax errors >> but all seems well. What on earth can be the cause of this >> behaviour? What do I check? Help? >> > Have you specified a bootfs? > > E.g.: > >zpool set bootfs=zroot zroot > Yes, I did. And just did it again. >>> Please post your /boot/loader.conf. >>> >>> And did it again (zpool set bootfs=zroot zroot) ; rebooted and finally >> the system boots up. >> So, problem solved. Posts arfe being fetched. Thanks. >> > > If it's a timeout problem, there's kern.cam.boot_delay=1. > +1 for kern.cam.boot_delay=1. I had the same problem and that setting fixed it for me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: new to os
Lars Eighner writes: > On Fri, 19 Aug 2011, Julian H. Stacey wrote: > >>> Aloha Lars, >>> >>> You mentioned WP5 in this thread. I have some docs on disks that were >>> created in WP5. You know any FreeBSD based app like abiword that can >>> read them for transfer to a contemporary program? >> >> Do you mean Word Perfect ? >> Wordperfect-8.0 used to run on FreeBSD 3.4-RELEASE & was free, >> while Corel charged for the MS based version ! > > If I recall correctly, this was a Linux version which ran with Linux > compatibility as it was then. Also it only ran with a GUI - the command > line version was available for $$$. > > I have no idea whether it could be persuaded (easily) to run with recent > Linux compatibility. I was checking with google and found http://tldp.org/FAQ/WordPerfect-Linux-FAQ/downloadwp8.html. Most of the links are dead or changed, but a couple of them do have files to download. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Is there way to get filename for specific LBA?
per...@pluto.rain.com writes: > Robert Bonomi wrote: > >> > Aug 31 05:13:24 da kernel: ad6: WARNING - READ_DMA UDMA ICRC >> > error (retrying request) LBA=107491647 >> > ... I looked at bsdlabel a it's partition f, /home. But what >> > is the file name? >> >> There's *no* easy way to find out. You'll have to grovel through >> all the filesystem metadata, and the layers of index blocks for >> every file until you find the 'rgiht' one. > > This is what "icheck -B" was for, but icheck(8) no longer exists and > that particular bit of functionality does not seem to be provided in > fsck(8). > > One current userland utility (other than fsck) which does know > how to grovel through the metadata and index blocks is dump(8), > but you'd have to hack on it to report which inode was using a > particular block. It looks like the best bet would be fsdb, assuming that it is a UFS file system. That does have a 'findblk' command to find a file containing a block, but you would need to calculate the block offset in the filesystem first. It doesn't look like it would be easy, as was said earlier. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help Finding ZFS snapshots
"Gene" writes: > On Mon, 05 Sep 2011 10:48:22 -0400, Daniel Staal wrote >> --As of September 5, 2011 8:13:52 AM -0500, Gene is alleged to have said: >> >> > Using FreeBSD 8.1, amd64 - I wanted to recover files from a snapshot of >> > usr/home. Everything I've found via googling refers to a link such as >> > "path/zfs/.snapshot" >> >> --As for the rest, it is mine. >> >> Try "path/.zfs". ;) >> >> (Which, on my system, then has a 'snapshot' directory, which holds >> all the snapshots.) >> >> Daniel T. Staal >> > > No such luck. The following: > > cd / > ls -R | grep -i "zfs" > > finds only 'zfs' directories in the source tree and ports. > > Other ideas? I know the snapshots exist, I can see 'em with > "zfs list -t snapshot". The .zfs directory is hidden by default so you have to specifically ls or go into them. Do a 'ls' on the base directory of any zfs file system, and then add .zfs to the end and you should see the .snapshots directory. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cpio command and schg flags
Polytropon writes: > On Mon, 5 Sep 2011 11:32:05 -0400, joeb1 wrote: >> I am trying to use this code sequence to clone a directory tree. >> mkdir /usr/test1 >> cd /var >> find . | cpio -dmp /usr/test1 >> >> The result is /usr/test1 gets populated with the directory tree but >> all the schg flags get stripped off. >> >> How can I keep the schg flags in the cloned directory? > > As far as I remember, cpio doesn't copy flags. But you > can use either dump + restore, or dpdup (from ports). > >>>From "man cpdup": > > The cpdup utility makes an exact mirror copy of > the source in the destination, creating and > deleting files and directories as necessary. > UTimes, hardlinks, softlinks, devices, permissions, > and flags are mirrored. > > Flags are explicitely mentioned here. Maybe you can give > this program a try? I think that tar will also work (but not gnu tar), and it is part of the base system. The manpage does show an example of how to do this, but calls it moving the file heirarchy. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: snd_hda: how to configure line-in passthrough to line-out?
Brandon Kuczenski writes: > I'm working on the sound on my system running 8.2-RELEASE. Currently > I have sound input and output working using snd_hda (i.e. I can record > on line in, and play it back on line out). > > What I would like to do is take the audio coming in on line-in and > send it back out the line-out "live" without recording it. > > Is this easy to do? I'd appreciate any hints. I do that all the time, so it definitely is not a problem. I find on my card that the output volume is controlled by a combination of 'volume' and 'mix' settings in mixer(8). I also must have the 'igain' set to something above 0, but the volume isn't directly controlled by it. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Timeline for 9.0-RELEASE?
Brett Glass writes: > Just looked at the project Web site, and the timeline for 9.0-RELEASE > is way, way out of date. If all goes well, when is 9.0 expected to be > released? What remains to be done? There is another web page at http://wiki.freebsd.org/Releng/9.0TODO that has been partially updated. That will at least give you some idea about the schedule. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Freebsd, Virtual OSs and GUI
Adam Vande More writes: > On Wed, Oct 12, 2011 at 5:38 PM, Jorge Biquez wrote: > > It is better to install KDE or GNOME as the base GUI or it is better to have >> any other ? (I do not know what could be). >> > > This is one of those ask a hundred different people get 100 different > answers. I prefer KDE which would work well for you because both KDE and > VirtualBox are built on QT4, a rather large system. KDE isn't really that > heavy though relatively speaking. VirtualBox runs great for me and does all > you indicated. > > >> >> What do you think is the best option to save hardware resources and >> accomplish this task ? Something important is that this lab machine will be >> connected directly with the ISP (public IP's) and I will need to connect >> remotely to control the server and the other OS's. >> > > You will probably want a CPU and chipset that has hardware assist for > virtualization, and plenty of RAM for both host and guests. Disk choice > should reflect your data capacity, redundancy, and speed needs. A good > quality Intel NIC is always nice. If the OP is going to run a 64-bit OS, then hardware vitualization assist is *required* for VirtualBox to handle it. It is not required when VirtualBox is running a 32-bit OS. Just another minor detail to consider. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help needed: sound/audio only semi-working
"Ronald F. Guilmette" writes: > I've been bringing up a new amd64 box with 8.2-RELEASE. So far I've managed > to get everything installed OK, including a boatload of freshly-built ports. > I've even gotten flash10 working with firefox... well... > > Unfortunately, this is only MOSTLY working. The video works great, but for > audio all I get is absolute silence. > > The really strange thing is that after I followed all the directions here: > >http://www.freebsd.org/doc/en/books/handbook/sound-setup.html > > This command: > > cat /dev/random > /dev/dsp > > *does* produce quite a bit of white noise sound. However when I perform > the other officially recommended basic audio functionality test: > > cdcontrol -f /dev/acd0 play 1 > > with one of my favorite old audo CDs in the drive (AND with that special > little wire running from the back of the drive to my motherboard) all that > happens is that the CD/DVD drive apparently _does_ start to read some stuff... > as evidenced by the blinking access light in the front of the drive... but I > still get no sound out, and YouTube videos still aren't giving me any audio > even though the video seems to be playing perfectly. > > So, um, I am grasping for ideas here on how I can debug this problem furher. > I really have no idea what to do next to get this debugged. I supposed that > if nobody gives me a good suggestion, I'm gonna try swapping out that special > little wire for another one and then try swapping the CD/DVD drive for another > one if that still doesn't solve it. > > Sigh. :-( I just checked and yes, the CD/DVD drive _can_ mount a data CD > alright. No problems doing that. > > So how can it be that this works just fine: > >cat /dev/random > /dev/dsp > > even while this: > > cdcontrol -f /dev/acd0 play 1 > > causes the disk to spin up and read, but otherwise produces utter silence? > > I'm flummoxed. > > Any help would be appreciated. > > > Regards, > rfg > > > > P.S. My motherboard (w/ onboard audio) is a Gigabyte GA-M55Plus-S3G. Here > is what a get when I cat /dev/sndstat: > > FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) > Installed devices: > pcm0: (play/rec) default > pcm1: (play/rec) > pcm2: (play/rec) > > Additional info: > > % sysctl hw.snd.default_unit > hw.snd.default_unit: 0 I also have a Gigabyte board with HDA audio, and it won't directly play CD sound either. I had already ripped all of my CDs to .ogg files, so I hadn't needed to play the CDs directly. I just tested ripping a small section of a CD using cdparanoia and it does produce a .wav audio file that can be played using sox. I also notice on my computer that mixer doesn't show any controls for CD audio. Unfortunately, I don't remember if CDs worked properly on this computer when I had Linux installed, so I don't know if the problem is FreeBSD or the motherboard. I did find that I have a program called kscd (for KDE) that will play, but I suspect that it uses digital extraction instead of playing from audio. My system uses a Gigabyte GA-MA785GPM-US2H, and the sndstat output is: FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: (play) pcm1: (play/rec) default pcm2: (play/rec) pcm3: (play/rec) Let me know if you want further information. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help needed: sound/audio only semi-working
Carl Johnson writes: > "Ronald F. Guilmette" writes: > >> I've been bringing up a new amd64 box with 8.2-RELEASE. So far I've managed >> to get everything installed OK, including a boatload of freshly-built ports. >> I've even gotten flash10 working with firefox... well... >> >> Unfortunately, this is only MOSTLY working. The video works great, but for >> audio all I get is absolute silence. __snip__ > I also have a Gigabyte board with HDA audio, and it won't directly play > CD sound either. I had already ripped all of my CDs to .ogg files, so I > hadn't needed to play the CDs directly. I just tested ripping a small > section of a CD using cdparanoia and it does produce a .wav audio file > that can be played using sox. I also notice on my computer that mixer > doesn't show any controls for CD audio. Unfortunately, I don't remember > if CDs worked properly on this computer when I had Linux installed, so I > don't know if the problem is FreeBSD or the motherboard. I did find > that I have a program called kscd (for KDE) that will play, but I > suspect that it uses digital extraction instead of playing from audio. > > My system uses a Gigabyte GA-MA785GPM-US2H, and the sndstat output is: > FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) > Installed devices: > pcm0: (play) > pcm1: (play/rec) default > pcm2: (play/rec) > pcm3: (play/rec) Just to follow up, I just rebooted into Linux and the CD audio appears to work properly on it and the CD mixer control seems to work properly. I have FreeBSD 8.1-RELEASE, so it may have changed since then. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nice man pages?
Patrick Lamaiziere writes: > Hello, > > I use sysutils/most to have nice manual pages in color, that's cool but > is there a way to do this with the base system (ie without adding port)? I use a colorized termcap with less, but it also works with /usr/bin/more. It depends on what type of terminal you are using it on. I have it for xterm and rxvt (which is what I use). This works for manpages, but you can also colorize your prompt. It is short, so my ~/.termcap is below: -- snip --- # this is just changes to the standard FreeBSD termcaps - 2010-12-13 cdj xterm|xterm-color|X11 terminal emulator:\ :md=\E[33;1m:so=\E[36;1m:se=\E[0m:us=\E[32;4m:ue=\E[0;24m:\ :ti@:te@:tc=xterm-xfree86: rxvt|rxvt terminal emulator (X Window System):\ :md=\E[33;1m:so=\E[36;1m:se=\E[0m:us=\E[32;4m:ue=\E[0;24m:\ :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:\ :tc=rxvt-mono: -- snip --- All that does is set bold to yellow, standout to cyan, and underline to green. I use white on black, so if you use something else you will probably have to adjust the colors. I haven't tried 9.0, but this works on 8.1-RELEASE and 8.2-RELEASE. You can decide for yourself if that does what you want. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nice man pages?
Thomas Dickey writes: > fwiw, without also setting the NC capability (something like NC#35), > it'll confuse curses/ncurses since that conflicts with the normal > color controls. Thanks, I had missed that description in the terminfo(5) manpage. It worked fine without it, but that might have been just because I hadn't been using enough colors. I put it in but there is no change for my applications. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nice man pages?
Carl Johnson writes: > Patrick Lamaiziere writes: > >> Hello, >> >> I use sysutils/most to have nice manual pages in color, that's cool but >> is there a way to do this with the base system (ie without adding port)? > > I use a colorized termcap with less, but it also works with > /usr/bin/more. It depends on what type of terminal you are using it > on. I have it for xterm and rxvt (which is what I use). This works for > manpages, but you can also colorize your prompt. Obviously I hadn't thought that through since there is no xterm in the base system, but both the xterm and rxvt termcap entries seem to work on the console. Just to be sure I made up a colorized cons25 entry. I left in the underline attribute, even though the console doesn't seem to support underline. I also added the nc capability that Thomas Dickey suggested should be used. The revised version of my ~/.termcap is below if anybody is interested: start ~/.termcap - # these are just changes to the standard FreeBSD termcap - 2010-12-13 cdj # added cons25 and nc capability - 2011-10-26 cdj xterm|xterm-color|X11 terminal emulator:\ :md=\E[33;1m:so=\E[36;1m:se=\E[0m:us=\E[32;4m:ue=\E[0;24m:nc#35:\ :ti@:te@:tc=xterm-xfree86: rxvt|rxvt terminal emulator (X Window System):\ :md=\E[33;1m:so=\E[36;1m:se=\E[0m:us=\E[32;4m:ue=\E[0;24m:nc#35:\ :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:\ :tc=rxvt-mono: cons25|colorized version of cons25|:\ :md=\E[33;1m:so=\E[36;1m:se=\E[0m:us=\E[32;4m:ue=\E[0;24m:nc#35:\ :ac=l\332m\300k\277j\331u\264t\303v\301w\302q\304x\263n\305`^Da\260f\370g\361~\371.^Y-^Xh\261i^U0\333y\363z\362:\ :tc=cons25w: end ~/.termcap - Note that the ac capability in cons25 should be a single (long) line. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to dual-boot FreeBSD 9 with Linux?
Unga writes: > Hi all > > Is any one by now successfully dual-booting FreeBSD 9 with Linux? > > I have tried with OpenSuse 11.4 with FreeBSD 9. OpenSuse installs > Grub1 to mbr. Grub1 doesn't seem to support FreeBSD 9. It cannot > recognise the file system type. > > Any help in this regard is very much appreciated. It isn't very difficult and there are at least two ways to do it. Grub1 actually does support ffs and ufs2 file systems, but the linux distributions don't seem to include the drivers. If you can get the source, that should have all of them. I think that I just got the grub package from the FreeBSD file system and copied the additional drivers directly into my linux grub directory, but I am not sure now. The other way is to use the 'chainloader' command. You just specify the disk and partition (slice) with the root command, and then add the commands 'chainloader +1' and 'boot'. The chainloader command just means to boot whatever is at the first sector of the previously specified disk and slice. I think the first sector of a ufs2 file system just jumps to the loader. The menu items from mine are just: title FreeBSD /boot/loader root(hd1,2,a) kernel /boot/loader boot title FreeBSD chainloader root(hd1,2) chainloader +1 boot In my case, those specifies that they use the third slice on the second disk. The first menu item requires that you already have the 'ufs2_stage1_5' file in your grub directory. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to get /dev/smb* ?
Антон Клесс writes: >> >> mbmon is very old. I've never gotten it to work on any machine I've >> every tried it on. >> >> Does your boot time output show anything smb-related at all, such as >> maybe "smbios0: at ..."? It's possible that >> your machine simply has no support for this. >> > > # dmesg -a |grep smb > > - returns nothing. > > Does it means that it is no way to read temperature sensors on motherboard? Have you tried: $ sysctl -a | grep temperature dev.cpu.0.temperature: 29.2C dev.cpu.1.temperature: 29.2C for your system? I have an AMD cpu and the amdtemp kernel module provides that information. I am not familiar with the Intel cpus, but the coretemp module is supposed to provide the same information for them. I use gkrellm for various thing, and it will display that information directly. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ntpdate on boot problem
Matthew Seaman writes: > On 05/11/2011 22:19, Robert Simmons wrote: >> On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best wrote: >>> same here. simply add something like the following to your crontab: >>> >>> 0 10 * * */2 /etc/rc.d/ntpdate onestart >> >> I have something similar in my crontab which is not exactly what I >> need. I want to make sure that the clock is set at every boot because >> I'm using this as a kerberos server. If the clock is not set properly >> at boot, kerberos will not work properly until the nightly cron jobs >> are run and the clock is set then. I need everything working at boot. >> I can't have a window of problems between boot and midnight or >> whenever cron runs ntpdate. > > crontabs have this handy '@reboot' syntax... It's all explained in > crontab(5). Just be aware that 'Run once, at startup', means when 'cron' starts, not just when the system boots, unless they have changed it recently. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Invalid fdisk partition table found
"Julian H. Stacey" writes: > > @ suggestions: > 1 Try > bsdlabel -B -w -r /dev/da1 > echo unplug, reinsert > newfs /dev/da1a > > 2 Base of _my_ man fdisk > " When running multi user, you cannot write unless you first run this: > sysctl kern.geom.debugflags=16 > " > > It looks like I never got round to sending in a send-pr for that, so feel free > looks like its been that way at least since 7.1.see > http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sbin/fdisk/ I thought I had seen a mention of that somewhere, so I grep'ed the man pages. I found hints on geom(4) and boot0cfg(8), but they certainly aren't obvious. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sudo log messages
Коньков Евгений writes: > Здравствуйте, Polytropon. > > Вы писали 4 декабря 2011 г., 15:41:45: > > P> On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: >>> Tell me please how to stop sudo to food /var/log/messages? > > P> ADDITION: Of course I meant /usr/local/etc/sutoers, > P> NOT sudo.conf. > > P> Instead of logging via syslog (to /var/log/messages), > P> why not use a specific log file for sudo? Add those > P> lines to the sudoers file: > > P> Defaults logfile=/var/log/sudo.log > P> Defaults !syslog > > P> Make sure /var/log/sudo.log exists, and maybe use > P> newsyslog.conf to deal with log rotation and archiving. > P> However, you can easily purge sudo log information > P> this way, if required. > > P> The file /usr/local/share/doc/sudo/sample.sudoers > P> contains an example. > > yes, that is not problem, but I want to control logging in one place > not in each config file of service I have ran on machine. > > I have thought that this > !sudo > *.* /var/log/sudo.log > will take off logging in /var/log/messages but this work as > log to /var/log/messages and to /var/log/sudo.log =(( You are not clear about what you really want. If you want it to log to auth.log instead of messages, then you can use the following in your sudoers file: Defaults syslog=authpriv The sample file that was mentioned earlier is one source for information, but the best source is the sudoers(5) man page. Just search it for syslog and you will find several settings. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with pkg_upgrade
David Jackson writes: > Since I wish to use packages instead of ports to update my system, someone > recommended I use pkg_upgrade. However, basically, it does not work. It > gets to downloaded packages. But, after 10 packages, it prints a message > "Protocol error" and then "Package x cannot be fetched", where x is the > name of the pavkage it stops at. I can restart pkg_upgrade, it downloads 10 > more packages where it stopped previously, but then gives this same message > again. Maybe the connection to the FTP server os being lost and code needs > to be added to automatically restart the FTP connection without the whole > thing crashing? > > I do think packages need to be better supported on FreeBSD, many users do > prefer to use packages due to speed and convenience and do not prefer to > build it all. it shouldnt be such a hassle I can't help directly with your problem, but both portupgrade and portmaster support packages. In both cases you can just supply the -P or -PP options to specify how to handle packages. I think they both require that the ports tree be present for the /usr/ports/INDEX file, but otherwise they can use just packages. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: Root access policy
Damien Fleuriot writes: > On 12/29/11 10:58 AM, Polytropon wrote: >> On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: >>> For the first time, a customer is asking me for root access to said >>> customer's servers. >> >>> Assuming that I'll be asked to continue administering said servers, I guess >>> I should at least enable accounting... >> >> You could have better success using sudo. Make sure >> the customer is allowed to "sudo ". The >> sudo program will log _all_ things the customer >> does, so you can be sure you can review actions. >> Furthermore you don't need to give him the _real_ >> root password. He won't be able to "su root" or >> to login as root, _real_ root. But he can use >> the "sudo" prefix to issue commands "with root >> privileges". >> > > "sudo su -" or "sudo sh" and the customer gets a native root shell which > does *not* log commands ! The sudoers manpage mention the noexec option which is designed to help with the first problem. They also show an example using !SHELLS which can help with the second. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing FreeBSD ver. 8.2
Polytropon writes: > On Sat, 7 Jan 2012 15:05:55 -0800 (PST), leeoliveshackelf...@surewest.net > wrote: >> (1) Does anyone know how to get FreeBSD to read the >> motherboard name? This name, on an xw4400, starts with >> "HP" followed by a eleven digits, and is given in Windows >> XP as "Full Computer Name" on the "Computer Name" tab >> of the "System Properties" window. Among other purposes, >> this name is used by Novell network operating system to >> distinguish hosts on a subnet. > > The OS provides the output of dmesg and maybe the > output of pciconf -lv, as well as the sysctl value > dev.acpi.0.%desc which may contain the required > information. However, I'm sure there is a program > in the ports collection that can be used to obtain > that kind of information. > > Try: > > dmesg | grep "HP" > sysctl -a | grep "HP" > pciconf -lv | less > > and see if there's such a number mentioned. Maybe > you can also use acpidump to retrieve that information > from the ACPI datasets. The 'kenv' command seems to have the board name available as 'smbios.system.product'. The 'kenv' command without arguments will show all values, so you can make sure that is the proper variable. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: kgzip(8) regression in RELENG_9 GENERIC
Devin Teske writes: > On Jan 23, 2012, at 12:56 AM, CyberLeo Kitsana wrote: > >> On 01/23/2012 12:30 AM, Devin Teske wrote: >>> >>> On Jan 21, 2012, at 1:41 AM, CyberLeo Kitsana wrote: >>> >>>> On 01/20/2012 09:02 PM, Devin Teske wrote: >>>>> Taking a GENERIC 9.0-RELEASE kernel and running kgzip(8) on it produces an >>>>> unusable kernel which causes immediate BTX halt in loader(8). >>>>> >>>>> ... >>>>> >>>>> 4. Say: kgzip kernel >>>> >>>> Curious, it doesn't even look like that binary is hooked into the build >>>> process at all on 9.0-RELEASE. >>>> >>> >>> Can you clarify what you mean by the above? >> >> On a brand new GENERIC box running 9.0-RELEASE with no special knobs: >> >> 8< >> (4b18d544)[cyberleo@jenga ~]$ which kgzip > > On my box: > > push900# uname -a > FreeBSD push900.vicor.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 > 07:15:25 UTC 2012 > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > push900# which kgzip > /usr/sbin/kgzip On my system: $ uname -a FreeBSD birch.localnet 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 $ whereis kgzip kgzip: /usr/src/usr.sbin/kgzip $ grep kgzip /usr/src/usr.sbin/Makefile* Makefile.amd64:# kgzip: builds, but missing support files Makefile.i386:SUBDIR+= kgzip So it appears to be i386 only. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9 and 3G Modems
Odhiambo Washington writes: > On Wed, Jan 25, 2012 at 18:54, Mike Tancsa wrote: > >> On 1/25/2012 5:43 AM, Odhiambo Washington wrote: >> > >> > I have a Huawei E1820 >> > >> > I will also try RTFM. >> >> Hi, >>kldload u3g >>kldload umodem >> > > Done, although kldload u3g tells me that file already exists! Perhaps > because I booted up with my Huawei dongle plugged in. > kldstat | grep u3g shows me nothing though. The command 'kldstat -v' shows that u3g is already compiled in for the 9.0-RELEASE kernel. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9 and Windows XP
Eduardo Morras writes: > On Sat, 9 Mar 2013 12:07:41 -0800 (PST) > wrote: > >> Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on >> a computer on which Windows XP currently resides? If so, how can >> this installation be >done? In particular, is there a way to install >> 9.1 so that it can be booted from the traditional master boot record? >> It is important that, when I am done, I can >still boot to Windows >> XP, as I must run some applications not available on FreeBSD. If the >> idea I am proposing is not feasible with version 9.1, will it work >> with >8.3? Any comments are appreciated. If this question has >> already been asked many times before, please just let me know where >> to look to find the answer. Thanks. >Newbie502 > > > As an addon to other answers, you can install VirtualBox, create a > minimal hard disk with MBR boot menu that points to the WindowsXP > partition. This way you don't need to restart in WinXP. The same can > be done from WinXP side, a minimal hd with MBR boot menu to startup > the FreeBSD. It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9 and Windows XP
Warren Block writes: > On Mon, 11 Mar 2013, Carl Johnson wrote: > >> It is my understanding that FreeBSD doesn't allow using part of a disk, >> but grabs the entire disk. That means that VirtualBox can't use >> partitions on a disk that any other partitions are being used by >> anything else, including FreeBSD itself. Am I wrong about this? I use >> VirtualBox using vdmk for an entire disk, but I have never been able to >> share with anything else. > > It's very hard to tell what situation is being described here. If the > VMDK is a pointer to a whole physical disk, that would probably make > the disk only usable by one VM. It should be possible to make the > VMDK point to just one partition on the disk. Then other VMs or a > physical machine could use those other partitions while the FreeBSD VM > was running. I was thinking of the case where I tried to allow direct access by a virtual machine to a slice on the same disk that I was running FreeBSD off of. I just looked further into that and discovered that it is possible, but not allowed by geom by default. It can be done by setting 'sysctl kern.geom.debugflags=0x10'. I am sure that you are aware of the dangers, but for anybody else reading this check out the warning in the geom(4) manpage. They refer to this option as 'allow foot shooting' for a reason. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Recipie for CPU souffle'
Polytropon writes:
> On Tue, 02 Apr 2013 12:55:20 -0700, Ronald F. Guilmette wrote:
>
> No, that does not work. Read the manpage to recognize clearly
> _what_ kind of input the /dev/speaker device accepts. It does
> not understand WAV files.
>
> However, try this example (cw.sh):
>
> #!/bin/sh
>
> read -p "CW ===> " TEXT
> echo ${TEXT} | morse | awk '{
> if(length($0) == 0)
> printf("P4\n");
> else {
> gsub(" dit", "P32L32E", $0);
> gsub(" di", "P32L32E", $0);
> gsub(" dah", "P32L8E", $0);
> printf("%sP16\n", $0);
> }
> }' | dd bs=256 of=/dev/speaker > /dev/null 2>&1
>
> This script doesn't require any non-OS components. You can use
> it as a basis to build a program that will send you system messages
> in an audible way in morse code... :-)
Have you looked at the morse man page lately, specifically the -p
option? :-) Just try 'morse -p sos' to test it.
--
Carl Johnsonca...@peak.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: define more partitions in freebsd
s m writes: > hello all > > i want to install freebsd8.2 on my system. for some reasons, i need > partitions more than 6. my freebsd just allow me to define partitions > from a to h, not any more. > > i checked FreeBSD handbook, but it doesn't say anything about defining > more partitions. > > my question is: how can i define more partitions on my freebsd? (for > example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). > > any comments or hints are appreciated. > SAM Others have already commented that GPT labels are better, but I think that you can have more than 8 partitions. I remember a posting a while back that the maximum had been increased. You will have to experiment if you want to do this, but gpart shows an example that uses 20 partitions: '/sbin/gpart create -s BSD -n 20 ada0s1'. I also don't know that bsdlabel will handle these, so you definitely should experiment first. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: define more partitions in freebsd
s m writes: > thanks guys, > > i understand another solution is GPT partitioning. but i prefer to have > more partitions in traditional freebsd (with MBR table i think). using GPT > is the last solution for me. > > i should create more than 8 partitions with gpart command (flag n which > identifies entries) but i have errors when using it. is there any special > option which should be included in kernel in order to use gpart with flag > n? any one test it before? > > thanks in advance, I just tried it on a FreeBSD 8.3 system without any problems. You will need to explain what kind of errors you had before anybody can help you. I used a zfs volume for testing as follows: gpart create -s MBR /dev/zvol/zpool/v/gtest gpart add -t freebsd /dev/zvol/zpool/v/gtest gpart create -s BSD -n 20 zvol/zpool/v/gtests1 gpart add -t freebsd-ufs -s 1G zvol/zpool/v/gtests1 gpart add -t freebsd-swap -s 2G zvol/zpool/v/gtests1 # add several more freebsd-ufs # output from 'gpart show zvol/zpool/v/gtests1' => 0 41942943 zvol/zpool/v/gtests1 BSD (20G) 0 2097152 1 freebsd-ufs (1.0G) 2097152 4194304 2 freebsd-swap (2.0G) 6291456 2097152 4 freebsd-ufs (1.0G) 8388608 2097152 5 freebsd-ufs (1.0G) 10485760 2097152 6 freebsd-ufs (1.0G) 12582912 2097152 7 freebsd-ufs (1.0G) 14680064 2097152 8 freebsd-ufs (1.0G) 16777216 2097152 9 freebsd-ufs (1.0G) 18874368 209715210 freebsd-ufs (1.0G) 20971520 209715211 freebsd-ufs (1.0G) 23068672 209715212 freebsd-ufs (1.0G) 25165824 209715213 freebsd-ufs (1.0G) 27262976 209715214 freebsd-ufs (1.0G) 29360128 209715215 freebsd-ufs (1.0G) 31457280 209715216 freebsd-ufs (1.0G) 33554432 209715217 freebsd-ufs (1.0G) 35651584 209715218 freebsd-ufs (1.0G) 37748736 209715219 freebsd-ufs (1.0G) 39845888 209705520 freebsd-ufs (1G) # output from 'disklabel zvol/zpool/v/gtests1' # /dev/zvol/zpool/v/gtests1: 20 partitions: # size offsetfstype [fsize bsize bps/cpg] a:2097152 04.2BSD0 0 0 b:41943042097152 swap c: 41942943 0unused0 0 # "raw" part, don't edit d:209715262914564.2BSD0 0 0 e:209715283886084.2BSD0 0 0 f:2097152 104857604.2BSD0 0 0 g:2097152 125829124.2BSD0 0 0 h:2097152 146800644.2BSD0 0 0 i:2097152 167772164.2BSD0 0 0 j:2097152 188743684.2BSD0 0 0 k:2097152 209715204.2BSD0 0 0 l:2097152 230686724.2BSD0 0 0 m:2097152 251658244.2BSD0 0 0 n:2097152 272629764.2BSD0 0 0 o:2097152 293601284.2BSD0 0 0 p:2097152 314572804.2BSD0 0 0 q:2097152 335544324.2BSD0 0 0 r:2097152 356515844.2BSD0 0 0 s:2097152 377487364.2BSD0 0 0 t:2097055 398458884.2BSD0 0 0 I also tried newfs on all the ufs partitions without problems. I just tried this on a FreeBSD 8.2 system and it works there as well. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gvim GUI cannot be used
Jens Jahnke writes: > Hi, > > On Fri, 5 Jul 2013 12:56:32 +0200 > CeDeROM wrote: > > C> Hey Raphael :-) Go to /usr/ports/editors/vim and make deinstall > C> reinstall it, that works for me, and it helps with dialogs in texmode > C> as well :-) > > for me this does not work. Unless I hack the Makefile and force it to > enable gui mode it just isn't compiled in. Try running 'make show-options' and see what you get. Mine shows that virtually everything is disabled. If I run 'make showconfig' then it shows no configurable options. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: had sound working, updated machine now lost sound
Antonio Olivares writes: > Dear all, > > Following advice from thread(s) : > > http://forums.pcbsd.org/showthread.php?t=13976 > > http://forums.freebsd.org/showthread.php?t=5136 > > root@grullahighschool:~ # sysctl hw.snd.default_unit=0 > hw.snd.default_unit: 1 -> 0 > > Got the sound working like it was. > How do I get it to stick across reboots? > > Which would be the preferred way? Since you can set it with sysctl then sysctl.conf is the logical place, although loader.conf might also work. I use sysctl.conf so I know that works. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adaptec 29160 Scsi card / camcontrol rescan
J.D. Bronson wrote: I know the bus will slow down with the tape drive attached, but will it come back to normal speeds once I remove the tape drive? - and/or do I have to run the camcontrol command again? Run the rescan again. Just removing the device from the bus does not cause the kernel or the hba to perform any action. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Location of disklabel
Hi all! To all your FS guru's outthere, I desperately need to know where the disklabel is stored (since my disk is in trouble!) Situation: My /dev/ad0s1 has 2 partitions: "a" (FS) followed by "b" (swap). By using "disklabel -r", I see my "a" and "b" indeed take up the entire slice. My desperate question: Where, then, is the "disklabel" stored? Somewhere in the partition table? The Master Boot Record? The reserved cylinder #0? Or is it stored somewhere inside /dev/ad0s1a ?? (if that's the case, does that mean the UFS1 intentionally left some space unused, for this purpose? And if so, is it always at a fixed location within a UFS1 slice?) What if in my slice, I have SWAP first, and then UFS1, then does that mean the SWAP Format also reserves some unused space for the disklabel to go??? Sorry if the question is stupid. I just somehow couldn't logically see where it would be stored, and yet be compatible with having other OS on the same drive... etc. Thanks! - Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IBM eServer 346 ServeRaid is too slow
Hi Eugene, Eugene Mitrofanov wrote: I've got Subj and FreeBSD-5.4PRE on it. But RAID0 is too slow: [EMAIL PROTECTED]:eugene# dd if=/dev/zero of=/var/tmp/1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 31.949508 secs (3281979 bytes/sec) mpt0: port 0x4000-0x40ff mem 0xcffe-0xcffe,0xcfff-0xcfff irq 28 at device 1.0 on pci4 da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 34678MB (71020544 512 byte sectors: 255H 63S/T 4420C) I'd say you are seeing the same as I am with the same card in a Dell 1855. There is something wrong with the mpt driver and the disks when they are setup in a raid0 set. If you split the disks and use them as individual drives then you will get full performance. Carl. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mathematica 5 under FreeBSD Emulation?
Hello, sorry if this has been discussed already, but I can't seem to find it: has anyone had any luck getting the Linux version of Mathematica *version 5* to work under FreeBSD emulation? Thanks, Carl ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup gets connection refused
When starting cvsup I get the message connection refused when trying to FTP. I think it takes the user id from my server and uses that ... and that's not known at the download server ofcourse. Where can I configure to use an anonymous userid or is there another way to solve this. Thanks, Carl _ Let the advanced features & services of MSN Internet Software maximize your online time. http://click.atdmt.com/AVE/go/onm00200363ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tar Syntax Help
Try leaving off the leading / from each line in your exclude list. I think what is happening is that, by default, tar drops the leading / from each file it tars up so that when you untar, it extracts all files relative to the current directory. I think because of this, when you specify absolute paths in your exclude file, tar fails to match them. Alternatively, if you want to keep the absolute paths, try tar with the -P option. Your exclude list may work as is in that case. I haven't ever tried that myself though. Just be careful when you untar if you do use that switch. Carl On Thu, Jul 07, 2005 at 08:20:50PM -0700, Drew Tomlinson wrote: > I'm trying to copy an entire file system while using an exclude file to > avoid copying things such as /dev, /proc, etc. I've read the man page > and found the -X or --exclude-from tar option. I've create a file > called /exclude.list. It contains lines such as: > > /exclude.list > /dev > /proc > > But I can't figure out how to form the correct command line. I > basically want to do this: > > tar -cvf - --exclude-from /exclude.list -C / . | tar xpf - -C . > > I've search the web and found examples that look similar to the above > but this does not work for me. tar attempts to copy /dev and I get all > the associated errors. I've tried other placements of either "-X", "X", > and "--exclude from" on the command line various things happen from it > just being ignored to tar thinking I want to create and archive named > "-X", etc., to tar trying to add a file named "-X", etc. to the current > archive. I'm at a loss. > > I'm using 4.11 and trying to make a good backup before upgrading to > 5.4. Can anyone tell me the secret incantation to make this work? > > Thanks, > > Drew > > -- > Visit The Alchemist's Warehouse > Magic Tricks, DVDs, Videos, Books, & More! > > http://www.alchemistswarehouse.com > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Growisofs seg faults with DVD-RAM. Anybody else seen this?
I was trying to use growisofs to write to a DVD-RAM and it kept seg faulting. It worked fine with a DVD-R. I tracked the problem down to place in the code where growisofs tries to perform an operation on a file handle it has already closed. I've implemented a workaround already. The problem is, that by my reckoning, this should affect anybody who is trying to use a DVD-RAM (not DVD+RW) with FreeBSD, but I haven't found any references to the problem on the net. I'm wondering if anybody else has seen this problem, and if you've found some other workaround for it? Or alternatively, you still have the problem and my patch would be useful to you. :-) By the way, I'm running Freebsd 5.4 Release and I'm using dvd+rw-tools 5.21.4.10.8 with an ATAPI DVD burner configured to be /dev/cd1. Thanks, Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
On Sat, Jul 30, 2005 at 03:54:25PM +0930, Greg 'groggy' Lehey wrote:
> On Friday, 29 July 2005 at 22:50:13 -0700, Carl Delsey wrote:
> > I'm wondering if anybody else has seen this problem, and if you've
> > found some other workaround for it? Or alternatively, you still have
> > the problem and my patch would be useful to you. :-)
>
> Is this a workaround or a fix? The latter is obviously preferable.
> Also, does this only affect FreeBSD, or is it general? In the former
> case, contact the maintainer (mail address in the Makefile); in the
> latter, contact the project.
It's a fix ... just not as elegant as I would like. Looking through the
code some more, it looks like it's a general problem. I'll try to get ahold
of the maintainer and get this fixed in the distribution.
In the meantime, if anybody needs a solution now, I'm including the patch
here.
--- growisofs.c Tue Aug 24 16:02:29 2004
+++ growisofs.c Sat Jul 30 10:35:45 2005
@@ -2043,7 +2044,9 @@
fcntl ((fd),F_SETFD,f|FD_CLOEXEC); } while (0)
CLOSEONEXEC(in_fd);
CLOSEONEXEC(out_fd);
-CLOSEONEXEC(ioctl_fd);
+if ((ioctl_handle) && (ioctl_handle != INVALID_HANDLE)) /*the fd might
already have been closed*/
+{ CLOSEONEXEC(ioctl_fd);
+}
#undef CLOSEONEXEC
if (!dry_run && (poor_man || next_session==0)) /* unmount media */
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?
On Sat, Jul 30, 2005 at 02:16:17PM -0400, Chuck Swiger wrote: > I'd be happy to review or test them first if you'd like, but any changes of > this sort really ought to go upstream to Andy Polyakov > <[EMAIL PROTECTED]> or to the cdwrite mailing list at > . Thanks. I've just emailed Andy about this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems burning multi session dvd-rw
On Fri, Jul 29, 2005 at 12:15:03PM +0200, Marc Fonvieille wrote: > On Fri, Jul 29, 2005 at 05:17:15PM +1000, Timothy Smith wrote: > > Marc Fonvieille wrote: > > > > >On Thu, Jul 28, 2005 at 03:15:06PM +1000, Timothy Smith wrote: > > > > > > > > >>i'm having some troubles burning a multi session dvd-rw. i blanked te > > >>dvd to make sure it was in sequential mode > > >> > > >>%dvd+rw-format /dev/cd0a -blank > > >>* DVD\uRW format utility by <[EMAIL PROTECTED]>, version 4.9. > > >>* 4.7GB DVD-RW media in Sequential mode detected. > > >>* blanking 100.0| > > >> > > >> > > >> > > >[...] > > > > > >Try to upgrade to a more up to date version of dvd+rw-tools and try with > > >-blank=full option. > > > > > >Marc > > > > > > > > > > > > > > i cvsup'd to the latest and still the same thing, any ideas? > > Did you use "-blank=full" or "-blank"? > Did you have the same issue with all DVD-RW brands? Is your DVD burner > firmware up to date? Is your DVD burner mentioned on dvd+rw-tools' > hardware page? I couldn't get -blank or -blank=full to properly erase a DVD-RAM and I had to resort to "dd if=/dev/zero of=/dev/cd0 bs=2048". That worked for me. YMMV. Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growisofs: no mkisofs options are permitted with =, aborting
On Tue, Aug 02, 2005 at 09:50:03AM +0930, Greg 'groggy' Lehey wrote: > On Monday, 1 August 2005 at 22:31:45 +0200, Hanspeter Roth wrote: > > > > Hello, > > > > I'm trying to burn an iso image onto a DVD+RW. > > I'm trying: > > > > growisofs -Z /dev/cd0=image.iso > > The version of growisofs that I use doesn't have a -Z option. From a > system that does: > >-Z /dev/dvd > Burn an initial session to the selected device. A special form > of this option is recognized to support burning of pre-mastered > images. See EXAMPLES section for further details. > > Is this your intention? If so, it seems that you're not sticking to > the syntax. It's valid syntax ... just not documented in the man page. You have to go out to the website to find out about it. > > This yields: > > > > growisofs: no mkisofs options are permitted with =, aborting... Looking through the code, this error message seems to mean that growisofs found a parameter that it doesn't recognize and assumes you mean to pass it to mkisofs. I'd double check the spelling of all the options. Maybe retype the command to make sure there aren't any invisible control characters that are somehow getting interpreted as options. If none of that works, try adding --quiet to the command line. My quick look through the code suggests this might work (Though my confidence of that is low). If it does work, I'd really like to hear it though. Finally, if none of those things work, you might try: growisofs -Z /dev/cd0=/dev/fd/0 < image.iso > > `dmesg | grep cd0` is: > > > > acd0: CDRW at ata1-master PIO4 > > cd0 at ata1 bus 0 target 0 lun 0 > > cd0: Removable CD-ROM SCSI-0 device > > cd0: 16.000MB/s transfers > > cd0: Attempt to query device size failed: NOT READY, Medium not present - > > tray closed > > This doesn't tell me whether you have a /dev/cd0 or not. That depends > on the release of FreeBSD. Use 'ls -l /dev/cd0' and check that it's a > character device. You should see: > >crw-r- 1 root operator4, 28 Jun 25 21:11 /dev/cd0 > > Older systems have: > >brw-r- 1 root operator6, 0 Aug 26 2000 /dev/cd0a >brw-r- 1 root operator6, 2 Aug 26 2000 /dev/cd0c > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply or reply to the original recipients. > For more information, see http://www.lemis.com/questions.html > See complete headers for address and phone numbers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growisofs: no mkisofs options are permitted with =, aborting
On Tue, Aug 02, 2005 at 01:25:22AM -0400, Chuck Swiger wrote: > Carl Delsey wrote: > > > >It's valid syntax ... just not documented in the man page. You have to > >go out to the website to find out about it. > > Look just before the NOTES section of the manpage: > > " To use growisofs to write a pre-mastered ISO-image to a DVD: > > growisofs -dvd-compat -Z /dev/dvd=image.iso You're right. My mistake. That's what I get for using my eyes to search a document instead of using the search feature. :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growisofs: no mkisofs options are permitted with =, aborting
On Thu, Aug 04, 2005 at 12:06:15AM +0200, Hanspeter Roth wrote: > On Aug 01 at 22:31, Hanspeter Roth spoke: > > > > > Hello, > > > > I'm trying to burn an iso image onto a DVD+RW. > > I'm trying: > > > > growisofs -Z /dev/cd0=image.iso > > > > This yields: > > > > growisofs: no mkisofs options are permitted with =, aborting... > > I must have been drunk! > I had also an additional option `-v' on the command-line. > Without this option it works. > > Sorry for the noise! That's good it's sorted out now. I was starting to question my debugging skills trying to figure this one out. ;-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
open() vs the lowest unused file descriptor
Hi! Today I noticed that on Single Unix Specification V2, as well as on the Linux 2.4.26 machine I have here, that the open() call promises to return the lowest unused file descriptor. I'm just wondering: does FreeBSD 4.x and 5.x promise that? If so, I think we should update the manpage to match SUSv2 more closely. Thank you! - Carl _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No Sound FBSD 8.1
Scott Ballantyne writes: > Hi Frank, > > You write: >> >> Just a guess, but does: >> >> # sysctl hw.snd.default_unit=1 >> >> help? >> >> If so, you can set it permanently in /etc/sysctl.conf >> > > Yes it does, and *thank* *you*. However, it only works with earphones, > not speakers. Any idea what I can do about that? > > And... do you have the time to explain why the default pcm0 channel > *doesn't* work? You can also use 'mixer -f /dev/mixer1' for testing. On my system /dev/mixer1 (default_unit=1) controls the back panel jacks, and /dev/mixer2 controls the front panel headphone jack. You will probably have to just experiment with the different mixer controls to see which controls which on your system. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: start kde in 8.1
Tim Dunphy writes: > sorry forgot to mention I am running it on a dell optiplex gx620 .. > thanks in advance > > On Thu, Oct 28, 2010 at 11:16 PM, Tim Dunphy wrote: >> hey guys, >> I have kdebase4 installed successfully under freebsd 8.1 >> I found the following advice on the net with so far isn't working to start >> it: >> echo "startkde" > ~/.xinitrc >> I have attempted startx but the system doesn't know about it. >> may I have a suggestion to proceed? Do you have /usr/local/kde4/bin in your path? -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Bridging Gigabit and Fast Ethernet Interfaces
if_bridge(4) says: The if_bridge driver currently supports only Ethernet and Ethernet-like (e.g., 802.11) network devices, with exactly the same interface MTU size as the bridge device. Am I correct to assume then that I can bridge a gigabit interface and a fast ethernet interface and that one of the "negatives" of doing this is that Jumbo frames couldn't be used on the gigabit side? I've got an Atom based server with an onboard gigabit nic and only one PCI slot. The server sits physically close to my 10/100 switch that hangs off my firewall. I was thinking of putting a 10/100 nic into the single PCI slot and running that to the 10/100 switch for internet access and then running cable across the room from the gigabit interface to a gigabit switch on my workbench. Wired gigabit clients on the bench would then have the benefit of gigabit access to the server for doing backups but also still have internet access via the server's bridge interface right? Is there a reason I wouldn't want to do it this way? Thanks, Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
GPT/ZFS/USB mountroot prompt
I followed a gpt/zfs on USB stick guide for putting a base 8.1-RELEASE amd64 onto a 4GB sandisk USB memory stick. All went fairly well and the system will boot but fails to mount the root file system and dumps me a the mountroot> prompt. Entering zfs:zrootusb at the prompt works and the system finishes booting. In /boot/loader.conf I've got: zfs_load="YES" vfs.root.mountfrom="zfs:zrootusb" zrootusb mountpoint is set to legacy and /etc/fstab exists but is empty, per the guide. Any ideas? Thanks, Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: GPT/ZFS/USB mountroot prompt
On Wed, Dec 1, 2010 at 12:07 AM, Carl Chave wrote: > I followed a gpt/zfs on USB stick guide for putting a base 8.1-RELEASE > amd64 onto a 4GB sandisk USB memory stick. All went fairly well and > the system will boot but fails to mount the root file system and dumps > me a the mountroot> prompt. Entering zfs:zrootusb at the prompt works > and the system finishes booting. > > In /boot/loader.conf I've got: > zfs_load="YES" > vfs.root.mountfrom="zfs:zrootusb" > > zrootusb mountpoint is set to legacy and /etc/fstab exists but is > empty, per the guide. > > Any ideas? > > Thanks, > Carl > adding kern.cam.boot_delay=1 to /boot/loader.conf seems to have fixed it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cpio misunderstanding?
Polytropon writes: > On Sun, 26 Dec 2010 11:30:59 -0800, David Brodbeck wrote: >> On Fri, Dec 24, 2010 at 4:57 PM, Joe Kraft wrote: >> > OK, now I know what's going on. I just don't know why. The immutable flag >> > was set on all these files, if you clear it cpio will happily copy them to >> > the new directory. >> >> Does cpio attempt to preserve flags? Since the error is "could not >> create," I'm wondering if it's trying to set the same flags on the >> copy of the file and failing to do so. > > I'm not sure about that - "man cpio" doesn't give a hint > about flags. On the other hand, tar's -p option does keep > the file mode (permissions), flags and maybe ACLs intact. > > I've tried "info cpio" ouch! ouch!, but that's not a > continuous manual that allows easy searching for strings. :-( > > Some search in the /usr/src/bin subtree for the "chflags" > call revealed that it is used by the chflags binary, cp, > mv and rm commands, but no hint it is involved directly > in cpio. I had done some testing for flag support out of curiosity, and found that only cp -p, bsdtar and dump support them. Cpio, afio, gnutar, gnucp and pax do not support them. I also tested extended attributes (used for ACLs?), and only bsdtar and dump worked for them. Those results were for usf, and generally didn't transfer to zfs at all or probably other file systems. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ZFS + GPT with root on memory stick and mirrored SATA drives
Posting the below for input. The bulk of this is from a guide that Morgan Wesström posted to this list. Some of it is taken from the root on ZFS wiki entries on freebsd.org. Some from a pjd post here: http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ And then there's this that Svein Skogen posted to the list: I usually (today) set up something similar. I sysinstall FreeBSD onto a CF card with the "one-big-root" method, then create a zpool (on spinning-metal-storage) where I create the usr, tmp, var fs'es, tar|tar the originals over and fix the mountpoint info on the zfs'es. Then I add swap on a zvol (since I don't know how to properly use a kernel dump, I don't need swap to store it). I'm setting up a new home server and I always agonize over partitioning. So the steps below install the base system with zfs root on a usb stick and /tmp /usr /var and swap on mirrored sata drives. I've tested these steps and everything works but before I press on with actually configuring and using the server, does anybody have any input on whether I should or shouldn't do it this way? ZFS best practices suggests that having elements of the root filesystem on different pools is a bad idea. So that might be strike 1. Memory Stick / /bin /boot /dev /etc /lib /libexec /media /mnt /proc /rescue /root /sbin /sys --> /usr/src/sys Hard disk zpool --- /tmp /usr /var swap on zvol Separate zfs datasets - /tmp /usr /usr/home /usr/local /usr/obj /usr/ports /usr/ports/distfiles /usr/ports/packages /usr/src /var /var/log /var/audit /var/tmp Install Procedure (Mostly by Morgan Wesström) - Select your country and keyboard layout. Enter the Fixit environment and use the live filesystem on your DVD. Your usb memory stick will most likely be da0 but you can (and should) check it with "camcontrol devlist" before you continue. Create a new GPT partitioning scheme: # gpart create -s gpt da0 Create a 64KiB partition for the zfs bootcode starting at LBA 1920: # gpart add -b 1920 -s 128 -t freebsd-boot da0 Create a zfs partition spanning the remainder of the usb memory stick and give it a label we can refer to: # gpart add -t freebsd-zfs -l FreeBSDonUSB da0 (The starting LBA for the first partition is there to align the partitions to the flash memory's erase block size. This is particularly important for the main zfs partition. The main partition above will start at exactly 1MiB (LBA 2048) which will align it to any erase block size used today. This alignment is also of great importance if you use this guide to install FreeBSD to one of the newer harddrives using 4096 byte sectors.) Install the protective MBR to LBA 0 and the zfs bootcode to the first partition: # gpart bootcode -b /dist/boot/pmbr -p /dist/boot/gptzfsboot -i 1 da0 Create /boot/zfs (for zpool.cache) and load the zfs kernel modules: # mkdir /boot/zfs # kldload /dist/boot/kernel/opensolaris.ko # kldload /dist/boot/kernel/zfs.ko Create a zfs pool and set its bootfs property: # zpool create zrootusb /dev/gpt/FreeBSDonUSB # zpool set bootfs=zrootusb zrootusb Switch to fletcher4 checksums and turn off access time modifications: # zfs set checksum=fletcher4 zrootusb # zfs set atime=off zrootusb Create zfs mirrored data pool on SATA disks # zpool create zdata mirror /dev/ad4 /dev/ad6 # zfs set canmount=off zdata # zfs set mountpoint=/zrootusb zdata # zfs set checksum=fletcher4 zdata # zfs create zdata/tmp # zfs create zdata/usr # zfs create zdata/usr/home # zfs create zdata/usr/local # zfs create zdata/usr/obj # zfs create zdata/usr/ports # zfs create zdata/usr/ports/distfiles # zfs create zdata/usr/ports/packages # zfs create zdata/usr/src # zfs create zdata/var # zfs create zdata/var/log # zfs create zdata/var/audit # zfs create zdata/var/tmp Create swap zvol on zdata pool # zfs create -V 5G zdata/swap # zfs set org.freebsd:swap=on zdata/swap # zfs set checksum=off zdata/swap Extract at a minimum, base and the generic kernel: # cd /dist/8.1-RELEASE/base # DESTDIR=/zrootusb ./install.sh # cd ../kernels # DESTDIR=/zrootusb ./install.sh generic Delete the empty, default kernel directory and move the generic kernel into its place: # rmdir /zrootusb/boot/kernel # mv /zrootusb/boot/GENERIC /zrootusb/boot/kernel Make sure the zfs modules are loaded at boot: # cat > /zrootusb/boot/loader.conf zfs_load="YES" vfs.root.mountfrom="zfs:zrootusb" kern.cam.boot_delay=1 ^d Create /etc/rc.conf. Adjust and add to your own needs: # cat > /zrootusb/etc/rc.conf hostname="sodserve" sshd_enable="YES" zfs_enable="YES" ^d Setup your time zone: # cp /zrootusb/usr/share/zoneinfo/EST5EDT /zrootusb/etc/localtime Create an empty fstab to avoid startup warnings: # touch /zrootusb/etc/fstab Set the root password in the new environment: # cd / # chroot /zrootusb /bin/sh # pa
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
> echo -en "\n\nNow run these two commands to make the changes live, and > reboot > zfs set mountpoint=legacy $zpool/be/$nroot > zpool set bootfs=$zpool/be/$nroot $zpool\n\n" Thanks for the input krad. It would be nice to easily switch back and forth but aren't you still stuck if everything blows up on that first reboot? In order to switch back to the known working dataset you've got to get to a fixit prompt to set the correct bootfs property right? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Date of a FreeBSD installation
Polytropon writes: > On Thu, 13 Jan 2011 13:50:27 -0800, Chuck Swiger wrote: >> On Jan 13, 2011, at 1:46 PM, Devin Teske wrote: >> > This is nearly always accurate on any FreeBSD system (when wanting to >> > query the date the machine was built): >> > >> >ls -l /etc/defaults/rc.conf >> >> I gather that you don't ever run mergemaster, which would update this file? >> My machine installed in 2001 has a Dec 2010 date for that file: >> >> -r--r--r-- 1 root wheel 36037 Dec 1 14:13 /etc/defaults/rc.conf > > Exactly that was my thought. Maybe a file that is NOT subject > to one of the system upgrade procedures would be better? Maybe > something in /boot? > > % ls -l /etc/defaults/rc.conf > -r--r--r-- 1 root wheel 34300 Aug 24 2008 /etc/defaults/rc.conf > % ls -l /boot/defaults/loader.conf > -r--r--r-- 1 root wheel 19426 Aug 24 2008 /boot/defaults/loader.conf > > No, forget about that, also nonsense, looks to new... How about /var/empty: % ls -ldo /var/empty/ dr-xr-xr-x 2 root wheel schg 512 Jul 18 19:16 /var/empty/ It can be changed, but doesn't look likely. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Date of a FreeBSD installation
Chip Camden writes: > Quoth Carl Johnson on Thursday, 13 January 2011: >> Polytropon writes: >> >> > On Thu, 13 Jan 2011 13:50:27 -0800, Chuck Swiger wrote: >> >> On Jan 13, 2011, at 1:46 PM, Devin Teske wrote: >> >> > This is nearly always accurate on any FreeBSD system (when wanting to >> >> > query the date the machine was built): >> >> > >> >> > ls -l /etc/defaults/rc.conf >> >> >> >> I gather that you don't ever run mergemaster, which would update this >> >> file? >> >> My machine installed in 2001 has a Dec 2010 date for that file: >> >> >> >> -r--r--r-- 1 root wheel 36037 Dec 1 14:13 /etc/defaults/rc.conf >> > >> > Exactly that was my thought. Maybe a file that is NOT subject >> > to one of the system upgrade procedures would be better? Maybe >> > something in /boot? >> > >> > % ls -l /etc/defaults/rc.conf >> > -r--r--r-- 1 root wheel 34300 Aug 24 2008 /etc/defaults/rc.conf >> > % ls -l /boot/defaults/loader.conf >> > -r--r--r-- 1 root wheel 19426 Aug 24 2008 /boot/defaults/loader.conf >> > >> > No, forget about that, also nonsense, looks to new... >> >> How about /var/empty: >> >> % ls -ldo /var/empty/ >> dr-xr-xr-x 2 root wheel schg 512 Jul 18 19:16 /var/empty/ >> >> It can be changed, but doesn't look likely. > > On my system, it gives a date several months in advance of my install > date (Nov 21 2009). Oops, you're right. I just checked and it is a few days before I actually installed mine, so that is probably when the ISO was built. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Date of a FreeBSD installation
> I'd suggest looking at the Btimes of top level directories > > stat -f "%SB %N" /* Or how about just / as this ~15 minutes earlier than most of the remaining top level directories sodserve# stat -f "%SB %N" /* Jan 9 04:54:21 2011 /COPYRIGHT Jan 9 04:54:21 2011 /bin Jan 9 04:54:21 2011 /boot Dec 31 18:59:59 1969 /dev Jan 9 04:54:21 2011 /etc Jan 9 04:54:21 2011 /lib Jan 9 04:54:21 2011 /libexec Jan 9 04:54:21 2011 /media Jan 9 04:54:21 2011 /mnt Jan 9 04:54:21 2011 /proc Jan 9 04:54:21 2011 /rescue Jan 9 04:54:21 2011 /root Jan 9 04:54:21 2011 /sbin Jan 9 04:54:21 2011 /sys Jan 9 04:48:39 2011 /tmp Jan 9 04:48:45 2011 /usr Jan 9 04:49:39 2011 /var sodserve# stat -f "%SB %N" / Jan 9 04:39:59 2011 / ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Simple command to reset / clear all logs?
Polytropon writes: > On Thu, 13 Jan 2011 20:11:03 -0600, Adam Vande More > wrote: >> Amusing, but you're the one full of shit. There's more things to automatic >> log file creation than are thought of in your imagination. > > Adam, > > I think Robert is right at least in regards of SOME > programs that use syslogd for logging OR do the > logging stuff on their own. I think that newsyslog will create the new log files if specified in the /etc/newsyslog.conf file. That might be the confusion about some log files being created automatically but others not. The newsyslog.conf(5) manpage mentions a 'C' flag that can be specified. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
