Windows 10: Installing and Running BASH on Windows 10 (Build 14316)

I have been using Ubuntu BASH on Windows 10 for a couple of days now, and here are a couple of real quick observations. Contrary to what the OP said, there is no need for SUDO on BASH in Windows 10, when you open BASH you are already root. This is wrong and goes against everything that Ubuntu and Linux in general stands for.

Also, I have used this app to try a lot of different things and some commands just don't work. Like

top

it does not do anything in BASH on Windows 10 but it is a handy command in an actual Ubuntu installation.

I think that this app is a joke and I can't see any practical use for it, but I am still playing with it to come to grips with its function.

 

@Rocky , all the "sudos" I did above are not for Windows 10. I was controlling my Raspberry Pi running Rasbian OS remotely on Windows 10. I said "sudo away" to connote start using bash. It's an expression for Linux geeks.

 

Cool, sounds good to me.

 

I got it to connect to the Pi today ,all is a go now ! upward and onward .lol

 

Time to sudo-away!

 

if I switch my Pi, and try to connect to another one, I get this message , I rebooted windows ,no difference ,I know the host is different I changed it ,,,any ideas ..

 

@caperjack , I can't replicate your issue. I've tried connecting my 2 Pi's and I was able to connect both of them at the same time. And both are in use (playing music)...

 

I also used "Bash on Ubuntu" window and still okay. I just finished updating both Pi's..

 

Remember this is a beta... and root is likely perfectly fine given that it's a virtual environment...

I imagine that most tools that deal with processes and what not would not work, or it might be because the tty is not configured in a way that top likes. Remember, it's a beta.

There are many valid uses I can think of. Windows has had a Subsystem for Unix for years to allow you to run posix commands under Windows. Imagine running perl scripts or python.. without having to rewrite them for Windows...

 

Hi there
Can you install services on it -- I'd like to see if the excellent MPD (Music Player Daemon) works -- be great if I could run that from a windows console.

However installing XRDP on the Linux host and simply accessing the Linux host directly via Windows RDP seems to negate the whole point of Bash on Windows - so is it a really useful function or will it be just a Toy.

What would be nice if you had a whole Linux Virtualized environment built in including a GUI -- Linux can be made really small so the overhead shouldn't be too much at all.

Cheers
jimbo

 

Remote desktop works great if your logging into the full Raspbian on a Pi. Once you install XRDP. If it's running OPENELEC/KODI though, its not so easy, if even possible. I haven't been able to make it work. I only just started trying about 10 min ago. Everything I read says you can't do it from Windows Remote Desktop. I'll have to plug my spare tower in and install the latest preview with BASH and give that a go.

 

There's no problem installing services. I was able to install mpc, mpd, moc but it doesn't detect a sound driver. I have yet to go back and try to resolve that. Maybe you can help us figure it out.


XRDP is good if you are not used to working on terminal screens and you rely on tools and icons (GUI) or if you are using office tools, etc. but SSH can also accomplish a lot if you know what you are doing.

 

Hi there
I'll have a go - I'm currently rebuilding a NAS box to use Esxi and a number of VM's this weekend. When I've done that I'll have a go with the latest build. I've got a spare machine I can use for this so it doesn't matter if I totally hose it up.

Mpd would be great as it can run command line - doesn't need a GUI. I'll see about the sound problem. Be later in the week though -- want to get my NAS server up and running again first.

Cheers
jimbo

 

I have just enabled this feature in 14342 and it appears this has changed.

After downloading Ubuntu from the store it prompts you to create a user and password. When you open bash it no longer opens root@localhost but yourname@yourWindowsPC. And you do have to use sudo now.





However through windows you have full control to %localappdata%\lxss\rootfs so it seems these authorities only apply to the bash side of things.

 

I found this video today on YouTube:
[youtube]DmsJHocTt84[/youtube]