Re: STABLE kernel fails to build on sys/fs/devfs/devfs_vnops.c

2005-10-09 Thread Marcin Koziej
> > I tried to build today's STABLE on 6.0-BETA2 FreeBSD 6.0-BETA2 #1: Wed Aug  
> > 3
> > Kernel config differs from GENERIC just by atapicam device.
> 
> Obviously, your userland and kernel sources are not synchronized. It is
> probably the cause of failed build.
> 
> Update complete source tree and try again.

It doesn't seem to be that simple to me.
I have rm -rf'ed all the sources and cvsupped with tag=RELENG_6 and 
I cannot build a GENERIC kernel. The problem seems to be forward declarations
of:
static struct vop_vector devfs_vnodeops;
static struct vop_vector devfs_specops;
static struct fileops devfs_ops_f;
which are initialized later in the code. The compiler flag -Wredundant-decls 
stops
on this. These declarations appeared in rev 1.114.2.4 of 
/src/sys/fs/devfs/devfs_vnops.c

I guess it must be something with my system because that change was on 18th of 
September. 
I use a normal compiler ( 3.4.4 [FreeBSD] 20050518) on 6.0-BETA2.


-- 
m.
Brain power of a glass of water.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: STABLE kernel fails to build on sys/fs/devfs/devfs_vnops.c

2005-10-09 Thread Jan Blaha
On  9.10.2005 00:41, Marcin Koziej wrote:
> > > I tried to build today's STABLE on 6.0-BETA2 FreeBSD 6.0-BETA2 #1:
> > > Wed Aug  3 Kernel config differs from GENERIC just by atapicam
> > > device.
> > 
> > Obviously, your userland and kernel sources are not synchronized. It
> > is probably the cause of failed build.
> > 
> > Update complete source tree and try again.
> 
> It doesn't seem to be that simple to me.
> I have rm -rf'ed all the sources and cvsupped with tag=RELENG_6 and 
> I cannot build a GENERIC kernel. The problem seems to be forward

OK, sorry I did not make myself clear. Do you follow the canonical way
of upgrading the system? It is important first make buildworld and after
this make buildkernel.

Can you reproduce the error with last RELENG_6 sources, cleaned contents
of /usr/obj and running the command "make buildworld buildkernel" in
/usr/src directory?

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

Regards,
Jan Blaha

-- 
Bombeck's Rule of Medicine:
Never go to a doctor whose office plants have died.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Disable hifn crypto card?

2005-10-09 Thread Emanuel Strobl
Am Samstag, 8. Oktober 2005 03:29 CEST schrieb Brandon Fosdick:
> I have a Soekris crypto card (hifn driver) in a box that I don't have
> immediate access to. Is there some way to disable the card w/o rebooting
> the machine? I know I could take the driver out of the kernel or force
> it not to load, but that requires a reboot that I'd like to avoid if
> possible. hifn is currently compiled into the kernel so I can't do a
> kldunload either. That was the first thing I thought of, but apparently
> today is not my lucky day.

If it's enough that ipsec won't make use of it you can see the sysctl:
net.inet.ipsec.crypto_support
I think -1 means no hw-crypto-support, 0 auto and 1 hw only, but I can't 
remember where I read about it to verify that ... :(

-Harry

>
> Thanks
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"


pgpB40uM0qWcg.pgp
Description: PGP signature


Re: FreeBSD binary upgrade / gmirror

2005-10-09 Thread Hector Lecuanda
I Could be wrong, but i believe that you dont have to disklabel your
GEOM devices on sysinstall.. just make sure you load the geom_mirror
module on your /boot/loader.conf file
(add geom_mirror_load="YES")
and mount the mirrored device...

Upon loading, the geom_mirror module will read the metadata on the
mirrored devices and will create the appropriate device (the one you
should mount)...

to be sure, after doing your upgrade, without labeling your disks
(dont touch them using sysinstall) just run

gmirror load

that will load the module and read your mirrored partitions.. all your
data should be there, and

gmirror status

will tell you what is the device you need to add to /etc/fstab

good luck!


On 10/8/05, rihad <[EMAIL PROTECTED]> wrote:
> I have a FreeBSD 5.3 box and its two HDD's are setup as one GEOM mirror
> unit /dev/mirror/gm0 (c.f. http://people.freebsd.org/~rse/mirror/). Now
> Now I want to do a binary upgrade to FreeBSD 5.4, but the new
> sysinstall's disklabel editor only recognizes the IDE disks and does not
> consider the GEOM mirror (mentioned in /etc/fstab, btw). How do I go
> about this? Thanks.
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>


--
-Hector Lecuanda
PGP Public Key / Llave Publica PGP:
http://lecuanda.com/pgp_pubkey.asc
http://lecuanda.com/pgp_pubkey.txt
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


5.x: how do I get a *swap*-backed /tmp via rc.conf?

2005-10-09 Thread David Wolfskill
I made the somewhat unexpected discovery that in FreeeBSD 5-STABLE,
if I use the "tmp*" variables in /etc/rc.conf to have an MFS /tmp
created, it is apparentyly not swap-backed -- as I expected from
the part of the mdmfs man page that reads:

 By default, mdmfs creates a swap-based (MD_SWAP) disk with soft-updates
 enabled and mounts it on mount-point.

and a review of the way mdmfs is invoked by /etc/rc; rather, it appears
to be malloc-backed.

Here's what's in /etc/{defaults/,}rc.conf about it on one such machine:

g1-59(5.4-S)[42] grep tmp /etc/{default*/,}rc.conf
/etc/defaults/rc.conf:tmpmfs="AUTO" # Set to YES to always create 
an mfs /tmp, NO to never
/etc/defaults/rc.conf:tmpsize="20m" # Size of mfs /tmp if created
/etc/defaults/rc.conf:tmpmfs_flags="-S" # Extra mdmfs options for the mfs /tmp
/etc/defaults/rc.conf:isdn_traceflags="-f /var/tmp/isdntrace0"  # Flags for 
isdntrace
/etc/defaults/rc.conf:clear_tmp_enable="NO" # Clear /tmp at startup.
/etc/rc.conf:tmpmfs="YES"
/etc/rc.conf:tmpsize="512m"
/etc/rc.conf:tmpmfs_flags="-i4096"
g1-59(5.4-S)[43] 

And:

g1-59(5.4-S)[43] sudo mdconfig -l -u md0
md0 malloc  524288 KBytes
g1-59(5.4-S)[44] 

Oh, for some sense of what we're working with:

g1-59(5.4-S)[44] uname -a
FreeBSD g1-59.catwhisker.org. 5.4-STABLE FreeBSD 5.4-STABLE #6: Sun Oct  9 
06:24:17 PDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP  i386
g1-59(5.4-S)[45] 

So, back to my original question:  how do I get a *swap*-backed /tmp?

[The way I was alerted to the possibliity that my /tmp might not
be swap-backed is that I was using a machine running 5-STABLE as a CVS
server, in order to update /usr/ports on another machine.  That's why I
have the -i4096 argument in there, BTW:  to double the number of inodes
for when the CVS server starts consuming them with wild abandon as it
builds an isomorphic hierarchy to /usr/ports in /tmp.  I think it only
took me 3 panics before I poked around in the mailing list archives and
noted scottl's comment about using a swap-backed /tmp instead, which got
me wondering what backing store my /tmp was using.  I did look at
/etc/rc.d/tmp, as well a /etc/rc.subr, but I'm still failing to see why
I'm getting a malloc-backed /tmp.  FWIW, although the /tmp in question
is an MFS in 4.x, I do this (use the box as a CVS server for /usr/ports)
without  problem on 4.x.]

(I don't need separate copies of any replies; I read -stable, so I set
Reply-To as an appropriate hint.)

Thanks.

Peace,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
Prediction is difficult, especially if it involves the future. -- Niels Bohr

See http://www.catwhisker.org/~david/publickey.gpg for public key.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


random ip id

2005-10-09 Thread Jeremy Baggs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

  I have a firewall with a small CF installation of FreeBSD 5.2.1
(post 20040814).  It is missing the sysctl variable:
net.inet.ip.random_id.  I am wondering if one of the libraries or
kernel objects I ripped out to minimize the install could be the
culprit for this.   Any clues would b e appreciated...


Thanks,
   Jeremy




 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDSek0ErogemV/I6ERAl5nAKDg6H8t5AcMwuIRUK6wRZ7t+Tj7KACbBRhP
bZLjix0mQiPt2jGBjgrBU0Q=
=Sry9
-END PGP SIGNATURE-

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: random ip id

2005-10-09 Thread Dan Nelson
In the last episode (Oct 09), Jeremy Baggs said:
> I have a firewall with a small CF installation of FreeBSD 5.2.1 (post
> 20040814).  It is missing the sysctl variable: net.inet.ip.random_id. 
> I am wondering if one of the libraries or kernel objects I ripped out
> to minimize the install could be the culprit for this.  Any clues
> would b e appreciated...

That sysctl was added in FreeBSD 5.3.  You may be able to get the same
functionality in 5.2.1 with the RANDOM_IP_ID kernel option, but you
should probably upgrade to 5.4.

-- 
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


harddrive won't mount/boot, superblock can't be fixed.

2005-10-09 Thread Mr. Darren
I had a bad ide cable which I have now replaced.  on
bootup the filesystem produced a lot of errors and I
lost my first superblock.  I since fsck'd and repaired
the superblock at sector 32.  At no time does fsck
create, fix, or transfer the sector 32 superblock to
the front of the drive.  mount won't accept the drive
in the condition it's in(says no superblock, or bad
superblock..  different programs, different errors). 
If anyone knows how I could get my data off and format
my /var drive, or possibly repair my damaged
superblock at the front of the drive with anyone of
the 50-some backups that exist throughout the drive.  

thanks

Darren




__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"