I have experience working as a software developer for a storage company(C, C++). The applications I've been doing interface with the SCSI device driver on Unixware, Linux and Solaris to communicate/activate vendor unique features on our company's RAID devices. I also have programming experiences with IPC, TCP/IP, multiple processes,
IPC, SMTP and unix system files. (The books by Richard Stevens is a great help!) I can troubleshoot systems and network related problems, I'm familiar with systems administration and network security. I have played around with
lots of stuff on unix. And for the things I don't have experience on, I know where to look for the
answers.
so far, I can't get a job here in the United States because I don't have work papers. Those guys take their citizenship for granted and ohh... it so unfair.
I dunno if i'm allowed to discuss this but i don't remember signing a non disclosure agreement so here goes:
my previous company develops and produces RAID subsystems. about 3 years ago, we thought of developing a NAS solution. there was a lot of discussion on which technology, what type of approach and what would be the most practical solution. we had a severe shortage of software engineers so the plan was put aside for a while. our company just bought a 'NAS solution' from another vendor and placed it inside the RAID box. the 'NAS solution' from the vendor used VxWorks(as reported by nmap), provided SMB, FTP and printer sharing.
anyway, about a year ago, our company decided to make their own NAS solution(more profit that way). we started work on it. the plan was to use an embedded pc, install a stripped down version of linux, equip it with a very light web server(forgot the name), samba and use cgi (perl and C)for the webministration.
the hardware guys started integrating a SCSI and network controller on the embedded pc. the plan is basically to put a (small)pc running linux inside the RAID box. and the whole thing would be connected to the network via ethernet. we started testing, playing around and stripping down the applications which will be installed in the embedded pc. we had NO experience on how to make a NAS system. all we did was customize a version of linux to function as a NAS, installed it on an x86 based machine which happens to fit inside the RAID box. and there it is
I have a LOT of questions. especially to the ppl here on/. on what we did and did wrong:
1.) we used a 32MB IDE flash disk as the boot device(/dev/hda) and ran all the applications from there. the RAID subsystem(/dev/sda) is just for storage of the data. the IDE flash disk happens to be an off-the-shelf sandisk 32MB compactflash card. i think that decision is a mistake coz i've read that cf cards have a finite amount of read/write cycles. what do you guys think?
2.) we could have utilized some of the space in/dev/sda as storage for/etc and other config files but the big boys upstairs want the product released asap. there should be a way to isolate the user space from the system space on/dev/sda but we weren't able to explore the possibility further. any ideas and discussion on how this can be achieved?
3.) i've tried applying for jobs in companies that are doing NAS projects. but they (or their recruiter) demands 5+ years in kernel programming. or an equivalent amount in embedded system development. aside from unloading the unnecessary drivers, we did not do anything inside the kernel. any ideas on what are being integrated into the kernel by these companies?
4.) i've read a while ago that m$ is making changes to smb. if m$ is successful in making 'proprietary' changes in the smb protocol, would that make most NAS subsystem relying on samba obsolete?
5.) we were able to open up and play inside a NAS solution offered by Western digital. has anybody played reound with one of these devices (ala i-opener)?
is it really that hard to get into a tech related job today?
i recently came to the us to look for a tech related job (bad timing huh). i have 3 yrs c/c++ coding experience with scsi and tcp/ip. explored the unix/linux system files a lot, done some net administration and i know my way around the computer. i'm not an expert in anything but i know where to look for the answers. i'd love to work on embedded linux devices or software development in *nix. (actually, any tech-related job will be fine)
i have been to a lot of job sites but recruiters aren't interested in hiring someone that doesn't exactly match what they're looking for.
would you hire someone who managed to convince your recruiter that he/she is an expert in (e.g. kernel programming)?
when can you call yourself an expert in %insert_specialized_field_here ?
ummm... i'd love to have that. i came here (us)looking for work but i can't find anyone interested in hiring me. i'd love to have a machine where i can install my favorite os and continue my 'studies'.
a crested penguin with a placard that says "will code for food and an h1b"
Slashdot Mirror
I have experience working as a software developer for a storage company(C, C++). The applications I've been doing interface with the SCSI device driver on Unixware, Linux and Solaris to communicate/activate vendor unique features on our company's RAID devices. I also have programming experiences with IPC, TCP/IP, multiple processes,
IPC, SMTP and unix system files. (The books by Richard Stevens is a great help!) I can troubleshoot systems and network related problems, I'm familiar with systems administration and network security. I have played around with
lots of stuff on unix. And for the things I don't have experience on, I know where to look for the
answers.
so far, I can't get a job here in the United States because I don't have work papers. Those guys take their citizenship for granted and ohh... it so unfair.
...when mankind finally invents replicators(things that convert energy into matter)...
I dunno if i'm allowed to discuss this but i don't remember signing a non disclosure agreement so here goes:
/. on what we did and did wrong:
/dev/sda as storage for /etc and other config files but the big boys upstairs want the product released asap. there should be a way to isolate the user space from the system space on /dev/sda but we weren't able to explore the possibility further. any ideas and discussion on how this can be achieved?
my previous company develops and produces RAID subsystems. about 3 years ago, we thought of developing a NAS solution. there was a lot of discussion on which technology, what type of approach and what would be the most practical solution. we had a severe shortage of software engineers so the plan was put aside for a while. our company just bought a 'NAS solution' from another vendor and placed it inside the RAID box. the 'NAS solution' from the vendor used VxWorks(as reported by nmap), provided SMB, FTP and printer sharing.
anyway, about a year ago, our company decided to make their own NAS solution(more profit that way). we started work on it. the plan was to use an embedded pc, install a stripped down version of linux, equip it with a very light web server(forgot the name), samba and use cgi (perl and C)for the webministration.
the hardware guys started integrating a SCSI and network controller on the embedded pc. the plan is basically to put a (small)pc running linux inside the RAID box. and the whole thing would be connected to the network via ethernet. we started testing, playing around and stripping down the applications which will be installed in the embedded pc. we had NO experience on how to make a NAS system. all we did was customize a version of linux to function as a NAS, installed it on an x86 based machine which happens to fit inside the RAID box. and there it is
I have a LOT of questions. especially to the ppl here on
1.) we used a 32MB IDE flash disk as the boot device(/dev/hda) and ran all the applications from there. the RAID subsystem(/dev/sda) is just for storage of the data. the IDE flash disk happens to be an off-the-shelf sandisk 32MB compactflash card. i think that decision is a mistake coz i've read that cf cards have a finite amount of read/write cycles. what do you guys think?
2.) we could have utilized some of the space in
3.) i've tried applying for jobs in companies that are doing NAS projects. but they (or their recruiter) demands 5+ years in kernel programming. or an equivalent amount in embedded system development. aside from unloading the unnecessary drivers, we did not do anything inside the kernel. any ideas on what are being integrated into the kernel by these companies?
4.) i've read a while ago that m$ is making changes to smb. if m$ is successful in making 'proprietary' changes in the smb protocol, would that make most NAS subsystem relying on samba obsolete?
5.) we were able to open up and play inside a NAS solution offered by Western digital. has anybody played reound with one of these devices (ala i-opener)?
is it really that hard to get into a tech related job today?
i recently came to the us to look for a tech related job (bad timing huh). i have 3 yrs c/c++ coding experience with scsi and tcp/ip. explored the unix/linux system files a lot, done some net administration and i know my way around the computer. i'm not an expert in anything but i know where to look for the answers. i'd love to work on embedded linux devices or software development in *nix. (actually, any tech-related job will be fine)
i have been to a lot of job sites but recruiters aren't interested in hiring someone that doesn't exactly match what they're looking for.
would you hire someone who managed to convince your recruiter that he/she is an expert in (e.g. kernel programming)?
when can you call yourself an expert in %insert_specialized_field_here ?
ummm... i'd love to have that. i came here (us)looking for work but i can't find anyone interested in hiring me. i'd love to have a machine where i can install my favorite os and continue my 'studies'.
a crested penguin with a placard that says "will code for food and an h1b"