search for: craci

Displaying 9 results from an estimated 9 matches for "craci".

Did you mean: crack
2015 Sep 20
3
move firmware-specific code into a directory
On Sun, Sep 20, 2015 at 06:32:48AM +0200, Celelibi via Syslinux wrote: > 2015-09-20 0:04 UTC+02:00, Gene Cumm via Syslinux <syslinux at zytor.com>: > > On Sat, Sep 19, 2015 at 4:32 PM, BALATON Zoltan <balaton at eik.bme.hu> wrote: > >> On Fri, 18 Sep 2015, Gene Cumm via Syslinux wrote: > >>> > >>> No. pxechn.c32 is BIOS only for now. >
2014 Aug 26
0
Re: filesystem
* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > I hope this is the right list. I have created an ext2 filesystem and > removed the dir_index feature. I don't know if this kind of experimentation > is going to help me learn something about filesystems or not. Well what is > dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I >
2014 Aug 25
2
filesystem
I hope this is the right list. I have created an ext2 filesystem and removed the dir_index feature. I don't know if this kind of experimentation is going to help me learn something about filesystems or not. Well what is dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I remove? Htree. I guess it can always be put back and it's on an experimental filesystem.
2005 Nov 20
1
about demo
Hi, I might have a silly question: when I type demo() I saw: graphics A show of some of R's graphics capabilities I wonder how to see the demo of graphics? Thanks! --------------------------------- [[alternative HTML version deleted]]
2015 Sep 20
0
move firmware-specific code into a directory
>>> > This is related to bug #37. > http://bugzilla.syslinux.org/show_bug.cgi?id=37 > > Actually, I think this raises a more general issue about the source > code organization. Most of the code of syslinux has been developped in > a time where only BIOSes were supported. And now, there is no real > separation between generic code and BIOS-only code (while UEFI
2002 Nov 27
0
invalid key given to dptr_close
A productional system (linux) running samba 2.2.5 runs 'cracy' from yesterday. There are lot of 'odd' behaviours. People cant logon or cant logoff. Access to files fails. Examining the logs the most eyecatching events are: (not that the keynumber started at 959 and went slowly down. I did not wait until it goes to zero and let the user reboot its machine before) Any idea ? thnx,
2015 Sep 20
1
move firmware-specific code into a directory
> To port a .c32 module to EFI requires a few steps: > > 1) The .c32 module must have access to the gnu-efi environment; I have posted a > patch some time ago that does exactly that (I really can't find it, surely Ady will help). > > 2) based on makefile variables it is very easy to define within the .c32 source code > "BIOS only sections" and "EFI only
2014 Aug 26
2
Re: filesystem
----- Original Message ----- From: "Bodo Thiesen" <bothie@gmx.de> To: <ext3-users@redhat.com> Sent: Monday, August 25, 2014 8:15 PM Subject: Re: filesystem > Hello Bill. [snip] > You're trying to understand what exactly? From the user point of view, > dir_index just makes directory accesses on very big directories faster. > When creating a new file, or
2015 Sep 20
2
move firmware-specific code into a directory
2015-09-20 14:21 UTC+02:00, Patrick Masotta via Syslinux <syslinux at zytor.com>: >>>> > > This is related to bug #37. > > http://bugzilla.syslinux.org/show_bug.cgi?id=37 > > > > Actually, I think this raises a more general issue about the source > > code organization. Most of the code of syslinux has been developped in > > a time where