Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

2018-10-19 Thread Matthew D. Fuller
On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of
Don Lewis, and lo! it spake thus:
>
> The first is that when I attempt to start a Virtualbox VM, the
> system panics.

Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: drm2 in base

2018-09-28 Thread Matthew D. Fuller
On Fri, Sep 28, 2018 at 01:01:02PM -0700 I heard the voice of
Steve Kargl, and lo! it spake thus:
>
> How did you get around the "fence_wait returned with error -512"
> messages filling /var/log/messages.

Well, I never got them "filling" in a flooding sense.  I did get
regular bursts of them for a while (often video-related, I think), but
they never caused any visible problem.

The last I see in old messages files now is from July.  That might
have been when I switched it from stable->next?  Looking at the
mssages file, shortly after the reboot shortly following the last
fence, I see

Jul 20 21:19:47 cepheus pkg: drm-stable-kmod-g20180619_1 deinstalled
Jul 20 21:19:48 cepheus pkg-static: drm-next-kmod-4.11.g20180619_1 installed

and I haven't seen one since.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: drm2 in base

2018-09-28 Thread Matthew D. Fuller
On Fri, Sep 28, 2018 at 11:00:02AM -0700 I heard the voice of
Steve Kargl, and lo! it spake thus:
> 
> I have a radeon HD 6450 video card (CAICOS firmware), and have been
> informed that the hardware is too old for graphics/drm-stable-kmod
> and that I should use graphics/drm-legacy-kmod.  

Well, please don't tell that to the 6450 I've got running on
drm-next-kmod (which also spent some time on drm-stable)...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

2018-05-31 Thread Matthew D. Fuller
On Thu, May 31, 2018 at 03:49:46PM -0500 I heard the voice of
Mark Linimon, and lo! it spake thus:
> 
> We do slightly better turning over ports PRs -- due to the fact that
> we attach a maintainer field to each port.  This doesn't completely
> solve the problem, but it goes some distance.

>From my perspective as a maintainer of some and occasional contributor
to others, I think "slightly" undersells it a bit; hardly without
exception, but it generally works OK.

I wrote up a couple more paragraphs about why I think it happens and
what we'd need to do to import more of that sense over into src.  But
it was way longer than it needs to be.  We get a lot more man-hours in
ports/ acting as conduits for the "outside patches -> svn" pipeline
because the incentives are rigged.  A bad outside contribution brought
into ports more often yields "hey, you should have noticed" to the
committer and more opprobrium back to the submitter.  A bad outside
contribution brought into src falls all over the commiter.

Not entirely unreasonable, since a lot of even small-ish breakages in
src are much bigger deals than even large-ish breakages in ports.  But
it still makes it expensive to contemplate being a conduit...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

2018-03-11 Thread Matthew D. Fuller
On Sun, Mar 11, 2018 at 10:43:58AM -1000 I heard the voice of
Jeff Roberson, and lo! it spake thus:
> 
> First, I would like to identify whether the wired memory is in the
> buffer cache.  Can those of you that have a repro look at sysctl
> vfs.bufspace and tell me if that accounts for the bulk of your wired
> memory usage?  I'm wondering if a job ran that pulled in all of the
> bufs from your root disk and filled up the buffer cache which
> doesn't have a back-pressure mechanism.

If by "root disk", you mean the one that isn't ZFS, that wouldn't
touch anything here; apart from a md-backed UFS /tmp and some NFS
mounts, everything on my system is ZFS.

I believe vfs.bufspace is what shows up as "Buf" on top?  I don't
recall it looking particularly interesting when things were madly
swapping.  I'll uncork arc_max again for a bit and see if anything odd
shows up in it, but it's only a dozen megs or so now.



-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

2018-03-06 Thread Matthew D. Fuller
On Mon, Mar 05, 2018 at 02:39:18PM -0600 I heard the voice of
Larry Rosenman, and lo! it spake thus:
> 
> Yesterday, and I'm seeing really strange slowness, ARC use, and SWAP
> use and swapping.
> 
> Ideas?

Since I updated to the Feb 25 -CURRENT I'm currently running (from
mid-Sept, I believe), I see similar.  It seems like the ARC has gotten
really unwilling to yield, so it grows up in size, and then doesn't
let up under pressure.  I saw programs being actively used constantly
swapping their working set in and out, since they were left with tiny
available memory.

Hard-slappping vfs.zfs.arc_max down a ways mitigated it enough to get
me through the days, but is a pretty gross hackaround...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Shared object "libelf.so.2" not found, required by "libkvm.so.6"

2015-11-30 Thread Matthew D. Fuller
On Mon, Nov 30, 2015 at 11:39:49AM +0200 I heard the voice of
Konstantin Belousov, and lo! it spake thus:
> 
> I do not know what is the best way to handle it. Most simple is to
> move libelf to /lib. How feasible is to move libkvm to /usr/lib (and
> all stuff in / which needs libkvm) is the open question.

To gild the moderately obvious, I question if we should just mask all
related problems forever, by just giving up tracking and moving
_everything_ into /lib.

According to du -A, /usr/lib/lib*.so* on my system is 11 meg.  /lib is
currently 9.4, so it's only about doubling the size.
/boot/kernel/kernel is 25, so the whole combined set is still smaller
than the kernel itself, never mind + the modules.

For that matter, everything under /usr/lib minus the .a files and the
debug/ tree is still only about 33 meg, so even if the net really
needs to be cast wider than lib*.so* (and it's not like we'd need to
move the symlinks themselves anyway), it can't spread very far.
Certainly we shouldn't be cavalier about blowing up the size of / for
no reason, but we're talking a pretty small increment.  Compared to
the kernel debug symbols before they got moved, it's miniscule.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CAM Shingled Disk support patches available

2015-11-19 Thread Matthew D. Fuller
On Wed, Nov 18, 2015 at 12:13:09PM -0500 I heard the voice of
Kenneth D. Merry, and lo! it spake thus:
> 
> Testing and comments are welcome.

GELI does explicit handling of each BIO type, so will need to be
updated to pass it through (possibly in the form of inverting the
default handling?) or it'll just EOPNOTSUPP it, whether the underlying
layer does or not.  I wouldn't be surprised if there were other geom
layers that did similar things.

Not meant to be read as some kind of "you need to"; just a comment on
a possible [lack of] impact.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: geli panics my system after suspend-resume: g_eli_orphan_spoil_assert() called for cd0.eli

