Linux on a Stick 0.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Infrastructure Monitoring Linux on a Stick 0.4 (Default branch)
# 1  
Old 01-04-2008
Linux on a Stick 0.4 (Default branch)

Linux on a Stick (LoaS) is a very small and simple Linux server distribution that boots from a USB flash drive and runs from RAM. It is targeted towards server administrators who are familiar with Linux, as its only configuration method is the command line. License: GNU General Public License (GPL) Changes:
This release fixes paths in OpenVPM's easy-rsa vars file. It upgrades the NTP package to 4.2.2. It upgrades the base libraries from Slackware v9 to Slackware v11. Init and install scripts have been rewritten in PHP. BusyBox has been upgraded to 1.8.2. This release supports headless systems serial consoles. New packages of note: NFS/NIS, OpenLDAP, PHP 5.02 FastCGI, FreeRadius, Zabbix, lighttpd, glusterfs, and DRDB.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Debian

Hardlink on wheezy by default for usb-stick?

May somebody can give me a hint. I am still using my old squeeze and it works the way I want. But my recent post about changing the owners rights, e.g. 777 or 755 anyway, it could be 644 as well. While configuring a new pc, just by chance I discovered how to enter the BIOS. And here it comes. I... (11 Replies)
Discussion started by: 1in10
11 Replies

2. SCO

Mount USB stick

hi Howto mount an USB stick under SCO 5.0.7? BTW ist it possible to mount USB stick in the command line using 'tools' at the Boot: prompt from OpenServer Release 5.0.7 installation CD? (1 Reply)
Discussion started by: ccc
1 Replies

3. Linux

installing CDlinux onto a SD stick?

what program(s) will i need, for either windows 7 or ubuntu (i have both installed on my HDD), to install onto a SD card, and how big should the memory stick be for this? the ISO is about 230mb (rounded up) and the SD card i plan to use is 512mb. (3 Replies)
Discussion started by: Sterist
3 Replies

4. Ubuntu

Ubuntu on USB stick?

Hey Guys I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Discussion started by: rbansal2
3 Replies

5. Filesystems, Disks and Memory

Mount USB stick...

Dummies questions, perfect for this. I cannot mount my idiotic usb stick on Slackware, I input the following on non-graphic mode as root: Mount -t vfat /dev/sdc1/usbstick usbstick is the folder i created for mounting my USB, the file system is FAT, and everytime I input that I get some kind... (2 Replies)
Discussion started by: Dax01
2 Replies

6. Solaris

crontab does not stick

When I do crontab cronfile and then checks crontab -l everything looks good. The cronjobs are there as they should. Then I leave it, hoping it to stop a process at 11.30 pm and start it up again at 06.00 am. When I am back in the morning, if I then do crontab -l, it is empty. And nothing... (4 Replies)
Discussion started by: lulle
4 Replies

7. UNIX for Dummies Questions & Answers

Stick with Solaris 10 or try something else?

Hello. New to the forum here. I was wondering if I could get some input from those who use Linux/Unix based operating systems exclusively. I use Solaris 10 here at work, while it was confusing at first (terminal commands and such,) I am quickly adapting to it. At home, I use Windows XP... (5 Replies)
Discussion started by: Filth Pig
5 Replies

8. Linux

Booting Linux from an USB stick

I got Puppy linux and installed it on a usb stick. In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick, What going on ?? (2 Replies)
Discussion started by: perleo
2 Replies
Login or Register to Ask a Question
UDISKS(7)							      udisks								 UDISKS(7)

