Discussion:
Local USB storage
Radek Bursztynowski
2013-07-17 10:47:36 UTC
Permalink
Hello,

Using LTSP 5.2 I put usb storage to usb port and I can see disk storage at /media/username/usss

Using LTSP 5.4 there is nothing at /media
So I switched to console and I can mount usb storage manually.

How to change it to automaticly mounting of this device?

lts.conf encloses:
LOCALDEV = True
HOTPLUG = True
LOCAL_STORAGE = True

Best regards,
Radek
Barry Cisna
2013-07-17 17:17:46 UTC
Permalink
Radek,

In the users and groups gui add each user to the fuse group.
Log out and log in the usb sticks should now show up,,and be
writable,,as expected.


Barry
Radek Bursztynowski
2013-07-17 17:32:58 UTC
Permalink
Barry,

Many thanks. I suspected that, but after LTSP installation I didn't find
fuse group in /etc/passwd.

I will correct it tomorrow.

Thanks again,
Radek


--
Post by Barry Cisna
Radek,
In the users and groups gui add each user to the fuse group.
Log out and log in the usb sticks should now show up,,and be
writable,,as expected.
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Radek Bursztynowski
2013-07-18 05:51:38 UTC
Permalink
Barry,

Thanks again. Works fine, but epel-6-i386 thin client doesn't show icon device (older thin clients show).
It is no big problem, but windows users like...

Best regards,
Radek

--
Radek,

In the users and groups gui add each user to the fuse group.
Log out and log in the usb sticks should now show up,,and be
writable,,as expected.


Barry


_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>;
Barry Cisna
2013-07-18 11:52:24 UTC
Permalink
Radek,

On ltsp-server-5.4.5.x and ltsp-release 5.9.x when an usb stick is
inserted,(and user is in fuse group),,,you should get the expected
<usbname> appear automagically on the desktop once the usb stick is
inserted into the TC.
FYI.

Barry
Radek Bursztynowski
2013-07-18 09:06:51 UTC
Permalink
Hello,

Is somebody could tell me what is fedora-5-i386-epel thin client image?

Many thanks in advance,
Radek
Barry Cisna
2013-07-18 14:40:53 UTC
Permalink
Radek,

Fedora 5 image for ltsp would have to be very very very old.
Maybe you was speaking of EL-5 image?
Are you finding this on an older build of an ltsp server you are
running,,,or?


Barry
Radek Bursztynowski
2013-07-18 16:55:04 UTC
Permalink
Barry,

I know Fedora 5. But when I executed ltsp-build-client --list
I found as follow:

epel-5-i386
epel-5-ppc
epel-5-x86_64
epel-6-i386
epel-6-ppc64
epel-6-x86_64
fedora-17-arm
fedora-17-armhfp
fedora-17-i386
fedora-17-ppc64
fedora-17-ppc
fedora-17-s390
fedora-17-s390x
fedora-17-sparc64
fedora-17-sparc
fedora-17-x86_64
fedora-18-arm
fedora-18-armhfp
fedora-18-i386
fedora-18-ppc64
fedora-18-ppc
fedora-18-s390
fedora-18-s390x
fedora-18-x86_64
fedora-19-arm
fedora-19-armhfp
fedora-19-i386
fedora-19-ppc64
fedora-19-ppc
fedora-19-s390
fedora-19-s390x
fedora-19-x86_64
fedora-5-i386-epel
fedora-5-ppc-epel
fedora-5-x86_64-epel
fedora-devel-i386
fedora-devel-ppc64
fedora-devel-ppc
fedora-devel-x86_64
fedora-rawhide-arm
fedora-rawhide-armhfp
fedora-rawhide-i386
fedora-rawhide-ppc64
fedora-rawhide-ppc
fedora-rawhide-s390
fedora-rawhide-s390x
fedora-rawhide-sparc64
fedora-rawhide-sparc
fedora-rawhide-x86_64

And this is the source of my question.

