> > Some modern disks use the "UASP"
> > protocol in preference to the traditional bulk-only mass storage protocol
> > supported by the Plan 9 usbdisk driver. Even if the disk also supports
> > bulk-only, the existing driver won't try to pick an alternate configuration
> > to force the disk to
On Fri, Jun 11, 2021 at 05:26:46PM +0100, Richard Miller wrote:
> > No luck!, although the end points appear now after manually executing
> > usb/disk.
> > ...
> > disk: logical block size 512, # blocks 7814037167
> > usb/disk: fsadd sdU9.0
>
> Once you've reached that point, it looks like the
> The usb subsystem is known to be pretty rudimentary, and indeed with respect
> to power management /sys/src/cmd/usb/usbd/usbd.c:/^portattach is headed by
> this comment:
> * BUG: does not consider max. power avail.
>
> Having said that, "It is impossible to use any usb disk" is possibly an
>
; if(grep a <{echo a}) echo true
a
true
; if(echo a | grep a >/tmp/1) echo true
true
But now:
; if(grep a <{echo a} >/tmp/1) echo true
;
Is this expected?
Regards,
adr.
--
9fans: 9fans
Permalink:
Thanks, it looks like a bug.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tad6cf6b7414c1847-Me2445f0e132fd2e7da654a5e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Hello,
I was importing rc-line-split.diff from 9legacy and I realized that
it is applied after rc-badrunes.diff.
How are the dependencies of the patches noticed?
Also I saw in https://plan9foundation.org
"The sources for the Plan 9 operating system can be found at
p9f.org/dl where new releases
Thanks for the patch!
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tad6cf6b7414c1847-Ma7401221faeb5647bc8bec13
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
On Wed, Jun 16, 2021 at 03:55:07PM +0200, David du Colombier wrote:
> > I was importing rc-line-split.diff from 9legacy and I realized that
> > it is applied after rc-badrunes.diff.
> >
> > How are the dependencies of the patches noticed?
>
> The patches apply in order. Some are independent,
>
Now all is making sense. The tricky part will be configuring it at
boot time to make it the root file system...
Thanks a lot to both of you for the help, specially to you Richard.
Regards,
adr.
--
9fans: 9fans
Permalink:
First of all, hello to everyone.
I've been using 9front attracted by the aarch64 support, not so
much by the 64 bit words but by the registers at hand.
I got problems with cwfs: the name length limit hardcoded at
compile time, impossibility of disk usage statistics for the "other"
partition (in
> The biggest problem to me is the usb code.
>
> First I'm using a kvm switch so there are a lot of attachments-detachments.
> At a certain point it will end with "No slots available" and the
> usb will became unusable. For me is a labyrinth, but I'm pretty sure
> someone with more experience
On Thu, Jun 17, 2021 at 04:05:15PM +0100, Steve Simon wrote:
> I must appologise, though I sent a reply at the time, an out of date x509
> certificate meant the email never reached my ISP.
Hi Steve, thanks anyway.
> What I tried to say was...
>
> > I wonder if the abaco problem you are seeing
> Some modern disks use the "UASP" protocol in preference to the
> traditional bulk-only mass storage protocol supported by the Plan
> 9 usbdisk driver. Even if the disk also supports bulk-only, the
> existing driver won't try to pick an alternate configuration to
> force the disk to fall back to
On Fri, Jun 25, 2021 at 05:17:39PM +0200, tlaro...@polynum.com wrote:
> On Fri, Jun 25, 2021 at 02:12:07PM +0000, adr via 9fans wrote:
> > On Fri, Jun 25, 2021 at 01:41:30PM +0100, Richard Miller wrote:
> > > > it just becomes difficult
> > > > to do anything when
On Fri, Jun 25, 2021 at 01:41:30PM +0100, Richard Miller wrote:
> > it just becomes difficult
> > to do anything when no fossil blocks can be allocated
>
> Thinking a bit further about this: intuitively one might expect to be
> able to reboot using a local file system which is completely full,
I don't think there is need of superuser concept here. What I'm
imagining, again, without having seen the source code, is something
like this:
The file system is formatted and data representing the structure of
the file system are stored normally.
At execution time, the file server check a flag
I noticed that you rearranged the patches so the rc ones are now
consecutive. Do you serve a 9p or there is another way to list the
patches by date? I'm going to use 9legacy as a base distribution
so this would be handy.
Regards,
adr.
--
9fans: 9fans
On Mon, 5 Jul 2021, cinap_len...@felloff.net wrote:
thats what we did in 9front (just so you dont need to do it all
over again in case you commit to that approach).
Maybe you are interested in this then. The default bsize and the
"-8" thing is only for kfs as Erik Quanstrom noticed here (I
Hi, let see if someone can put me in the right direction.
I'm having now this issue compiling ape/lib/sec (/sys/src/libsec
is modified):
pcc -FTVw -c -+ -D_POSIX_SOURCE -D_PLAN9_SOURCE -I../../../../libmp/port -I.
-I/sys/include/ape -I/sys/include ../../../../libsec/port/tlshand.c
Ok, the first error was that I used uintptr as in /sys/include/libc.h,
not uintptr_t as in /sys/include/ape/inttypes.h, that's the reason
of the ansi/old mix definition error.
I saw that setrealloctag.c is implemented in 9front's /sys/src/ape/lib/9/
the same way as setmalloctag.c, an empty
On Sun, Jun 27, 2021 at 12:04:09AM +0200, David du Colombier wrote:
> > venti-9p9, fossil-libventi, fossil-libventi-p9p, anyone with some
> > experience with this? It's worthy?
>
> I highly recommend the fossil-libventi patch. The purpose
> of this change is to get rid of the old liboventi and
venti-9p9, fossil-libventi, fossil-libventi-p9p, anyone with some
experience with this? It's worthy?
Thanks,
adr.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tac4d36dfa36d502c-M3dbeef3ea8045b3e74c40a0e
Delivery options:
On Mon, 12 Jul 2021, o...@eigenstate.org wrote:
Why not make getchunk allocate? Somethign like:
---
//.git/fs/object/e8259861da3a55c03491904e4d11c5c15b7577c5/tree/sys/src/cmd/jpg/readpng.c
+++ sys/src/cmd/jpg/readpng.c
@@ -94,7 +94,7 @@
}
static int
-getchunk(Biobuf *b, char *type, uchar *d,
On Mon, 12 Jul 2021, o...@eigenstate.org wrote:
Do you have an example?
I could upload it in some place but you don't need it, really. The
specification is clear, the length of a data chunk must be less
than 2^31 - 1, and the complete image data is represented by a
single zlib datastream that
On Mon, 12 Jul 2021, hiro wrote:
Date: Mon, 12 Jul 2021 20:04:23 +0200
From: hiro <23h...@gmail.com>
Reply-To: 9fans <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] pngread: alloc chunk's length
it's always useful to have the testcase available, for others and for
possible
On Mon, 12 Jul 2021, adr via 9fans wrote:
[...]
the length of a data chunk must be less than 2^31 - 1
[...]
can't be fixed (At least you want to allocate more than 2GB...)
[...]
Well... to be exact here, it can't be bigger than 2^31 - 1, so there
are "almost
Hi,
I was hacking libdisk/proto.c to accept quoted strings, when I
noticed that mkfs is not using libdisk.h. The problem modifying
mkfs.c is that the code taking care of kfs obliges me to keep
functions duplicated on proto.c. The easiest solution is to remove
kfs support and just extract
Checking the sent mail I noticed that I forgot to remove mag...
--- sys/src/cmd/jpg/readpng.c Thu Jan 24 23:39:55 2013
+++ /sys/src/cmd/jpg/readpng.c Sat Jul 10 13:09:13 2021
@@ -10,8 +10,6 @@
enum
{
- IDATSIZE = 100,
-
/* filtering algorithms */
FilterNone =
Hi,
Png is using a fix size to allocate space for the chunks. I noticed
it because it couldn't open some png files (the chunk size was
bigger than IDATSIZE).
This patch removes IDATSIZE and instead makes png to allocate the
size of the chunk before reading it.
--- sys/src/cmd/jpg/readpng.c
By the way, the lenght should be checked to not exceed 0x7FFF
so a corrupt chunk can be detected early.
--- /n/dump/2021/0627/sys/src/cmd/jpg/readpng.c Thu Jan 24 23:39:55 2013
+++ /sys/src/cmd/jpg/readpng.c Tue Jul 13 11:16:50 2021
@@ -10,8 +10,6 @@
enum
{
- IDATSIZE = 100,
-
On Tue, 13 Jul 2021, hiro wrote:
you seem to propose that if the png tells us to then we should
allocate 2GB per chunk, just bec. the spec allows it
even if the spec doesn't tell us a limit, we might want to have a limit.
No. The system should constrain the allocation. If you have enough
On Wed, 14 Jul 2021, o...@eigenstate.org wrote:
Yes, but your patch doesn't apply cleanly to 9front, and
it would be useful to check whether I fuck up porting it
manually.
Ok, but I told you already how to create one.
http://adr.freeshell.org/files/turner_ovid_banished_from_rome.png
On Tue, 13 Jul 2021, hiro wrote:
are you saying this is a purely synthetic error, it doesn't happen in
the wild bec. these sizes are normally more sane?
No, no... you got it wrong. You have to follow the specification
of the format, unless you want to have surprises like this one.
The file
Hi,
I changed the last patch so sam wont change the label at startup.
I added a new option '-l' to set the label, it's more flexible and
doesn't chage the normal behavior. If samriosnarf is in /env, sam will
use rio's snarf buffer instead of the internal one.
This patch should apply to 9legacy,
I don't want to add noise to the list, but it seem that some people
are confused about what I'm doing with this.
You start in rio to work in some project. You open sam in a big
window because all the files will be opened inside. You start
opening files and changing the focus using the menu, and
On Tue, 20 Jul 2021, adr via 9fans wrote:
buffer. I can't identify the file I'm editing using winwatch or
the menu when hidden, and so on.
Oh my... is "I can identify..." and I wanted to make things clear...
--
9fans: 9fans
Permali
On Tue, 20 Jul 2021, Skip Tavakkolian wrote:
what problem did this fix for you?
all the changes seem like bad ideas for general use; e.g. would hiding
a sam window show a name other than sam?
This is for using different instances of sam... Is not for your
"general use". I've explained this
You'll need to reinvent (or change, at least) plumbing if you want
multiple editors, be it one
per file or one per project.
I'll make sam create allways the named pipe with the pid in the
name so I can identify wich one I want to talk with.
There are a lot of possibilities.
On Mon, 19 Jul 2021, umbrati...@prosimetrum.com wrote:
This patch adds a command 'l' to set the label, and sets it at
startup as described above.
meh; you can already run !label blah from inside sam
That's run by sam, not samterm.
not sure the label-on-startup adds much?
It's for using
Ok, Let me explain this a little.
I don't like this "One X to rule them all" concept, recreating
complete interfaces. I would prefer to use one gui, and make the
programs integrate in it, rethinking some concepts if necessary.
Been able to modify the label is fundamental for this. It's a
way to
Hi,
I was hacking sam to set /dev/label to 'sam filename' when one is
given to be opened but then I thought that it would be better to
make samterm do it, so it'll work when using sam remotely.
This patch adds a command 'l' to set the label, and sets it at
startup as described above.
Regards,
In case someone was playing with this, last patch was really naive
(and buggy). I tried different approaches while learning more about
how the two parts of the editor interact with each other and after
some back-and-forths it's working now.
I enabled again the menu item when samriosnarf is
Last thing about your rpi image Richard, Is this the
one used in the go arm builders? Can I asume that
these are the only patches needed to have a working go?
Regards,
adr
Ok, thanks.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T3dbd3cda56f638ee-M16e29431130bbf818b28
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> I've put a script in contrib/miller/build-9pi.rc which shows the complete
process of building (almost) the 9pi image from the 4th edition ISO. You
can look at that to see what 9legacy patches are applied.
Hi Richard. I'm surprised by the small number of 9legacy patches you are using.
Any
I see, thanks.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T5da5467097e4eab2-M0fe5284a21a2266220ee5409
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Hi, plan6?
Your newlines are feeding the next getchar. You don't want to read chars, you
want to read strings.
Read the documentation, don't use stdio.h, explore the 9 way...
Regards,
adr
--
9fans: 9fans
Permalink:
Hi Antonio,
I replaced boot for an rc script time ago, but if I recalled correctly, this is
because
boot can't find fossil's configuration in any hard drive, so it tries to find a
kfs, but
the default kernel configuration doesn't include kfs in bootdir, so it gives
you that error.
Boot from
Oh, by the way, if you are using a usb hard disk, boot will screw with partfs
and
the usb disk's partitions will not be exposed. That's the main reason I
replaced it.
If that's the case, take a look in the mailing list archive, Richard Miller
gave some
workaround storing the config in the
49 matches
Mail list logo
