Re: won't boot after 8.0-RELEASE upgrade
As I guessed, I am using standard, not DD mode. Despite of this I was unable
to boot, and even more: FreeBSD 8.0 sysinstall did not find any partitions
neither on the (g)mirror, hardware RAID I described above or any individual
disks part of the RAID. I had to use FreeBSD 7.2 livefs to copy my data
after I formatted one of the disks with new 8.0 sysinstall.
I think this makes our problem totally unexplained.
As an example I'll show you my unable to boot system with gmirror fstab:
# DeviceMountpoint FStype Options Dump
Pass#
/dev/mirror/gm0s1b noneswapsw 0
0
/dev/mirror/gm0s1a / ufs rw 1
1
/dev/mirror/gm0s1d /usrufs rw 2
2
/dev/mirror/gm0s1e /varufs rw,acls 2
2
/dev/acd0 /cdrom cd9660 ro,noauto 0 0
Something I've noticed: when formatting an entire disk with sysinstall prior
7.0 its partition looks like this:
Offset Size(ST)End Name PType Desc Subtype
Flags
0 63 62- 12 unused0
63 781417602 781417664ad4s1 8freebsd 165
781417665 2990 781420654- 12 unused0
When formatted with later versions of sysinstall it looks like this:
Offset Size(ST)End Name PType Desc Subtype
Flags
0 63 62- 12 unused0
63 625142385 625142447ad4s1 8freebsd 165
I notice that the free part at the end is missing. My hardware raid,
described above in this thread, stores its metadata in the beginning of the
disk. Writes in the first sectors result in mirror break and the error I
wrote already. I know all of this because I did a lot of tests to help all
of you to find our problem out.
I have to say that my problems occured with system initially installed with
FreeBSD 5 or 6. One system with single drive installed with 7.2 (second
example) upgraded with no problems.
I hope my tests will help to find out what happens wit our older
disklabelled systems.
Polytropon wrote:
On Tue, 8 Dec 2009 14:09:16 -0800 (PST), Ivo Karabojkov i...@kit-bg.com
wrote:
So I'd like to know how
to distinguish mode of my current filesystems - is it standard or
dangerously dedicated?
If you've first created a slice on the disk, and then
partitions inside the slice, it's standard mode, e. g.
ad0 ab d e f g
{ [ (/) (swap) (/tmp) (/var) (/usr) (/home) ] }
s1
If you've omitted the slice, and created the partitions
on the disk device itself, it's dangerosly dedicated mode, e. g.
ad0
{ (/) (swap) (/tmp) (/var) (/usr) (/home) }
ab d e f g
You can tell by the existence of ad0s1[adefg] vs. ad0[adefg]
in /dev, or by trying to print the disks's slice table.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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
--
View this message in context:
http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26706523.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
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: Chomium on FreeBSD?
On Sun, Jun 28, 2009 at 11:47 PM, Daniel Underwood djuatde...@gmail.comwrote: Is there an effort to build a port of chromium for FreeBSD? I recently began using chromium on my Linux machine, and the HTML rendering speed is quite impressive. When it has the ability to synchronize bookmarks, I'll use it exclusively. I have been running it for weeks now. Google it, some guy compiled it and offers a package. regards, usleep ___ 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
Intel SRCZCR ?
Hello, At work we've a machine which is currently running FreeBSD 7.0 and we would like to upgrade to 7.2 This machine has an esoteric embedded RAID controller, the Intel SRCZCR RAID adapter. When I installed the machine one year ago I read the RELEASE Hardware Notes to check whether this chipset was supported or not. I didn't found any references, but I came across http://www.krellis.org/unix-stuff/srczcr-freebsd-howto.html and read that if was in fact supported by the iir(4) driver. Although I had a panic with the GENERIC kernel (see kern/122067), it works like a charm for more than one year now. Do you know if this card is still supported by the iir(4) driver (or other) in the 7.2-RELEASE ? Thanks, Julien (apologies for cross posting for those who're on freebsd-scsi) -- No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. ___ 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: Intel SRCZCR ?
Julien Cigar wrote: Hello, At work we've a machine which is currently running FreeBSD 7.0 and we would like to upgrade to 7.2 This machine has an esoteric embedded RAID controller, the Intel SRCZCR RAID adapter. When I installed the machine one year ago I read the RELEASE Hardware Notes to check whether this chipset was supported or not. I didn't found any references, but I came across http://www.krellis.org/unix-stuff/srczcr-freebsd-howto.html and read that if was in fact supported by the iir(4) driver. Although I had a panic with the GENERIC kernel (see kern/122067), it works like a charm for more than one year now. Do you know if this card is still supported by the iir(4) driver (or other) in the 7.2-RELEASE ? It is extremely unlikely that a single device support would have been removed within a single major branch like 7.x. It has never happened before. If it works for you in 7.0 it will continue to do so at least as good in 7.2. But there is a tiny possibility, with esoteric hardware, that a bug that was not fatal in a previous version becomes fatal in the new one. This is very rare but if you are very concerned you can check this by downloading a live cd (e.g. ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.2/7.2-RELEASE-i386-livefs.iso), booting it and testing a little. ___ 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
geometry does not match label (255h,63s != 16h,63s)
What are the meaning of the messages below when I boot 8.0-RELEASE-p1 and how can I prevent that? GEOM: ad6s1: geometry does not match label (255h,63s != 16h,63s). ... GEOM: ad6s2: geometry does not match label (255h,63s != 16h,63s). GEOM: ufsid/478e98a7fe5111d0: geometry does not match label (255h,63s != 16h,63s). GEOM: ufsid/479a0892240b3994: geometry does not match label (255h,63s != 16h,63s). # fdisk -s /dev/ad4: 484406 cyl 16 hd 63 sec PartStartSize Type Flags 1: 63 488281185 0xa5 0x80 # disklabel ad4s1 # /dev/ad4s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD 2048 16384 28552 b: 8388608 4194304 swap c: 4882811850unused0 0 # raw part, don't edit d: 41943040 125829124.2BSD 2048 16384 28552 e: 41943040 545259524.2BSD0 0 0 f: 67108864 964689924.2BSD 2048 16384 28552 g: 324703329 1635778564.2BSD0 0 0 -reg -- View this message in context: http://old.nabble.com/geometry-does-not-match-label-%28255h%2C63s-%21%3D-16h%2C63s%29-tp26710655p26710655.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: geometry does not match label (255h,63s != 16h,63s)
I see this too. I even went so far as to edit the labels and start again and then I got the opposite: geometry does not match label (16h,63s != 255h,63s) ..so I gave up. Google didnt turn anything up but I dont see this on FreeBSD 7.x at all. Only 8 So far, it has not been any issue from what I can tell and only apparent (for me) when gmirror is setup. -- J.D. Bronson Information Technology ___ 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
idled not disconnecting idle users on 7.2
I liked using idled on 4.11 to kick off idle users as it allowed me to specify which users can stay connected indefinitely, whereas sshd_config options ClientAliveCountMax 0 and ClientAliveInterval 60 would kick everyone off after an hour. I do have a couple of users that have a legitimate need to keep their SSH tunnel open as long as they need it. However, on 7.2 idled logs that it's disconnecting a user for idle, but it doesn't actually happen. Is there a kernel parameter or something other than idled that does the same thing (namely excluding users or groups from being idled disconnected)? Thanks! Scott___ 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: What is proper process for source installs?
On Tue, Dec 08, 2009 at 10:21:34PM -0600, Peter Steele thus spake: Ah, you _probably_ want to do 'make release' -- I have no experience with this however to be much more help if that _is_ what you need. Didn't know about that one. I'll have to check it out--thanks. I started out doing this a couple of months ago, and the project has been a wealth of experience and knowledge, to say the least. Once you are able to do manage building a release, you can actually build your own update server and distribute binary updates on your custom kernel. :) -jgh ___ 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: semi-problem starting sendmail
On Tue, 8 Dec 2009 18:25:43 -0500, Robert Huff roberth...@rcn.com wrote: I just generated new keys using the method specified the the article recommended by Giorgos, and I get the same result. Oops. I was hoping that would help, but it was only a wild guess by looking at the error message and the Google hits I could find for related threads. As Chuck wrote, the error is coming from the TLS support code. Can you try the openssl commands he mentioned? Date: Tue, 08 Dec 2009 23:33:07 +0200 From: Chuck Swiger cswi...@mac.com Subject: Re: semi-problem starting sendmail Message-id: d1adce71-7d5e-4e0d-ba3a-03b6e4af1...@mac.com Well, the error is coming from /usr/src/contrib/sendmail/src/tls.c, and depends on openssl to deal with your cert. Does: openssl verify -verbose /etc/mail/CA/private/cakey.pem ...say anything interesting? What about: openssl x509 -in /etc/mail/CA/private/cakey.pem -text ___ 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: geometry does not match label (255h,63s != 16h,63s)
Add my name to the list--we get tons of these messages since upgrading to 8.0 -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Bernt Hansson Sent: Wednesday, December 09, 2009 10:24 AM To: J.D. Bronson Cc: freebsd-questions@freebsd.org; regis505 Subject: Re: geometry does not match label (255h,63s != 16h,63s) J.D. Bronson: I see this too. I even went so far as to edit the labels and start again and then I got the opposite: I see that too on 8.0 geometry does not match label (16h,63s != 255h,63s) ..so I gave up. Google didnt turn anything up but I dont see this on FreeBSD 7.x at all. Only 8 Same here. So far, it has not been any issue from what I can tell and only apparent (for me) when gmirror is setup. I don't use gmirror or any sort of raid. GEOM: ad0s2: geometry does not match label (255h,63s != 16h,63s). GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s). ___ 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: What is proper process for source installs?
I started out doing this a couple of months ago, and the project has been a wealth of experience and knowledge, to say the least. Once you are able to do manage building a release, you can actually build your own update server and distribute binary updates on your custom kernel. Hmm, interesting. We'll have numerous customers in the field running our custom BSD image. We have a plan in place on how to distribute updates, but not through this concept of an update server. Might be worth checking it out. Thanks. ___ 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: geometry does not match label (255h,63s != 16h,63s)
What if we tried a custom kernel and removed these lines: options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization I think that might remove these 'errors'. -- J.D. Bronson Information Technology ___ 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: fixit and gmirror
On Tue, Dec 8, 2009 at 21:40, Tim Judd taj...@gmail.com wrote: Because the livefs uses a MFSROOT system (allows you to make changes to the ram-based disk image after boot), you have to load kernel modules before the mfsroot is mounted. As an example.. boot cd escape to loader prompt load /boot/kernel/geom_mirror.ko load /boot/kernel/smbfs.ko (if needed, i had to load two modules the time i had to use it) boot Thanks guys. Tim, that did the trick. I followed that sequence with the livefs cd, then did: # mount /dev/mirror/gm0s1a /temp/; mount /dev/mirror/gm0s1f /temp/tempusr/ and copied /temp/tempusr/boot to /temp/ (minus kernel.old so it would fit) and the system boots again. And I would like to note.. raid0 is striping, gstripe. raid1 is mirroring. I find it hard to recognize raid0 as your boot device. Right. It is raid1. Cheers, Joey ___ 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: geometry does not match label (255h,63s != 16h,63s)
Hi-- On Dec 9, 2009, at 10:44 AM, Peter Steele wrote: Add my name to the list--we get tons of these messages since upgrading to 8.0 This isn't new with 8.x; it's been around since 4.0, if not earlier. For a long time, BIOSes using the older C/H/S addressing mechanism were limited to ~8GB in size, and prior to LBA 48-bit addressing there was a ~130GB size limit. So long as the system is seeing the proper size of the drive, you can safely ignore the messages; if the drive size is not being detected properly, make sure your BIOS is updated, is set to look at drives using LBA mode (rather than C/H/S), and make sure the drive itself doesn't have a jumper limiting it to legacy addressing mode. Most of the time, you can safely ignore the message applies and one can ignore the rest the above. :-) Regards, -- -Chuck PS: Now, if 8.x is repeatedly logging these messages, that might be new behavior and worth adjusting. ___ 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
hplip 3.9.8 on fbsd 7.1 with HP LJ P2035
Hi, I can't seem to get it to probe the printer. hp-setup says: error: No devices found. error: Error occured during interactive mode. Exiting. dmesg|grep HP says: ugen0: Hewlett-Packard HP LaserJet P2035, class 0/0, rev 2.00/1.00, addr 2 on uhub0 The http://hplipopensource.com/hplip-web/models/laserjet/hp_laserjet_p2035.html page says a plugin is required, but no info on how to get that plugin. Help!! Thanks, Rich ___ 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: Dangerously Dedicated (was: How do I create large ...)
Date: Tue, 8 Dec 2009 22:00:29 +0100 From: Polytropon free...@edvax.de Subject: Re: How do I create large partitions in FreeBSD? To: krad kra...@googlemail.com Cc: Peter Steele pste...@maxiscale.com, freebsd-questions@freebsd.org freebsd-questions@freebsd.org Message-ID: 20091208220029.2052102f.free...@edvax.de Content-Type: text/plain; charset=US-ASCII On Tue, 8 Dec 2009 20:52:52 +, krad kra...@googlemail.com wrote: stay away from dangerously dedicated it seems as though they are being phased out I've followed the related discussion, but I'm not sure what to conclude from it... as far as I understood, creating an installation dangerously dedicated mode isn't possible from sysinstall anymore, but still possible via the command line tools. I don't see a reason why it is considered to be something bad, but the inclusion of a carrier slice for the OS's partitions has always been recommended. But for data disks where only one partition is intended, why create it inside a slice? I sort of followed the discussion as well. There was some disagreement about what dangreously dedicated means. Does it mean getting rid of the DOS partition table (slices?) Or, does it mean creating a slice or disks without BSD partitions? The Handbook (18.3) says: If the disk is going to be truly dedicated to FreeBSD, you can use the dedicated mode. Otherwise, FreeBSD will have to live within one of the PC BIOS partitions. FreeBSD calls the PC BIOS partitions slices so as not to confuse them with traditional BSD partitions. The programer in charge of the change seemed to indicate that the Dangerously dedicated mode (I assume that means no BSD partititons) conflicts with GEOM: Modular Disk Transformation Framework. GEOM appears to be an asbtraction layer for accessing various disks. With the move underway to start accessing all disk as SCSI(3 is device independent (with translation help)) devices, it probably makes for more elegant code. Handbook (19.2 GEOM Introduction) reads: GEOM permits access and control to classes -- Master Boot Records, BSD labels, etc -- through the use of providers, or the special files in /dev. Supporting various software RAID configurations, GEOM will transparently provide access to the operating system and operating system utilities. The important thing in that quote is that BSD labels (and Master Boot Records) are mentioned specificly. Regards, James Phillips __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. ___ 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: hplip 3.9.8 on fbsd 7.1 with HP LJ P2035
On Wed, 9 Dec 2009, Rich Winkel wrote: Hi, I can't seem to get it to probe the printer. hp-setup says: error: No devices found. error: Error occured during interactive mode. Exiting. Did you run hp-setup from the command line? The GUI has been broken for a long time. Can you find the printer from the CUPS control panel? Is it set as the default printer in CUPS? dmesg|grep HP says: ugen0: Hewlett-Packard HP LaserJet P2035, class 0/0, rev 2.00/1.00, addr 2 on uhub0 The http://hplipopensource.com/hplip-web/models/laserjet/hp_laserjet_p2035.html page says a plugin is required, but no info on how to get that plugin. Help!! Thanks, Rich ___ 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 -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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
Where is file channel_if.h
Hi All, I need to compile a sound driver which need the include file channel_if.h. This file seems to be part of FreeBSD kernel definition. The only file I can find is /usr/src/sys/dev/sound/pcm/channel_if.m. It is similar to a header file but it seems that it should be modified to have the C header file syntax. How to do this transformation ? Thanks for the help, Alain Aubord ___ 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
BIOS/FreeBSD? i7 laptop with constant fan and no c states on 8.0
I tried FreeBSD 8.0 on a Dell i7 laptop, but the fan is constantly spinning with maximal speed (and maximal noise). dev.cpu.0.cx_supported lists only C1. Maybe this is related to i386/135447 (but I am on 8.0/amd64 and not 7.2/i386). Even with powerd reducing the frequency to the lowest available, the fan still does not get quieter (it does on Windows 7). Is the BIOS doing something wrong or is it just FreeBSD not working with this fairly new processor, yet? Thanks, Jan Henrik ___ 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: geometry does not match label (255h,63s != 16h,63s)
J.D. Bronson wrote: What if we tried a custom kernel and removed these lines: options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization I think that might remove these 'errors'. My kernel already has these removed and yet I also only began getting these after upgrading from 7.2 to 8.0 on both servers at home. So far just ignored them. Normal csup source and make buildworld/etc dance followed with a portupgrade -af and make delete-old-libs. So, yes, another Me Too. :-) -Mike ___ 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: geometry does not match label (255h,63s != 16h,63s)
Well then so much for my idea of removing those options from the kernel. Darn. Well if they have 'been' there since earlier FreeBSD I wonder why we never saw them until 8.x now ? There must be some reason... They do not appear to be anything but cosmetic but still annoying and worrisome for people like us. I suppose the next thing would be to find the offending code and comment it out... :-) -- J.D. Bronson Information Technology Aurora Health Care - Milwaukee WI Office: 414.978.8282 // Fax: 414.978.3988 ___ 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: Dangerously Dedicated (was: How do I create large ...)
On Wed, 9 Dec 2009 11:42:31 -0800 (PST), James Phillips anti_spam...@yahoo.ca
wrote:
I sort of followed the discussion as well. There was some
disagreement about what dangreously dedicated means.
For comparison, I seem to remember that the two concepts
are called compatibility mode and (dangerously) dedicated
mode, with the dangerously looking like a further
addition.
Does it mean
getting rid of the DOS partition table (slices?)
The use of slices - DOS primary partitions has often been
suggested for FreeBSD, but it has always worked without them.
I think the neccessarity to use them is what I said before:
compatibility. FreeBSD can handle no slices well, but
maybe other operating systems and Windows can't?
A common problem is that due do compatibility (again),
the number of slices is limited to 4.
Or, does it mean
creating a slice or disks without BSD partitions?
How should this be possible? A partition (not a DOS primary
partition, to avoid misunderstandings) is required for
creating a file system. Let's say you want to create a
file system on a disk:
# newfs da0
This means that a partition is created - da0c - and inside
this partition the file system resides.
This is a common method for accessing data disks (disks
you don't boot from).
The Handbook (18.3)
says: If the disk is going to be truly dedicated to FreeBSD, you
can use the dedicated mode. Otherwise, FreeBSD will have to live
within one of the PC BIOS partitions. FreeBSD calls the PC BIOS
partitions slices so as not to confuse them with traditional BSD
partitions.
Exactly. No dangerously here.
The programer in charge of the change seemed to indicate that the
Dangerously dedicated mode (I assume that means no BSD partititons)
conflicts with GEOM: Modular Disk Transformation Framework.
No. It means absence of a slice carrying the partitions,
which is the dedicated approach.
GEOM
appears to be an asbtraction layer for accessing various disks. With
the move underway to start accessing all disk as SCSI(3 is device
independent (with translation help)) devices, it probably makes for
more elegant code. Handbook (19.2 GEOM Introduction) reads:
GEOM permits access and control to classes -- Master Boot Records,
BSD labels, etc -- through the use of providers, or the special files
in /dev. Supporting various software RAID configurations, GEOM will
transparently provide access to the operating system and operating
system utilities.
The important thing in that quote is that BSD labels (and Master
Boot Records) are mentioned specificly.
That's correct. BSD labels, usually created by disklabel,
refer to FreeBSD partitions. MBR refers to slices (this
is DOS primary partitions, and maybe includes logical
volumes inside a DOS extended partition, all the things
that produce drive letters).
The only thing I can conclude from this is that the removal
of dedicated mode is due to increasing compatibility with
the abilities of GEOM...
I've got lots of ? flying around my head... :-)
Allow me to try a summary:
Dedicated mode (also dangerously dedicated mode):
da0 da0a da0b da0d da0e da0f da0g
{(/)(swap) (/tmp) (/var) (/usr) (/home) }
Compatibility mode:
da0 da0s1 da0s1a da0s1b da0s1d da0s1e da0s1f da0s1g
{[ (/)(swap) (/tmp) (/var) (/usr) (/home) ] }
I'm not sure hgow this fits into the concept of installing
multiple operating systems. For example, Windows requires
you to install it in a slice. No problem with compatibility
mode, but does this work in dedicated mode, too? I think the
suggestion is No, does not work simply because the disk is
DEDICATED to FreeBSD.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: named needs restart after a reboot
On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wbl...@wonkity.com wrote: On Tue, 8 Dec 2009, Derrick Ryalls wrote: uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO amd64 I have most things working, but I have noticed that every time I reboot the machine, I need to manually restart named to get it listening on the proper interfaces as by default it is listening on 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it which seems like it would be configured correctly, but I have had to do this on a install before. Anyone have a guess as to what could be wrong? Only a guess: network interface comes up too late. If you're using DHCP to configure that interface, you could try SYNCDHCP. Or if it's an re(4) interface, there are patches in 8-STABLE that make it come up faster. -Warren Block * Rapid City, South Dakota USA ifconfig_nfe0=SYNCDHCP Was the fix, thanks! ___ 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
HP USB 2.0 Tape Drive
Hi, I'm looking to buy a tape drive and am currently looking at USB 2.0 DAT tape drives from HP. I searched the hardware compatibility list and cannot locate any information tape drives except the disclaimer that SCSI tape drives do work on SCSI controller cards that are recognized by the FreeBSD OS. The only thing I can find is that apparently the ehci driver must be used if USB 2.0 interface is to be used with a tape drive. Does anyone have had positive or negative experience using these USB-based DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) StorageWorks Q1581SB DAT 160 Tape Drive. If there are other branded USB 2.0-based tape drives (i.e. Quantum) that you've used with little or no problems, I would be interested in knowing about these. ~Doug ___ 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: HP USB 2.0 Tape Drive
Hi Doug, Does anyone have had positive or negative experience using these USB-based DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) I know that I am not really answering your question but here are a couple of thoughts that came to my mind when reading your post: - USB 2 should be able to sustain the transfer speed to stream your DAT drive, I checked that point; - I always considered DAT one of the worse tape solution myself, too sensitive to the physical conditions, too prone to errors, could never read a tape after 6 months; - why spending money in a 80GB tape drive when you can have 10TB of hard disk for the same price; I beleive you have a bunch of existing tapes that hold data you must read. Then I would plug my USB DAT to any operating system that supports it, transfer the data to some hard disc, and be done with the tapes. And if FreeBSD cannot use the tape drive, as it is a one time task only, I would go for some other OS. Good luck, Olivier ___ 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: Temporarily halt boot process to enter encryption keys?
Corey J. Bukolt wrote: Hello list, I have a FreeNAS box with a CF card for root, and 3 drives (soon to be 4) set up with encryption and raidz on top of them. A less than excellent detailed report of what I did is here: http://bit.ly/5BeZq8 This setup is a bit hackish as after the system boots I need to attach each drive using geli, run zpool import -f primary, and then restart all my services (nfs, samba, etc). It's become a bit of a chore (especially when doing it all from a N810), so I'm looking for a way to temporary halt the boot process so that I can ssh in, attach the drives, and then allow the system to continue to boot. A few ideas come to mind, such as meddling with rc scripts, but I'd like to get some suggestions from the more experienced FreeBSD hackers before I go off breaking my system. Thanks, ~Corey ___ 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 Anybody at all? ___ 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: HP USB 2.0 Tape Drive
Hi Doug, Does anyone have had positive or negative experience using these USB-based DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) I know that I am not really answering your question but here are a couple of thoughts that came to my mind when reading your post: - USB 2 should be able to sustain the transfer speed to stream your DAT drive, I checked that point; - I always considered DAT one of the worse tape solution myself, too sensitive to the physical conditions, too prone to errors, could never read a tape after 6 months; Interesting points you raise. I have owned several DAT drives (Quantum, Sony, and HP) over the past 17 years and have yet to lose ability to restore data due to bad tapes. I am careful where I store these between use. I use these with SCSI interfaces on Windows systems with one exception- I use a SCSI-based Sony DDS DAT 12/24 tape drive in a FBSD system running PGSQL. All I just want to know is whether FBSD will recognize and work with the tape drive I posed in my previous email (the Hewlett-Packard StorageWorks Q1581SB DAT 160 Tape Drive). Will it be identified as /dev/da* something? Can any one of you confirm if you got any USB 2.0 tape drive to work with FBSD? I like the fact that I can just plug a USB tape drive into a new system in seconds without having to fuss about installing a SCSI/SAS card and have a tape back up made relatively soon. As a side note: I had trouble getting certain branded USB external hard drives recognized by FreeBSD. I ended up using LaCie hard drives as these were listed as being compatible. Thus I am cautious about anything that uses USB in general with FreeBSD. I just got off the phone with a Quantum technical staffer and he was stymied by my question whether their USB 2.0 DAT 160 tape drive would be recognized by FBSD. He pushed me off to a sales representative who is just got off for the day. ~Doug ___ 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: Dangerously Dedicated (was: How do I create large ...)
On Wed, 9 Dec 2009 11:42:31 -0800 (PST) James Phillips anti_spam...@yahoo.ca wrote: I sort of followed the discussion as well. There was some disagreement about what dangreously dedicated means. Does it mean getting rid of the DOS partition table (slices?) Or, does it mean creating a slice or disks without BSD partitions? It means the former. ___ 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: Dangerously Dedicated
RW wrote: On Wed, 9 Dec 2009 11:42:31 -0800 (PST) James Phillips anti_spam...@yahoo.ca wrote: I sort of followed the discussion as well. There was some disagreement about what dangreously dedicated means. Does it mean getting rid of the DOS partition table (slices?) Or, does it mean creating a slice or disks without BSD partitions? It means the former. ___ 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 As far as I understand it, it's called Dangerously Dedicated because it may cause other systems not to recognise the disk. Consequently, newfs'ing a slice without first partitioning it can hardly be DD, since that is what other systems do, 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: geometry does not match label (255h,63s != 16h,63s)
On Wed, 09 Dec 2009 10:59:51 -0800 Chuck Swiger cswi...@mac.com wrote: Hi-- On Dec 9, 2009, at 10:44 AM, Peter Steele wrote: Add my name to the list--we get tons of these messages since upgrading to 8.0 This isn't new with 8.x; it's been around since 4.0, if not earlier. Something has changed though because I saw this for a data drive that been around for a long time and 7.x never complained. ___ 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: Dangerously Dedicated
On Wed, Dec 9, 2009 at 8:33 PM, Rolf Nielsen listrea...@lazlarlyricon.com wrote: RW wrote: On Wed, 9 Dec 2009 11:42:31 -0800 (PST) James Phillips anti_spam...@yahoo.ca wrote: I sort of followed the discussion as well. There was some disagreement about what dangreously dedicated means. Does it mean getting rid of the DOS partition table (slices?) Or, does it mean creating a slice or disks without BSD partitions? It means the former. As far as I understand it, it's called Dangerously Dedicated because it may cause other systems not to recognise the disk. Consequently, newfs'ing a slice without first partitioning it can hardly be DD, since that is what other systems do, right? That is correct. That slice will not be bootable, but you can use it to store data. - Max ___ 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: geometry does not match label (255h,63s != 16h,63s)
On Thu, 10 Dec 2009 01:36:53 + RW rwmailli...@googlemail.com wrote: On Wed, 09 Dec 2009 10:59:51 -0800 Chuck Swiger cswi...@mac.com wrote: Hi-- On Dec 9, 2009, at 10:44 AM, Peter Steele wrote: Add my name to the list--we get tons of these messages since upgrading to 8.0 This isn't new with 8.x; it's been around since 4.0, if not earlier. Something has changed though because I saw this for a data drive that been around for a long time and 7.x never complained. The message was added around this time last year: http://lists.freebsd.org/pipermail/svn-src-head/2008-December/002175.html -- Bruce Cran ___ 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: HP USB 2.0 Tape Drive
On Wed, 9 Dec 2009 17:09:05 -0800 , Doug Sampson do...@dawnsign.com wrote: All I just want to know is whether FBSD will recognize and work with the tape drive I posed in my previous email (the Hewlett-Packard StorageWorks Q1581SB DAT 160 Tape Drive). Will it be identified as /dev/da* something? I would guess it will identify as /dev/sa* (da = direct access, sa = sequential access), at least SCSI tape drives occur in that manner. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Dangerously Dedicated
On Thu, 10 Dec 2009 02:33:17 +0100, Rolf Nielsen listrea...@lazlarlyricon.com
wrote:
As far as I understand it, it's called Dangerously Dedicated because it
may cause other systems not to recognise the disk.
Primarily, it's called dedicated (only) because it describes
a setting where a whole hard disk is dedicated to the FreeBSD
operating system. The addition dangerously seems to describe
the danger that other operating systems cannot handle such a
disk layout, or may cause problems to them - but I don't know
this for sure because I'm not a multi-booter. :-)
Consequently,
newfs'ing a slice without first partitioning it can hardly be DD, since
that is what other systems do, right?
If you run newfs inside a slice, you would create a partition
covering the whole slice, and so it's still compatibility mode
(the opposite of DD mode); DD mode implies the absence of a
slice at all.
da0 da0s1 da0s1c
{[ (/) ] }
Other systems operate on slice level, on a DOS primary partition,
where they create their file systems in a certain way, e. g.
an msdos file system. In such a case, there are no partitions
inside the slice because partitions are specific to operating
systems like FreeBSD.
da0 da0s1da0s2da0s3 da0s3a
{[ C: ] [ D: ] [ (/) ] }
msdosfs msdosfs ufs
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: Dangerously Dedicated
On Wed, 9 Dec 2009 20:41:40 -0500, Maxim Khitrov mkhit...@gmail.com wrote:
On Wed, Dec 9, 2009 at 8:33 PM, Rolf Nielsen
listrea...@lazlarlyricon.com wrote:
As far as I understand it, it's called Dangerously Dedicated because it may
cause other systems not to recognise the disk. Consequently, newfs'ing a
slice without first partitioning it can hardly be DD, since that is what
other systems do, right?
That is correct. That slice will not be bootable, but you can use it
to store data.
Being bootable is a matter of what the MBR boot block
says. In a DD setting, it refers to the first partition
(that's not within a slice), e. g. ad0a. Especially in
a multi-OS setting, the use of slices seems to be
strongly recommended so all operating systems behave
in the required way (due to compatibility reasons,
see DOS primary partitions), which limits the number
of slices to 4.
For plain storage, it's not needed to encapsulate the
partition with the file system inside a slice, e. g.
ad1 ad1s1 ad1s1e
{[ (/data) ] }
in comparison to
ad1 ad1c
{(/data) }
And as it is known, the c can be omitted, as in
# mount /dev/ad1 /data
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: Temporarily halt boot process to enter encryption keys?
Corey, Umm...write a script perhaps? Nobody else has taken a shot at this one yet, so I'll try. This is just what I'd do. That said, it's probably not the best solution. It's an idea. You may have to work out some bugs along the way. In regards to interrupting the boot process, I don't think this is what you're after, unless you have console access. In which case you'd use geli to set the boot flag on your providers. The boot process will stop, ask for a password and then continue. The problem is that this occurs before daemons like sshd are started; Unless you have console access, you're screwed. Thus, your problem... You want the system to boot as usual, it's just you don't want it to start any third party daemons such as samba ...yet! (This is why runlevels on SysV style startups are useful. It would be a matter of switching to a custom runlevel.) You would first disable the various daemons by not having them in your 'rc.conf' file. You'd then write a wrapper script, in your language of choice. The wrapper simply calls the various '/usr/local/etc/rc.d' scripts to start all of your third party daemons as usual. ...and whatever else you need to do. Remember to pass the 'onestart' argument, because the rc scripts are no longer listed in /etc/rc.conf. With all that in place you'd ssh in and execute the wrapper as the root user. (root) engage Poof done. You can put the wrapper script anywhere you want. Name it anything you like. Just make sure it's executable by the root user. (Thus be careful when writing it!) An example of a python wrapper might look something like the one below. Change to fit your needs, obviously. Admittedly it's not he most pythonic code ever written. It also probably has bugs to work out, but again, it's an idea. #!/usr/local/bin/python Wrapper which executes a bunch of files. import os import sys import subprocess as sp # Change this to suit your needs: SCRIPTS_TO_CALL = [ '/usr/local/etc/rc.d/apache22', '/usr/local/etc/rc.d/samba', '/etc/rc.d/ntpd' ] if os.geteuid() != 0: sys.stderr.write(This script must be executed as the root user. Aborting.\n) for script in SCRIPTS_TO_CALL: if os.path.exists(script): command = script + onestart p = sp.Popen(command, shell=True, stdout=sp.PIPE, stderr=sp.PIPE) # Now write out any errors/output to their usual places: sys.stdout.write(p.stdout.read()+\n) sys.stderr.write(p.stderr.read()+\n) else: sys.stderr.write(File, '%s' does not exist. Skipping...\n % script) Hacky, perhaps buggy, but perhaps useful. Unless anyone has a better idea? With a little more refinement you could probably even convert your FreeBSD box into a sysV equivalent, making complex custom startups easier in the future. Blasphemy, I know! -Modulok- On 12/9/09, Corey J. Bukolt 0...@mail.ru wrote: Corey J. Bukolt wrote: Hello list, I have a FreeNAS box with a CF card for root, and 3 drives (soon to be 4) set up with encryption and raidz on top of them. A less than excellent detailed report of what I did is here: http://bit.ly/5BeZq8 This setup is a bit hackish as after the system boots I need to attach each drive using geli, run zpool import -f primary, and then restart all my services (nfs, samba, etc). It's become a bit of a chore (especially when doing it all from a N810), so I'm looking for a way to temporary halt the boot process so that I can ssh in, attach the drives, and then allow the system to continue to boot. A few ideas come to mind, such as meddling with rc scripts, but I'd like to get some suggestions from the more experienced FreeBSD hackers before I go off breaking my system. Thanks, ~Corey ___ 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 Anybody at all? ___ 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: named needs restart after a reboot
On Wed, Dec 9, 2009 at 3:39 PM, Derrick Ryalls ryal...@gmail.com wrote: On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wbl...@wonkity.com wrote: On Tue, 8 Dec 2009, Derrick Ryalls wrote: uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO amd64 I have most things working, but I have noticed that every time I reboot the machine, I need to manually restart named to get it listening on the proper interfaces as by default it is listening on 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it which seems like it would be configured correctly, but I have had to do this on a install before. Anyone have a guess as to what could be wrong? Only a guess: network interface comes up too late. If you're using DHCP to configure that interface, you could try SYNCDHCP. Or if it's an re(4) interface, there are patches in 8-STABLE that make it come up faster. -Warren Block * Rapid City, South Dakota USA ifconfig_nfe0=SYNCDHCP Was the fix, thanks! Spoke too soon. On one reboot, the interface couldn't talk to DHCP until I set it down then back up. I have gone to statically setting the IP. Not ideal, but seems to be working (based on one clean reboot). ___ 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: Temporarily halt boot process to enter encryption keys?
Modulok wrote: Corey, Umm...write a script perhaps? Nobody else has taken a shot at this one yet, so I'll try. This is just what I'd do. That said, it's probably not the best solution. It's an idea. You may have to work out some bugs along the way. In regards to interrupting the boot process, I don't think this is what you're after, unless you have console access. In which case you'd use geli to set the boot flag on your providers. The boot process will stop, ask for a password and then continue. The problem is that this occurs before daemons like sshd are started; Unless you have console access, you're screwed. Thus, your problem... Exactly. You want the system to boot as usual, it's just you don't want it to start any third party daemons such as samba ...yet! (This is why runlevels on SysV style startups are useful. It would be a matter of switching to a custom runlevel.) You would first disable the various daemons by not having them in your 'rc.conf' file. You'd then write a wrapper script, in your language of choice. The wrapper simply calls the various '/usr/local/etc/rc.d' scripts to start all of your third party daemons as usual. ...and whatever else you need to do. Remember to pass the 'onestart' argument, because the rc scripts are no longer listed in /etc/rc.conf. With all that in place you'd ssh in and execute the wrapper as the root user. (root) engage Poof done. You can put the wrapper script anywhere you want. Name it anything you like. Just make sure it's executable by the root user. (Thus be careful when writing it!) An example of a python wrapper might look something like the one below. Change to fit your needs, obviously. Admittedly it's not he most pythonic code ever written. It also probably has bugs to work out, but again, it's an idea. #!/usr/local/bin/python Wrapper which executes a bunch of files. import os import sys import subprocess as sp # Change this to suit your needs: SCRIPTS_TO_CALL = [ '/usr/local/etc/rc.d/apache22', '/usr/local/etc/rc.d/samba', '/etc/rc.d/ntpd' ] if os.geteuid() != 0: sys.stderr.write(This script must be executed as the root user. Aborting.\n) for script in SCRIPTS_TO_CALL: if os.path.exists(script): command = script + onestart p = sp.Popen(command, shell=True, stdout=sp.PIPE, stderr=sp.PIPE) # Now write out any errors/output to their usual places: sys.stdout.write(p.stdout.read()+\n) sys.stderr.write(p.stderr.read()+\n) else: sys.stderr.write(File, '%s' does not exist. Skipping...\n % script) Hacky, perhaps buggy, but perhaps useful. Unless anyone has a better idea? With a little more refinement you could probably even convert your FreeBSD box into a sysV equivalent, making complex custom startups easier in the future. Blasphemy, I know! -Modulok- Oooo.Not a bad idea at all. It might be even simpler just to disable the services in rc.conf, then use a simple shell script with something like: #!/bin/sh /etc/rc.d/nfsd start /etc/rc.d/samba start .etc Then all that would have to be done is boot the system, ssh in, attach the drives using geli, then run engage.sh (or whatever). Thank you very much for the idea. :) ~Corey ___ 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
mountroot prompt after hint.apic.0.disabled=1
Don't know if that loader.conf change affected this server, I disabled APIC in loader.conf after finding it may be responsible for a slow clock on this VMware guest FreeBSD install. I rebooted for the changes to take affect and it goes now to a mountroot prompt, can't seem to load the root partition. I type ? at the prompt and it does not list anything after 'List of GEOM managed disk devices'. Can anyone suggest how I can fix this problem? Thanks, Robert ___ 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
ipfilter nat redirect udp packets
Have this nat rule rdr rl0 0.0.0.0/0 port 6355 - 10.0.10.3 port 6355 I can see in the log that tcp packets are being redirected but udp packets are not. Can not find any verbiage in man 5 0r 8 ipnat that states rdr rule only matches on tcp packets. I thought tcp/udp packets should be redirected? Can anyone clarify this? ___ 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
make delete-old question
Hi, Successfully upgraded from 7.2 to 8.0 but had my usual problem when jumping major versions with the make delete-old target. The problem being that it asks me to confirm deletion of each lib/file with a y and a return. I've found that I never say n to any deletion and it becomes very tedious to hammer at the keyboard for hundreds of libs/files. Is there a way to change the Makefile so that they all get deleted with just one y and a return? Or possibly use yes(1) to script it? TIA. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ 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: make delete-old question
Frank Shute wrote: Hi, Successfully upgraded from 7.2 to 8.0 but had my usual problem when jumping major versions with the make delete-old target. The problem being that it asks me to confirm deletion of each lib/file with a y and a return. I've found that I never say n to any deletion and it becomes very tedious to hammer at the keyboard for hundreds of libs/files. Is there a way to change the Makefile so that they all get deleted with just one y and a return? Or possibly use yes(1) to script it? TIA. Regards, yes | make delete-old ___ 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: make delete-old question
Is there a way to change the Makefile so that they all get deleted with just one y and a return? Or possibly use yes(1) to script it? I often yes | make delete-old Olivier ___ 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
