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
MOUNT_UDF(8)						    BSD System Manager's Manual 					      MOUNT_UDF(8)

NAME
mount_udf -- mount a UDF filesystem SYNOPSIS
mount_udf [-o options] [-s sessionStart] [-n lastRecordedLBA] [-b blockSize] [-p packetSizeInBlocks] [-v verificationPolicy] [-w] devicePath mountPath DESCRIPTION
The mount_udf command attaches the UDF filesystem residing on the device devicePath to the global filesystem namespace at the location indi- cated by mountPath. This command is normally executed by mount(8) at boot time. The options are as follows: -o options Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -v verificationPolicy This is an advanced option not useful for regular use. It controlls the verification policy when writing to RW type optical media. Its value can be "meta", "all", or "none". Policy "meta" means only the metadata are verified after they are written. This is the default policy. Policy "all" means to verify data written, which could be several times slower than policy "meta". Policy "none" does not verify any data. It is only slightly faster than "meta" in normal cases, but may result a corrupted UDF disc if the write of metadata fails. -s sessionStart This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the start Logical Block Address of the last session where UDF data structures (VRS and AVDP) resides. This value overrides the value obtained from the device. -n lastRecordedLBA This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the last recorded Logical Block Address where the UDF VAT ICB will be searched. This value overrides the value obtained from the device. -b blockSize This is an advanced option not useful for regular use. It specifies the block size in bytes used when mounting the UDF volume. This value overrides the value obtained from the device. -p packetSizeInBlocks This is an advanced option not useful for regular use. It specifies the packet size in blocks when manually mounting the UDF volume. This value overrides the value obtained from the device. -w This is an advanced option not useful for regular use. It forces to enable the experimental packet writing function on optical media that has not been fully supported, such as CD-R, CD-RW, DVD-R, DVD+R, HD DVD-R, and BD-R. Writing to these media does not work on some drives and may cause data corruption or data loss on some other drives. Therefore, this flag should be used only by file system developers when debugging the experimental write functions. The -s, -n, -b, and -p flags are not useful in normal use. They are mainly used for debugging and data recovery. Since the -s, -n, and -p flags are all specified in units of block size, when any of these flags are specified, it is strongly recommended that the -b flag is also specified. SEE ALSO
mount(2), unmount(2), fstab(5), mount(8) BUGS
Reading of all UDF revisions (1.02 - 2.60) on both block device (e.g., hard drives and USB drives) and most optical media is supported. Writing to block devices, DVD-RW and DVD+RW is supported with the following exceptions: (1) Cannot write Finder Info, Resource Fork, or other extended attributes in UDF volumes of revision 1.02 and 1.50; (2) Cannot write to mirrored metadata partition. HISTORY
The mount_udf utility first appeared in Mac OS X. 4th Berkeley Distribution December 6, 2006 4th Berkeley Distribution
All times are GMT -4. The time now is 05:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy