> But what I need is /home/{$USER}/Maildir/ in order for Mutt to
> work with Maildirs. The above /etc/login.conf parts don't do the
> trick and other occurrences of MAIL I can't find.
>
> So what gives? (IOW please help! :)
You can set MAIL via /etc/login.conf, all applications that use
either
On Sat, Jan 20, 2001 at 11:11:39PM -0500, Andrew Gallatin wrote:
>
> Nicolas Souchu writes:
> <...>
> > What is the hose field?
>
> It is for server-class alphas. Alphas do their peer PCI buses a
> little differently. Rather than have a ppb between "peer" pci buses,
> each different peer bus
On Sat, Jan 20, 2001 at 04:35:11PM -0800, John Baldwin wrote:
> Look in /sys/compile/ after compiling a kernel, it should be in pci_if.*
> It's a function that ues kobj to lookup the pci_read_config method in the
> parent bus. Look in the PCI code to find the real pci_read_config...
>
> >From s
Bjoern Fischer wrote:
>
> > ...
> > So what gives? (IOW please help! :)
>
> You can set MAIL via /etc/login.conf, all applications that use
> either login(1) or setusercontext(3) should work.
>
> Beware of ssh! The OpenSSH client, that is part of FreeBSD is
> completey buggy here: It sets MAIL
Hi,
I started experimenting with kernel hacking to write an
infrared device driver. Therfore I read Alexander Langer's
article on DaemonNews and started modifying the led.c
example code.
Unfortunately I can't get my interrupt handler working.
Could anyone please have a short look on my code.
O
Hi all,
Sorry if this is the wrong place to post this, but
I think it needs attention.
Could someone from FreeBSD contact them to get the prob
resolved ?
This MX is nowhere near me, about 15 hops away!
Thanks
Jamie
On 2001.01.21 17:01:32 + Mail Delivery Subsystem wrote:
The original mes
On Sun, Jan 21, 2001 at 05:06:16PM +, Jamie Heckford wrote:
> Hi all,
>
> Sorry if this is the wrong place to post this, but
> I think it needs attention.
>
> Could someone from FreeBSD contact them to get the prob
> resolved ?
>
> This MX is nowhere near me, about 15 hops away!
>
FreeBSD
This: bus_teardown_intr(dev, sc->irq, sc->ih) != 0 ); looks pretty odd. See
your ir_detach().
Alex wrote:
> Hi,
>
> I started experimenting with kernel hacking to write an
> infrared device driver. Therfore I read Alexander Langer's
> article on DaemonNews and started modifying the led.c
> examp
Hi,
Martin Blapp ([EMAIL PROTECTED]) and I have been poking at a seemingly broken
linux_connect() in the linux emulation suite. Now I'm actually curious,
because there's a little voodoo going on which I don't quite understand
and I'd appreciate some clued people explaining it.
* inside a syscal
Also have a look at:
http://www.FreeBSD.org/cgi/cvsweb.cgi/syssrc/sys/compat/
linux/common/linux_socket.c?rev=1.21.2.2
&content-type=text/x-cvsweb-markup&cvsroot=netbsd
(Add these three lines together)
There is a comment form linux_connect():
*/
* We should only let this call succeed once p
As mentioned often before ( :-) ) I'm porting a compiler.
Currently, I'm working on the last bits, and one of the things left is
the possibility to do port-access as root from userland under Linux.
Does FreeBSD have any possibility to this?
Marco van de Voort ([EMAIL PROTECTED] or [EMAIL PRO
Adrian Chadd <[EMAIL PROTECTED]> writes:
> * inside a syscall, if I return (value); what happens?
errno gets set to that value, and if it's non-zero, the userland
syscall code returns -1 to the caller.
> * inside a syscall, if I set p->p_retval[0] to something, and then
> return (value); what
Neil Blakey-Milner wrote:
>
> On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> > All,
> >
> > I've committed these changes for cron to support DST change
> > to -current (see PR bin/24494 for description of my tests).
> > Everyone is welcome to test them out.
> > Please let me know if you encoun
On Sat, Jan 20, 2001 at 01:19:17PM -0800, Luigi Rizzo wrote:
> > I think this is a BIOS issue. I don't think any BIOS will let you
> > boot from arbitrarily-formatted floppies :)
>
> the 1480 format works.
Have you got this working now - or was it the larger size that didn't
work?
Joe
>
>
Hello,
I was thinking about securelevels this afternoon and my brain came up
with an idea: what about if we could set fine-grained securelevels? Like,
each securelevel could have its own set of prohibitons and that could
only be changed setting some option in the kernel and compiling a new
Someone forwarded me Bjorn's post.
> You can set MAIL via /etc/login.conf, all applications that use
> either login(1) or setusercontext(3) should work.
>
> Beware of ssh! The OpenSSH client, that is part of FreeBSD is
> completey buggy here: It sets MAIL to /var/mail/$USER, this is
> hardcoded.
Sergey Babkin wrote:
> Neil Blakey-Milner wrote:
> >
> > On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> > > All,
> > >
> > > I've committed these changes for cron to support DST change
> > > to -current (see PR bin/24494 for description of my tests).
> > > Everyone is welcome to test them out
Sergey Babkin wrote:
>
> Neil Blakey-Milner wrote:
> >
> > On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> > > All,
> > >
> > > I've committed these changes for cron to support DST change
> > > to -current (see PR bin/24494 for description of my tests).
> > > Everyone is welcome to test them ou
On 21 Jan 2001, at 14:50, Sergey Babkin wrote:
> Neil Blakey-Milner wrote:
> >
> > On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> > > All,
> > >
> > > I've committed these changes for cron to support DST change
> > > to -current (see PR bin/24494 for description of my tests).
> > > Everyone i
Jamie Heckford wrote:
> Sorry if this is the wrong place to post this, but
> I think it needs attention.
It is the wrong place and the only attention it needs is from
you. Read the message and understand it -- that should not be
too hard for somebody who claims to be:
> Chief Network Engineer
Quoting Sergey Babkin <[EMAIL PROTECTED]>:
> All,
>
> I've committed these changes for cron to support DST change
> to -current (see PR bin/24494 for description of my tests).
> Everyone is welcome to test them out.
> Please let me know if you encounter any problems caused by them
> (and better
In message <[EMAIL PROTECTED]> "Alex" writes:
: This is a multi-part message in MIME format.
:
: --=_NextPart_000__01C083CD.0EB2B120
: Content-Type: text/plain;
: charset="iso-8859-1"
: Content-Transfer-Encoding: 7bit
:
: Hi,
:
: I started experimenting with kernel hacking to writ
In message <3A6B3B82.15538.103246@localhost> "Marco van de Voort" writes:
: Does FreeBSD have any possibility to this?
See /dev/io.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> "Giovanni P.
Tirloni" writes:
: I was thinking about securelevels this afternoon and my brain came up
: with an idea: what about if we could set fine-grained securelevels? Like,
: each securelevel could have its own set of prohibitons and that could
: only be ch
"Giovanni P. Tirloni" <[EMAIL PROTECTED]> writes:
> I was thinking about securelevels this afternoon and my brain came up
> with an idea: what about if we could set fine-grained securelevels? Like,
> each securelevel could have its own set of prohibitons and that could
> only be changed settin
Greg Black wrote:
>
> Sergey Babkin wrote:
>
> > Neil Blakey-Milner wrote:
> > >
> > > On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> > > > All,
> > > >
> > > > I've committed these changes for cron to support DST change
> > > > to -current (see PR bin/24494 for description of my tests).
> >
> On Sat, Jan 20, 2001 at 01:19:17PM -0800, Luigi Rizzo wrote:
> > > I think this is a BIOS issue. I don't think any BIOS will let you
> > > boot from arbitrarily-formatted floppies :)
> >
> > the 1480 format works.
>
> Have you got this working now - or was it the larger size that didn't
> wor
Doug Barton wrote:
>
> This needs to be backed out immediately. This isn't even close to what was
> discussed in -hackers. After LONG, often pointless discussion, the
> following points were agreed to there.
Could you please look at the changes first ? The changes I
committed are _not_ t
The problem here has nothing to do with whether changing the behavior
is good or bad, and everything to do with the fact that cron is an
absolutely critical core piece of software that runs on these machines
and there is no guarentee that you haven't introduced one or many bugs
Doug Barton wrote:
>
> Sergey Babkin wrote:
> >
> > Neil Blakey-Milner wrote:
> > >
> > > On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> > > > All,
> > > >
> > > > I've committed these changes for cron to support DST change
> > > > to -current (see PR bin/24494 for description of my tests).
>
Lawrence Sica wrote:
>
> Quoting Sergey Babkin <[EMAIL PROTECTED]>:
>
> > All,
> >
> > I've committed these changes for cron to support DST change
> > to -current (see PR bin/24494 for description of my tests).
> > Everyone is welcome to test them out.
> > Please let me know if you encounter any
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Matt Dillon wrote:
> The problem here has nothing to do with whether changing the behavior
> is good or bad, and everything to do with the fact that cron is an
> absolutely critical core piece of software that runs on these machines
> and there is no guarentee that you haven't int
Dan Langille wrote:
>
> On 21 Jan 2001, at 14:50, Sergey Babkin wrote:
>
> > Let me ask a simple question: Why ? What are the benefits of
> > preserving the old behavior ?
>
> First, it's not "old" behaviour. It is existing behaviour. There is a
> difference. Because that's what was discusse
Since I hate finding unanswered questions in the archive, I'm posting the
resolution. The previous answers that suggested subnetting the internal
network and setting up additional port diversions for the webserver in the
firewall rules didn't do it, certainly not in combination. However,
settin
[EMAIL PROTECTED] wrote:
>
> ...
> So like I said, the solution was "UseLogin yes" in sshd_config.
Patched it and signalled it. Waiting for the next user to come by.
Another question to ask could be, why wasn't a patch completed?
Roelof
--
Home is where the (@) http://eboa.com/ is.
Nisser ho
On Sun, 21 Jan 2001, Sergey Babkin wrote:
> Doug Barton wrote:
> >
> > This needs to be backed out immediately. This isn't even close to what was
> > discussed in -hackers. After LONG, often pointless discussion, the
> > following points were agreed to there.
>
> Could you please look at
On Sun, Jan 21, 2001 at 03:12:09PM -0800, Luigi Rizzo wrote:
> > On Sat, Jan 20, 2001 at 01:19:17PM -0800, Luigi Rizzo wrote:
> > > > I think this is a BIOS issue. I don't think any BIOS will let you
> > > > boot from arbitrarily-formatted floppies :)
> 1480 always worked for me on the system i t
Sergey Babkin wrote:
> It still can be backed out.
Well, what are you waiting for? Back it out. Listen to what
people are saying and then maybe propose something that takes
into account their concerns.
To make this point a little more clearly -- the fact that Matt
Dillon, who is no fool, and
> In message <3A6B3B82.15538.103246@localhost> "Marco van de Voort" writes:
> : Does FreeBSD have any possibility to this?
>
> See /dev/io.
Much better to use i386_get_ioperm/i386_set_ioperm.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately oppon
> So like I said, the solution was "UseLogin yes" in sshd_config.
This only works for shh shell logins. If you want to start
an application on the remote site without invoking your
shell, the use of /bin/login is not possible. E.g. you want
to start an xterm or a mail (x-)client on a re
I had issues with this when I was doing some bootsector ASM coding. Basically,
you have to set up the disk header (first 32 bytes of sector 1?) to tell the
bios how many sectors your disk has. Many BIOSes will still only do 18 sectors
anyway, though. I can't remember the exact layout of the disk h
:> with your rather large diff set. For better or for worse, people
:> already know about the daylight savings shift problem. Thousands
:> of people depend on cron to work, which means that when you
:> make a major change like this it must be tested by a wider audience
:> for
On Sun, Jan 21, 2001 at 07:33:43PM -0800, Doug Barton wrote:
> You need to back out your changes and let the people who are
> proposing a more complete solution which has been widely discussed and
> agreed to have time to finish their work and send it to -arch for more
> discussion. Your dri
Sergy wrote:
> > > As far as I've watched this thread
> > > nobody had explained it. So could you please elaborate ?
> >
> > Nobody explained it to your satisfaction but you still committed it?
>
> Nobody explained it to my satisfaction why I should not commit it.
Ummm, well, that's a good reas
In message <[EMAIL PROTECTED]> Neil Blakey-Milner writes:
: "make buildkernel" currently fails if a "make buildworld" has not
I've committed this change, as threatened late last week, since no one
said not to.
buildworld is still required acorss major releases, when binutils
change, and when con
46 matches
Mail list logo
