Re: 8-stable -> 9-current upgrade

On 2011-09-08 02:12, Kevin Oberman wrote: > I've been looking for any information on any special steps required to > update from 8-stable to > 9-current. /usr/src/UPDATING is a bit out of date as it has > instructions for going from 5-stable > to "current", although the instruction may well be the

Re: Shared libraries version bump?

From: Kostik Belousov > The bump was done for BETA2, see r225227, done on 2011-08-28. > The bump has much less scope since we did the ABI analysis and > only bumped the libraries which interfaces changed in incompatible > way and which were not yet bumped. See the referenced commit for > the libr

Re: Shared libraries version bump?

> I think I'll rebuild all ports, and more, maybe I should make and keep > packages in case I can't update to BETA3 in place. If you want to be on the safe side, a complete rebuild is probably a good idea -- and moreover, one that removes all ports and cleans out ${PREFIX} and ${PKG_DBDIR} before

NFS server File Handle changing upon reboot

Hiroki Sato spotted a problem with NFS server file handles (FHs) changing after a server upgrade, because the exported file system type(s) get configured in a different order and, therefore, assigned different vfs_typenum values. A patch has been worked out, after discussion with various folks, th

Re: ath0 no longer attaches, cardbus problems?

On Wednesday, September 07, 2011 5:48:01 pm Daniel Eischen wrote: > On Wed, 7 Sep 2011, John Baldwin wrote: > > > On Wednesday, September 07, 2011 4:18:25 pm Daniel Eischen wrote: > >> On Tue, 6 Sep 2011, John Baldwin wrote: > >> > >>> On Tuesday, September 06, 2011 3:34:58 pm Daniel Eischen wrote

SSD - TRIM, SU and SUJ - Installer Options

Hi there, first off all I have to say, that your new Installer in FBSD v9.0 is very well done. I just found an option, which is not activated at this time. So I wanted to ask, if it’s possible a bug or something like that. I’ve tried to change the in the section Partition Editor with the subsect

Re: SSD - TRIM, SU and SUJ - Installer Options

I saw identical behavior a very long time ago but didn't have time to reproduce and report. It was very confusing. Regards, Mark ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, se

FreeBSD 9.0-BETA2 invalid ada0 layout prevents installation

Hi, Tried to install the BETA2 from a mem-stick onto a 250Gb disk. Which turned out to be used in a ZFS box. Since it does contain GPT info telling me ada0p1 was a freebsd-zfs partion. This however results in that I can not find any "normal" way in the guided and expert config menus to actual t

Re: 8-stable -> 9-current upgrade

On Thu, Sep 8, 2011 at 12:26 AM, Niclas Zeising wrote: > On 2011-09-08 02:12, Kevin Oberman wrote: >> I've been looking for any information on any special steps required to >> update from 8-stable to >> 9-current. /usr/src/UPDATING is a bit out of date as it has >> instructions for going from 5-st

Re: SSD - TRIM, SU and SUJ - Installer Options

On 09/08/11 16:22, mysph...@web.de wrote: Hi there, first off all I have to say, that your new Installer in FBSD v9.0 is very well done. I just found an option, which is not activated at this time. So I wanted to ask, if it’s possible a bug or something like that. I’ve tried to change the in t

Re: FreeBSD 9.0-BETA2 invalid ada0 layout prevents installation

On 08.09.2011 20:13, Willem Jan Withagen wrote: > This however results in that I can not find any "normal" way in the > guided and expert config menus to actual tell it to use the whole disk > for a new fresh FreeBSD install. > > it keeps complaining > Operation not permitted > 'ada0 table

Re: ath0 no longer attaches, cardbus problems?

On Thu, 8 Sep 2011, John Baldwin wrote: On Wednesday, September 07, 2011 5:48:01 pm Daniel Eischen wrote: On Wed, 7 Sep 2011, John Baldwin wrote: On Wednesday, September 07, 2011 4:18:25 pm Daniel Eischen wrote: Setting debug.acpi.disabled=hostres in /boot/loader.conf did not help. I tried

Re: ath0 no longer attaches, cardbus problems?

On Thursday, September 08, 2011 1:19:23 pm Daniel Eischen wrote: > On Thu, 8 Sep 2011, John Baldwin wrote: > > > On Wednesday, September 07, 2011 5:48:01 pm Daniel Eischen wrote: > >> On Wed, 7 Sep 2011, John Baldwin wrote: > >> > >>> On Wednesday, September 07, 2011 4:18:25 pm Daniel Eischen wrot

Re: 8-stable -> 9-current upgrade

2011/9/8 David Wolfskill : > On Wed, Sep 07, 2011 at 05:12:45PM -0700, Kevin Oberman wrote: >> ... >> I am particularly concerned with things like header files >> (/usr/include) that might bite me if not deleted. > > This isn't specific to that upgrade, but when I do a "make installworld", > I augm

Re: 8-stable -> 9-current upgrade

On Thu, Sep 08, 2011 at 07:59:59PM +0200, Olivier Smedts wrote: > ... > > I augment the instructions from UPDATING, prefixing the "make > > installworld" itself with: > > > > rm -fr /usr/include.old && mv /usr/include{,.old} && \ > > rm -fr /usr/share/man > > > > Thus, I have reasonable confidence

cvsup broken on amd64?

Hi, I have an Atom 330 with 9.0-BETA2/amd64 installed. I did a pkg_add -r cvsup-without-gui at first after installation. Using cvsup, resulted in a core dump (illegal instruction). I then removed all ports, and installed cvsup-without-gui from source. Started cvsup... core dump again. I then g

Re: Shared libraries version bump?

On Thu, Sep 8, 2011 at 4:42 AM, b. f. wrote: >> I think I'll rebuild all ports, and more, maybe I should make and keep >> packages in case I can't update to BETA3 in place. > > If you want to be on the safe side, a complete rebuild is probably a > good idea -- and moreover, one that removes all p

RE: Need a README to explain items in download directory

From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Chris Brennan > >On 9/3/2011 7:12 PM, Adam Vande More wrote: >> On Sat, Sep 3, 2011 at 6:00 PM, Craig Rodrigues > > wrote: >> >> For this line: >> >> (1) FreeBSD-

Re: ath0 no longer attaches, cardbus problems?

On Thu, 8 Sep 2011, John Baldwin wrote: On Thursday, September 08, 2011 1:19:23 pm Daniel Eischen wrote: I suspect you don't really need the pciconf -lb from before r220195 because r220195 works - ath attaches and is at the correct base address (0x8800). So the commit that broke ath/cardb

Re: cvsup broken on amd64?

> I have an Atom 330 with 9.0-BETA2/amd64 installed. > > I did a pkg_add -r cvsup-without-gui at first after installation. > Using cvsup, resulted in a core dump (illegal instruction). > > I then removed all ports, and installed cvsup-without-gui from source. > Started cvsup... core dump again. > >

Re: FreeBSD 9.0-BETA2 invalid ada0 layout prevents installation

Op 8 sep. 2011 om 19:00 heeft "Andrey V. Elsukov" het volgende geschreven: > On 08.09.2011 20:13, Willem Jan Withagen wrote: >> This however results in that I can not find any "normal" way in the >> guided and expert config menus to actual tell it to use the whole disk >> for a new fresh FreeB

Re: SSD - TRIM, SU and SUJ - Installer Options

Hello Nathan, thanks for your response. I thought the same, that the options are saved anyway, but in my test (with BETA2), if I don't reenter the options menu with my changed and saved values, the result anyway are the default values after continued os installation: # tunefs -p /dev/{SSD-devic

Re: Compiling BETA2 with clang fails

06.09.2011 17:44, Olivier Smedts wrote: You mean like fully rebuilding system with gcc and -march=athlon-xp and then try again? Like cleaning /usr/obj/ and then buildworld with clang but with "-march=athlon-xp" instead of "-march=native". As the problem does not seem to be in your current world

Re: cvsup broken on amd64?

Mike Tancsa wrote: Just curious as to why you need cvsup and not instead use csup that is in the base ? I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a statement that it will not work with FreeBSD

gmirror: how to make your system reboot

Hi, shouldn't there be a failsafe to not be able to destroy the gmirror as long as it is still in use like mounted? 1. create a gmirror with n>=1 disks 2. newfs the gmirror device 3. mount the gmirror device 4. remove all disks from the gmirror 5. system reboots (gmirror gone but still mounted)