Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

71%
+3 −0
Q&A Can I make a compressed RAM drive and externally prepare a (pre-)compressed file to copy onto it?

I don't know what these things are called exactly in the Linux world. But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive. There is also the c...

1 answer  ·  posted 2y ago by CanisSomnolentus‭  ·  edited 3mo ago by matthewsnyder‭

Question file RAMdisk ramfs
#4: Post edited by user avatar matthewsnyder‭ · 2024-01-23T02:40:28Z (3 months ago)
Can I make a compressed RAM drive and externally prepare a (pre-)compressed file to copy onto it?
I don't know what these things are called exactly in the Linux world.

But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive.
There is also the concept of an intrinsically compressed drive.

(Effective) compression takes time, of course. So I also wonder if there is such a thing to pre-compress a file externally to the system that has the compressed drive, and move it, e.g. coming from a network connection, onto the RAM drive without it taking time to compress.
(Though I guess that compressed drives favor speed over level of compression, to be feasible at all?)

For the curious (and maybe because someone might tell me that I should ask a different question as this scenario drawn here is not a good way to do what I want):

The aim of this is:
I have a machine with very limited storage (eMMC), and it is supposed to write a trimmed-down Linux image onto another machine it is connected to, and there is already a readily available program, geared towards doing that to the even smaller target machine.
That program takes a typical image file.

I cannot hold the image on the storage of the "pushing" machine.
But what if I made a RAM drive and kept a compressed Linux image in it, loaded from external connection for this event, and pointed the mentioned available flashing program to that file.
The Linux image would not fit, uncompressed, in the RAM - but compressed, it probably will, at least with usual zip settings, which are, I guess, better than a drive for "live" stuff.

I could write a modified flasher program and do decompression myself.
But if the same thing actually was only a few standard Linux commands away from working, why do it myself. (And also, learning new things that Linux can do, if it can do them, is always good.)

#3: Post edited by user avatar Quasímodo‭ · 2023-09-14T16:30:25Z (7 months ago)
Typo
  • I don't know what these things are called exactly in the Linux world.
  • But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive.
  • There is also the concept of an intrinsically compressed drive.
  • (Effective) compression takes time, of course. So I also wonder if there is such a thing to pre-compress a file externally to the system that has the compressed drive, and move it, e.g. coming from a network connection, onto the RAM drive without it taking time to compress.
  • (Though I guess that compressed drives favor speed over level of compression, to be feasible at all?)
  • For the curious (and maybe because someone might tell me that I should ask a different question as this scenario drawn here is not a good way to do what I want):
  • The aim of this is:
  • I have a machine with very limited storage (eMMC), and it is supposed to write a trimmed-down Linux image onto another machine it is connected to, and there is already a readily available program, geared towards doing that to the even smaller target machine.
  • That program takes a typical image file.
  • I cannot hold the image on the storage of the "pushing" machine.
  • But what if I made a RAM drive and kept a compressed Linux image in it, loaded from external connection for this event, and pointed the mentioned available flashing program to that file.
  • The Linux image would not fit, uncompressed, in the RAM - but compressed, it probably will, at least with usual zip settings, which are, I guess, better than a drive for "live" stuff.
  • I could write a modified flasher program and do decompression myself.
  • But if the same thing actually was only a few standard Linux commands away from working, why do it myself. (And also, leanring new things that Linux can do, if it can do them, is alsways good).
  • I don't know what these things are called exactly in the Linux world.
  • But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive.
  • There is also the concept of an intrinsically compressed drive.
  • (Effective) compression takes time, of course. So I also wonder if there is such a thing to pre-compress a file externally to the system that has the compressed drive, and move it, e.g. coming from a network connection, onto the RAM drive without it taking time to compress.
  • (Though I guess that compressed drives favor speed over level of compression, to be feasible at all?)
  • For the curious (and maybe because someone might tell me that I should ask a different question as this scenario drawn here is not a good way to do what I want):
  • The aim of this is:
  • I have a machine with very limited storage (eMMC), and it is supposed to write a trimmed-down Linux image onto another machine it is connected to, and there is already a readily available program, geared towards doing that to the even smaller target machine.
  • That program takes a typical image file.
  • I cannot hold the image on the storage of the "pushing" machine.
  • But what if I made a RAM drive and kept a compressed Linux image in it, loaded from external connection for this event, and pointed the mentioned available flashing program to that file.
  • The Linux image would not fit, uncompressed, in the RAM - but compressed, it probably will, at least with usual zip settings, which are, I guess, better than a drive for "live" stuff.
  • I could write a modified flasher program and do decompression myself.
  • But if the same thing actually was only a few standard Linux commands away from working, why do it myself. (And also, learning new things that Linux can do, if it can do them, is always good.)
