Package Details: ms-sys 1:2.4.1-2

Git Clone URL: (read-only)
Package Base: ms-sys
Description: Used to create Microsoft compatible boot records
Upstream URL:
Licenses: GPL
Conflicts: ms-sys-devel
Submitter: Allan
Maintainer: chungy
Last Packager: chungy
Votes: 220
Popularity: 1.939694
First Submitted: 2008-12-28 13:05
Last Updated: 2017-05-27 21:38

Dependencies (0)

Required by (0)

Sources (1)

Latest Comments

chungy commented on 2017-08-05 04:20

I've been able to successfully make bootable Windows 7 USB sticks with this package, but it is a little tricky. My method goes as such:
1. Partition the drive with MBR (not GPT!), making an NTFS partition with type 0x07 and the active flag set
2. Use mkfs.ntfs on the new partition
3. Run "ms-sys -n" on the partition, and "ms-sys -7" on the whole USB device itself
4. Copy all the files from the Windows 7 DVD/ISO to the NTFS partition; "cp -r" is sufficient...

arewaolakunle commented on 2017-08-04 13:43

@okabekudo Same here...ended up using rufus to create it. I actually thought something all of a sudden was wrong with my image(had only one).

okabekudo commented on 2017-06-20 21:09

I don't think this works any longer for creating bootable Windows 7 usb sticks on a fully updated system. I've tried for several hours now with different isos that all work when creating a bootable stick on windows. I know that I did nothing wrong in the process because I've done this many times. Formatting to ntfs setting bootflag creating mbr through ms-sys -7 copying the files of the iso to the stick. I even tried the devel version but no luck. It prompts "this is no bootable disk" every time on many different computers. Could someone try this to confirm it's broken?

chungy commented on 2017-05-27 23:05

> I don't know [...] why you're so eager to not use it.

I haven't been convinced that it's necessary for this package. Examples like chromium, firefox, systemd, tor are far easier to see the need given their attack surfaces.

> ? This has to be run as root.

For certain uses. I've used it as non-root plenty of times (eg: virtual machine images :p)

polyzen commented on 2017-05-27 22:58

I don't know how effective the hardening-wrapper is for this nor why you're so eager to not use it.

> disk devices/partitions are normally off-limits to non-root users

? This has to be run as root.

> PIE may become the default in gcc "soon" (nullifying the need for the wrapper).

It's probably been "soon" for years now. Doesn't nullify the need until it has happened.

> install the package beforehand and knock yourself out.

Would require you remembering all packages which are written in C/++.

chungy commented on 2017-05-27 22:46

From both the wiki and IRC discussion, I glean:
1. Including the makedepends for hardening-wrapper is optional.
2. It is most useful for programs susceptible to security attacks. ms-sys is not SUID and disk devices/partitions are normally off-limits to non-root users.
3. PIE may become the default in gcc "soon" (nullifying the need for the wrapper).
4. If you want to build a hardened executable, install the package beforehand and knock yourself out.

I understand that you are the previous maintainer, I thank your input, but at the moment, I don't believe there's a critical reason to include hardening-wrapper as a makedepends.

polyzen commented on 2017-05-27 22:30

Keeping hardening-wrapper around after the relevant builds can cause issues with other builds (IIRC Emacs was an example).

chungy commented on 2017-05-27 22:27

Hmm, thanks. I'm still not sure why it should be added, or why it's not part of base-devel if packaging standards demand it. I'll ask on IRC about it.

polyzen commented on 2017-05-27 22:17

chungy commented on 2017-05-27 22:15

I removed it because it didn't seem essential to building. You can still have the package installed if you want to build it that way.

polyzen commented on 2017-05-27 21:42

Why remove the hardening-wrapper makedep?

Conflicts are added to devel/VCS packages.

polyzen commented on 2016-03-28 02:01

BlueSpirit, the "1:" is an epoch[]. Read 3 comments back for why we're on 2.4.1. (Edit: This is the stable release.)


BlueSpirit commented on 2016-03-27 00:19

Why is there an 1: in front of the "real" version number? This confuses pacaur which thinks 1:2.4.1 is newer than 2.5.3 ;)

polyzen commented on 2016-03-13 11:31

Fantastic.. Hopefully these versions have been stable enough, and caused no issues. Thank you for pointing this out, kyb.

If you want to use the dev version: just download this[], add -dev to the pkgname, add yourself as maintainer, and presto magico. Edit: Also bump the pkgver if there's an update by then.


kyb commented on 2016-03-13 10:08

It could be cool to select the version while installing

The lastest stable version is 2.4.1 and development 2.5.3-dev. You may alse type stable or dev as aliases to the lastest verions.
please select version (

trusktr commented on 2012-12-03 23:09

Does this work with GPT (UEFI) disks? From what I understand, first is the MBR, followed by the GPT, right? Well, I have a backup copy so I guess I will just try it...

PLum commented on 2012-04-02 11:42

new version is marked as development

PLum commented on 2012-04-02 11:39

new version 2.3.0