My experience build the 2.6.17 kernel under Cygwin

Gabriel Goldstein
Tue Jan 9 18:42:00 GMT 2007

> 2.  Cygwin does not appear to handle the advanced file system
> to support mknod properly.  This may be a specific thing to my
> situation, but my dev kit had a sample file system.  It would not
> into cygwin without a seg fault. 

  Can you narrow it down to a tarball containing just a single file?  Or
is it
a fairly small tarchive?
File attached for review.  It's just a small sample fs from my dev kit
>  My workaround was to basically do this
> on a VM Ware / RH machine.  Annoying, but it did work.  What I may
> suggest is a way to have a real linux file system that you can 'mount'
> and provide this functionality.

  This one gets raised every so often, but it's not really a cygwin
issue.  It
requires a windows filesystem driver that knows how to mount a linux
filesystem.  That's a device driver, whereas cygwin is all user-mode
application; if you have such a driver on your machine, the linux drive
show up in windows and have a drive letter, and will automatically be
availably through /cygdrive/letter.

  (Yes, it would be *possible* to provide a cygwin filesystem driver
that runs
in usermode, and just uses ioctls to do raw sector reads and writes.
porting FUSE to cygwin would be the way to go at some stage....)

I was thinking, just for this purpose as it would be slow, to have a
'file' you could mount and it would hold the file system inside.  

I personally think a lot of engineers doing development have most of
their tools on Windows (ok, I'm a hardware guy) and another machine
sometimes isn't in the cards.

Any other ways to build an embedded fs under Cygwin?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: target_fs.tar.gz
Type: application/x-gzip
Size: 196945 bytes
Desc: target_fs.tar.gz
URL: <>
-------------- next part --------------
Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list