| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> How is geist's os going on?
<1> put to rest
<1> but continues as part of haiku
<2> wobster ; is it ok to store data inside an i-node?
<2> that's what i mean
<3> An inode isn't a descriptor.
<3> And no, it's not ok.
<2> Evil-Bill ; inode is not a descriptor? so what is it?
<4> asdfg, if you do not break the filesystem or you're building your own, why not? But when you add something to it you have make sure the consistency is held up and other things. It's your design
<2> wobster ; but it aim't against the concept of a file descriptor? I mean, jesus, the name says it is a file descriptor, so you should not put data there
<4> asdfg, ext4 will or ntfs does actually store very small files directly in the head. That's an optimization. So, nothing wrong with that basicly. But you will break somehting if you just try to write some crap into an existing filesystems structure that you shouldn'r change. That should be clear
<4> asdfg, say we are talking of ext2. then listen to Evil-Bill.
<2> wobster ; an i-node isn't a file descriptor?
<4> asdfg, no. it's a strcutures that's way below things like "file descriptors".
<3> The term 'file descriptor' usually refers to something else.
<3> int i;
<3> i = open("myfile", O_RDWR);
<3> i is a descriptor
<3> An inode is filesystem metadata.
<1> inode != open("myfile");
<2> hm... but the i-node contains the file descriptor?
<2> if not, where does "open" find it?
<4> asdfg, a file descriptor refers to something in userspace usually. An inode is a part of a filesystem, the physical layout of the partition,. It's something totally, totally different.
<4> asdfg, no. fopen -> syscall -> vfs -> lvm -> raid -> filesystem. a file descriptor is for fopen. an inode would be on the other hand.
<4> s/hand/end/
<4> asdfg, that are COMPLETELY unrelated. Excuse me, but I have my doubts you know how to use fopen() at all ...
<3> The kernel actually locates files by traversing directories. The directory metatada tells you the names of the files that live in the directory, and their ***ociated inode numbers.
<4> Yes, that's what a VFS layer would do. How it looks like underneith .. could be anything.
<1> like FAT (yikes, i'm writing a fat driver)
<1> i'm pretty sure bill gates was drunk that day
<3> The inode itself contains the list of disk blocks that comprise the file, the file access times, and the permissions. Now, you could call that a 'descriptor' in that it describes the layout of the file on disk, but when people talk about file descriptors, that's not what they mean.
<3> It's possible that the filesystem might depend on the inode not containing extaneous data.
<4> I don't he listens to us ... *grumble*
<4> think
<4> jesus, I'm too tired for this small keyboard :)
<1> bill gates should never have been allowed to make file systems
<1> craaazy
<3> Nobody listens to me anyway, because I'm evil.
<1> and you always rant about your eth drivers
<1> it mainly goes in one ear and out the other
<3> Meeting time.
<4> wtf .. he left?!
<4> damn. it's a thankless world ..
<4> I'll go and find him!!
<0> Does beos have GUI patents or something like that?
<5> beos' patents are gooey. And sticky =(
<0> If I would make nice tool, like existed in beos, for linux, would I be in big ****
<0> I mean modern linux desktop enverioment lack the easy way to mount partition, HD, unlike beos.
<6> baaaaaaawhahahaha
<6> http://youtube.com/watch?v=ihAoSwQqo44
<7> gr00ber: You are back! \o/
<5> semipermenant is really short o_O
<5> wb groober!
<6> \o/
<6> (o)
<6> / \
<6> yay
<7> iank: 1 day
<6> and 2 hours
<7> gr00ber: So you forked? :-)
<6> and joined
<6> my mommy was a pthread
<6> hm, a bit older
<7> But if you forked, you must be older.
<6> no, 15 year old dudes can be dads
<7> gr00ber: Well, it is likely.
<6> I f0rked at 21 actually
<6> it's not that uncommon these days
<7> hm
<7> At least, that is what I am ***uming ;-)
<6> the upside of that is that when I'm 40 one day, my kidz have left the nest and I'm debt free
<6> that's long term planing
<7> LOL
<7> It was an accidental fork? ;-)
<6> no :)
<7> Or you reconsidered afterwards? ;-)
<6> no, but grown-up kids are no fun
<6> you gotta kick them out before they turn 17 or so
<6> they also tend to become prohibitively expensive
<7> True
<7> :-)
<6> at least, I was :-)
<7> grI wasn't a hard kid, I think. :-)
<6> crashed two cards, amongst other stuff
<7> LOL!
<6> my father didn't lol
<7> Well...
<6> +-)
<7> If my parents only knew what kind of stuff I used to do... :-))
<6> right
<7> I remember them complaining about stuff my little brother did.
<8> heh, lucky bastards
<7> I thought: If you only knew what I did yesterday... :-))
<7> shackan_: Hm? :)
<8> just thinking loud :P
<7> shackan_: What's so lucky about this?
<6> it's scary to think about all the **** one did at that age. Totally crazy. And I'm sure my kidz will do the same. Cheezus ****ing christ.
<7> :-)
<7> gr00ber: True.
<7> gr00ber: And most likely you won't find out about most stuff, I hope that comforts you. ;-)
<6> somewhat
<6> maybe i'll just mold my kids into antisocial hackers that sits in front of the computer all day
<6> much like the dad on his not-so-young days
<8> heh, that's me
<6> ya
<7> :-)
<8> don't do that do your kids :P
<6> and was totally and utterly not interested in computers during weekends when I was 15-20 - all that mattered where friends and partying.
<7> gr00ber: You didn't hack when you were young?
<7> gr00ber: What a wasted youth you had. ;-)
<6> yes, but not at the expense of a social life
<8> gah, I hate you :P
<9> you never attend at an hackathon
<9> ;p
<6> hm?
<7> shackan_: Why?
<7> shackan_: You are confusing.
<6> hackaton's for fat kidz with jolt coke dispensers on their heads
<7> \o/
<6> hm, sleep time
<6> see ya'll moddafokkas
<8> <rant> heh, I would have rather not kept this in the logs, but anyway, you enjoyed life I never could, that's why </rant>
<7> shackan_: I am sorry to hear that, why couldn't you?
<8> period.
<7> hm.
<7> shackan_: Do you know you are really confusing? If you do not want to share something, better don't bring it up. ;-)
<10> hi
<10> can any body tell me, what's the meaning of this words: bit the bullet
<8> it's "bite the bullet" and you can find it out yourself
<5> "bite the bullet", usually meaning to "just do it", even though it might be painful and/or difficult.
<10> jank: why call it bit the bullet. I take it as I eat the bullet a bit
<5> not bit, bite.
<10> yes, I used to take it as I bite the bullet.....
<10> I just wander, how can I make it? now I see, it means Just Do it.
<10> thank you, iank
<11> "bit the bullet" would be past tense
<11> hey mathis, still working on your os?
<5> no, he's busy ignoring everyone =)
<5> There's a whole lot of people on IRC, and he's not just about to cheat and use *!*@*
<12> yeah, takes a lot of effort to ignore everyone individually
<11> hehe
<13> Hey guys, I'm looking at trying to read a sector of a USB drive. I've looked at this forum post about it [http://www.osdev.org/phpBB2/viewtopic.php?p=2213&sid=14d786c7b3f1121368ac47099839ca0f] as well as the Pheonix Enhanced Disk Drive Specs, but I think I'm still missing something... How do I know what Drive Number to provide? Anyone experienced with this?
<12> yawn
<12> good evening everyone
<14> morning geist :)
Return to
#osdev
or
Go to some related
logs:
unknown symbol unlock_kernel how to fix
#bash
#perl
xgodsoul
#math
DAWG HTML template irc
Package rar has no installation candidate
#oe
NOQUEUE: SYSERR(dspam)
ubuntu NSS User Private Key and Certificate Services
|
|