Le Fri, 31 Mar 2023 19:40:45 -0700,
Jared Harper a écrit :
> I have put together a patch that adds -executable, -readable, and
> -writable to /usr/bin/find.
>
> When I first started working on this patch, I implemented the access
> check by checking the stat of the file like so:
>
this doesn't
I have put together a patch that adds -executable, -readable, and
-writable to /usr/bin/find.
When I first started working on this patch, I implemented the access
check by checking the stat of the file like so:
int
is_permission(const FTSENT *entry, mode_t umode, mode_t gmode,
these come from the linux user guide and should all work the same as the
e25 if the document can be believed.
ok?
Index: usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.752
diff -u -p -r1.752 usbdevs
--- us
On Fri, Mar 31, 2023 at 10:13:44PM +0200, Mark Kettenis wrote:
> > Date: Fri, 31 Mar 2023 20:07:51 +
> > From: Klemens Nanni
> >
> > On Fri, Mar 31, 2023 at 08:12:20PM +0200, Mark Kettenis wrote:
> > > The name BM1000 only seems to come up in unofficial device trees.
> > > There is a prelimin
> Date: Fri, 31 Mar 2023 22:13:44 +0200
> From: Mark Kettenis
>
> > Date: Fri, 31 Mar 2023 20:07:51 +
> > From: Klemens Nanni
> >
> > On Fri, Mar 31, 2023 at 08:12:20PM +0200, Mark Kettenis wrote:
> > > The name BM1000 only seems to come up in unofficial device trees.
> > > There is a preli
> Date: Fri, 31 Mar 2023 20:07:51 +
> From: Klemens Nanni
>
> On Fri, Mar 31, 2023 at 08:12:20PM +0200, Mark Kettenis wrote:
> > The name BM1000 only seems to come up in unofficial device trees.
> > There is a preliminary data sheet for a BE-M1000 SoC out there? Is
> > that the proper name?
On Fri, Mar 31, 2023 at 08:12:20PM +0200, Mark Kettenis wrote:
> The name BM1000 only seems to come up in unofficial device trees.
> There is a preliminary data sheet for a BE-M1000 SoC out there? Is
> that the proper name?
Right, the CPU and SoC are called "Baikal-M1" and "BE-M1000", respectivel
> Date: Fri, 31 Mar 2023 17:12:42 +
> From: Klemens Nanni
>
> https://pcisig.com/membership/member-companies?combine=baikal
> https://linux-hardware.org/?id=pci:1d39-8060
>
> Feedback? OK?
The name BM1000 only seems to come up in unofficial device trees.
There is a preliminary data sheet fo
https://pcisig.com/membership/member-companies?combine=baikal
https://linux-hardware.org/?id=pci:1d39-8060
Feedback? OK?
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.2027
diff -u -p -r1.2027 pcide
On Fri, Mar 31, 2023 at 06:28:14PM +1000, David Gwynne wrote:
>
> i got a quectel ec25 to play with recently, and got side tracked
> thinking the usb controller was not talking to the modem correctly
> because when it attached it looked like this:
>
> umb0 at uhub2 port 1 "Android Android" rev 2.
i got a quectel ec25 to play with recently, and got side tracked
thinking the usb controller was not talking to the modem correctly
because when it attached it looked like this:
umb0 at uhub2 port 1 "Android Android" rev 2.00/3.18 addr
umb0: missing MBIM descriptor
and the usb descriptors looked
On Fri, Mar 31, 2023 at 09:53:32AM +0200, Theo Buehler wrote:
> group_get() can fail and return NULL. dh_getlen() accesses ie->group,
> so this will crash. Not sure if this is actually reachable, but it seems
> wrong. I've done what's done nearby. I don't want to look too closely...
phessler point
group_get() can fail and return NULL. dh_getlen() accesses ie->group,
so this will crash. Not sure if this is actually reachable, but it seems
wrong. I've done what's done nearby. I don't want to look too closely...
Index: ike_quick_mode.c
==
On Fri, Mar 31, 2023 at 08:20:34AM +0200, Claudio Jeker wrote:
> If the slowcgi timeout fires before the command was actually started then
> just abort the fastcgi request with error 408.
>
> This can happen on POST requests where the client stops sending data.
> Now bgplgd does not support POST b
14 matches
Mail list logo