#2: Post edited by user avatar tripleee‭ · 2023-09-14T16:29:49Z (7 months ago)
Typo
Can I make a compressed RAM drive and externally prepare a (pre-)compressed file to copy onto it?
  • I don't know what these things are called exactly in the Linux world.
  • But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive.
  • There is also the concept of an intrinsically compressed drive.
  • (Effective) compression takes time, of course. So I also wonder if there is such a thing to pre-compress a file externally to the system that has the compressed drive, and move it, e.g. coming from a network connection, onto the RAM drive without it taking time to compress.
  • (Though I guess that compressed drives favor speed over level of compression, to be feasible at all?)
  • For the curious (and maybe because someone might tell me that I should ask a different question as this scenario drawn here is not a good way to do what I want):
  • The aim of this is:
  • I have a machine with very limited storage (eMMC), and it is supposed to write a trimmed-down Linux image onto another machine it is connected to, and there is already a readily available program, geared towards doing that to the even smaller target machine.
  • That program takes a typical image file.
  • I cannot hold the image on the storage of the "pushing" machine.
  • But what if I made a RAM drive and kept a compressed Linux image in it, loaded from external connection for this event, and pointed the mentioned available flashing program to that file.
  • The Linux image would not fit, uncompressed, in the RAM - but compressed, it probably will, at least with usual zip settings, which are, I guess, better than a drive for "live" stuff.
  • I could write a modified flasher program and do decompression myself.
  • But if the same thing actually was only a few standard Linux commands away from working, why do it myself. (and also, leanring new things that Linux can do, if it can do them, is alsways good).
  • I don't know what these things are called exactly in the Linux world.
  • But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive.
  • There is also the concept of an intrinsically compressed drive.
  • (Effective) compression takes time, of course. So I also wonder if there is such a thing to pre-compress a file externally to the system that has the compressed drive, and move it, e.g. coming from a network connection, onto the RAM drive without it taking time to compress.
  • (Though I guess that compressed drives favor speed over level of compression, to be feasible at all?)
  • For the curious (and maybe because someone might tell me that I should ask a different question as this scenario drawn here is not a good way to do what I want):
  • The aim of this is:
  • I have a machine with very limited storage (eMMC), and it is supposed to write a trimmed-down Linux image onto another machine it is connected to, and there is already a readily available program, geared towards doing that to the even smaller target machine.
  • That program takes a typical image file.
  • I cannot hold the image on the storage of the "pushing" machine.
  • But what if I made a RAM drive and kept a compressed Linux image in it, loaded from external connection for this event, and pointed the mentioned available flashing program to that file.
  • The Linux image would not fit, uncompressed, in the RAM - but compressed, it probably will, at least with usual zip settings, which are, I guess, better than a drive for "live" stuff.
  • I could write a modified flasher program and do decompression myself.
  • But if the same thing actually was only a few standard Linux commands away from working, why do it myself. (And also, leanring new things that Linux can do, if it can do them, is alsways good).
#1: Initial revision by user avatar CanisSomnolentus‭ · 2021-09-02T18:48:05Z (over 2 years ago)
Can I make a compressed RAM drive and externally prepare a (pre-)compressed file to copy onto it?
I don't know what these things are called exactly in the Linux world.

But there is the concept of a drive in RAM, to write files onto and read them like it was any disk drive.
There is also the concept of an intrinsically compressed drive.

(Effective) compression takes time, of course. So I also wonder if there is such a thing to pre-compress a file externally to the system that has the compressed drive, and move it, e.g. coming from a network connection, onto the RAM drive without it taking time to compress.
(Though I guess that compressed drives favor speed over level of compression, to be feasible at all?)

For the curious (and maybe because someone might tell me that I should ask a different question as this scenario drawn here is not a good way to do what I want):

The aim of this is:
I have a machine with very limited storage (eMMC), and it is supposed to write a trimmed-down Linux image onto another machine it is connected to, and there is already a readily available program, geared towards doing that to the even smaller target machine.
That program takes a typical image file.

I cannot hold the image on the storage of the "pushing" machine.
But what if I made a RAM drive and kept a compressed Linux image in it, loaded from external connection for this event, and pointed the mentioned available flashing program to that file.
The Linux image would not fit, uncompressed, in the RAM - but compressed, it probably will, at least with usual zip settings, which are, I guess, better than a drive for "live" stuff.

I could write a modified flasher program and do decompression myself.
But if the same thing actually was only a few standard Linux commands away from working, why do it myself. (and also, leanring new things that Linux can do, if it can do them, is alsways good).