On 05/06/11 13:52, Matthew Dempsky wrote:
> If you have a sili(4) or ahci(4), I'd appreciate a quick test of the
> diff below. As long as you can still mount your disks without
> panicking, then it worked. :)
>
> One test for each is sufficient, so please reply to the list to save
> others from r
On Fri, May 06, 2011 at 10:52:19AM -0700, Matthew Dempsky wrote:
> If you have a sili(4) or ahci(4), I'd appreciate a quick test of the
> diff below. As long as you can still mount your disks without
> panicking, then it worked. :)
>
> One test for each is sufficient, so please reply to the list
On Fri, May 6, 2011 at 7:52 PM, Matthew Dempsky wrote:
> If you have a sili(4) or ahci(4), I'd appreciate a quick test of the
> diff below. As long as you can still mount your disks without
> panicking, then it worked. :)
>
> One test for each is sufficient, so please reply to the list to save
>
On Fri, May 06, 2011 at 09:46:35PM +0200, Otto Moerbeek wrote:
> On Fri, May 06, 2011 at 09:34:56PM +0200, Otto Moerbeek wrote:
>
> > On Fri, May 06, 2011 at 05:15:34PM +0200, David Coppa wrote:
> >
> > > On Fri, May 6, 2011 at 1:55 PM, Jasper Lievisse Adriaanse
> > > wrote:
> > >
> > > > sparc
On Fri, May 06, 2011 at 09:34:56PM +0200, Otto Moerbeek wrote:
> On Fri, May 06, 2011 at 05:15:34PM +0200, David Coppa wrote:
>
> > On Fri, May 6, 2011 at 1:55 PM, Jasper Lievisse Adriaanse
> > wrote:
> >
> > > sparc64 and loongson here, no issues.
> >
> > Works for me as well, amd64 and i386.
> I'm all for killing the ksh autoswitch feature. Whenever I end up on a
> system with EDITOR set to vi and ksh as shell I'm lost. If people like to
> use a specific mode they should add it to .profile.
>
I'm not, I use ksh and like the fact that it makes my history
keystrokes appropriate
for my e
On Fri, May 06, 2011 at 05:15:34PM +0200, David Coppa wrote:
> On Fri, May 6, 2011 at 1:55 PM, Jasper Lievisse Adriaanse
> wrote:
>
> > sparc64 and loongson here, no issues.
>
> Works for me as well, amd64 and i386.
>
> ciao,
> David
asmatthieu@ found out hppa does not work. I can fonfirm tha
Aerosmith Rocks o Draw The Line
Live! Bootleg Night in the Ruts Rock
In A Hard Place Done
With Mirrors Classics Live! Io
On Fri, May 06, 2011 at 08:12:43PM +0200, Reyk Floeter wrote:
> hi,
>
> the following diff needs some serious testing in existing setups.
> it does not add any new features...
>
> ...but it reorganizes, shuffles, and changes the relayd code and
> internal APIs and it introduces an privsep API tha
If you have a sili(4) or ahci(4), I'd appreciate a quick test of the
diff below. As long as you can still mount your disks without
panicking, then it worked. :)
One test for each is sufficient, so please reply to the list to save
others from redundant effort.
Index: ata/atascsi.c
===
On Fri, 06 May 2011 14:22:05 BST, Stuart Henderson wrote:
> If you have something which handles ENV (i.e. an interactive shell),
> isn't it already the case that you can run arbitrary commands?
I suppose it is not as bad as BASH_ENV (which is used for non-interactive
shells). I'm still not comfo
On Fri, May 6, 2011 at 1:55 PM, Jasper Lievisse Adriaanse
wrote:
> sparc64 and loongson here, no issues.
Works for me as well, amd64 and i386.
ciao,
David
Further to the earlier diff, this accomodates bob's New User verbiage
and logic from the install routine when someone answers "yes" to a
question where that is not an option, e.g. -config_create
-mark
Index: adduser.8
===
RCS file: /
Hi,
I remember exactly it has been working in the pre 4.9 times. now it
doesn't again, but may be I am missing something:
test net scheme:
router 1 (gif0) - (gif0) router 2
here's what hapenning:
router 1:
# ospfctl s i
Interface AddressState HelloTimer Linkstate Uptime
On 2011/05/06 08:49, Todd C. Miller wrote:
> On Fri, 06 May 2011 11:37:53 BST, Stuart Henderson wrote:
>
> > I'm not entirely convinced it's safe to add ENV to env_keep by
> > default but the only other workaround I've found (i.e. ln -s
> > /usr/bin/{vi,not_emacs} and setting VISUAL=/usr/bin/not_e
On Fri, 06 May 2011 11:37:53 BST, Stuart Henderson wrote:
> I'm not entirely convinced it's safe to add ENV to env_keep by
> default but the only other workaround I've found (i.e. ln -s
> /usr/bin/{vi,not_emacs} and setting VISUAL=/usr/bin/not_emacs)
> is messy and annoying to do on multiple machi
On Fri, May 06, 2011 at 12:46:40PM +0200, Claudio Jeker wrote:
> On Fri, May 06, 2011 at 11:37:53AM +0100, Stuart Henderson wrote:
> > sudo doesn't preserve ENV by default, so any shell settings (e.g.
> > set -o emacs) you might have in your ${ENV} file don't take effect.
> >
> > for people who li
On Fri, May 06, 2011 at 10:15:28AM +0100, Stuart Henderson wrote:
> Just noticed I still have Ms for this. Has it been tested on enough
> arch yet? So far I know it's been run on
>
> amd64 (sthen)
> armish (sthen)
> i386 (aja, sthen)
> macppc (aja, sthen)
> loongson (phessler)
>
> Any others? Con
I'm actually running with this for a week or so as well, amd64 and
i386, didn't notice breakage
* Stuart Henderson [2011-05-06 11:17]:
> Just noticed I still have Ms for this. Has it been tested on enough
> arch yet? So far I know it's been run on
>
> amd64 (sthen)
> armish (sthen)
> i386 (aja,
Add swapctrlcaps to Norwegian map.
Tested on laptop with and without usb keyboard attached on boot,
with no.swapctrlcaps in /etc/kbdtype.
Don't need remapping for X11 in .xmodmaprc anymore.
Index: sys/dev/pckbc/wskbdmap_mfii.c
===
RC
sudo doesn't preserve ENV by default, so any shell settings (e.g.
set -o emacs) you might have in your ${ENV} file don't take effect.
for people who like EDITOR=vi but also like "set -o emacs" in the
shell, this is really annoying; EDITOR/VISUAL are preserved, so the
(imo horrible) /bin/ksh "featu
On Fri, May 06, 2011 at 11:37:53AM +0100, Stuart Henderson wrote:
> sudo doesn't preserve ENV by default, so any shell settings (e.g.
> set -o emacs) you might have in your ${ENV} file don't take effect.
>
> for people who like EDITOR=vi but also like "set -o emacs" in the
> shell, this is really
This is based on a diff by Patrick Coleman.
Quoting his correct analysis:
> I believe ospfd/ospf6d are incorrectly handling states for loopback
> interfaces - basically, if the interface is down when the daemon is
> started, it comes up in state LOOP anyway. if_fsm then throws the
> error "if_fsm:
On Fri, 6 May 2011, Stuart Henderson wrote:
> Just noticed I still have Ms for this. Has it been tested on enough
> arch yet? So far I know it's been run on
>
> amd64 (sthen)
> armish (sthen)
> i386 (aja, sthen)
> macppc (aja, sthen)
> loongson (phessler)
>
> Any others? Considering how much it
Just noticed I still have Ms for this. Has it been tested on enough
arch yet? So far I know it's been run on
amd64 (sthen)
armish (sthen)
i386 (aja, sthen)
macppc (aja, sthen)
loongson (phessler)
Any others? Considering how much it sucks if ld.so is broken, it would
be good to have reports from a
The interface to sending new user welcome messages in adduser(8)
isn't very intuitive. For example when setting up the config file
using:
# adduser -config_create
Eventually you are asked:
Send message from file: /etc/adduser.message no [no]:
If you answer "yes", adduser takes your input as the
26 matches
Mail list logo
