Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

364
Visualizações
why can't we store file names directly in inodes

I don't really understand why in UNIX systems they don't store file names directly in the inodes but use a mapping system .. is this only because the size of the inode is defined and can't be changed so in case of long file names we couldn't store them? Or maybe that's in case we change the file name we don't have to do it one more time in the inode ?

Please tell me if I'm wrong or if there are other explanations . Thanks in advance

over 4 years ago · Santiago Trujillo
1 Respostas
Responde à pergunta

0

Why do not include file name directly in inode, here is the reasons that come to my mind:

  1. a file may have multiple names, a.k.a. hard link
  2. to support long file name, say at least 255 bytes (on most POSIX system), the inode will be much large, and because usually file names are not so long, so many of these space are wasted.
  3. if in the future we want/need to support longer file name, we need to change the structure of inode, and this could cause backward compatibile problem.
over 4 years ago · Santiago Trujillo Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda