The Official *nix Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
No sooner had Fed 10 been released, did Fed11 come out - but I reckon they rushed things a bit.
.. since the repos are also being prepared for red 12
The best bit it so google around for some Fed11 repos. I used city-fan.org for quicker UK-based ones, as well as a few in France, and the Livana repos to get media-thingies, like codecs plugins. I know the official RH ones tend to get swamped from time to time.
BTW - did you know about yum-fastestmirror?
.. since the repos are also being prepared for red 12
The best bit it so google around for some Fed11 repos. I used city-fan.org for quicker UK-based ones, as well as a few in France, and the Livana repos to get media-thingies, like codecs plugins. I know the official RH ones tend to get swamped from time to time.
BTW - did you know about yum-fastestmirror?
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Hmm.....so essentially, they've closed the repos for now? Thats okay, I can wait - I just thought I'd lost the links or something (still not entirely comfortable with yum...great when it works, a bugger when it doesn't). Where do I check the list of repos used? Is there like a Yum Manger or something?
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
Yes (I've written a chapter about it) - but if you look in /etc/yum.repos.d/ you'll see a list of them.RageMatrix wrote:Where do I check the list of repos used? Is there like a Yum Manger or something?
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Ta, but those file mean little to me...I'll have to do some research I reckon (by which time the repos will probably be back up, but oh wellDungeon-Dave wrote:Yes (I've written a chapter about it) - but if you look in /etc/yum.repos.d/ you'll see a list of them.RageMatrix wrote:Where do I check the list of repos used? Is there like a Yum Manger or something?
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- wanye
- Baaaaaa!

- Posts: 3047
- Joined: Tue Sep 07, 2004 12:46 pm 0
- PSN: wanye_m
- Location: nottingham
- Contact:
Re: The Official *nix Thread
not tried it with my 360, but MEDIATOMB is teh aces (so much better than twonkyvision, which is a resource hungry POS) and works a treat with my PS3. the only issue i came across was it binding to the wrong adapter/ip address (i have vmware server on there, and it was binding to a vmware adapter. a quick addition of "-i eth0" to the startup command sorted it out.Ratsoap wrote:Has anyone got any experience with serving media to a 360 with Ubuntu? I have mate who is keen to make the leap, but this is a make or break issue. Googling suggests something called ushare, which sounds like a bit of a ballache to be honest, which he won't be keen on. Are there alternatives?
He's currently using TVersity on his windows box.
still need to get a decent organised view set up (i want it to display files in my tv and film folders individually in date order instead of all in one place in pseudo-alphabetical order), but for now it is doing its job pretty well. the other thing i havent tried out is transcoding, but thats on my list of priorities, as episode 8 of dollhouse wont play on my ps3 so i need to get it converted/trancoding...
- dom
- Baaaaa!

- Posts: 1370
- Joined: Wed Feb 09, 2005 1:17 pm 0
- Location: Edinburgh, UK and level 691859
- Contact:
Re: The Official *nix Thread
Try using YaST in SuSE, the operating system which tells you to "have a lot of fun" when you install it...
OMG (or oligodendrocyte myelin glycoprotein) is a molecule found in your central nervous system.
- JQW
- Baaaaa!

- Posts: 1186
- Joined: Thu Feb 22, 2007 12:23 pm 0
- Location: Ripon, where nothing ever happens.
Re: The Official *nix Thread
Ever tried sysadmsh under SCO Unix? You often find that the default terminal definitions were so broken, even sysadmsh wouldn't work properly.dom wrote:Try using YaST in SuSE, the operating system which tells you to "have a lot of fun" when you install it...
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
Fixed that for you... "OpenServer" was affectionately known as "OpenSphincter" around these parts.JQW wrote:Ever tried SCO Unix? You often find it was so broken, it wouldn't work properly.
- JQW
- Baaaaa!

- Posts: 1186
- Joined: Thu Feb 22, 2007 12:23 pm 0
- Location: Ripon, where nothing ever happens.
Re: The Official *nix Thread
I've thankfully forgotten most of the other problems I've had with it. In the mid-1990s we had a SCO box in our training room which we used whenever we put on a training course that covered TCP/IP, SMTP and the like, with the SCO box acting as a mail host and IP router, amongst other things. The sodding thing hardly ever worked reliably, so it was hopeless for the type of training we were doing. I replaced it with an early Slackware Linux implementation, and it worked perfectly, at least once I'd recompiled the kernel to add IP routing.Dungeon-Dave wrote:Fixed that for you... "OpenServer" was affectionately known as "OpenSphincter" around these parts.JQW wrote:Ever tried SCO Unix? You often find it was so broken, it wouldn't work properly.
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Fuck Fedora 11 - many little things are now broken. Works fine on my server, but my laptop is not happy at all. Going to install Fedora 10 on it again tonight (from scratch, sadly, unless I can somehow rollback the F11 install) or perhaps CentOS.
Yum still broken, but going to copy over the repos from my server to my laptop and see if that fixes anything. That'll teach me to upgrade at the earliest opportunity...
Yum still broken, but going to copy over the repos from my server to my laptop and see if that fixes anything. That'll teach me to upgrade at the earliest opportunity...
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
umask and file permissions help?
Now, I thought I had this down, but apparently not...
When I type "umask", I get the value 0002. Now, the first digit is unused, so that leaves 002. I'm only just getting round with numeric file permissions, but it is essentially this, AFAICT:-
0 No permissions
4 Read
5 Read / Execute
6 Read / Write
7 Read / Write / Execute
My book says that any new file created has new permissions automatically assigned by the value of umask. Hows does this work then? I get the following permissions when I create a new file:-
O G P
6 6 4
rw rw r
RedHat-based systems cannot have execute permissions by default so you would get 666 instead of 777, so I'm assuming that 666 - 002 = 664; read/write for Owner and Group and read for Public. Is this how umask works? If so, is it user-specific, that is, can I change the value of umask for each user?
Now, I thought I had this down, but apparently not...
When I type "umask", I get the value 0002. Now, the first digit is unused, so that leaves 002. I'm only just getting round with numeric file permissions, but it is essentially this, AFAICT:-
0 No permissions
4 Read
5 Read / Execute
6 Read / Write
7 Read / Write / Execute
My book says that any new file created has new permissions automatically assigned by the value of umask. Hows does this work then? I get the following permissions when I create a new file:-
O G P
6 6 4
rw rw r
RedHat-based systems cannot have execute permissions by default so you would get 666 instead of 777, so I'm assuming that 666 - 002 = 664; read/write for Owner and Group and read for Public. Is this how umask works? If so, is it user-specific, that is, can I change the value of umask for each user?
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Re: The Official *nix Thread
Your umask is xor'd against 777 to determine the file creation mask.
So a umask of 077 will create a file with 700 permissions (actually it won't because the execute bit is never set by default)
*edit* you can set the umask per user in their .profile
So a umask of 077 will create a file with 700 permissions (actually it won't because the execute bit is never set by default)
*edit* you can set the umask per user in their .profile
Last edited by defsdoor on Tue Jun 16, 2009 8:28 pm 0, edited 1 time in total.
- disciple
- Sheepie Whore

- Posts: 13941
- Joined: Mon Oct 27, 2003 11:33 pm 0
- XBL Gamertag: LiberMentis
- PSN: Prime_Heretic
- Location: Greenfield
- Contact:
Re: The Official *nix Thread
Dunno, try `umask -S`
PS4 : Prime_Heretic
Steam: bitstorm
Elite Dangerous: Cmdr Britain
Steam: bitstorm
Elite Dangerous: Cmdr Britain
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Cool, so 'umask -S' makes it slightly more readable.
Are you sure it is XOR'd? The couple of Google links I looked at say that default file permissions for RedHat are 666 (non-executable by design, so 777 becomes 666) and that the umask is subtracted from that to get the default file permissions for that user based on the user-specific umask.
"The permission for the creation of new executable files is calculated by subtracting the umask value from the default permission value for the file type being created."
-- http://www.comptechdoc.org/os/linux/use ... ilesp.html
Correct?
Are you sure it is XOR'd? The couple of Google links I looked at say that default file permissions for RedHat are 666 (non-executable by design, so 777 becomes 666) and that the umask is subtracted from that to get the default file permissions for that user based on the user-specific umask.
"The permission for the creation of new executable files is calculated by subtracting the umask value from the default permission value for the file type being created."
-- http://www.comptechdoc.org/os/linux/use ... ilesp.html
Correct?
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Re: The Official *nix Thread
No - it's not XOR'd - it's mode & ~umask
Your umask allows you to override the permissions that a file create call use - giving you some control over programs. A program might like to be open to all users but you can easily restrict it's data files with your umask.
A program might want to create a file with 666 permissions - rw-rw-rw- but your umask can modify that. So a umask of 007 would result in files being created as 660 - rw-rw----
This is only restrictive masking though - if a program tries to create a file with 600 permissions your umask can't open that up wider but most programs actually look at you
It's slightly confusing because we talk of 664 files permissions etc.. yet umasks are a reverse mask. 770 and ANDing might have been easily for mortals to comprehend and I cannot think of a good reason offhand why straightforward ANDing wasn't used.
Your umask allows you to override the permissions that a file create call use - giving you some control over programs. A program might like to be open to all users but you can easily restrict it's data files with your umask.
A program might want to create a file with 666 permissions - rw-rw-rw- but your umask can modify that. So a umask of 007 would result in files being created as 660 - rw-rw----
This is only restrictive masking though - if a program tries to create a file with 600 permissions your umask can't open that up wider but most programs actually look at you
It's slightly confusing because we talk of 664 files permissions etc.. yet umasks are a reverse mask. 770 and ANDing might have been easily for mortals to comprehend and I cannot think of a good reason offhand why straightforward ANDing wasn't used.