Re: Cannot make a copy of video DVD with k3b
On 08/08/2014 08:49 PM, davidscha...@mobilicity.blackberry.com wrote: Sorry about top posting. This old phone only does it this way. I use k3b 2.0.2 under F17 for burning video dvd's and don't have a problem. Also use it for data dvd and install dvd. Would like to know how it is fubar. Dave Sent from my BlackBerry® smartphone powered by Mobilicity In my own case, K3b refused to burn 100% of a file which gave a proper md5sum on two computers, separate operating systems, separate downloads. The same file download transferred via Konqueror-SuperUser to the Windows 7 partition and burned by burncdcc.exe had no burn problem and the disk had no trouble installing and using (with the exception of a particular difficulty with its software). In the case of the "fubar" which is my own interpretation, here is the quote from MCP on the PCLOS Forum, which was posted on July 21, altho I didn't see it until today: "k3b has not given me any problems. I don't burn that many disks but just recently when I tried to copy a dvd it got to the point of burning and it just stopped and would not move past the "Insert blank disk" message. I tried several times and then resorted to creating an image which it did, but when I put in a blank and tried to burn it would not progress past the mdsum. The burn button was greyed out." On 08/09/2014 12:12 AM, Doug wrote: On 08/08/2014 08:49 PM, davidscha...@mobilicity.blackberry.com wrote: Sorry about top posting. This old phone only does it this way. I use k3b 2.0.2 under F17 for burning video dvd's and don't have a problem. Also use it for data dvd and install dvd. Would like to know how it is fubar. Dave Sent from my BlackBerry® smartphone powered by Mobilicity In my own case, K3b refused to burn 100% of a file which gave a proper md5sum on two computers, separate operating systems, separate downloads. The same file download transferred via Konqueror-SuperUser to the Windows 7 partition and burned by burncdcc.exe had no burn problem and the disk had no trouble installing and using (with the exception of a particular difficulty with its software). In the case of the "fubar" which is my own interpretation, here is the quote from MCP on the PCLOS Forum, which was posted on July 21, altho I didn't see it until today: "k3b has not given me any problems. I don't burn that many disks but just recently when I tried to copy a dvd it got to the point of burning and it just stopped and would not move past the "Insert blank disk" message. I tried several times and then resorted to creating an image which it did, but when I put in a blank and tried to burn it would not progress past the mdsum. The burn button was greyed out." Another post on the PCLOS Forum, from craesz, same thread, reads as follows: "I too am having difficulty with K3b... I haven't used this machine to burn a CD in a while. Each time I try to burn, it tells me that there is an I/O problem and most likely my drive is full it's not. I just ran the above command and the output is: Code: [Select] |brwxrwxrwx+ 1 root root 11, 0 Aug 7 05:46 /dev/sr0 " | -Original Message- From: Doug Sender: users-boun...@lists.fedoraproject.org Date: Fri, 08 Aug 2014 19:01:50 To: Reply-To: Community support for Fedora users Subject: Re: Cannot make a copy of video DVD with k3b On 08/08/2014 06:35 PM, Ed Greshko wrote: On 08/09/14 03:20, Michael Hennebry wrote: On Thu, 7 Aug 2014, JD wrote: /snip/ The subject is correct: there is something verkocht in the latest K3b, ver. 2.0.2. I tried on two computers with two OSs to burn a DVD with K3b, and it screwed up with both of them. In the PCLOS Forum, there is a new post today about K3b being fubar. Just another example of the devs not listening to Ann Landers' advice--"If it ain't broke, don't fix it!" Or another old axiom: "If you play with anything long enough, you'll break it!" I have used K3b for years without a problem, and they went and broke it. --doug -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cannot make a copy of video DVD with k3b
On 08/08/2014 08:49 PM, davidscha...@mobilicity.blackberry.com wrote: Sorry about top posting. This old phone only does it this way. I use k3b 2.0.2 under F17 for burning video dvd's and don't have a problem. Also use it for data dvd and install dvd. Would like to know how it is fubar. Dave Sent from my BlackBerry® smartphone powered by Mobilicity -Original Message- From: Doug Sender: users-boun...@lists.fedoraproject.org Date: Fri, 08 Aug 2014 19:01:50 To: Reply-To: Community support for Fedora users Subject: Re: Cannot make a copy of video DVD with k3b snip/ On 08/09/2014 12:12 AM, Doug wrote: On 08/08/2014 08:49 PM, davidscha...@mobilicity.blackberry.com wrote: Sorry about top posting. This old phone only does it this way. I use k3b 2.0.2 under F17 for burning video dvd's and don't have a problem. Also use it for data dvd and install dvd. Would like to know how it is fubar. Dave Sent from my BlackBerry® smartphone powered by Mobilicity In my own case, K3b refused to burn 100% of a file which gave a proper md5sum on two computers, separate operating systems, separate downloads. The same file download transferred via Konqueror-SuperUser to the Windows 7 partition and burned by burncdcc.exe had no burn problem and the disk had no trouble installing and using (with the exception of a particular difficulty with its software). In the case of the "fubar" which is my own interpretation, here is the quote from MCP on the PCLOS Forum, which was posted on July 21, altho I didn't see it until today: "k3b has not given me any problems. I don't burn that many disks but just recently when I tried to copy a dvd it got to the point of burning and it just stopped and would not move past the "Insert blank disk" message. I tried several times and then resorted to creating an image which it did, but when I put in a blank and tried to burn it would not progress past the mdsum. The burn button was greyed out." Another post on the PCLOS Forum, from craesz, same thread, reads as follows: "I too am having difficulty with K3b... I haven't used this machine to burn a CD in a while. Each time I try to burn, it tells me that there is an I/O problem and most likely my drive is full it's not. I just ran the above command and the output is: Code: [Select] |brwxrwxrwx+ 1 root root 11, 0 Aug 7 05:46 /dev/sr0 " | The subject is correct: there is something verkocht in the latest K3b, ver. 2.0.2. I tried on two computers with two OSs to burn a DVD with K3b, and it screwed up with both of them. In the PCLOS Forum, there is a new post today about K3b being fubar. Just another example of the devs not listening to Ann Landers' advice--"If it ain't broke, don't fix it!" Or another old axiom: "If you play with anything long enough, you'll break it!" I have used K3b for years without a problem, and they went and broke it. --doug -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
Dennis Kaptain wrote: > Rick Stevens suggested "systemctl mask tmp.mount" as a fix. I tried > that and then I couldn't log in. It turns out, that command will make > my / partition read only. Following http://fedoraproject.org/wiki/Features/tmp-on-tmpfs#Release_Notes has always worked for me. It shouldn't affect your / partition, odd. -- Rex -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cannot make a copy of video DVD with k3b
Sorry about top posting. This old phone only does it this way. I use k3b 2.0.2 under F17 for burning video dvd's and don't have a problem. Also use it for data dvd and install dvd. Would like to know how it is fubar. Dave Sent from my BlackBerry® smartphone powered by Mobilicity -Original Message- From: Doug Sender: users-boun...@lists.fedoraproject.org Date: Fri, 08 Aug 2014 19:01:50 To: Reply-To: Community support for Fedora users Subject: Re: Cannot make a copy of video DVD with k3b On 08/08/2014 06:35 PM, Ed Greshko wrote: > On 08/09/14 03:20, Michael Hennebry wrote: >> On Thu, 7 Aug 2014, JD wrote: >> >> /snip/ The subject is correct: there is something verkocht in the latest K3b, ver. 2.0.2. I tried on two computers with two OSs to burn a DVD with K3b, and it screwed up with both of them. In the PCLOS Forum, there is a new post today about K3b being fubar. Just another example of the devs not listening to Ann Landers' advice--"If it ain't broke, don't fix it!" Or another old axiom: "If you play with anything long enough, you'll break it!" I have used K3b for years without a problem, and they went and broke it. --doug -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cannot make a copy of video DVD with k3b
On 08/08/2014 06:35 PM, Ed Greshko wrote: On 08/09/14 03:20, Michael Hennebry wrote: On Thu, 7 Aug 2014, JD wrote: /snip/ The subject is correct: there is something verkocht in the latest K3b, ver. 2.0.2. I tried on two computers with two OSs to burn a DVD with K3b, and it screwed up with both of them. In the PCLOS Forum, there is a new post today about K3b being fubar. Just another example of the devs not listening to Ann Landers' advice--"If it ain't broke, don't fix it!" Or another old axiom: "If you play with anything long enough, you'll break it!" I have used K3b for years without a problem, and they went and broke it. --doug -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cannot make a copy of video DVD with k3b
On 08/09/14 03:20, Michael Hennebry wrote: > On Thu, 7 Aug 2014, JD wrote: > >> You cannot copy TO a dvd with dd, cp, mv etc >> because writing to optical media requires specialized SW like >> cdrecord. > > As mentioned, I've done it. > Surprised me that it worked. > That said, it does not work any more. > 'Tis been a few years since I've done it. > Actually, you can still do that today. Took me a while to remember this. In order to do that you need to access the drive in "Packet Writing" mode. You can do that after installing udftools and using the various utilities within it to create a packet writing device and associate it with the DVD drive and then format the DVD+/- RW disc properly for use. -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SOLVED? - Re: Command line for creating partitions
On Aug 8, 2014, at 2:16 PM, Robert Moskowitz wrote: > > On 08/08/2014 03:00 PM, Chris Murphy wrote: >> On Aug 8, 2014, at 4:29 AM, Robert Moskowitz wrote: >> >>> Unfortuately there is no such command to delete all partitions, though you >>> kind of can do it by changing the table type, say from msdos to gpt. >> I forgot to address this specifically. First, you really should delete the >> filesystem signature before deleting partitions. This makes the filesystem >> invalid, and thus things like libblkid and libparted aren't going to >> recognize latent (stale) filesystems. The tool for this is wipefs part of >> util-linux. Use it like this for example: >> >> wipefs -a /dev/sdb[123] >> >> That will delete the fs signatures on all file systems found on partitions 1 >> through 3 on disk sdb. The partition table still contains entries of course, >> but the filesystems in them are invalidated. >> >> Next, if you want to get rid of all partitions, you can also use wipefs on a >> whole disk. > > wipefs -a /dev/sdb That will only remove signatures from either an MBR or GPT. It will not remove signatures from filesystems. You really should remove filesystem signatures first with /dev/sdX[1234…] and then remove the partition map sig with sdX alone. > No. I am developing my own notes on how to build up a boot card (and > eventually drive) for Redsleeve on my Cubieboard2. At this stage, I tend to > build then break a number of times, so having commands to build rather than > having to use a GUI speeds the rebuild time. But so far no magic for fstab; > I am having to put UUIDs in it. > > I have been given nice scripts for F19 & F20 remixes and F21 alpha. We will > see what I will need for Centos7arm development... > > I will then be putting all that I did on the Redsleeve wiki. blkid will get you the UUID and filesystem type so it's a bit easier to build the fstab; otherwise to automate it with command line instead of GUI, you'd look at kickstart installs which leverages anaconda and blivet to do all of these things for you, then does the install per your requirements. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
On 08/09/14 03:44, Joe Zeff wrote: > On 08/08/2014 02:28 AM, Kevin Wilson wrote: >> What is a good practice to achieve it in Fedora 20 ? there is no >> /etc/rc.local in my fedora 20, and trying to add an entry in >> /etc/rc.local does not cause it be be run across boots. > > systemctl enable rc-local.service No need See the notes in the service file... # This unit gets pulled automatically into multi-user.target by # systemd-rc-local-generator if /etc/rc.d/rc.local is executable. As explained in the release notes of an earlier version of Fedora. All you need to do is create the /etc/rc.d/rc.local file and make it executable. -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SOLVED? - Re: Command line for creating partitions
On 08/08/2014 03:00 PM, Chris Murphy wrote: On Aug 8, 2014, at 4:29 AM, Robert Moskowitz wrote: Unfortuately there is no such command to delete all partitions, though you kind of can do it by changing the table type, say from msdos to gpt. I forgot to address this specifically. First, you really should delete the filesystem signature before deleting partitions. This makes the filesystem invalid, and thus things like libblkid and libparted aren't going to recognize latent (stale) filesystems. The tool for this is wipefs part of util-linux. Use it like this for example: wipefs -a /dev/sdb[123] That will delete the fs signatures on all file systems found on partitions 1 through 3 on disk sdb. The partition table still contains entries of course, but the filesystems in them are invalidated. Next, if you want to get rid of all partitions, you can also use wipefs on a whole disk. wipefs -a /dev/sdb ?? thanks for all of this. This removes the signature for the partition table. Most any tool will consider it invalid, rather than broken, so it's not going to offer to fix it, it'll offer to repartition it: so in the GPT case, it gets a whole new disk identifier GUID rather than just restoring the signature. It is possible, btw to restore the signature and thus restore the partition table and all of its partitions (since those sectors aren't actually erased). You could also blow away 34 sectors from the start and end of the drive using dd if=/dev/zero. That's a hammer. Oh and I mentioned cgdisk (member of the gdisk family) that was wrong, it's curse-based. You want to look at sgdisk which is for use in scripts and accepts all commands from the CLI. It has a way to delete partitions individually. Note that this does not employ wipefs, so the actual filesystem contained within the partition you've deleted is still intact; and this also leaves the partition header intact, all it's doing is removing a partition table entry. sgdisk also has two zap options: one overwrites everything (sectors containing both MBR and GPT structures), the other option overwrites only the sectors containing GPT structures. So it really depends what you want to achieve, and how arbitrary the source drives are going to be. If you're writing a program or script you might look at python-blivet which has done a ton of work abstracting all of this stuff, if you can do what you need to do in python, No. I am developing my own notes on how to build up a boot card (and eventually drive) for Redsleeve on my Cubieboard2. At this stage, I tend to build then break a number of times, so having commands to build rather than having to use a GUI speeds the rebuild time. But so far no magic for fstab; I am having to put UUIDs in it. I have been given nice scripts for F19 & F20 remixes and F21 alpha. We will see what I will need for Centos7arm development... I will then be putting all that I did on the Redsleeve wiki. then you can use sane pthyon code to do things like wipe all fs's, delete all partitions, create new GPT, add new partitions, format them. And you don't need to know the prose for the 5 different utilities to make that happen. python-blivet is actually at the core of the Fedora installer, specifically for manipulating storage (it does everything you can imagine in including create, modify, destroy LVM objects; btrfs subvolumes; bunch of md raid stuff, etc.) http://pkgs.fedoraproject.org/cgit/python-blivet.git/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange parted behaviour
On 08/08/2014 02:32 PM, Chris Murphy wrote: On Aug 8, 2014, at 7:21 AM, Robert Moskowitz wrote: So I am making progress but saw a strange bit. #parted /dev/sdb mkpart uboot ext3 4 516 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB fat32uboot I formated it with: #mkfs -t ext3 /dev/sdb1 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB ext3uboot So why did parted mislabel the partition? Yeah you're getting confused. It's really easy. It didn't format it ext3, it just sets it to a partition type GUID for that filesystem, which in the version of parted you're using is for Microsoft basic data (i.e. it would not have made any difference had you chosen fat32 or ext3, because on GPT disks parted uses the same partition type code until you get to the Fedora 21 version and then choosing ext3 would make it a partition type GUID for "Linux filesystem". Parted is showing it as fat32 because it found a fat32 superblock. When you reformatted it ext3, parted found the ext3 superblock. So again, it's a throwback from when parted did formatting and fs resizing. The behaviors change silently (including flags) between MBR and GPT partition schemes too. So you have to be aware of what partition method is being used. And after I did all the setup for GPT, it (the Cubieboard) would not boot. So I looked at cards that I had that did boot, and THEY were all type msdos. So back to the beginning making the card msdos, and can't label the partitions, oh, but finally rebuilt and I did create a bootable card! So now I have a good cookbook that I will eventually be able to post to the Redsleeve wiki (what I am build). Once I get the video to login, I will say success. I only get login so far to the serial console. For example "boot" flag for MBR disks sets the active bit for a partition; whereas on GPT the "boot" flag changes the partition type GUID to that of "EFI System partition". Yeah I know, you're welcome to start shooting gin at any time but I guarantee you it doesn't really help. It's sorta like taking Percocet for pain and realizing it still hurts, you just don't care. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SOLVED? - Re: Command line for creating partitions
On 08/08/2014 02:24 PM, Chris Murphy wrote: On Aug 8, 2014, at 4:29 AM, Robert Moskowitz wrote: I am learning how to use parted in command line format. Unfortuately there is no such command to delete all partitions, though you kind of can do it by changing the table type, say from msdos to gpt. Also learned that the unused 4Mb I am seeing on most SD cards is for a reason. To get on the 4Mb alignment for performance reasons. It's 4KB, not 4MB, and it doesn't apply to SSDs, only HDD's specifically the 512e AF variety. a.) It's AF, Advanced Format, which means it has 4096 byte physical sectors, and 512e means it's emulating 512 byte sectors. So it appears as having 512 byte logical sectors, while having 4096 byte physical sectors. So one real sector has 8 logical sectors, which is where the performance problem can occur, when effectively asking the drive to update portions of a sector it causes the drive firmware to read-modify-write the sector. It is for SDcards that I was dealing with, and my information comes from: http://www.gnu.org/software/parted/manual/parted.html Now, we will show how to partition a low-end flash device (“low-end”, as of 2011/2012). For such devices, you should use 4MiB-aligned partition^. This command creates a tiny place-holder partition at the beginning, and then uses all remaining space to create the partition you’ll actually use: $parted -s /dev/sdX -- mklabel msdos \ mkpart primary fat32 64s 4MiB \ mkpart primary fat32 4MiB -1s I figured out that you really don't need the tiny place-holder, just leave it unallocated. Good to know about HDD and SSD as that will be later thanks parted /dev/sdb mkpart offset fat32 0 4 When I do that, parted complains. "Warning: The resulting partition is not properly aligned for best performance." What you should do is use 1 and 5, assuming you really want only a 4MB partition. In that case the result ends up being: Number Start End Size File system NameFlags 1 2048s 10239s 8192s offset msftdata If you want to agree to the widely used convention, use LBA 2048 as the start. If you want to do your own thing, you could find out the erase block size for your SSD and align on those boundaries, but due to the non-transparency of the flash translation layer, there's no guarantee this means you're actually aligned on erase block boundaries: but it seems like a good idea, doesn't hurt anything, but might be a waste of effort depending on how things are actually implemented in the SSD. parted /dev/sdb mkpart uboot ext3 4 516 But it is still acting strange. Print is showing that ext3 partition fat32! That's probably because libparted is finding a latent FAT32 superblock. The first thing to understand about parted, is that it's crusty. It used to do a lot of stuff that it doesn't do anymore but has the legacy operands of what it used to do. It used to format and resize volumes and partitions in one go, and it no longer does this. There is no partition type code that tells parted what the filesystem is, so it looks (maybe via libblkid, not sure) for the actual partition contents to see what filesystem it is and tells you that. But it's totally superfluous information in a partitioning tool. But in parted parlance you have to know these weird things because of its legacy. Likewise it doesn't directly tell you, or let you directly tell it, what a GPT partition's partition type GUID is. You have to tell it a filesystem, and then it sets the type code accordingly, which is quite honestly maddening. But whatever you just have to accept it if you're going to use parted. Its view of the world is abstracted to the degree it'll give you a completely distorted picture, and it's why I don't like it. So your first command with fat32, doesn't actually cause the partition to be formatted fat32. It merely set the partition type GUID to EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data). Due to poor decision making, if you're using a Fedora 20 or older version, parted uses that same type code when specifying ext3 as the file system. Out of essentially unlimited UUIDs parted devs chose to usurp a Microsoft one. It baffles me whether I'm sober or drunk. The Fedora 21 version, parted will set an ext3 partition to partition type code 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem) instead. And meanwhile gdisk and cgdisk have done this correctly for years. The parted "File system" column is not a reflection of the partition type GUID, it's actually looking for filesystem superblocks to identify what the filesystem is. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question?
Re: running a specified binary across reboots
On 08/08/2014 02:28 AM, Kevin Wilson wrote: What is a good practice to achieve it in Fedora 20 ? there is no /etc/rc.local in my fedora 20, and trying to add an entry in /etc/rc.local does not cause it be be run across boots. systemctl enable rc-local.service -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cannot make a copy of video DVD with k3b
On Thu, 7 Aug 2014, JD wrote: You cannot copy TO a dvd with dd, cp, mv etc because writing to optical media requires specialized SW like cdrecord. As mentioned, I've done it. Surprised me that it worked. That said, it does not work any more. 'Tis been a few years since I've done it. -- Michael henne...@web.cs.ndsu.nodak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SOLVED? - Re: Command line for creating partitions
On Aug 8, 2014, at 4:29 AM, Robert Moskowitz wrote: > Unfortuately there is no such command to delete all partitions, though you > kind of can do it by changing the table type, say from msdos to gpt. I forgot to address this specifically. First, you really should delete the filesystem signature before deleting partitions. This makes the filesystem invalid, and thus things like libblkid and libparted aren't going to recognize latent (stale) filesystems. The tool for this is wipefs part of util-linux. Use it like this for example: wipefs -a /dev/sdb[123] That will delete the fs signatures on all file systems found on partitions 1 through 3 on disk sdb. The partition table still contains entries of course, but the filesystems in them are invalidated. Next, if you want to get rid of all partitions, you can also use wipefs on a whole disk. This removes the signature for the partition table. Most any tool will consider it invalid, rather than broken, so it's not going to offer to fix it, it'll offer to repartition it: so in the GPT case, it gets a whole new disk identifier GUID rather than just restoring the signature. It is possible, btw to restore the signature and thus restore the partition table and all of its partitions (since those sectors aren't actually erased). You could also blow away 34 sectors from the start and end of the drive using dd if=/dev/zero. That's a hammer. Oh and I mentioned cgdisk (member of the gdisk family) that was wrong, it's curse-based. You want to look at sgdisk which is for use in scripts and accepts all commands from the CLI. It has a way to delete partitions individually. Note that this does not employ wipefs, so the actual filesystem contained within the partition you've deleted is still intact; and this also leaves the partition header intact, all it's doing is removing a partition table entry. sgdisk also has two zap options: one overwrites everything (sectors containing both MBR and GPT structures), the other option overwrites only the sectors containing GPT structures. So it really depends what you want to achieve, and how arbitrary the source drives are going to be. If you're writing a program or script you might look at python-blivet which has done a ton of work abstracting all of this stuff, if you can do what you need to do in python, then you can use sane pthyon code to do things like wipe all fs's, delete all partitions, create new GPT, add new partitions, format them. And you don't need to know the prose for the 5 different utilities to make that happen. python-blivet is actually at the core of the Fedora installer, specifically for manipulating storage (it does everything you can imagine in including create, modify, destroy LVM objects; btrfs subvolumes; bunch of md raid stuff, etc.) http://pkgs.fedoraproject.org/cgit/python-blivet.git/ Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
On Fri, 8 Aug 2014 12:39:39 -0500 Chris Adams wrote: > Once upon a time, Dennis Kaptain said: > > It still doesn't seem like an ideal way to handle /tmp when I have a > > perfectly good partition and swapping is a major performance killer. > > I'd rather disk access wait time is caused by accessing /tmp when I > > need to rather than swapping tmpfs in and out for a program. > > Swapping tmpfs files to swap is no more of a performance killer than > writing /tmp to disk to begin with (the same data would be written to > the same disk, just in a little bit different format and location). Please, please don't start about this stuff yet again. It has been rehashed many times over, in countless places on the net: if your typical usecase does not involve large files in /tmp and you have enough RAM to never hit swap, tmpfs is more efficient. Otherwise, disk is more efficient. Everyone needs to decide for themselves, and configure their system accordingly. If the OP has already decided what he wants, just tell him how to configure it, rather than trying to persuade him that your size fits all. HTH, :-) Marko -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange parted behaviour
On Aug 8, 2014, at 10:38 AM, Rick Stevens wrote: > I don't think "uboot" is a valid partition type--it should be > "primary", "logical" or "extended". Thus the format of the command > should have been: Since the disk is GPT there's no such distinction among partitions. Behavior wise they're primary partitions, and on-disk they're most like primary partitions, but it's better to just say they're partitions with no distinction. > > # parted /dev/sdb mkpart primary ext3 4 516 > # parted /dev/sdb name 1 uboot > > I've noticed that parted sometimes makes some weird decisions if > parameters it expects are missing or mis-specified. Yes. It's designed to be stable: if you update parted from 2.0 to 3.1, chances are your app will still do the partitioning portion correctly. But if you're a mortal user looking for an interface that accurately communicates facts bidirectionally, parted is eyebrow raising. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange parted behaviour
On Aug 8, 2014, at 7:21 AM, Robert Moskowitz wrote: > So I am making progress but saw a strange bit. > > #parted /dev/sdb mkpart uboot ext3 4 516 > > # parted /dev/sdb print > Model: Generic- Multi-Card (scsi) > Disk /dev/sdb: 7969MB > Sector size (logical/physical): 512B/512B > Partition Table: gpt > Disk Flags: > > Number Start End SizeFile system NameFlags > 1 4194kB 516MB 512MB fat32uboot > > I formated it with: > > #mkfs -t ext3 /dev/sdb1 > > # parted /dev/sdb print > Model: Generic- Multi-Card (scsi) > Disk /dev/sdb: 7969MB > Sector size (logical/physical): 512B/512B > Partition Table: gpt > Disk Flags: > > Number Start End SizeFile system NameFlags > 1 4194kB 516MB 512MB ext3uboot > > So why did parted mislabel the partition? Yeah you're getting confused. It's really easy. It didn't format it ext3, it just sets it to a partition type GUID for that filesystem, which in the version of parted you're using is for Microsoft basic data (i.e. it would not have made any difference had you chosen fat32 or ext3, because on GPT disks parted uses the same partition type code until you get to the Fedora 21 version and then choosing ext3 would make it a partition type GUID for "Linux filesystem". Parted is showing it as fat32 because it found a fat32 superblock. When you reformatted it ext3, parted found the ext3 superblock. So again, it's a throwback from when parted did formatting and fs resizing. The behaviors change silently (including flags) between MBR and GPT partition schemes too. So you have to be aware of what partition method is being used. For example "boot" flag for MBR disks sets the active bit for a partition; whereas on GPT the "boot" flag changes the partition type GUID to that of "EFI System partition". Yeah I know, you're welcome to start shooting gin at any time but I guarantee you it doesn't really help. It's sorta like taking Percocet for pain and realizing it still hurts, you just don't care. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SOLVED? - Re: Command line for creating partitions
On Aug 8, 2014, at 4:29 AM, Robert Moskowitz wrote: > I am learning how to use parted in command line format. Unfortuately there is > no such command to delete all partitions, though you kind of can do it by > changing the table type, say from msdos to gpt. > > Also learned that the unused 4Mb I am seeing on most SD cards is for a > reason. To get on the 4Mb alignment for performance reasons. It's 4KB, not 4MB, and it doesn't apply to SSDs, only HDD's specifically the 512e AF variety. a.) It's AF, Advanced Format, which means it has 4096 byte physical sectors, and 512e means it's emulating 512 byte sectors. So it appears as having 512 byte logical sectors, while having 4096 byte physical sectors. So one real sector has 8 logical sectors, which is where the performance problem can occur, when effectively asking the drive to update portions of a sector it causes the drive firmware to read-modify-write the sector. > > parted /dev/sdb mkpart offset fat32 0 4 When I do that, parted complains. "Warning: The resulting partition is not properly aligned for best performance." What you should do is use 1 and 5, assuming you really want only a 4MB partition. In that case the result ends up being: Number Start End Size File system NameFlags 1 2048s 10239s 8192s offset msftdata If you want to agree to the widely used convention, use LBA 2048 as the start. If you want to do your own thing, you could find out the erase block size for your SSD and align on those boundaries, but due to the non-transparency of the flash translation layer, there's no guarantee this means you're actually aligned on erase block boundaries: but it seems like a good idea, doesn't hurt anything, but might be a waste of effort depending on how things are actually implemented in the SSD. > parted /dev/sdb mkpart uboot ext3 4 516 > > But it is still acting strange. Print is showing that ext3 partition fat32! That's probably because libparted is finding a latent FAT32 superblock. The first thing to understand about parted, is that it's crusty. It used to do a lot of stuff that it doesn't do anymore but has the legacy operands of what it used to do. It used to format and resize volumes and partitions in one go, and it no longer does this. There is no partition type code that tells parted what the filesystem is, so it looks (maybe via libblkid, not sure) for the actual partition contents to see what filesystem it is and tells you that. But it's totally superfluous information in a partitioning tool. But in parted parlance you have to know these weird things because of its legacy. Likewise it doesn't directly tell you, or let you directly tell it, what a GPT partition's partition type GUID is. You have to tell it a filesystem, and then it sets the type code accordingly, which is quite honestly maddening. But whatever you just have to accept it if you're going to use parted. Its view of the world is abstracted to the degree it'll give you a completely distorted picture, and it's why I don't like it. So your first command with fat32, doesn't actually cause the partition to be formatted fat32. It merely set the partition type GUID to EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data). Due to poor decision making, if you're using a Fedora 20 or older version, parted uses that same type code when specifying ext3 as the file system. Out of essentially unlimited UUIDs parted devs chose to usurp a Microsoft one. It baffles me whether I'm sober or drunk. The Fedora 21 version, parted will set an ext3 partition to partition type code 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem) instead. And meanwhile gdisk and cgdisk have done this correctly for years. The parted "File system" column is not a reflection of the partition type GUID, it's actually looking for filesystem superblocks to identify what the filesystem is. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
Once upon a time, Dennis Kaptain said: > It still doesn't seem like an ideal way to handle /tmp when I have a > perfectly good partition and swapping is a major performance killer. > I'd rather disk access wait time is caused by accessing /tmp when I > need to rather than swapping tmpfs in and out for a program. Swapping tmpfs files to swap is no more of a performance killer than writing /tmp to disk to begin with (the same data would be written to the same disk, just in a little bit different format and location). When a program writes data to disk, it goes through the kernel page cache, to the filesystem layer, to the block layer, and then to disk. The filesystem has to allocate space (which means other writes to disk, updating block allocations, directories, etc.). The blocks are cached in the page cache in case they are read later. If the kernel needs RAM, it can throw them away. tmpfs lives directly in the page cache. So, when a program writes to a tmpfs file, it goes to the page cache and stops. Later, if the kernel needs RAM, it can push those pages to disk (swap space). The only difference between /tmp on disk and tmpfs is when pages get pushed to disk. In a system with sufficient RAM to hold the normal /tmp contents (which aren't very big under most circumstances), they never get pushed to disk with tmpfs, and performance is faster. The only downside to /tmp-on-tmpfs is that it is limited in size, based on available RAM. Ideally, it would be based on swap size, or total RAM+swap, but that's harder to do. However, Fedora defaults to a root filesystem that isn't huge (with a separate /home), so the size of /tmp is still limited. /tmp was never supposed to be about holding arbitrary sized chunks of data. -- Chris Adams -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange parted behaviour
On 08/08/2014 12:38 PM, Rick Stevens wrote: On 08/08/2014 06:21 AM, Robert Moskowitz issued this missive: So I am making progress but saw a strange bit. #parted /dev/sdb mkpart uboot ext3 4 516 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB fat32uboot I formated it with: #mkfs -t ext3 /dev/sdb1 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB ext3uboot So why did parted mislabel the partition? I don't think "uboot" is a valid partition type--it should be "primary", "logical" or "extended". Thus the format of the command should have been: # parted /dev/sdb mkpart primary ext3 4 516 # parted /dev/sdb name 1 uboot I've noticed that parted sometimes makes some weird decisions if parameters it expects are missing or mis-specified. Somewhere in my reading and testing I got that mkpart format was mkpart part-type label fs-type start end and then part-type became dropped if the partition type is gpt. Seems on further reading you are probably right. There is a separate labels command. -- - Rick Stevens, Systems Engineer, AllDigital ri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - - - - A friend said he climbed to the top of Mount Rainier. My view is - -that if there's no elevator, it must not be that interesting. - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
On 08/08/2014 09:51 AM, Tim issued this missive: Allegedly, on or about 08 August 2014, Kevin Wilson sent: Should it have #!/bin/bash as its first line ? My older Fedora install has #!/bin/sh as its first line in the rc.local file. Not sure if it really is using a lighter weight shell (which sounds like a good idea), or one is aliased to the other, on my system. /bin/sh is a symlink to /bin/bash. If bash is started as /bin/sh, then it tries to mimic sh's startup mechanisms as close as possible while remaining POSIX-compliant. Generally speaking, you can use them interchangeably. The differences in operation are fairly minor (the order in which some compound statements are evaluated for example), although they can bite you on occasion. Startup shell scripts were historically written in sh (a.k.a. Bourne shell) since that was the only shell you were _guaranteed_ to have on a Unix system (BSD- or SVR3/4-derived). csh and ksh were optional, csh originally only being available on BSD-derived systems. bash (Bourne Again shell) was written to enhance and work around some shortcomings in the original Bourne shell and to move some of the more commonly used commands inside the shell rather than having to call external binaries. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - "Daddy, why doesn't this magnet pick up this floppy disk?" - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
On 08/08/2014 12:51 PM, Tim wrote: > Allegedly, on or about 08 August 2014, Kevin Wilson sent: >> Should it have #!/bin/bash as its first line ? > > My older Fedora install has #!/bin/sh as its first line in the rc.local > file. Not sure if it really is using a lighter weight shell (which > sounds like a good idea), or one is aliased to the other, on my system. aliased ls -l /bin/sh /bin/sh -> bash > -- Kevin J. Cummings kjch...@verizon.net cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://www.linuxcounter.net/) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
Allegedly, on or about 08 August 2014, Kevin Wilson sent: > Should it have #!/bin/bash as its first line ? My older Fedora install has #!/bin/sh as its first line in the rc.local file. Not sure if it really is using a lighter weight shell (which sounds like a good idea), or one is aliased to the other, on my system. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. ZNQR LBH YBBX -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
Allegedly, on or about 08 August 2014, Dennis Kaptain sent: > Rick Stevens suggested "systemctl mask tmp.mount" as a fix. I tried > that and then I couldn't log in. That sounds like a very old problem. I encountered that, many years ago, when I swapped hard drives on a PC. Check the permissions of your /tmp directory, the sticky bit needs to be set. $ ll -d /tmp drwxrwxrwt. 24 root root 12288 Aug 9 02:15 /tmp Without that, graphical logins would fail. But command line logins would work, as they didn't play around with putting things in /tmp. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. ZNQR LBH YBBX -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange parted behaviour
On 08/08/2014 06:21 AM, Robert Moskowitz issued this missive: So I am making progress but saw a strange bit. #parted /dev/sdb mkpart uboot ext3 4 516 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB fat32uboot I formated it with: #mkfs -t ext3 /dev/sdb1 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB ext3uboot So why did parted mislabel the partition? I don't think "uboot" is a valid partition type--it should be "primary", "logical" or "extended". Thus the format of the command should have been: # parted /dev/sdb mkpart primary ext3 4 516 # parted /dev/sdb name 1 uboot I've noticed that parted sometimes makes some weird decisions if parameters it expects are missing or mis-specified. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - A friend said he climbed to the top of Mount Rainier. My view is - -that if there's no elevator, it must not be that interesting. - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
On Friday, August 08, 2014 10:32:15 AM Dennis Kaptain wrote: > So, how do I turn off fedora's tmpfs forever so I can use my physical > /tmp partition and not consume all my valuable RAM? Or stated > otherwise, how do I disable tmpfs AND keep / read-write? systemctl mask tmp.mount -A -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E signature.asc Description: This is a digitally signed message part. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
2014-08-08 10:46 GMT-05:00 Chris Adams : > Once upon a time, Dennis Kaptain said: >> While lurking on the list, I learned in a thread "Cannot make a copy >> of video DVD with k3b" that the way fedora is configured, tmpfs will >> consume 50% of my RAM and mount itself in /tmp. If you have gobs of >> RAM I suppose you'd never miss it unless you are doing serious video >> editing or something like that. > > There's a lot of misinformation about this. The tmpfs does _not_ > "consume 50% of [your] RAM". The maximum size of a tmpfs defaults to > 50% of RAM, but it only uses space as needed. Also, space used in tmpfs > can be pushed to swap (so if you run low on RAM, files in tmpfs will be > pushed out to swap on disk to free up RAM for programs). > > -- > Chris Adams > -- Thanks for clearing that up Chris. It still doesn't seem like an ideal way to handle /tmp when I have a perfectly good partition and swapping is a major performance killer. I'd rather disk access wait time is caused by accessing /tmp when I need to rather than swapping tmpfs in and out for a program. Is there a way to totally disable tmpfs and keep / read-write? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to disable tmpfs
Once upon a time, Dennis Kaptain said: > While lurking on the list, I learned in a thread "Cannot make a copy > of video DVD with k3b" that the way fedora is configured, tmpfs will > consume 50% of my RAM and mount itself in /tmp. If you have gobs of > RAM I suppose you'd never miss it unless you are doing serious video > editing or something like that. There's a lot of misinformation about this. The tmpfs does _not_ "consume 50% of [your] RAM". The maximum size of a tmpfs defaults to 50% of RAM, but it only uses space as needed. Also, space used in tmpfs can be pushed to swap (so if you run low on RAM, files in tmpfs will be pushed out to swap on disk to free up RAM for programs). -- Chris Adams -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
how to disable tmpfs
While lurking on the list, I learned in a thread "Cannot make a copy of video DVD with k3b" that the way fedora is configured, tmpfs will consume 50% of my RAM and mount itself in /tmp. If you have gobs of RAM I suppose you'd never miss it unless you are doing serious video editing or something like that. My system has only 3GB of RAM and it does appear that 1.5GB is now a tmpfs. I really don't have that to spare. I do have a 5GB /tmp partition on a physical HDD that I thought I had been using for years. Only now did I learn that I'm not. Rick Stevens suggested "systemctl mask tmp.mount" as a fix. I tried that and then I couldn't log in. It turns out, that command will make my / partition read only. I googled it and discovered that someone else had the same problem. There was no answer to that thread. You can fix this by "mount -o remount,rw /" and then issuing "systemctl unmask tmp.mount" and rebooting again. I tried editing the entry in /etc/fstab from UUID=996d5f64-0745-4af7-9260-559d5c66c7bd /ext4defaults 1 1 to UUID=996d5f64-0745-4af7-9260-559d5c66c7bd /ext4defaults,rw1 1 but that still didn't mount / rw. So, how do I turn off fedora's tmpfs forever so I can use my physical /tmp partition and not consume all my valuable RAM? Or stated otherwise, how do I disable tmpfs AND keep / read-write? Thanks, -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Strange parted behaviour
So I am making progress but saw a strange bit. #parted /dev/sdb mkpart uboot ext3 4 516 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB fat32uboot I formated it with: #mkfs -t ext3 /dev/sdb1 # parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 4194kB 516MB 512MB ext3uboot So why did parted mislabel the partition? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
On Fri, Aug 08, 2014 at 12:28:25PM +0300, Kevin Wilson wrote: > I want to run a binary of some Fedora application I wrote immediately > after reboot. > > I know that as a workaround I can wrap it as a systemd daemon, but I > prefer not to. You don't need to wrap it in anything -- whatever legitimate complaints there can be, simply running a binary or script is really easy. You just need something like: [Service] Type=oneshot ExecStart=/usr/local/bin/whatever [Install] WantedBy=default.target (If this is a long-running daemon, possibly "Type=forking" or "Type=simple" -- and simple is the default so you can leave that off.) But as Ed noted, if you don't want to do that, you can use /etc/rc.d/rc.local. Or, particularly if you want this to run as a non-root user, you can use "@reboot" in cron. This replaces all of the other time specifiers, so, like this: @reboot /usr/local/bin/whatever > What is a good practice to achieve it in Fedora 20 ? there is no > /etc/rc.local in my fedora 20, and trying to add an entry in > /etc/rc.local does not cause it be be run across boots. It's a little unfortunate that we don't support the traditional file location, but, there we are. -- Matthew Miller Fedora Project Leader -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cannot make a copy of video DVD with k3b
On 08/07/2014 03:59 PM, Rick Stevens wrote:
>>
>> so it went from 4 to 3 tmpfs processes??
>> or is it just the lack of the tmpfs process /tmp ??
>
> First, /tmp starts out as just a directory on the root filesystem ("/").
>
> Before your reboot, the system created a tmpfs filesystem and mounted
> it at /tmp. Therefore it's listed as a separate filesystem in "df"
> (because there IS a separate filesystem of type "tmpfs" mounted there)
> and it's 3.9G in size (meaning you probably have 8G of RAM).
>
> After your reboot, /tmp remains just a directory on your / filesystem.
> It won't display as a separate filesystem (because nothing's mounted
> there) and your / filesystem is 20G with 5.6G free at the moment.
>
> This new layout (with 5.6G free) would have been enough to create the
> ISO image in /tmp, whereas with the tmpfs crap, /tmp was only 3.9G and
> half your RAM was sucked up by that. Now you have all 8G of RAM
> available.
thank you! makes sense..
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
SOLVED? - Re: Command line for creating partitions
I am learning how to use parted in command line format. Unfortuately there is no such command to delete all partitions, though you kind of can do it by changing the table type, say from msdos to gpt. Also learned that the unused 4Mb I am seeing on most SD cards is for a reason. To get on the 4Mb alignment for performance reasons. So here is some things that I have figured out: parted /dev/sdb mklabel gpt parted /dev/sdb mkpart offset fat32 0 4 parted /dev/sdb mkpart uboot ext3 4 516 But it is still acting strange. Print is showing that ext3 partition fat32! # parted /dev/sdb mkpart uboot ext3 4 516 Information: You may need to update /etc/fstab. [root@lx120e ~]# parted /dev/sdb print Model: Generic- Multi-Card (scsi) Disk /dev/sdb: 7969MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system NameFlags 1 17.4kB 4000kB 3983kB offset 2 4194kB 516MB 512MB fat32uboot On 08/08/2014 01:37 AM, Cameron Simpson wrote: On 07Aug2014 16:29, Robert Moskowitz wrote: On 08/07/2014 03:13 PM, Joachim Backes wrote: have a look at /sbin/cfdisk OK. One more to study. I was also told about gdisk. But all of these are command menu programs. Not one-liners. The nice 'one-liners' in kckstart files are just commands to anaconda, it seems. No such program and 'clearpart' or 'part'. Though I suppose I could deal with a program that read a command file of such commands. We have used sfdisk for a long time for cloning partition tables from one drive to another. That cloning is done by dumping the table and then reading the dump. But that means that there is a dump format to sfdisk's output, and you can just craft the right input. Definitely purely command line. Cheers, Cameron Simpson Tomkin Coleman (tcol...@nv7.uswnvg.com) wrote: | Well, yes, get the bike but BEWARE!! | At first, you will just want to get, like, a 250 Rebel, just for commuting | and maybe a little fun, but you will wind up buying a 550, (just in case you | want to tour), and then you will stop paying any attention to the theatre | company you are working with and the graduate school you are attending, and | then you will spend all your summers touring and riding around with your | newfound biking buddies, and then you will find that you have got a real job | just so you can buy the bike of your dreams and pretty soon you will find | that your entire life has centered around your monster bike and you can only | date women who love bikes and hang with buddies who love bikes and work at a | job that supports your lifestyle and you will be incredibly happy, but always | very greasy. S! The meaning of life is supposed to be a SECRET! :-) - Bob Larson..DoD#1711..b...@honshu.ho.att.com..1994 Suzuki RF600R -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
On 08/08/14 17:57, Kevin Wilson wrote: > Thanks a lot! > Should it have #!/bin/bash as its first line ? I don't believe it is necessary, but I add it as a force of habit. -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
Hi, Thanks a lot! Should it have #!/bin/bash as its first line ? Kevin On Fri, Aug 8, 2014 at 12:33 PM, Ed Greshko wrote: > On 08/08/14 17:28, Kevin Wilson wrote: >> I want to run a binary of some Fedora application I wrote immediately >> after reboot. >> >> I know that as a workaround I can wrap it as a systemd daemon, but I >> prefer not to. >> >> In previous fedora distros, making it run across reboots was enabled >> by adding an entry >> in /etc/rc.local. >> >> What is a good practice to achieve it in Fedora 20 ? there is no >> /etc/rc.local in my fedora 20, and trying to add an entry in >> /etc/rc.local does not cause it be be run across boots. > > Yes, Fedora does support an rc.local concept > > From > > http://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html > > 3.2.4. rc.local no longer packaged > The /etc/rc.d/rc.local local customization script is no longer included by > default. Administrators who need this functionality merely have to create > this file, make it executable, and it will run on boot. > > -- > If you can't laugh at yourself, others will gladly oblige. > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: seg fault - how to track down cause!
On Thu, 2014-08-07 at 17:51 -0700, Jack Craig wrote: > yes! use ps *** to get parent pid to follow, then i think the chant > is > something like, > > strace -f -p > > note, a lot of system call info gets dumped, but IMHO, the needle is > in > that haystack! > > you might want to log output to a file, ... > > also, i loved to find a failing clue and then pipe strace -f ... | > grep > > Or you can attach a gdb instance to it and watch the segfault happening, get a backtrace etc. That's what debuggers are for. [Please don't top-post on this list. See the Guidelines] poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: running a specified binary across reboots
On 08/08/14 17:28, Kevin Wilson wrote: > I want to run a binary of some Fedora application I wrote immediately > after reboot. > > I know that as a workaround I can wrap it as a systemd daemon, but I > prefer not to. > > In previous fedora distros, making it run across reboots was enabled > by adding an entry > in /etc/rc.local. > > What is a good practice to achieve it in Fedora 20 ? there is no > /etc/rc.local in my fedora 20, and trying to add an entry in > /etc/rc.local does not cause it be be run across boots. Yes, Fedora does support an rc.local concept From http://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html 3.2.4. rc.local no longer packaged The /etc/rc.d/rc.local local customization script is no longer included by default. Administrators who need this functionality merely have to create this file, make it executable, and it will run on boot. -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
running a specified binary across reboots
Hello, Fedora users, I want to run a binary of some Fedora application I wrote immediately after reboot. I know that as a workaround I can wrap it as a systemd daemon, but I prefer not to. In previous fedora distros, making it run across reboots was enabled by adding an entry in /etc/rc.local. What is a good practice to achieve it in Fedora 20 ? there is no /etc/rc.local in my fedora 20, and trying to add an entry in /etc/rc.local does not cause it be be run across boots. regards, Kevin -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
