headers
kjell | 1 Aug 2006 02:11
Favicon

Re: man fdisk tell more about print command

> >Seriously. Unless your mouth is still frozen from a trip to the dentist,
> >you CANNOT utter the term "mibibyte" without feeling like an idiot.
> 
> It's actually Mebibytes. I don't know about you, but for someone
> used to German it's pretty easy (may be my part-polish heritage).

Oh, that's so much better. Because kibibyte doesn't sound idiotic
in the least. Not remotely close to to Kilobyte-with-a-frozen-tongue.

-kj
Permalink | Reply | 0 comments |
headers
Deanna Phillips | 2 Aug 2006 08:47
Picon
Favicon

hotplugd takes anything as an argument

Hi,

Seems any user can run hotplugd -d <anything>, which causes it
to loop forever trying to write an an unknown event to syslog.

Like..

$ /usr/sbin/hotplugd -d ~/kitten.avi

$ tail /var/log/daemon
Aug  2 02:27:03 poa-alpina hotplugd[32175]: unknown event (0xb77)
Aug  2 02:27:03 poa-alpina hotplugd[32175]: unknown event (0x0)
Aug  2 02:27:03 poa-alpina hotplugd[32175]: unknown event (0x27c)
Aug  2 02:27:03 poa-alpina hotplugd[32175]: unknown event (0x0)
Aug  2 02:27:03 poa-alpina hotplugd[32175]: unknown event (0xf8c)
Aug  2 02:27:03 poa-alpina hotplugd[32175]: unknown event (0x0)

[...]

Aug  2 02:27:33 poa-alpina last message repeated 464559 times
Aug  2 02:29:34 poa-alpina last message repeated 1767570 times
Aug  2 02:39:35 poa-alpina last message repeated 8555548 times

How's this?

Index: hotplugd.8
===================================================================
RCS file: /cvs/src/usr.sbin/hotplugd/hotplugd.8,v
retrieving revision 1.5
diff -u -p -r1.5 hotplugd.8
(Continue reading)

Permalink | Reply | 3 comments |
headers
Ted Unangst | 2 Aug 2006 23:42
Picon

Re: hotplugd takes anything as an argument

On 8/1/06, Deanna Phillips <deanna <at> sdf.lonestar.org> wrote:
> Seems any user can run hotplugd -d <anything>, which causes it
> to loop forever trying to write an an unknown event to syslog.

"fixing" hotplugd won't change anything if you consider this a
problem.  any user can still write to syslog all they want.
Permalink | Reply | 1 comment |
headers
Deanna Phillips | 3 Aug 2006 00:28
Picon
Favicon

Re: hotplugd takes anything as an argument

Hi,

"Ted Unangst" <ted.unangst <at> gmail.com> writes:

> On 8/1/06, Deanna Phillips <deanna <at> sdf.lonestar.org> wrote:
>> Seems any user can run hotplugd -d <anything>, which causes it
>> to loop forever trying to write an an unknown event to syslog.
>
> "fixing" hotplugd won't change anything if you consider this a
> problem.  any user can still write to syslog all they want.

Hmm I never said that anything was broken.  I was only
suggesting what seemed like an improvement -- and I hardly even
considered it as an abuse issue.  See, when mistakenly run with
an invalid device, there's no sign that anything is going wrong
until one looks at the logs or notices the resource drain.

I am all for giving users plenty of rope, but I see no reason to
lay traps for them.
Permalink | Reply | 0 comments |
headers
Marc Balmer | 3 Aug 2006 16:38
Picon
Favicon

watchdogd

some hardware watchdog timers always change the default timeout period
of 30 seconds, because they only have a set of fixed values.  in these
cases you will always see 'watchdogd: period adjusted to nn by device'
when you start watchdogd(8)

as I have a lot of such devices this annoys me, I want it to be quiet to
have the same output on all device when they boot.

this small patch adds the option '-q' to watchdogd(8).

any objections?

Index: usr.sbin/watchdogd/watchdogd.8
===================================================================
RCS file: /cvs/src/usr.sbin/watchdogd/watchdogd.8,v
retrieving revision 1.7
diff -u -r1.7 watchdogd.8
--- usr.sbin/watchdogd/watchdogd.8	17 Jan 2006 14:27:04 -0000	1.7
+++ usr.sbin/watchdogd/watchdogd.8	3 Aug 2006 14:33:40 -0000
 <at>  <at>  -22,7 +22,7  <at>  <at> 
 .Nd watchdog timer retrigger daemon
 .Sh SYNOPSIS
 .Nm watchdogd
-.Op Fl d
+.Op Fl dq
 .Op Fl i Ar interval
 .Op Fl p Ar period
 .Sh DESCRIPTION
 <at>  <at>  -55,6 +55,9  <at>  <at> 
 If this option is specified,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andrés | 4 Aug 2006 01:28
Picon

A small script to find unused dependencies which, IMHO, should be included in the tree

I'm not experienced in shell scripting, so you may find lots of
errors, but I think this is a good start.

This script will find packages which are not used by others. In that
category falls three types of packages:

1. Packages that I use and I do know
2. Packages that I use and I don't know
3. Packages that were installed by others, and aren't used right now,
because I uninstalled the packages that depended upon it.

The goal is to make the removal of the third type easier.

pkg_check asks for every package it finds, you can delete it, keep it,
or see if you use it (looking to the package contents). It has two
modes: interactive and non-interactive, the last just prints to the
stdout the packages it finds.

Well, I hope this may be useful to the project, the first time I used
it I deleted tons of packages (without ever needed something after
that). I think it is a great tool for pkg_* stuff. A t least until
something smarter comes up.

Here it is:

#!/bin/sh

# Copyright (c) 2006 AndrC)s Delfino <adelfino <at> gmail.com>

# Permission to use, copy, modify, and distribute this software for any
(Continue reading)

Permalink | Reply | 4 comments |
headers
Will Maier | 4 Aug 2006 01:47
Gravatar

Re: A small script to find unused dependencies which, IMHO, should be included in the tree

On Thu, Aug 03, 2006 at 08:28:02PM -0300, Andr'es wrote:
> This script will find packages which are not used by others. In that
> category falls three types of packages:

Wouldn't this script be more appropriate somewhere in the
/usr/ports/infrastructure directory? I imagine your mail would be
more appropriate on ports <at> .

--

-- 

o--------------------------{ Will Maier }--------------------------o
| web:.......http://www.lfod.us/ | email.........willmaier <at> ml1.net |
*------------------[ BSD Unix: Live Free or Die ]------------------*
Permalink | Reply | 1 comment |
headers
Andrés | 4 Aug 2006 02:03
Picon

Re: A small script to find unused dependencies which, IMHO, should be included in the tree

I don't know, :/ I guess the script make sense along the other pkg_* tools.

On 8/3/06, Will Maier <willmaier <at> ml1.net> wrote:
> On Thu, Aug 03, 2006 at 08:28:02PM -0300, Andr'es wrote:
> > This script will find packages which are not used by others. In that
> > category falls three types of packages:
>
> Wouldn't this script be more appropriate somewhere in the
> /usr/ports/infrastructure directory? I imagine your mail would be
> more appropriate on ports <at> .
>
> --
>
> o--------------------------{ Will Maier }--------------------------o
> | web:.......http://www.lfod.us/ | email.........willmaier <at> ml1.net |
> *------------------[ BSD Unix: Live Free or Die ]------------------*
>
>

--

-- 
AndrC)s Delfino
Permalink | Reply | 0 comments |
headers
Ray Lai | 4 Aug 2006 08:36

Re: A small script to find unused dependencies which, IMHO, should be included in the tree

I think it would be better to have it written in Perl, since the file
locations or contents may change but the API is less likely to.

-Ray-

On Thu, Aug 03, 2006 at 08:28:02PM -0300, Andr??s wrote:
> I'm not experienced in shell scripting, so you may find lots of
> errors, but I think this is a good start.
> 
> This script will find packages which are not used by others. In that
> category falls three types of packages:
> 
> 1. Packages that I use and I do know
> 2. Packages that I use and I don't know
> 3. Packages that were installed by others, and aren't used right now,
> because I uninstalled the packages that depended upon it.
> 
> The goal is to make the removal of the third type easier.
> 
> pkg_check asks for every package it finds, you can delete it, keep it,
> or see if you use it (looking to the package contents). It has two
> modes: interactive and non-interactive, the last just prints to the
> stdout the packages it finds.
> 
> Well, I hope this may be useful to the project, the first time I used
> it I deleted tons of packages (without ever needed something after
> that). I think it is a great tool for pkg_* stuff. A t least until
> something smarter comes up.
> 
> Here it is:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Sideris Michael | 4 Aug 2006 09:15
Picon

Re: A small script to find unused dependencies which, IMHO, should be included in the tree

I think that the feature you are trying to implement here should be
available through in pkg_delete. Either being the automatic action to
take, like, delete the main package and its dependencies as long as they
are not used by any other packages, or as an option using -F. Anyway,
the concept is good, I wanted to do the same at some point but, you got
me :)
Permalink | Reply | 0 comments |

Gmane