> something's wrong, but is it the code or the comment?
Code.
Pavel
i was trying something a little bit different on the file
server (ken's) and i noticed that mount -n does not work
unless the user is none. digging in i see that ken's file
server will allow none with no afid, but will not allow
anyone else. this seems sensible. if you don't want auth,
attach as
> I see, good to know. Thanks.
>
> In any case I think there is a bug in kb.c.
> The function 'ptrbootpvals' seems correct:
>
> if(c > 3 && ch->buf[3] == 1)/* up */
> b |= 0x08;
> if(c > 3 && ch->buf[3] == 0xff) /* down */
> b |= 0x10;
>
> i generally rebuild everything from the top directory.
I see, good to know. Thanks.
In any case I think there is a bug in kb.c.
The function 'ptrbootpvals' seems correct:
if(c > 3 && ch->buf[3] == 1)/* up */
b |= 0x08;
if(c > 3 && ch->buf[3] == 0xff)
> I retried complete copy (16KB copy) of the first block of fscache.
> as erik pointed me.
> recover main
> end
> is enough.
great! i've done that twice to recover something that wasn't
quite right. in both cases help from hardware, and operational
mistakes both were required to get
Thanks, erik and cinap,
I have believed that tag/path of first block in fscache is to be created by
config mode.
but not.
I retried complete copy (16KB copy) of the first block of fscache.
as erik pointed me.
recover main
end
is enough.
thanks again
Kenji Arisawa
On 2013/02/22,
> So I made such sequence to install my modification in kb.c:
> - cd /sys/src/cmd/usb (not into kb subdirectory!)
> - mk
> - mk install
> - /sys/src/9/pc
> - mk 'CONF=pcf'
> - cp 9pcf /n/9fat
> - reboot
>
> The modification in kb.c was used.
usb is a pain. i generally rebuild everything from the
> the response were:
> check tag PC=12336 w"/dev/sdC0/fscache"(0) tag/path= /15.36:
> expected
> and then returned back to the selection prompt.
>
> why tag/path in fscache is the problem in recovering?
> they must be cleaned based on fsworm.
on the real file server, the command is
sorry
/dev/SD0 is typo.
please replace by /dev/sdD0
Kenji Arisawa
Thanks Cinap,
that is merely an exercise for disk corruption.
I assumed /dev/sdC0 is corrupted.
the back up is on /dev/SD0 with partitions 9fat, nvram, fscache, fsworm,
other,...
9fat, nvram on D0 is same as those of C0.
cwfs config in the first block of /dev/sdC0/fscache is copied to that of D0.
Hi all,
> I still have opposite scrolling direction when scrolling my mouse wheel (even
> with my patched kb.c). :(
I have found a problem - as usually placed between keyboard and chair. ;)
I made such sequence to install my modification in kb.c:
- cd /sys/src/cmd/usb/kb
- mk
- mk install
- /sy
see the recover command from the fsconfig(8) manual. to enter
config mode, you have to pass the -c option to cwfs. on boot, you
can do it on the bootargs line like local!/dev/sdXX/fscache -c
(thats the only 9front specific part, afaik theres no local cwfs root
filesystem support by the standard dis
Hello,
I have been playing with cwfs64x on 9front since last summer as my home system.
My current chief concern is, how to restore data when the disk is corrupted.
I have a copy of /dev/sdC0/fsworm on /dev/sdD0/fsworm.
However, I don't understand how to ream fscache based on the existing fsworm.
13 matches
Mail list logo