Sponsored Content
Full Discussion: LM 19.1 from pendrive
Operating Systems Linux LM 19.1 from pendrive Post 303032922 by Corona688 on Tuesday 26th of March 2019 04:58:00 PM
Old 03-26-2019
URL is broken.

You had persistence before, did you not? The issue you had was that it was slow, but this is not unexpected -- USB is slow. Working around it meant putting everything in RAM and that, of course, is not persistent. Catch 22. Slow media does not have a go-faster button, you sped it up by not using it!

It may be possible to do something with unionfs overlays, booting from image but writing to disk, or mounting a read-write /home overtop of the imaged one, etc, etc. Not recommended unless you understand the boot process for your distribution extremely well.

Last edited by Corona688; 03-26-2019 at 06:04 PM..
This User Gave Thanks to Corona688 For This Post:
 

6 More Discussions You Might Find Interesting

1. Red Hat

helo how to mount pendrive on redhat 9

helo my sysem is running on redhat 9. now i want to take data from redhat 9 pc to pen drive. but when i plug it it is not detected. can u tell me how to mount pendrive on redhat9. amit (1 Reply)
Discussion started by: amitpansuria
1 Replies

2. UNIX for Dummies Questions & Answers

boot from a pendrive

Can anybody explane 'How to boot from a pendrive' ?Is it possible to load Operating System from a pendrive----? How? (5 Replies)
Discussion started by: Ajith kumar.G
5 Replies

3. UNIX for Dummies Questions & Answers

Copying files unto a usb pendrive/external disk from Solaris 9

Hi all, Can anybody help me with how I can connect a usb pendrive or external disk to a Sun Server which runs on Solaris 9? I am able to connect the usb drive to a windows server easily and copy files but am wondering if it is possible to do that with Solaris. Any help will be appreciated. thanks. (3 Replies)
Discussion started by: rahmantanko
3 Replies

4. SCO

mount the pendrive on the unixware 7.1.4

please let me know how to mount the pendrive on the unixware (1 Reply)
Discussion started by: deepthi.s
1 Replies

5. UNIX for Dummies Questions & Answers

Unable to acces my pendrive in linux

Hi Gurus, in linux I am unable to access my pendrive(i am even not seeing the icon or location for my pendrive ). Please anyany could help me to get rid of this issue. regards, Sanjay :) (4 Replies)
Discussion started by: sanjay.login
4 Replies

6. Slackware

Which USB pendrive image to install Slackware on an old AMD K6 3D ?

Holla, I have been trying to install a recent distro, with a minimum X such as jwm, but unfortunately my cdrom is broken and I can only boot the USB port, with a pendrive. AMD K6 3D is today too old for being for linux. Is there an image of slackware than runs that processor and that can... (5 Replies)
Discussion started by: raptor34
5 Replies
install(1M)						  System Administration Commands					       install(1M)

NAME
install - install commands SYNOPSIS
/usr/sbin/install -c dira [-m mode] [-u user] [-g group] [-o] [-s] file /usr/sbin/install -f dirb [-m mode] [-u user] [-g group] [-o] [-s] file /usr/sbin/install -n dirc [-m mode] [-u user] [-g group] [-o] [-s] file /usr/sbin/install -d | -i [-m mode] [-u user] [-g group] [-o] [-s] dirx... /usr/sbin/install [-m mode] [-u user] [-g group] [-o] [-s] file [dirx...] DESCRIPTION
install is most commonly used in ``makefiles'' (see make(1S)) to install a file in specific locations, or to create directories within a file system. Each file is installed by copying it into the appropriate directory. install uses no special privileges to copy files from one place to another. The implications of this are: o You must have permission to read the files to be installed. o You must have permission to copy into the destination directory. o You must have permission to change the modes on the final copy of the file if you want to use the -m option. o You must be super-user if you want to specify the ownership of the installed file with the -u or -g options. If you are not the super- user, the installed file is owned by you, regardless of who owns the original. install prints messages telling the user exactly what files it is replacing or creating and where they are going. If no options or directories (dirx ...) are given, install searches a set of default directories ( /bin, /usr/bin, /etc, /lib, and /usr/lib, in that order) for a file with the same name as file. When the first occurrence is found, install issues a message saying that it is overwriting that file with file, and proceeds to do so. If the file is not found, the program states this and exits. If one or more directories (dirx ...) are specified after file, those directories are searched before the default directories. OPTIONS
The following options are supported: -c dira Install file in the directory specified by dira, if file does not yet exist. If it is found, install issues a message say- ing that the file already exists, and exits without overwriting it. -f dirb Force file to be installed in given directory, even if the file already exists. If the file being installed does not already exist, the mode and owner of the new file is set to 755 and bin , respectively. If the file already exists, the mode and owner is that of the already existing file. -n dirc If file is not found in any of the searched directories, it is put in the directory specified in dirc. The mode and owner of the new file is set to 755 and bin, respectively. -d Create a directory. Missing parent directories are created as required as in mkdir -p. If the directory already exists, the owner, group and mode is set to the values given on the command line. -i Ignore default directory list, searching only through the given directories (dirx ...). -m mode The mode of the new file is set to mode. Set to 0755 by default. -u user The owner of the new file is set to user. Only available to the super-user. Set to bin by default. -g group The group id of the new file is set to group. Only available to the super-user. Set to bin by default. -o If file is found, save the ``found'' file by copying it to OLDfile in the directory in which it was found. This option is useful when installing a frequently used file such as /bin/sh or /lib/saf/ttymon, where the existing file cannot be removed. -s Suppress printing of messages other than error messages. USAGE
See largefile(5) for the description of the behavior of install when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes). ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
chgrp(1), chmod(1), chown(1), cp(1), make(1S), mkdir(1), attributes(5), largefile(5) SunOS 5.10 1 Jul 2004 install(1M)
All times are GMT -4. The time now is 11:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy