Re: Upgrading boot from GPT(BIOS) to GPT(UEFI)

[Warren Block]

On Fri, 16 Dec 2016, Eric van Gyzen wrote:


On 12/16/2016 11:39, Slawa Olhovchenkov wrote:

On Fri, Dec 16, 2016 at 06:08:34PM +0100, Fernando Herrero Carrón wrote:


Hi everyone,

A few months ago I got myself a new box and I have been happily running
FreeBSD on it ever since. I noticed that the boot was not as fast as I had
expected and I've realized that, while my disk is GPT partitioned, the boot
process is still BIOS based:

% gpart show
=>   34  976773101  ada0  GPT  (466G)
 34  6- free -  (3.0K)
 40   1024 1  freebsd-boot  (512K)
   1064984- free -  (492K)
   2048   67108864 2  freebsd-swap  (32G)
   67110912  909662208 3  freebsd-zfs  (434G)
  976773120 15- free -  (7.5K)

I am reading uefi(8) and it looks like FreeBSD 11 should be able to boot
using UEFI straight into ZFS, so I am thinking of converting that
freebsd-boot partition to an EFI partition, creating a FAT filesystem and
copying /boot/boot.efi there.

How good of an idea is that? Would it really be that simple or am I missing
something? My only reason for wanting to boot with UEFI is faster boot,
everything is working fine otherwise.

Thanks in advance for your help.


I am also interesting by this case.
I think expand freebsd-boot to about 1M (size of /boot/boot1.efifat),
dding /boot/boot1.efifat and set to type to 'efi' may be enough. I am
never tried this.


I expect that would work.  It's slightly risky, though, since it doesn't let you
fall back to BIOS boot if EFI doesn't work.


The fallback in that case would just be changing that partition back to 
freebsd-boot and rewriting the bootcode to it.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Upgrading boot from GPT(BIOS) to GPT(UEFI)

[Warren Block]

On Fri, 16 Dec 2016, Eric van Gyzen wrote:


On 12/16/2016 11:08, Fernando Herrero Carrón wrote:

Hi everyone,

A few months ago I got myself a new box and I have been happily running
FreeBSD on it ever since. I noticed that the boot was not as fast as I had
expected and I've realized that, while my disk is GPT partitioned, the boot
process is still BIOS based:

% gpart show
=>   34  976773101  ada0  GPT  (466G)
 34  6- free -  (3.0K)
 40   1024 1  freebsd-boot  (512K)
   1064984- free -  (492K)
   2048   67108864 2  freebsd-swap  (32G)
   67110912  909662208 3  freebsd-zfs  (434G)
  976773120 15- free -  (7.5K)

I am reading uefi(8) and it looks like FreeBSD 11 should be able to boot
using UEFI straight into ZFS, so I am thinking of converting that
freebsd-boot partition to an EFI partition, creating a FAT filesystem and
copying /boot/boot.efi there.

How good of an idea is that? Would it really be that simple or am I missing
something? My only reason for wanting to boot with UEFI is faster boot,
everything is working fine otherwise.


I would recommend creating another partition for EFI instead of replacing your
freebsd-boot partition, in order to have a working fallback in case EFI boot
doesn't work.  You would need to steal some space from your swap partition.


Be aware that some newer Dells really don't like to have both and will 
refuse to boot in either mode with such a setup.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Clandestine USB SD card slot

[Warren Block]

On Sun, 16 Oct 2016, George Mitchell wrote:


So not only is it (apparently) recognized, but the sdhci_pci driver
attached to it!  But inserting or removing a card shows no activity.
What's my next step?  -- George


Is a device created for the empty reader?  It's worth trying to force a 
retaste of that device with 'true > /dev/daX' after the card is 
inserted.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: omitting make installkernel in an upgarde between 2 x 10-stable

[Warren Block]

On Sun, 4 Sep 2016, Matt Smith wrote:


On Sep 04 16:35, Julian H. Stacey wrote:

Hi, Reference:

From:   "Julian H. Stacey" 
Date:   Sun, 04 Sep 2016 13:37:26 +0200


"Julian H. Stacey" wrote:

Hi stable@ people
In a jail,  uname -r 10.3-RELEASE-p4, I started
cd /usr/src ; make buildworld,
then realised per
  https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
I will not be able to
make installkernel ; reboot
preceeding
make installworld
Am I on route to shooting myself in the foot ?


It survived. No shot foot :-)


Just to let you know. I have done this for years on versions 4 through to 10 
and never had a single problem. Only on minor version upgrades though from 
say 10.2 to 10.3. My procedure is:


make -j4 buildworld && make -j4 buildkernel
make installkernel
make installworld
mergemaster
shutdown -r now
make delete-old
make delete-old-libs

I do this because I don't have a keyboard or monitor on the machine during 
normal use. This has *always* worked fine. However for a major version 
upgrade from say 10.x to 11.x I have always done it the correct and proper 
way using single user mode via the console.


Can't recall the last time I did single user. It might have been more 
than a decade now.  Here is what I do:

http://www.wonkity.com/~wblock/docs/html/buildworld.html

(And no, "kernel" is not a mistake.)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vt(4) issues on 11.0-BETA3 (Actually 11-STABLE)

[Warren Block]

On Thu, 4 Aug 2016, Kevin Oberman wrote:


3. After one port erred on the build, I scrolled back to select the list of
ports still to be built (a portmaster(8) feature) and try to paste it into
the same window or a different one. I get a totally different region. Since
the list spanned several lines due to line wrap, I got a bunch of other
lines, no doubt from some other part of the buffer. I have a hunch that
this is tied to the fact that a great many lines of output get wrapped into
multiple lines on the display and the arithmetic of what is selected goes
awry. (Just a guess, though.)


Yes.  I submitted a patch to have portmaster save the output also to a 
file in /tmp because of this.  It's not in the latest port, I think. 
I'd attach it, but it's on a machine that is under some books and a 
failed hard drive awaiting shipment.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Release notes and handbook changes for identifying wireless adapters

[Warren Block]

On Mon, 1 Aug 2016, Shawn Webb wrote:


The discussion on this is too late for code changes to 11.0-RELEASE, but this 
should be documented loud and clear.


The difficulty here is that now we have to document different methods 
for different versions, which makes it harder for new users *and* the 
people trying to document it.  Too bad net.wlan.devices doesn't exist on 
10.X.  Maybe it could.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

[Warren Block]

Introduction

   The first quarter of 2016 showed that FreeBSD retains a strong sense of
   ipseity. Improvements were pervasive, lending credence to the concept
   of meliorism.

   Panegyrics are relatively scarce, but not for lack of need. Perhaps
   this missive might serve that function in some infinitesimal way.

   There was propagation, reformation, randomization, accumulation,
   emulation, transmogrification, debuggenation, and metaphrasal during
   this quarter.

   In the financioartistic arena, pork snout futures narrowly edged out
   pointilism, while parietal art remained fixed.

   In all, a discomfiture of abundance. View the rubrics below, and marvel
   at their profusion and magnitude! Marvel!

   --Warren Block
 __

   Please submit status reports for the second quarter of 2016 by July 7.
   A thesaurus will be provided for submitters who do not have one of
   their own. We will need them back afterwards, preferably with no new
   teeth marks on the covers. Thank you!
 __

FreeBSD Team Reports

 * Cluster Admin
 * The FreeBSD Core Team

Projects

 * Address Space Layout Randomization
 * Ceph on FreeBSD
 * Process-Shared Locks for libthr
 * RCTL Disk IO Limits
 * The Graphics Stack on FreeBSD

Kernel

 * ARM Allwinner SoC Support
 * CAM I/O Scheduler
 * FDT Overlay Support in UBLDR
 * Filemon Performance/Stability Improvements
 * FreeBSD Integration Services (BIS)
 * Infiniband
 * MMC Stack Under CAM Framework
 * NFS Server
 * Static Analysis of the FreeBSD Kernel with PVS Studio

Architectures

 * AmigaOne X5000 Support
 * FreeBSD on Cavium ThunderX (arm64)
 * powerpcspe Target

Userland Programs

 * ELF Tool Chain Tools
 * Native PCI-express HotPlug
 * Updates to GDB
 * Using lld, the LLVM Linker, to Link FreeBSD

Ports

 * GitLab Port
 * GNOME on FreeBSD
 * KDE on FreeBSD
 * Obsoleting Rails 3
 * Ports Collection

Documentation

 * New FreeBSD Mastery Books
 * Spanish FAQ and Chinese Porter's Handbook Translations

Miscellaneous

 * FreeBSD Build
 * Qt 5.6 on Raspberry Pi
 * The FreeBSD Foundation
 __

FreeBSD Team Reports

Cluster Admin

   Contact: <cluster...@freebsd.org>

   This quarter, we:
 * migrated services out of the hosting space in ISC (peter, sbruno)
 * began migration of services into the RootBSD hosting space (peter,
   sbruno)
 * collaborated with the phabricator admin team to migrate to a new
   and improved host in NYI. (allanjude, peter, sbruno)
 * installed a new and beefier Jenkins machine (gnn, lwshu, sbruno)
 * are still looking for more Asian mirrors for pkg, svn, and ftp
   (Japan, India). (sbruno)
 * completed the migration of the Taiwanese mirror to its new
   location. (lwshu)
 * started hosting a clang/llvm buildbbot in the FreeBSD cluster at
   NYI (sbruno, emaste)
 * resolved a UK mirror outage with Bytemark (gavin, peter)
 __

The FreeBSD Core Team

   Contact: FreeBSD Core Team <c...@freebsd.org>

   During the first quarter of 2016, the most important business of the
   FreeBSD Core Team has been to respond to the harassment incident last
   year. Core's actions were to assemble a timeline of the events and in
   the light of that to review Core's actions at the time; and to make
   recommendations about how better to handle such cases in future. During
   this process, draft reports were reviewed by people concerned in the
   case and in addition a number of interested members of the FreeBSD
   community. Core would like to thank everyone involved for their
   contributions.

   The report was published to the FreeBSD developer community in
   mid-February, and contained six recommendations for the community to
   consider.

   Core is also coordinating with the committee headed by Anne Dickison
   who are reviewing the Code of Conduct. A corpus of case studies is
   being assembled, which will be re-examined to see what impact changes
   to the Code of Conduct would have had.

   Core, together with John Baldwin, are working on a plan to create a
   separate repository containing GPLv3 toolchain components. This will
   allow modernization of code within base beyond what the existing GPLv2
   toolchain can handle, and permit support of certain new architectures
   where a copyfree licensed alternative (i.e., LLVM) is not yet
   available. A position paper will soon be circulated to developers for
   comment.

   During this quarter three new commit bits were issued, and one was
   returned for safekeeping. Please welcome Wojciech Macek, Jared McNeil
   and Stanislav Galabov, and 

Re: A gpart(8) mystery on 10.3-RELEASE

[Warren Block]

On Tue, 5 Apr 2016, Steven Hartland wrote:

On 05/04/2016 20:48, Warren Block wrote:


Actually, the more I think about it, using bootcode -p to write the entire 
EFI partition seems dangerous.  Unless it is surprisingly smart, it will 
wipe out any existing stuff on that EFI partition, which could be any 
number of important things put there by other utilities or operating 
systems, including device drivers.


The safer way is to mount that partition and copy the boot1.efi file to it.



Pretty sure that's not done as you cant guarantee fat support is available.


In the kernel, you mean?  True.  But odds are good that someone with a 
custom kernel without msdosfs will understand the implications of 
overwriting the EFI partition.


And of course it is safe to create an EFI partition, it would only be a 
problem if one already existed with some extra files on it.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: A gpart(8) mystery on 10.3-RELEASE

[Warren Block]

On Tue, 5 Apr 2016, Boris Samorodov wrote:


05.04.16 12:30, Trond Endrestøl пишет:


What am I doing wrong? Can't gpart(8) write both the pmbr and the efi
image as a single command? Is it an off-by-one error in gpart(8)?

gpart bootcode -b /boot/pmbr -p /boot/boot1.efifat -i 1 ada0
gpart: /boot/boot1.efifat: file too big (524288 limit)


Do you try to get only UEFI boot? Then do not use "-b" option. It is
needed for BIOS boot.

Do you need to get a system with both UEFI and BIOS boot? Then use two
different partitions for UEFI and BIOS booting schemes.


gpart bootcode -b /boot/pmbr ada0
bootcode written to ada0


This is needed only for BIOS boot and together with "-p /boot/gptboot"
option.


Well... bootcode -b only writes to the PMBR and does not take a 
partition number with -i.  So the short form version I use could be 
refused by a very strict option parser, requiring two separate steps:


  gpart bootcode -b /boot/pmbr ada0
  gpart bootcode -p /boot/gptboot -i1 ada0

The way it parses options when working on EFI partitions might be more 
strict.


Actually, the more I think about it, using bootcode -p to write the 
entire EFI partition seems dangerous.  Unless it is surprisingly smart, 
it will wipe out any existing stuff on that EFI partition, which could 
be any number of important things put there by other utilities or 
operating systems, including device drivers.


The safer way is to mount that partition and copy the boot1.efi file to 
it.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Swap Questions

[Warren Block]

On Fri, 14 Aug 2015, Tim Daneliuk wrote:


I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that has
512M of memory and 1G of swap partition.  I am seeing a ton of errors like
this:

Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(10): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(14): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(11): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(6): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(7): failed
Aug 14 00:01:22 myhost last message repeated 2 times


So, I added this to fstab (after creating /usr/swap0):

md99noneswapsw,file=/usr/swap0  0   0

And then did this:

swapon -aq


But, when I do a swapinfo, all I can see is the disk swap partition
that comes standard with the VPS:


Device  1K-blocks UsedAvail Capacity
/dev/gpt/swapfs   1048576   456572   59200444%


Add the -L (late) option to swapon.  How this works might differ between 
10-Release, 10-Stable, and 11.


Incidentally, md99 does not have to be literal, it's just meant to get 
the md device number up out of the way of common interactive usage of 
mdconfig.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: gptboot: unable to read backup GPT header - virtualbox guest with SAS controller

[Warren Block]

On Mon, 22 Jun 2015, Paul Koch wrote:


We get the following error after installing 10.1-p12 in a VirtualBox guest
when setup with an emulated LSI / SAS controller and a 50G fixed sized
virtual disk:

gptboot: error 1 lba 104857599
gptboot: unable to read backup GPT header

Can't seem to find anyone who has this same issue.

The problem does not exist if we configure the guest with a SATA controller
and same size virtual disk.


...


