Re: [leaf-user] Update(grade) to Bering 5.x

2016-07-09 Thread Bob von Knobloch
On 09/04/16 14:40, Bob von Knobloch wrote: > On 09/04/16 11:51, kp kirchdoerfer wrote: >> >We have long filenames on the iso image (>8.3). In FAT16 the >> >root-dir-entries >> >may run out of space because of that (root-dir-entries are also used to >> >store >> >long filenames) . That's why

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-11 Thread kp kirchdoerfer
Am Sonntag, 10. April 2016, 22:57:58 schrieb n22e113: > On 4/9/2016 05:51, kp kirchdoerfer wrote: > > But why do I invest time as Linux user to explain other Linux users > > ancient > > Windows filesystem limitations? I could have used Windows if I'm > > interested in such problems. I use ext4 on

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-11 Thread Erich Titl
Am 11.04.2016 um 02:57 schrieb n22e113: > On 4/9/2016 05:51, kp kirchdoerfer wrote: >> But why do I invest time as Linux user to explain other Linux users ancient >> Windows filesystem limitations? I could have used Windows if I'm interested >> in >> such problems. I use ext4 on my routers

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-10 Thread n22e113
On 4/9/2016 05:51, kp kirchdoerfer wrote: > But why do I invest time as Linux user to explain other Linux users ancient > Windows filesystem limitations? I could have used Windows if I'm interested > in > such problems. I use ext4 on my routers instead. > Just to report that by using alix2d3,

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-10 Thread kp kirchdoerfer
Hi Bob; Am Samstag, 9. April 2016, 14:40:06 schrieb Bob von Knobloch: > On 09/04/16 11:51, kp kirchdoerfer wrote: > > We have long filenames on the iso image (>8.3). In FAT16 the > > root-dir-entries may run out of space because of that (root-dir-entries > > are also used to store long

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-09 Thread Erich Titl
Hi Bob Am 09.04.2016 12:40, schrieb Bob von Knobloch: > On 09/04/16 11:51, kp kirchdoerfer wrote: >> We have long filenames on the iso image (>8.3). In FAT16 the root-dir-entries >> may run out of space because of that (root-dir-entries are also used to >> store >> long filenames) . That's why

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-09 Thread Bob von Knobloch
On 09/04/16 11:51, kp kirchdoerfer wrote: > We have long filenames on the iso image (>8.3). In FAT16 the root-dir-entries > may run out of space because of that (root-dir-entries are also used to store > long filenames) . That's why copying into / stopped at 80MB Err... not in my case. The same,

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-09 Thread kp kirchdoerfer
Am Freitag, 8. April 2016, 13:41:03 schrieb David M Brooke: > Thanks kp. > > Now I understand what Andrew meant! -r refers to the number of directory > entries permitted (like inodes, I guess). From the man page: > > -r root-dir-entries > Select the number of entries available in the

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Robert K Coffman Jr. -Info From Data Corp.
Giovanni, > du lists 1k blocks, if I remember well (many years ago 512 and 1k with > - -k flag ) > This is the difference: > 91095040k= 91095040*1024 = 93281320960 > 93281320960/1024/1024/1024= 86.88 GiBytes There was a single approximately 91MB file in that directory. It displays TB for

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Erich Titl
Am 08.04.2016 09:47, schrieb Bob von Knobloch: > On 08/04/16 11:29, Erich Titl wrote: >> Did you copy the files on the LEAF box or did you use a CF adapter on >> another linux system. In any case syslog should report something. The >> symptoms you describe might point to a problem in file system

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread John Sager
There are 330 files in the vanilla 5.2.4 distro, taking up about 109Mbyte. I suppose it's possible that it's a root dir issue if mkfs.vfat treats a CF partition as a floppy. Otherwise I would have expected 512 to be enough. I'm away from home at the moment but I'll try play around with that when I

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Mark Berndt
I've seen this behaviour on USB sticks as well. The sticks had plenty of room but would run out of space early during file copy. Reformatting on windows with the hp usb stick utility made them work correctly if I recall correctly. cheers Marko On Fri, 8 Apr 2016 03:06:15 PM Bob von Knobloch

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Bob von Knobloch
On 08/04/16 14:41, David M Brooke wrote: > Now I understand what Andrew meant! -r refers to the number of directory > entries permitted (like inodes, I guess). From the man page: > > -r root-dir-entries > Select the number of entries available in the root directory. > The default

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread David M Brooke
Thanks kp. Now I understand what Andrew meant! -r refers to the number of directory entries permitted (like inodes, I guess). From the man page: -r root-dir-entries Select the number of entries available in the root directory. The default is 112 or 224 for floppies and 512 for hard

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Robert K Coffman Jr. -Info From Data Corp.
> Last time I looked into this, I wondered if some aspect of Linux thinks the > disk > is only 50% of the size it really is... I've noticed on my Leaf boxes this phenomenon with du -h and a mounted SMB share: router# du . -d 0 91095040. router# du . -d 0 -h 86.9G . Seems like it is

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread kp kirchdoerfer
Am Freitag, 8. April 2016, 14:17:42 schrieb Bob von Knobloch: > On 08/04/16 13:27, David M Brooke wrote: > > And I thought it was just me who had this problem with CF cards!:-) > > > > Out of interest, how big is the disk partition & what proportion of that > > does 80MB represent? > > > > Last

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Bob von Knobloch
On 08/04/16 13:27, David M Brooke wrote: > And I thought it was just me who had this problem with CF cards!:-) > > Out of interest, how big is the disk partition & what proportion of that does > 80MB represent? > > Last time I looked into this, I wondered if some aspect of Linux thinks the > disk

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread John Sager
I did it on another computer. My LEAF system runs on a ALIX 3D2 board and I prepare the CF card on the other system which runs Xubuntu 14.04. So far I have been OK writing files to the CF from LEAF - updating configdb.lrp and copying modified .lrp files for some experiments. It will be interesting

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Andrew
Try to increase root dir size. Or to use installer available in 5.2 branch. 08.04.2016 10:39, John Sager пишет: > I have had problems on Linux copying to CF cards - stopping after about > 80Mbyte. I solved it by creating a file of the same size as the partition, > creating a FAT filesystem on it,

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Bob von Knobloch
On 08/04/16 11:29, Erich Titl wrote: > Did you copy the files on the LEAF box or did you use a CF adapter on > another linux system. In any case syslog should report something. The > symptoms you describe might point to a problem in file system handling > and this should not affect CF only. > >

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Erich Titl
Hi John Am 08.04.2016 07:39, schrieb John Sager: > I have had problems on Linux copying to CF cards - stopping after about > 80Mbyte. I solved it by creating a file of the same size as the partition, > creating a FAT filesystem on it, mounting it via /dev/loop0 & copying all > the files. Then I

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread Bob von Knobloch
On 08/04/16 09:39, John Sager wrote: > I have had problems on Linux copying to CF cards - stopping after about > 80Mbyte. I solved it by creating a file of the same size as the partition, > creating a FAT filesystem on it, mounting it via /dev/loop0 & copying all > the files. Then I used dd to

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-08 Thread John Sager
I have had problems on Linux copying to CF cards - stopping after about 80Mbyte. I solved it by creating a file of the same size as the partition, creating a FAT filesystem on it, mounting it via /dev/loop0 & copying all the files. Then I used dd to copy the file to the CF card partition. That

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-07 Thread Bob von Knobloch
On 07/04/16 21:06, Andrew wrote: > You should use i486 image. Geode is for Geode LX (which is something > between i586 and i686). Thanks Andrew, I erroneously assumed that geode was a good word for me :=( at least it boots to a shell now :=) I think there is a DMA problem with the CF card, I'll

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-07 Thread Andrew
Hi. You should use i486 image. Geode is for Geode LX (which is something between i586 and i686). 07.04.2016 21:02, Bob von Knobloch пишет: > Hi again, > > Some troubles getting Bering 5.2.4. > Firstly, I was unable to copy the LEAF files to my CF. > Linux sees it as too small for some reason

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-07 Thread Bob von Knobloch
Hi again, Some troubles getting Bering 5.2.4. Firstly, I was unable to copy the LEAF files to my CF. Linux sees it as too small for some reason and stops copying after about 80 MByte (although it shows a 256MByte partition). Using a USB2 card reader and a windows XP VM under VirtualBox, I was

Re: [leaf-user] Update(grade) to Bering 5.x

2016-04-05 Thread Victor McAllister
On 4/5/2016 6:27 AM, Bob von Knobloch wrote: > Hi, > I'm upgrading tp Bering uClibc 5.x from V3. > In the 'old' days, many LEAF packages had dependencies (compression, > encrypt libs etc.). How is this handled today? I see no mention amoug > the package lists (but it seems that all the sourceforge

[leaf-user] Update(grade) to Bering 5.x

2016-04-05 Thread Bob von Knobloch
Hi, I'm upgrading tp Bering uClibc 5.x from V3. In the 'old' days, many LEAF packages had dependencies (compression, encrypt libs etc.). How is this handled today? I see no mention amoug the package lists (but it seems that all the sourceforge LEAF sites are down right now). I can't simply put