On Thursday, September 11, 2014 12:38:02 PM Patrick Kelsey wrote:
> On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov wrote:
> > On 09.09.2014 21:53, Patrick Kelsey wrote:
> > > I don't think it is worth the trouble, as given the larger pattern of
> > > libc routines requiring multiple capsicum righ
On Fri, Sep 12, 2014 at 1:57 PM, Marcin Cieslak wrote:
>
>
> On Fri, 12 Sep 2014, John Baldwin wrote:
>
> at /usr/src/sys/dev/pci/vga_pci.c:318
>>> 318 return (bus_alloc_resource(dev, type, rid, start, end,
>>> count,
>>>
>> flags));
>>
>>> Current language: auto; currently min
On 9/12/14 3:23 PM, Craig Rodrigues wrote:
Hi,
I could live with this solution of additional port outside of the main
bash port, which creates the symlink and updates /etc/shells.
One other thing I am seeing is that many, many shell scripts are
written assuming "#!/bin/bash".
Forcing all ups
On Sep 12, 2014, at 3:55 PM, Bryan Drewery wrote:
> There already is one and ports requires using it!
Doh!
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 9/12/2014 5:45 PM, Lyndon Nerenberg wrote:
>
> On Sep 12, 2014, at 3:23 PM, Craig Rodrigues wrote:
>
>> Forcing all upstream script writers to switch to "#!/usr/bin/env bash", or
>> to convert their scripts to "#!/bin/sh" and remove all bash-specific
>> behaviors, is getting harder and harder
On Sep 12, 2014, at 3:23 PM, Craig Rodrigues wrote:
> Forcing all upstream script writers to switch to "#!/usr/bin/env bash", or
> to convert their scripts to "#!/bin/sh" and remove all bash-specific
> behaviors, is getting harder and harder,
> since many people are exposed to MacOS X and Linux
On Sat, Sep 13, 2014 at 02:33:58AM +0400, Subbsd wrote:
> On Sat, Sep 13, 2014 at 2:23 AM, Craig Rodrigues wrote:
> > Hi,
> >
> > I could live with this solution of additional port outside of the main
> > bash port, which creates the symlink and updates /etc/shells.
This is the approach I took at
On Sat, Sep 13, 2014 at 2:23 AM, Craig Rodrigues wrote:
> Hi,
>
> I could live with this solution of additional port outside of the main
> bash port, which creates the symlink and updates /etc/shells.
>
> One other thing I am seeing is that many, many shell scripts are written
> assuming "#!/bin/b
Hi,
I could live with this solution of additional port outside of the main
bash port, which creates the symlink and updates /etc/shells.
One other thing I am seeing is that many, many shell scripts are written
assuming "#!/bin/bash".
Forcing all upstream script writers to switch to "#!/usr/bin/en
On Sep 12, 2014, at 2:40 PM, Baptiste Daroussin wrote:
> If you want interoperability just use /usr/bin/env bash as a shebang. Btw you
> cannot get interoprability with OS-X in there because the bash they do provide
> is the last GPL-2 recent bash have many incompatiblities with this old
> vers
On Fri, 12 Sep 2014, Rang, Anton wrote:
If you want interoperability just use /usr/bin/env bash as a shebang.
That doesn't work for this use case -- the user shell coming from LDAP
-- but I agree that the port shouldn't be modifying /usr/bin.
It's easy enough to add the symlink manually aft
On Sep 12, 2014, at 14:53, Benjamin Kaduk wrote:
> On Fri, 12 Sep 2014, Rang, Anton wrote:
>
>>> If you want interoperability just use /usr/bin/env bash as a shebang.
>>
>> That doesn't work for this use case -- the user shell coming from LDAP
>> -- but I agree that the port shouldn't be modify
On Fri, 12 Sep 2014, John Baldwin wrote:
Please note I originally loaded "i915.ko", not "i915kms.ko"
Oh, that is probably your problem. X loaded i915kms automatically and
i915 and i915kms do not get along. i915 had already allocated the IRQ
when i915kms tried to alloc the same IRQ causing
The correct thing is to make a port/pkg that installs the symlink and
/etc/shells this for the user.
There is no need for changes to 'base' nor do we need a change to the
system port.
-Alfred
On 9/12/14 2:40 PM, Baptiste Daroussin wrote:
On Fri, Sep 12, 2014 at 02:12:45PM -0700, Craig Rodri
On Friday, September 12, 2014 08:57:55 PM Marcin Cieslak wrote:
> On Fri, 12 Sep 2014, John Baldwin wrote:
> >> at /usr/src/sys/dev/pci/vga_pci.c:318
> >>
> >> 318return (bus_alloc_resource(dev, type, rid, start, end,
> >> count,
> >
> > flags));
> >
> >> Current language:
On Fri, 12 Sep 2014, Rang, Anton wrote:
> > If you want interoperability just use /usr/bin/env bash as a shebang.
>
> That doesn't work for this use case -- the user shell coming from LDAP
> -- but I agree that the port shouldn't be modifying /usr/bin.
Here at MIT, where our Athena environment ha
> If you want interoperability just use /usr/bin/env bash as a shebang.
That doesn't work for this use case -- the user shell coming from LDAP -- but I
agree that the port shouldn't be modifying /usr/bin.
It's easy enough to add the symlink manually after installing the port if
you're in this s
On Fri, Sep 12, 2014 at 02:12:45PM -0700, Craig Rodrigues wrote:
> Hi,
>
> In the last 3 jobs that I have worked at, there have been
> a mix of Linux machines and FreeBSD machines.
> When using an NIS or LDAP environment where
> there is a single login across multiple machines, it is useful to
> h
"No" (as portmgr).
Ports should not be touching the base system like this. Let's NOT go
backwards and add a /bin/bash. In fact the /usr/bin/perl one will be
removed soon as well.
If we can actually eliminate ports touching /usr and / (not including
/usr/local and /var) then we gain a very large m
Hi,
In the last 3 jobs that I have worked at, there have been
a mix of Linux machines and FreeBSD machines.
When using an NIS or LDAP environment where
there is a single login across multiple machines, it is useful to
have a single shell setting.
Since Linux and MacOS X have "/bin/bash" as the sh
On Fri, 12 Sep 2014, John Baldwin wrote:
at /usr/src/sys/dev/pci/vga_pci.c:318
318 return (bus_alloc_resource(dev, type, rid, start, end, count,
flags));
Current language: auto; currently minimal
(kgdb) p *rid
$1 = 0
Hmm, type 1 is SYS_RES_IRQ. IRQ resources should not b
On Friday, September 12, 2014 05:45:31 PM Marcin Cieslak wrote:
> On Wed, 10 Sep 2014, John Baldwin wrote:
> > On Wednesday, September 10, 2014 12:45:08 PM Marcin Cieslak wrote:
> >> On my CURRENT as of 6 Sep (r271197):
> >>
> >> What I did was that:
> >>
> >> - kldload i915
> >>
> >> - startx
>
On Wed, 10 Sep 2014, John Baldwin wrote:
On Wednesday, September 10, 2014 12:45:08 PM Marcin Cieslak wrote:
On my CURRENT as of 6 Sep (r271197):
What I did was that:
- kldload i915
- startx
During X server start I get the following:
#10 0x808c2947 in resource_list_alloc (rl=,
bus
> Message: 1
> Date: Thu, 11 Sep 2014 15:23:07 +0200
> From: Nick Hibma
> To: freebsd-current@FreeBSD.ORG
> Cc: Hans Petter Selasky
> Subject: CDC-WDM driver (4G modems)
> Message-ID: <2d4cf978-b2c2-4253-93c7-595dabac0...@van-laarhoven.org>
> Content-Type: text/plain; charset=us-ascii
>
> F
24 matches
Mail list logo