2015-06-13 Thread Matthew D. Fuller
[ Redirect to -geom, bcc'd to -current for transition ]

On Sat, Jun 13, 2015 at 04:10:38PM +0200 I heard the voice of
José García Juanino, and lo! it spake thus:
 Hi FreeBSD current,
 
 I get a reproducible panic following these steps:
 
 1- Mount a geli encrypted DVD:

[...]

 4- Open again the lid a wait. The system resumes, but panics after a
 few seconds:
 
 panic: Function g_eli_orphan_spoil_assert() called for cd0.eli.

This is presumably what's hooked up in g_eli_create():

/*
 * Spoiling cannot happen actually, because we keep provider open for
 * writing all the time or provider is read-only.
 */
gp-spoiled = g_eli_orphan_spoil_assert;


The backtrace makes me think that coming out of resume will cause a
media change event on the cd0 device, which sounds a _little_ odd, but
may be necessary due to Stupid Reality Crap.  That pushes a spoil
event down to g_eli.  And g_eli seems to assume that can't happen to
a thing it's got around an open.


With the caveat that I'm no expert on ELI or GEOM, and any advice I
might give could just be the trigger for a nasal demon invasion of our
world, one thing you might try is taking that event as a hint to just
blow away the .eli device; treat it like an orphan.  So changing that
callback to using the g_eli_orphan func instead.  e.g., something like

Index: g_eli.c
===
--- g_eli.c (revision 284359)
+++ g_eli.c (working copy)
@@ -730,7 +730,7 @@ g_eli_create(struct gctl_req *req, struct g_class
 * Spoiling cannot happen actually, because we keep provider open for
 * writing all the time or provider is read-only.
 */
-   gp-spoiled = g_eli_orphan_spoil_assert;
+   gp-spoiled = g_eli_orphan;
gp-orphan = g_eli_orphan;
gp-dumpconf = g_eli_dumpconf;
/*

(not even remotely tested; beware of leopard)


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: how do I downgrade from 11-current to 10-stable

2015-05-31 Thread Matthew D. Fuller
On Sun, May 31, 2015 at 04:20:42PM -0700 I heard the voice of
Kevin Oberman, and lo! it spake thus:
 
 Unfortunately the list ends at 9.0. It would be nice if it could be
 updated. I might sift through SVN and see if I can put together a patch for
 10.2. It is quite likely that the version has not changed since 9.0.

In -CURRENT, it has a line for version 7 in 10.0 added in r265950
(apparently after the stable/10 branch point; the actual v7 support
was a year before that), that was seemingly never MFC'd.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: how do I downgrade from 11-current to 10-stable

2015-05-31 Thread Matthew D. Fuller
On Sun, May 31, 2015 at 04:35:35PM -0700 I heard the voice of
Garrett Cooper, and lo! it spake thus:
 
 V7 support was never MFCed to stable/9. It’s in stable/10 and newer
 and was included in 10.0-RELEASE:

Right, but it's not listed in 10.0's (or stable/10's) geli.8; _that_
rev was never MFC'd:


r265950 | thomas | 2014-05-13 10:46:52 -0500 (Tue, 13 May 2014) | 5 lines

Add mention of metadata version 7 in FreeBSD 10.0

Reviewed by:pjd
MFC after:  1 day




-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [HEADSUP] pkg(8) is now the only package management tool

2014-09-01 Thread Matthew D. Fuller
On Tue, Sep 02, 2014 at 03:51:31AM +0200 I heard the voice of
Michelle Sullivan, and lo! it spake thus:

 Correct, take a 9.2 install disk, install it, portsnap and then
 install pkg on it...  Oh wait, you can't.. pkg_install is broken,
 and 9.2 install disks don't have pkg in the BaseOS

So what?  The pkg port uses _ITSELF_ to register.  The pkg in the
base system isn't pkg, it just a bootstrap to fetch the pkg pkg (which
them uses itself to register too).  If you're using the pkg _PORT_,
it's not even involved in the first place.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Boot loader too large with Aug-11 FreeBSD/i386 11-CURRENT snapshot

2014-08-23 Thread Matthew D. Fuller
On Sat, Aug 23, 2014 at 09:02:10AM +0200 I heard the voice of
Joel Dahl, and lo! it spake thus:
 
 Today I installed 11-CURRENT from the 20140811 FreeBSD/i386 snapshot
 on my IBM T43 laptop but encountered some problems. The memstick
 installation went fine and I pretty much used default values
 everywhere, but upon reboot I got ”Boot loader too large”. Nothing
 more. Any ideas?

The freebsd-boot partition is bigger than five hundred twenty-mumble
k.  It'll be OK if you squeeze it down to 512.  Somthing like 'gpart
resize -i 1 -s 512k ada23' (untested, sub your disk).


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Boot loader too large

2014-07-11 Thread Matthew D. Fuller
On Fri, Jul 11, 2014 at 03:38:56PM -0700 I heard the voice of
Nathan Whitehorn, and lo! it spake thus:

 I don't honestly remember where that number came from. It's at line
 72 of usr.sbin/bsdinstall/partedit/partedit_x86.c. If 128 works
 better, I'm happy to change it, but it would be nice to know what
 the actual bounds here are before putting in a new arbitrary number.

src/sys/boot/i386/pmbr/pmbr.s says

-
next_boot:. incl (%si). .   .   # Next LBA
.   .   adcl $0,4(%si)
.   .   mov %es,%ax..   .   # Adjust segment for next
.   .   addw $SECSIZE/16,%ax.   .   #  sector
.   .   cmp $0x9000,%ax..   .   # Don't load past 0x9,
.   .   jae err_big..   .   #  545k should be enough for
.   .   mov %ax,%es..   .   #  any boot code. :)
-

(err_big being printing the Boot loader too large message).  Though
0x9 is actually 576k, not 545, but presumably there's some other
adjustment lopping off bits somewhere; that's 62 sectors diff.

Regardless, I settled on 512k for my boot partitions (after finding
the above error when I previously decided it's a few dozen k, I'll
just set aside a meg to be safe and then discovered the whole
not-booting thing that caused.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: CURRENT: why is CURRENT swapping so fast?

2014-06-14 Thread Matthew D. Fuller
On Sat, Jun 14, 2014 at 01:12:08AM +0200 I heard the voice of
Mark Martinec, and lo! it spake thus:

 The situation does not improve by itself, ARC has it all, less
 active jobs scramble and fight for whatever free memory is left for
 them and most of them remain swapped out. The best curse of action
 to recover is to reboot. Quite a pain.

You may want to check out
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187594 which I
believe is related.  Make sure you get the latest patch rather than
the older one, ref's in comment 10 at
http://www.denninger.net/FreeBSD-Patches/arc-patch.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS secondarycache on SSD problem on r255173

2014-06-06 Thread Matthew D. Fuller
On Fri, Apr 25, 2014 at 08:26:52PM -0500 I heard the voice of
Matthew D. Fuller, and lo! it spake thus:
 On Mon, Mar 03, 2014 at 11:17:05AM +0200 I heard the voice of
 Andriy Gapon, and lo! it spake thus:
  
  I noticed that on some of our systems we were getting a clearly
  abnormal number of l2arc checksum errors accounted in l2_cksum_bad.
  [...]
  I propose the following patch which has been tested and seems to fix
  the problem without introducing any side effects:
 
 I've been running this for 2 weeks now without any cksum_bad's
 showing up (long enough that without it, I'd have expected them),
 and no other obvious side effects.

Another 6 weeks on, still working fine and still seems to fix the
issue.  Any reason not to commit it?


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Fresh-install from -current snapshot: Boot loader too large

2014-05-08 Thread Matthew D. Fuller
On Thu, May 08, 2014 at 10:24:01AM +0200 I heard the voice of
Jeremie Le Hen, and lo! it spake thus:
 
 On the first boot I get the following error message:
 Boot loader too large

As I recall, this comes from the freebsd-boot partition being too big,
where too big is some unround number like 540k or something odd like
that.  Make sure that partition is 512k or something smaller.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: newcons and beeping X

2014-05-01 Thread Matthew D. Fuller
 A little investigation showed that the KDMKTONE ioctl handler was a
 complete stub, so anything X tried to do to ring the bell was
 completely unavailing.

Sub'd as http://www.freebsd.org/cgi/query-pr.cgi?pr=189170


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


newcons and beeping X

2014-04-27 Thread Matthew D. Fuller
I switched my workstation over to newcons today, and it worked just
fine, so yay.  After using it a while, it slowly dawned on me that I
wasn't making hardly any typing mistakes, nor was there any annoying
email coming in.  After all, if either were happing, I'd be getting
beeps; vt is making my life easier!  ...  wait...

A little investigation showed that the KDMKTONE ioctl handler was a
complete stub, so anything X tried to do to ring the bell was
completely unavailing.  Urg.  That's...  unpleasant.

From poking around in vt and comparing with syscons, I've come up with
the following patch which makes it work (as the couple beeps I've
spawned just writing this email show).  It's kinda fugly; should
probably be better factored, or less magic-numberized.  Possibly
vtterm_bell() should be able to take pitch/duration like sc_bell()
does.  But it's _much_ better than nothing; the bell should work!



Index: sys/dev/vt/vt_core.c
===
--- sys/dev/vt/vt_core.c(revision 264991)
+++ sys/dev/vt/vt_core.c(working copy)
@@ -1636,7 +1636,11 @@
 #endif
return (0);
case KDMKTONE:  /* sound the bell */
-   /* TODO */
+   if(*(int*)data)
+   sysbeep(1193182 / ((*(int*)data)0x),
+   (((*(int*)data)16)0x)*hz/1000);
+   else
+   vtterm_bell(tm);
return (0);
case KIOCSOUND: /* make tone (*data) hz */
/* TODO */



-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS secondarycache on SSD problem on r255173

2014-04-25 Thread Matthew D. Fuller
On Mon, Mar 03, 2014 at 11:17:05AM +0200 I heard the voice of
Andriy Gapon, and lo! it spake thus:
 
 I noticed that on some of our systems we were getting a clearly
 abnormal number of l2arc checksum errors accounted in l2_cksum_bad.
 [...]
 I propose the following patch which has been tested and seems to fix
 the problem without introducing any side effects:

I've been running this for 2 weeks now without any cksum_bad's
showing up (long enough that without it, I'd have expected them), and
no other obvious side effects.

FreeBSD 11.0-CURRENT #0 r264306M

So if there are votes, I vote for making it work without that 'M'  :)


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS secondarycache on SSD problem on r255173

2014-03-11 Thread Matthew D. Fuller
On Mon, Mar 03, 2014 at 11:17:05AM +0200 I heard the voice of
Andriy Gapon, and lo! it spake thus:
 
 I noticed that on some of our systems we were getting a clearly
 abnormal number of l2arc checksum errors accounted in l2_cksum_bad.
 The hardware appeared to be in good health.

FWIW, I have a system here where I see similar things; after
sufficient uptime it shows an impressive number and proportion of
checksum errors (50% or more of the hits, eventually), since at least
sometime last fall.  No indication anywhere else of problems (CAM,
SMART, zpool status).

Haven't tried the patches.  It would take most of a month of seeing
nothing to have much confidence they did anything anyway; it's got 2
weeks now and only ~500 errors, so it takes a long time with this
system/workload to ramp up.  But it'd be a nice fix to have, so mark
me up as a user-vote for landing if the code makes sense to the
codesense people.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: FreeBSD 10.0-RC3 Now Available

2013-12-27 Thread Matthew D. Fuller
On Fri, Dec 27, 2013 at 03:33:23PM +0100 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
 
 All you have to do is adapt it to run your particular setup,
 replacing da0 with the correct disk (and running it for each disk
 where your pool is, in my case, it was mfid0 and mfid1.)

I've taken to just dumping a rewrite-bootcode.sh script in /boot/ on
systems.  That way I don't have to remember or re-figure the
invocation, or worry about typos, or whatnot.  Makes it easy to just
kick the script after every installworld whether I really need it or
not, without having to think about it.

e.g.,

% cat /boot/rewrite-bootcode.sh
#!/bin/sh -x
for i in /dev/ada0 /dev/ada1; do
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ${i}
done


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: FreeBSD 10.0-RC3 Now Available

2013-12-27 Thread Matthew D. Fuller
On Fri, Dec 27, 2013 at 05:21:12PM +0100 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
 
 You *don't* need it after installworld, or freebsd-update install.
 You *only* need it if you *explicitly* run zpool upgrade
 yourzpool.

Well, that was my point; by removing the need to have to think about
how to do it, I can just do it any time I rebuild bootcode, whether I
need it or not.  Makes life simpler.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: svn commit: r255715 - head/usr.bin/calendar

2013-10-25 Thread Matthew D. Fuller
On Thu, Sep 19, 2013 at 08:17:50PM + I heard the voice of
Diane Bruce, and lo! it spake thus:
 
 Log:
   - calendar uses cpp internally, this diff removes this usage and
 substitutes a limited subset cpp processor internally.

(I'm sorta guessing at this change being the responsible one, but I
feel pretty safe about it.)

This gave my calendar output heartburn in two different ways.


Firstly, my ~/.calendar/calendar (which I'd long since forgotten even
existed; hadn't been touched since last millennium) had lines like

#include /usr/share/calendar/foo

which had worked fine previously, but now force-added the path to the
beginning, leading to a long list of

 38152 calendar NAMI /usr/share/calendar//usr/share/calendar/calendar.birthday

in the ktrace output.  It could reasonably be argued that it's
coloring outside the lines a bit, but the manpage still speaks as
though it should DTRT.

But the major upshot was that it didn't find any actual files, and so
calendar output nothing and exited without any errors or error code.
That part, doesn't seem so much right; it should at least say
SOMETHING, neh?


But with that tracked down and changed, it now started outputting
stuff.  Too much stuff.  Way too much stuff, in character sets my
xterm didn't know what to do with.  It turns out THAT was a result of
lines in the file like

/* #include calendar.croatian */

which cpp properly did nothing with, but the built-in parsing still
sees and processes.  That's definitely buggy...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: svn error during 'make buildkernel'?

2013-08-06 Thread Matthew D. Fuller
On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of
Glen Barber, and lo! it spake thus:
 
 The error generated is non-fatal, and once I receive response on a
 proposed patch, will be suppressed if the svn version used to check
 out the tree is not compatible with that used to check the version
 of the tree with the kernel build.

But not try the ports svn as well?  I mean, as breakage goes, it's not
even in the top 100; I'd _much_ rather have a kernel that I have to
guess the revision of but boots, than one properly recorded that
doesn't.  But it's still unpleasant, and is one of those things you
probably won't notice missing until suddenly you need it.

And this isn't just a presentism.  Sure, right _now_ devel/subversion
and base svnlite get along, but what happens when ports moves to 1.9
which changes the WT format?  Even if -CURRENT src gets upgraded
simultaneously[0], the same surely can't be said of every back branch.

I realize this is all still a WIP, and please don't read any anger
into my words.  But this _has_ been something I've found a little
worrisome since the original import/newvers change.  Heck, newvers can
show me version info if I'm getting my source tree from git or p4, but
can't handle ports svn?  By the time this works its way into a stable
branch, I really think it should either handle svnversion from ports
as well, or come with a big bright flashing warning that using svn
from anything but base svnlite for /usr/src is a degraded experience.


[0] Which still wouldn't really fix things, since
/usr/bin/svnliteversion is arbitrarily old, not up to date with
the source tree.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Question about portsdb (part of ports-mgmt/portupgrade)

2013-06-22 Thread Matthew D. Fuller
On Sat, Jun 22, 2013 at 12:34:38PM + I heard the voice of
Walter Hurry, and lo! it spake thus:
 
 But the corresponding action doesn't happen on 10.0-CURRENT
 (r251572) until I do a 'portsdb -Fu'.
 
 Why the difference?

Portsnap doesn't make/distribute INDEX-10 (until 10 spirals toward
-STABLE status, anyway).  I just symlink it to INDEX-9...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Cannot startx on FreeBSD10 Current

2013-06-21 Thread Matthew D. Fuller
On Sat, Jun 22, 2013 at 12:29:49AM + I heard the voice of
Miguel Clara, and lo! it spake thus:
 
 The only way to turn off is but force and this can cause damage to
 filesystems, this is indeed a very big issue, and I'm not sure if
 its specific to KMS or some freebsd-current problem cause I have no
 way to look into it!

One little trick you might try is to login to a second VTY and run
something like sleep 60 ; shutdown -r now before switching back and
running startx; if it's just a UI crash/lockup rather than a
whole-system such, that'll give you a clean reboot without FS damage.
Of course, if it's a whole-system lockup, it won't, but that also
means you can tell which it is, which may be diagnostically useful...

(ssh'ing in from another machine is another way to track such things,
but may be less convenient depending on your own setup...)


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Ports including sys/time.h broken

2013-03-27 Thread Matthew D. Fuller
On Wed, Mar 27, 2013 at 09:28:19PM +0100 I heard the voice of
Pawel Pekala, and lo! it spake thus:

 For some time now (about month?) ports using sys/time.h include fail to
 build and I`m sure they were building ok before. At least those seems
 affected by this:
 
 math/atlas
 math/openblas
 x11-toolkits/c++-gtk-utils

chromium also fails in a similar way.

I presume that:

 /usr/include/sys/time.h:134:17: error: unknown type name 'sbintime_t'

is really the important bit; something needs sys/types.h to get
sbintime_t and isn't pulling it in.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS cache devs UNAVAIL

2012-10-23 Thread Matthew D. Fuller
On Tue, Oct 23, 2012 at 11:08:55PM +0300 I heard the voice of
Andriy Gapon, and lo! it spake thus:
 
 Do you have a rough estimate of when you started to experience this issue?

I saw it with r241541 and not with my previous kernel (strings says it
was r238937; July 31).  So not a very narrow range for me.  The major
changes in ZFS in that interval I say in a glance at the log were the
TRIM and the tasting-for-root-pool.  But I don't have any reason to
suspect them other than hey, these are high-profile.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS cache devs UNAVAIL

2012-10-22 Thread Matthew D. Fuller
On Tue, Oct 23, 2012 at 12:57:34AM +0200 I heard the voice of
Michael Schmiedgen, and lo! it spake thus:
 
 after an update to CURRENT 2012-10-17 my ZFS cache devs are marked
 UAVAIL after boot. These two devs are SSD partitions that are listed
 with some wired numbers (see below). Before that they were listed
 fine as ada0p1 and ada1p1.

I saw this after my update to 10.0-CURRENT #0 r241541: Sun Oct 14.

In my case, it's ada2p2 which is the cache that comes up unavail on
boot.  One notable thing may be that p1 is used for ZIL, and comes up
fine.

NAMESTATE READ WRITE CKSUM
d   ONLINE   0 0 0
  mirror-0  ONLINE   0 0 0
ada1p3  ONLINE   0 0 0
ada0p3  ONLINE   0 0 0
logs
  ada2p1ONLINE   0 0 0
cache
  ada2p2ONLINE   0 0 0


I notice that you also have a second partition on your drives that's
part of another pool.  Maybe it's related to something giving up after
assigning one partition from the drive to zpool somewhere?  Though in
your case it's p2 that's working and p1 that's wandered off, so maybe
that's not it...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS on HEAD

2012-09-28 Thread Matthew D. Fuller
On Fri, Sep 28, 2012 at 09:31:41PM +0200 I heard the voice of
Sami Halabi, and lo! it spake thus:
 /usr/src/sys/amd64/confSAMI: unknown option KVA_PAGES

You're using amd64, not i386; you don't need to mess with KVA_PAGES.

In fact, you probably don't need to tune anything on amd64, unless
you've got either very little or very huge physical memory.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS on HEAD

2012-09-28 Thread Matthew D. Fuller
On Fri, Sep 28, 2012 at 09:44:08PM +0200 I heard the voice of
Sami Halabi, and lo! it spake thus:
 
 what count for little, and what count for huge.

Off the top of my head, I'd say less than 1 gig (maybe 2) or more than
256.  With very little, you may need to start looking at some of the
i386 tuning to things to scale back.  But anywhere in the middle the
defaults should work fine (I'm sure there are gains to be had from
working at tuning, but probably not huge and probably very dependent
on your particular hardware and workloads).


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-27 Thread Matthew D. Fuller
On Tue, Sep 27, 2011 at 09:36:17AM -0400 I heard the voice of
Robert Huff, and lo! it spake thus:
 Adrian Chadd writes:
   Our children will be dealing with Y2038. :-)
 
 Statistically, some of us will.

Actually, I had to deal with it just last week...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: 9.0 beta2 the new bsdinstaller

2011-09-22 Thread Matthew D. Fuller
On Wed, Sep 21, 2011 at 08:26:47AM + I heard the voice of
Thomas Mueller, and lo! it spake thus:
 
 I don't think there is any particular advantage in aligning GPT
 partitions on 1 MB boundaries.

No, but it's bg, and rund!  (http://dilbert.com/fast/1994-03-24/)

It's a nice round number, and with even the by-modern-standards
smallish drives I was using, it rounds to 0 wasted space.  So I
figured, what does it hurt?

My mail was just to say IWBNI the hurt was more Hey, this probably
isn't going to work, are you sure? rather than Hahaha, you think you
can boot??  Sucker!


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: 9.0 beta2 the new bsdinstaller

2011-09-20 Thread Matthew D. Fuller
On Tue, Sep 20, 2011 at 04:23:49PM +1000 I heard the voice of
Peter Jeremy, and lo! it spake thus:
 On 2011-Sep-19 13:25:27 +0100, Bruce Cran br...@cran.org.uk wrote:
 Will 64 kB be enough for 9.x?
 
 At least for x86 architectures, it seems adequate.  [...]
 
 As for size, I'd suggest that if the default freebsd-boot size is
 going to be changed, it should be adjusted so that the following
 partition is aligned to a reasonably sized power of 2 - 128KB or
 256KB.

I've been meaning to mention this, but we really should document
somewhere that it has a _MAXIMUM_ size.

I setup a system a few weeks back with GPT, and figured I'd just make
the first 'real' partition start at the 1 meg mark.  And make
everything before that (1 meg - the however many sectors for the pmbr)
the freebsd-boot partition.

It worked fine, up 'till the point that I tried to boot, and it
completely failed to, complaining that the boot code was too big.  I
had to track around in pmbr to find

.   .   cmp $0x9000,%ax..   .   # Don't load past 0x9,
.   .   jae err_big..   .   #  545k should be enough for
.   .   mov %ax,%es..   .   #  any boot code. :)

and redo the partition to 512k (leaving a few hundred k unused before
the next partition started) before it would boot.  That's a little
nerve-wracking to hit on a critical system...


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [RFC] Force stdio output streams to line-buffered mode

2011-02-19 Thread Matthew D. Fuller
On Sat, Feb 19, 2011 at 07:50:43PM +0100 I heard the voice of
Jeremie Le Hen, and lo! it spake thus:
 
 I've attached a small patch for stdio, so if the environment variable
 STDIO_IOLBF is set, the output streams will be line-oriented by default.
 iostat -x 1 | env STDIO_IOLBF=1 grep -v ad10 | cat -n

I've no real comment on anything else (sounds like an interesting
hack, whatever else), but just for this particular case, you know that
grep has a --line-buffered arg, right?


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Oddities in -current post-eventtimer

2011-01-03 Thread Matthew D. Fuller
OK, this has happened a couple times now.  I'm running a mid-Oct
-CURRENT, and at around 25 days uptime (not exact but consistently in
that vicinity), things start getting very choppy.  It's easily visible
in playing videos; things get very jerky and slow, but all sorts of
things start acting like they're happening in little chunks of time;
keyboard repeats get very slow, things that often take notable time
take much more, etc.  It's accompanied by a big spat of calcru:
runtime went backwards messages (presumably just another symptom).

The only fix I've found is to reboot, and then it's good for another
25ish days.  As a workaround, enabling kern.eventtimer.idletick sets
things rightish.  A look at the interrupts turns up a hint; while
vmstat says the overall average for cpu0 is just under 300/s, systat
-vmstat shows that it's currnetly running around 20-some.  The other
CPU's also settle at much lower levels.

Another more tiring workaround is just slinging the mouse around real
fast; that seems to hint to the system to keep checking stuff.
Watching systat, that doesn't seem to bring the cpuX interrupt rate up
very much, but the videos start playing smoothly.


FreeBSD 9.0-CURRENT #0 r214107: Wed Oct 20 06:25:50 CDT 2010
Quad-core running amd64.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Oddities in -current post-eventtimer

2011-01-03 Thread Matthew D. Fuller
On Mon, Jan 03, 2011 at 01:21:10PM +0200 I heard the voice of
Alexander Motin, and lo! it spake thus:
 
 Symptoms look very alike to ones fixed at r214597 on 2010-10-31:

Shoot, I missed that going by.  Sorry for the noise; I guess I've got
a good excuse to go upgrade now   8-}


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: TTY task group scheduling

2010-11-18 Thread Matthew D. Fuller
On Thu, Nov 18, 2010 at 06:23:24PM + I heard the voice of
Alexander Best, and lo! it spake thus:
 
 judging from the videos the changes are having a huge impact imo.

Well, my (admittedly limited, and certainly anecdotal) experience is
that Linux's interactive response when under heavy load was always
much worse than FreeBSD's.  So maybe that's just them catching up to
where we already are   ;)


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Interpreted language(s) in the base

2010-08-16 Thread Matthew D. Fuller
On Sun, Aug 15, 2010 at 11:15:55PM -0700 I heard the voice of
Doug Barton, and lo! it spake thus:
 
 However, a bigger reason was that it was impossible to marry our
 concept of a stable branch with the ever-evolving world that was
 perl.

This one at least is conceptually pretty easy to solve.  We don't have
any worries about how old or new the version of expat in base is;
since it's not called libexpat, nothing but the stuff in base written
specifically against it has to worry about it getting old, and
upgrading it requires only checking against those things in base.  So
we could go right ahead and import perl, just renamed to 'bsdscript'
8-}


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Switchover to CAM ATA?

2010-04-23 Thread Matthew D. Fuller
On Fri, Apr 23, 2010 at 06:48:09AM +0200 I heard the voice of
Szilveszter Adam, and lo! it spake thus:
 
 There is one interesting tidbit though: previously it used to be
 possible to run cdda2wav also as non-root, provided the user running it
 had read access to the /dev/cd0 device. This seems to no longer work.
 
 Has anybody else noticed this?

I think you may need to use the /dev/xpt* or /dev/pass* perms.  Can't
remember which.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: HEADS UP: /bin and /sbin are now dynamically linked

2003-11-26 Thread Matthew D. Fuller
On Tue, Nov 25, 2003 at 01:41:53PM -0500 I heard the voice of
Garance A Drosihn, and lo! it spake thus:
 
 It is a bit more complicated than that, because programs may
 include embedded references to other files.  So, I think
 some developer would *have* to do a little up-front work for
 any program that would be optionally-added to /rescue.

Oh, sure; nothing's ever as easy as it should be   :)

The advantage of this method is it's simple, cheap, automatic, and lets
us say You can try setting ADDITIONAL_RESCUE=usr.sbin/foo in make.conf
and it may work, without putting extra burden on developers or people
who don't wanna.  It may only be a fifth of a loaf, but...


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP: /bin and /sbin are now dynamically linked

2003-11-26 Thread Matthew D. Fuller
On Tue, Nov 25, 2003 at 02:17:02PM -0500 I heard the voice of
slave-mike, and lo! it spake thus:
 Would it be possible to get a copy of this script?
 
 Please! :)

Oh, it's pretty simplistic.  It's actually on a box that's in the closet
right now, but I think this is an older working version:
---
liblist:
@echo '== Getting needed libraries'
-@(cd ${SRCBASE}/bin  ldd ${BINFILES})  liblist.raw
-@(cd ${SRCBASE}/sbin  ldd ${SBINFILES})  liblist.raw
[ ... similar stuff for other dirs ... ]
[EMAIL PROTECTED] -v '^[a-z]' liblist.raw | awk '{print $$3}' | sort | uniq \
| sed 's,^${SRCBASE},,' | sed 's,^/,,'  liblist.cooked
[EMAIL PROTECTED]  liblist.cooked
@tar -cf - -C ${SRCBASE} `cat liblist.cooked` \
| tar -xvpf - -C ${DSTBASE}
-@(cd ${SRCBASE}/usr/lib  install -c -m 444 pam_* ${DSTBASE}/usr/lib)
@echo '== Done libraries'
---

You'll note that I already manually slipped in the pam_* .so's, which is
one of those additional non-obvious extra files things that Garance
mentioned in the other message.  I could probably replace the whole
transformation pipeline with a few lines of actual scripted awk(1); I
just did it all inline in the Makefile because I was lazy.

${SRCBASE} is somewhere I DESTDIR='d an installworld previously, and
${DSTBASE} becomes (as a result of a bunch of other make targets, of
which this is one of the later ones) a dir I can tar up and untar
somewhere as /.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to fix this in 5.1-REL??

2003-11-26 Thread Matthew D. Fuller
On Tue, Nov 25, 2003 at 08:57:10AM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
 
 While UPDATING contain details on updating a system, the Makefile in
 /usr/src (actually Makefile.inc1) contains a target of 'world' and,
 through V3 of FreeBSD, this was considered the appropriate target for
 re-compiling sources.
 
 In the days of V4, a new methodology for updating that was far less
 prone to failure that would leave a system unusable was developed with
 two new targets, 'buildworld' and 'installworld'.

I think you're a wee bit off on dates there...

src/Makefile:
revision 1.109.2.9
date: 1997/08/05 03:46:23;  author: asami;  state: Exp;  lines: +192 -91
This patch splits world into two parts, buildworld and
installworld, which can be run together or separately (or even on
different machines).  The buildworld target does not install
anything outside /usr/obj; you still need to be root to run it (the
default install rules want to set the ownership, etc.), but it's now
possible to upgrade a bunch of -stable machines by running make
buildworld on a 2.1.5 NFS server and then running make installworld
on each of the clients, while not compromising the stability of the
server at all.

Reviewed by:too many many people to list here, special thanks to bde

1.109.2.9 was between 2.2.2 and 2.2.5.  It was committed in parallel to
HEAD at the same time (1.133).  That's all over a year before 3 became
-STABLE.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP: /bin and /sbin are now dynamically linked

2003-11-25 Thread Matthew D. Fuller
On Mon, Nov 24, 2003 at 02:41:44PM -0800 I heard the voice of
David O'Brien, and lo! it spake thus:
 On Mon, Nov 24, 2003 at 04:07:49PM -0500, Michael Edenfield wrote:
  
  Would it be possible, through some make.conf magic, for the end-user to
  set extra programs to be put into /rescue that are not typically there?
  
  RESCUE_EXTRAPRGS= usr.bin/vi usr.bin/fetch
 
 This list could easily need things added to librescue.

If you can delay building the rescue stuff until after everything else,
you can use ldd(1) on the built binaries for everything else and hash up
the list from that.  I do something similar in a set of scripts I have to
generate filesystems for small systems (i.e., I create a variable in a
Makefile listing all the programs, and it automatically includes all the
libraries the programs need) with a little sed/awk.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Unfortunate dynamic linking for everything

2003-11-24 Thread Matthew D. Fuller
[ Lots of CC trimming ]

On Sun, Nov 23, 2003 at 06:27:01PM -0500 I heard the voice of
Richard Coleman, and lo! it spake thus:
 
 You would need to make sure that startup scripts never use tilde 
 expansion.  I'm not sure how common that is with RCNG.

Not just the startup scripts, but ANY script.  I dare say there's a long,
long list of scripts that use ~-expansion, to say nothing of the
homegrown ones we all have working quietly and forgotten for years.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: drm, irqs, etc.

2003-11-13 Thread Matthew D. Fuller
On Wed, Nov 12, 2003 at 06:42:39PM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
 
 In reality, 5.0 and 5.1 are neither, but questions have to go somewhere
 and it was announced some time ago that until a V5 version was
 declared 'STABLE', that questions should go to CURRENT and not STABLE.

Well, if you wanna be pedantic about it, no -RELEASE's are -STABLE
either.  It's just a question of which branch the releases are branched
(and/or snapshot'd) from.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: APIC-UP related panic

2003-11-12 Thread Matthew D. Fuller
I, for one, am always pleased to see these sort of in-depth explanations
of these sort of shims.

On Tue, Nov 11, 2003 at 11:35:26AM -0500 I heard the voice of
John Baldwin, and lo! it spake thus:
 
 It's documented in /sys/i386/conf/NOTES now along with 'device apic'.  For
 a longer explanation of what is happening:

[...]
 
 So, by default, to work around motherboards that don't hook IRQ 0
 up to the I/O APIC, we route IRQ 0 through the the 8259A PICs.

[...]
  
 However, if NO_MIXED_MODE works, that is actually the more desirable
 way to run your system.

How common is the need for this?  Does turning of mixed mode when it's
not needed give any real advantages higher up?


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: More ULE bugs fixed.

2003-11-05 Thread Matthew D. Fuller
On Wed, Nov 05, 2003 at 11:28:50AM +0100 I heard the voice of
Eirik Oeverby, and lo! it spake thus:
 
 The second is that mouse messages are actually *lost*, or bogus ones are 
 being generated. I guess it's the first, making moused or X misinterpret 
 the messages it gets. Where along the chain it fails I obviously have no 
 clue. The consequence of this is that when the mouse stops (like in #1) 
 but then resumes from an entirely different point - be it 10 pixels away 
 or at the other end of the screen - possibly even generating a button 
 push (but not necessarily the corresponding button release) message.

Note that I've had this to a greater or lesser extent for as long as I
can remember (certainly back to 3.0-CURRENT).  It corresponds with
syslog'd messages on my xconsole along the lines of:

Nov  3 12:46:13 mortis kernel: psmintr: out of sync (00c0 != ).
Nov  3 12:46:13 mortis kernel: psmintr: discard a byte (12).

It's certainly a lot more common (by orders of magnitude) on 5.x in the
past...   oh, I dunno, year-ish, than it was previously.  I lose mouse
function for maybe a second, then it squirms itself off somewhere on the
screen and sends some button press events.

I'm currently running 5.1-R, the traditional scheduler, a PS/2 mouse with
no moused.  And since I got them (much more rarely) with earlier
5-CURRENT's, and with 4-CURRENT's, etc, I can't see how it's scheduler
related.


 When you say you get the bogus mouse events (which I believe you are 
 saying atleast ;) only during load, I'm immediately thinking that yes, 
 that might make sense.

I don't get it only under load; sometimes from flat idle.  However, it's
usually when I first move the mouse, after it sitting still for a while
(where 'while' can vary from a few seconds to a few days, of course); it
hardly ever happens in mid-move.



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Text file busy

2003-09-04 Thread Matthew D. Fuller
On Thu, Sep 04, 2003 at 09:36:31AM -0700 I heard the voice of
Mikko Ty?l?j?rvi, and lo! it spake thus:
 
 If you are into foot shooting, you can always overwrite a shared lib,
 such as libc.so, and watch (almost) all your programs crash and burn :-)

*raise hand*

Yup.  Got the t-shirt.

Nothing like watching your pinkie move in slow motion to depress the
Enter key, while your brain is screaming, NO, I meant *MV*, not cp!!!



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Question related to FreeBSD Serial Console...

2003-09-03 Thread Matthew D. Fuller
On Tue, Sep 02, 2003 at 12:18:51PM +0100 I heard the voice of
[EMAIL PROTECTED], and lo! it spake thus:
 
 Keyboard and mouse manufacturers usually give dire warnings about plugging
 in PS/2 devices when the machine is powered up, maybe that's the reason
 why.

I think it's more because the interface isn't really designed
electrically to support hot-plugging.  I've cooked motherboards[0] by
hot-plugging keyboards before.

[0] Often I could, after heating up the soldering iron and a trip to
Radio Shack, recover them, but not always.



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: swapon vs savecore dilemma

2003-09-02 Thread Matthew D. Fuller
On Tue, Sep 02, 2003 at 12:58:40AM -0600 I heard the voice of
Scott Long, and lo! it spake thus:
 
 I still think that the real problem is in running swapon before
 savecore.  In 99% of the cases out there, RAM scales with storage,
 so I really can't imaging fsck needing to swap, and certainly not
 in it's 'preen-before-background' mode.

Note also that (last I heard, anyway) this is often worked around, or
non-issued, by us allocating swap from the bottom of the partition up,
and coredumps happening from the top down.  So, if you've got 512 megs
of swap, and 128 megs of ram, you'd need to use 384 megs of swap (+/-
housekeeping) before you corrupted your core.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-17 Thread Matthew D. Fuller
On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
Bill Moran, and lo! it spake thus:
 
 My best guess is that the chipset responds slowly to probes, thus it
 takes a while to get the list of devices from it.  However, I've never
 looked into it any more than that.

I've always presumed it to be a question of timing out probes to the
drives; it only ever happens on IDE controllers with no devices attached
to 'em.  I habitually just disable the controller channels that are empty
(or, in the case of my SCSI systems, just yank ATA support altogether).


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Panic in 5.1-R

2003-07-22 Thread Matthew D. Fuller
System runs ppp(8) for a PPPoE DSL connection.  I fired up another copy
of ppp for unrelated purposes (no args, just `ppp`), and got this panic:

panic: Resource  flags out-of-sync
cpuid = 1; lapic.id = 0c00
boot() called on cpu#1

#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:238
#1  0xc0242863 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:370
#2  0xc0242c1f in panic () at /usr/src/sys/kern/kern_shutdown.c:543
#3  0xc02ae257 in tunopen (dev=0xc2818200, flag=3, mode=8192, td=0x0)
at /usr/src/sys/net/if_tun.c:275
#4  0xc02089b9 in spec_open (ap=0xce7d2a64)
at /usr/src/sys/fs/specfs/spec_vnops.c:203
#5  0xc0208778 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:123
#6  0xc02a13b9 in vn_open_cred (ndp=0xce7d2bd8, flagp=0xce7d2cd8, cmode=3456, 
cred=0xc2edd000) at vnode_if.h:213
#7  0xc02a0f79 in vn_open (ndp=0x0, flagp=0x0, cmode=0)
at /usr/src/sys/kern/vfs_vnops.c:85
#8  0xc029a96d in kern_open (td=0xc2a18980, path=0x0, pathseg=UIO_USERSPACE, 
flags=3, mode=134794642) at /usr/src/sys/kern/vfs_syscalls.c:684
#9  0xc029a820 in open (td=0x0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:649
#10 0xc03bb1ce in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 
134883928, tf_esi = 2, tf_ebp = -1077938856, tf_isp = -830657164, tf_ebx = 
-1077938840, tf_edx = 9, tf_ecx = 134794646, tf_eax = 5, tf_trapno = 12, tf_err = 2, 
tf_eip = 405215043, tf_cs = 31, tf_eflags = 531, tf_esp = -1077938900, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1021
#11 0xc03a2c5d in Xint0x80_syscall () at {standard input}:139
---Can't read userspace from dump, or kernel process---



Actual source is at:
#3  0xc02ae257 in tunopen (dev=0xc2818200, flag=3, mode=8192, td=0x0)
at /usr/src/sys/net/if_tun.c:275
275 KASSERT(!(tp-tun_flags  TUN_OPEN), (Resource  flags out-of-sync));
(kgdb) print dev-si_name
$6 = 0xc2818290 tun0


Keeping the dump around, if there's anything else useful I can pull out.



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 8MB install

2003-06-25 Thread Matthew D. Fuller
On Wed, Jun 25, 2003 at 02:44:24AM -0700 I heard the voice of
Terry Lambert, and lo! it spake thus:
 
 Alternately, you could find a FreeBSD 1.1.5.1 distribution on the
 net somewhere, and install that, instead; I have personally run
 that version of FreeBSD on a 4M 386SX, to use it as an X Terminal.
 8-).

No need to get silly.

My 4M 386SX runs 2.1-STABLE just fine   :P



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: MAXLOGNAME 17 ?

2003-06-02 Thread Matthew D. Fuller
On Mon, Jun 02, 2003 at 12:52:38AM -0300 I heard the voice of
milo, and lo! it spake thus:
 
 I think that change this value can resolv. After one cvsup of current,
 my login and syslogd were compiled again but not works. Then I did one
 attach  with gdb in login and I watched that mistake was in
 setlogin(username) in the child process.

Yes, you can.

Just change the values, then do your buildworld/buildkernel etc.  You may
also need to recompile some ports that mess with usernames.  I used to do
this on 2.2.x to get 16-char usernames, and had to rebuild things like
sshd to handle it ('course, with ssh in base now, that's one less).
There were occasional weirdnesses (wtmp got screwy sometimes, never
tracked it down), but overall it worked fine.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: pw_user.c change for samba

2002-12-01 Thread Matthew D. Fuller
On Sat, Nov 30, 2002 at 10:24:58PM -0500 I heard the voice of
Garance A Drosihn, and lo! it spake thus:
 
 However, that doesn't answer the question of which 'adduser' is
 actually expected to be used in 5.0-current.  Does someone have
 the shell-script (non-perl) version of adduser?  Is it named
 something else, perhaps?
 
 Or are we going to ship 5.0-release with an 'adduser' that does
 require perl, even though perl is not in the base system?

I've had, among my stalled ideas, an intent to rewrite {add,rm}user in C
backending into pw(8) for all the dirty work.  Of course, that's waiting
for me to complete my porcine aviation instruction.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 3 floppy system for -current releases

2002-08-08 Thread Matthew D. Fuller

On Fri, Aug 09, 2002 at 02:12:33PM +0930 I heard the voice of
Daniel O'Connor, and lo! it spake thus:
 
 I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is
 easier to setup)

I've had one recent example here where FTP wouldn't work, but NFS flew.



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 3 floppy system for -current releases

2002-08-08 Thread Matthew D. Fuller

On Fri, Aug 09, 2002 at 07:20:53AM +0200 I heard the voice of
John Hay, and lo! it spake thus:
 
 I'm wondering if that was because something in our stack was bust or
 because of some firewall or other network thing?

I'm not sure.
This was 4.6.1-RC2, across a local 100mbps LAN.  The FTP server is a few
month old -CURRENT; FTP would disconnect itself after fetching the first
few files, and then on retry, cpio would start complaining about checksum
mismatches (though I could manually ftp the files around, or check them
on the server, and the checksums matched).  Also after the first
disconnect, using another server (such as one of the 'official' mirrors)
would get the same thing.  Switched to NFS, and everything ran clean
through.

Interestingly, I tried an experiment of just using one of the official
mirrors straight up, and it went just fine (through most of the 'bin'
dist, after which I stopped it).  I'm presuming it's just something
strange on my -CURRENT box, which wouldn't be much surprise.  It IS
-CURRENT, after all.


 So should I commit the code and let us tune what go on which floppy
 later or should I just sit back and enjoy the ride?

It wouldn't bother me overly much to have to go to a 3rd floppy.  At
least, not significantly more than it already does to have to use 2
floppies   ;



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: custom kernel

2002-06-24 Thread Matthew D. Fuller

On Mon, Jun 24, 2002 at 10:29:14PM -0700 I heard the voice of
Doug Barton, and lo! it spake thus:
  
  Well, what I do is place symlinks in /usr/src/sys/i386/conf, pointing to
  the real kernel config file(s), which are in a different hierarchy,
  and in the local part of my CVS repository (vs. the FreeBSD part).
  
  It may be a hack, but it's been a fairly effective one for some time
  now.  :-}
 
 That is also useful if you're prone to do 'rm -rm /usr/src' periodically
 :)

Indeed.  I keep mine in /usr/local/kernel (I sometimes have to copy them
over, such as when doing a kernel build over NFS on another box, but life
isn't perfect), and I newfs /usr/src and re-co the src tree between
builds (nice quick and easy way to cleanup, that).



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: gcc -O broken in CURRENT

2002-03-15 Thread Matthew D. Fuller

[ Trim the CC's a bit ]

On Fri, Mar 15, 2002 at 04:00:08PM -0800 I heard the voice of
Terry Lambert, and lo! it spake thus:
 Kenneth Culver wrote:
   Other reasons I haven't even thought of yet 8-).
 
  Yeah, I was just wondering if there were issues making us keep a.out stuff
  in FreeBSD aside from the I wanna run 2.2.x programs issue.
 
 Linking with third party a.out libraries.
 
 Other reasons I haven't even thought of yet 8-).

(ttypa):{1078}% file /usr/local/lib/netscape/communicator-4.7.us.bin 
/usr/local/lib/netscape/communicator-4.7.us.bin: FreeBSD/i386 compact
  demand paged dynamically linked executable

Now, if you'd like to talk Netscape into building a version intended for
a version of FreeBSD newer than, say, 3 years, 3.5 months (approximately)
old...



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Why is csh tcsh? This can be a bad thing...

2001-08-24 Thread Matthew D. Fuller

On Fri, Aug 24, 2001 at 09:46:00AM -0700, a little birdie told me
that Jordan Hubbard remarked
 From: Jim Bryant [EMAIL PROTECTED]
  Because of certain differences, it cannot be used wholesale as a
  replacement for csh.
 
 Then please enumerate them so that they can be given due attention.
 This is exactly the sort of detailed feedback that was requested when
 we first raised the issue of switching over, and nobody could come up
 with any concrete differences that would cause harm, so the deed was
 done.

It blew beets all over the startup script for ROM 2.4 MUD's.
It's a crappy script (who the hell scripts in csh anyway?  furrfu), but
it took me a good half hour to figure out what caused it to suddenly stop
working.  I always mean to rewrite it in sh, but I ended up just copying
in a /bin/csh.realcsh and pointing it over.

So yes, there's a difference.  But, on the flip side, I think that the
fact that it's been this long without anybody screaming majorly (after
the initial shakedown, of course) kinda sums it up.



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Userbase of -current

2001-07-19 Thread Matthew D. Fuller

On Wed, Jul 18, 2001 at 09:34:41PM -0400, a little birdie told me
that Garance A Drosihn remarked
 At 11:18 PM -0700 7/17/01, Peter Wemm wrote:
 If I had to guess, I'd put the total [genuine] -current userbase
 at between 20 and 50 people.  And many of those intentionally lag
 by a few weeks to a month or two.
 
 At the kernel-confab at usenix, I heard some people talking about
 how current wasn't really as bad as people assume it is.  I must
 admit I wonder how much current is actively used.  I know I try
 to build a new up-to-date current every two or three weeks, but I
 don't do much more on it than test a few changes.  I am certainly
 not stress-testing it.  Almost all of my real day-to-day work is
 done on machines which are tracking -stable.

FWIW, without extraordinary reason, I don't run 'production' machines on
-CURRENT (I think the last time I did so was when I ran a news server on
3.0-CURRENT).  However, my workstation runs -CURRENT, and my dialup router
does as well (mainly to make it easier to update), my laptop...  come to
think of it, almost all my of personal machines run -CURRENT, except for
one that runs 2.1-STABLE (386SX.  4 MB RAM.  80 meg disk.  Last benchmark:
13 days for a buildworld.  Don't think I'll update it any time soon).


-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: softupdates on /

2001-07-06 Thread Matthew D. Fuller

On Fri, Jul 06, 2001 at 12:52:06AM -0500, a little birdie told me
that Dan Nelson remarked
 In the last episode (Jul 06), David Scheidt said:
  
  I've dodged that problem by SIGSTOPing installworld a couple times during
  the /sbin install, waiting for softupdates to catchup, and then SIGCONTing
  it.  That's a pain; it's ugly, but it does work.  Easier than a reboot,
  sometimes.
 
 My workaround when it bit me was to run a while sleep 1 ; do sync ;
 done loop in another window to speed up the softupdate clock.  I
 suppose cranking down the kern.{file,meta,dir}delay sysctls would have
 done the same thing.

Meanwhile, I've completely avoided the problem.
All of my (ufs) filesystems are running with softupdates, except /.  I've
got plenty of free space on it, but:
/dev/da0s1a on / (ufs, local, synchronous)

/var, /usr, /tmp, etc are all on their own filesystems (/tmp is newfs'd
on boot, too; THAT's how you avoid cleaning race conditions ;), so the
only time writes happen on it is when I installworld or edit something in
/etc; either way, I like knowing it's there when it says it is.  Of
course, it does slow the installworlds down to an astonishing degree.



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Re: -CURRENT b0rked?

2001-05-12 Thread Matthew D. Fuller

On Sat, May 12, 2001 at 12:21:55PM +0300 I heard the voice of
Maxim Sobolev, and lo! it spake thus:
 
 It seems that sysinstall(8) was not fully integrated into
 buildworld - it depends on content of /usr/share/syscons/keymaps,
 while it shouldn't.
 
 I've just committed a patch that should fix this problem.

Hoo, here I come to make your life a living hell once more...

In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40:
keymap.h:2: `keymap_be_iso' undeclared here (not in a function)
keymap.h:2: initializer element is not constant
keymap.h:2: (near initialization for `keymapInfos[0].map')
keymap.h:3: `keymap_br275_iso' undeclared here (not in a function)
keymap.h:3: initializer element is not constant
keymap.h:3: (near initialization for `keymapInfos[1].map')
etc etc etc, for about 2.5 pages


-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Re: -CURRENT b0rked?

2001-05-12 Thread Matthew D. Fuller

On Sat, May 12, 2001 at 10:07:20PM -0500 I heard the voice of
Ken Wills, and lo! it spake thus:
 
 Deleting keymap.h (autogenerated, in obj/* somewhere, I forget), and restarting
 the build got me past this.

I start all my builds with an empty /usr/obj and a freshly co'd /usr/src.
Re-newfs'ing everything here and trying again, just to make doubly sure
now, but I'm pretty sure I cleaned up as always.


-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



-CURRENT b0rked?

2001-05-11 Thread Matthew D. Fuller

On several attempts to build world, I'm getting ths same error:

In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40:
keymap.h:3606: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a
function)
keymap.h:3606: initializer element is not constant
keymap.h:3606: (near initialization for `keymapInfos[21].map')

at which point the build bombs out.  This is with completely clean src/
and obj/ each time, and I haven't seen any commits to the file in the
last 24+ hours.  OTOH, I haven't seen a peep about this from anybody
else, so am I just hitting some sort of really weird condition that
nobody else has ever heard of here, or is nobody else building -CURRENT
right now?



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sshd library problems

2000-04-04 Thread Matthew D. Fuller

Hi Ben  :)

On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me
that Ben Rosengart remarked
 Hello all,
  I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is
 not working for me.  When I try to start it, I get the following:
 
 ** RSA_PKCS1: Unable to find an RSA implemenation shared library.
 ** Install either the USA (librsaINTL.so) or International (librsaUSA.so)
 ** RSA library on your system and run this program again.

(Aren't those filenames reversed?  Just a hunch...)


 I have rsaref-2.0 installed from ports, and I have USA_RESIDENT=YES and
 RSAREF=YES defined in /etc/make.conf.  I've cvsupped from a new vanilla
 standard-supfile, using the cvs-crypto collection.

Hm.
Don't know how much I can say beyond that.  I've put together a few
post-ssh systems (4.0-R, -CURRENT), and haven't had any trouble after I
remembered to install the crypto dists.


FreeBSD mortis.sighup.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0:
Tue Mar 14 03:49:39 CST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/MORTIS  i386

(ttypb):{54}% ll /usr/lib/librs*
-r--r--r--  1 root  wheel  6358 Mar 14 04:03 /usr/lib/librsaUSA.a
lrwxr-xr-x  1 root  wheel14 Mar 14 04:03 /usr/lib/librsaUSA.so@ - librsaUSA.so.1
-r--r--r--  1 root  wheel  8080 Mar 14 04:03 /usr/lib/librsaUSA.so.1
-r--r--r--  1 root  wheel  7122 Mar 14 04:03 /usr/lib/librsaUSA_p.a




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SMP buildworld times / performance tests

2000-03-31 Thread Matthew D. Fuller

On Fri, Mar 31, 2000 at 12:24:27PM +0200, a little birdie told me
that Brad Knowles remarked
 At 5:44 PM -0600 2000/3/30, Matthew D. Fuller wrote:
 
   Does softupdates provide faster performance than async/noatime?  I keep
   /usr/src and /usr/obj as such, would it be faster with softupdates?  And
   if so, why?
 
   Of course, once you ask this question, the next logical one that 
 follows is "what happens if you do all three?"

TTBOMK, nothing, as softupdates will override the other two.



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SMP buildworld times / performance tests

2000-03-30 Thread Matthew D. Fuller

On Wed, Mar 29, 2000 at 10:04:17PM -0800, a little birdie told me
that Matthew Dillon remarked
 
 Ha!  I found it.  Kirk gets the credit --- softupdates was turned on
 in one of the machine's /usr/obj's and off on the other machine's.
 
 So softupdates improves buildworld times by a significant margin.  I've
 turned softupdates on on both machines and am rerunning the test.  I
 expect I will see an improvement closer to what Bob Bishop saw when
 he ran the test (7% or so) rather then 20+%.

Does softupdates provide faster performance than async/noatime?  I keep
/usr/src and /usr/obj as such, would it be faster with softupdates?  And
if so, why?




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SMP buildworld times / performance tests

2000-03-30 Thread Matthew D. Fuller

On Thu, Mar 30, 2000 at 04:00:43PM -0800, a little birdie told me
that David O'Brien remarked
 On Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote:
  Does softupdates provide faster performance than async/noatime?
 
 In general it depends.  Softupdates is faster on creating a file and then
 deleteing it before both hit the disk.  Softupdates nulifies out the
 creation.  Async would write the file to disk just to turn around and
 delete it.
 
 For somethings mounting `async' is faster.

The question at task is, is buildworld one of them?  I don't think that
situation comes up a lot in buildworld, but I'm not exactly an authority
on it...



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ntpd hanging machine

2000-03-02 Thread Matthew D. Fuller

On Thu, Mar 02, 2000 at 02:55:16PM -0800, a little birdie told me
that Matthew Dillon remarked
 
 rtprio (and idprio) is virtually guarenteed to lockup your machine 
 eventually.  Don't use either.

Hm.
I've run ntpd rtprio'd to 52 for over a year, under -CURRENT and
RELENG_2_2.  Never had a freeze/crash I coudl attribute to it.



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: OpenSSH bugs with login.conf

2000-02-25 Thread Matthew D. Fuller

On Fri, Feb 25, 2000 at 07:07:54PM +0300, a little birdie told me
that Andrey A. Chernov remarked
 How to reproduce bug:
 with default /etc/login.conf try to log in using standard login (1) and
 "ssh localhost" (2). Then "echo $FTP_PASSIVE_MODE". You'll have  "YES" in
 case (1) and "Undefined variable." in case (2). User's ~/.login_conf not
 handled too.

As long as this type of issue is coming up, I'd like to mention another
related thing that's been brought up relating to the various ssh ports
from time to time; namely, login.access.

If we have OpenSSH in the base system, it'd be REALLY nice if it could
somehow be thwacked into following the same pattern of access control/etc
that every other login method uses.

I haven't actually looked through ssh in general to see what sort of
login process it uses, but is there any inherent reason why it can't just
use login(1) like everything else, and avoid special patching and
duplicated code to read the files?



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: multiple cd devices

2000-01-01 Thread Matthew D. Fuller

On Fri, Dec 31, 1999 at 01:45:31AM -0500, a little birdie told me
that Brian Fundakowski Feldman remarked
 The way certain devices, like cd with its monotonically increasing counter
 where devices are probed in order and assigned device based on precedence
 and not hardwiring/controller connection, work is consistent between
 the kernel and MAKEDEV.  If you have 2 cd devices, you have cd0 and cd1,
 so MAKEDEV accepts "cd2" for "two cd devices".  All CD devices work
 that way.  Disks don't, because there is potential for hard-wiring
 there, and will often be gaps.

FWIW, MAKEDEV for vty's (and pty's too?  dunno) works the same.




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: removing enigma(1)

1999-12-01 Thread Matthew D. Fuller

On Wed, Dec 01, 1999 at 04:09:11PM -0500, a little birdie told me
that Bakul Shah remarked
 
 Enigma is just a format converter at this point and should be
 left around (after renaming it crypt -- which is how it is
 known on all Unix versions older than 10 years).  Some of us

Renaming?
[15:25:53] mortis:~
(ttyp9):{838}% ll -i `which crypt` `which enigma`
23155 -r-xr-xr-x  2 root  wheel  4980 Oct 29 13:47 /usr/bin/crypt*
23155 -r-xr-xr-x  2 root  wheel  4980 Oct 29 13:47 /usr/bin/enigma*




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: removing enigma(1)

1999-12-01 Thread Matthew D. Fuller

On Wed, Dec 01, 1999 at 04:36:12PM -0500, a little birdie told me
that James Howard remarked
 On Wed, 1 Dec 1999, Matthew D. Fuller wrote:
 
  [15:25:53] mortis:~
  (ttyp9):{838}% ll -i `which crypt` `which enigma`
  23155 -r-xr-xr-x  2 root  wheel  4980 Oct 29 13:47 /usr/bin/crypt*
  23155 -r-xr-xr-x  2 root  wheel  4980 Oct 29 13:47 /usr/bin/enigma*
 
 Why is that a hard link instead of a symbolic link?

Probably the same reason most (all?) things in the base system that run
linked are hard links:
(ll -i | sort is instructive)

/sbin:
14445 -r-xr-xr-x   2 root  wheel 150840 Oct 29 13:46 mount_mfs*
14445 -r-xr-xr-x   2 root  wheel 150840 Oct 29 13:46 newfs*
(That's pretty cool, if mildly weird)
14442 -r-xr-xr-x   5 root  wheel  59756 Oct 29 13:46 mount_devfs*
14442 -r-xr-xr-x   5 root  wheel  59756 Oct 29 13:46 mount_fdesc*
14442 -r-xr-xr-x   5 root  wheel  59756 Oct 29 13:46 mount_kernfs*
14442 -r-xr-xr-x   5 root  wheel  59756 Oct 29 13:46 mount_procfs*
14442 -r-xr-xr-x   5 root  wheel  59756 Oct 29 13:46 mount_std*

/bin:
124 -r-xr-xr-x   2 root  wheel  48592 Oct 29 13:43 [*
124 -r-xr-xr-x   2 root  wheel  48592 Oct 29 13:43 test*

Sendmail the same way (I can't show it since I have Postfix installed,
but...)  (Ah, here's another system:)
430769 -r-sr-xr-x  5 root  7  290816 Nov 18  1998 /usr/bin/mailq*
430769 -r-sr-xr-x  5 root  7  290816 Nov 18  1998 /usr/bin/newaliases*
430769 -r-sr-xr-x  5 root  7  290816 Nov 18  1998 /usr/sbin/sendmail*


etc.




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: {a}sync updates (was Re: make install trick)

1999-10-07 Thread Matthew D. Fuller

On Thu, Oct 07, 1999 at 11:57:26AM +1000, a little birdie told me
that Peter Jeremy remarked
 
 How detailed should the man page be?

Exactly my query in writing this  ;


 If it stated "all file data will
 be written synchronously, but inodes where the only update is atime
 and free block bitmaps are written asynchronously", would that be any
 clearer to a user who didn't have a detailed understanding of UFS?
 If you would like it to say something different, write some patches
 and send them in as a PR (keeping in mind phk's recent e-mail about
 green bikesheds).

I'm still stewing on what should be with it; what we have works fine, if
being slightly inconsistent in an obscure way.  I'm trolling for ideas on
whether well enough should be left alone (since there's obviously an
incredibly small percentage of people USING sync as a mountop), or
whether a footnote should be added somewhere (I lean toward mount(2)
instead of mount(8) myself, with a possible xref in mount(8)).

I'll see what I think of, and possibly have some diffs tomorrow.


 There should be fairly few writes to the root partition, so having
 these writes synchronous is not a big performance hit.  On the other
 hand, there are probably a _lot_ of read accesses to devices in /dev
 and files in /bin (how many of your scripts begin #!/bin/sh?).  Unless
 you specify NOATIME, each of these read accesses implies an atime
 update within the inode.  Making these synchronous probably would
 be a big performance hit.

This is why I haven't screamed for them to be sync-tified...




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: make install trick

1999-10-06 Thread Matthew D. Fuller

On Wed, Oct 06, 1999 at 04:18:15PM -0500, a little birdie told me
that Kevin Day remarked
 
  /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100)
 
 My understanding was that that was just a indication of writes that were
 able to be done asynchronously without any risk, so they were done async.
 
 (sync isn't purely sync, only synchronous when it's required for integrity)

I was given to understand that while the default mountop follows these
conventions, explicit 'sync' meant SYNC meant SYNC meant SYNC.

This is my root filesystem.  It gets written to when I edit a file under
/etc or do an installworld.  I don't *CARE* how slow it is, I want to
know that it's solid, consistent, and complete.  Just 'consistent' isn't
enough.  No write is able to be done async without risk when I'm
explicitly saying 'write everything synchronously'.




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



{a}sync updates (was Re: make install trick)

1999-10-06 Thread Matthew D. Fuller

Thank you, this is *EXACTLY* what I was looking for   :)

On Thu, Oct 07, 1999 at 08:59:00AM +1000, a little birdie told me
that Peter Jeremy remarked
 
 As far as I can tell, the net effect is that inode access time updates
 will remain async writes into the filesystem.
 
 An easy way to tell would be to use NOATIME and see if you're still
 getting async writes.  (Or any writes at all).

This does appear to be it.
Testing such things as (cat /kernel  /dev/null  sync  sync)
preceded and followed by a 'mount' call in another window does show the
'async' counter incrementing, and when I remount it noatime it no longer
does.

Is this good, bad, ugly, or just inconsistent?  On the one hand, you can
argue that 'sync should be sync should be sync, I don't bloody care, just
don't do anything async at all', since that's what it's supposed to do:
mount(8):
 syncAll I/O to the file system should be done synchronously.

On the gripping hand, you can say, 'this is an ATIME update, there's no
way its presence or lack thereof can do anything bad to the filesystem,
so let it be async since it takes extra work to make it sync'.


Does anyone have any feeling either way on this?  I, unfortunately, seem
to have strong feelings BOTH ways...  sync atime updates will slow it
down, but on the flip side, if you're mounting sync in the first place
you don't care much for speed anyway.

Thoughts?




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ccd build failure

1999-09-23 Thread Matthew D. Fuller

On Thu, Sep 23, 1999 at 02:51:15PM -0700, a little birdie told me
that Darryl Okahata remarked
 Oliver Fromme [EMAIL PROTECTED] wrote:
 
  Uhm...  Maybe I misunderstand what your 100-line perl script
  does, but I use the following 3-line shell script instead:
  
 #!/bin/sh -
 cvs status | grep '^File:' | grep -v 'Status: Up-to-date$'
 true
 
  This works (and is faster), but it doesn't give you concise,
 nicely-formatted pathnames.  Personally, I prefer status like:

OK:
#!/bin/sh
(cvs status | grep '^File:' | grep -v 'Status: Up-to-date$') 2 /dev/null




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Panic (From -chat's Re: Real Audio program that discusses FreeBSD, solaris, and Linux)

1999-09-17 Thread Matthew D. Fuller

 http://www.thesync.com/etc/archives.html

When I tried to view the program linked here, my -CURRENT system went
kablouie.

FreeBSD mortis.futuresouth.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue
Sep 14 16:48:29 CDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/MORTIS  i386

I have a coredump.  Panic message is:
(Yes, I have mastered the skill of dropping to DDB and panicing while in
X  ;)

Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0c00
fault virtual address   = 0x14
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc0162490
stack pointer   = 0x10:0xcb1c9d4c
frame pointer   = 0x10:0xcb1c9d60
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 372 (screen-3.7.6)
interrupt mask  = tty  - SMP: XXX
panic: from debugger
mp_lock = 0103; cpuid = 1; lapic.id = 0c00
boot() called on cpu#1


Ideas?

Backtrace looks like:
#0  boot (howto=256) at ../../kern/kern_shutdown.c:281
#1  0xc0157319 in panic (fmt=0xc0282090 "feed_root: count == 0")
at ../../kern/kern_shutdown.c:531
#2  0xc0215685 in feed_root (feeder=0xc02aa460, 
buffer=0xcbfcbefe Address 0xcbfcbefe out of bounds, count=0,
stream=0xce35aefc)
at ../../dev/pcm/feeder.c:112
#3  0xc0214c80 in chn_write (c=0xc10d4000, buf=0xce35aefc) at
../../dev/pcm/channel.c:286
#4  0xc0213d70 in dsp_write (d=0xc10d3400, chan=0, buf=0xce35aefc,
flag=21)
at ../../dev/pcm/dsp.c:187
#5  0xc021321d in sndwrite (i_dev=0xc11e3f00, buf=0xce35aefc, flag=21)
at ../../dev/pcm/sound.c:310
#6  0xc018bcc4 in spec_write (ap=0xce35aeb4) at
../../miscfs/specfs/spec_vnops.c:369
#7  0xc0201cb0 in ufsspec_write (ap=0xce35aeb4) at
../../ufs/ufs/ufs_vnops.c:1858
#8  0xc0202251 in ufs_vnoperatespec (ap=0xce35aeb4) at
../../ufs/ufs/ufs_vnops.c:2313
#9  0xc0186032 in vn_write (fp=0xc15d4dc0, uio=0xce35aefc,
cred=0xc12e0f00, flags=0)
at vnode_if.h:331
#10 0xc0163fc8 in dofilewrite (p=0xce2c8340, fp=0xc15d4dc0, fd=13,
buf=0x81cfc88, 
nbyte=1066, offset=-1, flags=0) at ../../kern/sys_generic.c:363
#11 0xc0163ed7 in write (p=0xce2c8340, uap=0xce35af80) at
../../kern/sys_generic.c:298
#12 0xc0241d76 in syscall (frame={tf_fs = -1078001617, tf_es = 47, tf_ds
= -1078001617, 
  tf_edi = 135924656, tf_esi = -1077948116, tf_ebp = -1077948220,
tf_isp = -835342380, 
  tf_ebx = 13, tf_edx = 1066, tf_ecx = 136117384, tf_eax = 4,
tf_trapno = 12, 
  tf_err = 2, tf_eip = 405666084, tf_cs = 31, tf_eflags = 582, tf_esp
= -1077948224, 
  tf_ss = 47}) at ../../i386/i386/trap.c:1056
#13 0xc022f171 in Xint0x80_syscall ()





-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Panic (From -chat's Re: Real Audio program that discusses FreeBSD, solaris, and Linux)

1999-09-17 Thread Matthew D. Fuller

On Fri, Sep 17, 1999 at 04:02:37PM -0400, a little birdie told me
that Sean O'Connell remarked
 hi-
 
 This looks awfully familiar to what rvplayer does to me on
 my -current box.  Of course, no one has responded at all ot
 anything that I sent out...

I've never had any troubles out of it before.  This is the first time
I've had any problems out of it.  It didn't have any problems playing
mp3's, or audio off .avi clips.


 What kind of soundcard do you have?  Mine is Crystal CS4236B
 shipped with my box (a Digital 5510)...

This is the builtin on an Intel Providence motherboard:
pcm1: CS4236B at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0
on isa0




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: $FreeBSD tag confusion

1999-09-01 Thread Matthew D. Fuller

On Wed, Sep 01, 1999 at 09:20:44PM +0800, a little birdie told me
that Peter Wemm remarked
 
 23 cat /home/ncvs/CVSROOT/options
 tag=FreeBSD=CVSHeader
 tagexpand=iFreeBSD,Id

Speaking of the whole subject, where is this (method of defining tags)
documented?  I've searched every bit of CVS documentation I can find
anywhere, and none of it mentions this.




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Monday strikes again

1999-08-24 Thread Matthew D. Fuller

On Mon, Aug 23, 1999 at 09:44:10PM +0100, a little birdie told me
that Doug Rabson remarked
 
 It seems like  isa bus is never being attached for some reason. Have a
 look at nexus_attach() and see if anything suspicious is happening (like
 an error return from device_probe_and_attach()).

FWIW, I've been getting a panic on bootup for months (mid-April, maybe?)
on -CURRENT on one of my systems; could this be at all related?

Here is some info from the panic I got mid-late April.  I'll try
cvsup'ing and building a new kernel tonite and see if it's fixed, but in
case it isn't here's some info.

Bootup gets to here:
isab0: PCI to ISA bridge (vendor:0e11 device:0002) at device 15.0 on pci0

and them *boom*
Fatal trap 12: page fault while in kernel mode


fault virtual address = 0x24000208
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01456f5
stack pointer = 0x10:0xc02d5ef8
frame pointer = 0x10:0xc02d5f04
code segment = base 0x0, limit 0xf, type 0x1b
 = DRL 0, pres 1, def32 1, gran 1
processor eflags = interrupts enabled, resume, IOPL=0
current process = 0 ( )
interrupt mask = net tty bio cam
kernel: type 12 trap, code:0

DDB reveals
Stopped at device_probe_and_attach+0x9movl  0x8(%ebx),%edi

trace shows:
device_probe_and_attach(24000200) at device_probe_and_attach+0x9
bus_generic_attach(c09e1880, c02d5f38, c0145737, c09e1880, c09e1880)
  at bus_generic_attach+0x16
DEVICE_ATTACH(c09e1880, c09e1880, 0, c061cb40, c02d5f48)
  at DEVICE_ATTACH+0x25




-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Unhappy recent -CURRENT's (was Re: Monday strikes again)

1999-08-24 Thread Matthew D. Fuller

On Tue, Aug 24, 1999 at 03:52:15PM -0500, a little birdie told me
that Matthew D. Fuller remarked
 
 Here is some info from the panic I got mid-late April.  I'll try
 cvsup'ing and building a new kernel tonite and see if it's fixed, but in
 case it isn't here's some info.

Update:
-CURRENT now boots just fine, no problems, except the minor detail that
it fails utterly to detect my PCI bus.  Which, needless to say, is a bit
of an inconvenience, since my ethernet card is on PCI.  This is a Compaq
Presario 575, Pentium 120 processor with 80 megs of RAM.  Ethernet card
is a 3c905.  Everything else seems to work just fine (w/ and w/o PnP
included in kernel config, tho I don't think it affects any hardware I
have).  Verbose boot messages available if someone has time to take a
look.



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: is dumpon/savecore broken?

1999-07-21 Thread Matthew D. Fuller

On Thu, Jul 22, 1999 at 02:19:37AM +0200, a little birdie told me
that Andrzej Bialecki remarked
 On Tue, 20 Jul 1999, Matthew Dillon wrote:
  
  You can do it manually from /etc/rc.  If it doesn't even get that far,
  you used to be able to specify it in the kernel config but I do not know
  if that is possible any more.
 
 I remember doing this once or twice from DDB - writing appropriate values
 to _dumpdev, as they appeared on running system.
 
 Of course, the system can be in such state that this could equally well
 do more harm than good... :-/

But lemme guess...
This won't work with a system that panics before it gets around to
probing the harddrives...

This is one of my present problems  :(



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kvm_getswapinfo is broken

1999-05-26 Thread Matthew D. Fuller
On Tue, May 25, 1999 at 11:38:38PM -0600, a little birdie told me
that Kenneth D. Merry remarked
 
 {panzer:/usr/home/ken:2:0} pstat -s
 Device  1K-blocks UsedAvail Capacity  Type
 /dev/(null)3275520   327552 0%Interleaved
 /dev/(null)3930880   393088 0%Interleaved
 Total  7206400   720640 0%
 
 That's with -current as of Friday.


In a -CURRENT as of early last week, I see the same:
[2:28:11] mortis:~
(ttyp6):{106}% pstat -s
Device  1024-blocks UsedAvail Capacity  Type
/dev/(null)  655232  144   655088 0%Interleaved
/dev/(null)  524160  196   523964 0%Interleaved
/dev/(null)  130944   80   130864 0%Interleaved
/dev/(null)  262016   56   261960 0%Interleaved
/dev/(null)  524160   12   524148 0%Interleaved
Total   2096512  488  2096024 0%

It happened also through the buildworld before that one, which was a few
days before, but not the one before that, which was about a week back (or
something like that).  A quick perusal of the code tells me absolutely
nothing; at a guess, the kvm_read() is turning up nothing there, so I'll
make a wild guess that something moved and forget to tell the post office
to forward its references.



-- 

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew FullerMF4839http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Today's kernel crashes on starting X

1999-05-14 Thread Matthew D. Fuller
On Fri, May 14, 1999 at 02:17:28AM +0200, a little birdie told me
that Sheldon Hearn remarked
 
 
 On Fri, 14 May 1999 01:13:36 +0200, Gianmarco Giovannelli wrote:
 
  Here it continues to panic with screen, same errors of yesterday... I'll
  try with X right now but I think it is the same story... :-)
  Cvsupped and maked world this afternoon (CEST).
 
 Well guesss what? I'm seeing panics too, after suggesting that
 everything was cool and froody. :-)
 
 I don't have to start X, I get a panic as soon as I try to mount_mfs
 -- 100% reproducible. Someone else posted a backtrace, the one that
 incriminates checkalias(), I think?

I have one here with sources cvsup'd around 4am (CDT) today (as in, ~4
hours ago).  Start X, start up screen in an xterm, and *bing*.  However,
I strut my skill in manpiluating DDB while staring at a frozen X session
;

Here's some quickies from kgdb:
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0c00
fault virtual address   = 0x14
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc0162490
stack pointer   = 0x10:0xcb271d4c
frame pointer   = 0x10:0xcb271d60
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 570 (screen-3.7.6)
interrupt mask  = tty  - SMP: XXX
panic: from debugger
mp_lock = 0103; cpuid = 1; lapic.id = 0c00
boot() called on cpu#1

(kgdb) where
#0  0xc014f350 in boot ()
#1  0xc014f6ed in panic ()
#2  0xc012c899 in db_panic ()
#3  0xc012c839 in db_command ()
#4  0xc012c8fe in db_command_loop ()
#5  0xc012ea5f in db_trap ()
#6  0xc0213982 in kdb_trap ()
#7  0xc02265c2 in trap_fatal ()
#8  0xc0226259 in trap_pfault ()
#9  0xc0225ecf in trap ()
#10 0xc0162490 in ttyflush ()
#11 0xc0161bf1 in ttioctl ()
#12 0xc01650fe in ptyioctl ()
#13 0xc0181ad0 in spec_ioctl ()
#14 0xc01812f1 in spec_vnoperate ()
#15 0xc01f64c9 in ufs_vnoperatespec ()
#16 0xc017c045 in vn_ioctl ()
#17 0xc015b73f in ioctl ()
#18 0xc0226886 in syscall ()
#19 0xc02143a5 in Xint0x80_syscall ()


Unfortunately, it seems to be not giving me symbols.  I'll try
recompiling it with makeoptions=-g and see if I can't pull up one more
good panic/dump real quick.



-- 

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew FullerMF4839http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Panic with screen w/info (was Re: Today's kernel crashes on starting X)

1999-05-14 Thread Matthew D. Fuller

Well, this apparently doesn't involve X, only screen.
(X may still be broken/flaky, but this doesn't involve it specifically)
This time I just ran screen on a vty, and *poof*

--
Looking at the trace below, does this look like a (if not the) problem?
#10 0xc0162490 in ttyflush (tp=0xc029dc20, rw=3) at ../../kern/tty.c:1192
1192(*devsw(tp-t_dev)-d_stop)(tp, rw);
(kgdb) print tp
$1 = (struct tty *) 0xc30010b2
(kgdb) print tp-t_dev
Cannot access memory at address 0xc300110a.
--

I can keep this trace and compile tree around for a good while, just let
me know what to poke at and I'll prod it.  Panic msg and trace below.

--
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0c00
fault virtual address   = 0x14
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc0162490
stack pointer   = 0x10:0xcb1c9d4c
frame pointer   = 0x10:0xcb1c9d60
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 372 (screen-3.7.6)
interrupt mask  = tty  - SMP: XXX
panic: from debugger
mp_lock = 0103; cpuid = 1; lapic.id = 0c00
boot() called on cpu#1


#0  boot (howto=256) at ../../kern/kern_shutdown.c:288
#1  0xc014f6ed in panic (fmt=0xc0253514 from debugger) at
../../kern/kern_shutdown.c:451
#2  0xc012c899 in db_panic (addr=-1072290672, have_addr=0, count=-1,
modif=0xcb1c9bc8 )
at ../../ddb/db_command.c:434
#3  0xc012c839 in db_command (last_cmdp=0xc027e870, cmd_table=0xc027e6d0,

aux_cmd_tablep=0xc029ac78) at ../../ddb/db_command.c:334
#4  0xc012c8fe in db_command_loop () at ../../ddb/db_command.c:456
#5  0xc012ea5f in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#6  0xc0213982 in kdb_trap (type=12, code=0, regs=0xcb1c9d0c)
at ../../i386/i386/db_interface.c:157
#7  0xc02265c2 in trap_fatal (frame=0xcb1c9d0c, eva=20) at
../../i386/i386/trap.c:912
#8  0xc0226259 in trap_pfault (frame=0xcb1c9d0c, usermode=0, eva=20)
at ../../i386/i386/trap.c:810
#9  0xc0225ecf in trap (frame={tf_fs = -2147483624, tf_es = -1054801904,
tf_ds = 16777232, 
  tf_edi = -2147483648, tf_esi = 3, tf_ebp = -887317152, tf_isp =
-887317192, 
  tf_ebx = -1070998496, tf_edx = 0, tf_ecx = 16777217, tf_eax = 0,
tf_trapno = 12, 
  tf_err = 0, tf_eip = -1072290672, tf_cs = 8, tf_eflags = 66178,
tf_esp = -1070998496, 
  tf_ss = 3}) at ../../i386/i386/trap.c:436
#10 0xc0162490 in ttyflush (tp=0xc029dc20, rw=3) at ../../kern/tty.c:1192
#11 0xc0161bf1 in ttioctl (tp=0xc029dc20, cmd=2147775504,
data=0xcb1c9ecc, flag=3)
at ../../kern/tty.c:803
#12 0xc01650fe in ptyioctl (dev=0xf700, cmd=2147775504, data=0xcb1c9ecc
\003, flag=3, 
p=0xc9d9ea20) at ../../kern/tty_pty.c:740
#13 0xc0181ad0 in spec_ioctl (ap=0xcb1c9e08) at
../../miscfs/specfs/spec_vnops.c:441
#14 0xc01812f1 in spec_vnoperate (ap=0xcb1c9e08) at
../../miscfs/specfs/spec_vnops.c:129
#15 0xc01f64c9 in ufs_vnoperatespec (ap=0xcb1c9e08) at
../../ufs/ufs/ufs_vnops.c:2327
#16 0xc017c045 in vn_ioctl (fp=0xc1196bc0, com=2147775504,
data=0xcb1c9ecc \003, 
p=0xc9d9ea20) at vnode_if.h:395
#17 0xc015b73f in ioctl (p=0xc9d9ea20, uap=0xcb1c9f80) at
../../kern/sys_generic.c:564
#18 0xc0226886 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 134697096, 
  tf_esi = 134672224, tf_ebp = -1077951692, tf_isp = -887316524,
tf_ebx = 672221300, 
  tf_edx = 134697128, tf_ecx = 6, tf_eax = 54, tf_trapno = 12, tf_err
= 2, 
  tf_eip = 671965400, tf_cs = 31, tf_eflags = 582, tf_esp =
-1077951716, tf_ss = 47})
at ../../i386/i386/trap.c:1066
#19 0xc02143a5 in Xint0x80_syscall ()
--



-- 

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew FullerMF4839http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Panic with screen w/info (was Re: Today's kernel crashes on starting X)

1999-05-14 Thread Matthew D. Fuller
On Fri, May 14, 1999 at 01:36:41PM -0400, a little birdie told me
that Luoqi Chen remarked
 Here's the better fix, please let me know if it works,

I won't be in a position to crash this box again until tomorrow, but I'll
give it a whirl then.

Thanks.

 Index: tty_pty.c
 ===
 RCS file: /home/ncvs/src/sys/kern/tty_pty.c,v
 retrieving revision 1.57
 diff -u -r1.57 tty_pty.c
 --- tty_pty.c 1999/05/08 06:39:43 1.57
 +++ tty_pty.c 1999/05/14 17:32:33
 @@ -674,8 +674,7 @@
   tp-t_lflag = ~EXTPROC;
   }
   return(0);
 - } else
 - if (devsw(dev)-d_open == ptcopen)
 + } else if (devsw(dev)-d_open == ptcopen) {
   switch (cmd) {
  
   case TIOCGPGRP:
 @@ -711,7 +710,16 @@
   pti-pt_flags = ~PF_REMOTE;
   ttyflush(tp, FREAD|FWRITE);
   return (0);
 + }
 +
 + /*
 +  * The rest of the ioctls shouldn't be called until 
 +  * the slave is open. (Should we return an error?)
 +  */
 + if ((tp-t_state  TS_ISOPEN) == 0)
 + return (0);
  
 + switch (cmd) {
  #ifdef COMPAT_43
   case TIOCSETP:
   case TIOCSETN:
 @@ -735,6 +743,7 @@
   ttyinfo(tp);
   return(0);
   }
 + }
   error = (*linesw[tp-t_line].l_ioctl)(tp, cmd, data, flag, p);
   if (error == ENOIOCTL)
error = ttioctl(tp, cmd, data, flag);



-- 

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew FullerMF4839http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: the new config and booting

1999-05-12 Thread Matthew D. Fuller
On Thu, May 13, 1999 at 12:16:17PM +1200, a little birdie told me
that Joerg Micheel remarked
 
 Virgin systems is not virgin disks. If you buy a complete PC, this
 bootloader from Redmonton is already on the disk. I had similiar
 problems a while back and unless someone has explicitely looked
 after this, it still persits.

I just last night did a full install onto a set of fresh virgin disks in
a fresh virgin system (all bought component-at-a-time) without using DD.



-- 

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew FullerMF4839http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



-CURRENT told me to panic when it booted, so I did

1999-04-28 Thread Matthew D. Fuller
I get a thoroughtly reproducible (in fact, utterly non-un-reproducible)
panic on boot of recent -CURRENTs.  It did this on a cvsup from maybe 2,
3 days ago, and again with one done ~4pm CDT today.

Note: all these messages are hand-copied, this machine isn't in a
situation where it's easy to put a serial console on it  :(

Bootup gets as far as:
isab0: PCI to ISA bridge (vendor:0e11 device:0002) at device 15.0 on pci0
which immediately suceeds probing xl0.  -v doesn't show anything more
revealing.  Panic reads as:
Fatal trap 12: page fault while in kernel mode

fault virtual address = 0x24000208
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01456f5
stack pointer = 0x10:0xc02d5ef8
frame pointer = 0x10:0xc02d5f04
code segment = base 0x0, limit 0xf, type 0x1b
 = DRL 0, pres 1, def32 1, gran 1
processor eflags = interrupts enabled, resume, IOPL=0
current process = 0 ( )
interrupt mask = net tty bio cam
kernel: type 12 trap, code:0

DDB reveals
Stopped at device_probe_and_attach+0x9movl  0x8(%ebx),%edi

The first few nuggets of creamy goodness 'trace' reveals are:
device_probe_and_attach(24000200) at device_probe_and_attach+0x9
bus_generic_attach(c09e1880, c02d5f38, c0145737, c09e1880, c09e1880)
  at bus_generic_attach+0x16
DEVICE_ATTACH(c09e1880, c09e1880, 0, c061cb40, c02d5f48)
  at DEVICE_ATTACH+0x25


If previous items in the trace (I think there were around 6 of them)
would be helpful, I can grab them; it's just a pain copying the !$
things down  ;)

Ideas?  Trashing it isn't really an option, I use it too much.  It's not
a critical server, so I can experiment with patches/etc on it, but it's
my main workstation here, so I'd rather not trash it utterly in the
process.

It's presently up running this 3-day old -CURRENT world and a kernel
from...   early March, I think, working fine.

System is a Compaq Deskpro 575, P120 processor, 80 megs RAM, 1 floppy, 1
IDE drive, built-in lnc1 (which doesn't get along with the lnc driver),
xl0 used as net card, parallel port ZIP drive.  Kernel config follows:


#
# GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks
#
# For more information read the handbook part System Administration - 
# Configuring the FreeBSD Kernel - The Configuration File. 
# The handbook is available in /usr/share/doc/handbook or online as
# latest version from the FreeBSD World Wide Web server 
# URL:http://www.FreeBSD.ORG/
#
# An exhaustive list of options and more detailed explanations of the 
# device lines is present in the ./LINT configuration file. If you are 
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
#   $Id: GENERIC,v 1.166 1999/04/24 21:45:44 peter Exp $

machine i386
cpu I586_CPU
ident   NEWTAURUS
maxusers64

makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols

options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options MFS #Memory Filesystem
options NFS #Network Filesystem
options MSDOSFS #MSDOS Filesystem
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=2000 #Be pessimistic about Joe SCSI device
options UCONSOLE#Allow users to grab the console
options FAILSAFE#Be conservative
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options DDB
options MAXMEM=(80*1024)

config  kernel  root on wd0


controller  isa0
controller  pnp0# PnP support for ISA
controller  eisa0
controller  pci0

controller  fdc0at isa? port IO_FD1 irq 6 drq 2
diskfd0 at fdc0 drive 0

controller  wdc0at isa? port IO_WD1 irq 14
diskwd0 at wdc0 drive 0

controller  wdc1at isa? disable port IO_WD2 irq 15
diskwd2 at wdc1 drive 0


controller  scbus0

device  da0 #Only need one of these, the code dynamically grows
device  sa0
device  pass0

# atkbdc0 controls both the keyboard and the PS/2 mouse
controller  atkbdc0 at isa? port IO_KBD
device  atkbd0  at atkbdc? irq 1
device  psm0at atkbdc? irq 12

device  vga0at isa? port ? conflicts

# splash screen/screen saver
pseudo-device   splash

# syscons is the default console driver, resembling an SCO console
device  sc0 at isa?


device  npx0at nexus? port IO_NPX irq 13


device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3

# Parallel port
device 

Re: swap-related problems

1999-04-14 Thread Matthew D. Fuller
On Wed, Apr 14, 1999 at 01:12:00PM -0400, a little birdie told me
that Mikhail Teterin remarked
 
 Aha, now its clearer. May be, since we are do not conform anyway,
 we can design some clever way of notifying a program rather then
 SIGKILL-ing it?
 
 Perhaps, SIGBUS? Something, a program can catch, if it is prepared
 to, and, may be, do some syscall to find out which chunk of memory
 can not actually be used by it...

I think you're missing a point here.  (Or maybe I am, I don't know that
much about it myself).  The program that gets killed is NOT necessarily
the program that tried to access something causing a memory overcommit;
rather, the program that gets killed is the largest program around.
Often, they'll probably coincide, but by no means necessarily.

You'd also have to rely on somebody not writing a program that, inside
the SIGBUS handler, allocates and touches more memory, causing a SIGBUS,
causing more allocation, etc etc etc.  Lets try not opening any more
DoSen than there already are, 'K?



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: cvsup

1999-04-13 Thread Matthew D. Fuller
On Mon, Apr 12, 1999 at 10:52:52PM -0700, a little birdie told me
that John Polstra remarked
 
 Also, try the -s option.  (Read about it first in cvsup(1).)  It
 greatly reduces disk activity and will make your updates go faster,
 possibly with snappier GUI updates too.

Damn, I should RTFM more often  ;)
I could definately like this.


 The GUI performance varies widely between systems.  It was so-so
 on my old P/90, but it's pretty good on my PII/400.  It may be the
 disk activity that kills the GUI performance.  Disk operations are
 non-interruptible, so if the disk is really busy the GUI thread
 doesn't get control often enough.  (I'm guessing and could be totally
 wrong, though.)

As a data point, CVSup runs nicely, but if I iconify it and deiconify it,
it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay
itself completely.  Sucking down CVS repo to /usr/cvs (async, noatime).
Under 2.2-S, mind you.



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: cvsup

1999-04-13 Thread Matthew D. Fuller
On Tue, Apr 13, 1999 at 08:29:30AM -0700, a little birdie told me
that John Polstra remarked
 Matthew D. Fuller wrote:
  
  As a data point, CVSup runs nicely, but if I iconify it and deiconify it,
  it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay
  itself completely.
 
 Yes, that's when the problem is most obvious.
 
 Here's the bottom line from my point of view.  CVSup is slow to update
 the GUI because it is busy doing more important things, i.e., updating
 your files as quickly as it can.  I agree that it can be annoying.
 But would you really want me to slow down file updates just so the GUI
 could look better?

Oh god no; by all means, make the file updates faster!!
After about 4 days without cvsup'ing (including lots of fun gcc/egcs)
updates it took 6:16 to update my CVS repo including:
*default release=cvs
src-all
src-eBones
src-secure
ports-all
www
doc-all



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: cvsup

1999-04-13 Thread Matthew D. Fuller
On Tue, Apr 13, 1999 at 03:41:46PM -0700, a little birdie told me
that John Polstra remarked
 Matthew D. Fuller wrote:
 
  After about 4 days without cvsup'ing (including lots of fun gcc/egcs)
  updates it took 6:16 to update my CVS repo including:
 
 When CVSup is fetching entirely new files, it can't do anything much
 smarter than compress them.  It can't avoid moving the bits from point
 A to point B.  In the case of egcs, that's a lot of bits.
 
 But six hours and sixteen minutes?  That's awfully slow.  You must
 have had a really bad link that day.  I'd try a few different mirror
 sites if I were you.

Nono, 6 minutes and 16 seconds  :P
*lovin it*



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



crypt algorithms (was Re: DES from source?)

1999-04-03 Thread Matthew D. Fuller
On Sat, Apr 03, 1999 at 05:34:06PM +0200, a little birdie told me
that Dag-Erling Smorgrav remarked
 
  Do I need to change all passwd with 'passwd {user}' to use DES passwd crypt?
 
 Existing MD5 passwords will still work. New users will get DES
 passwords.

Did we ever hash out a mechanism to do this the other way (or integrate
new algorithms) and set 'try' vs. 'use' algorithms?  I'm unclear as to
whether PAM is supposed to/capable of addressing this.



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: /var/db/pkg/.mkversion

1999-04-01 Thread Matthew D. Fuller
[ Yes, I'm sticking my nose in where it probably doesn't belong and
should get chopped off for it.  It's a hobby ;]

On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me
that Satoshi - the Wraith - Asami remarked
 
 The same situation arises whether the version info is in /var/db/pkg
 or /some/other/place.  It has been pointed out many times in the past
 that we need something to ensure bsd.port.mk can synchronize itself
 with the rest of the system (simply because there are too many people
 who cvsup one without the other).
 
 The question is, can I ask you to make sysinstall write some kind of
 version info that can be used by bsd.port.mk to identify the age of
 the system?

This would require a little more work on the 'back' side, but what would
be so hard about just checking $Id$ strings around the .mk files?  If
not for the revision, at least for the date.


 The problem is real, we've been bitten too many times in the past
 (haven't you seen all the where's fetch -A? and other more subtle

Well, certainly, it's not always feasible, but I never understood this
one in particular.  It always seemed like a PERFECT candidate for an
OSVERSION (or whatever) bump; certainly the 3.1+ only, since pre-3.1
didn't have the -A (3.1 didn't either, but that would cut out all the
complaints from pre-3.1'ers).



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: /etc/rc.conf, take 46!

1999-03-23 Thread Matthew D. Fuller
On Tue, Mar 23, 1999 at 12:49:52PM +0200, a little birdie told me
that Sheldon Hearn remarked
 On Sun, 21 Mar 1999 18:06:41 PST, Jordan K. Hubbard wrote:
 
   if [ -f /etc/defaults/rc.conf ]; then
  . /etc/defaults/rc.conf
  -elif [ -f /etc/rc.conf ]; then
  -   . /etc/rc.conf
  +   for i in ${rc_conf_files}; do
  +   if [ -f $i ]; then
  +   . $i
  +   fi
  +   done
   fi
 
 Hi Jordan,
 
 What's the idea behind ignoring rc_conf_files just because we can't find
 /etc/defaults/rc.conf?

I have to jump in here and say 'Because that's where it's DEFINED'.

Sorry, I had to stick my nose in somewhere  ;)



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller  http://www.over-yonder.net/ |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: uptime weirdnessl

1999-02-18 Thread Matthew D. Fuller
On Thu, Feb 18, 1999 at 07:05:39PM -0500, a little birdie told me
that Brian Feldman remarked
  On Thu, Feb 18, 1999, Erik Funkenbusch put this into my mailbox:
   
   Any ideas?
 
 Yes. Look at /var/run/wtmp. Look CAREFULLY at /dev/null.

Look even more carefully at /var/run/utmp, since wtmp is in /var/log and
doesn't affect w/uptime anyway.  O:-)



---

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller http://www.over-yonder.net/~fullermd |
* fulle...@futuresouth.com   fulle...@over-yonder.net *
| UNIX Systems Administrator  Specializing in FreeBSD |
*   FutureSouth Communications   ISPHelp ISP Consulting   *
|  The only reason I'm burning my candle at both ends,   |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



  1   2   >