search for: cracy

...> I wonder if anyone has a knowledge of the source code general enough > to clarify this and move the firmware-specific code into a directory > arch/{bios,efi}. I personnally mostly know about the efi part. I like the proposal of arch/{bios,efi}. And because Free software is mostly do-o-cracy, please do. > Anyway this would be a large change conflicting with most pending > patches. So be it. I mean: Choose high level design improvement above outstanding patches. (and I think we, the Syslinux project, have a backlog of patches due fear of changing "too much" (yes, I sa...

...les), flex_bg (drop the constraint, that group meta data shall be stored in it's own group, thus allowing to virtually create bigger groups. Probably you can mke2fs one file system with flex_bg, then remove the feature flag and perfecly mount and use it with ext2 / ext3, however, e2fsck may get cracy on that setup - but I don't see, why the file system drivers should get a problem with that - anyways, I didn't test it), uninit_bg (speeds up mke2fs by skipping the "overwrite all bitmaps and inode tables with zeros" step). Regards, Bodo

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.

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]]

...ot; an EFI application (it does not have the EFI PE format) it remains a .c32 module, then it's not necessary to "chainload" to an EFI app what is not implemented in syslinux yet. >>> > I like the proposal of arch/{bios,efi}. > And because Free software is mostly do-o-cracy, please do. > Groeten > Geert Stappers <<< Finally: I think these .c32 module BIOS/EFI issues are not about code organization and I encourage all of us to think this very well before to either embrace radical changes on this point or to encourage probably wasting lot of creative e...

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...

...s not have the EFI PE format) it remains a .c32 module, > then it's not necessary to "chainload" to an EFI app what is not implemented in syslinux yet. > > > >>> > > I like the proposal of arch/{bios,efi}. > > And because Free software is mostly do-o-cracy, please do. > > > Groeten > > Geert Stappers > <<< > > Finally: > I think these .c32 module BIOS/EFI issues are not about code organization and I encourage > all of us to think this very well before to either embrace radical changes on this point or to >...

...drop the constraint, that group meta data shall be stored in it's own > group, thus allowing to virtually create bigger groups. Probably you can > mke2fs one file system with flex_bg, then remove the feature flag and > perfecly mount and use it with ext2 / ext3, however, e2fsck may get cracy > on that setup - but I don't see, why the file system drivers should get a > problem with that - anyways, I didn't test it), uninit_bg (speeds up > mke2fs by skipping the "overwrite all bitmaps and inode tables with > zeros" step). > > Regards, Bodo Yes all...

...tions is good. On that topic you may read "ifdef considered hamful" that specifically talks about portability. It's not life-changing, but worth reading IMO. > > >>>> >> I like the proposal of arch/{bios,efi}. >> And because Free software is mostly do-o-cracy, please do. > >> Groeten >> Geert Stappers > <<< > > Finally: > I think these .c32 module BIOS/EFI issues are not about code organization > and I encourage > all of us to think this very well before to either embrace radical changes > on this point or to...