NAME
udisks - Storage Management DESCRIPTION
udisks provides an interface to enumerate storage devices and perform operations on them. Any application can access the org.freedesktop.UDisks service on the system message bus. Some operations (such as formatting disks etc.) is restricted using polkit. DEVICE INFORMATION
On Linux, udisks relies on recent versions of udev(7) and the kernel. Influential device properties in the udev database include: UDISKS_PRESENTATION_HIDE If set to 1 this is a hint to presentation level software that the device should not be shown to the user. UDISKS_PRESENTATION_NOPOLICY If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device). UDISKS_DISABLE_POLLING If set to 1 this will disable the polling of drives for media changes, for devices which do not send out media notifications by themselves (this mostly affects CD drives). Some CD drives cause bad effects such as very high CPU usage when being polled. UDISKS_PRESENTATION_NAME The name to user for the device when presenting it to the user. UDISKS_PRESENTATION_ICON_NAME The icon to use when presenting the device to the user. If set, the name must follow the freedesktop.org icon theme specification. UDISKS_AUTOMOUNT_HINT A variable to influence whether a device should be automounted. Possible values include "always" (to hint that a device should always be automounted) and "never" (to hint that a device should never be automounted). Note that this is only a hint - the auto-mounter might not honor it. UDISKS_SYSTEM_INTERNAL If set, this will override the usual bus type based detection of whether a device is considered "system internal". "0" means "removable" (i. e. eligible for automounting, and normal users can mount), any other value means "system internal" (i. e. no automounting, and only administrators can mount). The ID_DRIVE_* properties are used to describe what kind of physical media can be used in a device. These are typically set on the main block device (e.g. /dev/sdb) and more than one these properties can be set if the device supports multiple kinds of media. ID_DRIVE_EJECTABLE Whether the media in the drive is physically ejectable. Only set this to 1 (or 0) if the drive truly uses (or doesn't) ejectable media. In particular, it is not necessary to set this for e.g. iPod or Kindle devices where it is necessary to send a command via eject(1) since the desktop user session will offer this option for removable devices regardless of whether they are ejectable. If this property is not set, a heuristic will be used to determine if the media is ejectable (drives using optical, Zip or Jaz media are considered ejectable). ID_DRIVE_DETACHABLE Whether the device is detachable. It is only meaningful to set this to 0 (to avoid marking a device as detachable) since the code for detaching the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive is detachable (currently only devices connected through USB are detachable). ID_DRIVE_CAN_SPINDOWN Whether the device can spin down. It is only meaningful to set this to 0 (to avoid marking a device as being capable of spinning down) since the code for spinning down the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive can spin down (currently only ATA devices, including those USB devices with a SAT layer) can be spun down). ID_DRIVE_FLASH The device is compatible with flash. ID_DRIVE_FLASH_CF The device is compatible with Compact Flash. ID_DRIVE_FLASH_MS The device is compatible with Memory Stick. ID_DRIVE_FLASH_SM The device is compatible with SmartMedia. ID_DRIVE_FLASH_SD The device is compatible with SecureDigital. ID_DRIVE_FLASH_SDHC The device is compatible with High-Capacity SecureDigital. ID_DRIVE_FLASH_MMC The device is compatible with MultiMediaCard. ID_DRIVE_FLOPPY The device is compatible with floppy disk. ID_DRIVE_FLOPPY_ZIP The device is compatible with Zip. ID_DRIVE_FLOPPY_JAZ The device is compatible with Jaz. The ID_DRIVE_MEDIA_* properties describe the current media in a device. As with the ID_DRIVE_* properties, these properties are typically set on the main block device (e.g. /dev/sdb). Typically only one of these properties are set. ID_DRIVE_MEDIA_FLASH The physical media currently inserted into the device is flash. ID_DRIVE_MEDIA_FLASH_CF The physical media currently inserted into the device is Compact Flash. ID_DRIVE_MEDIA_FLASH_MS The physical media currently inserted into the device is Memory Stick. ID_DRIVE_MEDIA_FLASH_SM The physical media currently inserted into the device is SmartMedia. ID_DRIVE_MEDIA_FLASH_SD The physical media currently inserted into the device is SecureDigital. ID_DRIVE_MEDIA_FLASH_SDHC The physical media currently inserted into the device is High-Capacity SecureDigital. ID_DRIVE_MEDIA_FLASH_MMC The physical media currently inserted into the device is MultiMediaCard. ID_DRIVE_MEDIA_FLOPPY The physical media currently inserted into the device is floppy disk. ID_DRIVE_MEDIA_FLOPPY_ZIP The physical media currently inserted into the device is Zip. ID_DRIVE_MEDIA_FLOPPY_JAZ The physical media currently inserted into the device is Jaz. REMOTE CLIENTS
TODO: write me. AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at http://bugs.freedesktop.org/enter_bug.cgi?product=udisks. SEE ALSO
udev(7), polkit(8), udisks-daemon(8), udisks-tcp-bridge(1), udisks(1) udisks March 2008 UDISKS(7)