Skip to main content

Label VFAT device (SDHC SD Card)

Solution:
[root@neo ~]# df -h | grep media | grep -v tmp

/dev/sdc1                      31525888  2944800  28581088  10% /media/8288-1391

[root@neo ~]# mlabel -i /dev/sdc1 ::TABLET

[root@neo ~]# df -h | grep media | grep -v tmp
/dev/sdc1                       31G  2.9G   28G  10% /media/TABLET


Issue:
I have a new tablet that I am attempting to script some automated, or event-driven sync mechanism.  I have added a 32 GB SDHC card to the device and enabled the tablet to ask whether it should mount the SD card as a USB device when connected to a PC.  Initially the device was identified as /media/8288-1391

Not a big deal, but I wanted something a bit easier to quickly identify.
 NOTE: This was written around RHEL 6/fedora 16 - things have changed since this time - most significantly the place where it gets mounted.


[root@neo ~]# tail -f /var/log/messages


Feb 18 22:33:55 neo kernel: [28587.481254] scsi 6:0:0:0: Direct-Access     Lenovo   ThinkPad Tablet  0000 PQ: 0 ANSI: 2
Feb 18 22:33:55 neo kernel: [28587.482412] sd 6:0:0:0: Attached scsi generic sg2 type 0
Feb 18 22:33:55 neo kernel: [28587.489779] sd 6:0:0:0: [sdc] Attached SCSI removable disk
Feb 18 22:34:05 neo kernel: [28598.162053] sd 6:0:0:0: [sdc] 63076352 512-byte logical blocks: (32.2 GB/30.0 GiB)
Feb 18 22:34:05 neo kernel: [28598.166042] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 18 22:34:05 neo kernel: [28598.252008]  sdc: sdc1





Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...