Comments

• 

  over 10 years ago by sax2 | Reply

  HI,

  during last hack week I implemented a tool which might be interesting for you too. The 'livestick' utility allows to easy deploy a live iso in a way that you gain read-write support, you will not loose any data which is on the stick before, and the tool uses a uniq uuid to identify the device on boot which is often a problem on sticks. If you don't mind I'd like to join you with this project ;)

  • 

    over 10 years ago by sax2 | Reply

    btw, livestick is part of the current kiwi packages

  ×
  Edit Comment 15
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  * Use asterisks
  * for lists
  
  This is an [example link](http://example.com/)
  
  This is an ![example image](http://paste.opensuse.org/view/raw/68957446)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
  btw, livestick is part of the current kiwi packages
   
  ×
  Reply to sax2
  btw, livestick is part of the current kiwi packages
  ---
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  * Use asterisks
  * for lists
  
  This is an [example link](http://example.com/)
  
  This is an ![example image](http://paste.opensuse.org/view/raw/68957446)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
   
×
Edit Comment 14
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
HI, during last hack week I implemented a tool which might be interesting for you too. The 'livestick' utility allows to easy deploy a live iso in a way that you gain read-write support, you will not loose any data which is on the stick before, and the tool uses a uniq uuid to identify the device on boot which is often a problem on sticks. If you don't mind I'd like to join you with this project ;)
 
×
Reply to sax2
HI,
during last hack week I implemented a tool which might be interesting for you too. The 'livestick' utility allows to easy deploy a live iso in a way that you gain read-write support, you will not loose any data which is on the stick before, and the tool uses a uniq uuid to identify the device on boot which is often a problem on sticks. If you don't mind I'd like to join you with this project ;)
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  over 9 years ago by jsmeix | Reply

  A short note what I accomplished and what I didn't:

  It was relatively easy to get a working Linux system on a USB stick. But it is time consuming until one understands Kwi sufficiently so that it makes what one wants.

  What did not work in the end was to get it running sufficiently fast from usual USB sticks. It runs sufficiently fast from a high-end USB stick with SLC (single level cell) flash memory. But on all usual (a.k.a. cheap) USB sticks it is too slow for normal usage. As fas as I understand it the root cause is that the openSUSE Linux kernel has no (not yet?) specific support for slow flash memory as used in usual USB sticks in contrast to SSD harddisks that have an intelligent controller with sufficient big data buffers in between. On usual USB sticks the kernel basically operates directly on the slow flash memory and - as fas as I found out - there is no way to tell the kernel the hardware parameters of flash memory - in particular the size of the physical units (physical block size) for read/write operations (that is usually something like 4MB or 8MB - mega bytes not kilo bytes!) so that the kernel could do its read/write operations on the flash memory using its physical block size to avoid both slowdown from read-modify-write in the USB stick and slowdown from multiple small reads (some KB) instead of big reads (4MB or 8MB) and needless wear from multiple small writes (some KB) instead of few big writes (4MB or 8MB). I am not at all a kernel expert here but I think if I could tell the kernel e.g. "use 4MB block size for /dev/sdb" then a Linux system may run with acceptable speed even on usual USB sticks.

×
Edit Comment 894
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
A short note what I accomplished and what I didn't: It was relatively easy to get a working Linux system on a USB stick. But it is time consuming until one understands Kwi sufficiently so that it makes what one wants. What did not work in the end was to get it running sufficiently fast from usual USB sticks. It runs sufficiently fast from a high-end USB stick with SLC (single level cell) flash memory. But on all usual (a.k.a. cheap) USB sticks it is too slow for normal usage. As fas as I understand it the root cause is that the openSUSE Linux kernel has no (not yet?) specific support for slow flash memory as used in usual USB sticks in contrast to SSD harddisks that have an intelligent controller with sufficient big data buffers in between. On usual USB sticks the kernel basically operates directly on the slow flash memory and - as fas as I found out - there is no way to tell the kernel the hardware parameters of flash memory - in particular the size of the physical units (physical block size) for read/write operations (that is usually something like 4MB or 8MB - mega bytes not kilo bytes!) so that the kernel could do its read/write operations on the flash memory using its physical block size to avoid both slowdown from read-modify-write in the USB stick and slowdown from multiple small reads (some KB) instead of big reads (4MB or 8MB) and needless wear from multiple small writes (some KB) instead of few big writes (4MB or 8MB). I am not at all a kernel expert here but I think if I could tell the kernel e.g. "use 4MB block size for /dev/sdb" then a Linux system may run with acceptable speed even on usual USB sticks.
 
×
Reply to jsmeix
A short note what I accomplished and what I didn't:
It was relatively easy to get a working Linux system on a USB stick. But it is time consuming until one understands Kwi sufficiently so that it makes what one wants.
What did not work in the end was to get it running sufficiently fast from usual USB sticks. It runs sufficiently fast from a high-end USB stick with SLC (single level cell) flash memory. But on all usual (a.k.a. cheap) USB sticks it is too slow for normal usage. As fas as I understand it the root cause is that the openSUSE Linux kernel has no (not yet?) specific support for slow flash memory as used in usual USB sticks in contrast to SSD harddisks that have an intelligent controller with sufficient big data buffers in between. On usual USB sticks the kernel basically operates directly on the slow flash memory and - as fas as I found out - there is no way to tell the kernel the hardware parameters of flash memory - in particular the size of the physical units (physical block size) for read/write operations (that is usually something like 4MB or 8MB - mega bytes not kilo bytes!) so that the kernel could do its read/write operations on the flash memory using its physical block size to avoid both slowdown from read-modify-write in the USB stick and slowdown from multiple small reads (some KB) instead of big reads (4MB or 8MB) and needless wear from multiple small writes (some KB) instead of few big writes (4MB or 8MB). I am not at all a kernel expert here but I think if I could tell the kernel e.g. "use 4MB block size for /dev/sdb" then a Linux system may run with acceptable speed even on usual USB sticks.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview