On 7 May 2016 11:29:04 GMT, Jasen Betts <jasen@xnet.co.nz> Gave us:>On 2016-05-07, DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> wrote:snip>> I think it was an early version of Mandriva (Mandrake) which had a >> partition manager 'fdisk' application which allowed the operator to >> create a file system from a list of over 100 different ones. Why that >> went away, I do not know. >0 > >still available for small disks > > >Welcome to fdisk (util-linux 2.28). >Changes will remain in memory only, until you decide to write them. >Be careful before using the write command. > >Device does not contain a recognized partition table. >Created a new DOS disklabel with disk identifier 0xe8caee2c. > >Command (m for help): n >Partition type > p primary (0 primary, 0 extended, 4 free) > e extended (container for logical partitions) >Select (default p): p >Partition number (1-4, default 1): 1 >First sector (2048-5530576, default 2048): >Last sector, +sectors or +size{K,M,G,T,P} (2048-5530576, default 5530576): > >Created a new partition 1 of type 'Linux' and of size 2.7 GiB. > >Command (m for help): t >Selected partition 1 >Partition type (type L to list all types): l > > 0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris > 1 FAT12 27 Hidden NTFS Win 82 Linux swap / So c1 DRDOS/sec (FAT- > 2 XENIX root 39 Plan 9 83 Linux c4 DRDOS/sec (FAT- > 3 XENIX usr 3c PartitionMagic 84 OS/2 hidden or c6 DRDOS/sec (FAT- > 4 FAT16 <32M 40 Venix 80286 85 Linux extended c7 Syrinx > 5 Extended 41 PPC PReP Boot 86 NTFS volume set da Non-FS data > 6 FAT16 42 SFS 87 NTFS volume set db CP/M / CTOS / . > 7 HPFS/NTFS/exFAT 4d QNX4.x 88 Linux plaintext de Dell Utility > 8 AIX 4e QNX4.x 2nd part 8e Linux LVM df BootIt > 9 AIX bootable 4f QNX4.x 3rd part 93 Amoeba e1 DOS access > a OS/2 Boot Manag 50 OnTrack DM 94 Amoeba BBT e3 DOS R/O > b W95 FAT32 51 OnTrack DM6 Aux 9f BSD/OS e4 SpeedStor > c W95 FAT32 (LBA) 52 CP/M a0 IBM Thinkpad hi ea Rufus alignment > e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a5 FreeBSD eb BeOS fs > f W95 Ext'd (LBA) 54 OnTrackDM6 a6 OpenBSD ee GPT >10 OPUS 55 EZ-Drive a7 NeXTSTEP ef EFI (FAT-12/16/ >11 Hidden FAT12 56 Golden Bow a8 Darwin UFS f0 Linux/PA-RISC b >12 Compaq diagnost 5c Priam Edisk a9 NetBSD f1 SpeedStor >14 Hidden FAT16 <3 61 SpeedStor ab Darwin boot f4 SpeedStor >16 Hidden FAT16 63 GNU HURD or Sys af HFS / HFS+ f2 DOS secondary >17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fb VMware VMFS >18 AST SmartSleep 65 Novell Netware b8 BSDI swap fc VMware VMKCORE >1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid fd Linux raid auto >1c Hidden W95 FAT3 75 PC/IX bc Acronis FAT32 L fe LANstep >1e Hidden W95 FAT1 80 Old Minix be Solaris boot ff BBT >Partition type (type L to list all types): > > >gdisk (the GPT equivalent of fdisk) shows a shorter list as it onlt >lists known GPT compatible operating systems. > >Hex code or GUID (L to show codes, Enter = 8300): > >0700 Microsoft basic data 0c01 Microsoft reserved 2700 Windows RE >3000 ONIE boot 3001 ONIE config 3900 Plan 9 >4100 PowerPC PReP boot 4200 Windows LDM data 4201 Windows LDM metadata >4202 Windows Storage Spac 7501 IBM GPFS 7f00 ChromeOS kernel >7f01 ChromeOS root 7f02 ChromeOS reserved 8200 Linux swap >8300 Linux filesystem 8301 Linux reserved 8302 Linux /home >8303 Linux x86 root (/) 8304 Linux x86-64 root (/ 8305 Linux ARM64 root (/) >8306 Linux /srv 8307 Linux ARM32 root (/) 8400 Intel Rapid Start >8e00 Linux LVM a500 FreeBSD disklabel a501 FreeBSD boot >a502 FreeBSD swap a503 FreeBSD UFS a504 FreeBSD ZFS >a505 FreeBSD Vinum/RAID a580 Midnight BSD data a581 Midnight BSD boot >a582 Midnight BSD swap a583 Midnight BSD UFS a584 Midnight BSD ZFS >a585 Midnight BSD Vinum a600 OpenBSD disklabel a800 Apple UFS >a901 NetBSD swap a902 NetBSD FFS a903 NetBSD LFS >a904 NetBSD concatenated a905 NetBSD encrypted a906 NetBSD RAID >ab00 Recovery HD af00 Apple HFS/HFS+ af01 Apple RAID >af02 Apple RAID offline af03 Apple label af04 AppleTV recovery >af05 Apple Core Storage bc00 Acronis Secure Zone be00 Solaris boot >bf00 Solaris root bf01 Solaris /usr & Mac Z bf02 Solaris swap >bf03 Solaris backup bf04 Solaris /var bf05 Solaris /home >bf06 Solaris alternate se bf07 Solaris Reserved 1 bf08 Solaris Reserved 2 >Press the <Enter> key to see more codes: >bf09 Solaris Reserved 3 bf0a Solaris Reserved 4 bf0b Solaris Reserved 5 >c001 HP-UX data c002 HP-UX service ea00 Freedesktop $BOOT >eb00 Haiku BFS ed00 Sony system partitio ed01 Lenovo system partit >ef00 EFI System ef01 MBR partition scheme ef02 BIOS boot partition >f800 Ceph OSD f801 Ceph dm-crypt OSD f802 Ceph journal >f803 Ceph dm-crypt journa f804 Ceph disk in creatio f805 Ceph dm-crypt disk i >fb00 VMWare VMFS fb01 VMWare reserved fc00 VMWare kcore crash p >fd00 Linux RAID >Hex code or GUID (L to show codes, Enter = 8300): > >but neither will actually create a filesystem, it only creates a >partition tagged with that type, the partition will need to be >formatted before it is usable.The one to which I refer was part of the installer and most certainly would create and format and install the OS to, and it was actually more like 150 types. Welcome to nice try... good guess.
Verifying SD Cards
Started by ●May 3, 2016
Reply by ●May 7, 20162016-05-07
Reply by ●May 7, 20162016-05-07
On 07/05/2016 12:52, DecadentLinuxUserNumeroUno wrote:> > Welcome to nice try... good guess. >*plonk*
Reply by ●May 7, 20162016-05-07
On Sat, 07 May 2016 10:06:28 +0100, mm0fmf <none@invalid.com> Gave us:>On 07/05/2016 08:20, Rob wrote: >> Jasen Betts <jasen@xnet.co.nz> wrote: >>> Kernel support exists for HPFS(IBM), NTFS(MS), HFS(Apple), XFS(SGI) >>> NFS(SUN), ZFS(SUN) etc. So by some measure these could also be >>> considered native. >> >> It seems this word causes considerable confusion. >> As English is not my first language and I get vocabulary only by reading >> technical articles, it was my understanding that "native filesystem" >> means the filesystem the OS normally uses for full functionality. >> >> i.e. NTFS for Windows, Ext* or similar for Linux, etc. >> >> This as opposed to foreign filesystem support like NTFS for Linux, or >> legacy filesystem support like FAT for Windows. >> >> But apparently this is incorrect. >> >Your understanding of native filing is more than acceptable Rob.Hey, Rob. Aren't you glad this retarded fuck approves? After all, he thinks making a retarded filter file edit session announcement is an important post.
Reply by ●May 7, 20162016-05-07
On Sat, 07 May 2016 13:04:07 +0100, mm0fmf <none@invalid.com> Gave us:>On 07/05/2016 12:52, DecadentLinuxUserNumeroUno wrote: > >> >> Welcome to nice try... good guess. >> >*plonk*Filter file edit session announcement posts are even more retarded than keeping a filter file to start with, child. Good job, you 20 IQ dumbfuck.
Reply by ●May 8, 20162016-05-08
On Sat, 7 May 2016 12:01:50 +0200, Hans-Bernhard Br�ker <HBBroeker@t-online.de> wrote:>Windows may leave casual observers under the impression that is has only >one FS available, because it generally doesn't offer a choice of FS to >the user. It just picks what Redmond decided was "best" for a given >situation. > >And of course "WIndows" isn't actually one OS, it's a whole line of at >least 3 distinct families: Windows 1 to 3, the Windows 9x family and the >NT-based family. Each of those can be said to have a different native >file system: FAT, FAT32 and NTFS, respectively.It's hard to group Win1/2 with Win3 - the change to protected mode profoundly changed the system. Nor is FAT32 really strictly associated with Win9x - it wasn't even introduced until OSR2 for Win95.
Reply by ●May 11, 20162016-05-11
On Sat, 07 May 2016 13:04:07 +0100 mm0fmf <none@invalid.com> wrote in Message id: <ngkld5$c5v$1@dont-email.me>:>On 07/05/2016 12:52, DecadentLinuxUserNumeroUno wrote: > >> >> Welcome to nice try... good guess. >> >*plonk*What took you so long?
Reply by ●May 11, 20162016-05-11
On Wed, 11 May 2016 09:54:55 -0400, JW <none@dev.null> Gave us:>On Sat, 07 May 2016 13:04:07 +0100 mm0fmf <none@invalid.com> wrote in >Message id: <ngkld5$c5v$1@dont-email.me>: > >>On 07/05/2016 12:52, DecadentLinuxUserNumeroUno wrote: >> >>> >>> Welcome to nice try... good guess. >>> >>*plonk* > >What took you so long?You're a bunch of pussies who run like Trump or cry "It's not fair!"
Reply by ●May 11, 20162016-05-11
On 11/05/2016 14:54, JW wrote:> On Sat, 07 May 2016 13:04:07 +0100 mm0fmf <none@invalid.com> wrote in > Message id: <ngkld5$c5v$1@dont-email.me>: > >> On 07/05/2016 12:52, DecadentLinuxUserNumeroUno wrote: >> >>> >>> Welcome to nice try... good guess. >>> >> *plonk* > > What took you so long? >He only showed recently on the Pi newsgroup. He's not even a good troll. Some are huge fun, witty, amusing and entertaining whilst still trolling along. Few people get plonked by me, just 4 at the moment including this not very competent troll.
Reply by ●May 11, 20162016-05-11
On 5/3/2016 10:54 AM, rickman wrote:> I found an eBay vendor with a really *great* price on 64 GB microSDXC > cards and ordered one ($11.50 shipped). It was shipped from within the > US so it came in a few days. I've used H2testw to verify that it really > is 64 GB and got this message... "Warning: Only 61052 of 61053 MByte > tested." A dialog pops up saying this is normal if you are using NTFS, > but I formatted it in exFAT. So is this a problem? > > The intended use is in the rPi, so I will try firing that up later today > and see if I can run a similar test there. I'd like to verify the speed > of the card. What utility would be good for that? > > If the card checks out I'm going to order several more.So far the card seems fine. But oddly enough I can't get the Samsung microSD to SD card adapter to work in my PC. I found an older 32 GB EVO card I had bought last year and that Samsung adapter doesn't work either. I measured them with calipers and they seem to be the same size. I thought the Samsung adapter was a bit thinner, but if anything the one that works is a couple thousandths thinner. I don't have any reason to believe the two Samsung adapters are actually fake and the ones that work most likely *are* fake. I also have some Kinston branded adapters that also won't work. This explains why I couldn't get any of the several 1 GB microSD cards to work last year. I guess I never realized it was the adapters and not the microSD cards. They all seem to work now in the two good adapters. I'll have to see if I can get any of the "bad" adapters to work in the rPi which I just found today. Seems I had it squirreled away in an unmarked box. -- Rick C
Reply by ●May 11, 20162016-05-11
rickman <gnuarm@gmail.com> writes:> This explains why I couldn't get any of the several 1 GB microSD cards > to work last year. I guess I never realized it was the adapters and > not the microSD cards.Try cleaning the contacts on the microSD cards with an eraser. I find that helps with adapters sometimes. I don't know a way to clean the contacts inside the adapters. Maybe I could do that by busting the adapter open. I might try that sometime. I have lots of them that came with cards, and they're cheap enough anyway.
