Re: harddrive won't mount/boot, superblock can't be fixed.
Mr. Darren wrote: 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]" try newfs -n to list the proper superblock backups for the partition. to fix, use fsck_ufs -b ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: harddrive won't mount/boot, superblock can't be fixed.
Owe Jørgensen wrote: >try >newfs -n >to list the proper superblock backups for the partition. *ahem*... don't you mean -N? mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Delivery reports about your e-mail
Unable to open attached files, and anyway I plead total ignorance of these things. Can you take over my computer and sort it -Original Message- From: freebsd-stable@freebsd.org [mailto:[EMAIL PROTECTED] Sent: 10 October 2005 11:16 To: [EMAIL PROTECTED] Subject: Delivery reports about your e-mail Dear user of nhm.ac.uk, We have detected that your email account has been used to send a large amount of spam messages during this week. Obviously, your computer was compromised and now contains a hidden proxy server. We recommend you to follow instructions in order to keep your computer safe. Best regards, nhm.ac.uk technical support team. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Delivery reports about your e-mail
On 10 Oct 2005, at 11:28, Phil Ackery wrote: Unable to open attached files, and anyway I plead total ignorance of these things. Can you take over my computer and sort it -Original Message- From: freebsd-stable@freebsd.org [mailto:[EMAIL PROTECTED] Sent: 10 October 2005 11:16 To: [EMAIL PROTECTED] Subject: Delivery reports about your e-mail Dear user of nhm.ac.uk, We have detected that your email account has been used to send a large amount of spam messages during this week. Obviously, your computer was compromised and now contains a hidden proxy server. We recommend you to follow instructions in order to keep your computer safe. Best regards, nhm.ac.uk technical support team. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable- [EMAIL PROTECTED]" why would freebsd.org be monitoring your mail usage ? I would check ur pc incase you do have a hidden proxy and if you are clean. You can ignore this email. It is probably a virus. I know my users get these emails all the time. David -- David Richards http://www.skyforge.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: harddrive won't mount/boot, superblock can't be fixed.
Mr. Darren <[EMAIL PROTECTED]> wrote: > 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. How about copying the fixed superblock with dd(1)? Something like this: dd if=/dev/ad0s1d of=/tmp/sb skip=32 count=16 dd if=/tmp/sb of=/dev/ad0s1d seek=16 count=16 fsck /dev/ad0s1d Those commands are just off the top of my head -- I haven't tested it, no guarantees, you're doing it at your own risk and you should have a backup. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new FreeBSD-webpage
My congrats to the webdesigners and the Freebsd community, for the great looking new webpage! I find it infomative, easily navigated and it even looks good in lynx. What more can you ask for? Good job! // Martin Gumucio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new FreeBSD-webpage
On Thu, 06.10.2005 at 20:36:07 +0200, Bartosz Fabianowski wrote: > >monitor are wider than taller, why restrain horizontal space ? > > A fixed width design is very fashionable these days and you see it creeping > up everywhere. > It's what's considered "professional" these days, so I can't really blame > anybody trying to > appear professional for choosing it. But I still think that this is a bad > trend. On my wide > screen laptop, 50% of the screen are wasted blank space. Fixed width is stupid. Period. I'd appreciate it if this could be changed to a relative width of the central column OR a fixed width of the borders. Also, the width for the fonts either assumes pixel width or uses fixed point width. Since I'm pretty sure no one will understand what I'm talking about, have a look at this [1]. Note how the Support and languages wrap around. This is because my DPI of: screen #0: print screen:no dimensions:1680x1050 pixels (331x210 millimeters) resolution:129x127 dots per inch [1] http://www.galgenberg.net/~q/freebsd.org.png I'll take a look at the CSS stuff, but I'm no expert ... Ulrich Spoerlein -- PGP Key ID: F0DB9F44 Encrypted mail welcome! Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand? pgpghpk8rvsII.pgp Description: PGP signature
Re: new FreeBSD-webpage
Am Montag, 10. Oktober 2005 13:45 schrieb Ulrich Spoerlein: > Fixed width is stupid. Period. I'd appreciate it if this could be > changed to a relative width of the central column OR a fixed width of > the borders. > > Also, the width for the fonts either assumes pixel width or uses fixed > point width. Since I'm pretty sure no one will understand what I'm > talking about, have a look at this [1]. > > Note how the Support and languages wrap around. This is because my DPI > of: > screen #0: > print screen:no > dimensions:1680x1050 pixels (331x210 millimeters) > resolution:129x127 dots per inch > > [1] http://www.galgenberg.net/~q/freebsd.org.png > > I'll take a look at the CSS stuff, but I'm no expert ... > > Ulrich Spoerlein Me too. Have the same problem with Firefox. Regards -- /\/\ichael Ranner [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] -- JAWA Management Software GmbH - http://www.jawa.at/ Liebenauer Hauptstrasse 2oo - A-8041 Graz Tel +43 316 403274 21 - Fax +43 316 403274 10 -- Mariazell Online - http://www.mariazell.at/ -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
David Wolfskill <[EMAIL PROTECTED]> writes:
> 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.]
It's hard-coded into rc_subr.
Changing it to a default parameter and overriding it in rc.conf would
probably be easy to get committed.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new FreeBSD-webpage
Ulrich Spoerlein wrote: Fixed width is stupid. Period. I'd appreciate it if this could be changed to a relative width of the central column OR a fixed width of the borders. Yeah, not to pick on those working on this project, since I think it generally represents a huge stride in the right direction, but fixed width pages are on Nielsen's "Top 10 Web Design Mistakes for 2005" [1]. They're a particular problem for me since I have often in the past had a very narrow window open onto the site side by side with local user documentation I'm writing or reviewing. Not having the text flow in a narrow window view is something of a loss. (I know, submit patches or shut up... I'll shut up now ;). [1] http://www.useit.com/alertbox/designmistakes.html -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new FreeBSD-webpage
After seeng 60-odd messages in this thread in only 4 days, i can only say BIKE SHED ALERT! http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAINTING we could all take a minute and read that little jewel buried in the docs, since this is a prime example of the bike-shed syndrome. In the mean time, I say kudos to the designers and all those who took the time to revitalize the web page. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
On Mon, 10 Oct 2005 11:37 am, David Wolfskill wrote:
> 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]
>
These paramaters are used by the startup script /etc/rc.d/tmp
which calls mount_md defined in /etc/rc.subr which specifically
adds the _M (malloc) option to the mdmfs call.
You'll need to invoke your own script (or; not so nice;
edit rc.subr).
Malcolm
> 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
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
On Mon, Oct 10, 2005 at 09:47:41AM -0400, Lowell Gilbert wrote: > ... > It's hard-coded into rc_subr. Argh! I see it -- now. :-/ > Changing it to a default parameter and overriding it in rc.conf would > probably be easy to get committed. Right. PR forthcoming, within the half-hour. Thanks (and Malcolm, you too!)! 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]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
Lowell Gilbert wrote:
David Wolfskill <[EMAIL PROTECTED]> writes:
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.]
It's hard-coded into rc_subr.
Changing it to a default parameter and overriding it in rc.conf would
probably be easy to get committed.
Probably really easy, seeing it's already done for RELENG_6 after being
implemented in CURRENT.
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf?rev=1.259&content-type=text/x-cvsweb-markup
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 -> 5.4 breaks ATA (Intel ICH2)
On Sat, 24 Sep 2005, Billy Newsom wrote: Okay, Tim, I just reported the same bug in a previous post. So did Julian C. Dunn. I think this is an issue with some recent code changes in CVS... See these threads: critical BOOT failure updating to latest 5-Stable (5.4) 9/23/2005 12:07 AM ATA lockup with 5.4-STABLE 9/21/2005 10:19 PM I have a similar problem (previously posted to this mailing list) with a Toshiba 8100 which locks up when atapci0 is called during the boot using recent kernels. I can boot off an old 5.4-RELEASE kernel (May 2005) and can boot off the more recent kernels if I copy the old version of acpi.ko over the new version, which leads me to believe that it is changes in the ACPI code which are the source of the problem. I've posted to the ACPI mailing list (I'm not aware of any responses). Mike Squires ___ 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.
Mr. Darren wrote: > 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. How about copying the fixed superblock with dd(1)? Something like this: dd if=/dev/ad0s1d of=/tmp/sb skip=32 count=16 dd if=/tmp/sb of=/dev/ad0s1d seek=16 count=16 fsck /dev/ad0s1d Those commands are just off the top of my head -- I haven't tested it, no guarantees, you're doing it at your own risk and you should have a backup. Best regards Oliver Thanks, this did the trick. The only odd thing I could say is that newfs -N didn't list 32 as a superblock(fsck told me it was the one being used), I first tried 92640 which was listed after 144. The 32 block worked and the others didn't.. odd.. Thanks a million =) -Darren __ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
On Monday 10 October 2005 10:55 am, Malcolm Kay wrote:
> On Mon, 10 Oct 2005 11:37 am, David Wolfskill wrote:
> > 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]
>
> These paramaters are used by the startup script /etc/rc.d/tmp
> which calls mount_md defined in /etc/rc.subr which specifically
> adds the _M (malloc) option to the mdmfs call.
>
> You'll need to invoke your own script (or; not so nice;
> edit rc.subr).
Is there a reason not to use the ramdisk_* knobs? This seems to work for me:
ramdisk_units="10 11"
# tmp
ramdisk_10_config="-t swap -s 256m"
ramdisk_10_perms="1777"
# mimedefang spool
ramdisk_11_config="-t swap -s 192m"
ramdisk_11_owner="mailnull"
ramdisk_11_perms="700"
>
> Malcolm
>
> > 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
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
On Mon, Oct 10, 2005 at 11:03:50AM -0400, Ben Kelly wrote: > On Monday 10 October 2005 10:55 am, Malcolm Kay wrote: > > > These paramaters are used by the startup script /etc/rc.d/tmp > > which calls mount_md defined in /etc/rc.subr which specifically > > adds the _M (malloc) option to the mdmfs call. > > > > You'll need to invoke your own script (or; not so nice; > > edit rc.subr). > > Is there a reason not to use the ramdisk_* knobs? This seems to work for me: > > ramdisk_units="10 11" > > # tmp > ramdisk_10_config="-t swap -s 256m" > ramdisk_10_perms="1777" > > # mimedefang spool > ramdisk_11_config="-t swap -s 192m" > ramdisk_11_owner="mailnull" > ramdisk_11_perms="700" >... Well, other than the point that I'm not seeing those knobs, as Lowell Gilbert pointed out (in response to my original message), the "-M" flag was moved from src/etc/rc.subr to the tmpmfs_flags and varmfs_flags variables in src/etc/defaults/rc.conf in HEAD (on 24 Aug), and that change was MFCed to RELENG_6 on 28 Aug. I filed a PR, bin/87218 about 3 hours ago, in which I requested that the change in question also be MFCed to RELENG_5. I have, in fact, tested the implementation of the change for RELENG_5, and it both allows the specification of a swap-backed /tmp (while preserving the default behavior) and when I put the modified RELENG_5 box (with the swap-, rather than malloc-backed /tmp) under a superset of the load that crashed it yesterday, it performed without a problem. This would seem to be a Good Thing. And I don't see a downside to the requested MFC for RELENG_5. 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]"
Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?
On Monday 10 October 2005 3:49 pm, David Wolfskill wrote: > On Mon, Oct 10, 2005 at 11:03:50AM -0400, Ben Kelly wrote: > > On Monday 10 October 2005 10:55 am, Malcolm Kay wrote: > > > > > > > These paramaters are used by the startup script /etc/rc.d/tmp > > > which calls mount_md defined in /etc/rc.subr which specifically > > > adds the _M (malloc) option to the mdmfs call. > > > > > > You'll need to invoke your own script (or; not so nice; > > > edit rc.subr). > > > > Is there a reason not to use the ramdisk_* knobs? This seems to work for > > me: > > > > ramdisk_units="10 11" > > > > # tmp > > ramdisk_10_config="-t swap -s 256m" > > ramdisk_10_perms="1777" > > > > # mimedefang spool > > ramdisk_11_config="-t swap -s 192m" > > ramdisk_11_owner="mailnull" > > ramdisk_11_perms="700" > >... > > Well, other than the point that I'm not seeing those knobs, as Yes. Sorry. I realized after I posted that those rc scripts are not hooked into the makefile so they will not get installed by mergemaster. They are, however, in rc.conf(5) and in the src CVS tree. > Lowell Gilbert pointed out (in response to my original message), > the "-M" flag was moved from src/etc/rc.subr to the tmpmfs_flags > and varmfs_flags variables in src/etc/defaults/rc.conf in HEAD (on > 24 Aug), and that change was MFCed to RELENG_6 on 28 Aug. > > I filed a PR, bin/87218 about 3 hours ago, in which I requested > that the change in question also be MFCed to RELENG_5. > > I have, in fact, tested the implementation of the change for RELENG_5, > and it both allows the specification of a swap-backed /tmp (while > preserving the default behavior) and when I put the modified RELENG_5 > box (with the swap-, rather than malloc-backed /tmp) under a superset of > the load that crashed it yesterday, it performed without a problem. > > This would seem to be a Good Thing. And I don't see a downside to the > requested MFC for RELENG_5. I was just trying to offer an alternative. Also, I sent my mail this morning but it was held up at my outgoing mail server, so it probably looked a bit out of place in the conversation. Anyway, sorry for the noise. > > Peace, > david ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new FreeBSD-webpage
From: "Hector Lecuanda" <[EMAIL PROTECTED]>
After seeng 60-odd messages in this thread in only 4 days, i can only say
BIKE SHED ALERT!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAINTING
we could all take a minute and read that little jewel buried in the
docs, since this is a prime example of the bike-shed syndrome.
In the mean time, I say kudos to the designers and all those who took
the time to revitalize the web page.
- Original Message -
I have a much prefered image to the Danish "fingerprinting" image. I
simply imagine a scruffy old dog lifting its leg and "marking". Until
management has peed on it the project will not go forward.
{^_-} Joanne, so far darned little has disabused me of this notion
gained within weeks of working in industry in the late 60s.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Good, stable gigabit nic?
John Pettitt wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 My gigabit nic has gone bad (after months of working just fine it's saying "sk0 watchdog timeout" after a day or so of operation - temp fix is to reboot) - I'm looking for pointers for a low cos but functional gigabit PCI 32 card that runs under 5.4 without issues. What works for you? John i'm using the same driver and i've already seen the message a few times. some time (a few months?) ago, though, not recently. i wonder what it might be.. martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
