Hi, Theresa,
> Ok, I changed the mount for c drive to vfat, and it fixed the truncation issue, but
>now c drive is not automatically mounted in my file manager on boot.
You probably have the "noauto" option specified. Remove that from the line for you
Windows partition in your /etc/fstab file
> In the /etc/fstab, the entry the corresponds to the filesystem you
> want to have mounted at boot time should have a 1 in the fifth field.
> A 0 in this field indicates that it should not be mounted at boot
> time.
This is what man fstab has to say about field # 5:
The fifth field, (f
eply-To: [EMAIL PROTECTED]
->To: [EMAIL PROTECTED]
->Subject: RE: [techtalk] truncated file names
->
->> Excerpts from linuxchix: 14-Dec-99 Re: [techtalk] truncated fi.. by
->> "Theresa Radke"@corelcit
->> > Ok, I changed the mount for c drive to vfat
Ok folks, thanks to all of you I have it fixed, I had to recompile the kernel and be
sure that vfat support was included, somehow I'd left it out.
Along the way Someone suggested I run make xconfig instead of make config, this was
incredibly helpful because of the graphical display and its' pop
> Excerpts from linuxchix: 14-Dec-99 Re: [techtalk] truncated fi.. by
> "Theresa Radke"@corelcit
> > Ok, I changed the mount for c drive to vfat, and it fixed the
> > truncation issue, but now c drive is not automatically mounted
> > in my file manager on boot.
>
> What is in your /etc/fstab?
>
Excerpts from linuxchix: 14-Dec-99 Re: [techtalk] truncated fi.. by
Kelly Lynn Martin@povert
> Sometimes it's quite unobvious what might be "relevant". :)
Well, she said she changed something. Hopefully it's obvious that the
file she changed is relevant :)
[EMAIL PROTECTED] htt
On Tue, 14 Dec 1999 18:59:53 -0500 (EST), Laurel Fan <[EMAIL PROTECTED]> said:
>It's much easier for people to help you if you give them the relevant
>config files or errors...
Sometimes it's quite unobvious what might be "relevant". :)
Kelly
[EMAIL PROTECTED] http://www.linuxch
Excerpts from linuxchix: 14-Dec-99 Re: [techtalk] truncated fi.. by
"Theresa Radke"@corelcit
> Ok, I changed the mount for c drive to vfat, and it fixed the
> truncation issue, but now c drive is not automatically mounted
> in my file manager on boot.
What is in your /etc/fstab?
It's much easie
Ok, I changed the mount for c drive to vfat, and it fixed the truncation issue, but
now c drive is not automatically mounted in my file manager on boot.
_
SignUP For your CorelCity FREE email at http://www.corelcity.com
*
My windows and linux file names are truncated, but you're right about how I mount
windows, at first after I recompiled windows was not automatically mounted so I edited
fstab and at that time changed it to msdos from vfat. would that affect my linux
files as well?
Excerpts from linuxchix: 14-Dec-99 [techtalk] truncated file n.. by
"Theresa Radke"@corelcit
> I am sure I chose a wrong option someplace along the way because
> now my long file names are truncated.
What filesystem? (vfat, umsdos, ext2..) What are they truncated to?
> Any ideas what I can do t
> I am sure I chose a wrong option someplace along the way because now
> my long file names are truncated.
Is this doing 'ls' on a windows filesystem?
If so, I don't see how it's related to the new kernel. That's (in my
experience) controlled by how you mount it. If it's mounted as an msdos
Ok, here I am back again with yet another issue. I downloaded and compiled the latest
kernel because it has a driver for my sound pro wanna be sound card.
I am sure I chose a wrong option someplace along the way because now my long file
names are truncated.
Any ideas what I can do to fix this
13 matches
Mail list logo