The guest boots fine, but we always get the gptboot error.

Is this just a problem with the virtualbox SAS controller emulation where
gptboot can't retrieve the backup table ?


That would be my first guess: an off-by-one error preventing the last 
block from being read.  It's not clear which emulated controller was 
being used for the diskinfo output posted earlier.  If it really was an 
off-by-one bug, the block count would differ depending on the 
controller.


However, some controllers keep metadata on the drive, and report a 
reduced capacity, and that would have almost the same effect.  Seems 
like there would be a complaint by the controller firmware about the 
contents of the metadata block, but maybe not by an emulated controller. 
If controller metadata is the problem, installing FreeBSD using the 
emulated controller in place should make sure the backup GPT is in the 
correct position, rather than switching to the SCSI controller after 
installing with, say, SATA.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Kernel fails to boot after update

[Warren Block]

On Mon, 25 May 2015, Brandon Wandersee wrote:


On 05/25, Trevor Roydhouse wrote:


https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html

Cheers,
TREV.



Thanks for the link, Trevor. I enabled DDB in the kernel (options DDB) in
order to prevent the reboot and learned that the VirtualBox kernel module was
causing the hold-up (I use VirtualBox very often, so I load the module at
start-up). I'd forgotten to *rebuild the module after updating the kernel.* I
feel foolish for having forgotten that---I've been using VirtualBox for
years---but all is well now. Thanks for the pointers, and sorry for cluttering
the list with such an inane issue. The quote in my signature seems fitting in
this case.  Anyway, take care, all.


This bit me also.  I usually do not rebuild port kernel modules until 
after a reboot in the new system, and this is the first time that there 
was a problem with that.  A boot from mfsBSD and temporarily commenting 
out vboxdrv_load=YES in /boot/loader.conf was the workaround.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.2-PRE: switch off that stupid Nakatomi Socrates

[Warren Block]

On Sat, 28 Sep 2013, Ben Morrow wrote:


Quoth David Demelier demelier.da...@gmail.com:


I personally think (but you may totally disagree with) that an operating
system *is* an operating system. And I really hate easter eggs or
anything else not serious being integrated into the system. I think
about a new user installing FreeBSD 9.2, I would not imagine his
reaction front of this kind of tribute or whatever you call that. For
me it stands for that's not serious, it looks like a toy.


Personally I thoroughly approve of a joke every now and then, as long as
it doesn't get out of hand.


The problem with humor is that it's subjective.  Think of a joke that 
lots of people found funny, but you did not.  Now put that same joke 
somewhere you will be forced to see it and be reminded of it often.


After a short time, it's not just unfunny, it's irritating.  Or, as 
someone once put it, there's a fine line between clever and stupid.


So this kind of thing should be easily disabled.  There should also be 
some warning, so when people see a vastly different boot screen, their 
first thought is not was I hacked?.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Update to 9.2-PRERELEASE, what is this?

[Warren Block]

On Tue, 20 Aug 2013, J David wrote:


On Sun, Aug 18, 2013 at 3:43 PM, Warren Block wbl...@wonkity.com wrote:

On Sun, 18 Aug 2013, David Demelier wrote:

http://files.malikania.fr/DSC_0223.jpg

What's that? Is this a joke?


Yes, sort of.


This is fantastic.  Kudos and thanks for the laugh to whoever snuck it in there.


After you're tired of it, override it in /boot/loader.conf: loader_logo=orb
A PR should probably be entered to correct /boot/defaults/loader.conf.


What do we set as loader_logo to change it back once this has been
fixed?  This probably isn't really orbbw, but it needs to stick around
as an easter egg for the life of 9.2.


The /boot/defaults/loader.conf entry is just a comment that lists the 
options, but does not list the new option.  Looking at 
/boot/beastie.4th, the new one is tribute and tributebw.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Update to 9.2-PRERELEASE, what is this?

[Warren Block]

On Sun, 18 Aug 2013, David Demelier wrote:


Hi,

After updating to r25, I have a strange boot loader, see:

http://files.malikania.fr/DSC_0223.jpg

What's that? Is this a joke?


Yes, sort of.  After you're tired of it, override it in 
/boot/loader.conf: loader_logo=orb


A PR should probably be entered to correct /boot/defaults/loader.conf.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FBSD 9.2 RC crashes running as virtualbox host

[Warren Block]

On Sat, 17 Aug 2013, Kevin Oberman wrote:


I built my new kernel and installed it, then rebooted before rebuilding
virtualbox-ose-kmod. Then I rebooted once again (which I think I forgot to
do the first time).  Then I started my VM and it was fine. There are three
kernel modules and I find it easier to reboot than to unload and reload all
three. I've also sometimes had odd behavior and the occasional panic when
unloading and reloading kernel modules. I am now running r254456 and all is
well.


That could be why I've had no problems.  I generally only have vboxdrv 
loaded.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FBSD 9.2 RC crashes running as virtualbox host

[Warren Block]

On Fri, 16 Aug 2013, Thomas Zenker wrote:


On 08/16/13 15:41, Mikhail Tsatsenko wrote:

2013/8/16 Thomas Zenker t...@zenker.tk:

Hi,

after updating my freebsd amd64 box from 9.1 (r250841) to 9.2-RC
(r254276) virtualbox crashes the machine. Seconds after starting VBOX

After starting VBOX gui or guest machine? If first, try to rebuild
userland portion of vbox too.


After starting a virtual guest machine in the GUI or directly from cli
leads to the crash. The userland has been rebuild w/ 9.2 also. The same
binaries of the userland portion built with 9.2 work w/o problems in 9.1.


Updated to 9.2-PRERELEASE #0 r254408 amd64 today, rebuilt and reloaded 
the VirtualBox kernel module, and just started a couple of guests from 
the GUI with no problems.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FreeBSD 9.1 won't boot with a graid error

[Warren Block]

On Thu, 1 Aug 2013, F. Senault wrote:


Hi everybody.

I've just upgraded a box from FreeBSD 9 to 9.1 via freebsd-update.

At the first reboot, the machine stopped with messages about GRAID :

GEOM_RAID: Promise: Subdisk kjihgfedcba`_^]\[ZYXWVUTSRQPONM:0-ada0 state
changed from NONE to ACTIVE

The trick is that I've never setup any kind of RAID on that old box...

Is there a way to completely disable GEOM_RAID loading on boot ?


Boot into the loader (option 2 at boot menu).  Enter:

  set kern.geom.raid.enable=0
  boot

That should allow it to boot, and can be added to /boot/loader.conf. 
I'm not sure of an easy way to clear the metadata for a permanent fix.


Apparently some manufacturers use motherboard RAID to test drives, so 
the metadata may have been on the drive from the factory.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Booting FreeBSD with Syslinux

[Warren Block]

On Thu, 1 Aug 2013, Daniel O'Connor wrote:



On 01/08/2013, at 9:04, dte...@freebsd.org wrote:

Have you tried mboot?


No I have not.

Do you know anyone that has got it to work?



Supposedly someone got it to work because there is an entry in the syslinux wiki
http://www.syslinux.org/wiki/index.php/Mboot.c32#FreeBSD_example


I'm following the threads on both lists, and that example looks more 
like a generic template than an actual, working command. 
kernel_option, for example.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Trouble building release with docs

[Warren Block]

On Sun, 21 Jul 2013, Glen Barber wrote:


On Sun, Jul 21, 2013 at 05:19:23PM +0930, Daniel O'Connor wrote:


On 21/07/2013, at 16:19, Glen Barber g...@freebsd.org wrote:


On Sat, Jul 20, 2013 at 04:44:56PM +0930, Daniel O'Connor wrote:

Hi,
I am trying to do a full (customised) release of 9.1 but I am
having trouble building the docs. If I use NODOC it builds fine,
but without that I get..


[...]

May I ask why 9.1?



Actually that's an excellent question :)

I though 9.1 was coming out not 9.2 but that is not correct.

So, if I rebuild with 9.2 checked out will the docs build?



Yes.


Depending on the use, just downloading the built documents from 
ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/ could be more 
effective.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Trouble building release with docs

[Warren Block]

On Sat, 20 Jul 2013, Daniel O'Connor wrote:


Hi,
I am trying to do a full (customised) release of 9.1 but I am having trouble 
building the docs. If I use NODOC it builds fine, but without that I get..
[andenes 7:04] /usr/src/release #/usr/bin/time make release BUILDNAME=$BUILDNAME
make -C /usr/src/release  BUILDNAME=9.1-GENESIS obj
make -C /usr/src/release  BUILDNAME=9.1-GENESIS ftp cdrom memstick
cd /usr/src/release/doc  make all install clean 'FORMATS=html txt'  
INSTALL_COMPRESSED='' URLS_ABSOLUTE=YES DOCDIR=/usr/obj/usr/src/release/rdoc
=== en_US.ISO8859-1 (all)
=== en_US.ISO8859-1/relnotes (all)
/usr/bin/grep '^?xml version=.*?' article.xml  article.parsed.xml.tmp
grep: article.xml: No such file or directory
*** [article.parsed.xml] Error code 2

Stop in /usr/src/release/doc/en_US.ISO8859-1/relnotes.
*** [all] Error code 1

Stop in /usr/src/release/doc/en_US.ISO8859-1.
*** [all] Error code 1

Stop in /usr/src/release/doc.
*** [reldoc] Error code 1

Stop in /usr/src/release.
*** [release] Error code 1

Stop in /usr/src/release.
   0.48 real 0.37 user 0.10 sys

There is article.sgml though.. I have installed textproc/docproj and I can 
build /usr/docs fine.


What does svn say about that file?

  % cd /usr/src/release/doc/en_US.ISO8859-1/relnotes/
  % svn stat

The article.sgml suggests a leftover file from an earlier /usr/src that 
was not removed before svn checkout.  That does not explain why 
article.xml is missing, though.  It is present on my 9-stable and 
8-stable checkouts.  Maybe a mixed or partial checkout?

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: experience with 9.2-PRERELEASE

[Warren Block]

On Wed, 17 Jul 2013, John Reynolds wrote:

The final blow to my sanity was when I rolled back and tried to install 
8.4-RELEASE and sysinstall couldn't make the disk devices after I hit 'W' in 
the disk label editor to commit my changes.


Somewhere, there is a FAQ or note that you should not press W in the 
installer.  But a quick check did not find where that was.


So, I'm wondering generically are people having problems with SSD's in 
FreeBSD? In this hardware I have not tried using a traditional SATA 
disk yet.


I use SSDs without problems on 9.2-STABLE amd64, but all on motherboard 
controllers.  The problems you're seeing sound like a controller 
problem.  For reference:

http://www.wonkity.com/~wblock/docs/html/ssd.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Where's the docs for FreeBSD maintenance with Subversion?

[Warren Block]

On Thu, 4 Jul 2013, N.J. Mann wrote:


In message b8cefc405bcd2f7248f4c260a9148296.authentica...@ultimatedns.net,
Chris H (bsd-li...@1command.com) wrote:

Greetings,
 I've _finally_ managed to get a break in my work schedule that coincides with
a period where pointyhat isn't barfing on my ARCH. So I was able to (cv)sup src 
 ports.
Update the kernel successfully, and (after hours of work), managed to upgrade 
ports. But
as (cv)sup was discontinued ~3 months ago, the ports aren't well synced, and 
I'm now
working on a fairly wobbly system. I'm on RELENG_8 (8.4), and would like to sync my src 

ports via the (now defacto) subversion method. My previous experience is with 
the client
meerly for the sake of obtaining the src, and building -- _not_ maintaining a 
tree. I've
read what little is available in the handbook, and much of the Subversion book. 
But there are
clearly different procedures/nuances where FreeBSD maintenance is concerned, 
both in the
building of Subversion, and it's usage, where FreeBSD is concerned. The biggest 
questions
in this regard, is;
1) what to do with my current INDEX-8  INDEX-8.db files?
2) what of the distfiles directory
Do I simply copy them over, and check them in?


When I converted from csup to svn I did the following - which seems to
work. :-)

1. mv /usr/ports /usr/ports.old
2. mkdir /usr/ports
3. svn checkout into /usr/ports
4. mv /usr/ports.old/distfiles /usr/ports

When I do a svn update it ignores distfiles.


The index files, too.  They can be (slowly) built with 'make index', or 
downloaded with 'make fetchindex', or portmaster will fetch it 
automatically.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

[Warren Block]

On Thu, 27 Jun 2013, Garrett Wollman wrote:


Having just gone through this in two different environments, I can
very very strongly recommend doing the following.  It's not the easy
button of the TV commercials, but it will make things much much
easier in the future.


This is an interesting procedure and should be made into a 
web-accessible document!  Setting up a build machine for a network is a 
fairly common desire, and your procedure looks to be doing everything 
the newest way.



Then look through the output of pkg query to identify the leaf
packages that are the ones you actually wanted explicitly to have
installed.


On a single machine, this can be approximated with portmaster's 
--list-origins option.  It gives a list of root and leaf ports which 
can be edited to just the desired ones.  Feed that list to portmaster on 
a system with no ports installed, and it will install the leaf ports and 
dependencies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

[Warren Block]

On Thu, 27 Jun 2013, Garrett Wollman wrote:


In article alpine.bsf.2.00.1306270602300.99...@wonkity.com,
wbl...@wonkity.com writes:

On Thu, 27 Jun 2013, Garrett Wollman wrote:


Having just gone through this in two different environments, I can
very very strongly recommend doing the following.  It's not the easy
button of the TV commercials, but it will make things much much
easier in the future.


This is an interesting procedure and should be made into a
web-accessible document!  Setting up a build machine for a network is a
fairly common desire, and your procedure looks to be doing everything
the newest way.


See
http://people.freebsd.org/~wollman/converting-to-pkg-repository.html.


Bookmarked--that could make a nice addition to one of the official docs, 
maybe the Handbook.  Thank you!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

[Warren Block]

On Wed, 26 Jun 2013, Jeremy Chadwick wrote:


When rebuilding everything, I have always resorted to this:

rsync -avH /usr/local/ /usr/local.old/
pkg_delete -a -f
rm -fr /usr/local/*
rm -fr /var/db/ports/*
rm -fr /usr/ports/distfiles/*
cd /usr/ports/whatever
make install clean
{lather rinse repeat until done}


I don't generally rebuild from scratch, but there is a procedure at the 
end of the portmaster man page for doing it.


Something that should be mentioned: if you are not deleting and 
reinstalling everything, always--yes, always--check the new entries in 
/usr/ports/UPDATING first.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

[Warren Block]

On Wed, 26 Jun 2013, Chris H wrote:


But it installed (pulled in) far more than those dependencies actually required.


It may bring in build dependencies, but should be no different than 
manually installing ports.



I believe, due to the fact that it doesn't appear to honor the original build
options recorded in /var/db/ports/portname/options. Nor, do I recall that it
honored /etc/make.conf -- make.conf(5). Maybe things have changed?


Both portupgrade and portmaster did and do honor these.  Both are 
automated versions of installing the ports manually.  That can be 
overridden with mis-recommended BATCH variable.  Don't do that.


I don't see it. Oh, and should it not have been clear; I _do_ 
anticipate the upgrade to re-build most everything, as that is why 
I'm trying to find a mass upgrader port, to do the dirty work. 
Also should it not have been clear in the beginning; I am _not_ doing 
anything more than upgrading everything _within_ my current version; 
eg; no major point upgrade, or anything.


Okay, look up the last time you installed or upgraded a port:
% ls -ltr /var/db/pkg

The last one is the most recently modified.  Update your ports tree, 
follow all the steps that apply to your system since that date.  If any 
ports are left to upgrade at the end, use either port upgrade program 
with -a.


I recommend portmaster.  It does almost everything portupgrade does, but 
without the overhead of Ruby or bdb.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

[Warren Block]

On Wed, 26 Jun 2013, Chris H wrote:

On Wed, 26 Jun 2013, Chris H wrote:

Okay, look up the last time you installed or upgraded a port:
% ls -ltr /var/db/pkg

The last one is the most recently modified.  Update your ports tree,
follow all the steps that apply to your system since that date.


That should say all the steps in /usr/ports/UPDATING that apply to your 
system since that date.



I recommend portmaster.  It does almost everything portupgrade does, but
without the overhead of Ruby or bdb.

Greetings Warren, and thank you for your reply.

Sounds like the plan. I'll take your advice, and run with it.
Gave me just the confidence I needed. :)


Good!  Please post if you have any problems.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: system sporadically hangs on shutdown after switching to WITH_NEW_XORG

[Warren Block]

On Sun, 16 Jun 2013, Ian Lepore wrote:


On Sun, 2013-06-16 at 09:07 -0700, Jeremy Chadwick wrote:

On Sun, Jun 16, 2013 at 06:01:49PM +0200, Michiel Boland wrote:

On 06/16/2013 17:55, Jeremy Chadwick wrote:
[...]


Are you running moused(8)?  Actually, I can see quite clearly that you
are in your core.txt:

Starting ums0 moused.

Try turning that off.  Don't ask me how, because devd(8) / devd.conf(5)
might be involved.



The moused is started by devd - I don't see a quick way of turning that off.


Comment out the relevant crap in devd.conf(5).  Search for ums
and comment out the two notify sections.


I don't understand why people treat devd as if it's some sort of evil
virus that they're forced to live with (using phrases like crap in
devd.conf).  In general, the standard devd rules tend to fall into 3
categories:
 * use logger(1) to record some anomaly
 * kldload a module
 * invoke a standard /etc/rc.d script

For moused, the devd rules invoke /etc/rc.d/moused, which implies that
setting moused_enable=NO in rc.conf would be all that's needed to
disable it.


Seems that way, but it's misleading.  Plug in a USB mouse, and devd will 
start moused anyway (with different options, but still...).  ISTR that 
can be disabled with


  moused_enable=NO
  moused_nondefault_enable=NO

I have not tested that lately.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Serial terminal issues

[Warren Block]

On Wed, 5 Jun 2013, Dimitry Andric wrote:


On Jun 4, 2013, at 23:32, Alban Hertroys haram...@gmail.com wrote:

I can't seem to get my serial terminal to work with my new system.

...

cat /boot.config

-D -S19200


cat /boot/loader.conf

boot_multicons=YES
boot_serial=YES
comconsole_speed=19200
console=comconsole,vidconsole


Does it work at 9600 baud?  Otherwise, check RTS/CTS, etc.


Also, check that the ten-pin header is on in the right orientation, not 
180 degrees around.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Corrupt GPT header on disk from twa array - fixable?

[Warren Block]

On Sun, 2 Jun 2013, Alban Hertroys wrote:


On Jun 2, 2013, at 16:12, Kimmo Paasiala kpaas...@gmail.com wrote:


Looking at the gpart(8) output it seems that only 20GBs of the disk is
recognized by the disk driver but the GPT table still shows the full
capacity 910GB. I'd say that the GPT table is in fact correct and if
you can somehow get the disks to be recognized with full capacity they
should be usable as they are. What does dmesg(8) say about the disks?


From dmesg:

ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored)
ST3500418AS CC34 ATA-8 SATA 2.x device
usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
USB_ERR_IOERROR
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: ST3500418AS CC34 ATA-8 SATA 2.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad10
ada4 at ahcich4 bus 0 scbus4 target 0 lun 0
ada4: Hitachi HDS721010CLA332 JP4OA39C ATA-8 SATA 2.x device
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored)
ada4: 300.000MB/s transfers (SATA 2.x, usbd_setup_device_desc: getting device 
descriptor at addr 2 failed, USB_ERR_IOERROR
UDMA6, PIO 8192bytes)
ada4: Command Queueing enabled
ada4: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada4: Previously was known as ad12
ada5 at ahcich5 bus 0 scbus5 target 0 lun 0
ada5: WDC WD1002FAEX-00Z3A0 05.01D05 ATA-8 SATA 3.x device
ada5: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada5: Command Queueing enabled
ada5: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada5: Previously was known as ad14
SMP: AP CPU #1 Launched!
Timecounter TSC-low frequency 13371081 Hz quality 800
GEOM: ada2: the secondary GPT header is not in the last LBA.
GEOM: ada3: the secondary GPT header is not in the last LBA.
GEOM_MIRROR: Device mirror/boot launched (2/2).
GEOM_MIRROR: Device mirror/swap launched (2/2).
GEOM_MIRROR: Device mirror/root launched (2/2).
GEOM: ada4: the secondary GPT header is not in the last LBA.
GEOM: ada5: the secondary GPT header is not in the last LBA.


There is a lot of stuff going on there.

You switched from a hardware RAID card to something else in the new 
machine.  Maybe a different card, or maybe just the motherboard.  The 
old controller may have put metadata on the drives and hidden it.  On a 
new controller, that metadata is not hidden.  This would explain the 
secondary GPT header is not in the last LBA message.


If the old controller split the combined drives into virtual volumes, 
there may be another GPT somewhere in the remainder of the drive.  If 
you could find that, gnop(8) could be used with an offset to mount it. 
This could be another explanation for the GPT being corrupt: the GPT 
at the start of the drive is for the first volume, the backup GPT at the 
end of the drive is for the second volume.


Finally, GPT and gmirror are combined.  That's a problematic 
combination because both want metadata in the last block of the drive. 
The new section in the Handbook about RAID1 (gmirror) describes that in 
the Metadata Issues section:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/GEOM-mirror.html

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Corrupt GPT header on disk from twa array - fixable?

[Warren Block]

On Sun, 2 Jun 2013, Alban Hertroys wrote:

On Jun 2, 2013, at 16:46, Warren Block wbl...@wonkity.com wrote:
I've never worked with gnop before; is this a safe approach?:

# kldload geom_nop
# gnop create -v -o 41943006 -S 512 ada4
# mount /dev/ada4.nop /mnt

I get the impression that gnop might be non-destructive, but that's not 
entirely clear from the man page.


Well, yes, but mount it read-only.  gnop is (yet another) GEOM 
transform.  It should be non-destructive as long as you don't write to 
it.



I tried the above on ada5 (the other half of the mirror that I applied gpart 
recover to earlier), but it spews:

gnop: Invalid offset for provider ada5.

What number does it expect for that offset?


The trick would be figuring out what number was used by the RAID 
controller.


And what exactly is gpart show showing? I was under the assumption 
that both would be sectors (which judging from the numbers would be 
512 bytes in size).


Yes, it's sectors--the last column is human-readable.  But the GEOM 
logical device might be constructed from the GPT parameters.  It may not 
see the additional blocks on the physical device until the GPT tables 
are repaired.  Which might corrupt the actual data.


Really, the easiest way would be to temporarily install the old RAID 
controller and copy the data off the array.


Finally, GPT and gmirror are combined.  That's a problematic 
combination because both want metadata in the last block of the 
drive. The new section in the Handbook about RAID1 (gmirror) 
describes that in the Metadata Issues section: 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/GEOM-mirror.html


I'm pretty sure the disks on the controller had nothing to do with gmirror ever.

Gmirror is only applied to a pair of new disks that I put in the (new) 
server to be able to copy my data over. I hadn't expected to be able 
to rely on those original disks to be readable at all without the 
controller, so I needed some place to store the data. I like the 
redundancy of a mirror, so I used gmirror for (only) the new disks.


gmirror is good.  GPT is also good.  The combination is a problem. 
gmirror metadata overwrites the backup GPT, so those disks will show 
corrupt also.  For now, the recommended workaround is to just use MBR, 
which doesn't have any metadata at the end of the disk.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Corrupt GPT header on disk from twa array - fixable?

[Warren Block]

On Mon, 3 Jun 2013, Dmitry Morozovsky wrote:


On Sun, 2 Jun 2013, Warren Block wrote:

[snip]


gmirror is good.  GPT is also good.  The combination is a problem. gmirror
metadata overwrites the backup GPT, so those disks will show corrupt also.
For now, the recommended workaround is to just use MBR, which doesn't have any
metadata at the end of the disk.


... or gmirror not whole disks, but GPT partitions (as OP does, as far as I can
tell from gmirror dmesg reports)


That works, but if there is more than one partition per disk, rebuilds 
fight with each other for the heads.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Corrupt GPT header on disk from twa array - fixable?

[Warren Block]

On Mon, 3 Jun 2013, Alban Hertroys wrote:


Really, the easiest way would be to temporarily install the old RAID controller 
and copy the data off the array.


Well, that would mean I'd have to assemble the old server again, as 
the controller is not compatible with the hardware in the new one. And 
that would probably be unnecessary as well, since I already did copy 
the data off those disks.


I was just curious whether it would be possible to read that data off 
the disks while I still have them (with their original contents) in 
the new server in the eventuality that I _did_ forget to copy 
something over or that something wasn't copied over correctly.


I copied the data over a 100MBit ethernet link, which was the fastest 
option I had with the old server; it had USB1 and no native SATA. 
Hence the RAID controller, but that was on a now deprecated PCI-X 
channel (those 64-bit parallel things) and all 4 ports were in use. 
Not to mention that the CPU was so old that it had a rather narrow 
margin for operating temperatures and overheated several times during 
the copying process, because rsync+sshd put a relatively high load on 
the CPU (An old Athlon XP 2000+).


PCI-X cards will operate in PCI slots.  Or at least some will; I've done 
that with an Intel network card.  The motherboard can't have components 
that block the unused part of the edge connector, or the offending card 
edge could be removed with extreme prejudice.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Command line not responding

[Warren Block]

On Fri, 17 May 2013, Michael Gass wrote:


On Fri, May 17, 2013 at 11:55:13AM -0700, Jeremy Chadwick wrote:

On Fri, May 17, 2013 at 12:56:53PM -0500, Michael Gass wrote:

Running 9.0-Stable on an i386.

Whenever I type a command at the prompt I get
the output

/usr/local/lib/libintl.so.9: Undefined symbol _ThreadRuneLocale

and nothing else - the command will not run. Just the
above output.  Commands like ls and exit work, but not much
else.  This happends whether I am logged in a user or as root.
Cannot even halt the system from the command line.

Started to happen after trying to update the freetype2 port.
Got an error msg while updating libXft-2.1.14.  From that point
on I cannot use  the command line.

I have no idea what to try.  Any suggestions.






First provide the contents of /etc/make.conf and /etc/src.conf.



Thanks for getting back to me. Here are the contents of the two
files.  I rebuilt the kernel last fall and have updated ports
fairly regularly since. Things have worked fine until today when
I tried to update ports.

# File: make.conf
# The ? in the below is for buildworld
CPUTYPE?=pentium2
# Uncomment the below for general builds.
CFLAGS= -O -pipe
# Uncomment the below for kernel builds.
# COPTFLAGS= -O -pipe


It is almost always a mistake to set CFLAGS in make.conf.  Not only does 
it not improve performance, it frequently causes problems.  It will 
sometimes decrease performance for ports that can safely use custom 
CFLAGS themselves, because it prevents them from using those custom 
flags.


In other words, custom CFLAGS provide few or zero improvements, and have 
a significant risk of causing problems.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Release ISO images have broken RockRidge data

[Warren Block]

On Wed, 10 Apr 2013, Eugene Grosbein wrote:


09.04.2013 21:58, Mark Saad ?:


While not the same you can always do this

mdconfig -a -t vnode -f yourfreebsd-version.iso

mount -t cd9660 /dev/md0 /cdrom

Then use pax, cpio , cp, rsync etc to copy the data off the image .


This way breaks hardlinks, so /rescue expands to 690M instead of 5M.


rsync will support hard links with -H.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Release ISO images have broken RockRidge data

[Warren Block]

On Wed, 10 Apr 2013, Thomas Schmitt wrote:


Hi,

Warren Block wrote:

sync will support hard links with -H


But how shall rsync know that the files in the ISO image stem from
hardlink siblings on the hard disk where the image was produced ?


Well, no it won't recreate them by inferral.  Although that would be 
kind of a neat option for rsync, which can already deal with checksums. 
But when copying files, it does support hard links.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: What is the Right Way(™) to run X?

[Warren Block]

On Sun, 17 Mar 2013, Matthew D. Fuller wrote:


On Sun, Mar 17, 2013 at 10:37:08PM +1030 I heard the voice of
Daniel O'Connor, and lo! it spake thus:

Hi,
I recently updated my 9.1-PRE system's ports and my previous X
config now results in no mouse (but the keyboard does work).

I found that I needed to add the following..
Section ServerFlags
Option  AllowEmptyInput False
EndSection


I think general wisdom is that AEI is a Bad Idea for various reasons
that I don't remember, but seemed reasonable when I read them.

However, some time back, X _did_ start being all stupid about finding
the mouse for me.  Un/re-plugging it (USB) after starting X made it
show up working, but that's annoying and stupid (and not an option on
other systems with e.g. PS/2 meece).  I wound up sticking the other
half of that oft-cargo-culted incantation:

Section ServerFlags
   Option AutoAddDevices off
EndSection

in my config, and it's worked OK since.  's probably worth a try...


Both options were used to tell X not to use hal for input device 
detection.  AEI was misused for that, but kind of worked while causing 
other problems.


Turning off AutoAddDevices is the good way that does not cause other 
problems.


Even better is just to deinstall hal.  I believe it is still required by 
Gnome and KDE, but xfce runs fine without it.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: svn - but smaller?

[Warren Block]

On Tue, 12 Mar 2013, John Mehr wrote:

On Tue, 12 Mar 2013 02:20:37 +0100
 Michael Ross g...@ross.cx wrote:


What'd you think about a syntax extension along the lines of

svnup --bsd-base
svnup --bsd-ports
svnup --bsd-all

with automagic host selection, default to uname's major version stable 
branch and default target dirs?


Hello,

This sounds good to me, and as long as there's some sort of a consensus that 
we're not breaking the principle of least surprise, I'm all for it.  The one 
default that may be unexpected is the defaulting to the stable branch -- 
people who track the security branches will be left out.  So maybe something 
like:


svnup --ports
svnup --stable
svnup --security (or --release)


How would you select the mirror?  There are two now, and likely more 
later.___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Spontaneous reboots on Intel i5 and FreeBSD 9.0

[Warren Block]

On Fri, 25 Jan 2013, Andriy Gapon wrote:


on 25/01/2013 12:26 Marin Atanasov Nikolov said the following:

Yes, it's a brand new one.


Then no: http://en.wikipedia.org/wiki/Bathtub_curve


But if a new (as in replacement) power supply does not change the 
symptoms, it's likely not the problem.


The last post of that forum thread says there was corruption in the ZFS 
filesystem.

http://forums.freebsd.org/showthread.php?t=9143

That is also a very old thread, so details might not apply any more. 
But a successful scrub would show both that the filesystem is okay and 
that ZFS can complete a scrub.  (If that's been mentioned already, never 
mind.)

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: RFC: Suggesting ZFS best practices in FreeBSD

[Warren Block]

On Thu, 24 Jan 2013, Jeremy Chadwick wrote:


#1.  Map the physical drive slots to how they show up in FBSD so if a
disk is removed and the machine is rebooted all the disks after that
removed one do not have an 'off by one error'.  i.e. if you have
ada0-ada14 and remove ada8 then reboot - normally FBSD skips that
missing ada8 drive and the next drive (that used to be ada9) is now
called ada8 and so on...


How do you do that?  If I'm in that situation, I think I could find the
bad drive, or at least the good ones, with diskinfo and the drive serial
number.  One suggestion I saw somewhere was to use disk serial numbers
for label values.


The term FreeBSD uses for this is called wiring down or wired down,
and is documented in CAM(4).  It's come up repeatedly over the years but
for whatever reason people overlook it or can't find it.


I was aware of it, it just seems like there ought to be a better way to 
identify drives than by messing with the hardware configuration. 
Something more elegant, less tied to changing the hardware configuration 
of the host.  Assigning the drive serial number as a label, for example.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: RFC: Suggesting ZFS best practices in FreeBSD

[Warren Block]

On Fri, 25 Jan 2013, Jeremy Chadwick wrote:


On Fri, Jan 25, 2013 at 12:58:15PM -0700, Warren Block wrote:

On Thu, 24 Jan 2013, Jeremy Chadwick wrote:


#1.  Map the physical drive slots to how they show up in FBSD so if a
disk is removed and the machine is rebooted all the disks after that
removed one do not have an 'off by one error'.  i.e. if you have
ada0-ada14 and remove ada8 then reboot - normally FBSD skips that
missing ada8 drive and the next drive (that used to be ada9) is now
called ada8 and so on...


How do you do that?  If I'm in that situation, I think I could find the
bad drive, or at least the good ones, with diskinfo and the drive serial
number.  One suggestion I saw somewhere was to use disk serial numbers
for label values.


The term FreeBSD uses for this is called wiring down or wired down,
and is documented in CAM(4).  It's come up repeatedly over the years but
for whatever reason people overlook it or can't find it.


I was aware of it, it just seems like there ought to be a better way
to identify drives than by messing with the hardware configuration.


I understand what you mean, but it's actually messing with a software
configuration (specifically CAM).

It's a one-time change that solves the dilemma; it only has to be
adjusted if you change controller brands or models, which is a lot less
often than changing disks.


Something more elegant, less tied to changing the hardware
configuration of the host.  Assigning the drive serial number as a
label, for example.


Hmm...  all this does is change the nature of the problem, no?  You
still have the issue of having to know some magical number to
determine out what path name refers to what physical disk in your system.
Can you expand on how this would solve it?


It's not so much a solution as in the right domain.  The point, as I see 
it, is being able to identify individual disks uniquely.  Forcing static 
devices names does that, sort of.  But plug a different disk into the 
same port as an existing one, and that disk is now identified as the old 
one.


Using a unique identifier already built into those drives helps. 
Serial numbers are unique, built into the drive, and even printed on the 
paper label.  They can be queried through software and take no disk 
space.  If a drive fails electronically to the point it can't be 
queried, that serial number can be identified from a current list of all 
the drive serial numbers in the array--it's the one not there.


There are problems, they aren't like LEDs on each drive that could flash 
to identify it.  Some enclosures don't make drive labels easy to see. 
Some of that can be addressed with labels.  Er, sticky labels, on the 
outside of the drive or enclosure.  And serial numbers are often 
inconveniently long.



As for a unique number per disk, disks within the past ~5 years (SATA,
SAS, and some SCSI) all tend to have this: it's called a WWN:

http://en.wikipedia.org/wiki/World_Wide_Name

But older ATA disks (and by older I don't mean ancient, I mean even
semi-old) may not have this, which means you get to use something else.
UUIDs come to mind, but then the question becomes what do you base the
generation off of?  Model string + serial number + firmware?

There are also complexities depending on HBAs (disk controllers) as
well; I've seen references, at least on Solaris, of people having one
disk showing up twice across 2 separate controllers (i.e. only 1
physical disk in the machine, but showing up as both c8d0 and c9d0, both
with the same model string and serial number).  I imagine some RAID
controllers would do this (when a drive isn't part of an array; it might
show up as both /dev/adaX and /dev/somedriverX).  I know at some point I
saw this with FreeBSD too during an OS install, I just can't remember
what the names were that I saw.


Surely that ought to be considered a bug.  Any drive ID system is going 
to be vulnerable to certain



Linux has by-uuid and by-id (the latter is what you'd like), but there
are caveats to that too:

https://wiki.archlinux.org/index.php/Persistent_block_device_naming
http://www.terabyteunlimited.com/kb/article.php?id=389

So at the end of the day I prefer CAM's wired down method -- the
reason is that by modifying loader.conf I **know for sure** bay/cable X
maps to /dev/adaX, and it's a one-time deal until I decide to move from
my ICH9 controller to, say, an Areca.


That illustrates one problem with making the configuration specific to 
host hardware as compared to drive specific.


As far as best practices, situations vary so much that I don't know if 
any drive ID method can be recommended.  For a FreeBSD ZFS document, a 
useful sample configuration is going to be small enough that anything 
would work.  A survey of the techniques in use at various data centers 
would be interesting.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe

Re: Spontaneous reboots on Intel i5 and FreeBSD 9.0

[Warren Block]

On Fri, 18 Jan 2013, Ronald Klop wrote:


Memory chips gone bad? Power (or other) cables gone loose?


Memory failures will cause intermittent and mysterious things.  Easy to 
test, too, just run memtest86 on it for a while.  Do that before 
rebuilding.  If memory is failing, corrupted data could be written to 
disk.


I had a Crucial DIMM fail spontaneously a couple of weeks ago.  Working 
one minute, totally failed the next.  The machine rebooted, for no 
visible reason.  After it came back up, compiles failed, always with 
different errors and in different places.


Power supplies also fail, as do motherboards.  These are both harder to 
swap out than memory, so test the memory first.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Spontaneous reboots on Intel i5 and FreeBSD 9.0

[Warren Block]

On Fri, 18 Jan 2013, kpn...@pobox.com wrote:


On Fri, Jan 18, 2013 at 09:48:05AM -0700, Ian Lepore wrote:

I tend to agree, a machine that starts rebooting spontaneously when
nothing significant changed and it used to be stable is usually a sign
of a failing power supply or memory.


Agreed.


But I disagree about memtest86.  It's probably not completely without
value, but to me its value is only negative:  if it tells you memory is
bad, it is.  If it tells you it's good, you know nothing.  Over the
years I've had 5 dimms fail.  memtest86 found the error in one of them,
but said all the others were fine in continuous 48-hour tests.  I even
tried running the tests on multiple systems.

The thing that always reliably finds bad memory for me
is /usr/ports/math/mprime run in test/benchmark mode.  It often takes 24
or more hours of runtime, but it will find your bad memory.


I've had good luck with gcc showing bad memory. If compiling a new kernel
produces seg faults then I know I have a hardware problem. I've seen
compilers at work failing due to bad memory as well.

Some problems only happen with particular access patterns.  So if a compiler
works fine then, like memtest86, it doesn't say anything about the health
of the hardware.


Most test tools are like that.  They might diagnose something as bad, 
but they often can't prove it is good.  SMART has a reputation for not 
finding any problems on disks that are failing, and capacitors that 
aren't swollen or leaking still may not be working.


But diagnostic tools can at least give a hint.  In my case, memtest 
indicated a problem--a big problem.  I removed one DIMM at random (there 
were only two) and the problems and memtest errors both went away. 
Replace the DIMM, and both came back.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: csup to svn for 8-stable

[Warren Block]

On Fri, 11 Jan 2013, Brian W. wrote:


When I tried the first time, it only grabbed a few folders, a second try
got me a conflict message. I then just whacked /usr/src and did the svn co
again, successfully.


An important difference is that if you modify a file in /usr/src, an svn 
update will not overwrite it but try to merge with new versions of the 
file from the repository.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1-RC3: xorg-input-mouse, xfce4-panel

[Warren Block]

On Thu, 27 Dec 2012, CeDeROM wrote:


Hello :-)

I have found some issues with 9.1-RC3 packages/configuration using
binary packages:

1. xorg-input-mouse is old driver (?) that has the issue mentioned on
the list (current?) - the mouse is not always detected at first xorg
run. Please make sure 9.1-RELEASE use new mouse driver that has this
issue fixed (?) and/or update default configuration to use
AllowEmptyInput properly (Off).


Use AutoAddDevices Off instead.  AEI is prone to problems.
http://www.wonkity.com/~wblock/docs/html/aei.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: How to update ports tree indexes when using svn

[Warren Block]

On Mon, 10 Dec 2012, Matthew Seaman wrote:


On 10/12/2012 14:39, S.N.Grigoriev wrote:

after the security announcement
(http://www.freebsd.org/news/2012-compromise.html) I use svn to
update my local ports tree. I've found out that the port index is not
updated. What is the preferred/recommended way to update port indexes
when using svn?


That ports INDEX generated for 'make fetchindex' is not being updated is
a temporary thing, while machines are quarantined and rebuilt.  So you
could just wait for a few weeks until service is resumed.


'portmaster -L' also seems to work without an updated index, just leave 
out the --index-only option.  I have not looked to see how it does that 
so quickly, or verified that it does not miss anything.


# portmaster -L | egrep '(ew|ort) version|total install'
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Where do I purchace an unlock code to build a custom kernel?

[Warren Block]

On Sat, 24 Nov 2012, Chris H wrote:


Hi Chris,

Friday, November 23, 2012, 11:50:16 PM, you wrote:


Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8)
would throw me a bone if it were wrong.
Anyway, I'll take your advice.


There are some architecture specific settings there, so it is best to
actually do this and fail it early (well if you would do buildkernel
it would be earlier :) than getting some strange errors.

If you were thinking to just copy it to i386 directory, to save you
future issues, I would recommend you to redo the config based on
GENERIC in i386 directory.


Understood. That's what I did (i386/GENERIC -- CUSTOM).
I _knew_ there would be issue(s) otherwise.

Thank you again for the advice. Looks to be working as expected. :)


Rather than copy and modify, a custom config can include the GENERIC 
config and override settings.  That generally makes the custom config 
file smaller and easier to maintain: 
http://www.wonkity.com/~wblock/docs/html/kernelconfig.html

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 and intel graphics

[Warren Block]

On Sun, 21 Oct 2012, Thomas Mueller wrote:


Normally I start X by startx which may be followed by an initialization file,
so I don't get the default spartan default twm all the time.  In Linux and
FreeBSD, I generally use X as nonroot.

So I don't really know how to start a program such as xterm as another user
or how to have both root and nonroot windows in X.


Open a terminal, su - to root in it.  In the exceptionally rare case of 
needing to run a graphic program as root, also set the DISPLAY variable 
to match the normal user's value, then run that program in the terminal.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 and intel graphics

[Warren Block]

On Sat, 20 Oct 2012, Thomas Mueller wrote:


How do you shutdown from a window in X if you're nonroot?


Users that are a member of the operator group can run shutdown -p or -r.


Can you have both root and nonroot windows simultaneously in X?


Sure.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1-RC2 - could it be that the installer does not write the MBR?

[Warren Block]

On Sat, 20 Oct 2012, Rainer Duffner wrote:


Am Fri, 19 Oct 2012 17:11:30 -0400
schrieb Glen Barber g...@freebsd.org:


On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote:

If I select the entire disk for FreeBSD, I think it's a reasonable
assumption that the MBR should replaced, too.
Please don't make people install FreeBSD 9.0 first on disks with
non-FreeBSD MRRs and then upgrade to 9.1.



Can you outline for me in detail what you did when you partitioned
your drive during the installation?


I chose entire disk, then deleted all partitions-suggestions except
the first one and created my own partitioning scheme.
(/, swap, var, usr, maybe /var/log and /home, too)


I have seen your specific issue exactly once, and reliably reproducing
the problem has not been successful so far.

BTW, what was on the drive before you did the install, if anything?


It had a version of Solaris. Maybe Opensolaris. I don't know exactly.
And I don't know if it had zfsroot or not. I created a HW-RAID1 with
the HP P400 controller on it.
The drives were previously used in another server.

I tried to install 9.1RC2 twice on these disks and it always went back
to the grub-prompt after reboot.
Then I installed 9.0 and it's running now.


I don't know if this is the problem, but it is worth pointing out that 
graid(8) is now included in GENERIC.  Leftover hardware RAID metadata 
could make for unexpected results.  For example,

http://forums.freebsd.org/showthread.php?t=35168
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Question About Tracking the Stable Branch

[Warren Block]

On Tue, 28 Aug 2012, Jamie Paul Griffin wrote:

I've always updated my -RELEASE systems using the traditional method 
so it seems it's no different other than perhaps updating more 
frequently and deciding whether or not both kernel code and userland 
code needs to be rebuilt together.


It certainly seems a bad idea for me as someone with a lot to learn, 
to patch specific parts of the source tree and rebuild those parts as 
something is bound to go wrong at some point for me.


In addition to what others have suggested, the devel/ccache port can 
seriously reduce world and kernel compilation time by caching results. 
Stuff that hasn't changed comes out of cache rather than from a 
recompile.  A buildworld every few days usually takes only about a 
fourth of the time it would take without ccache.  Unfortunately, so far 
it only has this extreme an effect with gcc, not so much with clang.


I usually use 4G of cache space; haven't tested to see how much is 
actually needed.  Setting CCACHE_COMPRESS=yes fits more files in the 
cache.  In my tests, there was no speed penalty.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown

[Warren Block]

On Mon, 27 Aug 2012, Matt Smith wrote:


On 2012-08-27 11:26, Erich Dollansky wrote:

I would run plain UFS for / /var and /tmp and see what will happen then.

I know what you will answer. But it will help to isolate the problem.



Did you mean not use the label at all? If so I just tried this. Set 
/dev/ada0p2 in the fstab. No change. Still get the same issue.


This might help investigations as I wrote down what I did to install it.

The way I created this filesystem was that I dropped out of the installer to 
a shell because I wanted to do the 4k alignment. And I ran this:


gpart create -s gpt ada0
gpart add -t freebsd-boot -l gptboot -s 512k ada0
gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
gpart add -t freebsd-ufs -l gptroot -b 1M -s 586G ada0
gpart add -t freebsd-swap -l gptswap ada0
gpart show

=34  1250263661  ada0  GPT  (596G)
 341024 1  freebsd-boot  (512k)
   1058 990- free -  (495k)
   2048  1228931072 2  freebsd-ufs  (586G)
 122893312021330575 3  freebsd-swap  (10G)

newfs -U -j -L root /dev/gpt/gptroot
glabel label root /dev/ada0p2
glabel label swap /dev/ada0p3
mount /dev/gpt/gptroot /mnt
vi /tmp/bsdinstall_etc/fstab

# DeviceMountpoint  FStype  Options DumpPass#
/dev/label/root /   ufs rw  1   1
/dev/label/swap noneswapsw  0   0


Stefan called it.  The newfs is done on /dev/gpt/gptroot, no problem 
there.  But when glabel writes to /dev/ada0p2--which is 
/dev/gpt/gptroot, same thing, it overwrites the last block.  And then 
the filesystem is mounted with the glabel device, which is actually one 
block smaller than the filesystem expects.


Could be either the filesystem or GEOM that's causing the failure at 
shutdown.


Happily, those glabels aren't accomplishing anything useful and can be 
skipped.  Removing the glabels and changing the devices in fstab might 
be enough.  A more cautious approach would be to back up, newfs, skip 
the glabel step, and then change the devices in fstab.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown

[Warren Block]

On Mon, 27 Aug 2012, Matt Smith wrote:


On 2012-08-27 14:56, Warren Block wrote:


Stefan called it.  The newfs is done on /dev/gpt/gptroot, no problem
there.  But when glabel writes to /dev/ada0p2--which is
/dev/gpt/gptroot, same thing, it overwrites the last block.  And then
the filesystem is mounted with the glabel device, which is actually
one block smaller than the filesystem expects.

Could be either the filesystem or GEOM that's causing the failure at 
shutdown.


Happily, those glabels aren't accomplishing anything useful and can
be skipped.  Removing the glabels and changing the devices in fstab
might be enough.  A more cautious approach would be to back up, newfs,
skip the glabel step, and then change the devices in fstab.


As I said on a previous mail I did boot it with a USB stick and cleared the 
glabel metadata and altered the fstab to point to both the GPT labels and the 
raw UFS device and I still get the issue. So am I right in thinking then that 
this has caused irreparable damage


To the filesystem?  Probably (weasel word) not.  The old instructions 
for gmirror used the last block out of a filesystem and there have been 
no notable reports of data loss.


One thing to mention is that SU+J might change what the filesystem does 
with that last block.  I'm avoiding SU+J until the dump problem is 
fixed, so have not experimented with that.


and the only way I can fix this now is to newfs the filesystem again, 
this time just using GPT labels and not using glabel at all?


I'll commit to it and say yes, that will work.

This is the first time I've ever done a manually partitioned installation 
with GPT and alignment, previously I've only ever used sysinstall with 
non-aligned MBR installations, so it was a bit of a learning curve. If I do 
have to newfs it again then I want to be sure that I'm doing the correct 
things so that I don't find myself with any other issues. So does the rest of 
what I did look fine?


No obvious problems jumped out at me.  Here are my notes:
http://www.wonkity.com/~wblock/docs/html/disksetup.html

The gpart version is halfway down.  I really need to switch that around.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown

[Warren Block]

On Mon, 27 Aug 2012, Warren Block wrote:


No obvious problems jumped out at me.  Here are my notes:
http://www.wonkity.com/~wblock/docs/html/disksetup.html

The gpart version is halfway down.  I really need to switch that around.


Changed now so that the gpart(8) version is first.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown

[Warren Block]

On Mon, 27 Aug 2012, Kevin Oberman wrote:


No obvious problems jumped out at me.  Here are my notes:
http://www.wonkity.com/~wblock/docs/html/disksetup.html

The gpart version is halfway down.  I really need to switch that around.


Pretty good page, but I would really suggest that you also do either
4k or 1M alignment on your partitions. If you don't and use a disk
with 4K blocks (internally), you will have terrible performance.


You mean add the -a parameter for gpart?  All that -a does is round 
partition starting blocks and sizes to even values.  If the numbers 
given are already even multiples, it does nothing.


The reason -a4k is not shown there is because until a few months ago, -a 
overrode -b.  So


  # gpart add -t freebsd-ufs -l gprootfs -a4k -b 1M -s 2G da0

did not start that partition at 1M, but instead at the next even 4K 
block after the first 512K partition; block 1064 instead of block 2048, 
AFAIR.  The fix to gpart (thanks to ae@) is in 9-stable and 9.1, but not 
earlier releases.


Mentioned a little farther down in the article is that keeping 
additional partitions to even multiples of 1M or 1G size will keep them 
in alignment.


1M is recommended by Microsoft and used by Windows, but seems a bit 
excessive to me.


Also by some Sun RAID controllers and other systems.  1M is a nice even 
multiple of a lot of common block sizes.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown

[Warren Block]

On Mon, 27 Aug 2012, Matt Smith wrote:


On 2012-08-27 19:42, Warren Block wrote:

No obvious problems jumped out at me.  Here are my notes:
http://www.wonkity.com/~wblock/docs/html/disksetup.html

The gpart version is halfway down.  I really need to switch that around.


Oh! You're the owner of that site. As it happens those were the exact 
instructions that I used to try and figure out how to do it as you are first 
in google for freebsd gpt newfs!


Hah--I'm famous!

It's just a shame that I then decided to use the same method that I had used 
before on my old system for the labelling. On my old system I had used MBR 
partitioning and so needed to use glabel for labelling the swap and I then 
used the same thing for the UFS partition for consistency in the fstab. It 
never occurred to me when I was labelling the GPT partitions that I could 
have used those directly.


Experience is what you get when you didn't get what you wanted.

One thing that is still bugging me though is I'm wondering why I had no 
problem with this on my old system. That was using a dangerously dedicated 
disk with MBR where the root partition was just /dev/ada4a.
It was also using UFS2 with SU+J enabled and I had used glabel in 
exactly the same way but on this box it had not done any damage. 
Shutdown etc worked perfectly fine. Is there something different with 
the way GPT partitions work?


In use, GPT partitioning should work just the same.  Without recreating 
it, hard to define the difference that caused the shutdown problem.


Thank you for your help anyway, and your wonkity site, which I also once used 
for converting my procmail to maildrop. And thanks also to Erich and Stefan 
for your help. When I get some spare time I'll redo the filesystem and hope 
that it works.


Please post a followup after that.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown

[Warren Block]

On Mon, 27 Aug 2012, Kevin Oberman wrote:


On Mon, Aug 27, 2012 at 1:16 PM, Warren Block wbl...@wonkity.com wrote:

On Mon, 27 Aug 2012, Kevin Oberman wrote:


No obvious problems jumped out at me.  Here are my notes:
http://www.wonkity.com/~wblock/docs/html/disksetup.html

The gpart version is halfway down.  I really need to switch that around.



Pretty good page, but I would really suggest that you also do either
4k or 1M alignment on your partitions. If you don't and use a disk
with 4K blocks (internally), you will have terrible performance.



You mean add the -a parameter for gpart?  All that -a does is round
partition starting blocks and sizes to even values.  If the numbers given
are already even multiples, it does nothing.


You can force alignment by use of -b. I just managed to miss that you
were doing that. '-a' simply does the alignment and I have no reason
to forces the location of any partition as all are multiples of 1M and
4K. Use of -a and -b on the same command seems rather useless,


Might make more sense if -a is seen as a safety check.  And yes, -b is 
an exception, done in this case to get the first partition at a specific 
spot.



but it seems that ignoring -b is still a bug.


Works for me in 9-stable.  Here's the change in -head:

http://svnweb.freebsd.org/base/head/sbin/geom/class/part/geom_part.c?r1=229916r2=235033

It was MFCed to 8-stable and 9-stable on 2012-05-11.

 I'm not sure I get your statement that All that -a does is round 
partition starting blocks and sizes to even values.  -a aligns the 
start of every partition to the stated size (as your example showed).


Sorry, I should have been more precise with the wording.  By even I 
meant even multiple of the given block value.



The reason -a4k is not shown there is because until a few months ago, -a
overrode -b.  So

  # gpart add -t freebsd-ufs -l gprootfs -a4k -b 1M -s 2G da0

did not start that partition at 1M, but instead at the next even 4K block
after the first 512K partition; block 1064 instead of block 2048, AFAIR.
The fix to gpart (thanks to ae@) is in 9-stable and 9.1, but not earlier
releases.

Mentioned a little farther down in the article is that keeping additional
partitions to even multiples of 1M or 1G size will keep them in alignment.


1M is recommended by Microsoft and used by Windows, but seems a bit
excessive to me.



Also by some Sun RAID controllers and other systems.  1M is a nice even
multiple of a lot of common block sizes.


True, but so is 4K (8-512 byte blocks). Obviously 1M is also a
multiple of all powers of 2 below it as is 4K. Even in this age  of
cheap disks, 1G alignment seems a bit extreme, but in most cases, it


Er, 1M.  It leaves a little less than 512K of unused space.  Starting at 
1G would be a more difficult decision for me, though you're right that 
it's a trivial amount of space on a lot of computers.



really is insignificant for general purpose systems. It is an argument
for single partitions, but I always worry that something screwy will
blow up /var with log messages and I would not want this to fill all
disk space, so I like to keep that, as well as a read-only root. Just
old-fashioned, I guess.


Understood.  Usually separate filesystems for me, although I recently 
took to using tmpfs for /tmp.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Keyboard cutting off soon after launching X

[Warren Block]

On Thu, 26 Jul 2012, Daniel P. Wright wrote:


I am having issues with my keyboard running FreeBSD 9-RELEASE.  It is
recognised fine by the system and works within the console (outside of X),
but within a couple of minutes of X launching it stops working in X.  I can
still use ctrl-alt-F1 (or whatever) to break back out to the console, and
from there can kill X and relaunch.  It cuts out within a minute or so
every time though, so the computer is pretty much unusable under X.

I've seen similar problems on the FreeBSD forums, and tried to follow the
advice there, namely:

1) Ensuring the half and dubs daemons are running


hald and dbus...


2) Setting [Option  AutoAddDevices  Off] in xorg.conf


This tells X not to use hald.  If you window manager/desktop environment 
does not require hald, not running hald at all might fix the problem. 
dbus can be kept.  AFAIK, xfce is the only desktop environment that 
doesn't need hald, but all the simpler window managers should be fine.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Keyboard cutting off soon after launching X

[Warren Block]

On Thu, 26 Jul 2012, Erich Dollansky wrote:


I ran FreeBSD since 8 on this machine but I have had to start finding a
new setting for xorg.conf to make X working again after a recent
upgrade.

Enable moused in rc.conf and the following from xorg.conf helped me this
time:

#
# 24.07.12 ed:  we enable the mouse and see what will happen.
#
Section ServerLayout
Identifier X.org Configured
Screen  0  Screen0 0 0
InputDeviceMouse0 CorePointer   # 24.07.12 ed:
enabled for 1.7.7 # InputDeviceKeyboard0 CoreKeyboard
EndSection

Section ServerFlags
Option  AllowEmptyInput false   #
16.07.10 ed: enabled for 1.7.5 # 24.07.12 ed: disabled for 1.7.7

#
16.07.12 ed:setting it to false
#   freezes X until mouse
#   moves #
Option  AutoAddDevices  false EndSection

I have had to define the mouse as InputDevice and set AllowEmptyInput
to false.


The comment wrap there is very confusing.  But please stop using 
AllowEmptyInput.  It was so misused that it has even been removed from 
later versions of xorg.

http://www.wonkity.com/~wblock/docs/html/aei.html

There is an interaction with hald and moused that makes it worthwhile 
lately for some users to run moused from rc.conf.  There may be a 
similar interaction with kbdmux(4) or some other keyboard component for 
keyboards.


hald can be improved greatly by its absence.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Keyboard cutting off soon after launching X

[Warren Block]

On Fri, 27 Jul 2012, Erich Dollansky wrote:


On Thu, 26 Jul 2012 11:03:05 -0600 (MDT)
Hi,

Warren Block wbl...@wonkity.com wrote:


On Thu, 26 Jul 2012, Erich Dollansky wrote:


Enable moused in rc.conf and the following from xorg.conf helped me
this time:

Option  AllowEmptyInput false   #



The comment wrap there is very confusing.  But please stop using
AllowEmptyInput.  It was so misused that it has even been removed
from later versions of xorg.
http://www.wonkity.com/~wblock/docs/html/aei.html


I have read this before. But what else would you do when the line above
solves the problem?


Personally, I would wonder why AutoAddDevices Off did not solve the 
problem.  I've had more than a few people tell me that AEI worked for 
them, and so there was no reason to try AutoAddDevices.  So far, no one 
has reported that AEI worked but AutoAddDevices did not.


Failing that, I'd rebuild xorg-server with the HAL option disabled.  If 
the desktop environment requires hald, it can still be run but will not 
be used by xorg.


Which brings up another possibility: there could be something going on 
with the input stream after xorg, some utility or part of a desktop 
environment that has a bug that causes it to eat all keyboard events. 
It might even be a portion of xorg that needs to be rebuilt.



There is an interaction with hald and moused that makes it worthwhile
lately for some users to run moused from rc.conf.  There may be a


I wonder why.


Changes in the drivers, most likely.


similar interaction with kbdmux(4) or some other keyboard component
for keyboards.

hald can be improved greatly by its absence.


Isn't this the case on some Linux machines?


Many Linux systems have dumped hal for udev.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: The MFC process...

[Warren Block]

On Tue, 17 Jul 2012, Eitan Adler wrote:


On 17 July 2012 05:50, David Magda dma...@ee.ryerson.ca wrote:

On Tue, July 17, 2012 02:10, Eitan Adler wrote:

Of interest to me: if it could be limited to just the commits I made
and optionally show me the log message and diff it would be very
helpful.

On a general note: be careful with any level of automation with this
script though. Sometimes there are good reasons that a commit wasn't
MFCed.




A lot of messages have a MFC after note on them, so the the developer/s
in question already know which commits are good candidates for bringing
over to STABLE. It may simply be that they could use a reminder on them.


Just to add: developers get an automated email at the MFC after time
reminding them to MFC.


But only once.  It would be nice if it was like PR notifications, once a 
week.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: The MFC process...

[Warren Block]

On Tue, 17 Jul 2012, Eitan Adler wrote:


On 17 July 2012 09:28, Warren Block wbl...@wonkity.com wrote:

On Tue, 17 Jul 2012, Eitan Adler wrote:


On 17 July 2012 05:50, David Magda dma...@ee.ryerson.ca wrote:


On Tue, July 17, 2012 02:10, Eitan Adler wrote:


Of interest to me: if it could be limited to just the commits I made
and optionally show me the log message and diff it would be very
helpful.

On a general note: be careful with any level of automation with this
script though. Sometimes there are good reasons that a commit wasn't
MFCed.





A lot of messages have a MFC after note on them, so the the developer/s
in question already know which commits are good candidates for bringing
over to STABLE. It may simply be that they could use a reminder on them.



Just to add: developers get an automated email at the MFC after time
reminding them to MFC.



But only once.  It would be nice if it was like PR notifications, once a
week.


Please no! If this is the case, it should be an option.


I don't expect it to happen.  But right now, there's only the initial 
mail that the MFC is due, and no reminder afterwards.  We have the open 
PR mails once-weekly; MFCs are at least as important.


Come to think of it, entering PRs for past-due MFCs could be a way to do 
that with the existing systems.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: The MFC process...

[Warren Block]

On Tue, 17 Jul 2012, Eitan Adler wrote:


On 17 July 2012 09:53, Warren Block wbl...@wonkity.com wrote:


I don't expect it to happen.  But right now, there's only the initial mail
that the MFC is due, and no reminder afterwards.  We have the open PR mails
once-weekly; MFCs are at least as important.


I have a special place in my email for MFC reminder emails which I use
as a todo list. Getting weekly reminders would just be annoying.


Why would it be a problem with with MFCs if it isn't a problem for PRs?


Come to think of it, entering PRs for past-due MFCs could be a way to do
that with the existing systems.


We have this already: PRs in the 'patched' state.


Unless there was no PR.  Which brings up the question of how can we 
query for MFCs now?  For example, how many MFCs are past due?  What is 
the oldest one?

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: The MFC process...

[Warren Block]

On Tue, 17 Jul 2012, Eitan Adler wrote:


On 17 July 2012 10:10, Warren Block wbl...@wonkity.com wrote:

I have a special place in my email for MFC reminder emails which I use
as a todo list. Getting weekly reminders would just be annoying.


Why would it be a problem with with MFCs if it isn't a problem for PRs?


Some people find the PR ones annoying. ;)
A better answer: because sometimes I make a deliberate decision to
*not* MFC something even though it says MFC after


Right now, there's no way for anyone but the original committer to tell 
whether an MFC has been forgotten, is delayed, no longer applies, or any 
other reason.



Unless there was no PR.  Which brings up the question of how can we query
for MFCs now?  For example, how many MFCs are past due?  What is the oldest
one?


svn mergeinfo --show-revs eligible


But those are just commits that svn sees as eligible for a merge, not 
ones with an actual MFC after message.



The OP seemed interested in writing a script to make this output usable.


I'd be interested in this also.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: video issue - Intel Atom based motherboard D2500HN

[Warren Block]

On Sun, 15 Jul 2012, Marek Salwerowicz wrote:


W dniu 2012-07-14 22:00, Warren Block pisze:


Did you try the changes mentioned here?
http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035366.html


Not yet - but are they only available in 10-Current or also in 9-Stable ?
I'd like to use stable in that box.


Those changes are only in HEAD (CURRENT) right now.  Looks like they 
could be manually applied to 9-STABLE, though.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: video issue - Intel Atom based motherboard D2500HN

[Warren Block]

On Sat, 14 Jul 2012, Marek Salwerowicz wrote:


I recently bought a Intel D2500HN motherboard with Intel GMA 3600 video card.
I want to install FreeBSD 9-Release on it via PXE, but after booting the 
system, it seems that video card driver doesn't work properly.


Have a look at this picture: 
http://img703.imageshack.us/img703/5648/20120714393.jpg


I've tried the
# vidcontrol 80x25

but unfortunately it doesn't help.

Do you have any idea how to deal with taht graphics?


Did you try the changes mentioned here?
http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035366.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: new desktop box

[Warren Block]

On Mon, 2 Jul 2012, Zoran Kolic wrote:


I run an 8120, it is a bulldozer however. I overclock it by adjusting
the multiplier in the bios. Stock freq is 3.1GHZ and I run it at 4.2 GHz
with an increase in Vcore of only 0.125V cooling with air. Solid as a
rock.


How about heating?


- buildworld runs about 20min.
- buildkernel runs about 6min.


That is what matters.   :)


If you use gcc, devel/ccache can improve that a lot.  ccache also works 
with clang, but does not seem very effective.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: new desktop box

[Warren Block]

On Thu, 28 Jun 2012, Zoran Kolic wrote:


Thanks all for reply!


The real question is which video card do you want to use?


Since I'm not gamer nor do 3d, some silent card will suffice.
There are nvidia gp520 and radeon 6450, both with no fan.


Do not get a Radeon newer than the 4000-series, the drivers are not 
available in FreeBSD at present.  The 4650 has worked well for me.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: new desktop box

[Warren Block]

On Wed, 27 Jun 2012, Lucas Holt wrote:


AMD and Intel both have good CPU offerings. Both have a turbo feature to 
improve single core workloads.

The real question is which video card do you want to use? Both have integrated 
solutions now or you could pick a discrete card. I personally go amd but buy 
nvidia cards as there are binary drivers. Amd's newer cards are not supported 
by x11 well under bsd. If you go with an on CPU gpu (APU) this is an intel only 
scenario.

Amd chips are cheaper but you need a video card too. 
___


The Core i5 processors cost more (sometimes a lot more), but dominate 
AMD in benchmarks.  FreeBSD also has/will have support for the open 
Intel video driver.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Kernel modules are broken after updating to the latest FreeBSD 9-STABLE

[Warren Block]

On Mon, 18 Jun 2012, Olav Gjerde wrote:


Yesterday I updated to the latest version of FreeBSD 9-STABLE. I
always follow the procedure in the manual -
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
And I use the GENERIC config with no modifications.

The system boots fine, however quite a few important kernel modules no
longer works. Specifically nullfs, fdescfs, zfs, zlib, xfs, while some
other modules like geom_mirror and geom_raid works.

I get the following error messages:
KLD nullfs.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD fdescfs.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type

What could have gone wrong? What can I do to fix this?


Did you miss the buildkernel/installkernel steps?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: devd problem with 9-stable

[Warren Block]

On Fri, 15 Jun 2012, Ronald Klop wrote:


On Fri, 15 Jun 2012 08:01:21 +0200, Kevin Oberman kob6...@gmail.com wrote:


On Thu, Jun 14, 2012 at 3:11 AM, Ronald Klop
ronald-freeb...@klop.yi.org wrote:
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman kob6...@gmail.com 
wrote:



Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.


From devd.conf


attach 50 {
  device-name ugen[0-9]+;
  match vendor 0x0529;
  match product 0x0600;
  action /usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
  device-name ugen[0-9]+;
  match vendor 0x0529;
  match product 0x0600;
  action /usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};

If I manually enter the action command, it works fine, but it fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.

Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a



Did you run devd with debug messages on? Options -D and -d are helpful.
If you do does devd match the right devd.conf sections and start the 
action?


With debug i get:
Processing event '!system=USB subsystem=DEVICE type=ATTACH
ugen=ugen1.3 cdev=ugen1.3 vendor=0x0529 product=0x0600 devclass=0xff
devsubclass=0x00 sernum= release=0x0100 mode=host port=1
parent=ugen1.2'
[long list of Testing entries, none of which 'vendor' matched]
Executing 'logger Unknown USB device: vendor 0x0529 product 0x0600 bus 
uhub3'


So it looks like devd is not matching the vendor. But my devd.conf
file contains that vendor. I don't know exactly why it is not being
tested against. Nothing in the debug output gives me a clue and I
tried grepping for one of the tested vendor IDs in /etc/devd.conf and
/etc/devd/*.conf.  Not found.

I am at a loss.


http://www.freebsd.org/releases/9.0R/errata.html
See point 3 under Open Issues.


Even with those changes, devd is not triggering on my scanner attach:

match subsystem DEVICE;
match type ATTACH;
match cdev ugen[0-9]+.[0-9]+;
match vendor 0x04b8;
match product 0x010a;
action echo HERE! $cdev  /tmp/zoot;

# devd -d -D -f /etc/devd/wb.conf

Processing event '!system=USB subsystem=DEVICE type=ATTACH ugen=ugen0.6 
cdev=ugen0.6 vendor=0x04b8 product=0x010a devclass=0xff devsubclass=0xff 
sernum= release=0x0103 mode=host port=4 parent=ugen0.4'

Pushing table
setting system=USB
setting subsystem=DEVICE
setting type=ATTACH
setting ugen=ugen0.6
setting cdev=ugen0.6
setting vendor=0x04b8
setting product=0x010a
setting devclass=0xff
setting devsubclass=0xff
setting sernum=
setting release=0x0103
setting mode=host
setting port=4
setting parent=ugen0.4
Processing notify event
Testing system=USB against ^DEVFS
Testing system=USB against ^DEVFS
Popping table

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: devd problem with 9-stable

[Warren Block]

On Fri, 15 Jun 2012, Oliver Fromme wrote:


Warren Block wrote:
 [...]
 attach 50 {
 [...]

 Even with those changes, devd is not triggering on my scanner attach:

  match subsystem DEVICE;
  match type ATTACH;
  match cdev ugen[0-9]+.[0-9]+;
  match vendor 0x04b8;
  match product 0x010a;
  action echo HERE! $cdev  /tmp/zoot;

Have you tried to put those lines inside a notify block
instead of an attach block?  The documentation is not
very clear about the difference between an attach block
an a notify block with $type=ATTACH, but it probably
wouldn't hurt to try both.


Well, it did work with an attach event.  Progress: the event is seen 
with a notify event.  However, something is not right with the execution 
of backticks in the action string:


notify 20 {
match subsystem DEVICE;
match type ATTACH;
match cdev ugen[0-9]+.[0-9]+;
match vendor 0x04b8;
match product 0x010a;
action devnum=`echo $cdev | sed -e 's/^ugen//'`  \
echo $devnum  /tmp/example  \
echo $cdev  /tmp/example;
};

When the event is seen:
Executing 'devnum=`echo ugen0.6 | sed -e 's/^ugen//'`  echo devnum:   /tmp/example 
 echo cdev: ugen0.6  /tmp/example'

$devnum never gets a value, the contents of /tmp/example are:
  devnum:
  cdev: ugen0.6

Trying $() instead of backticks makes it worse:
Executing 'devnum=$(echo $cdev | sed -e 's/^ugen//')  echo devnum: $devnum  /tmp/example 
 echo cdev: $cdev  /tmp/example'

/tmp/example is then:
  devnum:
  cdev:
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: devd problem with 9-stable

[Warren Block]

On Fri, 15 Jun 2012, Oliver Fromme wrote:


 When the event is seen:
 Executing 'devnum=`echo ugen0.6 | sed -e 's/^ugen//'`  echo devnum:   /tmp/example 
 echo cdev: ugen0.6  /tmp/example'

 $devnum never gets a value, the contents of /tmp/example are:
devnum:
cdev: ugen0.6

 Trying $() instead of backticks makes it worse:
 Executing 'devnum=$(echo $cdev | sed -e 's/^ugen//')  echo devnum: $devnum  /tmp/example 
 echo cdev: $cdev  /tmp/example'

Unfortunately, the manual page does not explain how the action
strings are parsed exactly.  I guess the problem is not the
backticks but the fact that the parser tries to expand $devnum
as a devd variable, so the shell never sees it.  This also
explains why using $() makes things worse.


It should be pointed out that this is a regression from 8.x.


You can try to prepend a backslash, i.e. echo \$devnum.  This
isn't documented, but then again, using backslashes to continue
strings that span multiple lines isn't documented either.


devd has already expanded variables by then:
Executing 'devnum=ugen0.6  echo devnum: \  /tmp/example  echo cdev: ugen0.6 
 /tmp/example'

It does seem to work to use the bracketed form:

action devnum=`echo $cdev | sed -e 's/^ugen//'`  echo ${devnum}  
/tmp/example;


In case the sed command still doesn't work, alternatively you
can use shell substring processing instead (this is also more
efficient because the shell doesn't have to create a pipe and
fork a sed process):

  action devnum=$cdev; devnum=\${devnum##ugen}; echo \$devnum  /tmp/foo

Or even:

  action devnum=$cdev; echo \${devnum##ugen}  /tmp/foo


I like that, and it does work without the backslash.
  action devnum=$cdev ; echo ${devnum##ugen}  /tmp/example;
  cat /tmp/example
  0.6

I started to enter a PR, but got confused partway through.  The problem 
here is that devd is expanding variables unknown to it in action strings 
(unless the bracket notation is used), and replacing them with empty 
strings.  Agreed?

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: devd problem with 9-stable

[Warren Block]

On Fri, 15 Jun 2012, Freddie Cash wrote:


On Fri, Jun 15, 2012 at 11:45 AM, Oliver Fromme o...@lurza.secnetix.de wrote:

Chuck Swiger wrote:
  On Jun 15, 2012, at 11:23 AM, Oliver Fromme wrote:
   You can try to prepend a backslash, i.e. echo \$devnum.  This
   isn't documented, but then again, using backslashes to continue
   strings that span multiple lines isn't documented either.
 
  Line continuations and escaping special chars like $ are in man sh:

Yes, I know that, but the question is how devd(8) parses the
action strings.

The problem here is that we have multiple levels or parsing.
First, devd reads the line, concatenates continuation lines
(apparently -- it's not documented), expands devd variables,
and *then* it passes the resulting string to the shell for
further parsing and processing.


If you have that many levels of backticks, variable expansions,
programs, etc, wouldn't it be a prime candidate for a script?  Just
pass in a couple of variables directly from devd, and then do
everything else inside the script?


It can be done that way, sure.  But allowing short scripts in the action 
string makes for less files to maintain.  Exactly how devd parses the 
action string should be better-defined either way.___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Backups with 9-STABLE -- Options?

[Warren Block]

On Sun, 10 Jun 2012, Karl Denninger wrote:


1. Is it REALLY safer to have the root filesystem run WITHOUT
softupdates?  (As was previous default practice)


The FAQ has an entry which has been there for a while.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#SAFE-SOFTUPDATES


2. In order of risk of data loss what are the risks and options for SU,
SU+J and neither?  Neither exposes you to huge time delays on a
post-crash boot due to the fsck requirement, but SU can expose you to a
failed background fsck and thus get you the huge time delay too.  Since
SU+J eliminates this the only argument for NOT using it is that it's
more dangerous to your data than running without either or with SU
alone.  Is this true?


AFAIK, they should be the same as far as filesystem integrity, it's just 
that SU+J cuts down the time spent waiting for fsck.



3. Is there intent to fix dump -L with SU+J?


Yes, and there have been commits in the last few months.
http://svnweb.freebsd.org/base/head/sys/ufs/ufs/inode.h?sortby=dateview=log


If so, is there a projection on when?


Sorry, no idea.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Documenting 'make config' options

[Warren Block]

On Wed, 6 Jun 2012, Vincent Hoffman wrote:


On 06/06/2012 22:23, Glen Barber wrote:

On Wed, Jun 06, 2012 at 02:14:46PM -0700, Doug Barton wrote:

On 06/06/2012 11:59, Dave Hayes wrote:

I'm describing more of a use case here, not attempting to specify an
implementation. If a user invokes 'make', a window is presented to them
with various options. It's probably very common that this is met with an
initial reaction of what the hell do these do?, even from the most
seasoned of admins (presuming they are unfamiliar with the software they
have been asked to install). I claim it would be an improvement to have
that information at the fingertips of the make invoker.

What manner of providing this information would meet your needs?


IMHO, something informing what THAT is in devel/subversion option
MOD_DONTDOTHAT would be nice.  :)


Not something I had bothered looking up till now as I hadnt wanted to
use it but the 2nd hit on google,
http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2009-April/161673.html
describes it quite well.
I tend to go with, If i dont know what it is, and its not default, I
probably dont need it.
Unless it looks interesting, then I google it ;)

Maybe an (optional) new file with a longer descriptions of the make
options so as not to crowd the make config dialog?
I dont mind looking up compile time options for software I am installing
but I can see how having a precis available locally might be handy.


Here's an idea: if the description is too long to show in the very 
limited space, cut it off, show a ..., and show the entire description 
in a two- or three-line text box below the main one.  The  indicate 
a highlight here:


  ---
  [ ] GOOFY Build with support for the...  
   [ ] EXAMPLES  Install the examples

  ---
 OKCancel

   -
   Build with support for the GOOFY framework
   that provides concurrent whoopsies integrated
   with a Perubython interpreter, and stuff.
  ---

The description at the bottom is from whatever option is currently 
highlighted, and changes as the user scrolls through the options.  It 
would be blank if the entire description could be displayed in the space 
available above.


The advantage of this is that it would work with existing ports, and 
give the ability to use longer descriptions.  The disadvantage is that 
dialog(1) would probably need modifications.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ports devel/tkcvs

[Warren Block]

On Thu, 24 May 2012, Sean Bruno wrote:


Probably doing something wrong, but when I install tkcvs to get tkdiff
on my box, the only thing it does is fire up and display a wish
window.

Did I do it wrong?  :-)


No idea, but devel/diffuse might be alternative.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: [stable-9] Touchpad mouse stopped working

[Warren Block]

On Thu, 17 May 2012, Tom Evans wrote:


On Thu, May 17, 2012 at 12:01 PM, A.J. Fonz van Werven
f...@skysmurf.nl wrote:

After moving from 9.0-RELEASE to 9-STABLE yesterday, the touchpad mouse on
my netbook stopped working. When I do
# /etc/rc.d/moused onestart
the pointer appears and can be moved for a second or two, then it stops
responding. Any thoughts?

$ uname -a
FreeBSD ace.skysmurf.nl 9.0-STABLE FreeBSD 9.0-STABLE #0: Thu May 17 10:49:00 
CEST 2012     r...@ace.skysmurf.nl:/usr/obj/usr/src/sys/GENERIC  i386



Did you mean the mouse doesn't move in xorg, or on the console? If in
xorg, have you seen this thread on x11@?

http://lists.freebsd.org/pipermail/freebsd-x11/2012-April/011756.html
http://lists.freebsd.org/pipermail/freebsd-x11/2012-May/011851.html

The proposed solution is to set AutoAddDevices off, so that hald is
not used to enumerate mice/keyboards, and instead rely on explicitly
configuring them in your xorg.conf.

This doesn't work for me, I need working hald as I plug and unplug
keyboards and mice each time I take my laptop out of its dock,


There might be some hardware thing in your setup that requires hald, but 
I do manage to hot-connect external USB mice without HAL installed.  One 
notebook needed moused_enable, but that's all.  Can't recall whether 
that one even has InputDevice sections in xorg.conf.  I'll post the 
config in a bit.___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: [stable-9] Touchpad mouse stopped working

[Warren Block]

This is the config file I use.  Hot-connect works for USB mice and 
keyboards.  Comments included for completeness.



From rc.conf:


dbus_enable=YES
moused_enable=YES

Without running moused from rc.conf, only one of the mice would work at 
a time.


HAL is not installed, so the AutoAddDevices setting is unnecessary but 
kept as a reminder.  The double monitor entries and Virtual setting are 
for using an external projector.  Note that all the InputDevice stuff is 
commented.  xorg doesn't need it.


xorg.conf:

Section ServerLayout
Identifier X.org Configured
Screen  0  Screen0 0 0
#   InputDeviceMouse0 CorePointer
#   InputDeviceKeyboard0 CoreKeyboard
Option DontZap On
Option AutoAddDevices Off
EndSection

Section Files
ModulePath   /usr/local/lib/xorg/modules
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
Identifier Monitor0
VendorName AUO
Option Position 0 0
EndSection

Section Monitor
Identifier Monitor1
Option Above LVDS
#Option Position 0 800
EndSection

Section Device
### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz
### [arg]: arg optional
#Option NoAccel # [bool]
#Option SWcursor# [bool]
#Option ColorKey# i
#Option CacheLines  # i
#Option Dac6Bit # [bool]
#Option DRI # [bool]
#Option NoDDC   # [bool]
#Option ShowCache   # [bool]
#Option XvMCSurfaces# i
#Option PageFlip# [bool]
Identifier  Card0
Driver  intel
VendorName  Intel Corporation
BoardName   Mobile GM965/GL960 Integrated Graphics Controller 
(primary)
BusID   PCI:0:2:0
Option  Monitor-LVDS Monitor0
Option  Monitor-VGA  Monitor1
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
SubSection Display
Viewport   0 0
Depth 24
Virtual 1280 2080
EndSubSection
EndSection
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: [stable-9] Touchpad mouse stopped working

[Warren Block]

On Thu, 17 May 2012, Tom Evans wrote:


On Thu, May 17, 2012 at 3:29 PM, Warren Block wbl...@wonkity.com wrote:

On Thu, 17 May 2012, Tom Evans wrote:

This doesn't work for me, I need working hald as I plug and unplug
keyboards and mice each time I take my laptop out of its dock,



There might be some hardware thing in your setup that requires hald, but I
do manage to hot-connect external USB mice without HAL installed.  One
notebook needed moused_enable, but that's all.  Can't recall whether that
one even has InputDevice sections in xorg.conf.  I'll post the config in a
bit.


Yes, moused is exceptional in that regard, but my main issue is
attaching/detaching keyboards. Most of my time, I use a PS/2 Model M,
connected to a laptop dock with a USB-PS/2 adaptor. I need that when
I undock, I can use the laptop keyboard, and when I redock, that I get
back my external keyboard.

I suppose the equivalent to sysmouse/moused is kbdmux, but with hald
and older Xorg, this did just DTRT.

PS: I just read to the end of the thread, Warren your config looks
interesting if it can handle hotplugging keyboards. I will give this a
try this evening, I also want to do some testing to see if the state
in hald changes between xorg restarts.


A USB keyboard here just worked; kbdmux lets you type on either or both. 
Unfortunately, the notebook does not have a PS2 port*, and I don't have 
a dock for it, so USB is all I can test.



* Yes, I'll happily hot-connect PS2 keyboards and laugh at the danger of 
doing so!  Bwahahaha!___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ATI Radeon 4250 in Dual Head Config?

[Warren Block]

On Mon, 16 Apr 2012, Sean Bruno wrote:


Does anyone have an ATI 4250 in a dual head config?  I'd be interested
in looking over your xorg.conf.

Sean

p.s.  Mine at the moment, that doesn't work very well:
http://people.freebsd.org/~sbruno/4250_xorg_conf.txt


Here's what I use with a 4650, comments removed to save space.
Notes:
1. Don't use AEI: http://www.wonkity.com/~wblock/docs/html/aei.html
2. Monitors are assigned to connectors in the Device section.  The
   Position option in the Monitor section defines what part they show.
3. This is one desktop across two monitors, the combined size set in the
   Virtual line.
4. HAL is not installed, but I'm fairly sure this will work either way.

Section ServerLayout
Identifier   Manually Configured
Screen   0  Screen0 0 0
Option   DontZap Off
Option   AIGLX On
Option   AutoAddDevices Off
EndSection

Section Files
ModulePath /usr/local/lib/xorg/modules
FontPath /usr/local/lib/X11/fonts/bitstream-vera/
EndSection

Section DRI
Group 0
Mode  0660
EndSection

Section Extensions
Option   Composite Enable
EndSection

Section Monitor
Identifier   Monitor0
VendorName   HWP
ModelName2615
Option   PreferredMode 1920x1200
Option   Position 1280 0
EndSection

Section Monitor
Identifier   Monitor1
VendorName   SAM
ModelName215
Option   PreferredMode 1280x1024
Option   Position 0 0
EndSection

Section Device
Identifier  Card0
Driver  radeon
VendorName  ATI Technologies Inc
BoardName   RV730 PRO [Radeon HD 4650]
Option  AccelMethod EXA
Option  Monitor-DVI-0 Monitor0
Option  Monitor-VGA-0 Monitor1
Option  ClockGating On
Option  DynamicPM On
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
SubSection Display
Virtual 3200 1200
EndSubSection
EndSection


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9-stable: what happened to geom_labels?

[Warren Block]

On Wed, 7 Mar 2012, Peter Maloney wrote:


On 03/06/2012 05:08 PM, Warren Block wrote:

A new install of 9-release, updated to 9-stable today with the GENERIC
kernel.
gpart show -l shows GPT labels, yet there isn't even a /dev/gpt
directory.

Has something changed with labels?

...

# Setting this to 0 will get rid of the /dev/gptid directory and you
will see your /dev/gpt directory again.
kern.geom.label.gptid.enable=0


This does remove /dev/gptid, but /dev/gpt did not reappear.


# Not sure what this does; I assume it means to show either gptid (if
not disabled above) or the original device name (eg. da0p2)
kern.geom.label.gpt.enable=0


Setting that to 1 still does not cause the /dev/gpt directory to appear. 
What's odd about this is that it did work on 8-stable recently.  A 
system here with i386 8-stable from January 13 has both sysctls enabled 
and both gpt and gptid directories in /dev.  So does an i386 9-stable 
from February 9.  The system where they aren't appearing is amd64 from 
Tuesday (March 6).


None of these systems have ZFS filesystems.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

9-stable: what happened to geom_labels?

[Warren Block]

A new install of 9-release, updated to 9-stable today with the GENERIC 
kernel.

gpart show -l shows GPT labels, yet there isn't even a /dev/gpt directory.

Has something changed with labels?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: sendmail and smarthost

[Warren Block]

On Mon, 27 Feb 2012, Warren Block wrote:

In 8.3-PRERELEASE, sendmail is now happily ignoring a smarthost unless 
DONT_PROBE_INTERFACES is set.  That used to be unnecessary.


That machine rarely sends email, but a bug followup sent on Feb 25 went 
through.  Maybe not significant since it was outside the local domain.


Adding an IPv6 entry for the hostname to /etc/hosts prevents the problem 
without requiring DONT_PROBE_INTERFACES.  (Thanks to George Shapiro!)


This brings up the question of why an IPv6 hosts entry is needed on an 
IPv4-only system, but that's for another thread.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: sendmail and smarthost

[Warren Block]

On Thu, 1 Mar 2012, Warren Block wrote:

Adding an IPv6 entry for the hostname to /etc/hosts prevents the problem 
without requiring DONT_PROBE_INTERFACES.  (Thanks to George Shapiro!)


Make that Greg, not George.  He now gets to call me Wally.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: sendmail and smarthost

[Warren Block]

On Thu, 1 Mar 2012, Warren Block wrote:


On Mon, 27 Feb 2012, Warren Block wrote:

In 8.3-PRERELEASE, sendmail is now happily ignoring a smarthost unless 
DONT_PROBE_INTERFACES is set.  That used to be unnecessary.


That machine rarely sends email, but a bug followup sent on Feb 25 went 
through.  Maybe not significant since it was outside the local domain.


Adding an IPv6 entry for the hostname to /etc/hosts prevents the problem 
without requiring DONT_PROBE_INTERFACES.  (Thanks to George Shapiro!)


This brings up the question of why an IPv6 hosts entry is needed on an 
IPv4-only system, but that's for another thread.


Or not, updating and rebuilding seems to have everything back to normal. 
Most likely I built a GENERIC kernel with IPv6 instead of a custom one 
without.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

sendmail and smarthost

[Warren Block]

In 8.3-PRERELEASE, sendmail is now happily ignoring a smarthost unless 
DONT_PROBE_INTERFACES is set.  That used to be unnecessary.


That machine rarely sends email, but a bug followup sent on Feb 25 went 
through.  Maybe not significant since it was outside the local domain.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 8.3-BETA1 installation problem

[Warren Block]

On Wed, 22 Feb 2012, Omer Faruk SEN wrote:


I am trying to install FreeBSD 8.3-BETA1 to a system with ssd disk
recognized as ad6. At fixit mode i can dd device but at installer
(sysinstall) when I configured disk and using w installer is unable to
format devices stating that

Unable to find device node for /dev/ad6s1b in dev. The creation of file
systems will be aborted

any suggestion on what may be the reason for that or is it a bug on
installer


Using Write is one of the causes for that.  Don't Write, just choose 
Quit after making selections.


(There are other causes, like old partitioning information on the disk. 
Removing that with gpart destroy or just dd-ing zeros over it is the 
cure in that case.)

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

ssh-add echos passphrase

[Warren Block]

Is anyone else seeing ssh-add echo the passphrase on a recent 8-stable?

FreeBSD lightning 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Tue Feb 21 
15:37:08 MST 2012 root@lightning:/usr/obj/usr/src/sys/LIGHTNING  i386

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ssh-add echos passphrase

[Warren Block]

On Tue, 21 Feb 2012, Doug Barton wrote:


On 02/21/2012 16:16, Warren Block wrote:

Is anyone else seeing ssh-add echo the passphrase on a recent 8-stable?


No. Are you sure that you're running the agent before you ssh-add?


8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Tue Feb 21

  # pkill ssh-agent
  % ssh-add ~/keyfile
  Could not open a connection to your authentication agent.
  % eval `ssh-agent -c`
  Agent pid 2658
  % ssh-add ~/keyfile
  Enter passphrase for /home/wblock/keyfile: abc123

Another system has -stable from January 13 and works as expected (no 
passphrase echo).

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ssh-add echos passphrase

[Warren Block]

On Tue, 21 Feb 2012, Warren Block wrote:


Is anyone else seeing ssh-add echo the passphrase on a recent 8-stable?

FreeBSD lightning 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Tue Feb 21 
15:37:08 MST 2012 root@lightning:/usr/obj/usr/src/sys/LIGHTNING  i386


After backdating a few days with no change, then csupping back to 
RELENG-8, ssh-add is back to normal.  Wish I had an idea why.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: New BSD Installer

[Warren Block]

On Fri, 17 Feb 2012, Freddie Cash wrote:


On Fri, Feb 17, 2012 at 3:12 AM, Pete French petefre...@ingresso.co.uk wrote:

I wasn't aware you could do that.  I was only aware that it was the
other way around.  That (my) misconception seems to also be relayed
by others such as Miroslav who said:


Should this not be the recommended way of doing things even for MBR
disks ? I have a lot of machines booting from gmirror, but we always
do it by mirroring MBR partitions (or GPT ones). I cant see why you would
want to do it the other way round in fact. It doesnt gain you anything
does it ?


The problem with mirroring partitions is that you thrash the disk
during the rebuild after replacing a failed disk.


Potentially, yes.


And the more partitions you have, the worse it gets.


One big mirrored partition avoids it, but then there's only one 
partition.  (ad0p2a?  Forget I mentioned that.)



If you mirror the device, then the rebuild process only has to rebuild
a single thing.

If you mirror 4 partitions on a device, then there will be four
simultaneous, parallel rebuild processes running, thrashing the drive
heads on both devices, killing you I/O throughput and extending the
length of the rebuild.


Some queuing logic in the mirror rebuild could avoid that.  I am 
blissfully unaware of how complicated that might be.___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: New BSD Installer

[Warren Block]

On Thu, 16 Feb 2012, Jeremy Chadwick wrote:

On Fri, Feb 17, 2012 at 01:08:28AM +0100, Miroslav Lachman wrote:


Please don't mix two things together. gpart can replace fdisk and
bsdlabel, but GPT vs. MBR is a different thing. GPT doesn't play
nice with GEOM classes which store their metadata on last sector.
For example, you can't use gmirror of a whole drives and use GPT on
top of this mirror. (and gmirror is not the only one)


This is quite possibly the most concise, clearest definition of a major
(borderline catastrophic) situation pertaining to GPT + GEOM
combinations.

I'm going to be more bold than usual: who is fixing this, and when is it
going to be MFC'd to 9, 8, and probably 7 would be a good idea?  If
nobody is fixing this, someone had better light a fire under someone's
ass to fix it.  I'm absolutely amazed this is still a problem.


How can it be fixed?  GPT only has two points of reference, the start 
and end of the disk.  To do more it would have to be aware of a lot of 
possible disk formats.


On the other hand, GEOM stuff works inside GPT partitions.  And if 
that's not acceptable, MBR partitions will be around for a long time.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: New BSD Installer

[Warren Block]

On Thu, 16 Feb 2012, Jeremy Chadwick wrote:


On Thu, Feb 16, 2012 at 06:34:53PM -0700, Warren Block wrote:


(...Linux mdadm)

So for version 0.90 of their metadata format, you lose drive capacity by
about 64-128KBytes, given that the space is needed for metadata.  For
version 1.0, I'm not sure.  For version 1.1 it looks like the metadata
can be stored at the beginning.

So overall, this sounds to me like the equivalent of if GEOM was to
lie about the actual capacities of the devices when using classes that
require use of metadata (gmirror, etc.).


Sorry, I may be misunderstanding your point.  GEOM classes don't lie, 
they accurately represent the space.  The space provided by a gmirror is 
one block less than the actual space occupied, to allow for the metadata 
block at the end.  The problem is that GPT puts backup partition tables 
at the end of the physical (not logical) device. Create a GEOM device on 
that drive, and the GEOM metadata overwrites the backup GPT partition 
table.  Well, the last block of it, anyway.


But create the GEOM device inside a GPT partition that spans the drive, 
and things are fine.  The GPT backup tables are safely outside the GEOM 
metadata, which is safely outside of the data.


Short-form: GPT tables are at the absolute start and end of the physical 
disk.  GEOM metadata is relative, at the end of the logical device, not 
necessarily the end of the physical device.



On the other hand, GEOM stuff works inside GPT partitions.  And if
that's not acceptable, MBR partitions will be around for a long
time.


MBR partitions don't scale past 2TB.  Arguing that use of MBR is an
acceptable workaround is the equivalent to burying one's head in the
sand.  Let's try to accept the future, not feign ignorance.


I wasn't recommending it.  If putting GEOM data inside GPT partitions 
isn't acceptable (but why not?), there's the alternative of not using 
any partitioning at all.  Create the GEOM device on the bare drive using 
the full space.  Of course it won't boot...

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: New BSD Installer

[Warren Block]

On Thu, 16 Feb 2012, Jeremy Chadwick wrote:


On Thu, Feb 16, 2012 at 07:40:35PM -0700, Warren Block wrote:

On Thu, 16 Feb 2012, Jeremy Chadwick wrote:


On Thu, Feb 16, 2012 at 06:34:53PM -0700, Warren Block wrote:


(...Linux mdadm)

So for version 0.90 of their metadata format, you lose drive capacity by
about 64-128KBytes, given that the space is needed for metadata.  For
version 1.0, I'm not sure.  For version 1.1 it looks like the metadata
can be stored at the beginning.

So overall, this sounds to me like the equivalent of if GEOM was to
lie about the actual capacities of the devices when using classes that
require use of metadata (gmirror, etc.).


Sorry, I may be misunderstanding your point.  GEOM classes don't
lie, they accurately represent the space.  The space provided by a
gmirror is one block less than the actual space occupied, to allow
for the metadata block at the end.  The problem is that GPT puts
backup partition tables at the end of the physical (not logical)
device. Create a GEOM device on that drive, and the GEOM metadata
overwrites the backup GPT partition table.  Well, the last block of
it, anyway.

But create the GEOM device inside a GPT partition that spans the
drive, and things are fine.  The GPT backup tables are safely
outside the GEOM metadata, which is safely outside of the data.


I wasn't aware you could do that.  I was only aware that it was the
other way around.  That (my) misconception seems to also be relayed
by others such as Miroslav who said:


GPT doesn't play nice with GEOM classes which store their metadata
on last sector.  For example, you can't use gmirror of a whole drives
and use GPT on top of this mirror. (and gmirror is not the only one)


So if I read this correctly, it means that the erroneous behaviour is
the result of someone doing things in the wrong order (for lack of
better terminology).


Yes, or the misconception that GPT behaves the same way as GEOM 
classes.  (Which isn't helped by both GPT and gpart 
coincidentally starting with a g.)



However, with the methodology you describe (GEOM device inside a GPT
partition), are our bootloader bits (BTX, etc.) smart enough to figure
this out and thus be able to boot/load kernel/so forth from such a
device?


gptboot does not see the mirror, but will boot from one of the mirrored 
drives.  Since the drives are identical, that works.  A smart boot 
loader that could handle other GEOM classes is possible.


One disadvantage is that identical partitions have to be created 
manually on both drives and then mirrored rather than creating a mirror 
and creating a single set of partitions on it.


ae@ has an article on GPT and gmirror:
http://translate.google.com/translate?js=nprev=_thl=enie=UTF-8layout=2eotf=1sl=autotl=enu=http%3A%2F%2Fbu7cher.blogspot.com%2F2011%2F03%2Ffreebsd-gmirror-gpt-ufs.htmlact=url

And so do I:
http://www.wonkity.com/~wblock/docs/html/gmirror.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FreeBSD 8.2-stable: devd fails to restart

[Warren Block]

On Tue, 7 Feb 2012, Torfinn Ingolfsen wrote:


On Mon, 06 Feb 2012 00:08:55 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:


On Sat, 4 Feb 2012, Torfinn Ingolfsen wrote:


On Sat, 04 Feb 2012 10:34:19 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:



Possibly relevant:
http://www.freebsd.org/cgi/query-pr.cgi?pr=140462cat=

(Using DHCP from /etc/rc.conf leaves a lock on devd.pid.  SYNCDHCP does
not.)

And the thread:
http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html


Yes, it seems to be that problem. Tested on my other machine, which hasn't 
changed since the problem was discovered:
root@kg-v7# service devd status
devd is not running.
root@kg-v7# ll /var/run/devd.pid
-rw---  1 root  wheel  3 Jan 12 20:40 /var/run/devd.pid
root@kg-v7# lsof /var/run/devd.pid
COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
dhclient 1075  root5w  VREG   0,703 918547 /var/run/devd.pid
dhclient 1091 _dhcp5w  VREG   0,703 918547 /var/run/devd.pid
root@kg-v7#

So, if this was worked on back in 2009, why isn't fixed yet?


I switched to using SYNCDHCP which avoids the problem, didn't enter a
PR, and quickly forgot about it.  It would be nice to have it fixed.


I'm all for getting it fixed, even if I don't know how yet.
Should a PR be against devd, dhclient, or ... something else?


It's devd, IMO.  Hey, come to think of it, I did enter a PR, the one 
above.  If this is still a problem in 9 (which I can test in a bit), 
posting to -current might get some needed attention on it.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ld: kernel.debug: Not enough room for program headers

[Warren Block]

8-stable i386 is building again.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FreeBSD 8.2-stable: devd fails to restart

[Warren Block]

On Sat, 4 Feb 2012, Torfinn Ingolfsen wrote:


On Sat, 04 Feb 2012 10:34:19 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:



Possibly relevant:
http://www.freebsd.org/cgi/query-pr.cgi?pr=140462cat=

(Using DHCP from /etc/rc.conf leaves a lock on devd.pid.  SYNCDHCP does
not.)

And the thread:
http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html


Yes, it seems to be that problem. Tested on my other machine, which hasn't 
changed since the problem was discovered:
root@kg-v7# service devd status
devd is not running.
root@kg-v7# ll /var/run/devd.pid
-rw---  1 root  wheel  3 Jan 12 20:40 /var/run/devd.pid
root@kg-v7# lsof /var/run/devd.pid
COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
dhclient 1075  root5w  VREG   0,703 918547 /var/run/devd.pid
dhclient 1091 _dhcp5w  VREG   0,703 918547 /var/run/devd.pid
root@kg-v7#

So, if this was worked on back in 2009, why isn't fixed yet?


I switched to using SYNCDHCP which avoids the problem, didn't enter a 
PR, and quickly forgot about it.  It would be nice to have it fixed.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FreeBSD 8.2-stable: devd fails to restart

[Warren Block]

On Sat, 4 Feb 2012, Torfinn Ingolfsen wrote:


More data:
root@kg-v2# service devd status
devd is not running.
root@kg-v2# service devd start
Starting devd.
devd: devd already running, pid: 808
/etc/rc.d/devd: WARNING: failed to start devd
root@kg-v2# rm /var/run/devd.pid
root@kg-v2# service devd start
Starting devd.
root@kg-v2# service devd status
devd is running as pid 30165.
root@kg-v2# service devd stop
Stopping devd.
root@kg-v2# service devd status
devd is not running.
root@kg-v2# ll /var/run/devd.pid
-rw---  1 root  wheel  5 Feb  4 16:45 /var/run/devd.pid
root@kg-v2# service devd start
Starting devd.
root@kg-v2# service devd status
devd is running as pid 30206.

Let me try to install the webcamd port again... done.
Now testing again:
root@kg-v2# service devd status
devd is running as pid 30206.
root@kg-v2# service devd stop
Stopping devd.
root@kg-v2# ll /var/run/devd.pid
-rw---  1 root  wheel  5 Feb  4 16:48 /var/run/devd.pid
root@kg-v2# service devd status
devd is not running.
root@kg-v2# service devd start
Starting devd.
root@kg-v2# service devd status
devd is running as pid 35551.

Not really sure what's going on here.


Possibly relevant:
http://www.freebsd.org/cgi/query-pr.cgi?pr=140462cat=

(Using DHCP from /etc/rc.conf leaves a lock on devd.pid.  SYNCDHCP does 
not.)


And the thread:
http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org