@allquixotic There are 5 Traffic Shaper modes on pfSense.

Google results for ("hfsc" "cbq" "fairq" "codelq" "priq") are useless. I have no idea what they mean.

So I'm trying to convert from command prompt to poweshell but I can't figure out how to change the default size of the window. It is not the same size as command prompt & is to large for my laptopt

@William Right click the title bar (or left click the icon) > Defaults > Windows Size.

hmm didn't work urrghh what is going on

it changes when I open a new window

@Burgi I once ran into the issue of having Windows 10, but it's been fixed.

@William Exactly. Defaults changes all new windows, Properties changes the current window.

I think this is the issue superuser.com/questions/36074/…

testing it now

FWIW, you can change the window size in script as well: $host.UI.RawUI.WindowSize = [System.Management.Automation.Host.Size]::new($x, $y)

lol

Thanks Hi Ben you seem to be a Powershell expert why does it take so long for basic commands like ls/dir to display in powershell?

What I want with pfSense (part of it, anyway) is exactly what's been posted on this forum thread, except the answer is four images I can't see... and then 10 pages of people thanking the user for such a great guide. That. I. can't. see.

Fuck you denvercoder9. I hate forums.

@William Those commands (which are actually both aliases for Get-ChildItem) internally use the .NET type FileInfo, which I suspect loads a boatload of extra info when they're created, before you ask for that information

There's also the general overhead of the whole infrastructure being CLR, but that shouldn't be noticeable on a reasonably fast system

@ThatRussianGuy I can't either. I don't think there are any images

@ThatRussianGuy Do you have to be logged in to get attachments?

is it a bad idea to do New-Alias dir cmd /c dir`

(and yes, forums are a horrible experience after having been on SE)

@BenN That's a possibility I considered. I think I'll have to overcome my laziness :P

@William You could, but you would lose all the nice things that make PowerShell powerful

And then you would have to deal with the process launch, which is pretty expensive

And quoting would be a terrible disaster

quoting what would a disaster? Here is the question I had asked stackoverflow.com/questions/33227307/…

@ThatRussianGuy heh

(fun fact: in one of my answers, I was helping someone escape a space when running a command to run some other thing, and eventually we needed nine spaces to keep arguments quoted correctly in the end)

Quoting spaces to dir would be painful because cmd's launch would eat some of the quotes

And you have to deal with cmd escaping

wouldn't this work function ls {cmd /c "dir $args"}

It will "work" but the results will no longer be PowerShell objects

@BenN Yes. That works.

You'd get a collection of lines of text instead of a collection of nice objects

@DavidPostill :D

thxs

@ThatRussianGuy Create an account and log in to see the images :)

Doing that right now

Then you could write a self-answered question using the information you find ;)

@BenN But... But... Server bullies Fault...

@BenN So I timed cmd /c dir and powershell's dir and they are close to the same speed

It seems to be dispalying objects differently purposefully

Yep, processes are expensive

no they are the same speed timed

Well, when you shell out to cmd, you get the classic dir's format; PowerShell has no influence over that

This calls for science

FUCK YOU PFSENSE, FUCK YOU PFSENSE FORUMS, FUCK YOU SIMPLE MACHINES FORUM BOARDS, FUCK YOU WHOEVER THOUGHT IT WAS A GREAT IDEA TO HIDE IMAGES FROM NON LOGGED-IN USERS WITHOUT ANY SORT OF INDICATION WHATSOEVER.

How do you know there are images then?

It's like they went "We could give zero shits to usability and UX... or... we could actively create a negative user experience. Yeah. Sounds great. Let's go with that."

> I have attempted to document the process (...) in screenshots.

Thread was read 55956 times. Images were viewed 2500 times.

@ThatRussianGuy I take it you can see the images now?

Yeah.

@BenN although you may be right about the objects explain this Measure-Command {ls} Measure-Command {dir /c "dir"} at least on my machine the ls is faster. Sorry if you already stated this I don't 100% understand.

@William For large directories, cmd /c dir completely annihilates Get-ChildItem, by an order of magnitude

Hopefully I won't be deterred by my wife's avalanche of cat videos anymore.

But for smaller directories, the startup cost of the new process dominates, which I think is why you're getting the similar speeds

there is something else going on

how do I convert the object to text before outputing?

It does it for you

you may be right. My solution is to run powershell in cmd

for now

Linux ls stills completes faster then both dir and powershell's ls no idea why

because ntfs is reading all dem sneaky other bits

I'm using cygwin

what does the object contain i wonder

it is my Downloads folder the largest folder on my computer

thanks everyone

Not what I asked/meant

Also, how many times have you ran ls on cygwin, as it's likely cached it now

Huh... apparently when we install Notepad++ from our software library it also installs a little tool and catches any request to open Notepad.exe and redirects it to open in Notepad++.exe instead! o.o

I believe that's called an Image Hijack in Autoruns

hjmmm

IIRC the Registry thingy responsible is called something along the lines of Image File Execution Options

pretty sure there's a reg key to do exactly that tho

we were discussing it last week or so.

night yall

@djsmiley2k See the properties on FileInfo

Night