{"action":"created","issue":{"url":"https://api.github.com/repos/Drive-Trust-Alliance/sedutil/issues/16","labels_url":"https://api.github.com/repos/Drive-Trust-Alliance/sedutil/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/Drive-Trust-Alliance/sedutil/issues/16/comments","events_url":"https://api.github.com/repos/Drive-Trust-Alliance/sedutil/issues/16/events","html_url":"https://github.com/Drive-Trust-Alliance/sedutil/issues/16","id":130161568,"number":16,"title":"conf file not up-to-date; redundant option for fdisk in buildbiospba","user":{"login":"juliandroid","id":7766093,"avatar_url":"https://avatars.githubusercontent.com/u/7766093?v=3","gravatar_id":"","url":"https://api.github.com/users/juliandroid","html_url":"https://github.com/juliandroid","followers_url":"https://api.github.com/users/juliandroid/followers","following_url":"https://api.github.com/users/juliandroid/following{/other_user}","gists_url":"https://api.github.com/users/juliandroid/gists{/gist_id}","starred_url":"https://api.github.com/users/juliandroid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/juliandroid/subscriptions","organizations_url":"https://api.github.com/users/juliandroid/orgs","repos_url":"https://api.github.com/users/juliandroid/repos","events_url":"https://api.github.com/users/juliandroid/events{/privacy}","received_events_url":"https://api.github.com/users/juliandroid/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-31T18:09:35Z","updated_at":"2016-02-01T23:15:52Z","closed_at":null,"body":"In the **conf** file I had to fix the TINYCORE to **Core-current.iso** because http://distro.ibiblio.org/tinycorelinux/6.x/x86/ doesn't contain the hard-coded version anymore (maybe you can take the old one from the \"archive\" directory or use the current.iso).\r\n\r\nThe other problem I have is maybe due to different versions of the fdisk. On my machine \r\n> fdisk -v\r\n> fdisk from util-linux 2.27.1\r\n\r\nskips one of the steps (might be harmless):\r\n\r\n> ~/msed/sedutil/images/biospba$ sudo fdisk -C 10 biospba-1.10-dirty.img\r\n> \r\n> Welcome to fdisk (util-linux 2.27.1).\r\n> Changes will remain in memory only, until you decide to write them.\r\n> Be careful before using the write command.\r\n> \r\n> Device does not contain a recognized partition table.\r\n> Created a new DOS disklabel with disk identifier 0xa072777f.\r\n> \r\n> Command (m for help): h\r\n> \r\n> Command (m for help): o\r\n> \r\n> Created a new DOS disklabel with disk identifier 0x389aeee2.\r\n> \r\n> Command (m for help): n\r\n> Partition type\r\n>    p   primary (0 primary, 0 extended, 4 free)\r\n>    e   extended (container for logical partitions)\r\n> Select (default p): p\r\n> Partition number (1-4, default 1): 1\r\n> First sector (1-2047, default 1): 63\r\n> Last sector, +sectors or +size{K,M,G,T,P} (63-2047, default 2047): \r\n> \r\n> Created a new partition 1 of type 'Linux' and of size 992.5 KiB.\r\n> \r\n> Command (m for help): a\r\n> Selected partition 1\r\n> The bootable flag on partition 1 is enabled now.\r\n> \r\n> **Command (m for help): 1**\r\n> **1: unknown command**\r\n> \r\n> Command (m for help): t\r\n> \r\n> Selected partition 1\r\n> Partition type (type L to list all types): b\r\n> Changed type of partition 'Linux' to 'W95 FAT32'.\r\n> \r\n> Command (m for help): w\r\n> The partition table has been altered.\r\n> Syncing disks.\r\n\r\nObviously the \"1\" command is not recognized in that context!\r\n\r\nEdit: I see the **same** issue with **buildrescue** - it seems after setting the active partition (\"a\") you don't need to pass \"1\"?"},"comment":{"url":"https://api.github.com/repos/Drive-Trust-Alliance/sedutil/issues/comments/178249253","html_url":"https://github.com/Drive-Trust-Alliance/sedutil/issues/16#issuecomment-178249253","issue_url":"https://api.github.com/repos/Drive-Trust-Alliance/sedutil/issues/16","id":178249253,"user":{"login":"r0m30","id":1573106,"avatar_url":"https://avatars.githubusercontent.com/u/1573106?v=3","gravatar_id":"","url":"https://api.github.com/users/r0m30","html_url":"https://github.com/r0m30","followers_url":"https://api.github.com/users/r0m30/followers","following_url":"https://api.github.com/users/r0m30/following{/other_user}","gists_url":"https://api.github.com/users/r0m30/gists{/gist_id}","starred_url":"https://api.github.com/users/r0m30/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/r0m30/subscriptions","organizations_url":"https://api.github.com/users/r0m30/orgs","repos_url":"https://api.github.com/users/r0m30/repos","events_url":"https://api.github.com/users/r0m30/events{/privacy}","received_events_url":"https://api.github.com/users/r0m30/received_events","type":"User","site_admin":false},"created_at":"2016-02-01T23:15:52Z","updated_at":"2016-02-01T23:15:52Z","body":"The system is set up to use any existing resources if they already exist on your machine, so when tinycore updates their distro I don't see it until I start fresh, and as I said in the other report I'll do that when I build the next release.  I'll also take a look at the doc to see if I can make it clearer.  I sometimes assume that the reader knows more than they can be reasonably expected to know when they are new to the project.  \r\n\r\nI'm using Ubuntu 14.x to build on and I have fdisk v 2.20.1 from their standard package system.  I don't know if they changed the command sequence in 2.27 but it looks like it :-(\r\n\r\nThat said I know that there are a couple of distros packaging the software, so it can be built from what is there."}}