Best regards,
Radek
Post by Barry Cisna
Radek,
Fedora 5 image for ltsp would have to be very very very old.
Maybe you was speaking of EL-5 image?
Are you finding this on an older build of an ltsp server you are
running,,,or?
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Jim Kinney
2013-07-18 17:28:38 UTC
Permalink
vague memory of this but those ancient F5's may be there to support REAL
i386 systems as clients. Somewhere after that point, Fedora dropped i386
and went to i486 as the lowest level cpu supported and someone was still
using IBM PC Jr. systems as thin clients.

Unfortunately, those ancient systems, barring a direct lightning strike,
will run forever.


On Thu, Jul 18, 2013 at 12:55 PM, Radek Bursztynowski <
Post by Radek Bursztynowski
Barry,
I know Fedora 5. But when I executed ltsp-build-client --list
epel-5-i386
epel-5-ppc
epel-5-x86_64
epel-6-i386
epel-6-ppc64
epel-6-x86_64
fedora-17-arm
fedora-17-armhfp
fedora-17-i386
fedora-17-ppc64
fedora-17-ppc
fedora-17-s390
fedora-17-s390x
fedora-17-sparc64
fedora-17-sparc
fedora-17-x86_64
fedora-18-arm
fedora-18-armhfp
fedora-18-i386
fedora-18-ppc64
fedora-18-ppc
fedora-18-s390
fedora-18-s390x
fedora-18-x86_64
fedora-19-arm
fedora-19-armhfp
fedora-19-i386
fedora-19-ppc64
fedora-19-ppc
fedora-19-s390
fedora-19-s390x
fedora-19-x86_64
fedora-5-i386-epel
fedora-5-ppc-epel
fedora-5-x86_64-epel
fedora-devel-i386
fedora-devel-ppc64
fedora-devel-ppc
fedora-devel-x86_64
fedora-rawhide-arm
fedora-rawhide-armhfp
fedora-rawhide-i386
fedora-rawhide-ppc64
fedora-rawhide-ppc
fedora-rawhide-s390
fedora-rawhide-s390x
fedora-rawhide-sparc64
fedora-rawhide-sparc
fedora-rawhide-x86_64
And this is the source of my question.
Best regards,
Radek
Post by Barry Cisna
Radek,
Fedora 5 image for ltsp would have to be very very very old.
Maybe you was speaking of EL-5 image?
Are you finding this on an older build of an ltsp server you are
running,,,or?
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
--
--
James P. Kinney III
*
*Every time you stop a school, you will have to build a jail. What you gain
at one end you lose at the other. It's like feeding a dog on his own tail.
It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
*
http://electjimkinney.org
http://heretothereideas.blogspot.com/
*
Burke Almquist
2013-07-18 23:35:33 UTC
Permalink
vague memory of this but those ancient F5's may be there to support REAL i386 systems as clients. Somewhere after that point, Fedora dropped i386 and went to i486 as the lowest level cpu supported and someone was still using IBM PC Jr. systems as thin clients.
Unfortunately, those ancient systems, barring a direct lightning strike, will run forever.
Given the requirements of running a modern version of LTSP, I don't know why you would even support trying to build for actual 386 anymore. A number of releases back, even Slackware dropped support for anything less than a 486. Linus killed off 386 support in newer kernels. You now need at least a 486 to run Linux on intel in the newer kernels.
Jim Kinney
2013-07-19 12:42:18 UTC
Permalink
That's why those ancient versions are still in K12LTSP. Some schools still
have real i386 PCs as thin clients.
Post by Jim Kinney
Post by Jim Kinney
vague memory of this but those ancient F5's may be there to support REAL
i386 systems as clients. Somewhere after that point, Fedora dropped i386
and went to i486 as the lowest level cpu supported and someone was still
using IBM PC Jr. systems as thin clients.
Post by Jim Kinney
Unfortunately, those ancient systems, barring a direct lightning strike,
will run forever.
Given the requirements of running a modern version of LTSP, I don't know
why you would even support trying to build for actual 386 anymore. A number
of releases back, even Slackware dropped support for anything less than a
486. Linus killed off 386 support in newer kernels. You now need at least
a 486 to run Linux on intel in the newer kernels.
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Loading...