User talk:Claunia

From Wikipedia, the free encyclopedia

Contents

[edit] Template:File system (F) and Template:Infobox Filesystem (I)

I agree that (I) is more consistent with Wikipedia standards and looks a little better than (F), which I whacked together in a hurry to replace the "Common File System Features" table.

The only articles I've added (I) to are HFS Plus and NTFS. I'll tag my template for deletion as soon as they're converted.

But just a couple of minor nit-picky things:

  1. Please use lowercase titles for article and template names wherever possible.
  2. There may need to be two columns for some items in the template, because features and limits of the on-disk file system format and the actual OS implementation often differ.
  3. "File allocation" needs to be split into "free space mapping", "allocation mapping" and "metadata" because they're often kept track of with different data structures.
  4. I lumped per-file and per-volume compression into a single item in (F) because file systems only implement one or the other. Also, per-volume encryption is implemented at the block device level, not the file system level on many Unices, so I lumped that too.

—Ghakko 01:29, 22 August 2005 (UTC)

  1. If you can rename (I), I dunno how to and was AlistairMcMillan who created the first.
  2. Well the intention is to put what filesystem defines in the limits, not what every and every implementation wants. For example in FAT16, Windows NT uses the filesystem specification limit (64Kb cluster maximum), while DOS and Windows 9x are limited to 32Kb cluster, and Windows 2000 and XP limits FAT32 to be 32Gb while Windows 9x limits to 32Kb cluster as in FAT16, and as far as I think Linux's FAT implementation is able to violate the specification (128Kb cluster for ex.)
  3. I agree but for simplicity, let it be as it is as most filesystems use the same structure for all. When it differs, it can be specified.
  4. So, it can be "real-time compression" and "real-time encryption" and put in it "per-file" or "per-volume".
Please answer as soon as possible so we can start replacing all tables with the infobox and request the "common filesystem features" article for remove (and put the infobox explanation in infoboxes list)
Claunia 05:16, 22 August 2005 (UTC)
Just to keep things moving, I've converted NTFS and HFS Plus to (I) and renamed (I). (F) has also been tagged for deletion.  ;-) I'll probably go on to fix up the Linux filesystems next.
Thanks for your energetic clean-up work.
—Ghakko 20:15, 23 August 2005 (UTC)
Ok so we currently have NTFS, HFS Plus, Hierarchical File System, HPFS, BeFS and File Allocation Table.
Will check ASAP linux kernel source code for checking file system structures as well as all documentation I have at hand for adding limits. Please inform me here wherever you add the infobox.
Regards —Claunia 00:08, 24 August 2005 (UTC)

[edit] Binary times

Ok, so, for the ones that are implementing the infoboxes, I put the following:

Maximum date for unsigned 32-bit value of seconds from 1970/01/01 00:00:00 2106/02/07 06:28:16

Maximum date for signed 32-bit value of seconds from 1970/01/01 00:00:00 2038/01/19 03:14:08

I think, that all *NIX fs uses one or the other.

[edit] GPT partitions IDs (for adding to infoboxes)

Put everything in GUID_Partition_Table, but, what ones are the GUIDs for AIX/Itanium, OpenVMS/Itanium?

[edit] ARC console on BeBox

Claunia,

On my talk page you pointed out that the BeBox in fact cannot run the ARC firmware, which I had apparently mistakenly asserted in the BeBox article. Certainly you appear correct—it seems ARC was in fact never released for the BeBox line. I apologize if my error caused any trouble; I will try to be more careful in the future.

—Ryanaxp 21:37, September 5, 2005 (UTC)

Trouble, none.
This is an open encyclopedia, everyone everywhere can have errors. Just there are enough people to check that things are correct ^^
Thanks for fast answer, please request for delete the image of "arc on bebox" or at least change it to "arc on prep" as it is a screenshot of a PReP (maybe an IBM or Motorola one, who knows).
—Claunia 21:55, 5 September 2005 (UTC)

[edit] What the h* is sad xD?

What is a "sad xD"?--Hhielscher 11:59, 25 September 2005 (UTC)

I didn't realize how to comment the change so put that. Just "SquashFS official homepage" is prettier and more stylish than "homepage", that was the reason for the change. —Claunia 12:10, 25 September 2005 (UTC)
Thanks. But what is the meaning of xD in this context?--Hhielscher 12:55, 25 September 2005 (UTC)
Laughs. xD means you are laughing with the eyes closed and the mouth open. —Claunia 15:38, 25 September 2005 (UTC)

[edit] Microkernel

Well, maybe not... although, I thought QNX was meant to have one? Doesn't help that the microkernel page here even lists BeOS.

The whole 'BeOS is a microkernel' thing seems to have come about from a misinterpretation of what micro meant - yes, the kernel is 800KB uncompressed, but its not a true microkernel at all - there are non-essential functions in the kernel (but even the IDE and base filesystem drivers are modules).

However, theres no article for Kinda a microkernel, but its not, really... no, really, so microkernel will do fine. --Kiand 00:20, 9 October 2005 (UTC)

[edit] How to spell UNIX?

http://web.greens.org/about/unix.html

Just, you read "The Bell Labs documentation was very careful to always spell UNIX in all capital letters, and small caps whereever possible.", so UNIX is UNIX, Unix and unix are just incorrect forms just too used.

Please revert all of your edits.

—Claunia 18:31, 5 November 2005 (UTC)

The Unix expertise of an organization on Green parties that apparently pays so much attention to detail that their HTML could've been assembled by a five-year-old, and the fact that they refer to "MULTICS" (which was of course "Multics" [they even link 'MULTICS' to a site that uses only 'Multics']), et al. aside, please read Talk:Unix#UNICS vs UNIX.
I will not be reverting my edits and anyone categorically reverting them will naturally get an RfC, as that would obviously be a colossal waste of many peoples' time (on top of being wrong). ¦ Reisio 19:56, 5 November 2005 (UTC)
So you know how to spell UNIX better than the creators and the copyright holders? —Claunia 21:37, 5 November 2005 (UTC)
If you've read Talk:Unix#UNICS vs UNIX, you know that Dennis Ritchie, a co-creator of Unix, has acknowledged that it was originally "Unix". Others associated also use "Unix" and while I haven't personally seen a good quote of Thompson saying "It's 'Unix'", logic suggests his view is in accordance with theirs. Clearly, though, when you referred to "the creators", you meant Bell Labs and AT&T, who did mostly use "UNIX" (at least after 1974). Nowadays, due to idiotic legalities, "UNIX" is only what The Open Group says it is and nothing more, but "Unix" was, is and always shall be the OS in general. All that aside, I almost certainly know more about how to spell it than the copyright holders - they care about their bottom lines, and I am a pedant. ¦ Reisio 22:42, 5 November 2005 (UTC)

[edit] WikiProject Macintosh

Thanks for joining! Our current focus is Apple Computer. Our former focus and current FAC is Apple Macintosh; you can vote here. It looks like you have already found Template:user WikiProject Macintosh. We’re all honored that you want to join our WikiProject. --HereToHelp (talk) 13:32, 18 December 2005 (UTC)

[edit] New Template

Thought you might like these new templates:

{{User apple}} produces
Mac This user is contributing using a Macintosh computer.

and

{{User:Scepia/Apple-g}} produces
This user thinks Apple Inc. products are cool.

Enjoy! --t-bte288-c 18:22, 18 December 2005 (UTC)

[edit] Separating blue and red links

I am looking for help for a project that I am doing and I noticed that you list yourself as a computer programmer with javascript and html skills. I have left a message with the Computer help desk but have yet to receive any replies or comments. Any help you can offer would be wonderful.

I am looking for an easier way to parse and separate red and blue links at the missing encyclopedic articles project so that valid blue links can be removed and article that need to be created can be grouped together. See this edit (before and after) for the kind of work that is being done currently by hand. If you can provide assistance by writing a script or referring me to another person who might be more helpful, I would greatly appreciate it. Ideally it would sort the html and return wikisyntax that could be entered back in, though I would be grateful with anything. Thanks in advance. --Reflex Reaction (talk)• 15:02, 13 January 2006 (UTC)

[edit] FAT filesystem

You can mention FASTFAT if you wish. It is as relevant to the FAT topic as would be the discussion of the Linux or BSD msdos filesystem drivers. The VFAT driver is really only discussed to justify why people say VFAT and not LFNs. And yeah, I do operating system development too. Adam Mirowski 15:41, 28 January 2006 (UTC)

[edit] EFI on IA-32

You provided this link as a reference that EFI will be supported on IA-32. I can't find any such wording, only that EFI is required on x64. Can you point out what I'm missing? --Steven Fisher 21:32, 10 March 2006 (UTC)

The PowerPoint presentation, talks a lot about that, and includes a sheet of EFI and ACPI usability in Windows XP, 2003 and Vista/Longhorn on x86, x64 and Itanium. —Claunia 22:35, 10 March 2006 (UTC)

[edit] Saying Hello

I saw you edited one of my pages, so came over to see who you were. Canary Islands, nice! I spent a week on La Palma once. It snowed. All week. I was sad. :-( — Nicholas (reply) @ 22:39, 20 May 2006 (UTC)

[edit] Current mac project collaboration

The current WP:MAC collaboration is Apple II family. Please devote some time to improve this article to featured status. — Wackymacs 13:51, 12 August 2006 (UTC)

[edit] Hello :)

Good day genius lady , have any webpages about the "Canary Islands Computer Museum Engine" thing ? :) Ammar 09:36, 21 November 2006 (UTC)

[edit] Time_(computing) for DOS

Hi / Buenas:
You mentionned at 18:59 on October 28th, 2007, that the resolution of DOS was only 2 seconds, with the comment “DOS internal structures handles seconds in a 5 bits structure, so resolution is 2 sec.”
If I read correctly the article about temporal resolution, it refers to the precision of the measurement. And if I further read the Accuracy_and_precision article, it should refer to the apparent data delivered (while accuracy is about how they are correct, or acertadas if you prefer.)
Now unless I am mistaken, DOS (both the TIME command and the GETTIME interrupt call) delivers system time with 2 digits beyond the second, that is 1/100th of a second resolution. While as far as I know, in the typical case of the IBM PC, its accuracy is at most of 55 ms, the same as the resolution of the underlying BIOS clock.
As such, I take the liberty to cancel your edit. Of course you are free to correct me if I am wrong, particularly if in fact resolution is to be meant as accuracy (but then the correct value would be probably 55 ms).

Perhaps we should have another part, about how to retrieve filesystem timestamps, which will then state that DOS resolution is 2 sec, and similarly for the various other OS and languages; however my knowledge is rather limited here; it looks like you know much more about filesystems, so perhaps you can improve it this way. AntoineL (talk) 18:01, 7 January 2008 (UTC)


[edit] Fair use rationale for Image:Bintercanarias2.png

Thanks for uploading Image:Bintercanarias2.png. You've indicated that the image meets Wikipedia's criteria for non-free content, but there is no explanation of why it meets those criteria. Please go to the image description page and edit it to include a fair use rationale. If you have any questions, please post them at Wikipedia:Media copyright questions.

Thank you for your cooperation. NOTE: once you correct this, please remove the tag from the image's page. STBotI (talk) 05:41, 22 May 2008 (UTC)